Adding changes for near repeat calculator

Hi Eric,
please find the code changes for near repeat calculator. Five files have been changed

IO.py
Bobs.py
Engine.py
Primitve.py
runforesttestfull.py

Kind Regards
Jay

Merged into main branch.  We might want to return to the code and add more comments.


locomotive's equipment grid item disappears when mining locomotive

Mod source
Factorio Mod Portal
Which mod are you having an issue with?

[ ] pyalienlife
[X] pyalternativeenergy
[ ] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[ ] Pypostprocessing failure
[X] Other

What is the problem?
I placed a spent nexelit battery in an advanced locomotive, hoping it would help store extra energy. It didn't seem to have any effect (even though the locomotive had diesel fuel canisters in it). That may be intended, though strange; however, when I right-clicked to mine the locomotive, the battery vanished. It wasn't in the locomotive, nor in my inventory, nor my trash slots, nor lying on the ground. It seems to have just been deleted.
Steps to reproduce

Place advanced locomotive on tracks
Open locomotive fuel menu
Put spent nexelit battery into locomotive's equipment grid
Close out of menu
Mine (pick up) the locomotive
Battery is now vanished from game.

Additional context
No response
Log file
No response

Ref: https://github.com/pyanodon/pybugreports/issues/514
Thanks for the report. Fixed.


SWARM-1782: Allow finalname of uberjar to be customized

Allow finalname to be set in maven builds.
For gradle builds it will use the old behaviour, so the hardcoded "-swarm.jar " is moved from BuildTool.java to PackageTask.java.
If no name is set, it will default to the old value (finalName + (this.hollow ? "-hollow" : "") + "-swarm.jar").

[x ] Have you followed the guidelines in our Contributing document?
[ x] Have you created a JIRA and used it in the commit message?
[x ] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ x] Have you built the project locally prior to submission with mvn clean install?

ok to test


AMBARI-25343. Storm Service Check fails during Rolling Upgrade due to…

… Nimbus leader selection (dlysnichenko)
What changes were proposed in this pull request?
The issue is kind of "known": service check can not pass until Nimbus selects leader. If Nimbus HA is enabled, we increase a retry count
How was this patch tested?
live cluster check
unit tests

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5411/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5412/
Test PASSed.


After updating to the latest version, the created space cannot be modified or saved.

Same as Issue 201, patch will be released today.

On Nov 1, 2023, at 12:38 PM, 陈述句 @.***> wrote:
https://user-images.githubusercontent.com/25047688/279739413-7bdf5124-3dae-4805-86a9-1be2017b81c9.png
—
Reply to this email directly, view it on GitHub https://github.com/Make-md/makemd/issues/203, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFHKNQ4OIYFOMUXSGWWH5LYCJ3H5AVCNFSM6AAAAAA6ZR3BY2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE3TENZRGY3DKMI.
You are receiving this because you are subscribed to this thread.

Fixed in 0.8.6


Roadmap for 2019-2020

Hi all!
In the last months we were focus on improve the codebase with tests, mostly e2e test and CI.
Now we are more confidents on the source code and it's easier to validate PRs and merge new contributions. I think is a good time to discuss about the roadmap for NodeGoat in the following months.
Right now we are close to publish release 1.4 that includes (e2e and ci). I just want to suggest some possible targets for the following releases.
Release 1.5
Main goal:

Improve source code

Pending PRs (Update/review):

[ ] change app.csp() with contentSecurityPolicy() #119
[ ] replace helmet.xframe() with helmet.frameguard(), xframe is deprecated #118
[ ] Adding secondary /api/login route for JSON user login processing #91
[ ] Upgrade dependencies #169

Targets:

[x] #156 (asg: @servatj) Forever is not in use, let's move to Nodemon as npm script
[x] #150 (asg: @UlisesGasconMigration to node 12 (support for Node 12|10|8)
[x] #151 (asg: @UlisesGascon) Add CONTRIBUTING Guide and CoC (PR #177)
[ ] #157 (asg: @flippedcoder) Migration from Swig Deprecated to ejs
[ ] #152 (asg: @lucas1004jx @UlisesGascon )Migration to es6+ (PR #185)
[ ] #153 Upgrade dependencies to secure latest versions in package.json, see: #82
[ ] #149 (asg: @servatj) migration from Grunt to npm scripts
[ ] #154 (asg: @carlosAzaustre @UlisesGascon) Harmonize the JS Style with Standard and Prettier
[ ] #155 (asg: @UlisesGascon) Let's add git hooks for linting and testing with Husky
[ ] #158 (asg: @PeterWunderlich) Migration from bcrypt-nodejs Deprecated to bcrypt
[ ] #159 Improve Cypress and travis scripts, like cy.exec validation
[ ] Migration from Mocha to Jest and add Unit tests
[ ] We need a definitive cool super-fancy logo! 💪
[ ] Let's simplify the configuration steps
[ ] Update README and relevant documentation
[ ] Let's add multi-language support for The Tutorial Guide, this will help the use of Nodegoat as a very effective workshop tool for non-english speakers
[ ] Include ZAP testing in CI workflow, See: #34 and The Guide
[ ] Migration to purpleteam suggested by @binarymist in issue #142
[ ] Add code review checklist #37
[ ] Example / Implementation for noSQL Injection #90 by @lirantal
[ ] Autogenerate documentation (Readme.md, dependencies...). Assigned to @UlisesGascon
[ ] Let's include codeclimate

Release 1.6
Main goal:

Refresh to OWASP 2019
Let's refresh the technology that we use :muscle:

Targets:

[ ] #180 Implement REST API endpoints
[ ] #181 Implement Client Side Rendered UI with React
[ ] #182 Implement Auth for REST endpoints
[ ] #183 Demonstrate API security issues. See
[ ] #184 Tutorial and hands on labs guide for securing REST endpoints

Open Questions && Discussions
Main goals/ideas suggested by @ckarande:

Upgrade to the latest OWASP Top 10 (#99)

Honestly, I didn't find certain new additions to OWASP top 10 2017 very relevant to Node.js usage (e.g, not many Node.js users deal with XML) but in the sprit of demonstrating the top 10, it could be worth explaining / incorporating the latest OWASP top 10 list. I would like to retain some of the existing vulnerabilities from the OWASP Top 10 2013 version that are not in the 2017 version (such as CSRF, Insecure Redirects, etc) . So we can make two sections on the tutorial site - OWASP Top 10 2017, and Beyond OWASP Top 10.

Provide versions that are close to real world Node.js usage

As you may know, current version of Nodegoat uses templates for rendering UI and cookie based stateful session. This architecture is good for beginners to have the least resistance to start diving into the security specific concepts. However, I would like to provide two additional versions of NodeGoat that are close to real world Node.js apps and demonstrate security vulnerabilities in the context of these architectures:

Architecture 2: Using client side rendering with React (or Vue/Angular) and stateless session management using JWT. As part of this upgrade the UI build system to use webpack / UI framework specific build CLI.
Architecture 3: various services broken down into individually deployable micro services.
Also check: #38

If we have a clear roadmap it will super easy to reclute contributors and provide them a clear path to follow :-)
I will try to setup a local Hackathon in Madrid to reclute new contributors and close some issues 👍
In order to keep all smooth and simple to review, I will suggest to work using issues per feature and link those issues to small PRs and commit using GitFlow (branches per release) so we can concentrate all the PRs per release. And then a final PR from the release branch to the master in order to upgrade package version and deploy in Heroku.
What do you think? Do you agree for the targets/items for release 1.5? I think that we need to discuss a lot for 1.6 as now it is very conceptual

A very good compilation of next tasks and release roadmap. It looks good to me.
I just created release 1.4 and we are all set to start rolling out tasks you listed for Release 1.5. I agree that items for 1.5 are well defined and we can proceed with those. As we proceed, let's create issues for each item in the list and add it to corresponding milestones.
I have added you to the list of collaborators for the project 🎉🎉. Thanks for your contributions and looking forward to work together to make NodeGoat even more valuable resource for the community.

thanks a lot @ckarande !! 🤗
Can you add me extra rights for manage issue label creation and milestone assignation? maybe projects, too?  :-)

Of course. Can you please check if you have the necessary rights now.

Oh yeah! Now it is perfect ^^

May be worth updating the checklist? purpleteam has been testing NodeGoat for several years now


Remove default variables in c headers

Fixes: https://github.com/leejet/stable-diffusion.cpp/issues/477

Hijacking this pr to also make the default slg scale to 0.

std::vector is not a thing in C as far as I'm aware 🤔

Damn you're right.

I'll change it to a C array later.


fix to overlay issue

Hi, I'm not sure what this is attempting to fix? #4 appears to be an issue in your app somewhere (i.e. we don't have that issue in any of our hosted demo/seed applications or running the component stand-alone).


Disallow query that sets the keyspace by using the query method

This is currently in the codebase:
async fn query_no_metrics(
    &self,
    query: impl Into<Query>,
    values: impl ValueList,
) -> Result<Option<Vec<result::Row>>, QueryError> {
    let query: Query = query.into();
    let query_text: &str = query.get_contents();

    // In case the user tried doing session.query("use keyspace ks") run session::use_keyspace
    if query_text.to_lowercase().starts_with("use ") {
        eprintln!("Warning: Raw USE KEYSPACE queries are experimental, please use session::use_keyspace instead");

        let mut keyspace_name: &str = &query_text["use ".len()..].trim_end_matches(';').trim();

        let case_sensitive: bool = keyspace_name.starts_with('"');

        keyspace_name = keyspace_name.trim_matches('"');

        return self
            .use_keyspace(keyspace_name, case_sensitive)
            .await
            .map(|_| None);
    }
    ...

I propose to remove the logic because:

It allocates a string for literally every query, for something that will happen only once or just a few times in a normal application (I guess?)
There is already a warning, telling us that we misuse the query method by setting a keyspace.

Sine this repo is fairly new and not even on crates.io, I propose we can change the logic like so:
    if query_text.starts_with("use ") || query_text.starts_with("USE ") {
        panic!("Don't set the keyspace by this method, but use session::use_keyspace");
    }

I think it would be better to just crash everything instead of handling wrong user input (and the fix for users is really simple).

There was some discussion about this choice in the original PR: #160
There is a use case of someone that loads many queries from a file and passes them to session.query()
We wanted to make this as painless as possible without the user having to parse USE queries themselves .
After implementing #168 doing use keyspace like this could probably be supported without the warning.
About the allocation maybe we could change it to a regex to keep case insesitivity, but for now performance is not the top priority - we will profile the code after getting all basic features done.

But wait, this code wouldn't allocate for every query, but only for queries that start with use, right? These kind of queries are not expected to be common (as opposed to, for instance, executing prepared statements), so an allocation here will not influence the overall performance.
Performance actually is one of the top priorities, but on the fast path - we want the most common operations to be fast, while for the less common ones (like use keyspace) we'd prefer user experience over raw performance - and #168 would make everything happen automagically from the user's perspective.

Ah, the current logic does allocate, but the snippet here does not reflect the actual code!
The condition is as follows:
if query_text.to_lowercase().starts_with("use ") {
    // ...
}

to_lowercase() creates a new string, so there is an allocation. We can use a regex as @cvybhu said, or use str::eq_ignore_ascii_lowercase.

Alright, that's a performance bug :) str::eq_ignore_ascii_lowercase sounds like a perfect solution.

@piodul Woops, that right. I edited the original code, so in the code snippet in my question it doesn't reflect the real code indeed. I will edit that accordingly.
I think str::eq_ignore_ascii_lowercase will indeed be sufficient, nice find! Comparing can than be done by something like this:
...
let query_text: &str = query.get_contents();
if query_text.len() > 4 && query_text[0..=3].eq_ignore_ascii_lowercase("use ") {
...
}

I guess that can already place the current code, can someone verify? I can make a PR if needed.

@piodul Woops, that right. I edited the original code, so in the code snippet in my question it doesn't reflect the real code indeed. I will edit that accordingly.
I think str::eq_ignore_ascii_lowercase will indeed be sufficient, nice find! Comparing can than be done by something like this:
...
let query_text: &str = query.get_contents();
if query_text.len() > 4 && query_text[0..=3].eq_ignore_ascii_lowercase("use ") {
...
}

I guess that can already place the current code, can someone verify? I can make a PR if needed.

Sounds good, although you might want to call as_bytes() on the input string and use the version that operates on raw bytes (thanks @piodul for pointing it out) https://doc.rust-lang.org/std/primitive.slice.html#method.eq_ignore_ascii_case , to avoid utf-8 issues, because we ultimately just want to compare first 4 bytes. Also,  query_text.len() > 4 will work because keyspace names cannot be empty, but  query_text.len() >= 4 will also suffice in this case :)

Since the PR is merged which improves the efficiency of checking if a keyspace is used, this issue can be closed


[Realm Browser Plugin] Open relevant realm file on Realm Browser

A week ago, I have created an Xcode plugin to open Realm Browser with relevant Realm File. Little did I know that you guys have created already this plugin to open Realm Browser but not with file.
Thus, by recommendation of @jpsim in the issue (https://github.com/kittinunf/RealmBrowser-Plugin/issues/1), I think it is a nice idea to extend the functionality of Realm Browser plugin itself by combining my implementation into yours. This PR is to serve this purpose, and ultimately deprecate my plugin once it is merged.
I intentionally break things into a multiple commits just for reviewer to easier review my code.
All comments are appreciated. :sunny:

Hi there Kittinun!
Awesome! Thank you so much for this! As someone who debugs Realm files in a production app, this sort of thing is incredibly useful for me!
That being said, I think I found a bit of a problem, although it might be an issue on Realm Browser's side that I could potentially take care of.
I just tried using the plugin on my own copy of Xcode, and this happened:

One of my apps uses Realm in a pretty crazy way. It has a standard default.realm file where all of the main data is kept, and then for each user-generated file in the app, it has a subsequent .realm file that stores cached information about each file. When I opened the Browser via the plugin, it looks like it was instructed to open every single .realm file in my Simulator device's directory, including all the cache files.
In any case, it might be best if I include some safeguards in Realm Browser for these kinds cases (Maybe a prompt that appears when a certain number of Realm files are opened at once)
/cc @jpsim What do you think?

@TimOliver, I wouldn't think of that edge case.
Yeah, you are very right. I way I am able to grasp the Realm file is to recursively find all of .realm file extension and open them all. It was kind of blind-fully because I don't have any info about how Realm Browser is opening the file or what file(s) the Browser is(are) actively opening.
It works well and effectively in my use case (I have 2 apps in my Simulator with 2 default Realm files in 2 folders), but it seems like it might be not the case for you. :scream:
I am very happy to add more guard on my side if there is anything I can do.

@kittinunf Fair enough. I've been told it's not a normal way to use Realm (But it still works very well!). :)
At the very least, do you know if it's possible to open up the .realm files for the app that the Simulator is currently displaying (That would mitigate it a fair amount)? If not, I might do a bit of digging to have a look, but if it's not possible then it can't be helped.
No worries! Let's see what JP says, but I get the feeling that this should be a safeguard feature of the Browser itself to prevent too many files from opening at once.

@kittinunf thanks for the PR :sparkles:! I look forward to getting this into the official Realm plugin.
@TimOliver I'd add a prompt to the browser when it's asked to open more than 5 files simultaneously (Are you sure you want to open 'X' Realm files at once?) to address this in the very short term.

I'll let @TimOliver continue to review this, but it looks fine to me @kittinunf. Thanks for your hard work!

@TimOliver thoughts?

I'll test it with my Browser changes once more to be sure!

Yep! It looks good on this end!
One final thing I might recommend is that even though I added some checks on the Browser side to ensure not too many files are opened at once, it might also be good to add the same check here in advance. That can wait until after the merge though.
In any case, I'm happy for the merge to go ahead!

Thank you so much for this PR, @kittinunf ! I hope you'll contribute to realm again in the future :smile:.

@jpsim, I am more than happy to contribute. As I am a Realm fan myself, we use Realm in our iOS and Android (for Realm-Java, it is kind of love and hate along the process, haha) so a chance to contribute back to Realm eventually benefits ourself and Realm community. :dancers:

@kittinunf :) Is there anything in particular we can do better on the Java side? It’s been a long road, but we have some exciting stuff coming up there in the immediate future including much improved Realm Objects (and of course null support, async queries/transactions and better notifications). Anything else tripping you up?

@TimOliver I can open another simple PR to take care of that. It could be as simple as an Alert Confirmation with yes/no buttons. If yes, open with that many files, and no for doing nothing. How does that sound to you? If it sounds good, I will craft it over the weekend.
@timanglade, we have been fighting with lack of null support, unable to implement common interface on RealmObject, and gson serializing/deserializing with Realm Proxy class. We tried so hard, because we like to Realm with our Android so much and don't want to give up on it just yet. Don't take me wrong though, you guys makes an awesome DB.

@kittinunf Yeah! If you can spare the time to do that, that would be a great help! Thank you so much for that! :)

@kittinunf Actually, you know what? There might be a smarter way to go about doing this.
My check for multiple files in Realm Browser is in the [NSApplication application:openFiles:] method, but in my last set of tests, it looks like the Plugin isn't passing the files to the Browser through that delegate, more that it's most likely calling 'openFile' multiple times.
Instead of doubling up on the logic for checking if multiple files are being passed, it might be better to ensure that the Realm Plugin is passing multiple Realm files to Realm Browser via the openFiles: delegate method.
Do you know anything about that? If not, then I can easily spend some time on this.

@TimOliver Ah I guess, it might be my fault because I always use NSWorkspaceLaunchNewInstance when open file. Perhaps I need to use NSWorkspaceLaunchDefault or 0, then it should help, I guess?

@kittinunf Yeah, I was looking into it as well and it looks like there's a lot of different ways to go about doing this.
Apparently [NSWorkspace openURLs:withAppBundleIdentifier:options:additionalEventParamDescriptor:launchIdentifiers:] might do the trick. Shall I have a look into that one? :)

@kittinunf Understood! We feel the same honestly. You’ll really like the new object stuff we are working on now :)

@TimOliver let's discuss on another thread. I will open up another PR to take care of this.


⚠ Bofrost.fr has degraded performance

In 5fb6a33, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1542 ms

Resolved: Bofrost.fr performance has improved in c679e36.


pop3 client port number

Why does pop3 client use a specific port "4228"?
https://github.com/azure-rtos/netxduo/blob/617d1f0bb79ed1623efdeebabb100e299ef266ce/addons/pop3/nxd_pop3_client.c#L2680

Hi @ReKawashima, thanks for bringing it up, this bug will be fixed in next release. Closing the issue now. Feel free to re-open if you have additional questions.


Bug 1951703: CSV properties annotation accepts arbitrary types

Downstream https://github.com/operator-framework/operator-registry/pull/621.
Implements OLM-2133: Allow bundle authors to provide properties of any type via their CSV's olm.properties annotation.

/test e2e-upgrade

/test e2e-upgrade

/hold
Getting some consensus on whether this should merge before or after 4.8.0 is released.

Will be included in the upstream sync.


Lazily clean up temp files from DETR partitioner.

Tested on my laptop both cases (older and younger than cutoff).

It looks like Python 3.9 TemporaryDirectory() lacks the ignore_cleanup_errors kwarg.  Should be harmless to include it.


spyder editor shows syntax error for match case statement

After the long awaited addition of the match-case statement in Python 3.10, I eagerly created a 3.10 venv and got spyder using it as the interpreter.  In general all is well, but I have noticed that the Spyder editor does seem to be confused about what is the correct syntax for 'match'.
First:, I am running on a Macbook Air M1 with:

Spyder version: 5.2.2 None
Python version: 3.9.5 64-bit ... This is from About Spyder, my python interpreter is a venv of python 3.10.2
Qt version: 5.12.10
PyQt5 version: 5.12.3
Operating System: Darwin 21.3.0

Whenever I have a match-case statement e.g.,
`
string = 'alt 2'
match string:
case 'option 1':
print('yay 1')
case 'alt 2':
print('two')
case :
print('')
`
The Spyder editor marks the line with 'match' as 'invalid syntax' and puts a red 'x' to the left of the line and a red '-' at the right margin.
Interestingly, there are actually no problems running the script above.  The output in the ipython console is correct and no errors or warnings are given.   This appears to be just a cosmetic problem, but as I do actually use those red indicators to check for typos, or other problems, I would hate to start getting used to ignoring them just because they don't know how to deal with the new syntax.  I didn't find that this has been reported anywhere, nor could I find any solutions online.  Any suggestions?  Is this a known issue?

Hey @JeepTJU, thanks for reporting. We use a third-party library called Pyflakes to display errors and warnings in our editor, so this is not something we can solve here.
Since it seems Pyflakes doesn't have support for Python 3.10 yet, please add next to your match statement a comment like this to avoid the editor display an error about it:
match ... # noqa

I don't need if you need to do the same for case as well. Sorry for the inconvenience.

thnaksss


[LB Installer] Error when installing EAN animation data on EAN files modified with YaEAN

New EAN code seems to have compatibility issues with files modified with YaEAN, this is a problem in regards to installing new data to CMN.ean
XV2 Serializer will just hang on an infinite loop
while the Installer spits this log
System.Exception: Failed at EAN install phase (CMN/CMN.ean.xml). ---> System.NullReferenceException: Object reference not set to an instance of an object.
   at Xv2CoreLib.EAN.EAN_Node.LinkEskData(ESK_Skeleton skeleton) in C:\Users\Unleashed\Documents\GitHub\XV2-Tools\Xv2CoreLib\EAN\EAN_File.cs:line 1164
   at Xv2CoreLib.EAN.EAN_Animation.LinkEskData(ESK_Skeleton skeleton) in C:\Users\Unleashed\Documents\GitHub\XV2-Tools\Xv2CoreLib\EAN\EAN_File.cs:line 574
   at Xv2CoreLib.EAN.EAN_File.LinkEskData() in C:\Users\Unleashed\Documents\GitHub\XV2-Tools\Xv2CoreLib\EAN\EAN_File.cs:line 111
   at LB_Mod_Installer.Installer.Install.GetParsedFileFromGame(String path, Xv2FileIO fileIO, Boolean onlyFromCpk, Boolean raiseEx)
   at LB_Mod_Installer.Installer.Install.GetParsedFile[T](String path, Boolean fromCpk, Boolean raiseEx)
   at LB_Mod_Installer.Installer.Install.Install_EAN(String xmlPath, String installPath, Boolean isXml)
   --- End of inner exception stack trace ---
   at LB_Mod_Installer.Installer.Install.Install_EAN(String xmlPath, String installPath, Boolean isXml)
   at LB_Mod_Installer.Installer.Install.StartInstall()
   at LB_Mod_Installer.Installer.Install.Start()

this issue is regarding this line
EskRelativeTransform = esk?.RelativeTransform;
not sure what's wrong, it's as if the null check isn't really working
i tried the traditional If statement check aswell with the same issue

That's pretty odd. I can't seem to reproduce the issue on my end either... but the ESK linking can just be disabled for installing and XMLing since it doesn't serve a purpose there. It's just there to easily get the default bone values for animation playback.
No point wasting time trying to fix it when its not needed.


No multi-users-select element

Hi, first of all I want to say thanks for this cool lib!
During work on my app I found that there is no multi-users-select element.
I'm ready to create pull request with fix.

Thanks! Multi-select elements have been added by #223 😃 They are available in jslack 2.2.0+


docs: Use img shortcode from theme

Why not do this edit in the docs repo?

I may not understand the process of pull/push between the docs repo and this repo. In this case, the "img" shortcode was moved from the docs repo to the theme repo a while ago. But it returned to the docs repo this morning after the merge.

I may not understand the process of pull/push between the docs repo and this repo.

hugoDocs is master
the only change going from hugo -> hugoDocs is edits done in this repo (which should be the edits that reflects new features, changes to code)
the above looks like a bad merge situation; I try my best, but when there's a lot of merge conflicts, I may glitch.

Just to be clear: The only motivation behind the /docs subtree construct is to provide a versioned snapshot of the documentation in the GitHub source tarballs (which is also why we vendor the theme).

I'm closing this. This will eventually be synced.


fix(peerDependencies): fix peer dependency versions

The peer dependency versions were causing npm install to fail with anything other than the exact same version specified in package.json. I suggest similar updates are made to devDependencies and dependencies in another PR.

@dsebastien Any feedback on this PR?

Sorry I didn't give feedback earlier. I agree with the change you propose, but you need to update the PR before I can merge it (it has conflicts)

Actually don't bother, I'll push the change myself, don't want to bother you updating this for two lines ;-)

No worries, thanks for pulling it in.

I've released v0.5.3 with this; also took the opportunity to update the dependencies :)


Readme.md Formatting mismatch

The text description has large text for paragraph.
source: 79ce486

That text should not be displayed as headings.


Bind the loop variable

Fix for https://code.djangoproject.com/ticket/34023#comment:3

@mpasternak Thanks :+1: Please update also user_deleted_form() calls.

@felixxm Sure!


Inference on the non -default GPU，such as "cuda:5"

Thank you very much for your amazing work, but I encountered some problems when doing inference with the existing model and parameters:

When I specify the number of the GPU, I always find that the program will run on the default GPU (cuda:0) Simultaneously load an identical model.

I often encounter program jams when inferencing. I am not sure whether it is related to the first point.

I would like to understand how long normal inferencing takes and if there is a way to solve my problem. Thank you again for your outstanding contribution to this work.

Hi there,

Inference on non-default GPU is currently not supported. I will add this feature in the future.
Regarding the processing speed, the duration can vary depending on the complexity and characteristics of the data. If the network struggles to accurately estimate the medial axis, it might result in longer processing times. This is particularly true for data that significantly deviates from the training set's domain. Generally, the process should complete within a few minutes. To help diagnose your specific case, could you send me the data you're using<EMAIL_ADDRESS>? Alternatively what is the output in the terminal when the program jams?

Cheers,
Harry

I'm glad to receive your reply, I think my doubts have been resolved. In addition, the reason why the inference process was blocked may be because I tried to modify the GPU index involved in the project, which may have caused the network model to not be loaded or not located on the GPU I specified. I'll try to resolve this issue, thank you very much for your reply!


feat: implement basic version of tauto tactic

Adds a basic version of the tauto tactic, mostly a line-by-line translation of the Lean 3 version.

As per this zulip discussion, makes tauto always-classical and eliminates tauto!.
Does not yet add any symmetry-based logic or the fancy union-find datastructure from https://github.com/leanprover-community/mathlib/pull/180.
Adds a andThenOnSubgoals tactic combinator in Mathlib.Tactic.Basic.

Ok, got it. I'll re-remove the tauto! syntax. What about the import Mathlib.Tactic.Tauto in Syntax.lean. Is that still needed?

I did some refactoring (not changing the algorithm at all), and moved some declarations to other homes.
I wouldn't mind one day have a MetaM level version of tautoCore and tautology, but there's no immediate need.

Before we can widely deploy tauto we'll need the fix for https://github.com/leanprover/lean4/issues/1963. However I'm inclined to merge now as it is already useful.

bors merge


Support detecting all networks in OpenShift

Networks in config.openshift.io/v1 is exposed for both
OpenShiftSDN and OVNKubernetes, while ClusterNetworks
seems to be only used with the operator for OpenShift SDN.
[majopela@bluehat subm-demo]$ subctl join --kubeconfig cluster-a/auth/kubeconfig broker-info.subm --cable-driver libreswan
* broker-info.subm says broker is at: https://api.majopela-cluster-a-09-10-20-1599722826.devcluster.openshift.com:6443
...
⠈⠑ Discovering network details     Discovered network details:
        Network plugin:  OVNKubernetes
        Service CIDRs:   [<IP_ADDRESS>/16]
        Cluster CIDRs:   [<IP_ADDRESS>/14]
...

[majopela@bluehat subm-demo]$ subctl join --kubeconfig cluster-b/auth/kubeconfig broker-info.subm --cable-driver libreswan
* broker-info.subm says broker is at: https://api.majopela-cluster-a-09-10-20-1599722826.devcluster.openshift.com:6443
...
⠈⠑ Discovering network details     Discovered network details:
        Network plugin:  OpenShiftSDN
        Service CIDRs:   [<IP_ADDRESS>/16]
        Cluster CIDRs:   [<IP_ADDRESS>/14]

Related-Issue: #778

@sridhargaddam @skitt this is working now


Assertion error on void genTxt()

When I try to ./FaceAlignment prepare:
FaceAlignment: /home/bh/git/face-alignment-at-3000fps/src/prepare.cpp:49: void genTxt(const string&, const string&): Assertion `inFile && outFile' failed.

This is just the training file missing on /data/ folder.
Go here http://ibug.doc.ic.ac.uk/resources/facial-point-annotations


drop box listener APItoken

Empire Version
2.5
OS Information (Linux flavor, Python version)
kali linux latest
Python latest
Expected behavior and description of the error, including any actions taken immediately prior to the error. The more detail the better.
my port forwarding is correct and i checked after starting listener the service was confirmed from Canyouseeme website but no staging would happen with macro or python script!
both external and private port are the same
Host: is set to external IP
Bindip: is set to private IP
Screenshot of error, embedded text output, or Pastebin link to the error
Any additional information

Do you have any information about the actual error occurring or any clues as to why staging isn't happening? Are you getting any messages from Empire?

yes there was a series of errors i will provide them as soon as i can.

Exception in thread Thread-2:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner
self.run()
File "/root/Desktop/Empire/lib/common/helpers.py", line 900, in __run
self.__run_backup()
File "/usr/lib/python2.7/threading.py", line 754, in run
self.__target(self.__args, **self.__kwargs)
File "/root/Desktop/Empire//lib/listeners/dbx.py", line 1082, in start_server
for match in dbx.files_search(resultsFolder, ".txt").matches:
File "/usr/local/lib/python2.7/dist-packages/dropbox/base.py", line 2073, in files_search
None,
File "/usr/local/lib/python2.7/dist-packages/dropbox/dropbox.py", line 272, in request
timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/dropbox/dropbox.py", line 363, in request_json_string_with_retry
timeout=timeout)
File "/usr/local/lib/python2.7/dist-packages/dropbox/dropbox.py", line 447, in request_json_string
timeout=timeout,
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 555, in post
return self.request('POST', url, data=data, json=json, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 508, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 618, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 521, in send
raise ReadTimeout(e, request=request)
ReadTimeout: HTTPSConnectionPool(host='api.dropboxapi.com', port=443): Read timed out. (read timeout=30)

after getting an agent it give me this error
and i can get no more agents

i found how the error occur
after starting listener on drop box
if internet get disconnected the error occur
the work around is to restart the hole system
why?
i do not know!

Dropbox is killing Empire listeners on their end. The options here are basically either figure out a way to avoid Dropbox's detection of Empire agents, or use another listener.


Required plugin "DiscordRolesync' not found

I've installed and was able to configure all the settings in discourse.
However I receive
Processing by DiscordRolesync::SyncsController#botstats as JSON
Required plugin 'DiscordRolesync' not found

Plugin name is 'DiscordRolesync', but plugin directory is named 'discord-rolesync'

I was able to sync roles once i was logged in.
But noticed it didn't grant roles to another user upon first login
Have to click sync for every user that joins the discourse

Disregard, Fixed.

I have the same issue


check28 - Warning! for AWS Default KMS Keys

So this is an interesting one - for check28 I get two keys are not set to rotate:

When I run the CLI commands manually I get 8 keys - the screenshot above shows 10 keys - not sure why that is the case.

Also, the keys that are showing not set to rotate! are AWS default master keys that are created when you encrypt a resource without specifying your own CMK. One of those keys does not display from the manual query - the one from us-east-1
Unfortunately, there doesn't appear to be a way to distinguish a CMK and a default KMS master key. I tried searching using 'Keys[*].KeyArn' but do not see anyway to differentiate between CMK and AWS default keys.
I also opened a case with AWS and was told that once a default AWS key has been created, there is no way to delete it. :( AWS supposedly rotates default master keys every year but when you do a query for a key the response is False:

Yep, I have seen there is no way to set rotation for default keys...

Answering your other question, prowler queries all keys in all regions, this is why you get 10 keys. If you use a single command you will get only keys on your current working region.

Ah! Okay, got it apologies for that.
As a suggestion, since no way to determine whether default KMS key or not, perhaps update the message to something like:
WARNING! Key XXXXXXXXX in Region XXXXX is not set to rotate OR Default KMS Key In Use!

Ok, added your suggestion in PR #18


Service updates

subscribe to this thread to get notified on every updates

first release. customizable options enabled.

report won't be pushed back when it faces errors.
inspect console log for error messages.

Customizable git commit message feature added. Now you can decide what would be the commit message for the report while pushing into your repo.

default branch has been changed from master to main.
cppcheck is updated to latest version
Removed: ability to change commit message for the report while pushing ( planned for the next release )


Obsidian becomes unresponsive when no timeMin or timeMax value is specified.

When I take the sample block from the readme:
```sync-calendar
name: "{numberTodos} todos @ Apr. 21"
timeMin: "2023-04-21"
timeMax: "2023-04-22"
```

And change it to this and let it render:
```sync-calendar
name: "{numberTodos} todos @ Apr. 21"
```

Obsidian becomes unresponsive, even after restarting. It goes away when I move or delete the plugin folder. Here's is some system information of that helps:

macOS 13.1.
Obsidian 1.2.8 (it also froze in 1.2.7).
Plugin version 1.1.3.

Sorry for the confusion, but I'm unable to reproduce the issue you reported. The latest version of the plugin appears to be working properly for me.
https://github.com/dustinksi/obsidian-sync-calendar/assets/20951128/2cd8f1f7-33e4-4bcd-aff5-fef9e709ee25
A few suggestions to help resolve this:

Please double-check that you are running the latest release of the plugin. If not, try updating to the latest version and see if that fixes the problem.
As an alternative, you can enable "Debug Logging" for the plugin. This will output logs that may help locate where the problem is occurring. Please enable logging and send me the logs, so I can better diagnose what's going wrong.

Please let me know if any of these options help resolve the issue. I apologize for the inconvenience and will do my best to get to the bottom of this and push out any necessary fixes. Please feel free to ask me for any additional details or let me know if there's any other way I can assist you in troubleshooting this.


Fix actual_root_path implementation

Fix actual_root_path implementation

Hello @drewbug could you share what you are trying to do here?

@kbrock: The README says: By default, this class will look for a yml file named "countries.yml" in the same directory as the file.
I was just attempting to bring the actual implementation into line with this. I was bitten by this when starting a daemon from a different working directory. My easy workaround is: set_root_path __dir__, but this doesn't work on Ruby versions older than 2.0

Thanks, that is helpful.
Using dir or filename will be the same result. The directory of this gem file, not the caller's dir. Maybe caller or caller_location may be of use?
I'll try and play with this...

You're right, @kbrock, I didn't even think about that. D'oh!

@drewbug there may be a way to look at self.class.method(?).source_location or something?
I'm sure the answer is simple, just have to find it


Add GA4 tracking to browse action link

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠
What

the action link appears on the /browse/benefits page to signpost to a highlighted link
adds GA4 tracking to this link

Why
Part of the GA4 migration.
Visual changes
None.
Trello card: https://trello.com/c/lstNprcf/717-add-tracking-to-action-link

Thanks @AshGDS, great job noticing that. I've added the data-ga4-track-links-only attribute as well, which has fixed the problem here.

Ah yes good point, have fixed thanks @AshGDS


Update database schema

User story

As a developer
I want / need an updated database schema
So that it natches the Kubernetes API

Acceptance criteria

[ ] Kubernetes API and database schema match

Linked Issues

Blocked by:
Related to: #85
Implements

Additional information

none

Definition of done (DoD)

Colours match with color scheme
Implementation is unit tested
Code documentation updated (jsdoc or godoc?)
Changes to database documented at Confluence- Database scheme
Changes to architecture documented at Confluence - Architecture

DoD general criteria

Feature has been fully implemented
All acceptance criteria were met
Product owner approved features
All tests are passing
Pull request to "develop" branch is merged & closed
Bill of materials is updated with new dependencies

First changes with watcher implementation, needs further implementation

Excel with Kubernetes API representation is uploaded to confluence and can be updated with new approaches for the scheme. For example what fields should be imported and if they should, as a special field in PostgreSQL or as plain JSON?

Scheme specified and documented. Changes will be applied once feature implementationr requires it.


get a typo in images.md: Dokcer authentication

For my first contribute to open source code, I found the typo which exists in both release-1.14 and master branch docs.
Please check if anything I need to do for this pull request, such as to modify some informal pr message.
Thx, dear reviewers.

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.
It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address.  Check your existing CLA data and verify that your email is set on your git commits.
If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at<EMAIL_ADDRESS>
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.
It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address.  Check your existing CLA data and verify that your email is set on your git commits.
If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at<EMAIL_ADDRESS>
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I have signed the CLA, please check.

@erictune
Kubernetes Prow Robot suggests me in email that, the pr needs your approve if wanted to be fully approved. If you check that, I will appreciate it. Thx.

/lgtm
/approve


Adding @types/ws to the dependencies

Closing the issue https://github.com/uport-project/daf/issues/91

This was fixed here https://github.com/uport-project/daf/commit/55e0fcb1a68e86c7003909fb03f92ee1b357026c


Flutter thingsboard mobile app no answer after login

Hi!
After creating mobile app with Flutter and thingsboard, On the android 11 emulator, I obtained the login/password page.
I put my credentials for thingsboard.cloud and get... nothing.
The debug put no error messages.
I case I put wrong credentials, I got an error message.
Why can I access to my dashboards defined on thingsboard.cloud ?
Thanks!

Hi. I'm having a similar problem. In my case, I can't access the dashboard. Did you find a solution?

Hi @Ifousoft and @yunamoon
We are very sorry that you received this error. We have already updated the code in the master branch and fixed this problem.

You need to use another project (https://github.com/thingsboard/flutter_thingsboard_pe_app) to connect thingsboard.cloud


Spyder python3.11.9 can't find spyder_kernels module

Describe the bug
When opening spyder, then console report /nix/store/4rf5qybw37b4lh1g0xczlv14sqdbmnpm‑python3𔂭.11.9/bin/python3.11: Error while finding module specification for 'spyder_kernels.console' (ModuleNotFoundError: No module named 'spyder_kernels')
Steps To Reproduce
Steps to reproduce the behavior:

Install spyder from 24.05
Open spyder from start menu

Expected behavior
Spyder's python should find spyder_kernels since it is in the spyder's dependencies list.
Additional context
I've tried to install spyder on nixos bootable iso using nix-env and still get same result.
Notify maintainers
@gebner

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
❯ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.40, NixOS, 24.05 (Uakari), 24.05.20240717.c716603`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.5`
 - channels(root): `"nixos-24.05"`
 - nixpkgs: `/nix/store/sj9yrq21wbbfr5715hys3laa2qd6x471-source`

Add a :+1: reaction to issues you find important.

I think I just learned how to install python package correctly in system-wide.
(pkgs.python3.withPackages (python-pkgs: [python-pkgs.spyder]))

IMO this should not happen when installing pkgs.spyder, which is what a normal user would do, right?
The user should not have to install python system-wide.
I would like to re-open this issue because of this, pinging the spyder maintainer here: @gebner

I think I just learned how to install python package correctly in system-wide.
(pkgs.python3.withPackages (python-pkgs: [python-pkgs.spyder]))

This worked for me, thanks a lot :)


Will you continue on your tut?

Hi Patrick,
I enjoyed your tutorial very much and was looking forward to find out more. Seems like you stopped working on it, right? We have Autumn/Winter 2017 now and the last words were from "cold days 2016".
I know there are more important things in life but I'd like to know if sth will ever be continued.

I would really appreciate it. This no-framework-tutorial is great! 👍

I put my effort into a book instead, which is also in the form of a tutorial. I had to start from scratch because I learned a lot since publishing this tutorial.
See http://patricklouys.com/professional-php/ for more.


Add STIG reference parser

This ensures that rules part of STIG profile contain annotations with the STIGID.
One can see the STIG references as annotation on the rule when deployed together with content from https://github.com/ComplianceAsCode/content/pull/11593
$ CONTENT_IMAGE=ghcr.io/complianceascode/k8scontent:11593 make deploy-local
$ oc get rule  ocp4-api-server-tls-security-profile -oyaml
...
metadata:
  annotations:
    compliance.openshift.io/image-digest: pb-ocp4vkwnn
    compliance.openshift.io/profiles: ocp4-moderate-rev-4,ocp4-stig,ocp4-high-rev-4,ocp4-stig-v1r1,ocp4-moderate,ocp4-high,ocp4-nerc-cip
    compliance.openshift.io/rule: api-server-tls-security-profile
    control.compliance.openshift.io/NIST-800-53: SC-8;SC-8(1)
    control.compliance.openshift.io/STIG: CNTR-OS-000020
    policies.open-cluster-management.io/controls: SC-8,SC-8(1),CNTR-OS-000020
    policies.open-cluster-management.io/standards: NIST-800-53,STIG
...

/hold for test

@yuumasato It is weird. I noticed there is stig annotation for stig in the master branch without the PR:
$ oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.16.0-0.nightly-2024-02-26-013420   True        False         11h     Cluster version is 4.16.0-0.nightly-2024-02-26-013420

$ oc get rule  ocp4-api-server-tls-security-profile -o=jsonpath={.metadata.annotations} | jq -r
{
  "compliance.openshift.io/image-digest": "pb-ocp4qrc9k",
  "compliance.openshift.io/profiles": "ocp4-nerc-cip,ocp4-high-rev-4,ocp4-stig-v1r1,ocp4-moderate,ocp4-stig,ocp4-moderate-rev-4,ocp4-high",
  "compliance.openshift.io/rule": "api-server-tls-security-profile",
  "control.compliance.openshift.io/NIST-800-53": "SC-8;SC-8(1)",
  "policies.open-cluster-management.io/controls": "SC-8,SC-8(1)",
  "policies.open-cluster-management.io/standards": "NIST-800-53"
}

Verification pass with 4.16.0-0.nightly-2024-02-29-062601:

$ utils/build_ds_container.py -i ghcr.io/complianceascode/k8scontent:11593
2024-03-01 15:36:10,750:INFO: Created profile bundles for ocp4, rhcos4

$ oc get rule  ocp4-api-server-tls-security-profile -o=jsonpath={.metadata.annotations} | jq -r
{
  "compliance.openshift.io/image-digest": "pb-ocp44m6tp",
  "compliance.openshift.io/profiles": "ocp4-high,ocp4-stig,ocp4-moderate,ocp4-high-rev-4,ocp4-moderate-rev-4,ocp4-stig-v1r1,ocp4-nerc-cip",
  "compliance.openshift.io/rule": "api-server-tls-security-profile",
  "control.compliance.openshift.io/NIST-800-53": "SC-8;SC-8(1)",
  "policies.open-cluster-management.io/controls": "SC-8,SC-8(1)",
  "policies.open-cluster-management.io/standards": "NIST-800-53"
}
$ oc get rule  upstream-ocp4-api-server-tls-security-profile -o=jsonpath={.metadata.annotations} | jq -r
{
  "compliance.openshift.io/image-digest": "pb-upstream-ocp46k8b6",
  "compliance.openshift.io/profiles": "upstream-ocp4-high,upstream-ocp4-stig-v1r1,upstream-ocp4-stig,upstream-ocp4-moderate-rev-4,upstream-ocp4-moderate,upstream-ocp4-nerc-cip,upstream-ocp4-high-rev-4",
  "compliance.openshift.io/rule": "api-server-tls-security-profile",
  "control.compliance.openshift.io/NIST-800-53": "SC-8;SC-8(1)",
  "control.compliance.openshift.io/STIG": "CNTR-OS-000020",
  "policies.open-cluster-management.io/controls": "SC-8,SC-8(1),CNTR-OS-000020",
  "policies.open-cluster-management.io/standards": "NIST-800-53,STIG"
}

/unhold

@Vincent056 @rhmdnd This should be ready for review

@rhmdnd @Vincent056 I have added a parser for SRGs.
When content from https://github.com/ComplianceAsCode/content/pull/11647 is deployed, we can see the following annotations:
oc get rule  ocp4-api-server-tls-security-profile -o=jsonpath={.metadata.annotations} | jq -r
{
  "compliance.openshift.io/image-digest": "pb-ocp4j6dgh",
  "compliance.openshift.io/profiles": "ocp4-moderate-rev-4,ocp4-stig-v1r1,ocp4-high-rev-4,ocp4-high,ocp4-nerc-cip,ocp4-moderate,ocp4-stig",
  "compliance.openshift.io/rule": "api-server-tls-security-profile",
  "control.compliance.openshift.io/NIST-800-53": "SC-8;SC-8(1)",
  "control.compliance.openshift.io/SRG-APP-CTR": "SRG-APP-000014-CTR-000040;SRG-APP-000560-CTR-001340",
  "policies.open-cluster-management.io/controls": "SC-8,SC-8(1),SRG-APP-000014-CTR-000040,SRG-APP-000560-CTR-001340",
  "policies.open-cluster-management.io/standards": "NIST-800-53,SRG-APP-CTR"
}

Do you have any opinion on the control name SRG-APP-CTR?

Got the same result with comment https://github.com/ComplianceAsCode/compliance-operator/pull/494#issuecomment-1977010549 when content from https://github.com/ComplianceAsCode/content/pull/11647 deployed

/unhold

/label qe-approved

Do you have any opinion on the control name SRG-APP-CTR?

This should align with the cells in the STIG spreadsheets, right?

Do you have any opinion on the control name SRG-APP-CTR?

This should align with the cells in the STIG spreadsheets, right?

Yes, but not necessarily.
The SRGs in each rule should match the ones in the spreadsheet, unless there were changes or bugs during generation of the spreadsheeet, and/or changes that DISA did from the spreadsheeet to the published xml.

@Vincent056 should be ready for review


Clear device name error properly on provisioning

We weren't clearing device name error on input change.
This would cause the error to persist, even after changing the input text which was confusing to some users.

@keybase/react-hackers

The commits dd0d6c62723f...b4f69799868e introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)

The commits dd0d6c62723f...a09e5fa39bd8 introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)

i mean, if we're cleaing the error and its in the store, we should just update it in the store and this component is fine. why does it have its own cached version of the error? we should avoid having local state period

Login was using a route prop and signup was using the store for deviceNameError.
I changed login to use the store like signup, and am triggering a clear of the error on input change.

Route prop isn't a great place for something like an error cause it needs to be cleared on a input state change.

The commits 7f9625a81a54...2f2be2783002 introduce visual changes on linux. :mag_right: 1 changed

Changed: Paper_Key-Normal (before) (after)


nvrtc is not supported in cuda 5.5 .

Hi , @piiswrong ：
nvrtc is not supported in cuda 5.5  .  Out of the consideration of compatibility , one better method is to use MACRO for distinguishing whether to use nvrtc , just as the case of cudnn. Thanks.

+1, this change makes cuda-6.5 inapplicable

You are right. I'll add a flag when I have time. But I a little busy these days. It will be great if somebody can step in. Should be a simple change

fixed in https://github.com/dmlc/mxnet/pull/1048

@piiswrong , Thanks !


Version bump to 0.2.1

This change is

r? @Fraser999
(maidsafe_highfive has picked a reviewer for you, use r? to override)

Reviewed 1 of 1 files at r1, 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io


Support py3 and tests

Work in progress PR, for work on adding some tests (and Python3 support)

Good catch on the move mouse commands.  I would have been submitting another PR for those otherwise.
Also, thanks for taking the time to look into testing!


Package request: Azote

Project description
Wallpaper manager for wlroots-based compositors and some other WMs
Metadata

homepage URL: https://nwg-piotr.github.io/nwg-shell/azote
source URL: https://github.com/nwg-piotr/azote
license: GPL3.0, COLORTHIEF
platforms: Linux

Duplicate of #217492

Ah, somehow missed that. Closing.


List of inference issues

Need to update the inference accuracy to reflect that we want to allow ~1-2% loss during deployment process.

Definition updates
Pre/post processing for open?
What hyperparameters do we want to have rules about (aside from batch size)?
Formal DUT/SUT definition
Input optimization - what input-based optimizations do we want to prohibit (e.g., quantization)
Single score for each set of BM results?

Wrong place and obsolete.


WIP - Adds support for storm-0.10.0

Per Issue #68 Adds support for storm-0.10.0
This creates a multi-module maven build and a v9-v10 shim.  Profiles are used to choose the correct shim at compile time.  Modified build-release.sh to use STORM_RELEASE and MESOS_RELEASE environment variables to influence build behavior.
./build-release.sh builds 0.9.6 and mesos 0.24.1
STORM_RELEASE=0.X.X builds for storm 0.X.X and mesos 0.24.1
STORM_RELEASE=0.X.X MESOS_RELEASE=0.Y.Y builds for storm 0.X.X and mesos 0.Y.Y
Updated versioning of artifacts per issue #76.
Updated .gitignore for _docker, *.zip, *.tgz, to avoid polluting git with build artifacts.
Tested storm-0.9.6 and storm-0.10.0 on live clusters.  No issues to date.

@DarinJ : I see you've added the classifier stuff and adjusted the framework tarball with the storm and mesos suffixes -- awesome!   It looks like it's in good shape, should I test this out now, or are you intending on iterating on it a bit more first?

@erikdw yeah I'm kind conservative on the @'s.  I also sneakily edited my original post to make it even harder to figure out :).
I just got around to testing 0.9.6 and 0.10.0 and they're both doing as expected.  Please test, especially if you can test the docker image, I'm not setup to do that presently.  If you're happy enough to merge, I can squash the commits and rebase.

@DarinJ : I just merged PR #80 that conflicts a bit with this PR (#77).  Can you please rebase / merge your changes on top of that?  Thanks!

@erikdw @choang OK, rebased, applied requested changes and retested.  I think we're good.  Noticed one issue after merge in the new version of build-release.sh. In the dockerImage build -t xxx failed had to move to build -t xxx ..

@brndnmtthws erikdw was looking at this but it on vacation, can you look at this.  I tested it quite a bit, seems to work fine.  After #85 I noticed it's getting more difficult to use LocalState on the supervisor as it was previously without a lot of effort, I tried to maintain the current feel of LocalState, but it might be easier to use a HashSet for keeping track of the ports.

@erikdw hope you had a nice vacation.  When you get a chance can you look at this.

@DarinJ : yep, will do, thanks for your work on it so far, I'll build it with 0.9.6 and verify it's working.
BTW, the "latest" mesos is now 0.26.0, I had some issues with my docker image and vagrant VM host having differing mesos versions (i.e., mesos-slave was setting MESOS_NATIVE_JAVA_LIBRARY to /usr/lib/libmesos-0.26.0.so, instead of just /usr/lib/libmesos.so, and since my docker image had /usr/lib/libmesos-0.25.0.so it failed).  I'm guessing working around such inconsistencies is the reason for @brndnmtthws's workaround here., unless there was a bug fixed in mesos-0.26.0 regarding passing of env variables / setting of that particular one for docker.

@DarinJ : I've tested with storm 0.9.6 and mesos 0.26.0.  FYI, I had to make 1 other change for using mesos 0.26.0:
-          credentialBuilder.setSecret(ByteString.readFrom(new FileInputStream(secretFilename)));
+          credentialBuilder.setSecret(ByteString.readFrom(new FileInputStream(secretFilename)).toString());

Also, I had to make a change to the various vagrant scripts to allow this new naming scheme to work:
${RELEASE} -> ${RELEASE}*
Can you please change make the vagrant script change along with your other changes in here?
Also, give me a bit of time to read through the code a bit more please.

(Just leaving a breadcrumb here)
I wondered what happened with LocalState in storm-0.10.0 that required this shim to be created.  Here's the explanation:
storm-0.9.6 implementation of LocalState was based on Java serialization and the snapshot is a map from Object to Object:

https://github.com/apache/storm/blob/v0.9.6/storm-core/src/jvm/backtype/storm/utils/LocalState.java

Whereas in storm-0.10.0, LocalState has been changed to use Thrift for serialization and the snapshot is a map from String to TBase:

https://github.com/apache/storm/blob/v0.10.0/storm-core/src/jvm/backtype/storm/utils/LocalState.java

This was done to allow for rolling upgrades that avoid problems with the stored state being inconsistent between storm versions:

https://issues.apache.org/jira/browse/STORM-765
https://issues.apache.org/jira/browse/STORM-634

Here are the changes made to storm that implemented this new behavior:

https://github.com/apache/storm/commit/b1dc422bd502ad031d027ba0c026c3e666abe42f#diff-437638c20d4ef66fa4e866a8316c3919

@erikdw bit of a delayed response due to holidays.  Glad to know it worked for you, I'm taking a look a the vagrant scripts now seems straight forward and can do that.
Looked at the changes for mesos 0.26.0, looks like the CredentialsBuilder.setSecret method now has an argument of type String vs ByteString, and they created a second method CredentialsBuilder.setSecretBytes which takes a ByteString.  We could do yet another shim here but for something this simple and the fact it's only accessed once reflection seems like the better choice (though I'm sure I'll eventually regret it).  I've already coded that and am in the process of testing.
Not sure I'll get a chance to do any new changes to LocalState for a bit and while it could be better it works.

@DarinJ : ah, so you're gonna use reflection to figure out whether we need to use the String vs. ByteString in the code, thus preserving support for pre-0.26.0 and post-0.26.0 mesos.  Cool.

@erikdw Think I got all of your requested changes in.  There's a few things that could be better, but I think it's best to address them separately (They're already mentioned as issues elsewhere).  They are:

Not using LocalState, instead use Zookeeper on nimbus and a ConcurrentMap on supervisors
Use maven to build tar ball and docker images, use maven-release plugin
Investigate best way to pass MESOS_NATIVE_LIB to to supervisors when using Docker

This is working for me in my test environment with docker and 0.26. :+1:

Thanks for the changes @DarinJ!  Minor nits mentioned above and then we should be good.  BTW, I would also love it if you happened to know more about the "mesos state storage" APIs that I mentioned above.  We can take that offline though.

@erikdw address squashed commits and rebased.  Still need to test the docker build since merging (not overly worried but want to be thorough), so give me the weekend to sign off.
I did notice during the merge on line 101 of the build-release.sh this line got changed in the last PR:
+  cmd="docker build -t karthick/mesos-storm:git-`git rev-parse --short HEAD` ."

Not sure if that was intentional, pinging @dsKarthick also.  Let me know if it should go back to mesos I can revert that change.  Might be wise to make it $DOCKER_USERNAME passed in like STORM_RELEASE and MESOS_RELEASE, so they can push the built image to dockerhub?  Might be wise to do DOCKER_REGISTRY too in case they want to push to a local registry for speed.

Oh, that was surely a mistake by @dsKarthick & me -- we don't want his own dockerhub account being used, so yes, please revert that.
Let's handle generalizing the docker config in a separate PR to unblock this one.
I'll hold off on your a-ok after the weekend.
Thanks a lot for all the work on this!

@erikdw built the docker image and all went well, should be good changes prior to rebasing have been working well for me so far.  Left the change to the docker tag as a separate commit for book keeping.

thanks @DarinJ !!   Let me sanity check tomorrow, assume it's all good though so should be merging this in tomorrow.

@erikdw gentle reminder. If there's issues I'd like to know while it's still in my head :).

@DarinJ : thanks for the reminder.  I just didn't prioritize completing the testing well.  I've now tested with storm-0.10.0 & mesos-0.26.0, looks good to me!  I'm going to merge your change now, thank you very much for your hard work on making this framework a bit version-agnostic and implementing some of our ideas for versioning and build-ability.

FYI, I tested with storm-0.9.6 and mesos-0.25.0 and it worked as well.  Woot!


Update SDK with 4.20 APIs

code loks good and I can run tests locally without errors, but I see a failing github action. I can run the setup tools step locally without these errors, so probably a runner env and/or ubuntu issue. It would be good to solve it before moving on:
go: golang.org/x/tools/cmd/goimports@latest (in golang.org/x/tools@v0.28.0): go.mod:3: invalid go version '1.22.0': must match format 1.23

code loks good and I can run tests locally without errors, but I see a failing github action. I can run the setup tools step locally without these errors, so probably a runner env and/or ubuntu issue. It would be good to solve it before moving on:
go: golang.org/x/tools/cmd/goimports@latest (in golang.org/x/tools@v0.28.0): go.mod:3: invalid go version '1.22.0': must match format 1.23

never mind


Shortcut for like button

i want to press like for song i'm listening by pressing global shortcut

Hello @seniorivn. Thanks for you feature request. I might look at it in January tiliado/nuvolaplayer.project#19

Hello @seniorivn. If you are still interested in this feature, I would like to ask you for help: Could you create a new Yandex Music account for me with an arbitrary username and password? I cannot get through the CAPTCHA test with Russian letters.

@fenryxo i don't think i'm interested, but i'll help. Check your mail for login and password.

Thanks :-)

Released in 1.5.


Update DataClasses.kt

As a Kotlin newbie and Java developer, I was assuming the data annotation would start with an at sign (@data). Perhaps some additional information would be helpful, like for example: (this will look like this: "data class Person").

The correct fix is to change "annotation" to "modifier" in the text. "data" used to be an annotation in pre-release versions of Kotlin, but now it's a modifier.

Dmitry Jemerov: "The correct fix is to change "annotation" to "modifier" in the text. "data" used to be an annotation in pre-release versions of Kotlin, but now it's a modifier."

@FreekDB, thanks for noticing. I've updated the text.


Bug: Query bindings for array-valued bindings broken

Describe the bug
I'm updating my code base from surrealdb.js version 0.11.1 to surrealdb version 1.0.0-beta.20 and running into a snag. I have this query which returns the expected result set, whether I run it in Surrealist.app:
SELECT VALUE <-belongs_to_model_schema<-entity_schema AS e FROM model_schema WHERE id in $modelSchemaIds FETCH e

or using the 0.11.1 SDK:
const modelSchemaIds = ['model_schema:x'];
const response = await this.query('SELECT VALUE <-belongs_to_model_schema<-entity_schema AS e FROM model_schema WHERE id in $modelSchemaIds FETCH e', { modelSchemaIds });

However, when I attempt this query using SDK 1.0.0-beta.20, I'm getting an empty result set!
Steps to reproduce
See description
Expected behaviour
I'd expect to get the same results that I was getting for SDK version 0.11.1.
SurrealDB version
surreal 1.5.4 for linux on x86_64
JavaScript SDK version
0.0.1-beta.20
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Figured it out (sort of): It's not processing the query bindings properly. If I change the query call from this:
const modelSchemaIds = ['model_schema:x'];
const response = await this.query('SELECT VALUE <-belongs_to_model_schema<-entity_schema AS e FROM model_schema WHERE id IN $modelSchemaIds FETCH e', { modelSchemaIds });

to this:
const modelSchemaIds = ['model_schema:x'];
const response = await this.query(`SELECT VALUE <-belongs_to_model_schema<-entity_schema AS e FROM model_schema WHERE id IN [${modelSchemaIds.map(modelSchemaId => `"${modelSchemaId}"`).join(', ')}] FETCH e`, { modelSchemaIds });

then I get the expected results.

Also works if I map them to StringRecordId instances:
const modelSchemaIds = ['model_schema:x'];
const response = await this.query('SELECT VALUE <-belongs_to_model_schema<-entity_schema AS e FROM model_schema WHERE id IN $modelSchemaIds FETCH e', { modelSchemaIds.map(modelSchemaId => new StringRecordId(modelSchemaId) });

Still broken in v1.1.0.
surreal.query('select ->friends->user.* from only $auth;') returns records in the nested response object.
surreal.query('select ->friends->user.* from only $auth;') returns no records. Running this query against the DB returns the expected records.


pip Install python-docx==1.1.1 raise error in python 3.12, ERROR: Failed building wheel for lxml<=4.9.2,>=3.1.0 (in mac os)

I tested that Python3.12 can successfully install lxml==5.2.1 in my mac and also can install python-docx==1.1.0
But pip install python-docx==1.1.1 required lxml<=4.9.2,>=3.1.0, raise errors as blow:
I try to upgrade pip, setuptools and wheel, The error is still unresolved. Could you please improve lxml version requirement in the future release?
`Using cached python_docx-1.1.1-py3-none-any.whl (242 kB)
Building wheels for collected packages: lxml
Building wheel for lxml (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for lxml (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [175 lines of output]
:117: SyntaxWarning: invalid escape sequence '.'
:67: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
Building lxml version 4.9.2.
Building without Cython.
Building against libxml2 2.9.4 and libxslt 1.1.29
running bdist_wheel
running build
running build_py
creating build
creating build/lib.macosx-10.9-universal2-cpython-312
creating build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/_elementpath.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/sax.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/pyclasslookup.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/init.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/builder.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/doctestcompare.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/usedoctest.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/cssselect.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/ElementInclude.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/init.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/soupparser.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/defs.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/_setmixin.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/clean.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/_diffcommand.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/html5parser.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/init.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/formfill.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/builder.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/ElementSoup.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/_html5builder.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/usedoctest.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
copying src/lxml/html/diff.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/html
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron
copying src/lxml/isoschematron/init.py -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron
copying src/lxml/etree.h -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/etree_api.h -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/lxml.etree.h -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/lxml.etree_api.h -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/objectify.pyx -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/etree.pyx -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/public-api.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xmlid.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/cleanup.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xslt.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xpath.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/debug.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/serializer.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/classlookup.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/saxparser.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/objectpath.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/relaxng.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xinclude.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/iterparse.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/parser.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/dtd.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/apihelpers.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xmlerror.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/readonlytree.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/extensions.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xmlschema.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/schematron.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/docloader.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/nsclasses.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/parsertarget.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/xsltext.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/proxy.pxi -> build/lib.macosx-10.9-universal2-cpython-312/lxml
copying src/lxml/includes/xmlerror.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/c14n.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/xmlschema.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/init.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/schematron.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/tree.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/uri.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/etreepublic.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/xpath.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/htmlparser.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/xslt.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/config.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/xmlparser.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/xinclude.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/dtdvalid.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/relaxng.pxd -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/lxml-version.h -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
copying src/lxml/includes/etree_defs.h -> build/lib.macosx-10.9-universal2-cpython-312/lxml/includes
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/rng
copying src/lxml/isoschematron/resources/rng/iso-schematron.rng -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/rng
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl
copying src/lxml/isoschematron/resources/xsl/XSD2Schtrn.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl
copying src/lxml/isoschematron/resources/xsl/RNG2Schtrn.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl
creating build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_abstract_expand.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_dsdl_include.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_skeleton_for_xslt1.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_svrl_for_xslt1.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/iso_schematron_message.xsl -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
copying src/lxml/isoschematron/resources/xsl/iso-schematron-xslt1/readme.txt -> build/lib.macosx-10.9-universal2-cpython-312/lxml/isoschematron/resources/xsl/iso-schematron-xslt1
running build_ext
building 'lxml.etree' extension
creating build/temp.macosx-10.9-universal2-cpython-312
creating build/temp.macosx-10.9-universal2-cpython-312/src
creating build/temp.macosx-10.9-universal2-cpython-312/src/lxml
clang -fno-strict-overflow -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -O3 -Wall -arch x86_64 -g -DCYTHON_CLINE_IN_TRACEBACK=0 -Isrc -Isrc/lxml/includes -I/Users/Flyingpang/long-image-text-env/include -I/Library/Frameworks/Python.framework/Versions/3.12/include/python3.12 -c src/lxml/etree.c -o build/temp.macosx-10.9-universal2-cpython-312/src/lxml/etree.o -w -flat_namespace
src/lxml/etree.c:262394:36: error: no member named 'curexc_traceback' in 'struct _ts'
PyObject* tmp_tb = tstate->curexc_traceback;
~~~~~~  ^
src/lxml/etree.c:262397:21: error: no member named 'curexc_traceback' in 'struct _ts'
tstate->curexc_traceback = tb;
~~~~~~  ^
src/lxml/etree.c:263340:53: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)op1)->ob_digit;
~~~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:263457:53: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)op1)->ob_digit;
~~~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:265182:53: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)op1)->ob_digit;
~~~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:267536:55: error: no member named 'gi_code' in 'PyGenObject'
if (PyGen_CheckExact(obj) && ((PyGenObject*)obj)->gi_code && ((PyCodeObject )((PyGenObject)obj)->gi_code)->co_flags & CO_ITERABLE_COROUTINE) {
~~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:267536:104: error: no member named 'gi_code' in 'PyGenObject'
if (PyGen_CheckExact(obj) && ((PyGenObject*)obj)->gi_code && ((PyCodeObject )((PyGenObject)obj)->gi_code)->co_flags & CO_ITERABLE_COROUTINE) {
~~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:268588:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:268643:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:268897:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:268952:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269093:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269148:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269289:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269344:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269523:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269578:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269757:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
src/lxml/etree.c:269812:55: error: no member named 'ob_digit' in 'struct _longobject'
const digit* digits = ((PyLongObject*)x)->ob_digit;
~~~~~~~~~~~~~~~~~~  ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
Compile failed: command '/usr/bin/clang' failed with exit code 1
creating var
creating var/folders
creating var/folders/rp
creating var/folders/rp/_b7j9qm55gg5627hy8zw5djm0000gn
creating var/folders/rp/_b7j9qm55gg5627hy8zw5djm0000gn/T
cc -I/usr/include/libxml2 -c /var/folders/rp/_b7j9qm55gg5627hy8zw5djm0000gn/T/xmlXPathInitv4mdlpck.c -o var/folders/rp/_b7j9qm55gg5627hy8zw5djm0000gn/T/xmlXPathInitv4mdlpck.o
cc var/folders/rp/_b7j9qm55gg5627hy8zw5djm0000gn/T/xmlXPathInitv4mdlpck.o -lxml2 -o a.out
error: command '/usr/bin/clang' failed with exit code 1
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for lxml
Failed to build lxml
ERROR: Could not build wheels for lxml, which is required to install pyproject.toml-based projects`

With this and https://github.com/python-openxml/python-docx/issues/1385, I think it looks like pinning lxml to the previous major version in 5a80006553f982ef47ebc9b4eb3652452b3c07e7 did more harm than good.

@musicinmybrain it looks like #1385 is unrelated to the lxml pin.
However a build problem on Python 3.12 is enough to consider reverting this pin ...
Yeah, I'm going to pull that pin. It looks like the cure is worse than the disease. The intent was to allow it to install smoothly on Apple Silicon, but if it breaks elsewhere that's just as bad. We'll just have to live with some folks with newer Macs having to work a little harder to get lxml installed and hope that problem goes away.

I'm getting the same error on pip install. If it ends up being relevant:

python version 3.12.2
pip version 24.0
setuptools 67.6.1
wheel 0.40.0

OSX 13.4.1

@flyingpang @musicinmybrain @evaneill I've pulled that pin on the develop branch up on GitHub.
Can you try a clean install from that branch and see if that resolves this problem?
$ pip uninstall python-docx
$ pip install git+https://github.com/python-openxml/python-docx@develop

@flyingpang @musicinmybrain @evaneill I've pulled that pin on the develop branch up on GitHub.
Can you try a clean install from that branch and see if that resolves this problem?
$ pip uninstall python-docx
$ pip install git+https://github.com/python-openxml/python-docx@develop

Thanks, I can now install the develop branch in a clean environment

@evaneill thanks! That's super helpful :)
I'll push a new maintenance release here ...

https://github.com/python-openxml/python-docx@develop

I tested in my clean python3.12 env, it can successful install develop branch. Thanks!

Okay, v1.1.2 is up on PyPI :)


UI elements in tutorial content

My question concerns the tutorial content. At present, the tutorial content is stored as a string with markdown notation, which is parsed when the data is loaded in my app's Tutorial panel. I have realized one key limitation with this approach. It does not allow for me to include HTML elements from the app's UI in the tutorial content. Consider if I wanted to write an instruction like "Click on the button marked 'Variable' to reveal the available data types" followed by the actual button in a disabled state, to make it clear to the user just which button I am referring to. I think this would be helpful to the user. I suppose this means that I will have to save the tutorial content as HTML, or as Svelte components in their own right, even. How do I consolidate the two approaches, a) wanting to store lesson data in a JSON - later in a Supabase table - and b) wanting to include elements from the app UI interwoven with the text content of my tutorial?

Pr #32 solves this issue


Mitigate stragglers

When running on Lithops, it's common to see a small number of tasks take a lot longer than the others. To mitigate this, we could have a rule like "if any tasks are taking more than x times as long as the first y% completed tasks then launch speculative duplicates for them". (E.g. x=2, and y=75.) This only works since tasks are idempotent.

There is quite a lot of literature on mitigating stragglers in distributed systems (e.g. https://www.sciencedirect.com/science/article/pii/S1319157822000659, https://www.usenix.org/legacy/event/osdi08/tech/full_papers/zaharia/zaharia_html/index.html). A lot of it however assumes that tasks are heterogeneous, or that tasks need to be optimally packed onto available workers, neither of which is the case here, so a simpler policy may suffice.

First attempt in 544fb62d0275e7cba156a9c3dcd7d00ae70df31d


tests: improve reliability locally and during CI

significanly relax progress tests (fix #31, fix #47)
use domain.invalid as invalid domain name

Codecov Report

Merging #48 into master will decrease coverage by 2.40%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #48      +/-   ##
==========================================
- Coverage   93.22%   90.81%   -2.41%
==========================================
  Files           5        5
  Lines         295      294       -1
==========================================
- Hits          275      267       -8
- Misses         20       27       +7

Impacted Files
Coverage Δ

src/Curl/utils.jl
75.75% <0.00%> (-21.22%)
:arrow_down:

src/Curl/Multi.jl
91.66% <0.00%> (-0.08%)
:arrow_down:

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 068fa60...50a914d. Read the comment docs.


mbedtls: Re-add patch to disable VIA padlock

The comment mentioned a conflict with libwebsockets, but we actually
still get this conflict even now that we don't use libwebsockets.
Not sure what component is clashing but we should basically just keep
this patch.
Follow-up to #36823.

I removed it in the previous PR as it mentioned libwebsockets, but obviously that was not the whole story :)
@hpvb @Faless It would likely be good to report this upstream so that they can see if they want to make a proper fix. I'm clueless about ASM and why the symbol conflict is happening though :)
There's no real need to cherry-pick for 3.1 as I kept the patch there, but I'll just cherry-picking the README.md edit for consistency.

Cherry-picked for 3.2.1.

Cherry-picked for 3.1.3.


RFC: rename LambdaEnv -> Invocation

I think "invocation" is a more suitable:

the event and context are relevant only during a specific invocation of the lambda function
"env" is reminiscent of environment variables that have a different lifecycle. Also the concept became overloaded in our custom lambda runtime which is less than ideal.

I left deprecated aliases in place. Should be a pretty easy find-replace for downstreams.

Having superficial experience with aws lambda (before feral existed) I like the name better.

Seems reasonable. Could we provide a Scalafix for the rewrite?

Could we provide a Scalafix for the rewrite?

Let me look into that :)

Will do a follow-up PR with scalafixes for this and some other changes. Thanks everyone!


Add model name for Plus Plug S V2

https://kb.shelly.cloud/knowledge-base/shelly-plus-plug-s-v2

Thanks @thecode @chemelli74


Fixed #32301 -- Made clearsessions raise CommandError when clear_expired() is not implemented.

Raising a CommandError is the recommended way to report errors from
management commands.

@francoisfreitag Thanks :+1: I rebased and simplified tests.


Remove ingress from Istio

Remove lint error from preconfigured.yaml
Remove ingress from all values.yaml addon files
Remove preconfigured k8s ingress object
Remove k8sIngress from top level values.yaml
Initial removal of ingress charts

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: sdake
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [sdake]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sdake: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-local-tests.sh
a476cce7b30806a87fabfd025081515e31610ab8
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@philrud PTAL

thanks @sdake!! you saved me from working on this during lunch break :)
Q: I'd like to see the ingress config remains for some of our addons.  for example:  install/kubernetes/helm/istio/charts/kiali/templates/ingress.yaml
as this will work with k8s ingress.

@duderino I've provided my reasoning here: https://github.com/istio/istio/issues/12015#issuecomment-469764994
If @costinm believes we should do it for 1.1, let's do it of course, I just don't understand what are we gaining by doing this now, considering the new installer is around the corner.

@linsun happy to drop the addons commits from the layers - which would restore them.  I am not clear they would work as is, and they would need qualification I suspect.  Unfortunately, I am really tight on time this week to do such qualification.  Monday is open :)
Cheers
-steve

@sdake: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
bc3fc5c7624a816d80062fd4001125d8d58e9504
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
bc3fc5c7624a816d80062fd4001125d8d58e9504
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
bc3fc5c7624a816d80062fd4001125d8d58e9504
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake let's drop it. I'm chairing a doc testing day this Fri with Dan - we can ask folks to test this on that day.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
bc3fc5c7624a816d80062fd4001125d8d58e9504
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
bc3fc5c7624a816d80062fd4001125d8d58e9504
link
/test istio-integ-k8s-tests

prow/istio-integ-local-tests.sh
b622bd73d01131c7734b0dec8e3638caf95f13e4
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
bc3fc5c7624a816d80062fd4001125d8d58e9504
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
cc48544c749d40d5fdce7d7c3093e9827b05c06f
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@sdake: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
cc48544c749d40d5fdce7d7c3093e9827b05c06f
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
cc48544c749d40d5fdce7d7c3093e9827b05c06f
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Closing because of https://github.com/istio/istio/issues/12015#issuecomment-469911843 and comments on this PR