PKCS12 in FIPS mode, PKCS12KDF vs. PBKDF2

Hello, I have a question regarding usage of PKCS12 in FIPS mode. It is related to https://github.com/openssl/openssl/issues/19997, which claims that PKCS12KDF is not FIPS-compliant and thus cannot work in FIPS mode - I do not dispute that. But I also stumbled upon https://mta.openssl.org/pipermail/openssl-users/2021-January/013405.html that suggests that with PBKDF2 it should be ok...
I created a pfx file that looks like this:
$ openssl pkcs12 -info -noout -in test.pfx
Enter Import Password:
MAC: sha256, Iteration 2048
MAC length: 32, salt length: 8
PKCS7 Encrypted data: PBES2, PBKDF2, AES-256-CBC, Iteration 2048, PRF hmacWithSHA256
Certificate bag
PKCS7 Data
Shrouded Keybag: PBES2, PBKDF2, AES-256-CBC, Iteration 2048, PRF hmacWithSHA256

I can produce such pfx file both with openssl (with default provider) and wincrypt (regardless of FIPS mode of windows)...
But when trying to load this with openssl in FIPS mode, it fails on EVP_KDF_fetch(NULL, "PKCS12KDF", NULL) regardless of pfx file algorithms.
I tried to debug openssl code directly, I see that the call stack is like this:
p12_kiss.c:PKCS12_parse
p12_mutl.c:PKCS12_verify_mac
p12_mutl.c:pkcs12_gen_mac
p12_key.c:PKCS12_key_gen_utf8_ex
p12_key.c:PKCS12_key_gen_uni_ex

I see that the usage of PKCS12KDF is hardwired in PKCS12_key_gen_uni_ex().
I assumed that PKCS12KDF/PBKDF2 will be picked dynamically while processing the pfx. I see that PBKDF2 is available in FIPS mode.
If you can explain to me what's wrong with my understanding, I'd really appreciate. Thanks much.
PS: Currently on openssl 3.0.7. I checked quickly the 3.0.8/3.1.0-beta and saw that there is no significant changes with regard to PKCS12, just on latest main branch there is some enhancements allowing to work with PKCS12 from non-default OSSL_LIB_CTX...
To describe my scenario: I need to use the same cert and private key both on linux and windows. Now upgrading from 1.1.1 to 3.0 and have a requirement for FIPS compliance. The current implementation is using pfx to distribute the cert/key. My trouble is that wincrypt is not able to use anything but pfx to import the private key, while openssl (in FIPS) has trouble using pfx.

Please see the discussion in https://github.com/openssl/openssl/issues/19997.
Basically everything you have done is correct, however if you want to verify the integrity it uses PKCS12KDF (which is not FIPS).
So you either verify using a non fips algorithm, or you dont do the verify (with the -nomac option).
e.g:
LD_LIBRARY_PATH=. OPENSSL_CONF=./apps/openssl.cnf ./apps/openssl pkcs12 -export -out test.p12 -inkey test/certs/server-pss-key.pem -in test/certs/server-pss-cert.pem -certpbe AES-256-CBC -keypbe AES-256-CBC -macalg SHA256
....

LD_LIBRARY_PATH=. OPENSSL_CONF=test/fips-and-base.cnf OPENSSL_CONF_INCLUDE=test OPENSSL_MODULES=providers ./apps/openssl pkcs12 -provider fips -info -noout -in test.p12

Warning: -macsaltlen option ignored without -export
Enter Import Password:
MAC: sha256, Iteration 2048
MAC length: 32, salt length: 8
Error verifying PKCS12 MAC; no PKCS12KDF support.
Use -nomacver if MAC verification is not required.

Thank you for the prompt response @slontis, I do believe it helped me resolve my confusion.
The detail I was missing is the difference between the main PKCS12 document-level MAC (which mandates the usage of PKCS12KDF) and the individual nested bags that may employ different schemes/algorithms as they are defined by standards other than PKCS12.
The result being that PKCS12 may for now be used only without MAC verification when FIPS is enabled or without FIPS enabled.

The standard is horribly complex :)


使用docker-compose部署报错显示NeteaseCloudMusicApi有兼容性问题

Step 7/15 : RUN yarn install
 ---> Running in 8d69d8577487
yarn install v1.22.15
[1/4] Resolving packages...
warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>warning Resolution field<EMAIL_ADDRESS>is incompatible with requested version<EMAIL_ADDRESS>[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The CPU architecture "x64" is incompatible with this module.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info "<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "svg-sprite-loader > svg-baker ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 8.x".
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[4/4] Building fresh packages...

测试环境是虚拟机：
[root@terminal_01 YesPlayMusic-master]# cat /etc/redhat-release  CentOS Linux release 7.9.2009 (Core) [root@terminal_01 YesPlayMusic-master]# lscpu |grep Architecture Architecture:          x86_64

看起來沒問題——確實選中需要的版本了。只是不知道為何你的 yarn 特別 verbose。


Bump version and Add EventHubs sample

I upgrade the Kafka extension for the next release with EventHubs sample.
What I did

Add EventHubs sample
Update the documentation related ca.cert except for language samples.

Todo

Languages sample/documentation update

For language support, we don't need the ca.cert anymore, however, for the testing, we need published nuget.
I'll do this after publish the new version.

Hi @ryancrawcour If you are ok, could you approve this pr again?


Unable to type ' using AltGr modifier

Microsoft PowerToys version
0.55.0
Running as admin

[ ] Yes

Area(s) with issue?
General
Steps to reproduce
After updating PowerToys to 0.55.0, I have been unable to type ' using the combination AltGr+P on a Slovak keyboard when PowerToys is running. I've tried disabling all features, and not running as admin, to no effect.
The keyboard is configured under the English (United States) language like so:
✔ Expected Behavior
' to be inserted after pressing AltGr+P.
❌ Actual Behavior
No character is written.
Other Software
No response

Duplicate of #15910

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software.

This is fixed in release 0.55.1. Please update your PowerToys at https://aka.ms/installpowertoys

Seems to be working fine now


[Bug]: Non Visibility and No Effects of BuyMeACoffee Icon

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug

The BuyMeACoffee icon was not visible in Dark mode.
Also, It had no scale-up hover effects like the neighborhood icons

Expected behavior

The icon should be visible in both dark and light modes;
with similar scaling up hover effects;
with smooth transitions

Add ScreenShots
#Before

#After

Screen Recording
https://github.com/singodiyashubham87/Draw-it-out/assets/98605616/8dd615b8-3469-4a53-89ee-7f633d12c749
On which device are you experiencing this bug?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor
[X] I want to work on this issue

Please @singodiyashubham87 ,
Assign me this Issue so that I can start working on it.

White Bg to BuyMeACoffee icon is more better on the Dark Mode (than gray)

@shivamm-verma If you have searched the issues then haven't you saw this one https://github.com/singodiyashubham87/Draw-it-out/issues/236 ?
Duplicate issue, Closing.


Missing avatarCustomDisplaySize for class sap.f.AvatarGroup

OpenUI5 version: 1.101
Browser/version (+device/version): CR100
As per the docs, the sap.f.AvatarGroup control exposes the avatarDisplaySize property, similar to the property displaySize of the sap.m.Avatar, meaning it could also be sap.m.AvatarSize.Custom.
However, unlike the sap.m.Avatar, here a property to define this custom size is missing! There is no avatarCustomDisplaySize to correspond to the customDisplaySize of sap.m.Avatar.
Thus one must use a CSS workaround.

Hello @dfenerski,
Thank you for sharing this finding. I've created an internal incident with ID:<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Boyan Rakilovski

Hello,
This is indeed a missing handling for the control. A backlog item was scheduled for this to be added.
Best regards,
Jordan

Backlog item is BGSOFUIPIRIN-5695.

Great news about the progress, but can we expect this in the latest LTS 1.96? What's the policy on such cases?

Hello @dfenerski,
Unfortunately, since this is considered a feature request, downports to LTM versions are out of scope.
Regards,
Stanislav


Add new Al-Kharid palace agility shortcuts

Depends on #5799
Adds the new Al-Kharid palace shortcuts to the Agility plugins obstacles list.

Will rebase upon the merge of 5799.


send-hooks, webhook subscription management

Hi,
thanks for sharing this architecture. I know the webhook subscription management is optional, I did not see it in the template. is it possible to share that also? particularly the lambda to link webhook to eventbridge rule.
Dong

Hey @dzhang,
We are working on this and will get back to you.

Do you have any updates on the webhook subscription management template? This template would help me a lot!

Hey @Luan10017 - thanks for your interest. Unfortunately, we are still in progress and will let you know when ready. In the meantime, you can try using the relevant APIs.

I am interested too! :)

Interested about the subscription management as well :)


Demo screenshots

Hey, this sounds great, but it would be really awesome if you could add some demo screenshots to your README
Cheers :)

The demo app, even in its current state should suffice? http://imagine-demo.herokuapp.com

Thanks for providing the demo link,  the app is looking good.

Closing, more links and docs soon. I promise :)

Well, guess I'm not closing. I don't have permission.

Thanks for the link to the demo app, will close this for you :)


Not able to debug w/ Chrome

See https://github.com/facebook/react-native/issues/10729

Yeah, I've been hitting this one for months.  I'm only encountering this issue in files that contain multiple global functions (e.g. redux action files). I haven't encountered this in react component files which follow the pattern of stuffing most functions inside a single global react component class declaration.
My far from ideal workaround is to move the function under test to be the last function in the file.

This issue was also being tracked in react-native and someone posted solution there...
Replace
function someFn() {}
with
const someFn = () => {}
There can't be ANY functions in the source file you're trying to set a breakpoint in.
https://github.com/facebook/react-native/issues/10729

Wow!  Thanks!
On Jan 26, 2017 3:04 PM, "wookiem"<EMAIL_ADDRESS>wrote:

This issue was also being tracked in react-native and someone posted
solution there...
Replace
function someFn() {}
with
const someFn = () => {}
There can't be ANY functions in the source file you're trying to set a
breakpoint in.
https://github.com/facebook/react-native/issues/10729
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bartonhammond/snowflake/issues/164#issuecomment-275513115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABORPJ4ud--c93gnqNz2N0VqNNEgClBzks5rWQpYgaJpZM4Ky48D
.

@bartonhammond I was thinking about rewriting everything to ES6 since we're transpiling with babel anyway. In fact I already did that in my project so I should be able to create a PR fairly easy.

@siemiatj Sounds good - just make another PR!  Many thanks

I advise Vanilla JS if you can help it. Until the browsers (and node) add support for ES2015 imports/exports, you may be painting yourself into a corner unless you can get your binary packed up and off your plate. Just saying.

I won't agree here. We're using babel to transpile JSX anyways, and almost all examples now are written with ES6 syntax. It's still vanilla JS :) Node won't support modules probably for a while since it's problematic to implement (the last thing I heard).

Just FYI, you should try this again with RN 0.42. Evidently they refactored the source map generation, I tried it with our app in the areas where multiple functions in a file were having this issue and it seems to be fixed now.
<EMAIL_ADDRESS>


SDPManager allow limiting client's bitrate

Hello Team!
I need somehow to limit data bitrate sending by client. Is it possible on SFU side? Is it possible at all?
Thanks.

You can do it in the SDP answer in the bitrate field. It is not dynamic though.

@murillo128 Thanks a lot for reply. I'm using SDP Manager. Do we have some interface of doing this?

not currently sorry, you can modify the sdp string on text mode.

@murillo128 Got it. Thanks. Can be closed.

let's open it as a feature request

I think you can control bitrate using rtpsender in the client.  @tomas-berg


SpinFort show eggs

Short Description:
SpinFort wasn't printing eggs when they were awarded at spinning.
It now prints the egg with his km and adds it do the db too.

Oh, now I know why I had ever seen the eggs.

👍

@solderzzc me too!
@DeXtroTip nice!


Exposing the Oid of PostgreSQL types

This PR closes #1111 and supersedes #2146. It adds a function to retrieve OIDs, which is very useful in very dynamic schemas, such as DBMSs or when you want to provide a more low-level interface to the DB.
This function is a non-panicking alternative to .oid().

@abonander is this a better solution to the situation? Could this be reviewed?

This is fine as long as the documentation is very clear about the caveats. The suggested change has those.

This is fine as long as the documentation is very clear about the caveats. The suggested change has those.
The try_ prefix of the method suggests that the implementation will attempt to look up the OID, so that should be omitted.

Makes total sense to me :) I added your changes to the PR. Thanks for reviewing it!

@Razican can you run cargo fmt real quick? It doesn't like something in my suggested change but it's not obvious what (maybe a Tab character got in there somehow).

Done :)


Extend playbook validation: Error out if there is an unknown key in vars/ansible_bender/

Fixes #92

/packit copr-build

@TomasTomecek I have updated the list, hope everything is covered for vars/ansible_bender

@TomasTomecek for the multilevel extraction of keys in the dictionary, I am thinking of using a stack to solve it, what are your thoughts regarding it.

/packit copr-build

I looked at json schema if it's able to help us here and... It seems it is!
https://stackoverflow.com/questions/53770325/additionalproperties-rule-in-json-schema-is-not-applied-to-nested-level-proper
Seems like that all we need to do is to enable additionalProperties: false on all the levels which will disallow unknown keys in the dict

I looked at json schema if it's able to help us here and... It seems it is!
https://stackoverflow.com/questions/53770325/additionalproperties-rule-in-json-schema-is-not-applied-to-nested-level-proper
Seems like that all we need to do is to enable additionalProperties: false on all the levels which will disallow unknown keys in the dict

That will be an awesome fix :stars:, thank you

\packit test

/packit test

I looked at json schema if it's able to help us here and... It seems it is!
https://stackoverflow.com/questions/53770325/additionalproperties-rule-in-json-schema-is-not-applied-to-nested-level-proper
Seems like that all we need to do is to enable additionalProperties: false on all the levels which will disallow unknown keys in the dict

@TomasTomecek What I found was BUILD_SCHEMA has got only one properties key so I can add additionalProperties key only to one level.

Also a test case here would be awesome!

/packit test

/packit test

/packit test

/packit test

/packit test

The F30 copr issue should be fixed now hopefully:
https://gitlab.com/testing-farm/cruncher/merge_requests/7

/packit test

/packit test

/packit test

/packit test

@TomasTomecek I am not sure where actually the problem lies, I request your review on this.

I finally figured it out, now I understand why you were so confused about this - took me some time to understand what's wrong. Here we go:

You were right - validate method of ImageMetadata is not being called anywhere:
https://github.com/ansible-community/ansible-bender/blob/1cf0518581fb0447c9fe48108b2f229bf6f6297b/ansible_bender/conf.py#L77
The code which needs to be changed lies in core.py, class PbVarsParser
https://github.com/ansible-community/ansible-bender/blob/1cf0518581fb0447c9fe48108b2f229bf6f6297b/ansible_bender/core.py#L235
That class creates a playbook which exapands all the variables defined in vars section of a playbook - this has to be done so that people can use jinja templating in ansible_bender section of vars
And that's place where we need to introduce validation.
So once we update our internal structure with data from the playbook, we should validate that our structure is valid, that would be here:
https://github.com/ansible-community/ansible-bender/blob/1cf0518581fb0447c9fe48108b2f229bf6f6297b/ansible_bender/core.py#L365

That's great you wrote a test case for this - we can now check whether this would be a better solution to the problem.

/packit test

I finally figured it out, now I understand why you were so confused about this - took me some time to understand what's wrong. Here we go:

You were right - validate method of ImageMetadata is not being called anywhere:
https://github.com/ansible-community/ansible-bender/blob/1cf0518581fb0447c9fe48108b2f229bf6f6297b/ansible_bender/conf.py#L77
The code which needs to be changed lies in core.py, class PbVarsParser
https://github.com/ansible-community/ansible-bender/blob/1cf0518581fb0447c9fe48108b2f229bf6f6297b/ansible_bender/core.py#L235
That class creates a playbook which exapands all the variables defined in vars section of a playbook - this has to be done so that people can use jinja templating in ansible_bender section of vars
And that's place where we need to introduce validation.
So once we update our internal structure with data from the playbook, we should validate that our structure is valid, that would be here:
https://github.com/ansible-community/ansible-bender/blob/1cf0518581fb0447c9fe48108b2f229bf6f6297b/ansible_bender/core.py#L365

That's great you wrote a test case for this - we can now check whether this would be a better solution to the problem.

@TomasTomecek I have worked out as you said, I wish to have your review, again!

/packit test

/packit test

/packit test

/packit test

/packit test

/packit test

no need to do that: every push is first built as an RPM and then used in the testing infra

/packit test

meh, sorry for the delay, I was lazy to implement cleanup of jobs and this is the result :( Cleaning up manually now

things will resume soonish

okay so let's green this PR, merge it and release ab 0.8


Retrigger bodhi update via dist-git PR comment

I'm sorry it took so long. I couldn't find the time to come back to this issue recently :disappointed:
note: OGR doesn't have has_write_access method. Not yet. I am going to implement it :)
also help needed :grin::  test_bodhi_update_retrigger_via_dist_git_pr_comment won't pass because because the CreateBodhiUpdateHandler.run method is not called. Even though the task.bodhi_update task gets the signature of the Celery task. This means that the JobHandler.get_signature method is executed and according to its documentation the run_bodhi_update task should be run, but this obviously does not happen. Any idea why?
Fixes #1541

RELEASE NOTES BEGIN
Packit now allows to re-trigger Bodhi update via dist-git PR comment /packit create-update.
RELEASE NOTES END

Thanks for finding time to implement this! I will have a closer look at the PR later. But as for the question:

also help needed :grin: test_bodhi_update_retrigger_via_dist_git_pr_comment won't pass because because the CreateBodhiUpdateHandler.run method is not called. Even though the task.bodhi_update task gets the signature of the Celery task. This means that the JobHandler.get_signature method is executed and according to its documentation the run_bodhi_update task should be run, but this obviously does not happen. Any idea why?

Since there is no real Celery in the tests, we call some methods which would Celery do  => call the run_.. ourselves :D yes, there is definitely a place for improvement of the tests, we already discussed splitting the integration tests to not test the whole use case at once. You can see how this should be done e.g. here.

I'll take it in points:

I have this error and maybe it could be somehow related with the tests (but I am not sure)

well the reason why you get this error is that the get_latest_build_in_tag method should be static, because the self parameter is not used. Only I forgot to make a PR in the packit repository that removes the self parameter :D thanks for pointing to it

Should we take the last built Koji package from the db instead?

I'm not sure if I get your point. However, I tried to recreate the KojiBuildEvent (because I didn't know that koji has python API) using data from the database. I ended up adding a some new stuff to the database and code in general, and the result was a lot of extra code. On top of that, most of the tests were crashing :D

but I think that in the commit named Feat(bodhi hangler): Get last koji build from koji api we expect a KojiBuildEvent even if in this case we are reacting to a PullRequestCommentPagureEvent which has not the needed Koji data

I don't think that KojiBuildEvent is relevant in this context. We only need to extract a minimal amount of information from it, so I have created a wrapper that contains the minimal amount of information we need to re-trigger a bodhi update. Basically, the user wants to re-trigger the bodhi update and we are not interested in KojiBuildEvent (besides the above mentioned amount of information to re-trigger the bodhi update). Compared to creating a whole KojiBuildEvent, I don't think it's worth it in the current situation. (Although it's possible that the koji API has tools to get all the information (for example ClientSession().getBuild()). However, I haven't read that much documentation and also getBuild method doesn't return everything (I think).

I tried your changes locally with podman-compose.

Wow that's cool, I could use it at least 50 times already... How? :D I didn't know we are able to run packit service locally. Do we have it documented somewhere? How you do it? :D

I think you don't need to do that; here you can see that the list of Koji builds is optional.

Yes, I know that if I'll set the koji_builds parameter to None it gets the latest build. However the problem is that we need some data for logging, creating error messages and generally in the pre-check method. So this means we still have to get the data somehow.

then the latest Koji builds are searched in the same way you are doing

Unfortunately yes. But at least I am trying to use at least get_latest_build_in_tag method from packit. As I described above - we need this data not only for create_update but for logs, etc...
But if you have an idea how to get around it without searching for the data in the way I do it then I am open to suggestions :innocent:

will you be able to finish this (I only added 2 notes) or should we help you somehow?

We have discussed with Jirka that we will probably meet next Thursday to finish this. (And that we can help if needed.)

I am wondering whether we should solve this here or do it together for retriggering Koji builds by comment where this is missing as well

I would open a followup to that :) so we can get this merged finally


python311Packages.reconplogger: 4.13.0 -> 4.14.0

Diff: https://github.com/omni-us/reconplogger/compare/refs/tags/v4.13.0...v4.14.0
Description of changes

Things done

Built on platform(s)

[ ] 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

[ ] Fits CONTRIBUTING.md.

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

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

4 packages built:

python311Packages.reconplogger
python311Packages.reconplogger.dist
python312Packages.reconplogger
python312Packages.reconplogger.dist


PLATFORM-517: implemented vault delete and added test coverage

This PR adds required vault delete command and adds test coverage. To facilitate testing the signature of the client was modified slightly so that guzzle can be injected instead magically instantiated in the constructor.
ping @rayward @bigcommerce-labs/platform

I've enabled travis on the repo, so if you push another commit, it should build 🙏


Implementation probably incorrect

Current implementation of Life is probably incorrect:

There should be no stable configurations like

X.
XX

-- they should mutate to stable block
XX
XX

There almost always "semaphores" present

XXX

which flips to
X
X
X

every turn
Traditional implementation usually populates every generation from initially empty field, calculating cell presence by inspecting neighbour 9 cells from previous grid for every cell.
Then you'll see "blocks", "hives", "semaphores", "gliders", "frigates" and all other stuff. Even self-replicated custom configurations were found.

Many thanks for your opinion and review, I agree that this implementation works not fine and I will fix it


Castle Wars Timer Feature

Is your feature request related to a problem? Please describe.
I am in a castle wars clan and we often have people asking for the "ttg" time-to-game. There is almost always someone playing the game, however I was thinking a RL plugin wouldn't be that difficult?
Describe the solution you'd like
If you enter the cws portal, the plugin shows you the timers of the games or the time until the next game until the next server reset.
Describe alternatives you've considered
As I stated above, maybe it can show the start times of all the games during the day? At the very least a timer that shows time until the next game. It would be cool if it showed you the time till game ends and then the 5 minute lobby time and then the game start.

How would we get those timers? That's entirely server-sided information which the client cannot see unless you are actually in the waiting zones.

Castle Wars games happen every 25 minutes (20 minute game, 5 minute lobby). As there is always a game occurring on w334, entering the portal should show how much time there is left until the next game. With that, it should be possible to always know when games are starting as they happen at regular intervals until world reset.

How would we get those timers? That's entirely server-sided information which the client cannot see unless you are actually in the waiting zones.

I figured the timer wouldn't be active unless the person stepped into a portal and then it would take the time and print out a list of all the game times and/or showed when the next game would be. Like maybe theres a tab in runelite that shows all the times and then theres a little icon like a minigame teleport cooldown that shows time to next game?


Flappy Bird Game Agent

Aim
This is the AI agaent which addapt the environment of the Flappy Bird Game using Reinforcement Learning with Open AI Gym environment.
Details
Performance of  Agent
https://user-images.githubusercontent.com/51924622/121337387-1dca1080-c93a-11eb-9b9f-61bf00bc327f.mp4

What the features will your script have

@avinashkranjan Please Assign me this issue under GSSoc23

Go Ahead @ayush-09


Official dendron wiki contains youtube videos marked as "Made for kids"

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] UI
[ ] Workbench
[ ] Publishing
[ ] Pods
[ ] Markdown
[ ] Hierarchy
[ ] Graph
[x] Misc (Choose this if your not sure)

Describe the bug
The embedded videos on the wiki are embedded from youtube, but they have been marked as content made for kids. This disables certain youtube features. I cannot add the video to my own Watch Later playlist.
Most users won't be able to dedicate an hour of time to look through the wiki and watch the onboarding video when they first come across the wiki. I would love to check this out later and I'm sure other people would too, but if I can't look back at it in my watch later playlist in my own time, then I might not remember to check out dendron.
To Reproduce

Go to https://wiki.dendron.so/#onboarding
Click on "Watch on YouTube" (inside the video embed)
Click "Save"
See error:

Expected behavior
I should be able to add the video to my watch later playlist.
Screenshots

Thanks for that. Didn't realize that saving would be disabled. Just updated the audience section of all the Dendron videos so you should be able to save going forward!


Don't ping users for their own messages

addresses: https://github.com/TheSkeward/omega-bot/issues/137

Also addresses #64


How to run different tasks on multiple servers

In staging I have 3 servers: 2 frontends and a load balancer.
The set of tasks to execute are different on the frontends and the load balancer.
I believe that only one set of servers can be specified and the tasks will act on them.
How can I set up the tasks to work on different set of servers at the same time without running shipit 2 times in a row (by specifying for example a deploy-staging-frontend and deploy-staging-loadbalancer tasks)
OR by doing something more hacky like:
// do things on frontend servers
// [...]
shipit.config.servers = ['loadbalancer.com']
shipit.initSshPool();
// [...]
// now do things on the load balancer

TL;DR;
How can I specify multiple pools and run tasks on specific pools?
Thank you

@mikegleasonjr you can't for now.


Development of an official DNP3 library for Espressif SoCs (IDFGH-11322)

Is your feature request related to a problem?
No response
Describe the solution you'd like.
Develop the DNP3 library to be used in the Espressif SoCs based in the Standard as the same way as it was developed the Lib for Modbus
Describe alternatives you've considered.
Instead to write down the protocol in code, by using a library which could be easily and widdely used for Utilities Automation integration with supervisories (SCADA)
Additional context.
DNP3 protocol is very widely used inside the utilities as it has a more powerfull concept than Modbus, and aloows more precise and accurate data exchange between automation devices.

@shukrhu We will not support this library in ESP-IDF, as this is not a widely used IoT protocol. Besides esp_modbus, there might be some future plans on other industrial protocol support, but not DNP3.
We'd leave this open for a bit, to see if there's any other comments.

Closing as there's no recent activity.
Assessment: will not support DNP3 in IDF.


Contribution guidelines and Code of Conduct

Adding a Contributors guideline that's heavily borrowed from here
And a Code of Conduct from here
@StanczakDominik ^

Thanks!


Everything about this mod can be changed via the config ?

but when i look for a config its just lategame_upgrades\installing.txt and the License ? installed with r2 modman
the mod works i just cant config anything

Config files are generated in Bepinex/config/
This one starts with com.malco

If you're using r2modman you can edit the config with the manager

oh okay i found it thanks


Remove dict comprehension for older python

dict comprehension is introduced in python 2.7 and doesn't work on 2.6 or older

Is this the only thing that is not compatible 2.6? I have never tested the lib with python2.6. Is it really worth supporting?

I found it when I tried to pack an RPM for centos6.5 and python2.6 complained about it doesn't know how to handle the syntax. So I could safely assume that's the only syntax not compatible with 2.6. For other parts as far as I've tested, runs well with 2.6.

Alright then!  Thank your for contributing :)

Merged Remove dict comprehension for older python #150


add mesos-demo example

Signed-off-by: Amre Shakimov<EMAIL_ADDRESS>

This looks good. @tgraf  should we try to integrate this in our CI?

This looks good. @tgraf should we try to integrate this in our CI?

Yes we definitely should


Remove dependence on Polymer

Similar to ajax-form, I don't believe file-input benefits much from Polymer. In fact, it makes maintenance more complicated, IMHO. This was discussed a bit more at rnicholus/ajax-form#55.

When do you plan to finish?

Shortly after I start.

With some of the recent breaking changes to the Shadow DOM spec, and the fact that moving away from polymer requires a lot more code in the case of <file-input>, I'm wondering if it's worth the effort to go this route at the moment. My ajax-form element was pretty easy to decouple from polymer. Also, unit tests still need to be rewritten.

I'm not sure it makes sense to do this, given what Polymer provides. A fair amount of boilerplate code would have to be introduced. I think the best choice is to update file-input to work with Polymer 1.x instead.

Good for me.
And could you please provide some date when do you plan to migrate to 1.0 (more or less) ?

No, sorry.
On Wed, Jul 29, 2015 at 7:56 AM Kamil<EMAIL_ADDRESS>wrote:

Good for me.
And could you please provide some date when do you plan to migrate to 1.0
(more or less) ?
—
Reply to this email directly or view it on GitHub
https://github.com/rnicholus/file-input/issues/24#issuecomment-125941012
.


feat: [M3-6427] - Add No Results section for Marketplace Search

Description 📝
Add No Results section for Marketplace Search
Preview 📷

Remove this section or include a screenshot or screen recording of the change
How to test 🧪

Navigate to Marketplace search
Search for app that doesn't exists (ex; datadog)
Should display "No Results" message.

How do I run relevant unit or e2e tests?

yarn test
yarn cy:run

Nice, it works well!
Would it be possible to center the "No Results" text?

Do we need any other input from the UX team as far as wording and design should go?

Thank you @jdamore-linode and @mjac0bs thank you for the feedback, I will circle back with UX on this.

Thank you for the feedback. Based on the UX feedback, updated the no results copy and adjusted alignment to center.

Nitpicks on copy: I'm wondering if clearer copy might read: "Sorry, no results matched your search for "datadog". Please try another term."
Thought process being:

"no  results" sounds kind of strange and is slightly harder to scan as a reader than "no results"
telling the user to "please try again" feels misleading because if the user were to try the same action again, the results would be the same. It feels more clear to state what they should actually try to yield different results.

What do others (and UX) think?

@mjac0bs Agreed that "Sorry, no results matched your search for "datadog" sounds clearer. I don't think we even need the second sentence as it's pretty obvious that the user should search for a different term

Let's remember to update changelog too 👍


Extra entry Saxion (students)

There should be another entry for saxion students because the format for students has changed, the old one should not be deleted/moved because teachers still use the old entry.
Old and new format for teachers:
<EMAIL_ADDRESS>Old student format:
<EMAIL_ADDRESS>New student format:
<EMAIL_ADDRESS>

@ConventionalEcho I merge this pull request, but it does not influence the ability of students to request licenses, because all subdomains of domains listed in this repository are considered valid by default. Thank you!


Community Page

Create a community page:

How to get involved with IETF & SCITT
SCITT regular meetings
SCITT on the IETF Email lists
SCITT on Slack

hey @SteveLasker ,can u elaborate more on this issue

Hi @DHRUVKHANDELWAL00, welcome to the SCITT community.
We'd like to host a page that provides insight into how folks can get involved. The page would incorporate the topics above.
Some examples:

Helm Community
ORAS Community

I am willing to pick this up if no maintainer objects.


C0-9255-1 after uninstalling and going back to CEX

Hi,
I've uninstalled the DEX mode, I've restored the system and I'm on 3.74 CEX.
I can open the PS Store and see the content but I can't download anything (Error c0-9255-1) and I get the same error even trying to activate the system through settings.
What can the problem be?
Thanks

I thought that uninstalling the DEX mode would restore the original CID. In that case, is there any plugin for 3.60 DEX to remove the red expiration message ?

https://github.com/Princess-of-Sleeping/Red-Msg-Delete

C0-9255-1 does not match the OpenPsid of the device and the OpenPsid of the content.

Would it be possible to restore the openpsid via another method?

#2

Is there any way to retrieve the original overwritten open psid?

IdStorage::Leaf 65 -> offset 0x198 0x10-bytes

Sorry for reviving this but apparently i'm having the same issue when i access the PlayStation store
I've been trying to figure out for days on how to restore my cID through act.dat because of MLTActivator (unrelated but still)


fixes incompatibility with new odata primitive format.

Related to https://github.com/microsoft/OpenAPI.NET.OData/pull/589
Latest changes in the conversion library add the type property to the schema of the ReferenceNumeric type used in odata primitives.
This causes incompatibility with the IsODataPrimitiveType which only expects one schema to have the type of string.
This PR updates the implementation so that the new scenario is captured and older documents with the older format are not broken by this change.

Generation run for this PR at https://dev.azure.com/microsoftgraph/Graph Developer Experiences/_build/results?buildId=166335&view=logs&j=0c914960-8b50-5299-c9aa-dd3c9595168e&t=10763a1c-e2a2-5bd5-46f6-1e38af74bcce
With the generated commit confirming no composed types at https://github.com/microsoftgraph/msgraph-sdk-dotnet/compare/main...kiota/v1.0/pipelinebuild/166335


GetID panic in TestDownloading

Extracted this problem from #2718, where it didn't belong
kiai$ sudo rkt run --net=host --dns=<IP_ADDRESS> --volume src-dir,kind=host,source="$(pwd)" --volume build-dir,kind=host,source="$(pwd)/release-build" --interactive coreos.com/rkt/builder:1.2.0 --exec /bin/sh
# make check
make check
  ACTOOL       /opt/build-rkt/target/bin/stage1-coreos.aci
  COPY FILES   kvm-qemu
  ACTOOL       /opt/build-rkt/target/bin/stage1-kvm.aci
can't load package: package ./release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic: read /opt/rkt/release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic/vmlinux.its.S: syntax error
can't load package: package ./release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic: read /opt/rkt/release-build/tmp/usr_from_kvm/kernel/linux-4.9.2/arch/mips/generic/vmlinux.its.S: syntax error
  GOFMT        ./api/v1 ./api/v1alpha ./common ./common/apps ./common/cgroup ./common/cgroup/v1 ./common/cgroup/v2 ./common/labelsort ./common/networking ./common/overlay ./lib ./networking ./networking/netinfo ./networking/tuntap ./pkg/aci ./pkg/aci/acitest ./pkg/backup ./pkg/distribution ./pkg/fileutil ./pkg/flag ./pkg/fs ./pkg/group ./pkg/keystore ./pkg/keystore/keystoretest ./pkg/label ./pkg/lock ./pkg/log ./pkg/mountinfo ./pkg/multicall ./pkg/passwd ./pkg/pod ./pkg/selinux ./pkg/set ./pkg/sys ./pkg/tar ./pkg/tpm ./pkg/user ./rkt ./rkt/config ./rkt/flag ./rkt/image ./rkt/pubkey ./stage0 ./stage1/app_add ./stage1/app_rm ./stage1/app_start ./stage1/app_stop ./stage1/attach ./stage1/common ./stage1/common/ssh ./stage1/common/types ./stage1/enter_kvm ./stage1/gc ./stage1/init ./stage1/init/common ./stage1/init/kvm ./stage1/init/kvm/hypervisor ./stage1/init/kvm/hypervisor/hvlkvm ./stage1/init/kvm/hypervisor/hvqemu ./stage1/iottymux ./stage1/stop ./stage1/stop_kvm ./stage1_fly/enter ./stage1_fly/gc ./stage1_fly/run ./stage1_fly/stop ./store/db ./store/imagestore ./store/treestore ./tests ./tests/cniproxy ./tests/echo-socket-activated ./tests/inspect ./tests/rkt-monitor ./tests/rkt-monitor/cpu-stresser ./tests/rkt-monitor/log-stresser ./tests/rkt-monitor/mem-stresser ./tests/rkt-monitor/sleeper ./tests/stub-stage1/enter ./tests/stub-stage1/gc ./tests/stub-stage1/run ./tests/testutils ./tests/testutils/aci-server ./tests/testutils/logger ./tools/cleangen ./tools/common ./tools/common/filelist ./tools/depsgen ./tools/filelistgen ./tools/quickrm ./version
  GO VET       github.com/rkt/rkt/api/v1 github.com/rkt/rkt/api/v1alpha github.com/rkt/rkt/common github.com/rkt/rkt/common/apps github.com/rkt/rkt/common/cgroup github.com/rkt/rkt/common/cgroup/v1 github.com/rkt/rkt/common/cgroup/v2 github.com/rkt/rkt/common/labelsort github.com/rkt/rkt/common/networking github.com/rkt/rkt/common/overlay github.com/rkt/rkt/lib github.com/rkt/rkt/networking github.com/rkt/rkt/networking/netinfo github.com/rkt/rkt/networking/tuntap github.com/rkt/rkt/pkg/aci github.com/rkt/rkt/pkg/aci/acitest github.com/rkt/rkt/pkg/backup github.com/rkt/rkt/pkg/distribution github.com/rkt/rkt/pkg/fileutil github.com/rkt/rkt/pkg/flag github.com/rkt/rkt/pkg/fs github.com/rkt/rkt/pkg/group github.com/rkt/rkt/pkg/keystore github.com/rkt/rkt/pkg/keystore/keystoretest github.com/rkt/rkt/pkg/label github.com/rkt/rkt/pkg/lock github.com/rkt/rkt/pkg/log github.com/rkt/rkt/pkg/mountinfo github.com/rkt/rkt/pkg/multicall github.com/rkt/rkt/pkg/passwd github.com/rkt/rkt/pkg/pod github.com/rkt/rkt/pkg/selinux github.com/rkt/rkt/pkg/set github.com/rkt/rkt/pkg/sys github.com/rkt/rkt/pkg/tar github.com/rkt/rkt/pkg/tpm github.com/rkt/rkt/pkg/user github.com/rkt/rkt/rkt github.com/rkt/rkt/rkt/config github.com/rkt/rkt/rkt/flag github.com/rkt/rkt/rkt/image github.com/rkt/rkt/rkt/pubkey github.com/rkt/rkt/stage0 github.com/rkt/rkt/stage1/app_add github.com/rkt/rkt/stage1/app_rm github.com/rkt/rkt/stage1/app_start github.com/rkt/rkt/stage1/app_stop github.com/rkt/rkt/stage1/attach github.com/rkt/rkt/stage1/common github.com/rkt/rkt/stage1/common/ssh github.com/rkt/rkt/stage1/common/types github.com/rkt/rkt/stage1/enter_kvm github.com/rkt/rkt/stage1/gc github.com/rkt/rkt/stage1/init github.com/rkt/rkt/stage1/init/common github.com/rkt/rkt/stage1/init/kvm github.com/rkt/rkt/stage1/init/kvm/hypervisor github.com/rkt/rkt/stage1/init/kvm/hypervisor/hvlkvm github.com/rkt/rkt/stage1/init/kvm/hypervisor/hvqemu github.com/rkt/rkt/stage1/iottymux github.com/rkt/rkt/stage1/stop github.com/rkt/rkt/stage1/stop_kvm github.com/rkt/rkt/stage1_fly/enter github.com/rkt/rkt/stage1_fly/gc github.com/rkt/rkt/stage1_fly/run github.com/rkt/rkt/stage1_fly/stop github.com/rkt/rkt/store/db github.com/rkt/rkt/store/imagestore github.com/rkt/rkt/store/treestore github.com/rkt/rkt/tests github.com/rkt/rkt/tests/cniproxy github.com/rkt/rkt/tests/echo-socket-activated github.com/rkt/rkt/tests/inspect github.com/rkt/rkt/tests/rkt-monitor github.com/rkt/rkt/tests/rkt-monitor/cpu-stresser github.com/rkt/rkt/tests/rkt-monitor/log-stresser github.com/rkt/rkt/tests/rkt-monitor/mem-stresser github.com/rkt/rkt/tests/rkt-monitor/sleeper github.com/rkt/rkt/tests/stub-stage1/enter github.com/rkt/rkt/tests/stub-stage1/gc github.com/rkt/rkt/tests/stub-stage1/run github.com/rkt/rkt/tests/testutils github.com/rkt/rkt/tests/testutils/aci-server github.com/rkt/rkt/tests/testutils/logger github.com/rkt/rkt/tools/cleangen github.com/rkt/rkt/tools/common github.com/rkt/rkt/tools/common/filelist github.com/rkt/rkt/tools/depsgen github.com/rkt/rkt/tools/filelistgen github.com/rkt/rkt/tools/quickrm github.com/rkt/rkt/version
  (C) CHECK
  GO TEST      github.com/rkt/rkt/common github.com/rkt/rkt/common/cgroup/v1 github.com/rkt/rkt/common/labelsort github.com/rkt/rkt/common/overlay github.com/rkt/rkt/pkg/backup github.com/rkt/rkt/pkg/distribution github.com/rkt/rkt/pkg/fileutil github.com/rkt/rkt/pkg/flag github.com/rkt/rkt/pkg/group github.com/rkt/rkt/pkg/keystore github.com/rkt/rkt/pkg/lock github.com/rkt/rkt/pkg/log github.com/rkt/rkt/pkg/mountinfo github.com/rkt/rkt/pkg/passwd github.com/rkt/rkt/pkg/pod github.com/rkt/rkt/pkg/selinux github.com/rkt/rkt/pkg/set github.com/rkt/rkt/pkg/tar github.com/rkt/rkt/pkg/user github.com/rkt/rkt/rkt github.com/rkt/rkt/rkt/config github.com/rkt/rkt/rkt/flag github.com/rkt/rkt/rkt/image github.com/rkt/rkt/stage1/init/common github.com/rkt/rkt/stage1/init/kvm github.com/rkt/rkt/store/db github.com/rkt/rkt/store/imagestore github.com/rkt/rkt/store/treestore
ok  	github.com/rkt/rkt/common	1.020s	coverage: 23.6% of statements
ok  	github.com/rkt/rkt/common/cgroup/v1	1.008s	coverage: 10.2% of statements
ok  	github.com/rkt/rkt/common/labelsort	1.007s	coverage: 61.5% of statements
ok  	github.com/rkt/rkt/common/overlay	1.006s	coverage: 37.5% of statements
ok  	github.com/rkt/rkt/pkg/backup	1.014s	coverage: 71.9% of statements
ok  	github.com/rkt/rkt/pkg/distribution	1.037s	coverage: 70.1% of statements
ok  	github.com/rkt/rkt/pkg/fileutil	1.012s	coverage: 31.9% of statements
ok  	github.com/rkt/rkt/pkg/flag	1.006s	coverage: 86.5% of statements
ok  	github.com/rkt/rkt/pkg/group	1.007s	coverage: 35.7% of statements
ok  	github.com/rkt/rkt/pkg/keystore	1.280s	coverage: 52.6% of statements
ok  	github.com/rkt/rkt/pkg/lock	1.008s	coverage: 77.2% of statements
ok  	github.com/rkt/rkt/pkg/log	1.005s	coverage: 62.9% of statements
ok  	github.com/rkt/rkt/pkg/mountinfo	1.201s	coverage: 78.4% of statements
ok  	github.com/rkt/rkt/pkg/passwd	1.005s	coverage: 31.7% of statements
ok  	github.com/rkt/rkt/pkg/pod	1.169s	coverage: 23.4% of statements
ok  	github.com/rkt/rkt/pkg/selinux	1.006s	coverage: 3.4% of statements
ok  	github.com/rkt/rkt/pkg/set	1.006s	coverage: 100.0% of statements
ok  	github.com/rkt/rkt/pkg/tar	8.081s	coverage: 51.5% of statements
ok  	github.com/rkt/rkt/pkg/user	1.009s	coverage: 53.4% of statements
TestOpenSocket: Listening on 1 systemd-provided socket(s)
TestOpenSocket: Listening on localhost:0
Downloading ACI: 0 B of an unknown total size
Downloading ACI: 3.07 KB of an unknown total size

--- FAIL: TestDownloading (0.54s)
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x752b2a]

goroutine 23 [running]:
panic(0xf98fe0, 0xc42000e120)
	/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1ae
testing.tRunner.func1(0xc42044d500)
	/usr/lib/go-1.7/src/testing/testing.go:579 +0x474
panic(0xf98fe0, 0xc42000e120)
	/usr/lib/go-1.7/src/runtime/panic.go:458 +0x271
github.com/rkt/rkt/store/treestore.(*Store).GetID(0x0, 0xc4200a43f0, 0x47, 0xc4203f58e0, 0xc4203f58a0, 0x170ca00, 0xc420029840)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/store/treestore/tree.go:93 +0xea
github.com/rkt/rkt/store/treestore.(*Store).Render(0x0, 0xc4200a43f0, 0x47, 0xc4200a4300, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/store/treestore/tree.go:115 +0xd7
github.com/rkt/rkt/rkt/image.(*Fetcher).FetchImage(0xc4203f5cc8, 0x1713400, 0xc420409f80, 0xc4201b27e0, 0x17, 0x0, 0x0, 0xc42007c020, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/rkt/image/fetcher.go:89 +0x3d8
github.com/rkt/rkt/rkt.TestDownloading(0xc42044d500)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/rkt/fetch_test.go:295 +0x158a
testing.tRunner(0xc42044d500, 0x1147870)
	/usr/lib/go-1.7/src/testing/testing.go:610 +0xca
created by testing.(*T).Run
	/usr/lib/go-1.7/src/testing/testing.go:646 +0x530
FAIL	github.com/rkt/rkt/rkt	0.586s
ok  	github.com/rkt/rkt/rkt/config	1.023s	coverage: 74.1% of statements
ok  	github.com/rkt/rkt/rkt/flag	1.006s	coverage: 40.7% of statements
ok  	github.com/rkt/rkt/rkt/image	1.029s	coverage: 7.1% of statements
ok  	github.com/rkt/rkt/stage1/init/common	1.013s	coverage: 7.6% of statements
ok  	github.com/rkt/rkt/stage1/init/kvm	1.009s	coverage: 19.4% of statements
ok  	github.com/rkt/rkt/store/db	7.527s	coverage: 68.4% of statements
ok  	github.com/rkt/rkt/store/imagestore	7.887s	coverage: 55.6% of statements
panic: test timed out after 1m0s

goroutine 50 [running]:
panic(0xa6b920, 0xc4203c1a20)
	/usr/lib/go-1.7/src/runtime/panic.go:500 +0x1ae
testing.startAlarm.func1()
	/usr/lib/go-1.7/src/testing/testing.go:918 +0x14e
created by time.goFunc
	/usr/lib/go-1.7/src/time/sleep.go:154 +0x78

goroutine 1 [chan receive]:
testing.(*T).Run(0xc420093380, 0xb08e67, 0x13, 0xb73568, 0x4ccba3)
	/usr/lib/go-1.7/src/testing/testing.go:647 +0x56e
testing.RunTests.func1(0xc420093380)
	/usr/lib/go-1.7/src/testing/testing.go:793 +0xba
testing.tRunner(0xc420093380, 0xc42004bd20)
	/usr/lib/go-1.7/src/testing/testing.go:610 +0xca
testing.RunTests(0xb739b8, 0xf63b20, 0x3, 0x3, 0x0)
	/usr/lib/go-1.7/src/testing/testing.go:799 +0x4bb
testing.(*M).Run(0xc42004bef0, 0x30)
	/usr/lib/go-1.7/src/testing/testing.go:743 +0x130
main.main()
	github.com/rkt/rkt/store/treestore/_test/_testmain.go:104 +0x2f9

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
	/usr/lib/go-1.7/src/runtime/asm_amd64.s:2086 +0x1

goroutine 21 [syscall]:
syscall.Syscall6(0xf7, 0x1, 0x1e9f, 0xc4203db400, 0x1000004, 0x0, 0x0, 0xc4200e9668, 0x46a320, 0xc4200e9660)
	/usr/lib/go-1.7/src/syscall/asm_linux_amd64.s:44 +0x5
os.(*Process).blockUntilWaitable(0xc420105380, 0x0, 0x0, 0x5)
	/usr/lib/go-1.7/src/os/wait_waitid.go:28 +0x104
os.(*Process).wait(0xc420105380, 0xc420096960, 0xc420105380, 0xc420302680)
	/usr/lib/go-1.7/src/os/exec_unix.go:22 +0xf9
os.(*Process).Wait(0xc420105380, 0xc420096918, 0xc4200e97d0, 0xc4200968f0)
	/usr/lib/go-1.7/src/os/doc.go:49 +0x39
os/exec.(*Cmd).Wait(0xc420096840, 0x0, 0x0)
	/usr/lib/go-1.7/src/os/exec/exec.go:434 +0xf6
os/exec.(*Cmd).Run(0xc420096840, 0x70, 0xc4200e98e0)
	/usr/lib/go-1.7/src/os/exec/exec.go:279 +0x87
os/exec.(*Cmd).CombinedOutput(0xc420096840, 0xb73500, 0xc4201a29c0, 0xc42006d770, 0xc4203ee420, 0xc420096840)
	/usr/lib/go-1.7/src/os/exec/exec.go:494 +0x2b8
github.com/rkt/rkt/pkg/tar.ExtractTar(0x7fcd05425de0, 0xc42033a1c0, 0xc4202a5f20, 0x2f, 0xc42033a100, 0xc4200e9c10, 0xc4203ee420, 0x0, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/tar/chroot.go:123 +0x500
github.com/rkt/rkt/pkg/aci.renderImage(0xc420354000, 0x1, 0x1, 0xc4202a5f20, 0x2f, 0x7fcd053d9028, 0xc42006ce10, 0xc4200e9c10, 0x1, 0x0)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/aci/render.go:72 +0x17c
github.com/rkt/rkt/pkg/aci.RenderACIWithImageID(0xc4200a7830, 0x6, 0xc4200a7837, 0x40, 0xc4202a5f20, 0x2f, 0xf743c0, 0xc42006ce10, 0xc4200e9c10, 0xc42001550c, ...)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/aci/render.go:36 +0x17f
github.com/rkt/rkt/store/treestore.(*Store).render(0xc420254fc0, 0xb0655c, 0xd, 0xc4200a7830, 0x47, 0x0, 0x0, 0x0, 0x0)
	github.com/rkt/rkt/store/treestore/_test/_obj_test/tree.go:258 +0x7dd
github.com/rkt/rkt/store/treestore.TestTreeStoreRender(0xc420093440)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/store/treestore/tree_test.go:123 +0x1cd
testing.tRunner(0xc420093440, 0xb73568)
	/usr/lib/go-1.7/src/testing/testing.go:610 +0xca
created by testing.(*T).Run
	/usr/lib/go-1.7/src/testing/testing.go:646 +0x530

goroutine 7 [chan send]:
github.com/rkt/rkt/pkg/tar.ExtractTar.func1(0xc4201a29c0, 0xc42006d770, 0xc4203ee420)
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/tar/chroot.go:120 +0x8b
created by github.com/rkt/rkt/pkg/tar.ExtractTar
	/opt/build-rkt/gopath/src/github.com/rkt/rkt/pkg/tar/chroot.go:121 +0x4ef

goroutine 33 [syscall]:
syscall.Syscall(0x0, 0x9, 0xc4200ec200, 0x200, 0xa262d2, 0x44bcc7, 0xa23b40)
	/usr/lib/go-1.7/src/syscall/asm_linux_amd64.s:18 +0x5
syscall.read(0x9, 0xc4200ec200, 0x200, 0x200, 0xc420462d30, 0x10019000041d180, 0x0)
	/usr/lib/go-1.7/src/syscall/zsyscall_linux_amd64.go:783 +0x63
syscall.Read(0x9, 0xc4200ec200, 0x200, 0x200, 0x30, 0xc4203ee120, 0xc420462d08)
	/usr/lib/go-1.7/src/syscall/syscall_unix.go:161 +0x5b
os.(*File).read(0xc42007abd0, 0xc4200ec200, 0x200, 0x200, 0x0, 0xc4203ee0f0, 0xc420462d48)
	/usr/lib/go-1.7/src/os/file_unix.go:228 +0x83
os.(*File).Read(0xc42007abd0, 0xc4200ec200, 0x200, 0x200, 0x0, 0x0, 0x1)
	/usr/lib/go-1.7/src/os/file.go:101 +0x70
bytes.(*Buffer).ReadFrom(0xc42010f110, 0xf6e560, 0xc42007abd0, 0xc420462e68, 0x1, 0x0)
	/usr/lib/go-1.7/src/bytes/buffer.go:176 +0x1b6
io.copyBuffer(0xf6d560, 0xc42010f110, 0xf6e560, 0xc42007abd0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/usr/lib/go-1.7/src/io/io.go:384 +0x3c2
io.Copy(0xf6d560, 0xc42010f110, 0xf6e560, 0xc42007abd0, 0x0, 0x0, 0x0)
	/usr/lib/go-1.7/src/io/io.go:360 +0x7f
os/exec.(*Cmd).writerDescriptor.func1(0x472d31, 0x0)
	/usr/lib/go-1.7/src/os/exec/exec.go:253 +0x69
os/exec.(*Cmd).Start.func1(0xc420096840, 0xc42000cca0)
	/usr/lib/go-1.7/src/os/exec/exec.go:370 +0x39
created by os/exec.(*Cmd).Start
	/usr/lib/go-1.7/src/os/exec/exec.go:371 +0x87f
FAIL	github.com/rkt/rkt/store/treestore	60.034s
tests/tests.mk:10: recipe for target '/opt/build-rkt/stamps/__tests_tests_mk_short_tests.stamp' failed
make: *** [/opt/build-rkt/stamps/__tests_tests_mk_short_tests.stamp] Error 1
#

Environment as follows:
rkt Version: 1.26.0
appc Version: 0.8.10
Go Version: go1.7.4
Go OS/Arch: linux/amd64
Features: -TPM +SDJOURNAL
--
Linux 4.8.6-300.fc25.x86_64 x86_64
--
NAME=Fedora
VERSION="25 (Workstation Edition)"
ID=fedora
VERSION_ID=25
PRETTY_NAME="Fedora 25 (Workstation Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:25"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=25
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=25
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
VARIANT="Workstation Edition"
VARIANT_ID=workstation
--
systemd 231
+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN

The discriminant here seems to be running the unit test inside rkt itself. I have no issues running it on my dev environment, but I now reproduce it as well inside the rkt-builder image.
I initially tried to blame either the --net=host or other default isolator, but I tried disabled both and running with all insecure-options and this still panic.
Looking at GetID() I don't anything clearly wrong. We can add an additional nil-check there but I think this will just move the failure one level up. Some investigation still needed on why we are hitting this abnormal case.

It never even occurred to me to try to run the tests outside of the rkt-builder image.  If I try to do that, they fail, for the obvious reason I expected - my host system is missing various dependencies required to do this.
kiai$ make unit-check
  GO           github.com/rkt/rkt/rkt
# github.com/rkt/rkt/vendor/github.com/coreos/go-systemd/sdjournal
build-rkt-1.27.0/gopath/src/github.com/rkt/rkt/vendor/github.com/coreos/go-systemd/sdjournal/journal.go:27:33: fatal error: systemd/sd-journal.h: No such file or directory
 // #include <systemd/sd-journal.h>
                                 ^
compilation terminated.
makelib/build_go_bin.mk:57: recipe for target '/home/sjg/go/src/github.com/rkt/rkt/build-rkt-1.27.0/target/bin/rkt' failed
make: *** [/home/sjg/go/src/github.com/rkt/rkt/build-rkt-1.27.0/target/bin/rkt] Error 2

If that is how the tests are intended to be run, though, are there some guidelines somewhere on what those requirements are exactly, so I can set up my host appropriately?

Build-dependencies are documented in our devdocs. Those were noted down some time ago before rkt-builder came to light. They may need some update and in general is a worthy goal to fix this failure and make tests green in the containerized environment, but I don't want to block your other tasks.
We generally don't suggest dev-building inside a rkt container, mostly because of the chicken-egg bootstrapping problem :)

Ah yes, that's about as long a list as I expected  ;-)  Sorry I overlooked it.
Coming late to the party, now that rkt-builder is here that seems like the obvious way to go (which is why I wasn't looking for the dependency list before).  So, I'm keen to see the tests work within rkt-builder.  That will certainly make things more straightforward for occasional contributors like me.


fix installation errors on debian

Grafana has new debian repo: https://grafana.com/blog/2019/01/05/moving-to-packages.grafana.com/

Please could you also make the ID into a variable?
We host debs in our own repo (see https://www.aptly.info/) and sign all published packages with our own key - it would be great to have this configurable.
It would also mean we could fix things ourselves through vars if there was another issue like this one


Extend Ruby client to add caching and authentication

Add a couple of features to the MVP client
Caching

Cache results to disk for 12 hours, so if the same package is scanned more than once it does not check OSS Index
Before requesting results from OSS Index for a package, see if the cached results are valid
If a plug-and-play caching algorithm cannot be found, do not implement caching

Rate limits

Reads an optional username/token from a configuration file on disk which is passed via the OSS Index API to allow use of an authenticated request which has a less restrictive rate limit
Gracefully handles a rate limit by informing the user that it has be exceeded

If the user is unauthenticated, mention that authenticated users have a higher rate limit

We could create a ticket to configure the TTL to some other time period, but this as it sits is done.


etcdctl, e2e: use 0xe7cd as argument separator in cov-enabled etcdctl

Fixes #7980

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@2f84f3d). Click here to learn what that means.
The diff coverage is 100%.

@@            Coverage Diff            @@
##             master    #7990   +/-   ##
=========================================
  Coverage          ?   74.51%
=========================================
  Files             ?      340
  Lines             ?    26510
  Branches          ?        0
=========================================
  Hits              ?    19753
  Misses            ?     5302
  Partials          ?     1455

Impacted Files
Coverage Δ

etcdctl/ctlv2/ctl_cov.go
100% <100%> (ø)

etcdctl/ctlv3/ctl_cov.go
50% <100%> (ø)

Continue to review full report at Codecov.

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


[messaging] requestPermissions on Android 13

I'm running into issues with requestPermission on Android 13.
in app.gradle
targetSdkVersion 33
in manifest
  <uses-permission android:name="android.permission.POST_NOTIFICATIONS"/>
in package.json
deps
    "@nativescript/angular": "~14.2.0",
    "@nativescript/core": "~8.3.5",
    "@nativescript/firebase-core": "^2.4.4",
    "@nativescript/firebase-crashlytics": "^2.4.4",
    "@nativescript/firebase-messaging": "^2.4.4",

dev-deps
    "@nativescript/android": "8.3.1",
    "@nativescript/ios": "8.3.3",
    "@nativescript/types": "~8.3.1",

I have this code:
main.ts
import {firebase} from '@nativescript/firebase-core';
import '@nativescript/firebase-messaging';
import '@nativescript/firebase-crashlytics';

some.service.ts
constructor()
    firebase().initializeApp()
      .then(firebaseApp => {
        const messaging = firebase().messaging();
        messaging.onMessage(this.onMessage);
        messaging.onNotificationTap(this.onNotificationTap);
      })
      .catch(error => this.loggerService.error('Firebase::Failed to initialize', error));

In another method:
registerToken()
    const messaging = firebase().messaging();
    messaging.requestPermission({ios: iosPermissions}).then(authStatus => {
      const granted = authStatus === AuthorizationStatus.AUTHORIZED || authStatus === AuthorizationStatus.PROVISIONAL;
      if (granted) {
        messaging.registerDeviceForRemoteMessages()
          .then(result => {
            messaging.getToken().then(token => this.storeToken(token));
            messaging.onToken(this.onTokenCallback);
          })
          .catch(error => this.loggerService.error('register failed', error));
      }
    }).catch(error => this.loggerService.error('request permission failed', error));

Then I have "some.component.ts" using the "some.service.ts", and I get this error
request permission failed Error: Cannot assign primitive value to array of objects.
  at requestPermission (file: src/webpack:/my-app/node_modules/@nativescript/firebase-messaging-core/index.android.js:258:0)
  ...

It points to this code (index.android.js:258:0):
const perms = Array.create('java.lang.String', 1);
perms[0] = android.Manifest.permission.POST_NOTIFICATIONS; // line 258
activity.requestPermissions(perms, 1001);

This is working fine in earlier Android versions. (also without the app.gradle and manifest changes).
Any tips on how to solve this?
I checked two other cases #125 and #144, but they seemed to have other issues.

HI,
Did you tried to delayed the permission request with settimeout() maybe you request permission too early !?

Thanks for the tip, @kefahB, but even adding a 5 second delay did not make any difference.
It seems like the issue is the type of android.Manifest.permission.POST_NOTIFICATIONS. Maybe some of my dependencies or configurations are incorrect?

Did you installed SDK 33 ? if not begin with this first and then if it doesn't work try to set compileSdkVersion 33 at app.gradle

I had already installed SDK 33, but compileSdk 33 jn app.gradle was the key. It works now, thanks!


No token to add to options.ini

Please make sure these boxes are checked (put an 'x' inside them) before creating the issue.

[x ] I am using Python 3.5 or higher (run python --version on the command line)
[x ] I have followed the official guides to install the bot for my system
[ x] I have updated my dependencies to the latest version using the appropriate update_dependencies script
[ x] I am running version 1.9.6_3 of MusicBot

Description of issue
Discord does not use bot tokens anymore. How do I get the bot to work without it? The Client ID and secret does not work as the token
Steps to reproduce

Create Discord bot and see

Log file
Please attach your MusicBot log file (located at logs/musicbot.log) to this issue. You can do so by dragging and dropping the file here.

You need to make a Bot App User on that page.


Restart to Update has a huge delay

Issue Type: Bug
I noticed this during the Insiders phase of this version but always forgot to report it, but ever since the start of the last cycle, "Restart to update" takes ages on macOS. It happened that I was done working and hit the button and then completely forgot about it until an hour later VS Code opened up again.
 Seems related to Squirrel.

I noticed it with Figma as well, I think they are using Squirrel, too.

I started getting this after updating to the macOS Big Sur beta. Let me know if you want me to run any profiling or anything.

https://github.com/Squirrel/Squirrel.Mac/commit/a3a5b3f03b824441c014893b18f99a103b2603e9 might be worth a try

Can you check if this is an issue with exploration builds based on Electron 11 https://az764295.vo.msecnd.net/exploration/1441f82102c7fe5945c5135c2c518c5776ac2c62/VSCode-darwin.zip ?

@deepak1556 do exploration builds get auto updates?

yup they do, we use exploration builds to test newer runtimes before promoting them to insiders and then stable. Electron 11 update will be pushed to insiders sometime early next week https://github.com/microsoft/vscode/pull/110759, so you can also wait and test then.

I'll install exploration and report back with my findings, thank you!

@Stanzilla I checked today that, even 1.52.0-insider (f4187f2) is still base on Electron 9.3.5 :(

oh maybe it was reverted?

@Stanzilla Let's hope that #111931 will finally get merged 🚀


Issues with last played position sync between Serenity (using MX Player) and Plex

Hi,
It's been a while since I last used Serenity, but I noticed that the sync of the last play position is not working perfectly well.
It kind of works half way. When I launch from Serenity, it will play from the last played position 12:03 known to Plex. I then pause MX Player at 14:32 and come back to Serenity.
I then play the same file on Plex for Android, it does play from 14:32. GREAT!!
I then pause Plex for Android at 18:48. I then come back to Serenity and press "Play", I expect it to resume from 18:48 but MX Player actually starts the playback at 14:32 for some reason.
If I then launch the video in Plex Web and not Serenity, it picks up from 18:48 and not 14:32 like Serenity. So Plex seems to be aware of the 18:48 position.
Can you reproduce the issue?
I run the latest version of everything (PMS, Serenity, Plex for Android).

External players no longer supported, in favor of internal exoplayer.


Feedback for “Try Lama Cleaner Online”

Hello, I have paid for the windows installer but I have not received the download link or any other way to install it and I have paid 2 times, I have attached the attachment, please help!
001.pdf

Hello, I have sent an email to your 163 mailbox, please check it.


Default values for optional arguments

Optional arguments currently don't work with default values when the argument is undefined or null. This issue has also been observed by @artemgurzhii.
// component.js
@argument(optional('string'))
foo = 'defaultValue'

{{! parent-template.hbs}}
<Component />

{{! component-template.hbs}}
{{log foo}} {{! => undefined}}

Also, setting the value of the optional argument in the component during any point of the component lifecycle does not mutate the value:
// component.js
didInsertElement () {
  super.didInsertElement(...arguments)
  this.set('foo', 'mutatedValue')
}

{{! component-template.hbs}}
{{log foo}} {{! => undefined (still)}}

This is also true when argument values are supplied to the component:
{{! parent-template.hbs}}
<Component @foo="providedValue" />

// component.js
didInsertElement () {
  super.didInsertElement(...arguments)
  this.set('foo', 'mutatedValue')
}

{{! component-template.hbs}}
{{log foo}} {{! => providedValue}}

If this is a bug, I assume it's a problem with the getter logic for optional arguments.

Updating the following dependencies resolves this issue:
"ember-cli-htmlbars-inline-precompile": "^2.0.0",
"ember-source": "~3.7.0"

Can you confirm that's the case for you @artemgurzhii?

@willviles updating ember-cli-htmlbars-inline-precompile still doesn't work for me

@willviles are you using the beta version? Or the latest "stable" release?


Unable to get floating ip pools

Jenkins 2.308 over docker
Openstack-cloud-plugin version tried 2.51-2.60
please note that over ver 2.51 i have managed to get the pool list but apply/save buttons are broken because of old version of the plugin.
The error causing the provisioned instance to spin up but without floating ip

Thanks for the report!
What exact version of the plugin produced this specific stacktrace? Also, what are your networks and routers details? I speculate you might be running into this as some of your routers are not up, or connected to an external gateway. If confirmed this is the case, this will be reflected in the plugin.

@olivergondza,
It happened at ver 2.60
there is no problem with the network - also, ver 2.51 did managed to view the float ip pools.

@ssibahi, between 2.51 and 2.52 the plugin have switched from deprecated nova networking to neutron networking. For some reason, new code does not identify your pools correctly. However, you will have to provide the details of what your network and router details are to get this fixed.
Please attach result of this diagnosing script:
Jenkins.instance.clouds.each {
  if (it instanceof jenkins.plugins.openstack.compute.JCloudsCloud) {
    client = it.openstack.@clientProvider.get()
    println "Routers: " + client.networking().router().list()
    println "Networks: " + client.networking().network().list()
  }
}

Confirmed by other user, that this happens when there are routers without external_gateway_info. So in https://github.com/jenkinsci/openstack-cloud-plugin/blob/parent-2.60/plugin/src/main/java/jenkins/plugins/openstack/compute/internal/Openstack.java#L332, r.getExternalGatewayInfo() is null.

Released as 2.61


Update json and libv8

So it works with ruby 2.3 on macOS Sierra

ping
can we merge this, @cppforlife?

I've started watching this repo so I can know of such useful pull requests in the future...

Let's just merge them in time, so people don't have to look at PRs for things already potentially done ;)

Pfft... "don't have to look at"... "don't have to work at". I wasted about half an hour trying to get this setup. I agree.


Consider publishing a new version to crates.io

Hi, thanks for this awesome crate!
We started using askalono in onefetch and realized in this issue that with the latest changes in askalono we can detect correctly an ISC license, but with the version published in crates.io (0.3.0) it's not working properly.
It seems that we can't publish on crates.io if we rely on unpublished versions, so we were wondering if there would be a new version released anytime soon.
Thanks again!

Yeeeeeeeppp, you caught me. I've been on some mental block of "gotta make a 1.0 release" and "it's gotta be perfect" but it's better to release rapidly than not at all.
I believe there's a couple small backwards-incompatible API changes, so I think what I'll do is cut a 0.4.0, with all changes up to now and get that out the door. I've set some time aside for myself to do that tomorrow morning, but might try to do that today too.
Thanks for the prod -- really, I've needed to just do this. :)

All set! 0.4.0 is on GitHub as well as crates.io + cli.

Thanks!!


Forcefully scan wifi device

Forcefully registers the Android BroadcastReceived for scan the wifi first and then refresh the list in response to ensure any new/old devices being updated in the list.

Thanks @devstepbcn


feat(8695xu9r9): related handled by morph

Ticket
CU-8695xu9r9
Summary
Navigation item related item handled by morph
Test Plan

run migration
start an app
no functional changes should be present

Task linked: CU-8695xu9r9 Migrate string relation to string + poly


Input wrapper methods

This adds simple wrappers for input methods, all just so that we don't have to remember the chrome api method names and create the params objects.

please, write example for use

How to emulate input in a field?
To fill an input selector?
tab.evaluate('document.querySelector("input.signup").value=<EMAIL_ADDRESS>')


[5.2] New "preview" mail driver

This PR introduces a new mail driver "Preview", if selected it'll generate a HTML file for each email sent and put it inside a directory specified in the configuration files.
To setup the mail driver a configuration should exist inside config/mail.php:
'preview' => storage_path('framework/emails'),

The generated files will have a format:
someone_at_somedomaincom_message_subject.html

At the top of every generated file a html comment will be placed:
<EMAIL_ADDRESS><EMAIL_ADDRESS>subject:Message Subject-->

The scenario is that the developer will open up the .html file in a web browser and see the content of the email as well as the sender, receiver, and subject.

Note 1: If the specified preview directory doesn't exist, it'll be created along with a .gitignore file.
Note 2: Generated previews older than 1 minute will be deleted while generating new ones.
Note 3: I'm not sure if introducing a new directory inside the storage folder would be considered breaking or not so this PR is a suggestion of a new driver in 5.2 and will be looking for feedback if there are changes to be made.

Would rather people use something like Mailtrap.io for this.

The idea was to prevent hitting a network activity to check the email output, something like when you're working on regular views and you check the output for tweaks.
Sometimes the internet connection is not that good, so I usually switch to the "log" driver but it doesn't help with visualising the final HTML output.
I think this can be introduced as a package if not a core driver.

@themsaid Make it into a package then, the idea is good.


wip: cody ignore integration test

add integration test
Test plan

wip

moved to https://github.com/sourcegraph/cody/pull/2963


Multiple "pip install" commands in a single Jupyter cell occassionally failed when executing the second and subsequent "pip install" commands

Applies To

[x] Notebooks (.ipynb files)
[x] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Occasionally when multiple "pip install" commands were put into a single Jupyter notebook cell, ONLY the first "pip install" command can be successfully executed.
Subsequent "pip install" commands will failed to execute with error messages.
VS Code Version
1.95.3
Jupyter Extension Version
v2040.10.0
Jupyter logs

Coding Language and Runtime Version
Python v3.13.0
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Closing as this isn't something thats controlled by the Jupyter extsnion.
This is something thats handled by the Python kernel itself.
I.e. its an issue with IPyKernel package that handles these shell comments.


Fallback proxy doesn't work on Node v17+

Environment Versions

OS Type: Windows 11
Node version: 16.14.2 & 17.9.0 & 18.0.0 & 18.2.0
http-server version: 14.1.0

Steps to reproduce

http-server --proxy http://localhost:8080? doesn't redirect deep paths to the root.
I use NVM. When I switch to node.js v16.14.2 everything works well. But not on v17.9.0, v18.0.0 and v18.2.0.

Actual result
[2022-05-22T22:50:53.564Z]  "GET /en/org" Error (404): "connect ECONNREFUSED ::1:8080"
[2022-05-22T22:50:53.564Z]  "GET /en/org" Error (404): "Not found"
[2022-05-22T22:50:53.566Z]  "GET /en/org" Error (404): "Not found"

Having a similar problem, but even trying node v16.14.2 doesnt solve it for me.
React SPA, home page and routes work fine, but browser refresh or deep linking fails.
Proxy functionality seems not to intercept, returning 404 instead.
http-server 14.1.1 (latest)
node 18.12.1 (upgraded to latest)
Ubuntu Server Linux 20.04.5, all packages latest
(Using TLS because browser requires it for Brotli support, but happens in http too.)
$ node_modules/.bin/http-server -S -C ~/keys/localhost.crt -K ~/keys/localhost.key ./dist -p 3000 -b --proxy https://localhost:3000?
Starting up http-server, serving ./dist through https

http-server version: 14.1.1

http-server settings:
CORS: disabled
Cache: 3600 seconds
Connection Timeout: 120 seconds
Directory Listings: visible
AutoIndex: visible
Serve GZIP Files: false
Serve Brotli Files: true
Default File Extension: none

Available on:
  https://<IP_ADDRESS>:3000
  https://<IP_ADDRESS>:3000
Unhandled requests will be served from: https://localhost:3000?
 Tried sirv-cli, but it did not work for me (does not play well when starting multiple web servers via node-foreman). Using browser-sync as workaround.

This set of options finally worked for me while using Node 18:
http-server ./build -a localhost -P http://localhost:3002? -p 3002

Available on:
  http://localhost:3002
Unhandled requests will be served from: http://localhost:3002?

I am using Node v21 and this works fine for me:
http-server -o -p 8080 -P http://<IP_ADDRESS>:8080? ./dist
But this doesn't:
http-server -o -a localhost -p 8080 -P https://<IP_ADDRESS>:8080/index.html? -c-1 -S -C ./certificate/cert.pem -K ./certificate/key.pem ./dist
It seems that there is an issue with the proxy when using https


Dolphin SMS alerts are not implemented？

Discussed in https://github.com/apache/dolphinscheduler/discussions/6376

Originally posted by Dev-Mao September 27, 2021
Dolphin SMS alerts are not implemented in 1.3.7？
Only the email plugin is seen

Discussed in #6376
Originally posted by Dev-Mao September 27, 2021 Dolphin SMS alerts are not implemented in 1.3.7？
Only the email plugin is seen

We won't implement SMS alarm, because there is no free SMS interface，I think you can implement it by yourself


LIF neuron implementation with CPU backend

Implementation of LIF neuron model with no kernel and no external input (I_e=0).
The input current to each neuron is therefore just the sum of all the weights of incoming spikes
Binning policy and sampling are ignored!
We integrate in jumps dt = min(t_final - t, t_event - t), since we know the exact solution of the differential equal describing the membrane potential.
We use std::queue inside lif_cell_group.hpp for events waiting to be processed in advance, because we don't require the incoming events to be sorted. Instead, as soon as advance is invoked, it redistributed the events into event_queue of each cell. Since event_queue is a priority_queue, it will sort the events on the fly. This is done for efficiency reasons, because it is faster to have many small priority queues (one for each cell), than to have one large priority queue of all the events inside the cell group.

The requested changes should be implemented now!


dash_background_color inconsistency with Tangram

I have noticed that there is still problem with color transparency in Tangram ES. In Tangram, it was discussed in issue #741 and it is fixed now in v0.20.1.
In our use case: the first color track_background_color is set as transparent. The second color track_color is not transparent, this color is used in style dashed_grade5 as dash_background_color.
Our style with parameters below works in Tangram, but in Tangram ES our style with same parameters looks different: one can see two-colored dashed lines.
I am attaching a style:

global:
    ...
    track_background_color: [1.0, 1.0, 1.0, 0.3]
    track_color: [0.6, 0.4, 0.0]
    ...

styles:
    ...
    dashed_grade5:
        base: lines
        blend: translucent
        dash: [1.5, 2.5]
        dash_background_color: global.track_color
        material:
            diffuse: 1.0
            ambient: 1.0
    ...

layers:
    ...
    roads:
        ...
        grade5:
            filter: { tracktype: grade5 }
            draw:
                lines:
                    style: dashed_grade5
                    color: global.track_background_color
                    width: [ [13, 1px], [16, 3px]]
                    visible: true
                    outline:
                        color: global.track_background_color
                        dash_background_color: global.track_background_color
                        width: 5px

And here is screenshot of this style in Tangram ES:

And here is screenshot of this style in Tangram:

I suspect this is a result of https://github.com/tangrams/tangram-es/issues/2023. Tangram ES doesn't yet support specifying the dash and dash_background parameters in draw rules (only in styles).

Thank you. I have moved it into style and now it is working. Do you want me to close this issue, or should I left it open as a reminder for #2023?

Glad it's working! Matching the behavior of Tangram JS here is still our goal, but since this is already tracked in #2023 let's close this issue.


[BUG] ALPHA.5 - REI not compatible

With Alpha.5, If I try selecting REI search bar and inputting anything, the game immediately crashes. Crash Log and Latest.log do not reflect that its INDREV causing this, however, by disabling mods one by one, it was determined indrev was the cause.
Crash log( ignore "most likely caused mod" it picks a random mod every time this crash occurred): https://pastebin.com/BN2pRt8M
Latest log: https://pastebin.com/QVCtznhe

This doesn't seem to be related to IR at all so I'll close it for now


Add some tests for Netflow decoding

The tests are a bit more expansive than the existing tests for sFlow
or NFv5 as we check the whole structure. I am also testing the
String() function as it is easier to read. It is a bit redundant, but
checking only for the wire format makes it difficult to compare with
Wireshark. Only testing for the textual representation is not totally
good as it is not what is used by users of the decode function.

Thank you!


Fixes #179 missing references and libraries that break the solution build.

If you download the solution as is, and try to build it, there are missing references. I've included two nuget packages to solve this problem.
OTOH, the project requires a series of assemblies from VS2013 SDK, which I've also included in the repository for convenience.

Thanks for contributing, great work!


Automated cherry pick of #10340: etcd: fix "fatal error: concurrent map writes"

Cherry pick of #10340 on release/3.7.
#10340: etcd: fix "fatal error: concurrent map writes"

Codecov Report

Merging #10341 (b424a8f) into release/3.7 (0ff3997) will increase coverage by 1.87%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.7   #10341       +/-   ##
================================================
+ Coverage         5.98%    7.86%    +1.87%
================================================
  Files              848      110      -738
  Lines           131795    13368   -118427
================================================
- Hits              7887     1051     -6836
+ Misses          123206    12197   -111009
+ Partials           702      120      -582

Flag
Coverage Δ

aFlag
7.86% <0.00%> (+1.87%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/auth_totp.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/idp.go
1.84% <0.00%> (ø)

pkg/apigateway/handler/misc.go
0.00% <0.00%> (ø)

pkg/apigateway/handler/resource.go
0.00% <0.00%> (ø)

pkg/util/imagetools/imagetools.go
40.50% <0.00%> (-2.74%)
:arrow_down:

pkg/monitor/alerting/eval_context.go
34.82% <0.00%> (-2.18%)
:arrow_down:

pkg/hostman/diskutils/nbd/lvmutils.go
4.70% <0.00%> (-0.24%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.78% <0.00%> (-0.09%)
:arrow_down:

pkg/monitor/alerting/engine.go
0.99% <0.00%> (-0.04%)
:arrow_down:

... and 675 more

Continue to review full report at Codecov.

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


Add lint.preview

Summary
This PR adds a new lint.preview option similar to format.preview that controls whether preview mode is enabled for the linter.
Closes https://github.com/astral-sh/ruff/issues/7649
Test Plan
I wrapped the into_settings of the formatter and linter in dbg expressions and verified that:

lint.preview = true -> Preview mode is enabled for the linter only
format.preview = true -> Preview mode is enabled for the formatter only
preview = true -> Preview mode is enabled for both the linter and the formatter.
--preview overrides the preview, lint.preview, and format.preview option
preview = true and lint.preview = false enables preview for the formatter only (same test for the linter)

Current dependencies on/for this PR:

main

PR #8000

PR #8002   👈

This comment was auto-generated by Graphite.

Is it intentional that we have tool.ruff.format.preview but no ruff format --preview. Otherwise i would implement the latter because i need it for the ecosystem check with preview style.

Is it intentional that we have tool.ruff.format.preview but no ruff format --preview? Otherwise i would implement the latter because i need it for the ecosystem check with preview style.

No. I can add it as part of this or another PR or you can add it. Let me know what you prefer

Is it intentional that we have tool.ruff.format.preview but no ruff format --preview? Otherwise i would implement the latter because i need it for the ecosystem check with preview style.

No. I can add it as part of this or another PR or you can add it. Let me know what you prefer

Actually, the CLI options are already supported. It's just that they were hidden until now (because we didn't support any preview styles)

Actually, the CLI options are already supported. It's just that they were hidden until now (because we didn't support any preview styles)

:facepalm: should have checked, thanks

Can you update the docs in preview.md or would you prefer that I did?

Can you update the docs in preview.md or would you prefer that I did?

I created another PR for this


Buffer is not defined: ReferenceError: Buffer is not defined

Buffer is not defined: ReferenceError: Buffer is not defined
    at o.getMarkdownDocument

This is likely caused by the webpack adoption... I believe we now need to polyfill things explicitly. Adding @aeschli  for more help and fyi. Also for this specific case the global TextEncoder/Decoder could be used. That's available as a global in all contexts that we support

I wonder if it's worth creating separate tsconfigs for web that excludes the node types? Will take a look to see how complex this would be to add

134c34535162b621d4f010386ed8bd4b3cba925e try adding browser specific tsconfig. These errors won't show in the editor but should help catch references to Buffer or process
Let me know if you think this is worth adding for other extensions as well. I'll look into adopting it for the built-in extensions I maintain

@mjbvz can you provide some verification steps for this issue?

To verify:

yarn web
Open md file
Trigger a workspace symbol search


[test][base-ui] Fix import paths in useTab tests

I forgot to update to '@mui-internal/test-utils' in https://github.com/mui/material-ui/pull/39037 😓
Fixes CI currently failing on master: https://app.circleci.com/pipelines/github/mui/material-ui/110305/workflows/1def82a9-c4b9-4ac0-aac3-f179632f70ae/jobs/591293

[x] I have followed (at least) the PR section of the contributing guide.

Great. it is nice.


slow ( unresponsive ? ) logout / shutdown after running a succesful xfce session

Please paste the output of the following command here: sudo edit-chroot -all

name: xenial
encrypted: no
Entering /media/removable/USB Drive/chroots/xenial...
crouton: version 1-20170901092920~master:0216f9d1
release: xenial
architecture: amd64
xmethod: xiwi
targets: xiwi,audio,keyboard,touch,core,xfce-desktop,extension
host: version 9592.96.0 (Official Build) stable-channel caroline
kernel: Linux localhost 3.18.0-14875-g438cb8ab27c6 #1 SMP PREEMPT Sat Sep 16 10:00:51 PDT 2017 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Unmounting /media/removable/USB Drive/chroots/xenial...

Please describe your issue:
I had crouton installed on a separate external USB stick as I don't really want to 'clutter' my current ChromeOS. Installation took a while, but it was succesful. This was the command that I used to install:
sudo sh ~/Downloads/crouton -r xenial -t audio,keyboard,touch,core,xfce-desktop,xiwi,extension -p /media/removable/sd-card -u
and to run it, simply using
sudo sh /media/removable/sd-card/bin/startxfce4
I've got few connection error, but then the screen switches full screen bringing up the XFCE interface up. it's great. Everything seems fine with running the Linux part of it. Unfortunately adding "-xiwi" somehow doesn't, but "-xiwi-tab" is working although resolution will be very very small
Now the real issue is that after I log-out/shutdown the XFCE session and when I want to lock/log-out/shutdown my ChromeOS, it tooks either very slow ( or just unresponsive ) to a point I had to pressed the "off" button just to shut it down.
I think the normal behaviour when you want to lock/log-out is that ChromeOS will get you back to login screen, however in my case the screen will just go black ( okay, i thought it's a between process that will eventually got you to login screen ), but it just stay there .... for a long time ... and pressing any button doesn't seem to response anything
Has anyone encountered similar issue ? It did give me a thought that crouton brick my ChromeOS, so I'm quite reluctant to use it at the moment
I had crouton experience before with my previous Chromebook, it was an Acer Chromebook 15 and it ran great
This is my 2nd Chromebook and I thought I go higher with Samsung Chromebook Pro
If known, describe the steps to reproduce the issue:

@aleifuu,
It may just be slow or having a hard time unmounting everything on the external media.
You can switch back to Chrome OS while the chroot is running and press ctrl+c in the shell session that launched your desktop, that should shutdown your chroot and unmount everything also.
You can also use unmount-chroot to see what's still mounted and even terminate them if need be.
Here's the usage -
chronos@localhost ~ $ unmount-chroot
unmount-chroot [options] name [...]

Unmounts one or more chroots, optionally killing any processes still running
inside them.

By default, it will run in interactive mode where it will ask to kill any
remaining processes if unable to unmount the chroot within 5 seconds.

Options:
    -a          Unmount all chroots in the CHROOTS directory.
    -c CHROOTS  Directory the chroots are in. Default: /mnt/stateful_partition/crouton/chroots
    -f          Forces a chroot to unmount, potentially breaking or killing
                other instances of the same chroot.
    -k KILL     Send the processes SIGKILL instead of SIGTERM.
    -p          Print to STDOUT the processes stopping a chroot from unmounting.
    -t TRIES    Number of seconds to try before signalling the processes.
                Use -t inf to be exceedingly patient. Default: 5
    -x          Keep the root directory of the chroot mounted.
    -y          Signal any remaining processes without confirmation.
                Automatically escalates from SIGTERM to SIGKILL.

Hope this helps,
-DennisL

Alright. Cool
I could try that later on. You may be right with the unmounting part. Since using dongle for adapting usb-c interface for normal usb-stick, I think it does slow the system a bit ( or maybe I just got a 'bad' dongle ) sigh

Okay, I just tried again. Unfortunately, it's the same result
So the process was logging out from xfce4 ( i was using -X xiwi-tab btw,
and crouton-integration is working ), going back to shell wait untill the
process unmounts the chroots itself, did the 'sudo unmount-chroot' command
... It just give me one line response like 'Unmounting
/media/removable/USB\ Drive\ 1/chroots/xenial'
Then, just to make sure I unplug the usb stick and  dongle before pressing
the sign out on the ChromeOS
Still faded out to blank screeen, instead of login screen ...
Maybe I should close out the chronos shell tab too maybe ... Do you think ?
On Oct 1, 2017 1:03 AM, "DennisL"<EMAIL_ADDRESS>wrote:

@aleifuu https://github.com/aleifuu,
It may just be slow or having a hard time unmounting everything on the
external media.
You can switch back to Chrome OS while the chroot is running and press
ctrl+c in the shell session that launched your desktop, that should
shutdown your chroot and unmount everything also.
You can also use unmount-chroot to see what's still mounted and even
terminate them if need be.
Here's the usage -
chronos@localhost ~ $ unmount-chroot
unmount-chroot [options] name [...]
Unmounts one or more chroots, optionally killing any processes still running
inside them.
By default, it will run in interactive mode where it will ask to kill any
remaining processes if unable to unmount the chroot within 5 seconds.
Options:
-a          Unmount all chroots in the CHROOTS directory.
-c CHROOTS  Directory the chroots are in. Default: /mnt/stateful_partition/crouton/chroots
-f          Forces a chroot to unmount, potentially breaking or killing
other instances of the same chroot.
-k KILL     Send the processes SIGKILL instead of SIGTERM.
-p          Print to STDOUT the processes stopping a chroot from unmounting.
-t TRIES    Number of seconds to try before signalling the processes.
Use -t inf to be exceedingly patient. Default: 5
-x          Keep the root directory of the chroot mounted.
-y          Signal any remaining processes without confirmation.
Automatically escalates from SIGTERM to SIGKILL.
Hope this helps,
-DennisL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3433#issuecomment-333325572,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU98eKe6DQFidiIjktea-HarL1JGZ-Ujks5snoJ7gaJpZM4Ppila
.

@aleifuu,

Maybe I should close out the chronos shell tab too maybe ... Do you think ?
…

I don't know but it may help.
Sorry but I haven't run many chroots on external media of late.
Hope this helps,
-DennisL

Do you think installing crouton not on external media could solve the
isssue that I am having ?
I'm just super cautious when it comes to shutting down electronic devices
by force you know. Lol
I meant, any log/output that I could post that might help too ?
On Oct 1, 2017 6:19 AM, "DennisL"<EMAIL_ADDRESS>wrote:

@aleifuu https://github.com/aleifuu,
Maybe I should close out the chronos shell tab too maybe ... Do you think ?
…
I don't know but it may help.
Sorry but I haven't run many chroots on external media of late.
Hope this helps,
-DennisL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3433#issuecomment-333342555,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU98eBQKN5E4BOMTpQknq6q3oMVk3PzXks5snsyMgaJpZM4Ppila
.

@aleifuu,

Do you think installing crouton not on external media could solve the
isssue that I am having ?

Yes, I think it could. I think shutting down & unmounting the chroot on external media may be the problem.
You could try installing a new chroot or moving the existing one on external media to your internal drive.
Then see if it behaves any differently when shutting it down. You can always delete it from your Chromebook if need be.

Maybe I should close out the chronos shell tab too maybe ... Do you think ?

Yes, that might help. Sometimes the powerd process can interfere with logging out, it's happened to me.

Still faded out to blank screeen, instead of login screen ...

If that happens again try pressing the full screen and/or the switch window key and see if that helps.
Hope this helps,
-DennisL

Might be because it is a small memory stick
Or because you have barely any space left

Or maybe cause xiwi is more slow than without xiwi

it's a typical 16GB SanDisk stick. with crouton installed, it occupies
around 3.9GB i think. So it's still plenty of space left
My Chromebook lists still having 20GB left free
It looks like unmounting process takes a long time eating up the RAM (
maybe ) ...
On Sun, Oct 8, 2017 at 2:03 PM, Ender<EMAIL_ADDRESS>wrote:

Might be because it is a small memory stick
Or because you have barely any space left
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dnschneid/crouton/issues/3433#issuecomment-334987606,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AU98ePlt-ALUseUEl1aIw23skZIwXyuKks5sqHOlgaJpZM4Ppila
.