Doesn't work playstation store

Hi!
with script doesn't work playstation store.
somewhere another place - https://www.esetnod32.ru/download/home/trial/ doesn't work js.
What need for normal work playstation store?
only install this script and ublock.

ghacks-user.js doesn't change javascript behaviour.
On uBlock there are blacklists loaded by default, as EasyPrivacy, that will break some sites.
 The issue is a JS script blocked by uBlock.

No url given, no description of behavior broken, no testing or narrowing down of possible preferences, no troubleshooting attempted - how about turning off ublock, for instance. Cannot test or replicate. Invalid.

Sorry, haven't place for wrote message.

clean firefox 53 and you script.
when we login on https://store.playstation.com/#!/en-us/home/games
{"error":"invalid_client","error_description":"Bad client credentials","error_code":4102,"parameters":[]}
and see that.
What's wrong?

I do not have a login so I cannot test that, but loading https://store.playstation.com/#!/en-us/home/games causes zero issues for me (I enabled all scripts in NS, allowed all thru uBo and uMatrix).
See this: https://community.us.playstation.com/t5/PlayStation-Network-Support/Cannot-login-PSN-store-via-Chrome/td-p/45352485  (and there are more google search results)
The solution in the above link was to do with allowing cookies

The trick is that you need to allow cookies from sonyentertainmentnetwork.com

First this manual i've read and do it and all nothing.
We have problem.
Developers nobody have psn for test?

@Myrai Have you enabled cookies? You can use an extension to control cookies and third party cookies on a site by site basis. The actual cookie setting in the user.js is 2701: network.cookie.cookieBehavior. A value of 0 allows both cookies and 3rd party cookies, which from the previous link I gave is what you will want.

@Myrai it could also be network.http.referer.XOriginPolicy. Try setting it to 0. If that doesn't help, reset all prefs in about:config for which there's a [SETUP] or [WARNING] tag in the user.js.
If you follow the Troubleshooting tutorial you should be able to identify the prefs that cause the problem. NOTE it can be more than 1 pref that is causing the problem!

FF53, new profile, latest master user.js, no addons - created an account @ https://store.playstation.com/ with only changing network.cookie.cookieBehavior to 0.  I don't know what your problem is but it's definitely not this user.js. closing this again

Thanks @earthlng . I suspect English is not @Myrai 's first language, but there may be several reasons

cookies, which we highlight as a pref to look at (this could be his problem, I suspect it is)
Myrai mentions uBo in the first post, but on a subsequent test doesn't - anyway, XSS blocking would not help as it is needed - see earlier comment about sonyentertainmentnetwork.com
There could be a MiTM AV (although sony would have decent ciphers) interfering for all we know

it's definitely not this user.js

Well to be fair, it probably is this user.js - re cookie setting - BUT, we mention this, lots! Maybe I should add a line to the short readme in the user.js ?
- Search this file for the "[SETUP]" tag to find SOME common items you could check before
  using to avoid unexpected surprises: eg COOKIES are DENIED by default (see 2701)


[TEST] Test on Scala 2.13

Why are the changes needed?

enable CI test on Scala-2.13 for all modules except Flink SQL engine
Choose the Spark home version based on server's runtime Scala version for testing
Choose target Scala version of Spark engine main resource Jar  based on Spark home's Scala version
Fixed 1 assertion error of kyuubi-spark-lineage module, as Spark on Scala 2.12 and 2.13 show different order of column linage output in MergeIntoTable ut

SparkSQLLineageParserHelperSuite:
- columns lineage extract - MergeIntoTable *** FAILED ***
  inputTables(List(v2_catalog.db.source_t))
  outputTables(List(v2_catalog.db.target_t))
  columnLineage(List(ColumnLineage(v2_catalog.db.target_t.name,Set(v2_catalog.db.source_t.name)), ColumnLineage(v2_catalog.db.target_t.price,Set(v2_catalog.db.source_t.price)), ColumnLineage(v2_catalog.db.target_t.id,Set(v2_catalog.db.source_t.id)))) did not equal inputTables(List(v2_catalog.db.source_t))
  outputTables(List(v2_catalog.db.target_t))
  columnLineage(List(ColumnLineage(v2_catalog.db.target_t.id,Set(v2_catalog.db.source_t.id)), ColumnLineage(v2_catalog.db.target_t.name,Set(v2_catalog.db.source_t.name)), ColumnLineage(v2_catalog.db.target_t.price,Set(v2_catalog.db.source_t.price)))) (SparkSQLLineageParserHelperSuite.scala:182)

Fixed other tests relying on Scala scripting results

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

Was this patch authored or co-authored using generative AI tooling?

- KYUUBI #3839 session user sign - check session user sign *** FAILED ***
  java.lang.IllegalArgumentException: signature verification failed: publicKeyBase64:g = MIGbMBAGByqGSM49AgEGBSuBBAAjA4GGAAQBwzFKFI0jsJxTOlj17JiUg5t+Uoi80XE3ZW17+2f+F5unUrK9doAPhc6ocyr43Gk9Qr0RirtXdm3fl8FIuttlil0Al2ChHH2s8sVTrcSTYqtRR8WO/e+7LL2VZMV+/2VQOLiFpEKboT96oG9KCHfENNzHvYgwlXJHXemxU/ldt6q3lxw=, signatureBase64:g = MIGHAkF7HlamPOWIUUljI/yJ6IAsrBwfB1Z5v2+ySLdurochqCjO71tJkJxJvEbfy7QunfcFY0HmAFWl5Wk+9ZxyLrFKcgJCAcjlyKqZ7Wj1XuJZ50eXzKVNu1jMeM6JGU9zYepTiHdstuq9iR55Pda2qvg2OQJXWgxv/aCqq9upcUBP02MviThZ, plainText:user
  at org.apache.kyuubi.util.SignUtils$.verifySignWithECDSA(SignUtils.scala:75)
  at org.apache.kyuubi.session.SessionSigningSuite.$anonfun$new$10(SessionSigningSuite.scala:94)
  at org.apache.kyuubi.session.SessionSigningSuite.$anonfun$new$10$adapted(SessionSigningSuite.scala:72)
  at org.apache.kyuubi.operation.JDBCTestHelper.$anonfun$withMultipleConnectionJdbcStatement$4(JDBCTestHelper.scala:61)
  at org.apache.kyuubi.operation.JDBCTestHelper.$anonfun$withMultipleConnectionJdbcStatement$4$adapted(JDBCTestHelper.scala:61)
  at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)
  at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)
  at scala.collection.AbstractIterable.foreach(Iterable.scala:926)
  at org.apache.kyuubi.operation.JDBCTestHelper.withMultipleConnectionJdbcStatement(JDBCTestHelper.scala:61)
  at org.apache.kyuubi.operation.JDBCTestHelper.withMultipleConnectionJdbcStatement$(JDBCTestHelper.scala:54)
  ...
  Cause: java.lang.IllegalArgumentException: Illegal base64 character 20
  at java.util.Base64$Decoder.decode0(Base64.java:714)
  at java.util.Base64$Decoder.decode(Base64.java:526)
  at java.util.Base64$Decoder.decode(Base64.java:549)
  at org.apache.kyuubi.util.SignUtils$.verifySignWithECDSA(SignUtils.scala:62)
  at org.apache.kyuubi.session.SessionSigningSuite.$anonfun$new$10(SessionSigningSuite.scala:94)
  at org.apache.kyuubi.session.SessionSigningSuite.$anonfun$new$10$adapted(SessionSigningSuite.scala:72)
  at org.apache.kyuubi.operation.JDBCTestHelper.$anonfun$withMultipleConnectionJdbcStatement$4(JDBCTestHelper.scala:61)
  at org.apache.kyuubi.operation.JDBCTestHelper.$anonfun$withMultipleConnectionJdbcStatement$4$adapted(JDBCTestHelper.scala:61)
  at scala.collection.IterableOnceOps.foreach(IterableOnce.scala:563)
  at scala.collection.IterableOnceOps.foreach$(IterableOnce.scala:561)
  ...

DropNamespaceV1Suite:
- DROP NAMESPACE using V1 catalog V1 command: basic tests
- DROP NAMESPACE using V1 catalog V1 command: test handling of 'IF EXISTS'
- DROP NAMESPACE using V1 catalog V1 command: namespace does not exist
- DROP NAMESPACE using V1 catalog V1 command: drop non-empty namespace with a non-cascading mode *** FAILED ***
  Expected exception java.lang.IllegalStateException to be thrown, but org.apache.spark.sql.AnalysisException was thrown (DropNamespaceSuite.scala:73)

Curiously,  columns lineage extract - MergeIntoTable case has different order of column lineages result

on Scala 2.12, name, price, id

columnLineage(List(ColumnLineage(v2_catalog.db.target_t.name,Set(v2_catalog.db.source_t.name)), ColumnLineage(v2_catalog.db.target_t.price,Set(v2_catalog.db.source_t.price)), ColumnLineage(v2_catalog.db.target_t.id,Set(v2_catalog.db.source_t.id)))

on Scala 2.12, id, name, price

  columnLineage(List(ColumnLineage(v2_catalog.db.target_t.id,Set(v2_catalog.db.source_t.id)), ColumnLineage(v2_catalog.db.target_t.name,Set(v2_catalog.db.source_t.name)), ColumnLineage(v2_catalog.db.target_t.price,Set(v2_catalog.db.source_t.price))))

Codecov Report

Merging #5196 (c778e8d) into master (3a06cc3) will not change coverage.
Report is 1 commits behind head on master.
The diff coverage is 0.00%.

@@          Coverage Diff           @@
##           master   #5196   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         589     589
  Lines       33236   33250   +14
  Branches     4386    4389    +3
======================================
- Misses      33236   33250   +14

Files Changed
Coverage Δ

...ala/org/apache/kyuubi/plugin/lineage/Lineage.scala
0.00% <0.00%> (ø)

...in/lineage/helper/SparkSQLLineageParseHelper.scala
0.00% <0.00%> (ø)

...n/scala/org/apache/kyuubi/engine/ProcBuilder.scala
0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

1 remaining blocker exception in CI tests.
The Spark hive connector's ut "DROP NAMESPACE using V1 catalog V1 command: drop non-empty namespace with a non-cascading mode" failed on Spark 3.3 on Scala2.13, while it passes on Spark 3.2 on Scala2.13, and also on Spark 3.1-3.3 on Scala2.12.
- DROP NAMESPACE using V1 catalog V1 command: drop non-empty namespace with a non-cascading mode *** FAILED ***
  Expected exception java.lang.IllegalStateException to be thrown, but org.apache.spark.sql.AnalysisException was thrown (DropNamespaceSuite.scala:73)

I need a hand in this block issue in Hive Spark Connector, with mixed runtime conditions and various test results. Do you have time to have look at this? @Yikf

Hi @Yikf , thanks for your support for fixing the problem in Hive Spark connector module. Well done, and now all the test pass on all Spark version on Scala 2.13.
Could you consider move the changes in Hive Spark connector module to a separate PR ? As the adaption is more about Spark version rather than about Scala version.
After the offline discussion with @pan3793 , we would like to do

separate PR code changes for  Hive Spark connector, and will be merged to 1.8
Scala 2.13 compilation test will be left as it is , with 1.8 and master branch
the CI tests for Scala 2.13 will be enabled on master after cutting branch of 1.8

Hi, all the modules (except Flink and Flink IT) now pass all the CI test on Scala 2.13.
As discussed offline, we agree not to enable test runs on the master branch, until the version 1.8.0 branch is cut.
And is there any changes of this PR we could leave to master branch before cutting 1.8.0?  cc @pan3793
I suggest:

introduce spark.archive.scala.suffix to spark.archive.name
replace scala.binary.version of flink.archive.name to 2.12

The code on the remote branch has become rotten. I will create a new PR to enable test on Scala 2.13.

Thanks. It should be good to go.
Shall we merge to branch-1.8 as well ?

Thanks. It should be good to go. Shall we merge to branch-1.8 as well ?

OK if no conflicts

OK, let me squash the commits into one and rebase to the master branch.
It will be merged if CI test pass again.

The PR title/description is not match the change now, please update it before merging

Could you have a second look at this PR ?
The extracted method was replaced by the regex in SparkProcessBuilder. Tests were added for both regexes.
And the title and descriptions are updated.

Thanks for the help and reviewing. This PR is accomplished with the essential support from @pan3793 and @wForget .
Merged to master (1.9.0) and branch-1.8 (1.8.0).


overfitting

I find that the validation loss will increase after only 3 stages.  Does the model have heavy over-fitting problem ?
Train on 5823 samples, validate on 648 samples
Epoch 0
5823/5823 [==============================] - 322s - loss: 14098.2655 - val. loss:<PHONE_NUMBER>
Epoch 1
5823/5823 [==============================] - 322s - loss: 5548.3110 - val. loss:<PHONE_NUMBER>
Epoch 2
5823/5823 [==============================] - 321s - loss: 3508.6181 - val. loss:<PHONE_NUMBER>
Epoch 3
5823/5823 [==============================] - 320s - loss: 2460.4376 - val. loss:<PHONE_NUMBER>
Epoch 4
5823/5823 [==============================] - 322s - loss: 1882.4434 - val. loss:<PHONE_NUMBER>
Checkpoint saved
.
.
.
Number of stage 3
Train on 5823 samples, validate on 648 samples
Epoch 0
5823/5823 [==============================] - 322s - loss: 678.7651 - val. loss: 91479.6172
Epoch 1
5823/5823 [==============================] - 321s - loss: 619.2658 - val. loss: 95824.9844
Epoch 2
5823/5823 [==============================] - 321s - loss: 572.6705 - val. loss:<PHONE_NUMBER>
Epoch 3
5823/5823 [==============================] - 322s - loss: 525.9343 - val. loss:<PHONE_NUMBER>
Epoch 4
5823/5823 [==============================] - 321s - loss: 481.5498 - val. loss:<PHONE_NUMBER>
Checkpoint saved
Number of stage 4
Train on 5823 samples, validate on 648 samples
Epoch 0
5823/5823 [==============================] - 322s - loss: 441.9791 - val. loss:<PHONE_NUMBER>
Epoch 1
5823/5823 [==============================] - 321s - loss: 430.3209 - val. loss:<PHONE_NUMBER>
Epoch 2
5823/5823 [==============================] - 320s - loss: 400.2233 - val. loss:<PHONE_NUMBER>
Epoch 3
5823/5823 [==============================] - 322s - loss: 393.7606 - val. loss:<PHONE_NUMBER>
Epoch 4
5823/5823 [==============================] - 321s - loss: 382.1619 - val. loss:<PHONE_NUMBER>
Checkpoint saved
.
.
.
Number of stage 19
Train on 5823 samples, validate on 648 samples
Epoch 0
5823/5823 [==============================] - 394s - loss: 231.7763 - val. loss:<PHONE_NUMBER>
Epoch 1
5823/5823 [==============================] - 388s - loss: 229.1790 - val. loss:<PHONE_NUMBER>
Epoch 2
5823/5823 [==============================] - 399s - loss: 231.8644 - val. loss:<PHONE_NUMBER>
Epoch 3
5823/5823 [==============================] - 412s - loss: 233.6944 - val. loss:<PHONE_NUMBER>
Epoch 4
5823/5823 [==============================] - 398s - loss: 228.1494 - val. loss:<PHONE_NUMBER>
Checkpoint saved

3 stages mean 15 epochs, that's enough I think.
It would be nice to test it by reducing the size of the model.

Thank you for your reply.
I tested the model trained with 3 stages.
The evaluated results are still not good:
Bleu_1: 0.127
Bleu_2: 0.032
Bleu_3: 0.007
Bleu_4: 0.002
Could you give more details about how to reducing the size of the model ?

Did you do the same hyper-parameter settings as in the paper?

The code is for demonstrating the example. To make it work faster, there are smaller values than the numbers in the paper. ex) TOPK = 3

Thanks.
I actually only used the default hyper-parameter setting in the training and generate code.
I will try to fix that.


ui: drag & drop file upload is not working

Currently on the tip file upload is not working. It looks like the duplicate check is failing. I can add another check in the JavaScript, but we should understand what caused the change in behavior.
For example:
http://localhost:3179/my-search/camli/search/files?wholedigest=sha1-xxx
The search handler used to respond with:
{
    "files": []
}

but now only responds with:
{}

FYI: @mpl

So it looks like it happened here: d94796d4ef768a99e87960bff47e8fc2feb0d7af
I'm assuming the 'files' object is no longer being returned if empty.

yeah, I was about to tell you that I knew where to look for the problem. Feel free to fix or I'll do it later today.

and thanks for the report!
There might be other cases like that with the map->struct changes that I missed.

Ok, I can make the change today.
In general, should we no longer rely on empty objects being returned from the server? I'd have to look closer, but it may affect other cases as well

No, the server should keep answering the same thing regardless of what internal changes  we make, so the client (web UI) can keep on expecting whatever it was receiving before. I caught one or two cases during review where such breaking changes were made but I may have missed some other. I need to re-review that particular aspect probably.

https://camlistore-review.googlesource.com/5067

01cddcc8d557d14fb3cba5de28871d4dbfefc26b


Tracks showing up in multi-scrobbler, but not Maloja

I have multi-scrobbler set up to pull info in from Plex (via Tautulli) and Spotify. I have Maloja set up via API using ENV variables.
I am running in both applications in Docker. using multi-scrobbler:develop.
When multi-scrobbler starts up, the logs show:
2020-11-25T14:00:23-08:00 info   : [Scrobblers] Maloja client initialized
2020-11-25T14:00:23-08:00 info   : [Maloja    ] Test connection succeeded!
2020-11-25T14:00:23-08:00 info   : [Maloja    ] Maloja Server Version: 2.10.5

And when I play tracks in Spotify and Plex, they show up in the multi-scrobbler logs. However, the tracks never appear in Maloja. Am I missing a step?

Do you see a scrobble confirmation in the log for Maloja? It should look like this once the app completes an api call to Maloja for a track scrobble:

2020-11-25T15:28:23-05:00 info   : [Maloja    ] Scrobbled (New)     => (Spotify) Jeff Parker - Blackman, played at 2020-11-25T15:27:48-05:00
2020-11-25T15:28:23-05:00 info   : [Spotify   ] New Track => Jeff Parker - Blackman, played at 2020-11-25T15:27:48-05:00

Just deployed a change that may fix this as well...please try updating your container :) latest or develop

I updated my container on develop and it doesn't seem to have fixed the issue. I also updated my Maloja HOST setting because I noticed it was still set for IPV6. Set Maloja HOST=<IP_ADDRESS> but that did not seem to fix the issue either. Still seeing a message on startup of multi-scrobbler that suggests successful connection to Maloja, but nothing shows up in Maloja.
I am not seeing scrobble confirmations in my multi-scrobbler log.
I do not seem to have an apis.log in my maloja/logs folder. Could that be indicative of a problem w/ Maloja install? I'm running a pretty standard setup of the container.
Here is the content of maloja/logs/debug.log:
2020/11/25 20:59:07  Query Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 20:59:07  Aggregate Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 21:00:05  Query Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 21:00:05  Aggregate Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 21:42:43  Query Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 21:42:43  Aggregate Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 22:00:05  Query Cache: 0 Perm Hits, 5 Tmp Hits, 49 Misses; Current Size: 44/5
2020/11/25 22:00:05  Aggregate Cache: 0 Perm Hits, 0 Tmp Hits, 10 Misses; Current Size: 0/10
2020/11/25 22:21:14  Query Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 22:21:14  Aggregate Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 22:52:32  Query Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0
2020/11/25 22:52:32  Aggregate Cache: 0 Perm Hits, 0 Tmp Hits, 0 Misses; Current Size: 0/0

Thanks for the info. Your maloja instance is fine, Test connection succeeded! from your first log means its working. It's definitely an issue with this app :) I have been writing code under the assumption of an existing history in Maloja because that's how mine looks...so I'm running into use-cases now that break things when Maloja has zero history. Sorry! I will do more testing tomorrow with a clean Maloja install and no history to make sure I've caught everything.
But in the mean time I have push another change to develop that may fix your issue. Please update your container and let me know what happens.
ALSO if you can set this ENV var LOG_LEVEL=debug or change it from the status page by clicking debug

I downloaded the latest update on develop and it solved the problem. Multi-scrobbler and Maloja seem fully functional. Thanks for the help and for developing multi-scrobbler! Very excited to have this set up.


Misc edits

Fixing two typos in the build command in the examples README
Modifying the Cargo.toml to use the local ogc_sys instead of re downloading the whole repo.

oh yes, and the checks failed because libogc now is on version 2.4.1, which changes things about AESND methods

Yeah exactly, I'll probably just bypass checks and commit this anyways because I'm happy enough your change wouldn't cause a build fail (if it was actually compiling lol)

but since i don't really know anything about wii homebrew, i don't want to mess things up by making important changes to aesnd.rs


Python: add CRC validation to reader

It would be nice to make this a flag at constructor time, and maybe default it to off so we don't get a performance hit when this lands. If anyone feels strongly that it should be on by default that's fine too.


1846 grantfinder terminology changes

Ticket #1846
Description
Screenshots / Demo Video
Testing
Automated and Unit Tests

[x] Added Unit tests

Manual tests for Reviewer

[ ] Added steps to test feature/functionality manually

Checklist

[ ] Provided ticket and description
[ ] Provided screenshots/demo
[ ] Provided testing information
[ ] Provided adequate test coverage for all new code
[ ] Added PR reviewers

yes, the feature flag should be enabled in Staging!

@thelmaboamah could you make sure there is nothing on your side blocking this PR. It shows you have requested changes and I'm pretty sure I've marked all changes as resolved so I'm not sure what is happening. Thanks.


[FLINK-5285] Abort checkpoint only once in BarrierTracker

Prevent an interleaved sequence of cancellation markers for two consecutive checkpoints
to trigger a flood of cancellation markers for down stream operators. This is done by
aborting each checkpoint only once and don't re-create checkpoint barrier counts for already
aborted checkpoints.
cc @StephanEwen

Thanks for the review @StephanEwen. Merging...


Fix no allele bug, add more tests for no matches

Closes #97

Decided to add in fixes to EB as well


Allauth template elements

Looking into #4691 I stumbled upon the elements directory.
Since 0.58.0 (2023-10-26) it is possible to override just the elements instead of overriding the templates completely: https://docs.allauth.org/en/latest/common/templates.html#styling-the-existing-templates
This feature lowers our effort to keep up-to-date with allauth but I'm not sure if we can achieve the same quality.

I would love to have a look at solving this issue, however as I am still new, I am a little confused on what a fix would look like, and some extra guidance would be greatly appreciated

Submit a PR and I will have a look at it. I have some time on Monday en Tuesday next week.

I need more clarification on the issue before I can start. I have created a local branch, but I am not sure where to go from here

The template/account folder contains an implementation of the allauth templates. These templates can be removed in favor of the elements that allauth provides: https://github.com/pennersr/django-allauth/tree/main/allauth/templates/allauth/elements
Thats it. if you are familiair with how django templates work it is a game of trail and error te find out which elements need customization and which base templates need to be overridden. If this still sounds like gibberish to you then I advice to learn the django fundaments first before contributing.


Unresolved Dependencies sbt-idea:0.11.0 (sbtVersion=0.11.2, scalaVersion=2.9.1)

Using SBT 0.11.2.  I tried 0.11.1 and 0.11.2 dependencies.  Is there a different way to load plugins.  I did move my .sbt file into project already.
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::          UNRESOLVED DEPENDENCIES         ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: com.github.mpeltonen#sbt-idea;0.11.1: not found
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] 	Note: Some unresolved dependencies have extra attributes.  Check that these dependencies exist with the requested attributes.
[warn] 		com.github.mpeltonen:sbt-idea:0.11.1 (sbtVersion=0.11.2, scalaVersion=2.9.1)
[warn]
[error] {file:/home/danno/testing_scala_book.git/testingscala/project/}default-bd12c2/*:update: sbt.ResolveException: unresolved dependency: com.github.mpeltonen#sbt-idea;0.11.1: not found

Try version 0.11.0 (or 0.11.1-SNAPSHOT) for the plugin with sbt 0.11.2. See http://mpeltonen.github.com/maven/com/github/mpeltonen/sbt-idea_2.9.1_0.11.2/

Yes, I had tried the different ones, I may have forgot to do a reload-plugins when I did so.  Trying again.

Mikko,
What should the plugin.sbt look like now? Also I moved plugins.sbt to project from project/plugins per sbt warnings.

resolvers += "sbt-idea-repo" at "http://mpeltonen.github.com/maven/"
addSbtPlugin("com.github.mpeltonen" % "sbt-idea" % "0.11.0")
Anything else that needs to be changed?

That should be all. Remember to also remove the project/plugins -directory, because if the directory exists, project/plugins.sbt is ignored.

Hey Daniel,
Have you figured out how to resolve the above dependency ?
I tried the above plugin configuration in "/.sbt/plugins/build.sbt" and in "project/plugins.sbt". I tried to remove target directories from under the project,  and there is no project/plugins directory.
"gen-idea no-sbt-classifiers" does not create error, but, I think I do not get all dependencies into my idea project, right?
( I am just starting to play with this )
Thanks.

Guyz,
I've the same problem, using the no classifiers too... I still see
com.github.mpeltonen:sbt-idea:0.11.0 (sbtVersion=0.11.2-20111116-052110, scalaVersion=2.9.1)
As you can see the classifier is present !!
Any clues might help
thanks in advance

Hmm, so are you sure you're using the official sbt 0.11.2 and not some snapshot version? I've never seen the timstamp (which in Maven world means a snapshot) in sbt version in those error messages.

Hello ! I have the same issue with sbt 0.11.2 from http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-tools.sbt/sbt-launch/0.11.2/sbt-launch.jar

All, I gave it a try again, and got the same results.  Now when I run ./sbt reload plugins, it runs fine.    Check that these dependencies exist with the requested attributes.
[warn] 		com.github.mpeltonen:sbt-idea:0.11.1-SNAPSHOT (sbtVersion=0.11.2, scalaVersion=2.9.1)
[warn]
[error] {file:/home/danno/testing_scala_book.git/testingscala/}default-cef86a/*:update-sbt-classifiers: sbt.ResolveException: unresolved dependency: com.github.mpeltonen#sbt-idea;0.11.1-SNAPSHOT: not found
[info] Created /home/danno/testing_scala_book.git/testingscala/.idea_modules/project.iml

Now I have a build.sbt in the root of the project:
name := "Testing Scala"

version := "1.0"

scalaVersion := "2.9.0-1"

libraryDependencies ++= Seq("org.scalatest" % "scalatest_2.9.0-1" % "1.6.1" % "test" withSources() withJavadoc(),
                            "joda-time" % "joda-time" % "1.6.2" withSources() withJavadoc())

In project/plugins.sbt
resolvers += "sbt-idea-repo" at "http://mpeltonen.github.com/maven/"

addSbtPlugin("com.github.mpeltonen" % "sbt-idea" % "0.11.1-SNAPSHOT")

I have deleted project/project project/target and target folder before doing this.

If you're using 0.11.0 version of the plugin with sbt 0.11.2, you should use "gen-idea no-sbt-classifiers". It includes in Idea metafiles everything but source jars of sbt jar files, which should not be a big problem in normal case.
Version 0.11.1-SNAPSHOT should work ok with just "gen-idea" in this regard (i.e. addSbtPlugin("com.github.mpeltonen" % "sbt-idea" % "0.11.1-SNAPSHOT")).

Ok, I got the error too after removing my whole ~/.ivy/.
There's still some problem when not using "no-sbt-classifiers". Sbt tries to resolve the plugin in update-sbt-classifiers task, but is for some reason ubale to do so. "gen-idea no-sbt-classifiers" should be decent workaround anyway.

Getting same issue here.

I'm getting same kind of problem.
plugins.sbt is
resolvers += "sbt-idea-repo" at "http://mpeltonen.github.com/maven/"
addSbtPlugin("com.github.mpeltonen" % "sbt-idea" % "0.11.0")
looks to be resolving without using the organisation?
[info] Resolving com.github.mpeltonen#sbt-idea;0.11.0 ...
[warn] 	module not found: com.github.mpeltonen#sbt-idea;0.11.0
[warn] ==== local: tried
[warn]   /Users/Brett/.ivy2/local/com.github.mpeltonen/sbt-idea/scala_2.9.1/sbt_0.11.2/0.11.0/ivys/ivy.xml
[warn] ==== typesafe-ivy-releases: tried
[warn]   http://repo.typesafe.com/typesafe/ivy-releases/com.github.mpeltonen/sbt-idea/0.11.0/ivys/ivy.xml
[warn] ==== public: tried
[warn]   http://repo1.maven.org/maven2/com/github/mpeltonen/sbt-idea_2.9.1_0.11.2/0.11.0/sbt-idea-0.11.0.pom
[warn] ==== Scala-Tools Maven2 Repository: tried
[warn]   http://scala-tools.org/repo-releases/com/github/mpeltonen/sbt-idea_2.9.1_0.11.2/0.11.0/sbt-idea-0.11.0.pom
[warn] ==== Scala-Tools Maven2 Snapshots Repository: tried
[warn]   http://scala-tools.org/repo-snapshots/com/github/mpeltonen/sbt-idea_2.9.1_0.11.2/0.11.0/sbt-idea-0.11.0.pom
[info] Resolving commons-io#commons-io;2.0.1 ...
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	::          UNRESOLVED DEPENDENCIES         ::
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn] 	:: com.github.mpeltonen#sbt-idea;0.11.0: not found
[warn] 	::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] 	Note: Some unresolved dependencies have extra attributes.  Check that these dependencies exist with the requested attributes.
[warn] 		com.github.mpeltonen:sbt-idea:0.11.0 (sbtVersion=0.11.2, scalaVersion=2.9.1)
[warn]
[error] {file:/work/soc2011/first-akka-sbt/}default-b4b137/*:update-sbt-classifiers: sbt.ResolveException: unresolved dependency: com.github.mpeltonen#sbt-idea;0.11.0: not found
sbt version is 0.11.2

It looks like this is related to this sbt issue: https://github.com/harrah/xsbt/issues/304

'no-sbt-classifiers' behavior is now the default in master.

Did you push the change? I didn't see it.

Not yet, and changed the version :)
But should be out now, with 1.0.0 version!

Cool! :)

oh noes
how can I can get all the sources by default now?

You will still get the sources for libraries (including Scala). You will not get sources for SBT and plugins.

You need to publish-local sbt-idea sources for the sbt-classifiers to work. I.e. someting like this seems to work:

First, you may need to run 'rm ~/.ivy2/cache/scala_2.9.1/sbt_0.11.2/com.github.mpeltonen/sbt-idea/ivy*' to clean up ivy files. This may depend on if you've publish-local'd some other versions of the plugin.
Clone the sbt-idea repo if you haven't already, or pull latest changes
git co 1.0.0
./sbt publish-local

Now 'gen-idea sbt-classifiers' should work and include sbt sources in Idea files. At least this worked for me.

thanks this worked!
hope this would be resolved properly though, I consider the ability to flawlessly get sources for the libraries you use to be important

I can't wait, and I guess it should also map docs too. But I guess I will
find out.  I appreciate all that you do, Mikko.
On Sat, Jan 21, 2012 at 11:03 AM, Mikko Peltonen <
<EMAIL_ADDRESS>
wrote:

You need to publish-local sbt-idea sources for the sbt-classifiers to
work. I.e. someting like this seems to work:

First, you may need to run 'rm
~/.ivy2/cache/scala_2.9.1/sbt_0.11.2/com.github.mpeltonen/sbt-idea/ivy*' to
clean up ivy files. This may depend on if you've publish-local'd some other
versions of the plugin.
Clone the sbt-idea repo if you haven't already, or pull latest changes
git co 1.0.0
./sbt publish-local

Now 'gen-idea sbt-classifiers' should work and include sbt sources in Idea
files. At least this worked for me.

Reply to this email directly or view it on GitHub:
https://github.com/mpeltonen/sbt-idea/issues/119#issuecomment-3597764

--
Daniel Hinojosa
Programmer, Instructor, and Consultant
<EMAIL_ADDRESS>http://www.evolutionnext.com
http://www.abqjug.org

I had the same issue, but I resolved it by doing the following.
addSbtPlugin("play" % "sbt-plugin" % Option(System.getProperty("play.version")).getOrElse("2.0-RC2"))


fix: set timeout for delete work

Signed-off-by: ycyaoxdu<EMAIL_ADDRESS>#159 set a timeout for deleting work.

root@yuchen clusteradm [fix] $ clusteradm get clusters
NAME       ACCEPTED   AVAILABLE   CLUSTERSET   CPU   MEMORY       KUBERENETES VERSION
cluster2   true       Unknown                  8     16185152Ki   v1.21.1
root@yuchen clusteradm [fix] $ clusteradm get works --cluster cluster2
NAME    CLUSTER    NUMBER OF MANIFESTS   APPLIED   AVAILABLE
work2   cluster2   1                     True      True
root@yuchen clusteradm [fix] $ clusteradm delete work work2 --cluster cluster2
Error: delete work work2 timeout, failed to delete
root@yuchen clusteradm [fix] $ clusteradm delete work work2 --cluster cluster2 --force
work work2 in cluster cluster2 is deleted
root@yuchen clusteradm [fix] $ clusteradm get works --cluster cluster2


executePHP should default to false

Defaulting to true is risky for anyone unaware

It already does afaik. Checked on 2.0.0


GlowBrush is causing an error in Windows XP SP3

Once I set the GlowBrush for the window, and run the application. Put the mouse on the edge for 1 second, this will crash the application. After debugging the error was talking about GlowWindow.
[System.EntryPointNotFoundException]	{"Unable to find an entry point named 'GetPhysicalCursorPos' in DLL 'user32.dll'.":""}	System.EntryPointNotFoundException
the call stack is showing the error in GlowWindow.WndProc(...){ ... }
Link to the Repo
Environment

MahApps.Metro __ v 1.5.0 __ dll v<IP_ADDRESS>
Windows OS Windows XP SP3
Visual Studio 2017
.NET Framework 4.0

GetPhysicalCursorPos was introduced with Windows Vista.
MahApps.Metro doesn't support Windows XP anymore, and so does Microsoft for 3 years already.


Issue reading file using readChunkAsArrayBuffer

I'm facing an issue where the readChunkAsArrayBuffer does not seem to output the expected values. I have an application that is using the Aspera Drag and Drop utility to drop files from the user's local machine. To test the issue I used an html input tag and looped through the file using a normal JS File object and compared chunks of the JS file to the Aspera file. I found that the two blobs are equal until about half way through the file. After that the blobs from the file.splice method and readChunkAsArrayBuffer are no longer equal. It may be important to note that the file is around 5GB in size.
Here's the sample code I used to compare the two files
import {b64toBlob} from "../mediaconch/b64toBlob";
import {asperaWeb} from "../Aspera/AsperaConnect";

function compareFiles(asperaDrapAndDropFile) {
    const CHUNK_SIZE = 1024 * 1024;
    const fileSize = asperaDrapAndDropFile.size;

    const htmlFileInput = document.getElementById('file-input').files[0];

    for (let i = 0; i < asperaDrapAndDropFile.size; i += CHUNK_SIZE) {
        let readSize;

        if (fileSize < i + CHUNK_SIZE) {
            readSize = fileSize - i;
        } else {
            readSize = CHUNK_SIZE;
        }

        const asperaArrayBuffer = await asperaWeb.readChunkAsArrayBuffer(
            {
                path: asperaDrapAndDropFile.name,
                offset: i,
                chunkSize: readSize,
            }
        );

        const asperaBlob = b64toBlob(
            asperaArrayBuffer.data,
            asperaArrayBuffer.type
        );

        const htmlInputBlob = htmlFileInput.slice(i, i + readSize);

        blobsAreEqual(asperaBlob, htmlInputBlob).then(result => {
            if (result) {
                console.log('The loop blobs are equal');
            } else {
                console.log('The loop blobs are not equal');
                console.log('i = ' + i);
                console.log('readSize = ' + readSize);
            }
        });
    }

    function blobsAreEqual(blob1: Blob, blob2: Blob) {
        if (blob1.size !== blob2.size) {
            return new Promise((resolve, reject) => {
                resolve(false); // Blobs are not equal.
                return;
            });
        }

        return new Promise((resolve, reject) => {
            const reader1 = new FileReader();
            const reader2 = new FileReader();

            reader1.onloadend = () => {
                const buffer1 = new Uint8Array(reader1.result);

                reader2.onloadend = () => {
                    const buffer2 = new Uint8Array(reader2.result);

                    for (let i = 0; i < blob1.size; i++) {
                        if (buffer1[i] !== buffer2[i]) {
                            resolve(false); // Blobs are not equal.
                            return;
                        }
                    }
                    resolve(true); // Blobs are equal.
                };

                reader2.readAsArrayBuffer(blob2);
            };

            reader1.readAsArrayBuffer(blob1);
        });
    }
}

Just wanted to bump this to see if anyone has started looking into this issue? Is there any way we can get this escalated & prioritized?

@rgodfreyDisco sorry for the delay - we are looking into it. So that we are looking at the same things, can you confirm which OS, browser, and Connect version you are using for your tests?

@dwosk We're using "@ibm-aspera/connect-sdk-js": "5.0.0" in our application.
I'm on windows 10, chrome version 115.0.5790.173.
My coworker is on macOS Ventura 13.5.1 running chrome 116.0.5845.96

With macOS Ventura, Aspera Connect v4.2.6 (client version), and latest Chrome, I'm seeing the same issue. When comparing blobs of a 5GB file, the blobs are identical up until the same 4GB offset:
The loop blobs are not equal
i =<PHONE_NUMBER>
readSize = 1048576

If I re-run the test multiple times it consistently fails at the same offset. Even if I start the test at that offset, the blobs are immediately different.
4294967296 corresponds to 2^32 which is actually above the maximum size for the integer type we use to parse the offset parameter. Attempting to read a chunk starting at an offset of 4GB results in an overflow, which explains why the blobs are suddenly different.
We'll have to change the type that we parse the offset parameter into in the backend in order to support higher offsets.
However, iteratively comparing blobs of an entire 5GB file takes a considerable amount of time - is this the intended behavior for your integration or is this simply test code? Other than this issue, the blobs do seem to be correct.

It will be fixed in the next release of Aspera Connect, which is currently slated to be v4.2.7. Unfortunately, I cannot give a timeline as to when it will be released though.

The code I attached was just sample code I used to debug the issue, we're not reading and comparing the entire file. We are using another library that jumps around the file and reads it in at different points. It ends up reading a couple chunks toward the end of the file which is causing us issues.

Ok that is what I thought. As a workaround, can you instruct the library to not read chunks after that offset?

Great, glad to hear it will be fixed in the next version.
Unfortunately we need to read chunks toward the end to analyze the files correctly.
The workaround I have implemented is to bubble the drop event up to a wrapper div and then parse through the files using the js File.slice() function. But there are still restrictions to this workaround since we also provide a way to use a file selector to select files. In that scenario there is no event to bubble up.
If there was a way to create a normal js File from the Aspera File object (and visa versa) then I could implement a workaround that covers all scenarios

Yeah, that makes sense. In the drag and drop use case, you have access to the native drop event and can use the File API to read the chunks, which is what it sounds like you are doing.

But there are still restrictions to this workaround since we also provide a way to use a file selector to select files. In that scenario there is no event to bubble up.
If there was a way to create a normal js File from the Aspera File object (and visa versa) then I could implement a workaround that covers all scenarios

Unfortunately, for security reasons, I do not think the browser will allow something like this - though I agree this would be useful.

@rgodfreyDisco FYI Connect 4.2.7 has been released which contains the fix for this issue.

Great news! Thanks for the heads up @dwosk

@dwosk Is there a way to make sure users have a specific version of Connect?

It is possible to enforce a minimum version of Connect with the minVersion option documented here.
I believe this will result in an OUTDATED Connect status event if the user's Connect is lower than this specified minimum version. If your Aspera integration is using the default Connect installer UI included with the SDK then this should open a modal with download links to the latest Connect installers. If your integration has its own Connect installer UI then it will be up to your application to handle this OUTDATED event appropriately and do something similar.

Is that the correct link? I don't see a minVersion option there

@rgodfreyDisco sorry I've updated the link.

Perfect! Thanks again for your help!


Scheduler policy can be read from ConfigMap

Feature Description

One-line feature description (can be used as a release note): Allow users to configure scheduler policy (which predicates to enable, which priority functions to enable, weights of priority functions, etc.) using ConfigMap, as an alternative to scheduler config file
Primary contact (assignee): @bsalamat
Responsible SIGs: sig-scheduling
Design proposal link (community repo): https://docs.google.com/document/d/19AKH6V6ejOeIvyGtIPNvRMR4Yi_X8U3Q1zz2fgTNhvM/edit#heading=h.lcgxfb3ef4vt
Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @davidopp
Approver (likely from SIG/area to which feature belongs): @davidopp
Feature target (which target equals to which milestone):

Alpha release target (x.y) 1.8
Beta release target (x.y) 1.9
Stable release target (x.y)

/sig scheduling

@bsalamat May I ask what's the status of this feature? Can we make it in 1.8 or postponed?

It is partly implemented and is available even in 1.7. Scheduler can read its policy config from a ConfigMap, however, it does not monitor changes to the ConfigMap. So, changes made to the ConfigMap after scheduler start-up won't be picked up and user has to manually restart the scheduler for the changes to be effective.

Oh, I think the PR can be tracked is: https://github.com/kubernetes/kubernetes/pull/44805

@bsalamat @kubernetes/sig-scheduling-feature-requests can you confirm that this feature targets 1.8?
If yes, please, update the features tracking spreadsheet with the feature data, otherwise, let's remove this item from 1.8 milestone.
Thanks

@idvoretskyi This does not target 1.8. I am not sure if I have permission to change milestone.

Can someone make the design document public? I can't access it...

@yuvipanda Please join kubernetes-dev to gain access.

@bsalamat what's the correct milestone?

Hi, I'm trying to use this feature by creating the following configMap
kind: ConfigMap
apiVersion: v1
metadata:
  name: kube-scheduler
  namespace: kube-system
data:
  kind: Policy
  apiVersion: v1
  predicates:
  - name: MatchInterPodAffinity
  - name: NoDiskConflict
  - name: CheckNodeDiskPressure
  - name: MaxEBSVolumeCount
  - name: MaxGCEPDVolumeCount
  - name: GeneralPredicates
  - name: PodToleratesNodeTaints
  - name: CheckNodeMemoryPressure
  - name: NoVolumeZoneConflict
  priorities:
  - name: BalancedResourceAllocation
    weight: 1
  - name: NodePreferAvoidPodsPriority
    weight: 1
  - name: NodeAffinityPriority
    weight: 1
  - name: TaintTolerationPriority
    weight: 1
  - name: SelectorSpreadPriority
    weight: 10
  - name: InterPodAffinityPriority
    weight: 1
  - name: LeastRequestedPriority
    weight: 1
  - name: ServiceSpreadingPriority
    weight: 4

But it's failing validation... Do you have any documentation, example, snippet showing how I should properly do this?
Thanks a lot! =)

@waldman Here is a scheduler policy config (in JSON) that I was using a while ago to test configuring scheduler:
{
"kind" : "Policy",
"apiVersion" : "v1",
"metadata" : {
    "name": "scheduler-policy-config",
    "namespace": "kube-system"
    },
"predicates" : [
	{"name" : "PodFitsHostPorts"},
	{"name" : "PodFitsResources"},
	{"name" : "NoDiskConflict"},
	{"name" : "NoVolumeZoneConflict"},
	{"name" : "MatchNodeSelector"},
	{"name" : "HostName"}
	],
"priorities" : [
	{"name" : "LeastRequestedPriority", "weight" : 1},
	{"name" : "BalancedResourceAllocation", "weight" : 1},
	{"name" : "ServiceSpreadingPriority", "weight" : 1},
	{"name" : "EqualPriority", "weight" : 1}
	]
}

I then create the configmap by running:
kubectl create configmap scheduler-policy-config --namespace=kube-system --from-file=path/to/scheduler-policy-config.json

Is this a currently supported feature, is there documentation and what valid parameters I can use for predicates and other fields

Yes, it is a supported feature, but our documentation about scheduling config policy is not adequate, unfortunately.
The built-in predicates do not take parameters. You can only add/remove predicates in the config file/configmap.

@bsalamat
Any plans for this in 1.11?
If so, can you please ensure the feature is up-to-date with the appropriate:

Description
Milestone
Assignee(s)
Labels:

stage/{alpha,beta,stable}
sig/*
kind/feature

cc @idvoretskyi

@justaugustus
This is already implemented. There is a part of this that require scheduler to watch the ConfigMap and restart itself when a change is observed, but there is no plan to add the auto-restart.

Sounds good, I'll close this out!
/close


Assessment of the difficulty in porting CPU architecture for SDL-mixer

Hello everyone! I am working on implementing a tool to assess the complexity of CPU architecture porting. It primarily focuses on RISC-V architecture porting. In fact, the tool may have an average estimate of various architecture porting efforts.My focus is on the overall workload and difficulty of transplantation in the past and future,even if a project has already been ported.As part of my dataset, I have collected the SDL-mixer project. I would like to gather community opinions to support my assessment. I appreciate your help and response! Based on scanning tools, the porting complexity is determined to be  simple, with a small amount of code related to the CPU architecture in the project.  Is this assessment accurate?Do you have any opinions on personnel allocation and consumption time？ I look forward to your help and response.

Correct, SDL_mixer is written in very portable C: it runs on many architectures unmodified.
@wangyuliu
Can you please stop sending these automated messages? They are very similar to spam. The issue tracker is for issues. For questions and/or discussions, use the discourse server instead.


[SIL] Key consume addr checking off var_decl attr.

Previously, the lexical attribute on alloc_stack instructions was used. This doesn't work for values without lexical lifetimes which are consumed, e.g. stdlib CoW types.  Here, the new var_decl attribute on alloc_stack is keyed off of instead.  This flag encodes exactly that a value corresponds to a source-level VarDecl, which is the condition under which checking needs to run.

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please apple silicon benchmark

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please apple silicon benchmark

@swift-ci please test

@swift-ci please test macos platform


New subsegments within Lambda set parent segment as last subsegment, even after subsegment has called end()

From within an xray-enabled lambda function, I create and send subsegments like this:
records.stream().forEach(item -> {
  Subsegment apiRequestSS = xrayRecorder.beginSubsegment("API_REQUEST_SUBSEGMENT");
    try {
      // do something
    } finally {
      apiRequestSS.close();
      xrayRecorder.sendSubsegment(apiRequestSS);
    }

The problem is that these subsegments seem to be nested inside each other. This seems counterintuitive to me - I would expect each of the subsegments to reference the top-level segment, since I am closing the newly created subsegment upon every iteration. The result of the trace looks a bit like this:

Is this a feature or a bug? If it is a feature, this nesting was not quite clear from the documentation.
Thanks!

Closing - my code was nesting segments as a result of user error. Using close() to end the subsegment, followed by sending the subsegment, resulted in a non-nested structure


[PROJECT ADDITION]- PCOS DETECTION

Polycystic Ovary Syndrome (PCOS) is a hormonal imbalance affecting women of childbearing age. Early detection is crucial for proper management. Machine learning offers a promising approach to aid in PCOS diagnosis.
The project's core is a well-structured dataset containing patient information relevant to PCOS diagnosis. This data might include:
Demographic details (age, weight, etc.)
Medical history (menstrual irregularities, acne, etc.)
Lab test results (hormone levels, ultrasound findings)
I will take the dataset from Kaggle and prepare a model for it . I will create a separate folder named as the Project Title.
Inside that folder, there will be four main components.
Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.
Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.
@abhisheks008 please assign me this project .

@abhisheks008 please assign me the project

Which models are you planning to implement?
@payalsinha12

i will implement a model using different classifiers which will helps a person to determine that she was suffering from pcos or not after preparation of model if someone wants to use frontend and backend for it they can @abhisheks008

Use these models for your project,

Random Forest
Decision Tree
Logistic Regression
XGBoost
Lasso
Ridge
Gradient Boosting
KNN
Naive Bayes
MLP Classifier

Assigned @payalsinha12


Update backup-sql-server-database-azure-vms.md

Updating notes around proxy config for the Azure Backup rules to clarify how to properly configure proxy devices for use, as most proxy devices use domain wild cards for whitelist, there are none for Azure Backup services, and you will need to rely on uploading the IP address ranges for whitelist.

@supmn084 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Increment version for core releases

Increment package version after release of azure-core-amqp

/azp run cpp - core - ci


Help: Manually committing offset while using ConsumerGroup

I have been trying to do the same thing, I have referenced a similar issue https://github.com/SOHU-Co/kafka-node/issues/502 but couldn't see a clear answer.
I have a consumerGroup,
I have configured it with autoCommit: false
To manually commit the offset I had to use consumer.client.sendOffsetCommitV2Request(...)
Is this correct?
I couldn't get it to work using any other methods,
did I miss something?

My advice referenced in the previous thread still stands.
You should be able to manually commit by calling autoCommit or the alias of it commit.
consumerGroup.commit(true, callback);

I'm a little confused here.
We only use ConsumerGroup's, and we are running with v0.10 brokers.
Previously, our ConsumerGroup's were using the Client object and were manually committing by calling Client.sendOffsetCommitV2Request.
We have switched to using the new KafkaClient (by setting the kafkaHost on the options) with our ConsumerGroup's, and we continue to manually commit by calling Client.sendOffsetCommitV2Request (because KafkaClient inherits from Client).
Above, you suggest calling autoCommit/commit (on HighLevelConsumer because ConsumerGroup inherits from HighLevelConsumer), but that still ends-up calling Client.sendOffsetCommitRequest and not Client.sendOffsetCommitV2Request.
We use V2 because there were issues with V0 which we did not have with V2 (I don't recall what they were, but they were critical).
Is there any reason for us to stop using V2?

This should continue to work since we override sendOffsetCommitRequest method to call the correct commit version in the client.
If possible you should avoid interacting with the client that lives inside the ConsumerGroup in case this changes in the future.
I plan on adding better support for manual commits in the future since it's frequently requested.

Ah, yes, I see.  I'll try switching to use ConsumerGroup.commit and see if that doesn't work for us.


spreadsheetView.dataSource = self crashing

Expected Behavior
Actual Behavior
Steps to Reproduce the Problem

Specifications

Xcode version: ?
iOS version: ?
Dependency manager + version: ?

@IBOutlet weak var spreadsheetView: SpreadsheetView! (taken outlet - used UIView)
spreadsheetView.dataSource = self.   - crashing
spreadsheetView.delegate = self
why it is not initialise.

Expected Behavior
Actual Behavior
Steps to Reproduce the Problem
Specifications

Xcode version: ?
iOS version: ?
Dependency manager + version: ?

For those developers that encounter this crash, the solution is below:

On the storyboard click on your SpreadsheetView
On the right panel select "Identity Inspector"
Under 'Custom Class' set the Module to SpreadsheetView and not to your target.
(in case you didn't set it the view should be a SpreadsheetView class (also under 'Custom Class'))


Question about Circuit.ToJSON() output when overrides to LineCode, XfmrCode, or other codes exist for a component

In an OpenDSS file, an entry for a new line, transformer, or other component can reference a code (e.g., a LineCode) and then override values in the code by specifying new values in the definition of the component, after reference to the code. For example:
New Line.lineA .... Linecode=LineCodeB, EmergAmps= 410
In this example, the line's EmergAmps value will be 410, regardless of what LineCodeB specifies. My question is, can I trust that the output of Circuit.ToJSON() will always capture any overridden code values for a component?
In the given example, this would mean that the JSON output for a line specified as:
New Line.lineA .... EmergAmps= 410, Linecode=LineCodeB
would reflect the value of EmergAmps as given in LineCodeB, and the one used in any analysis by OpenDssDirect. I just want to verify that this is the way the ToJson function works and the way the JSON schema is used, for any component.

My question is, can I trust that the output of Circuit.ToJSON() will always capture any overridden code values for a component?

Kinda: if the values are present, they should be ones from the LineCode, but it also omits previously set values.
When you set LineCode=..., it replaces most of the current values in the Line. A lot of properties are marked as unset when you specify a LineCode, e.g. if you previously provided R1 and X1 (or a Geometry and Spacing pair), they should be omitted from the output (either JSON or DSS code from the Circuit.Save() function) in the default settings (without the compatibility flag NoPropertyTracking).
For New Line.lineA .... EmergAmps= 410, Linecode=LineCodeB, it should list the value copied from LineCodeB, currently.
I made a note to check if we can omit EmergAmps (also NormAmps and Ratings) from the output in this case (IIRC, there was a specific detail about this).
Note that FaultRate, pctPerm, and Repair are not copied from the LineCode. Just right now, I marked those as deprecated and unused. Pre-2014 versions of OpenDSS copied those values from the LineCode to the lines, but they are not used anywhere since then (i.e., users need to provide those values individually on each Line).
Most of these changes I'm mentioning should be included in the next release in the next few days and should be reflected later in the docs in our site. I wasn't expecting the release of OpenDSS v<IP_ADDRESS>, so now I'm finishing porting the new code, especially the new WindGen. We do a lot of refactoring and cleaning up while porting.


Provide ability to find which subcommand threw a ParameterException

If a command has multiple subcommands, and if the parse method threw a ParameterException, it is not possible to find out which subcommand threw the exception. This means it is not possible to give specific usage help feedback to the user on how the subcommand should be used correctly.
Solution: add method ParameterException::getCommandLine that returns the (sub)command that threw the exception. Client code could look like this:
CommandLine top = new CommandLine(new MyApp());
try {
    List<CommandLine> parsedCommands = top.parse(args);
    // ... do something with the parsed commands
} catch (ParameterException ex) { // incorrect user input for one of the subcommands
    out.println(ex.getMessage());
    ex.getCommandLine().usage(out); // get the offended subcommand from the exception
}

To implement this, change the ParameterException constructor (and similar for all subclasses) to add a required CommandLine parameter.
Note to self: the ParameterException hierarchy needs to be refactored. Exceptions thrown from the CommandLine constructor should not extend from ParameterException. Let's introduce a new ConfigurationException (extends RuntimeException) to indicate a CommandLine could not be constructed. DuplicateOptionAnnotationException and ParameterIndexGapException should extend this new exception. CommandLine constructor code throwing IllegalArgumentException and IllegalStateException should throw a ConfigurationException instead.
The remaining exceptions can extend ParameterException, and CommandLine can be a mandatory ParameterException constructor parameter.
These are breaking API changes, so require a major version increment.

This has been implemented and pushed to master.


More pointers

Pass pointers further down to TakeSingleHeader.
Replace span.Slice with new Span<byte> to avoid bounds checks

dev

Method
Mean
StdErr
StdDev
Scaled
Scaled-StdDev
RPS
Gen 0
Allocated

ParsePlaintextTechEmpower
2.6467 us
0.0223 us
0.1223 us
1.00
0.00
377,835.86
-
350 B

ParsePipelinedPlaintextTechEmpower
2.6323 us
0.0193 us
0.1059 us
1.00
0.06
379,891.41
-
350 B

ParseLiveAspNet
6.2356 us
0.0924 us
0.5062 us
2.36
0.22
160,369.65
-
1.12 kB

ParsePipelinedLiveAspNet
7.6393 us
0.0600 us
0.3286 us
2.89
0.18
130,902.06
-
1.12 kB

ParseUnicode
12.3045 us
0.0978 us
0.5355 us
4.66
0.29
81,270.87
-
1.97 kB

ParseUnicodePipelined
15.2304 us
0.0564 us
0.3091 us
5.77
0.28
65,658.24
0.0099
1.97 kB

davidfowl/more-pointers

Method
Mean
StdErr
StdDev
Scaled
Scaled-StdDev
RPS
Gen 0
Allocated

ParsePlaintextTechEmpower
2.5530 us
0.0094 us
0.0514 us
1.00
0.00
391,694.37
-
350 B

ParsePipelinedPlaintextTechEmpower
2.6083 us
0.0252 us
0.1378 us
1.02
0.06
383,386.03
-
350 B

ParseLiveAspNet
6.1137 us
0.0688 us
0.3770 us
2.40
0.15
163,567.54
-
1.12 kB

ParsePipelinedLiveAspNet
7.5028 us
0.0339 us
0.1855 us
2.94
0.09
133,283.91
-
1.12 kB

ParseUnicode
12.1608 us
0.0579 us
0.3170 us
4.77
0.15
82,231.66
-
1.97 kB

ParseUnicodePipelined
14.9371 us
0.0709 us
0.3883 us
5.85
0.19
66,947.58
0.0137
1.97 kB

PS: After adding those headers to the micro benchmarks, things look worse for pipelining in general (not sure why).

I have a change the supersedes this

How has the allocations for plaintext gone up to 350 B? Was 105 B before wasn't it?

@benaadams different machines? Not sure, we need to see.

Having a dig

@benaadams the benchmarks changed. We have more headers now


*: let patrol region tick interval configurable

PTAL

/run-all-tests tidb=release-2.0 tikv=release-2.0 tidb-test=release-2.0

CI failure not related. I'm going ignore it.


error Command "identity" not found.

yarn identity create # yarn identity create to create a network identity for your Hub
yarn run v1.22.19
error Command "identity" not found.

are you executing this from the apps/hubble folder?

are you executing this from the apps/hubble folder?

Yeah, I didn't go into apps/hubble folder.
And I think we should update the README.md.
cd apps/hubble Navigate to this folder from the root

supportive of the change, lets close this issue for now


General type inference and type checking for transformation patterns

In legalize.py and other places, we define transformation patterns like this:
# Expansions for immediates that are too large.
expand.legalize(
        a << iadd_imm(x, y),
        Rtl(
            a1 << iconst(y),
            a << iadd(x, a1)
        ))

Each transformation pattern is represented by the XForm class defined in meta/cdsl/xform.py.
We need a general type inference and type checking system for these patterns that uses the type constraints specified through type variables in the instruction definitions. The type inference is used to:

Infer the types of temporary symbols such as a1 in the output pattern above. The generated transformation code can't always depend on the simple forward type inference that many InstBuilder methods support.
Detect cases where the types of temporary symbols in the output can't be inferred from the types available in the input pattern and issue an error.
Verify ahead of time that the type constraints make sense, and we won't generate code that doesn't verify.
Inform the generation of test cases for an SMT solver. At some point we want to use z3 or another SMT solver to verify each transformation pattern. Since SMT solvers don't accept polymorphic problems, we need to select valid types for the symbols used in a pattern, or possible enumerate all valid type combinations to generate test cases.
Detect cases where a transformation only applies to a subset of the types that the input pattern can represent. This leads to additional preconditions to be checked before applying a pattern.

We currently have a type inference implementation that:

Assigns a type variable to every symbol used in the pattern. These variable can be free or derived from other type variables.
Collects a list of free type variables.
Complains of any of the free type variables are associated with a temporary symbol which only appears in the output.

The current implementation does not compute strict type sets for each type variable, and it is not clear that it can always determine a way of computing the type of a temporary symbol.
Free type variables
A general implementation of the type inference should first compute a set of free type variables, such that the type of every symbol can be computed as a function of these variables.
The type constraints imposed by the instructions in the pattern can be represented as a set of triples:
(Var, Func, Var)

Here, Var is a symbol in the pattern, and Func is one of the type variable functions listed in the TypeVar class. The meaning of a tuple (a, f, b) is the constraint that typeof(a).f() == typeof(b). The function can be TypeVar.SAMEAS to require a and b to be of the same type.
The set of tuples can also be seen as a labeled, directional graph where the nodes are symbols and the labeled edges are constraints. We need to prove that every temporary symbol (i.e., one that appears only in the output pattern) can be reached from a symbol that appears in the input pattern.
Determine a root set of free variables such that the entire graph can be reached for that root set. The set doesn't have to be minimal, but smaller is better.
If the root set can consist of mutually independent type variables, even better. This would make it much easier to enumerate all the possible type combinations for an SMT solver.
Type sets
In the instruction definitions, every type variable has an associated set of allowed types. We should compute the corresponding type sets for the free pattern type variables.
The current implementation is incomplete. It doesn't do anything with type variable functions.

@d1m0, is this complete now?

This is all done except for:

Detect cases where a transformation only applies to a subset of the types that the input pattern can represent. This leads to additional preconditions to be checked before applying a pattern.

I think PR #112 addresses this, but you should confirm that.

With the merge of #112 I think this can be closed.


[Question] distiluse-base-multilingual-cased-v2 - wrong vector dimension (768 vs 512) in onnx version?

I was just playing around with the model distiluse-base-multilingual-cased-v2 and noticed that your onnx versions both (quantized and normal) produce embeddings with 768-dimensional vectors instead of 512.
Example:
index.html
<!DOCTYPE html>

    <title>Transformers.js Example</title>

Transformers.js Example

main.js
import { pipeline } from 'https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>
async function allocatePipeline() {
  let pipe = await pipeline("feature-extraction",
                             "Xenova/distiluse-base-multilingual-cased-v2");
  let out = await await pipe("test", { pooling: 'mean', normalize: true });
  console.log(out);
}
allocatePipeline();

That gives me
Proxy(s) {dims: Array(2), type: 'float32', data: Float32Array(768), size: 768}

However, the model page states

This is a sentence-transformers model: It maps sentences & paragraphs to a 512 dimensional dense vector space and can be used for tasks like clustering or semantic search.

Also, I used the Python package
from sentence_transformers import SentenceTransformer
model = SentenceTransformer('sentence-transformers/distiluse-base-multilingual-cased-v2')
model.encode("test")

which gives me a correct 512-dimensional embedding.
Am I missing some option here or overseeing the obvious?

Here's the model architecture according to their README:

SentenceTransformer(
  (0): Transformer({'max_seq_length': 128, 'do_lower_case': False}) with Transformer model: DistilBertModel
  (1): Pooling({'word_embedding_dimension': 768, 'pooling_mode_cls_token': False, 'pooling_mode_mean_tokens': True, 'pooling_mode_max_tokens': False, 'pooling_mode_mean_sqrt_len_tokens': False})
  (2): Dense({'in_features': 768, 'out_features': 512, 'bias': True, 'activation_function': 'torch.nn.modules.activation.Tanh'})
)

It would appear as though they store the final "dense" layer in a separate folder (https://huggingface.co/sentence-transformers/distiluse-base-multilingual-cased-v2/tree/main/2_Dense) and the model was only converted from the pytorch_model.bin in the root directory.
If you try using the HF transformers python library (not sbert), you should also get 768 dimensions, simply because it doesn't know of the existence of the final dense layer.

Thanks for your answer!
You're right with transformers library in Python, it returns a 768 dimensional vector too.
from transformers import AutoModel, AutoTokenizer
import torch

model_name = "sentence-transformers/distiluse-base-multilingual-cased-v2"
model = AutoModel.from_pretrained(model_name)
tokenizer = AutoTokenizer.from_pretrained(model_name)

inputs = tokenizer("Hello, my dog is cute", return_tensors="pt")
outputs = model(**inputs)

sentence_embedding = outputs[0][0][0]

len(sentence_embedding)
#768

or simply
from transformers import pipeline
pipe = pipeline('feature-extraction', model= "sentence-transformers/distiluse-base-multilingual-cased-v2")
out = pipe('I love transformers!')
len(out[0][0])
#768

where the first tensor ([CLS]) should be the sentence embedding (afaik) according to the BERT paper (right?).
I suppose the dense layer in the sentence transformer models serves only for shortening the tensors and saving memory. It's certainly a nice banana skin to slip over. :D
Are you aware of any way to add the dense layer to the onnx.model so I could create it once for my purpose? I want to avoid loading two models and piping data around.
Also (for anyone reading this in the future), I am not aware of any parameter to ignore the dense layer in sentence transformer  models.


[BUG] Most fluids don't render in fluid containers on "Fabulous!" graphics

Description:
Whenever any fluid is put inside a Tank or a Pump, it does not render. The issue doesn't happen with lava.
The issue also doesn't happen on mod version 1.10.0-alpha.12.
Steps to Reproduce:

Place a Tank down
Insert any fluid in it (except for lava) by any means (buckets, pumps etc.)

Technical Information:

Minecraft: 1.17.1
Fabric API: 0.40.8
Industrial Revolution: 1.11.0-alpha.2
Modpack: none

Logs:
latest.log
Details:
1.11.0-alpha.2

1.10.0-alpha.12

Tested other industrial mods (Modern Industrialization, Tech Reborn), the issue happens with all of them. Mentioning this in case it helps identify the issue. Tested all mods separately to exclude the possibility of an incompatibility between them.
I figured out the issue, it only happens of "Fabulous!" graphics settings.

Closing this as I'm not playing on 1.17 anymore and I have no idea if the issue is still present on 1.18.x. Also MI devs said the "Fabulous!" preset is problematic in general for mods anyway.


Nisse Engström: Watch asphelponline.com

Nisse Engström requests the watch of the watch_keyword asphelponline.com. See the Metasmoke search here and the Stack Exchange search here.

Coverage remained the same at 63.155% when pulling d7e6e496582d80012011de80a6068fd41f915d20 on auto-blacklist-1512646045.1368039 into 70bce3227eff2f73abd30d2695d658a499731bbb on master.

!!/approve


Issue-12884: Fix Test Case Summary Performance Issues

Describe your changes:
Fixes #12884
Implement logic to store and compute test case summary from testSuite

Type of change:

[ ] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My PR title is Fixes <issue-number>: <short explanation>
[x] I have commented on my code, particularly in hard-to-understand areas.
[x] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[x] I have added tests around the new logic.
[x] For connector/ingestion changes: I updated the documentation.

@TeddyCr do we need to run any migrations to get the existing summary or should we let the next run pick it up

@TeddyCr do we need to run any migrations to get the existing summary or should we let the next run pick it up

@harshach to me the safest would be to let the next run pick up the summary. wdyt?


python312Packages.prometheus-fastapi-instrumentator: init at 7.0.0

Description of changes
Add Prometheus FastAPI instrumentator.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1761


ortools_vendor: 9.9.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository ortools_vendor to 9.9.0-1:

upstream repository: https://github.com/Fields2Cover/ortools_vendor
release repository: https://github.com/Fields2Cover/ortools_vendor-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: null

https://github.com/ros/rosdistro/pull/40527#issuecomment-2046224920

Hi @mjcarroll, it should be fixed now :) Thank you


Need help building kernel headers for HP 13 to install virtualbox

name: trusty
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/trusty...
crouton: version 1-20160627183059~master:e3c0a690
release: trusty
architecture: amd64
xmethod: xiwi
targets: xfce,xiwi
host: version 8172.60.0 (Official Build) stable-channel chell
kernel: Linux localhost 3.18.0-11125-g013294a #1 SMP PREEMPT Thu Jun 23 04:33:37 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes```

#### Please describe your issue:

I am the owner of a shiny new HP Chromebook 13 m5 version, and I am so far quite happy.
I am now trying to install virtualbox to run one critical windows only program that I absolutely need.
I previously had an original Pixel so was able to use divx118 prebuilt kernel header packages and virtualbox was a breeze to install.

The HP 13's kernel is 3.18.0 so it looks like I have to build my own.

I followed the guide here using the 3.18 branch: https://github.com/dnschneid/crouton/wiki/Build-kernel-headers-and-install-Virtualbox-(x86)

Doing that produces two .deb files named:
linux-headers-3.18.0-12563-g8e79f0d-dirty_3.18.0-12563-g8e79f0d-dirty-10.00.Custom_amd64.deb

linux-image-3.18.0-12563-g8e79f0d-dirty_3.18.0-12563-g8e79f0d-dirty-10.00.Custom_amd64.deb

Installing these does not quite work  -- my kernel version is 3.18.0-11125-g013294a when I do uname -r, so virtualbox still complains that I don't have the correct headers. I tried just setting dkms --kernelsourcedir to the headers I built and installed but no dice.

So where do I go from here? Did I build kernel headers for the wrong version? How do I do it for my version? Or do I just have to rename/force virtualbox to use the version I built

Thanks for the help!

Sorry no solution yet. This is a duplicate of #2642 please close this one and continue discussion at #2642. Thanks.


Make an in-page widget for feedback

While https://github.com/SuffolkLITLab/docassemble-GithubFeedbackForm is useful, to try to get a stronger feedback stream, we can reduce the friction people run into when dealing with feedback.
The prototype idea is to have a thumbs-up / thumbs-down option that when clicked on, sends the feedback to the server, and swaps the thumbs for a "would you like to make an anonymous review", along with a text input.

Despite conversations on Monday about this being in the Toolkit, I don't think it belongs, since there will be a lot of shared code between this feature and features already in GithubFeedbackForm (we can't and shouldn't depend on that package in here, as it will be a circular dependency), and arguably this feature requires several other tightly knit features (to view the feedback data mostly), which isn't a good fit for ALToolbox IMO.
Gonna transfer this issue to GithubFeedbackForm.


Drag and dropping a tab without moving it from it's original position creates a new window instance

Description
https://user-images.githubusercontent.com/9108903/130522933-d9d7a8c3-c739-4af4-93b0-b18a8e1f166e.mp4
When attempting a drag and drop operation on a window tab, if it is barely moved or only moved to within it's original position on the tab bar, it is removed from the tab bar and spawns a new window.
Steps To Reproduce

Create more than one tab (can be more than two).
Attempt to drag and drop the tab without moving it out of it's rough original position.

Expected behavior
Unless deliberately moved out of position, the tab should have remained in it's position when the mouse click is released and not spawned a new window.
Files Version
Version: <IP_ADDRESS>
Windows Version
Windows 11 Pro 21H2 22000.160
Relevant Assets
No response

Merging with #8976
This seem like it's cause by the title bar having a small area to drag the tab into for window merging.


Tagged releases?

Hello,
The README mentions versions (at least v1.0.0 for now); would it be possible to have git tags as well? GitHub automatically generates tarballs for tagged versions, allowing anyone to download e.g. termbox 1.0.0 with an URL like https://github.com/nsf/termbox/archive/v1.0.0.tar.gz.
Thanks!

Yeah sure, I'll tag it today or tomorrow.

https://github.com/nsf/termbox/tree/v1.0.0
https://github.com/nsf/termbox/tree/v1.1.0
Tags are here now, and 1.1.0 was kind of released, but I wouldn't make a big deal out of it. It's just here to mark some progress.

Thanks!


Better orderbutton dimensions

The iframe container for orderbutton are set on 100% height.
On most cases this is too much for any page rendering because will fail in 2 scroll bars on page. One for iframe and one for the page itself.
A better setup is to put a limit of 80%.
/bb-modules/Orderbutton/html_client/mod_orderbutton_js.phtml
on line 98 change the value:
this.style.height = '80%';

Hello,
Thanks for suggestion.
Can you attach a screenshot of two scroll bars?
how 80% value will help if windows is very narrow and product list is long?

This will be fixed in next BoxBilling release


Remove official docker images & move testing images to test folder

Proposed changes
Removed official docker images from scripts folder
Moved test images from scripts folder to test folder
Removed official docker image make targets
Should be merged after https://github.com/nginx/agent/pull/827
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[ ] I have read the CONTRIBUTING document
[ ] I have run make install-tools and have attached any dependency changes to this pull request
[ ] If applicable, I have added tests that prove my fix is effective or that my feature works
[ ] If applicable, I have checked that any relevant tests pass after adding my changes
[ ] If applicable, I have updated any relevant documentation (README.md)
[ ] If applicable, I have tested my cross-platform changes on Ubuntu 22, Redhat 8, SUSE 15 and FreeBSD 13

🎉 Thank you for your contribution! It appears you have not yet signed the F5 Contributor License Agreement (CLA), which is required for your changes to be incorporated into an F5 Open Source Software (OSS) project. Please kindly read the F5 CLA and reply on a new comment with the following text to agree:
I have hereby read the F5 CLA and agree to its terms
You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

I have hereby read the F5 CLA and agree to its terms

recheck

@nginx-seanmoloney do we need a release note for this?


Json marshalling is needed for Rest route and uncommented code seems to be executed

I've applied the camel rest dsl example here for the Camel K, the simple integration file is as follows, which fails;
import org.apache.camel.builder.RouteBuilder;

public class RestRoute extends RouteBuilder {

    @Override
    public void configure() throws Exception {

        // rest endpoints
        rest("/status")
            .get("/hello").to("direct:hello");

        // routes
        from("direct:hello")
            .transform().constant("Hello World");

    }

}

However, if I add marshal().json() line to the route, it works;
import org.apache.camel.builder.RouteBuilder;

public class RestRoute extends RouteBuilder {

    @Override
    public void configure() throws Exception {

        // rest endpoints
        rest("/status")
            .get("/hello").to("direct:hello");

        // routes
        from("direct:hello")
            .transform().constant("Hello World")
            .marshal().json();

    }

}

And even if I comment out the marshal().json() line, it continues to work;
import org.apache.camel.builder.RouteBuilder;

public class RestRoute extends RouteBuilder {

    @Override
    public void configure() throws Exception {

        // rest endpoints
        rest("/status")
            .get("/hello").to("direct:hello");

        // routes
        from("direct:hello")
            .transform().constant("Hello World")
            //.marshal().json();

    }

}

Is there a problem with this example, or the code I've shared, or is this a bug?
I've also asked this on stackoverflow but I suspect that it may be a bug;
https://stackoverflow.com/questions/67731034/camel-k-rest-route-needs-json-marshalling-and-commented-code-executed

I'm attaching the terminal output and the operator logs here.
Terminal output that includes the output of the kamel --dev mode;
Terminal Output
Camel K Operator logs taken from the MiniKube;
Camel K Operator logs

I tried to run the same example but it is working for me.
I suspect there is an issue with pulling the base image for the kit, can you try to delete all the kits ?
kubectl delete integrationkits --all


mailcatcher run in foreground mode

This version operates mailcatcher in foreground mode only.

As there is no impact on performance this will remain the case for the time being


decoder and encoder model

Hey!
nice code man!
Can you reproduce the results of the original code? If I understand correctly you only implemented the encoder side?
Best,
Luca

Not sure if this only an encoder, a decoder, or both, but there's an option for masking, so I'm assuming it's a decoder or the full transformer.

You can create the encoder/decoder as you wish. TransformerBody however, is an encoder. The wikitext example in this repo seems to be a universal transformer (a single TransformerBody is called multiple times, not stacked like plain transformer). I have tried building an encoder that has masking enabled (masking is originally enabled in the decoder).


overview: Section 6

I went through Section 6. It also displays what I think we should do. In particular:

I moved stuff around a bit, to improve consistency
I split a couple of items
when an item has several targets but finding one tells you about the other, I didn't split, and indicated where to find one target. For instance, "Circular trigonometric function" links to the definition of sin. I did split circular and hyperbolic, especially since we don't have reciprocals hyperbolic trig functions
When we can obviously express something but the definitions is not there, I didn't write anything. I think we should add those definitions to mathlib, in particular for the sake of discoverability. For instance we don't have convergent series of real numbers.

What I think I have a hard time to do is being consistent about the following question: what do we do when we have a very general form of something, but we would need an API for the elementary version? For instance I resisted the temptation to write that we have Taylor series. We have them in several variables. But since we have the deriv vs fderiv distinction, I say we don't have Taylor series in one variable.

In my PR I didn't split "Z/nZ and its units" but linked to a theorem about a : zmod n being a unit iff a is coprime to n. This way, people can still easily discover zmod n. But of course we could simply add an entry for zmod.


Moving away from new Buffer(...)

new Buffer(...) is deprecated and unsafe. Would it be possible to replace its usage with Buffer.from(...)?

yeah we should switch over to safe-buffer


WIP: fix panic

When restic is unable to read an extended attribute (e.g. the FS does not support it, but still returns the attribute as available for a file), continue instead of returning the error.  Files in /sys do this sometimes.
Closes #811

Codecov Report

Merging #809 into master will decrease coverage by -0.05%.
The diff coverage is 24%.

@@            Coverage Diff             @@
##           master     #809      +/-   ##
==========================================
- Coverage   53.61%   53.56%   -0.05%
==========================================
  Files          97       97
  Lines        7491     7495       +4
==========================================
- Hits         4016     4015       -1
- Misses       2883     2887       +4
- Partials      592      593       +1

Impacted Files
Coverage Δ

src/restic/node_xattr.go
20% <22.22%> (ø)
:white_check_mark:

src/restic/node.go
35.61% <25%> (-0.68%)
:x:

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 0674f32...132afbe. Read the comment docs.


feat: update setup.py, removal of urllib3 module version upper boundary requirement [APE-1610]

Update setup.py - removal of urllib3 module version requirement
What I did

fixes: #1741
How I did it

Updated setup.py by removal of urllib3 module version upper boundary requirement
How to verify it

Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

Can you give a quick explanation why the library pin is troublesome?

Can you give a quick explanation why the library pin is troublesome?

Hey, thanks for looking into this. As ape is not using urllib heavily I think it's safe to remove the upper bound as it creates conflicts with other libraries that depend on specific versions of urllib.

We could also bump it completely to the 2.0 range, as we are about to do big breaking change release


Tutorial map for arrivals

For new players we want a short tutorial map to replace arrivals. Basically a wrapping hallway in arrivals that has text and arrows on the ground to direct new players and tell them the controls.
This is going to be in addition to the onboarding UI #28616  #28618, so the map doesn't have to teach everything, but having both will help grab more attention and leave less new players confused.
Probably needs ideas on what exactly to show. This is a stripped down list from #28618.
Step 1:

[ ] Explain the movement controls. (Show button prompts/description: move around, explain that you can't rotate the screen)

Step 2:

[ ] Explain hands and swapping hands
[ ] Explain the importance of E for interaction/using
[ ] Explain pockets/Slots
[ ] Move PDA into hands
[ ] Interact with PDA (explain item status)
[ ] Explain item usage

Step 3:

[ ] Toggle flashlight on and off (Toggle actions)
[ ] Have the player Scream (Explain do-afters/timed actions)
[ ] Explain Combat mode and switch to it
[ ] Ask the player to perform an attack
[ ] Have the player switch out of combat mode

Step 4 ((If the player is a mid-round join, and not already on the station):

[ ] Guide the player to the shuttle

Optional:
The map should allow experienced players to bypass the tutorial section by going through a door, but the tutorial should be eye catching enough that new players walk that way.

Hello I am doing the coding part of this

TECHNICAL TASKS
[] Map Invincibility -
A map where everything is invincible, and even mobs cannot be harmed. This is a map setting, used for "safe spaces" like a tutorial area. This is not specifically a new player experience feature; it's just a setting a map has.
[] Tutorial Game Mode -
A mode where everyone must spawn on the Departure Terminal, which is converted to a special Tutorial Departure Terminal. This terminal should have map invincibility.
[] Reverse Panic Bunker
A panic bunker which filters by maximum playtime not minimum playtime. It can be circumvented by whitelisted players and admins.

Let me know when this is in and I'll setup hooks for the onboarding system, that way the UI highlights and onboarding flow can match up nicely with the tutorial :)

Baby jail covers the cvars needed to tune who exactly can join the server

shuttle.arrivals_map works for setting what map the departure terminal should use

I am Urist McShitter, 12 years old I see cool video game I download game I create account?
I pick... Scug, the Gateway (newbie) server. It is the start of the round.
Everyone starts at Departure Terminal. This Departure Terminal is a "tutorial" area. It's a basic "walk through this and look at the signs" tutorial, nothing fancy. Everyone has to rush through to get to the shuttle.
Urist McShitter reads the tutorial steps and gets the basic idea of the controls. They are encouraged to open their guidebook and read more. They get on the shuttle and go to the station.
Once getting off at the station they encounter peak unadulterated, heavily-adminned shithousery, because it's sixty greytiders loose in an empty space station Utter, total chaos.
After one hour of playtime, Urist Mcshitter is released from baby jail and can play on real servers.
Server stats
20 TPS 60 pop Tutorial only Access special rule: Only brand new players and whitelisted players (use the MRP whitelist for the time being) can join. After ten hours on Wizden servers you cannot connect and you must move on to real, hardcore Space Station 14 gameplay unless you are whitelisted or an admin.
New game mode: Tutorial Tutorial works like Greenshift except:
1. Everyone spawns at the departure terminal

2. The departure terminal is in tutorial mode

This terminal is indestructable, nobody can be hurt whilst they're on it, and it has no spawnable items.

i thought the reason for going with a UI onboarding system and a light tutorial was to reduce the sort of "tutorial period." It's kinda unreasonable to force people to play through an hour long extended tutorial especially with the implication that it isn't going to reasonably resemble a normal round in any way.

i thought the reason for going with a UI onboarding system and a light tutorial was to reduce the sort of "tutorial period." It's kinda unreasonable to force people to play through an hour long extended tutorial especially with the implication that it isn't going to reasonably resemble a normal round in any way.

It's not going to be anywhere near an hour long, at maximum a tutorial section like this would be 5 minutes max. Not to mention that players can simply just run through it to get to the shuttle. Or if you are really worried about that, we can just add a door you need to interact with at the start to skip the tutorial. (Not push to open, require an interaction so that new players don't accidentally skip the tutorial)

I've added a cvar to #28765 to support making folks at departures invincible.

Map invincibility can be done by mappers, although it'd be nice to have code support so it doesn't need snazzy map edits to remove everything on the map being Damageable.
Somebody should get around to making a tutorial-friendly departure terminal map and wiring it in.
My job here is done... I'm gonna go work on the wawas now

Map invincibility can be done by mappers

adding removedComponents: - Damageable to every entity would be complete hell

I'm looking into making a map for this.