Fix out-of-bounds error in atdgen parsers

When running make test in atd, which just switched to yojson 2.0.x, we get an out-of-bounds error on two unit tests:
$ make test
...
> [FAIL]        atdgen         34   test ambiguous record with json adapters.
  [FAIL]        atdgen         35   test wrapping of polymorphic types.
...
┌──────────────────────────────────────────────────────────────────────────────┐
│ [FAIL]        atdgen         34   test ambiguous record with json adapters.  │
└──────────────────────────────────────────────────────────────────────────────┘
[invalid] out-of-bounds substring position or length: string = "ambiguous", requested position = 1, requested length = 9
          Raised at Stdlib.invalid_arg in file "stdlib.ml", line 30, characters 20-45
          Called from Dune__exe__Test_ambiguous_record_j.read_ambiguous.f in file "atdgen/test/test_ambiguous_record_j.ml", line 203, characters 12-156
          Called from Yojson.Safe.map_ident in file "lib/read.ml" (inlined), line 1977, characters 3-43
          Called from Dune__exe__Test_ambiguous_record_j.read_ambiguous in file "atdgen/test/test_ambiguous_record_j.ml", line 225, characters 14-42
          Called from Dune__exe__Test_atdgen_main.test_ambiguous_record in file "atdgen/test/test_atdgen_main.ml", line 579, characters 4-55
          Called from Alcotest_engine__Core.Make.protect_test.(fun) in file "src/alcotest-engine/core.ml", line 180, characters 17-23
          Called from Alcotest_engine__Monad.Identity.catch in file "src/alcotest-engine/monad.ml", line 24, characters 31-35

The problem occurs when parsing unquoted JSON fields, which are supported as an extension of JSON. I believe I fixed the bug, but didn't add a unit test yet because I'm not sure yet where to put it.
To get the detailed error message above, check out https://github.com/ahrefs/atd/pull/310 and run make test.

I'll take a look tomorrow to see if some kind of unit test can be built to exercise this, given it is quite subtle and has not been detected by anything but atdgen. Clearly that part is under-tested.

While figuring out the situation it seems like I broke this in #108 following #85, so I've added a test making sure that the f function gets the right range passed.

I've been wondering whether I can write a test for {foo: null, bar: "hello"} using map_string on "hello", but when I reach the read_space after the bar: applying map_string calls the mapping function with "" 0 0 since it assumes that the opening " of the string is the ending " of the string, so returns the buffer that hasn't accumulated anything.
I am not sure how this API is supposed to be used. The only function I see for reading this is to call start_any_variant to discard the opening " but it feels a bit… wrong. What does atdgen do to map_string?
According to this autogenerated code it does seem to start_any_variant and expect the double-quote constructor?

What does atdgen do to map_string?

It calls it via map_ident. This used to be an optimization that prevented allocating a string for the JSON field name. This is one of the reasons why the Buffer module from the standard library wasn't suitable. See for example this generated code which does the equivalent of
match String.sub s pos len with
| "id" -> 2
...

(returning an int rather than constructing an expression is itself part of an optimization that prevents the creation of a closure)
Now that we use the Buffer module and are forced to allocate a fresh string to hold the substring, the optimization that saved the allocation of the substring is gone and we could simplify the generated code above.
Note that there are other optimizations that make atdgen's code generation more complicated than it could be. I estimate the speedup provided by these optimizations to be about 4x compared to naive implementation. It's something but it's not huge. I think these optimizations are only valuable when dealing with massive amounts of JSON data. I'm open to getting rid of them. Atdgen parsers could work on the Yojson.Safe.t AST instead of calling a bunch of partial parsing functions. This is what we do for the other languages supported by atd (Java, Python, Scala, TypeScript) and used to do with atdgen's predecessor based on camlp4, json-static. It would reduce the maintenance burden of atdgen but also of yojson.

I was just thinking about it the other day - there is a lot of support-code for atdgen that's dealing with the internals of Yojson, which forces us to either keep the implementation fixed to not break atdgen or break atdgen all the time, neither of these options is particularly exciting (that said, there is also not much of a need to change things willy-nilly)
So making atdgen use the Yojson.Safe.t AST might solve this and allow us to concentrate on improving one surface API. But I realize that this might create issues for atdgen users. Unfortunately the slowdown is hard to quantify without... essentially doing the work on the atdgen side. I'll create an RFC to keep track of this and maybe we can come up with another fast API that makes sense for consumers that already know what structure they expect (not only atdgen but also ppx_deriving_yojson and ppx_yojson_conv come to mind).


Unable to change default ports in Unraid install

Hey, just letting you know, despite changing the port from 3000 to 3010 during install since im using 3000 on another app, it seems to have not actually changed it.
Once installed it still tries to use 3000, making my other app inaccessible and also making this one inaccessible.

works just fine...did you change the port after a fresh docker install?


Add a Changelog

Hi, this is a follow-up issue from #3, as I got no feedback on my question there:
Can you please add a Changelog file, or create releases with the respective changes?
It would be nice to have at least a bit of information about what changed between releases.

Hi @diesl,
you are absolutely right.
Future releases will have all changes documented.


Immense game start up delay.

This making me pull my hair out, but something is creating a five to TEN minute delay on start up (before the minecraft window pops up). Disabling this mod removes this delay.
https://paste.ee/p/b5Kzk#s=0&l=323
Line 323 shows the delay.

Unfortunately, I cannot reproduce this. This seems to be a problem involving some other mod in your modpack, as I do not encounter it with just NCR itself. Try to split your modpack in two before you narrow it down to specific mod(s) that are causing this issue when combined with NCR.

Try using smoothboot


load all the required FHIR valuesets as part of the docker setup #66

cc @ashaban

Closing this PR,
change implemented here using an image mainatined by intrahealth


Fix some mypy errors

Part of #217

chore(typing): Use cast() between compatible models for type checker
chore(typing): Re-order get_new_contracts for clarity (and avoid changing types in reassignments)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 7 (28.57%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 86.319%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/sources/colombia.py
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

app/sources/colombia.py
1
72.62%

app/commands.py
3
96.49%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2000

Relevant Lines:
2317

💛  - Coveralls


Pls Help

When i play singleplayer on my world creatures are lvl 50+ but if i invite my friend by LAN creatures are lvl 1 all the time. How can i change that and have high level of creatures on multiplayer?

Did you edit the config? If so, show me your edited lines

Yes i edited it:
"increasingDistance": 2000,
"distanceFactor": 0.75,
"increasingTime": 30,
"timeFactor": 0.1,
"heightDistance": 50,
"heightFactor": 0.05,
"maxFactorHealth": 9.55,
"maxFactorDamage": 7.0,
"maxFactorProtection": 10.0,
"maxFactorSpeed": 2.0,
"allowRandomValues": false,
"randomChance": 10,
"randomFactor": 10,
"extraXp": true,
"maxXPFactor": 5.0,
"startingFactor": 1.0,
"startingDistance": 0,
"startingTime": 0,
"startingHeight": 62,
"positiveHeightIncreasion": true,
"negativeHeightIncreasion": true,
"affectBosses": true,
"excludeDistanceInOtherDimension": true,
"excludeTimeInOtherDimension": true,
"excludeHeightInOtherDimension": true,
"dropMoreLoot": true,
"moreLootChance": 0.02,
"maxLootChance": 0.7,
"chanceForEachItem": 0.5,
"levelZLevelFactor": 0.0,
"levelZPlayerRadius": 0.0,
"hudTesting": false,
"excludedEntity": [],
"allowSpecialZombie": true,
"bigZombieChance": 10,
"bigZombieSlownessFactor": 0.7,
"bigZombieBonusLifePoints": 150,
"bigZombieBonusDamage": 30,
"bigZombieSize": 1.5,
"speedZombieChance": 10,
"speedZombieSpeedFactor": 1.5,
"speedZombieMalusLifePoints": 10,
"dynamicBossModification": true,
"dynamicBossModificator": 0.5,
"bossMaxFactor": 5.0,
"bossDistanceFactor": 0.05,
"bossTimeFactor": 0.0,
"creeperExplosionFactor": 2.0
}

i have the same problem on my server and I hadn't changed a thing

Mh looks good, not sure why it is not working correctly

Come to my discord.


Single Sign-on

'ello
Could you make this work with Single Sign-on please?
Regards
Hein

I assume you are talking about this:
https://docs.microsoft.com/microsoftteams/platform/tabs/how-to/authentication/auth-aad-sso
The reason why I have not yet included that is because of the limitations regarding what permission scopes you get acquire a token for through the SSO authentication for Teams.
However, the workaround for internal applications (which is a very common scenario for developing Teams applications) using admin consent would probably enable you to get whatever permission scopes you need, not only permissions to call Microsoft Graph, but your custom API application as well.
So, I'll evaluate this a bit more and put it on the backlog.

SSO would be a great addition for Teams!
MSAL redirect is not allowed in an IFrame, and a popup to login in Teams, when already logged in, is not that user-friendly. How can we achieve this?

Agreed, I would love to see this as well.

Hi guys and thank you for your comments!
I haven't had the time to do much work on Blazorade Teams for a while. I've also postponed development efforts on it because of the toolkit Microsoft has come out with. I'll have to look into that in more detail before I make any decisions on how to go forward with Blazorade Teams. You can read more about the Teams Toolkit and how to build Teams applications using it in this article.
What comes to SSO, I completely agree with you. I guess I started building authentication support in Blazorade Teams using a wrong approach. I would say, and I hope you can agree, that the majority of Teams applications, at least the ones you would build using Blazorade Teams, are applications build for a single company. In such cases it would not be a problem to create a single-tenant Azure AD application registration and configure the Teams application to use that, so you would not have to use MSAL at all.
I hope I can have a look into the Teams Toolkit in a near future and decide where Blazorade Teams fits into the picture.

In fact, it was not the Teams Toolkit I was referring to, but TeamsFx, which you can read more about on Github.

Thanks for responding Mika.  I've looked at the TeamsFx and one of the problems that I have with it is that they aren't supporting multi-tenant and Blazorade Teams does that quite nicely.  I have a tab application running using Blazorade Teams and it meets all of our needs except for SSO.  In my case I'm not building an application for a single company unfortunately.  We are creating a Teams app for our Cosmos Forms product and need to support multi-tenant for sure.
I totally understand though that given that TeamsFx is coming it may not make much sense for you to duplicate the effort that Microsoft is going through.

@MikaBerglund  I've done some work to add support for SSO, but it doesn't seem like I have permission to create a pull request.  Is that something I need to request from you?


Adapt script to bash version 3

Description
This PR fixes: https://github.com/apache/cloudstack/issues/6060
Bash version 3 does not have support for associative arrays. Hence during the packaging phase the metadata.ini file created (on osx) isn't in proper format as the script used to generate it i.e., templateConfig.sh made use of associative arrays - which is supported from bash v4 onward. This eventually leads failure to deploy DB on OSX.
This PR modifies the script to work on systems using bash v3.

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
Ran the script with bash v3 ( bash -x engine/schema/templateConfig.sh <IP_ADDRESS> )and verified the metadata.ini file

@blueorangutan package

@Pearl1594 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 2793

@blueorangutan test

@rohityadavcloud a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Tested full build, deploydb (against simulator) and UI/dev workflow on osx. With this script, OSX may now be used as a build-dev-test env.

Trillian test result (tid-3525)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37250 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6069-t3525-kvm-centos7.zip
Smoke tests completed. 90 look OK, 2 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_01_vpc_site2site_vpn_multiple_options
Failure
518.53
test_vpc_vpn.py

test_01_invalid_upgrade_kubernetes_cluster
Failure
53.01
test_kubernetes_clusters.py

ContextSuite context=TestKubernetesCluster>:teardown
Error
90.61
test_kubernetes_clusters.py

Failures unrelated.


Use :exception for protect_from_forgery

Why: To better protect the admin interface.

Coverage remained the same at 97.536% when pulling a32d344140d1c119784086c007f3a353e6d187ea on fix-hakiri-warning into 61d7264a2b83a4c8e5708bf9e66955098a851e0e on master.

Coverage remained the same at 97.536% when pulling a32d344140d1c119784086c007f3a353e6d187ea on fix-hakiri-warning into 61d7264a2b83a4c8e5708bf9e66955098a851e0e on master.


New paper page should have text inputs for title, venue, and year

Scenario
When a user visits the new paper page
Then the page should render
Hints
A paper management system manages papers in addition to authors.
Papers should have a 'title' and a 'venue' string as well as a 'year' integer, indicating publishing date.
Papers should be manageable by users using views similar to authors.
Instead of generating the paper model and all the needed controllers and views separately (for new, create, read, update, etc.), use a Rails scaffold.
It generates a model, a database migration, controller and views, and a basic suite:
rails generate scaffold paper title:string venue:string year:integer
Take a look at the generated files and adapt the tests.
The new migrations need to be applied: rails db:migrate RAILS_ENV=development && rails db:migrate RAILS_ENV=test
Error

Got NameError: undefined local variable or method `new_paper_path' for #RSpec::ExampleGroups::NewPaperPage:0x00007fc59c6e5ca8
Did you mean?  new_author_path

19 exercise tests have passed. There are 44 in total. You will solve multiple at once towards the end.

TODO: Adapt all pending tests


Take most up to date duration from playback event.

For some podcasts the itunes:duration tag is not presented in the RSS feed.
This PR takes the duration from the underline player when this data is available.

Hi @roeierez,
I can see where the regression has occurred. In the playMediaItem function within the _DefaultAudioPlayerHandler class I call super.mediaItem.add(mediaItem); at the start of the function, whereas I should be calling super.mediaItem.add(_currentItem); at the end of the function when the duration has been calculated (if it was previously zero).

Fixed as part of the feature/up-next branch and soon to be merged into master.


Comp auto

Added an additional auto mode that doesn't really care about starting position

I have left the old auto modes in because we may want to re-implement them with the new ball positions


Adding support for a 1 digit in 3rd position of CO code for non-geographical area codes in PhoneUS validator

As discussed in a previously closed issue, non-geographical US area codes can have a 1 in the third position of the CO code. The current phoneUS validator does not support this.
For example:
888-511-xxxx (replacing xxxx with some real 4 digit number) is a valid US phone number but not accepted by the validator.

PR with a unit test + fix is welcome


Comment sorting feature in 1.0.20 not persistent after logout/login

Hi,
when you log out and log back into Kanboard the comment sorting is reset.

Yes, at the moment this settings is stored in the user session not in the database.

Available in dev.


NSFS | versioning | Implement list-object-versions

Explain the changes
list-object-versions returns metadata about all versions of the objects in a bucket. You can also use request parameters as selection criteria to return metadata about a subset of all the object versions.
Moved object sorting under .versions to dir_cache
1. Kept 2 seperate cache for list-objects and list_object_versions
2. Sorting of the all entries done in version_dir_cache
3. handled keymarker and versions id marker
4. Added test cases for list object versions

Issues: Fixed #7169
Testing Instructions:

Create few objects and append the same to create versions of the original object
Delete few object
Performat list-object_versions operation. This should returns the metadata of all objects including versions and delete_markers

[ ] Doc added/updated
[x] Tests added

Signed-off-by: Vinayakswami Hariharmath<EMAIL_ADDRESS>

@v-harihar
Hi, wasn't here for a long time, finally, have the chance to review these changes.
I see some missing implementation here - In the design doc, few implementation details were discussed and I can't find them covered by this PR -
Sort  - all keys and within key sort all versions.
New parameters -
version_id_marker - will start listing from that marker
New response fields -
DeleteMarker- will tell if a  version is a delete marker / regular version.
IsLatest - boolean (will be marked when traversing on the real folder/ null for disabled buckets)
VersionIDMarker - string
NextVersionIDMarker - string
Also, we will need relevant unit tests for this to be covered.

@v-harihar Hi, wasn't here for a long time, finally, have the chance to review these changes. I see some missing implementation here - In the design doc, few implementation details were discussed and I can't find them covered by this PR - Sort - all keys and within key sort all versions. New parameters - version_id_marker - will start listing from that marker New response fields - DeleteMarker- will tell if a version is a delete marker / regular version. IsLatest - boolean (will be marked when traversing on the real folder/ null for disabled buckets) VersionIDMarker - string NextVersionIDMarker - string
Also, we will need relevant unit tests for this to be covered.

sure.

Approved but -

Please squash the commits
Please add the gaps in the next pr


stack resolver lts-14.6, GHC 8.6.5

Add dependencies to Test-Suite to make it pass

This won't work until you update the HLint code to use the new API, see https://github.com/gibiansky/IHaskell/issues/1066.

It seems to Work On My Machine and on my branch in Travis.
The test which failed here failed with
[NbConvertApp] ERROR | Kernel died while waiting for execute reply.

Is that an HLint problem?

I would like to rerun that build job, how do I do that in Travis anyway...

Oh I forgot, here's the link to sucessful Travis build of the same commit.
https://travis-ci.org/jamesdbrock/IHaskell/builds/586329058

Oh I don't have the Restart Build button because I don't own the repository. Unless you're sure this in an HLint problem and the build will fail, would you please try the build again @vaibhavsagar ?

Ok build restarted.

Hey it built on the third try. Thoughts? I tried using HLint in a notebook with this build and it seems fine.

Reference: http://hackage.haskell.org/package/hlint-2.2.2/changelog

I also don't like that we're depending on the IHaskell display packages in the test suite, because those packages in turn depend on IHaskell, so there is a cyclic dependency if you need to run the tests for the package build (as Nix does).

Oh. Ok I'll try again without those dependencies.

So without those dependencies for Test-Suite hspec I get a series of errors stack test that looks like:
ihaskell            >   src/tests/IHaskell/Test/Eval.hs:104:5:
ihaskell            >   1) Code Evaluation evaluates expressions
ihaskell            >        uncaught exception: SourceError
ihaskell            >        Could not load module ‘IHaskell.Display.Blaze’
ihaskell            >        It is a member of the hidden package ‘ihaskell-blaze-<IP_ADDRESS>’.
ihaskell            >        You can run ‘:set -package ihaskell-blaze’ to expose it.
ihaskell            >        (Note: this unloads all the modules in the current scope.)
ihaskell            >        Use -v to see a list of the files searched for.
ihaskell            >        Could not load module ‘IHaskell.Display.Aeson’
ihaskell            >        It is a member of the hidden package ‘ihaskell-aeson-<IP_ADDRESS>’.
ihaskell            >        You can run ‘:set -package ihaskell-aeson’ to expose it.
ihaskell            >        (Note: this unloads all the modules in the current scope.)
ihaskell            >        Use -v to see a list of the files searched for.

I'll investigate later.

Yeah, this is an issue with Stack >=2. I think it's frustrating that we don't have control over this aspect of the tests, when it worked previously.

This is what I get with hlint-2.2.2:
[21 of 25] Compiling IHaskell.Eval.Lint ( src/IHaskell/Eval/Lint.hs, dist/build/IHaskell/Eval/Lint.o )

src/IHaskell/Eval/Lint.hs:59:41: error:
    • Couldn't match type ‘(ExtsModule, [a0])’ with ‘ModuleEx’
      Expected type: [ModuleEx]
        Actual type: [(ExtsModule, [a0])]
    • In the third argument of ‘applyHints’, namely
        ‘(map (\ m -> (m, [])) modules)’
      In the expression:
        applyHints classify hint (map (\ m -> (m, [])) modules)
      In an equation for ‘ideas’:
          ideas = applyHints classify hint (map (\ m -> (m, [])) modules)
   |
59 |       ideas = applyHints classify hint (map (\m -> (m, [])) modules)
   |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^

I've fixed the HLint issue in #1095.

Superseded by #1096.


evaluation of chatgpt

Could you provide the relevant code about the evaluation of ChatGPT?

Waiting, too.


Merging Communities

https://www.hackerrank.com/challenges/merging-communities/problem

Can I do it in cpp?

I can do it in python, I have a solution ready


Pre-encode headlines, captions, images using tokenizer

Closes https://github.com/mahalrs/newsgen/issues/16
Uses tokenizer to encode headlines, captions, and images and saves them to new .json files (headlines_encoded.json and captions_encoded.json)

Related to #20

Fixed most of the requests. Turns out you can't index the batch encoding from the tokenizer directly, so I just pulled out the input_ids and attention_masks and added them as separate fields to the json for each article. Hopefully that works.


Some Scaffold scripts fail in powershell 7

When running Scaffold in Powershell 7 (vs the windows built in "Windows Powershell") some elements fail.
Particularly the enable/disable services calls seem to fail. This seems to be the result of Get-WmiObject being deprecated in powershell 7.

Fixed in #95 and now live on NPM with Launchpad version 1.3.9, scaffold version 1.6.0


Update sbt-mima-plugin to 0.5.0

Updates com.typesafe:sbt-mima-plugin from 0.4.0 to 0.5.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention @scala-steward in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [{ groupId = "com.typesafe", artifactId = "sbt-mima-plugin" }]

labels: semver-minor

Codecov Report

Merging #1202 into master will increase coverage by 0.28%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1202      +/-   ##
==========================================
+ Coverage    86.3%   86.58%   +0.28%
==========================================
  Files          90       90
  Lines        2803     2803
  Branches      114      114
==========================================
+ Hits         2419     2427       +8
+ Misses        384      376       -8

Impacted Files
Coverage Δ

.../core/shared/src/main/scala/io/circe/Decoder.scala
86.25% <0%> (-0.25%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
88.3% <0%> (+0.58%)
:arrow_up:

...les/core/shared/src/main/scala/io/circe/Json.scala
79.14% <0%> (+1.84%)
:arrow_up:

...re/shared/src/main/scala/io/circe/JsonNumber.scala
91.46% <0%> (+2.43%)
:arrow_up:

...re/shared/src/main/scala/io/circe/KeyDecoder.scala
97.29% <0%> (+2.7%)
:arrow_up:

...rc/main/scala/io/circe/shapes/SizedInstances.scala
92.85% <0%> (+14.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Simulate disconnect when changing from 1p to 3p

Phase change from 1p to 3p (vice versa) results in a blocking by our corsa e with go-e v3 - so it is useless. Therefore it should be possible to simulate unplugging the car when changing the phases - like it is realised by clever-pv.de (which works perfectly).

Missing all related and required  information.
Feel free to add informations or create a PR to discuss and fix a potential problem.

Nobody from the main development team owns such a box or such a vehicle, nor does anyone know what clever-pv could supposedly do differently.
So what do you expect?

As far as I know this API setting represents just a basic charger configuration setting (look in the app at "Austecken Simulieren") that should be handled by the charger automatically if enabled.
Just try to modify it and see if the app/api switches the value accordingly.
Beside of that it may also be another bug in the charger firmware that rejects a proper operation of the setting.
Just have a look at issues like https://github.com/goecharger/go-eCharger-API-v1/issues/95 etc.
It would not be a problem for us to add any custom wakeup routine for go-e-charger but we need more info how it should and does work beside just looking at this "documentation". We already have the necessary internal infrastructure and calls to trigger it.
So please provide a tracelog etc from the communication with the charger that does solve your issue with another solution so that we can compare if they really do anything different and what is different.

Just try to modify it and see if the app/api switches the value accordingly.

@spofastic any result?


[Feature] Delegate improvement

it will be good if can merge these codes.

@cczallen thanks, looks good to me.


Fix sample config for SSL in docs

Minor, it seems that the suggested structure for the SSL config has an extra level of brackets

And should not "certificate" be `"crt" ? https://github.com/kadirahq/meteor-up/blob/97cc7e5a3882edbb2655bb8098e94e1900937bb7/src/modules/meteor/index.js#L47

Yeah, it should be crt.

cool, I've changed it


Disassembly of missing x86 instructions yields '??'

On the current dev version (1.1.1228), missing x86 instructions are not ignored (as on release version) but partially included in the output. See pictures below for comparison.

Note that on dev it breaks the iteration of bv.instructions, as the None returned from arch.get_instruction_info does not have the length property.
Here are few hashes and corresponding addresses (can be found in VT database) with unknown instructions:
58af924e90c5a8f95e663d63b4058a2d963bc9b88463bff699e431961eca8222 - 0x555947
e69c4abcc4d2f130e66560fc27829b4fe62a2b1f66933790a3060bd7f4fcd878 - 0x30015815

Resolved in build 1.1.1254-dev.


Partial ESLint fixes in src/test/mocks/

For #4060 #14838 13142

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for enhancements.
[ ] The wiki is updated with any design decisions/details.

General thoughts: if we see the same warning being suppressed a lot in our codebase, we should consider just disabling it, because it's likely to be noise in practice, and not actually useful.
Looking at the PR, I'd say that class-methods-use-this and no-unused-vars are likely both in that category.

General thoughts: if we see the same warning being suppressed a lot in our codebase, we should consider just disabling it, because it's likely to be noise in practice, and not actually useful.
Looking at the PR, I'd say that class-methods-use-this and no-unused-vars are likely both in that category.

class-methods-use-this and no-unused-vars are likely both in that category.

These 2 are actually some of the ones (if not the one) we specifically enabled, so that we tighten up our coding practices moving forward. Granted, that means that all the existing code will have a lot of these sprinkled all over the place 😔

class-methods-use-this and no-unused-vars are likely both in that category.

These 2 are actually some of the ones (if not the one) we specifically enabled, so that we tighten up our coding practices moving forward. Granted, that means that all the existing code will have a lot of these sprinkled all over the place 😔

Codecov Report

Merging #15101 (4c1f9dc) into main (dac8669) will decrease coverage by 0%.
The diff coverage is 33%.

@@          Coverage Diff           @@
##            main   #15101   +/-   ##
======================================
- Coverage     65%      65%   -1%
======================================
  Files        557      557
  Lines      26215    26220    +5
  Branches    3727     3729    +2
======================================
+ Hits       17060    17061    +1
- Misses      8459     8463    +4
  Partials     696      696

Impacted Files
Coverage Δ

src/client/interpreter/activation/service.ts
76% <33%> (-3%)
:arrow_down:

Codecov Report

Merging #15101 (4c1f9dc) into main (dac8669) will decrease coverage by 0%.
The diff coverage is 33%.

@@          Coverage Diff           @@
##            main   #15101   +/-   ##
======================================
- Coverage     65%      65%   -1%
======================================
  Files        557      557
  Lines      26215    26220    +5
  Branches    3727     3729    +2
======================================
+ Hits       17060    17061    +1
- Misses      8459     8463    +4
  Partials     696      696

Impacted Files
Coverage Δ

src/client/interpreter/activation/service.ts
76% <33%> (-3%)
:arrow_down:


Disable ccache on JDK11+OpenJ9 on x/p-Linux

The changes to enable openssl on JDK11 seem to have caused problems when CCACHE is enabled.
This doesn't appear to occur outside jenkins so at least for now I'm going to disable it

Yep temporary (I hope!) related issue will be kept around to cover a subsequent better fix


chore: update es/pt/fr translations for asset description overrides

It took a bit of time due to the recent changes within the Globalization WS, but here are the asset description overrides in the languages for which we currently have translators. There is a plan for additional languages to be done through bounties soon™.
As a side note, I haven't checked the logic for this library, but if there is a mechanism to fallback to English if a string is missing or empty in a language, I think it would be preferable next time (and easier on my side) if the strings in the other languages were left empty, this way translators can filter "untranslated" strings on the Gitlocalize platform. Same goes for the "web" repo strings actually.
And it might be a good thing to empty strings in other languages when there are substantial changes that you want to see reflected in other languages to a string. Due to the growing number of strings it seems unreasonable to have to review all of them manually each time they need to be updated I would think.
Would it be possible to integrate this in the engineering process when they have to update strings in English maybe ?

@kaladinlight Thanks a lot for the review and for having caught this!
That's my fault for being too trusting of a new contributor, even as a non-Spanish speaker I should have at least reviewed the Markdown and URLs a bit. I've done a full review of the file side-by-side with the original and corrected some other errors you did not mention, so at least the strings are consistent with each other.

@kaladinlight Thanks a lot for the review and for having caught this!
That's my fault for being too trusting of a new contributor, even as a non-Spanish speaker I should have at least reviewed the Markdown and URLs a bit. I've done a full review of the file side-by-side with the original to correct the errors you've mentioned, and corrected some other errors you did not mention too, so at least now the strings are consistent with each other.

No worries and thanks for looking through the rest. I found a few more small ones if you want to cross reference with the fr and pt translations

Thanks for these changes. I've checked Portuguese and French, they seem to be fine. The spacing and position for money units in French are actually how currencies are written usually (I've translated those like this on purpose).
I don't have such knowledge about the other two languages so I'm fine using the usual US money format as you suggested. If you prefer that we use this format in French too, just tell me I'll amend my files.

I just did a quick google search on the euro, but I am no expert haha. I biggest thing is the correct addresses obviously. I think we are good to go from here. Thanks for working through those with me!


On 6.14.1, Vector layers partially not shown.

Describe the bug
On 6.14.1, Vector layers partially not shown.
Please see reproduced html at next chapter.
Is this bug? And if it is bug, are there any work around?
To Reproduce
https://code4history.dev/ShibeContour/index_ol6_bugonly.html
This site is what includes bug, which uses OpenLayers 6.
Only upper half of polygon is shown and some text features also not shown.
Souce code is:
https://github.com/code4history/ShibeContour/blob/main/index_ol6_bugonly.html
Expected behavior
https://code4history.dev/ShibeContour/index_ol5_bugonly.html
This site is what expected, which uses OpenLayers 5.
Whole Polygon & all texts are shown.
Souce code is:
https://github.com/code4history/ShibeContour/blob/main/index_ol5_bugonly.html

I also checked history.
v.6.1.1 works well
https://code4history.dev/ShibeContour/index_ol6.1.1_history_ok.html
But from v6.2.0, this error occured.
https://code4history.dev/ShibeContour/index_ol6.2.0_history_ng.html
So I assume the difference between 6.1.1 and 6.2.0 causes this error.

You're using a VectorTile layer where a Vector layer would be more appropriate, because the url does not handle different tiles. Alternatively, you can make the 6.2.0 and above version work by making the tile url unique per tile, e.g. by changing
url: "./shibe.geojson",

to
url: "./shibe.geojson?{z}-{x}-{y}",

But a better fix would be to use a Vector layer instead:
const shibeLayer = new ol.layer.Vector({
  source: new ol.source.Vector({
    attributions: 'Rendered with MapTiler Desktop',
    format: new ol.format.GeoJSON(),
    url: "./shibe.geojson",
  }),
  style: function(feature, resolution) {
    return [new ol.style.Style({
        stroke: new ol.style.Stroke({color: "#ff0000ff", width: 3}),
        fill: new ol.style.Fill({color: "#ff000066", width: 3}),
        text: new ol.style.Text({
            font: "Bold 20px/1 Verdana",
            text: feature.get("町村"),
            fill: new ol.style.Fill({color: "#ff0000ff"}),
            stroke: new ol.style.Stroke({color: "#ffffffff", width: 1}),
            overflow: true
        })
    })];
  }
});

Thank you!
Sorry I misundersood what layer should use for each data sources.
With changing VectorTile to Vector, it become pretty better.


failed to build Dockerfile.saichallenger-client-bldr

in Dockerfile.saichallenger-client-bldr, change the version of a python package or anything to trigger the container build
i see bunch of errors trying to install OS packages coming from the dependent container
and after that docker-saichallenger-client-bldr fails too
ERROR: failed to solve: process "/bin/sh -c apt-get -o Acquire::Check-Valid-Until=false update && apt-get install -y         apt-utils         build-essential         python3         python3-pip         iproute2         rsyslog         supervisor         cmake         graphviz         doxygen         aspell         git         wget         libffi-dev         nlohmann-json3-dev         python3-paramiko     && rm -rf /var/lib/apt/lists/*" did not complete successfully: exit code: 100
ERROR: "docker build -f dockerfiles/${BASE_OS}/Dockerfile.client --build-arg NOSNAPPI=${NOSNAPPI} -t sc-client:${BASE_OS} ." command filed with exit code 1.

===========================================
     SAI Challenger build options
===========================================

 Docker image type  : client
 Base OS            : buster
 ASIC name          :
 ASIC target        :
 Platform path      :
 SAI interface      : redis

===========================================

#0 building with "default" instance using docker driver

#1 [internal] load build definition from Dockerfile.saichallenger-client-bldr
#1 transferring dockerfile: 2B done
#1 DONE 0.0s

#2 [internal] load .dockerignore
#2 transferring context: 84B done
#2 DONE 0.0s
ERROR: failed to solve: failed to read dockerfile: open /var/lib/docker/tmp/buildkit-mount502350835/Dockerfile.saichallenger-client-bldr: no such file or directory
make: *** [Makefile:696: docker-saichallenger-client-bldr] Error 1
Error: Process completed with exit code 2.

https://github.com/mgheorghe/DASH/actions/runs/9371392501/job/25800567766?pr=6

https://github.com/opencomputeproject/SAI-Challenger/issues/237
https://github.com/opencomputeproject/SAI-Challenger/pull/238

hi @mgheorghe - the 2 SAI-Challenger PRs seem to be closed/merged now.  Want to check?

hi @mgheorghe - just checking in on this in case you had time.

Checking in w/ @mgheorghe

Kristina to close


Helm install timed out. Pod is looking for previous 'default' namespace of ibm-system
Error from server (NotFound): error when creating "/tmp/portieris/default-custom-resources.yaml": namespaces "ibm-system" not found
Helm installing ...
helm install portieris --create-namespace --namespace portieris helm/portieris
install.go:159: [debug] Original chart version: ""
install.go:176: [debug] CHART PATH: /home/cicd/portieris/portieris/helm/portieris

client.go:108: [debug] creating 1 resource(s)
client.go:258: [debug] Starting delete for "portieris" ClusterRole
client.go:108: [debug] creating 1 resource(s)
client.go:258: [debug] Starting delete for "admission-portieris-webhook" ClusterRoleBinding
client.go:108: [debug] creating 1 resource(s)
client.go:258: [debug] Starting delete for "image-policy-crds" ConfigMap
client.go:287: [debug] configmaps "image-policy-crds" not found
client.go:108: [debug] creating 1 resource(s)
client.go:258: [debug] Starting delete for "portieris" ServiceAccount
client.go:287: [debug] serviceaccounts "portieris" not found
client.go:108: [debug] creating 1 resource(s)
client.go:108: [debug] creating 1 resource(s)
client.go:467: [debug] Watching for changes to Job create-crds with timeout of 5m0s
client.go:495: [debug] Add/Modify event for create-crds: ADDED
client.go:534: [debug] create-crds: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:495: [debug] Add/Modify event for create-crds: MODIFIED
client.go:534: [debug] create-crds: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:495: [debug] Add/Modify event for create-crds: MODIFIED
client.go:258: [debug] Starting delete for "create-crds" Job
client.go:108: [debug] creating 5 resource(s)
client.go:108: [debug] creating 1 resource(s)
client.go:467: [debug] Watching for changes to Job validate-crd-creation with timeout of 5m0s
client.go:495: [debug] Add/Modify event for validate-crd-creation: ADDED
client.go:534: [debug] validate-crd-creation: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:495: [debug] Add/Modify event for validate-crd-creation: MODIFIED
client.go:534: [debug] validate-crd-creation: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:495: [debug] Add/Modify event for validate-crd-creation: MODIFIED
client.go:108: [debug] creating 1 resource(s)
client.go:467: [debug] Watching for changes to Job create-default-image-policies with timeout of 5m0s
client.go:495: [debug] Add/Modify event for create-default-image-policies: ADDED
client.go:534: [debug] create-default-image-policies: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:495: [debug] Add/Modify event for create-default-image-policies: MODIFIED
client.go:534: [debug] create-default-image-policies: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
Error: failed post-install: timed out waiting for the condition
helm.go:84: [debug] failed post-install: timed out waiting for the condition

Pod in a crashloopbackoff...
kubectl get namespaces,deployment,pods,svc,secrets --all-namespaces
NAME                        STATUS   AGE
namespace/default           Active   77d
namespace/kube-node-lease   Active   77d
namespace/kube-public       Active   77d
namespace/kube-system       Active   77d
namespace/portieris         Active   4m59s

NAMESPACE     NAME                        READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/coredns     2/2     2            2           77d
portieris     deployment.apps/portieris   3/3     3            3           4m52s

NAMESPACE     NAME                                      READY   STATUS             RESTARTS   AGE
kube-system   pod/coredns-66bff467f8-754lb              1/1     Running            4          77d
kube-system   pod/coredns-66bff467f8-ndnpq              1/1     Running            4          77d
kube-system   pod/etcd-k8-test-m1                       1/1     Running            23         77d
kube-system   pod/kube-apiserver-k8-test-m1             1/1     Running            165        77d
kube-system   pod/kube-controller-manager-k8-test-m1    1/1     Running            25         77d
kube-system   pod/kube-flannel-ds-amd64-5rqcj           1/1     Running            1          77d
kube-system   pod/kube-flannel-ds-amd64-fnr4q           1/1     Running            1          77d
kube-system   pod/kube-flannel-ds-amd64-vqf4j           1/1     Running            5          77d
kube-system   pod/kube-proxy-86ppv                      1/1     Running            1          77d
kube-system   pod/kube-proxy-88zhp                      1/1     Running            4          77d
kube-system   pod/kube-proxy-mvdwn                      1/1     Running            1          77d
kube-system   pod/kube-scheduler-k8-test-m1             1/1     Running            23         77d
portieris     pod/create-default-image-policies-gccf5   0/1     CrashLoopBackOff   5          4m41s
portieris     pod/portieris-7476478d7c-8xrcv            1/1     Running            0          4m52s
portieris     pod/portieris-7476478d7c-cs842            1/1     Running            0          4m51s
portieris     pod/portieris-7476478d7c-vq4vj            1/1     Running            0          4m51s
portieris     pod/validate-crd-creation-6dhvz           0/1     Completed          0          4m51s

Pod logs...
kubectl logs pod/create-default-image-policies-gccf5 --namespace portieris
2020-07-22 19:17:32.282021 I | proto: duplicate proto type registered: google.protobuf.Any
2020-07-22 19:17:32.282154 I | proto: duplicate proto type registered: google.protobuf.Duration
2020-07-22 19:17:32.282218 I | proto: duplicate proto type registered: google.protobuf.Timestamp
imagepolicy "default" configured
imagepolicy "default" configured
clusterimagepolicy "default" configured
Error from server (NotFound): error when creating "/tmp/portieris/default-custom-resources.yaml": namespaces "ibm-system" not found

What should have happened differently?
Helm install completes successfully - using 'portieris' namespace
How can it be reproduced?
helm install portieris --create-namespace --namespace portieris helm/portieris
Any other relevant information

Set IBMContainerService to false and you shouldn't see this.


python3Packages.auditok_0_1_5: init at 0.1.5

Description of changes
Add version 0.1.5 of the auditok package, needed for ffsubsync.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
23.11 Release Notes (or backporting 23.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.

Original version of the PR was written by @Arguggi: https://github.com/NixOS/nixpkgs/pull/209430.
The most recent version of the package is 0.2.0, but ffsubsync pins the dependency at 0.1.5. Since there are no other dependents, I'm just adding a package for 0.1.5. Notably, 0.2.0 uses a different test framework (genty) which is not in nixpkgs. I'm not really sure what the standard way to handle this is, so let me know if I should do it differently.
In addition to the tests for this package, I also packaged ffsubsync in a separate branch and tested it.

nixpkgs-review output
$ git -c fetch.prune=false fetch --no-tags --force https://github.com/NixOS/nixpkgs master:refs/nixpkgs-review/0
remote: Enumerating objects: 85, done.
remote: Counting objects: 100% (80/80), done.
remote: Compressing objects: 100% (21/21), done.
remote: Total 85 (delta 58), reused 71 (delta 55), pack-reused 5
Unpacking objects: 100% (85/85), 70.89 KiB | 412.00 KiB/s, done.
From https://github.com/NixOS/nixpkgs
   0a49cae10a00..658dd039b33b  master     -> refs/nixpkgs-review/0
$ git worktree add /home/benjamin/.cache/nixpkgs-review/rev-2188808d911f043ef0b8b92cee1903a3016239af/nixpkgs 658dd039b33b4932a93c236f0158fb3ebc9ed4aa
Preparing worktree (detached HEAD 658dd039b33b)
Updating files: 100% (37066/37066), done.
HEAD is now at 658dd039b33b Merge pull request #252701 from r-ryantm/auto-update/libisoburn
$ nix-env --extra-experimental-features no-url-literals --option system x86_64-linux -f /home/benjamin/.cache/nixpkgs-review/rev-2188808d911f043ef0b8b92cee1903a3016239af/nixpkgs -qaP --xml --out-path --show-trace --no-allow-import-from-derivation
$ git merge --no-commit --no-ff 2188808d911f043ef0b8b92cee1903a3016239af
Automatic merge went well; stopped before committing as requested
$ nix-env --extra-experimental-features no-url-literals --option system x86_64-linux -f /home/benjamin/.cache/nixpkgs-review/rev-2188808d911f043ef0b8b92cee1903a3016239af/nixpkgs -qaP --xml --out-path --show-trace --no-allow-import-from-derivation --meta
2 packages added:
python310Packages.auditok_0_1_5 (init at 0.1.5) python311Packages.auditok_0_1_5 (init at 0.1.5)

$ nix build --extra-experimental-features nix-command no-url-literals --no-link --keep-going --no-allow-import-from-derivation --option build-use-sandbox relaxed -f /home/benjamin/.cache/nixpkgs-review/rev-2188808d911f043ef0b8b92cee1903a3016239af/build.nix
4 packages built:
python310Packages.auditok_0_1_5 python310Packages.auditok_0_1_5.dist python311Packages.auditok_0_1_5 python311Packages.auditok_0_1_5.dist

warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/jr2jqwlddn6z4kq3y8famqk1jjp8qcdp-python3.10-auditok-0.1.5.drv^*'
warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/jr2jqwlddn6z4kq3y8famqk1jjp8qcdp-python3.10-auditok-0.1.5.drv^*'
warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/h3gz9hx05kx5p0hlq69d11y31igbxsys-python3.11-auditok-0.1.5.drv^*'
warning: The interpretation of store paths arguments ending in `.drv` recently changed.


update file

The preconditions check in setAddress(WorkerNetAddress address) can be chained to save a statement: mAddress = Preconditions.checkNotNull(address);

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/14383/
Test PASSed.

Hey @SummitFH, please fix the issues raised by alluxio-bot and sign the CLA when you have the chance. Thanks!

@SummitFH  can you sign the CLA?

@SummitFH Feel free to reopen this after you sign the cla.


Allow passing session data to the fetch function

This is the first implementation of #488.
Locally everything works as expected and also client-side refreshes of the session work flawlessly.
Some highlights

[ ] New tests are passing

[ ]
[ ]

[ ] New settings are available

[ ] Name the variable where houdini stores its session. Maybe this is unneeded?
[ ]

[ ] The doc has been updated

During implementation I noticed that mutations do not take an event object, so I had no easy way to access event.locals/event.parent. I will tackle this tomorrow.
Probably there should also be more tests.

Closing this in favor of #507 where I'm picking up the torch while you're on vacation. Thanks again for putting all the effort into helping us lately. I hope you're having a relaxing time!


Add documentation for changing load manager

Motivation
Documentation for how to switch to ModularLoadManagerImpl needs to exist after #303 is merged.
Modifications
The markdown document docs/ModularLoadManagerImpl describes how to switch between load managers.
Result
Documentation for switching load managers will be present. The document will later be expanded to explain the architecture of ModularLoadManagerImpl.

In addition to how enable the load manager, can you also cover how it works (how is the traffic reassigned, what kind of resources are monitored, etc..)


Fixed lookup.tests.LookupTests.test_exclude() on PostgreSQL 16 beta 1.

Order doesn't matter for this test, and on PostgreSQL 16 "%" is ordered before "_", so switch to sort by pub_date.
https://www.postgresql.org/about/news/postgresql-16-beta-1-released-2643/

Thanks for checking :+1:


[flash_crtl] Re-arrange the INFO page layout

Claim 2 pages as CreatorReserved.  These pages are to be used in the future for creator features or some other as-yet unanticipated need.
Arrange for the OwnerReserved pages to be arranged equally between the banks.
Update OwnerReserved page indicies in perso.

This PR should be cherry-picked to earlgrey_1.0.0 when that branch is open for software dev.


Change Tx validation logic to add: Tx wait that its parent has been validated.

A Child Tx must be executed after its parent if it has a parent Tx.
This order is not guaranteed by the current code and can easily arrive when Proof has a big file as input. The child verify Tx can be executed during the proof input file download.
After Tx verification, the Tx's parent, if it exists, is verified to be already validated.
To do that, the presence of the parent Tx in the db is verified. A cache is used to avoid Db query of the recent Tx.
If the parent is not found, the Tx is put in a waiting list.
When the parent arrives, the child Tx are removed from the waiting list and added to the mempool with the parent tx.
The process_event logic code is more complex because I wanted to avoid using a mutex for the cache, and we need to mix sync code (cache / waiting Tx verification) and async one.
I set it in draft because to be fully tested, the PE #136 must be merged to be able to test it with bigfile.

I've applied the changes.


Create Blog “what-is-the-best-python-course-to-start-with”

Automatically generated by Netlify CMS

👷 Deploy Preview for datascienceprogram processing.

Name
Link

🔨 Latest commit
a2003975199256fcfaedaaa8b94c8337a0c7ee76

🔍 Latest deploy log
https://app.netlify.com/sites/datascienceprogram/deploys/63b29122f438000008a2f5c4


Fix assement due date display in Course Tab

Checklist

[X] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de (currently only on localhost).
[X] Client: I added multiple screenshots/screencasts of my UI changes

Motivation and Context

It fixes issue #1534
Description

I added the evaluation of assessmentDueDate to the method convertDateArrayFromServer, as it was missing there.
Steps for Testing

Log in to Artemis
Navigate to Course Administration
Create an exercise without Assessment Due Date
Assessment Due Date should not be displayed in exercise overview

This should work for all exercise types.
Screenshots

I guess both changes are important

@tessaRuckstuhl I merge this for now. Thanks for the contribution. I guess assessmentDueDate might need to be converted in more places in the code. Also the conversion follows the same pattern in many different places. As you have now changed this pattern, it would be great if you could change this pattern in all places in a separate PR. Would this be possible? Thanks!


[Feature Request] Multivariate normal distribution

Multivariate normal distributions can be useful in simulation of signals and are frequently used in statistical analysis.
Notes:

There is no closed form for the cumulative distribution function so iterative estimations have to be made
A sampling function requires independent standard normal variates, that can be generated by box muller transform (for bivariate version).

closed by eaa8571


feat(pixels): add my new pixel(40, 0)

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

mistakenly !


Added principalOrg condition to IAM role for least priviledge access

Description of changes:
Added aws:PrincipalOrgID to improve least privilege access for IAM role
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Rejecting this PR as the solution currently caters for accounts that may not be in the organization.


Differentiate between client and server version of ErrMessageSizeTooLarge

Right now, the Kafka broker can return ErrMessageSizeTooLarge if a message is deemed to large based on the broker configuration, but we also return it client-side in the producer based on the sarama configuration: https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/async_producer.go#L255
For debugging purposes, it would be nice to be able to differentiate between the client and server-side version.
cc @andremedeiros @kvs @eapache

There are a lot of cases where we return kafka server errors directly:

https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/consumer.go#L366
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/async_producer.go#L255
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L225
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L253
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L275
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L312
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L351
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L506
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L513
https://github.com/Shopify/sarama/blob/53f2a54a5cfd662728648b20eb26e4a8e19b4887/client.go#L540

At the time it seemed unnecessary to define a new local error when the kafka-provide value had the exact right meaning, but I guess this could lead to confusion...

This case is a bit more confusing because it is determined by two configuration settings that live in different places that could be different from each other. This made debugging this error a lot harder.
Many of the other cases where we do this are not really influenced by different configuration settings, and we return what the broker would return anyway based on our best locally cached knowledge. I am not against a generic solution, but we jumped in the rabbit hole of adding context to these errors before without much luck.
Note: we also have ErrMessageTooLarge: https://github.com/Shopify/sarama/blob/master/errors.go#L37-L38

Ah you're right, that's legitimately confusing. Especially when you throw the consumer version of the error into the mix.

I don't know that I have much more to add than a "me too", but I lost some critical time because this error is outright misleading. The error message:

kafka server: Message was too large, server rejected it to avoid allocation error.

It didn't even occur to me to look at the producer limits when the message specifically says the error was rejected by the server, and I knew the server limits were higher than the messages I was sending.

Fixed by #2628 🎉


Disable passthrough for unrecognised media types.

Clients that explicitly set an unmapped media type will be presented with a 415 status code and a message saying "Unsupported media type".
Helps to identify media type issues early.

Coverage remained the same at 89.035% when pulling a83b0f284363fbc095254746dce255387c84dc6b on DomainGroupOSS:feature/disable-pass-through into fc4e84d67c738597e3c42aec8ea5b83c7e95662d on Miserlou:master.


Data Ingestion Stage

[x] Update config.yaml
[x]  Update params.yaml
[x] research or analysis
[x]  Update the entity
[x]  Update the configuration manager in src config.
[x]  Update the components
[x]  Update the pipeline

Dry run Successful for stage 1


v2.2.1 block tail points to itself ?

I have a lfs_mount problem. the lfs_mount will return LFS_ERR_CORRUPT in the end.
After some debugging, I found that in meta-pair {2,3}, block 2 has a LFS_TYPE_TAIL tag, and it contains tail 2 and 3, whch are the current meta-pair themselves.
If I understand littlefs correctly, such "tails pointing back to me" should not happen. Is this a known issue? If so, has it been fixed?

Okay, I found the bug myself.
Assume there are 6 blocks in littlefs, block 0,1,2,3  are in use. 0 has a tail pair of {2, 3}. Now we try to write more into 0.
When writing to block 0, we will split(FIRST SPLIT), thus allocate block 4 and 5. Up to now , everything is as expected.
Then we will try to commit in block 4, during which split(SECOND SPLIT) is triggered again(In our case, some files are large, some are small, one split may not be enough).  Still as expected now.
BUG happens when we try to alloc a new block pair for the second split:
As lookahead buffer reaches the end , a new lookahead buffer will be generated from flash content, and block 4, 5 are unclaimed blocks because they are not programed yet. HOWEVER, block 4,5 should be occupied in the first split!!!!!

I am at lost when I try to fix this. Is there any good idea on how to fix this?

It seems, that commit ce2c01f098f4d2b9479de5a796c3bb531f1fe14c results in this. In this commit, a lfs_alloc_ack is inserted in lfs_dir_split, which will cause split to reset lfs->free.ack to block count.
In summary, this problem exists after 2.1.3.

I'm interesting in this issue. But I seems hard for me to reproduce it. Can I have a guidance to reproduce it?

I'm interesting in this issue. But I seems hard for me to reproduce it. Can I have a guidance to reproduce it?

I have fixed this. see https://github.com/littlefs-project/littlefs/pull/620
Wish this helps.

我已收到您的邮件，我一定会尽快处理。叶思远

thx a lot

我已收到您的邮件，我一定会尽快处理。叶思远


Degraded RAG results in v0.4.2 (compared to v0.3.35)

Bug Report
Installation Method
Using Docker to deploy Open WebUI
Environment

Open WebUI Version: v0.4.2

Ollama: 0.4.2

Operating System: macOS 15.0.1

Confirmation:

[X ] I have read and followed all the instructions provided in the README.md.
[X ] I am on the latest version of both Open WebUI and Ollama.
[   ] I have included the browser console logs.
[   ] I have included the Docker container logs.
[X ] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:
I am running two instances of Open WebUI:
•	Port 2000: Open WebUI v0.4.2
•	Port 3000: Open WebUI v0.3.35
Both are fresh installations. I created the same knowledge object and added an identical markdown file to it on both instances. Subsequently, I created a custom model based on Llama:3.2 using the knowledge object in both instances, setting the TEMPERATURE value to 0 (accuracy over creativity).
Expectation: Both Open WebUI v0.4.2 and Open WebUI v0.3.35 should produce similar results since they are running the same custom RAG model.
Actual Behavior:
For the same questions, my custom model in Open WebUI v0.4.2 consistently provides worse responses compared to Open WebUI v0.3.35. I tested with different files, including various file formats, and multiple questions. The answers from v0.4.2 are consistently inferior to those from v0.3.35. Strangely, when I click on citations, they are mostly the same between the two versions. However, v0.4.2 tends not to follow the citations as closely.
Even tried changing the TEMPERATURE values. No luck.
What changes might account for this discrepancy?
Reproduction Details

Setup Instances:

Deploy two instances of Open WebUI on different ports:

Port 2000: Install Open WebUI v0.4.2
Port 3000: Install Open WebUI v0.3.35
Ensure both installations are fresh and have no prior configuration.

Create Knowledge Object:

On both instances, create the same knowledge object.
Add an identical markdown file to the knowledge object in each instance.

Configure Custom Model:

In both WebUI instances, create a custom model based on Llama:3.2 using the knowledge object.
Set the TEMPERATURE value to 0 for both models to prioritize accuracy over creativity.

Run Tests:

Ask identical questions to both models in each WebUI instance.
Observe and document the responses from each version.

You can disable RAG query generation. Please check the changelogs.

@tjbck

changelogs

Dumb question - From where I can disable RAG query generation? Couldn't able to find the checkbox

From where I can disable RAG query generation? Couldn't able to find the checkbox

In Interface tab.
Also, you can change Query Generation Prompt. This prompt is used both for internet search and RAG search. I found that better results will be with prompt like that:
`
Task:
Based on the user's message and interaction history, generate search query. Refrain from verbose responses or any additional commentary. Prefer suggesting a search if uncertain to provide comprehensive or updated information. Then output both search query and user message. Today's date is: {{CURRENT_DATE}}. Search query must be in a user's message language.
Guidelines:

Respond exclusively with a JSON object.
Be concise, focusing strictly on composing search queries with no additional commentary or text.

Output:
JSON format: {
"queries": ["Search query", "User message"]
}
User message:
{{prompt:end:4000}}
Chat History:
{{MESSAGES:END:6}}
`


Re-design and possible UX enhancements

Andrew Temple mentioned that he'd like to look into doing a redesign of the site. Let's use this issue for discussion.

Also, mockups.


Need a big improvement to Crystal website

I know there is a Crystal website repo but here get more attention.
My first impress on Crystal Lang website (https://crystal-lang.org) feels dry, boring and too many code examples in a page which can do more harm or scared away newbie or non-IT savvy when they visit the site for the first time, in contrast to RubyOnRails, Laravel, Vapor, etc.
If we want to grow community from all walk of life, we’ll need to revamp with friendly introductions and what made Crystal so special from other languages, this way the community will adopt without feeling difficulty or less motivated to pick up 2nd language after Ruby.
The current code examples feels lifeless, we need to highlight colours.
What do you guys think?

This issue is probably best for https://github.com/crystal-lang/crystal-website

Not an issue. Please reopen on https://github.com/crystal-lang/crystal-website or create a thread on the mailing list. Thanks :)


larger than max Segmentation fault (core dumped)

larger than max Segmentation fault (core dumped)
linux python3.6 下 跑3G的文本 报错

用的fast_cut


[release-1.8] Workloadentry add should trigger push to the proxy

This is an automated cherry-pick of #28785

@googlebot I consent.


add wireless thermostat accessory Heizkörperthermostat Basic 6256/1-WL

Description
This pull request adds support for radio heating thermostats of type "Heizkörperthermostat Basic 6256/1-WL“. Possibly also for the „Heizkörperthermostat Comfort 6256/2-WL“, but unfortunately I do not have this one for testing. The wireless thermostats use different datapoints than the existing thermostat implementation, so I added a new accessory category, took the existing implementation and adjusted the datapoints.
API sample
{
  "00000000-0000-0000-0000-000000000000": {
    "devices": {
      "XXXXXXXXXX": {
        "floor": "02",
        "room": "09",
        "interface": "RF",
        "displayName": "Thermostat Büro",
        "unresponsive": false,
        "channels": {
          "ch0000": {
            "displayName": "Thermostat Büro",
            "functionID": "3e",
            "inputs": {
              "idp0000": {
                "pairingID": 52,
                "value": "invalid"
              },
              "idp0001": {
                "pairingID": 56,
                "value": "0"
              },
              "idp0002": {
                "pairingID": 54,
                "value": "0"
              },
              "idp0003": {
                "pairingID": 57,
                "value": "invalid"
              },
              "idp0004": {
                "pairingID": 58,
                "value": "0"
              },
              "idp0005": {
                "pairingID": 66,
                "value": "0"
              },
              "idp0006": {
                "pairingID": 7,
                "value": "0"
              },
              "idp0007": {
                "pairingID": 4,
                "value": "0"
              },
              "idp0008": {
                "pairingID": 53,
                "value": "0"
              },
              "idp0009": {
                "pairingID": 320,
                "value": "21"
              },
              "idp000a": {
                "pairingID": 304,
                "value": "invalid"
              },
              "idp000b": {
                "pairingID": 332,
                "value": "0"
              }
            },
            "outputs": {
              "odp0000": {
                "pairingID": 51,
                "value": "7"
              },
              "odp0001": {
                "pairingID": 52,
                "value": "0"
              },
              "odp0002": {
                "pairingID": 56,
                "value": "0"
              },
              "odp0003": {
                "pairingID": 54,
                "value": "96"
              },
              "odp0004": {
                "pairingID": 57,
                "value": "invalid"
              },
              "odp0005": {
                "pairingID": 66,
                "value": "0"
              },
              "odp0006": {
                "pairingID": 58,
                "value": "0"
              },
              "odp0007": {
                "pairingID": 304,
                "value": "22.8"
              },
              "odp0008": {
                "pairingID": 331,
                "value": "0"
              },
              "odp0009": {
                "pairingID": 333,
                "value": "0"
              },
              "odp000a": {
                "pairingID": 305,
                "value": "0"
              },
              "odp000b": {
                "pairingID": 273,
                "value": "0"
              },
              "odp000c": {
                "pairingID": 59,
                "value": "21"
              },
              "odp000d": {
                "pairingID": 68,
                "value": "0"
              }
            }
          }
        }
      }
    }
  }
}

@superyaro Hi Yaro, if you want we can go through the pull requests together. Just get in touch. Greetings Dennis

Dennis,
can you check the changelog please. I pushed a 3.0.5-beta.1 to NPM, if it's ok for you I release it. Please check it on your system since I don't have the actors running (yet),
thank you for the big contrib, it makes me feel less alone ;)
J

@dennis-nikolas-falk We should extend BuschJaegerWirelessThermostatAccessory.js from BuschJaegerThermostatAccessory.js in the future, I would like to change the Accessories to a "class"/"extend" system like in  BuschJaegerSmokeSensorAccessory:
class BuschJaegerSmokeSensorAccessory extends BuschJaegerAccessory
what do you think about it?
Jaro

@dennis-nikolas-falk We should extend BuschJaegerWirelessThermostatAccessory.js from BuschJaegerThermostatAccessory.js in the future, I would like to change the Accessories to a "class"/"extend" system like in BuschJaegerSmokeSensorAccessory: class BuschJaegerSmokeSensorAccessory extends BuschJaegerAccessory what do you think about it?
Jaro

Yes I think that would be the better way. But unfortunately I don't have that much experience with JavaScript/TypeScript and Node.js/NPM. I work more with Java. But I would still like to support the project.

Dennis, can you check the changelog please. I pushed a 3.0.5-beta.1 to NPM, if it's ok for you I release it. Please check it on your system since I don't have the actors running (yet),
thank you for the big contrib, it makes me feel less alone ;)
J

I will check the version and let you know. Thanks for the note in the changelog :)

@superyaro Looks good to me. Wireless thermostat, wireless window contact and binary inputs work. You can publish this version as stable/newest if you like. Suggestion: I think it would be a good idea to have an issue board here in the project.

opened Issues


notification queue client not able to pull lifecycle events from Engflow cluster

Client
Command:
$> bazel run //java/com/engflow/notificationqueue:client \
-- --notification_queue_endpoint=grpc://demo.cluster.engflow.com --queue_name=default/eventstore/lifecycle-events
INFO: Running command line: bazel-bin/java/com/engflow/notificationqueue/client '--notification_queue_endpoint=grpc://demo.cluster.engflow.com' '--queue_name=default/eventstore/lifecycle-events'
Listening for build events...
Error on request: UNAVAILABLE: io exception

Irrespective of build events on the cluster, it always fails after ~36 seconds.
If grpcs is used with valid tls_certificate and tls_key, it is not failing but returns immediately with no result.
INFO: Running command line: bazel-bin/java/com/engflow/notificationqueue/client '--notification_queue_endpoint=grpcs://demo.cluster.engflow.com' '--queue_name=default/eventstore/lifecycle-events' '--tls_certificate=/Users/vijay/tmp/canary_latest/engflow.crt' '--tls_key=/Users/vijay/tmp/canary_latest/engflow.key'
Listening for build events...
Finished pulling notifications

Note: the client README suggests --queue_name to be  eventstore/lifecycle-events but the actual queue name registered in the backend is default/eventstore/lifecycle-events.

We need to first activate --eventstore_publish_lifecycle_events. I will add that info to the example.

I have checked with Opal and Envoy and it is failing. Looks like the connection is not getting accepted. I will look what have changed in engflow/engflow and engflow/prod because the engflow/example have not been touched.

I am running a local cluster with no auth, I get this error when using the API with the example:
W 2023-03-01 16:24:30.387 thread=engflow-scheduler-default-4 [com.engflow.notificationqueue.grpc.NotificationQueueServiceV1$1.onFailure] Error reading client stream
java.lang.NullPointerException
	at com.engflow.util.grpc.AsyncStreamGrpcClientResponseObserver.requestElementFromClient(AsyncStreamGrpcClientResponseObserver.java:61)
	at com.engflow.util.grpc.AsyncStreamGrpcClientResponseObserver.lambda$fetchNext$0(AsyncStreamGrpcClientResponseObserver.java:84)
	at com.google.common.util.concurrent.AbstractTransformFuture$TransformFuture.doTransform(AbstractTransformFuture.java:250)
	at com.google.common.util.concurrent.AbstractTransformFuture$TransformFuture.doTransform(AbstractTransformFuture.java:240)
	at com.google.common.util.concurrent.AbstractTransformFuture.run(AbstractTransformFuture.java:122)
	at com.google.common.util.concurrent.DirectExecutor.execute(DirectExecutor.java:31)
	at com.google.common.util.concurrent.AbstractFuture.executeListener(AbstractFuture.java:1270)
	at com.google.common.util.concurrent.AbstractFuture.complete(AbstractFuture.java:1038)
	at com.google.common.util.concurrent.AbstractFuture.setFuture(AbstractFuture.java:851)
	at com.google.common.util.concurrent.SettableFuture.setFuture(SettableFuture.java:61)
	at com.engflow.util.grpc.AsyncStreamGrpcClientResponseObserver.add(AsyncStreamGrpcClientResponseObserver.java:160)
	at com.engflow.util.grpc.AsyncStreamGrpcClientResponseObserver.onNext(AsyncStreamGrpcClientResponseObserver.java:133)
	at io.grpc.stub.ServerCalls$StreamingServerCallHandler$StreamingServerCallListener.onMessage(ServerCalls.java:262)
	at io.grpc.ForwardingServerCallListener.onMessage(ForwardingServerCallListener.java:33)
	at io.grpc.Contexts$ContextualizedServerCallListener.onMessage(Contexts.java:76)
	at io.grpc.ForwardingServerCallListener.onMessage(ForwardingServerCallListener.java:33)
	at io.grpc.Contexts$ContextualizedServerCallListener.onMessage(Contexts.java:76)
	at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messagesAvailableInternal(ServerCallImpl.java:318)
	at io.grpc.internal.ServerCallImpl$ServerStreamListenerImpl.messagesAvailable(ServerCallImpl.java:301)
	at io.grpc.internal.ServerImpl$JumpToApplicationThreadServerStreamListener$1MessagesAvailable.runInContext(ServerImpl.java:834)
	at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
	at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:133)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at com.engflow.util.threading.MetricReportingScheduledThreadPoolExecutor$InstrumentedTask.run(MetricReportingScheduledThreadPoolExecutor.java:217)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

I will continue digging but it is difficult to know what change in the past months. I will keep you informed.

Well, I have isolated the commit that "broke" the example: https://github.com/EngFlow/engflow/commit/fe749dad7b33391c508a383796f14f93b8bae24d

I will try to change the example in order to be compatible with the changed in engflow/engflow.
After that, I will try to add a test for this against opal, so we can capture if we break things here.

Filed a backend bug, it shouldn't throw NPE even when the client is holding it wrong.

https://github.com/EngFlow/engflow/pull/13476 Fixed the issue.

https://github.com/EngFlow/engflow/issues/13477


When moving a Red Team Lab application into AC review, it sends team members an email and slack notification saying they need to do a review. Only AC members should get that notification.

@danblah This is true for all submissions with external reviewers. We should change so the notification always only goes to the external reviewers and not to OTF staff. Sounds good?

That sounds great, thanks!

@danblah Is the Slack notification needed at all? It looks like this:
[submission.title] is ready for review. The following are assigned as reviewers: [reviewers]
If we remove the staff from the list of reviewers no Slack users will remain, only external reviewers.

Wait, I do think we want existing slack notification. Maybe something that says:
[submission.title] is ready for AC review. The following are assigned as reviewers: [reviewers]


Runtime server-side configuration

Before, during the build phase big-AGI would check for env keys to inform the UI about the backend configuration at that point in time.
Now, there's a single roundtrip between the UI and the backend to re-assess dynamic support for features. This initial framework not only adds env-var validation, but also fixes all the issues experienced with Docker earlier (where the UI kept asking for the keys despite them being on server).
Needs to update docs too.

Done for now. In the future, we'll adopt mode of backend configuration within the backend, and reflect it in the frontend as well.
Next up shall be some backend-set Auth, which may not even impact the frontend.


feature/vdx-217

added configs for energy shr plus some changes in the structure of the config
still needs some changes related to the literal string values that mentioned in the ticket

What's up with the manual auth? What does it do, why is it needed and how does it relate to the ticket.
Also I am seeing changes that point to your IP

removed those references, it was an experimental thing, and shouldn't be committed in the first place. regarding usages of isManualIdentification is for determining if the user is here via the manual flow vs wallet flow

Yes, but why is that needed and what is the relationship to the ticket at hand?

@nklomp the ux design for this ecosystem has different images/texts depending on your flow. this is addressing these differences


Update Accessibility Conformance Documentation

GitHubTags: #A11y_OSvisualupdate, #A11yMAS, #A11yTCS, #Win32, #DesktopApp, #WindowsUILibrary, #A11YAAT
Recommendation: "Fix and close other bugs before starting accessibility conformance documentation. Any bug that will not be fixed and closed within SLA must be declared in the AAT. The SLA for this bug is also 60 days."

@mayurinaik can you provide a link to the documentation you're referring to? I don't have context on this doc. Also if it's an internal doc I would recommend you follow up with the owner over email, this repo is for bugs about the WinUI product and not accessibility documentation.

Filled out AAT


Configure progress bar

Add option in class file for progress bar
config colors and the position
config draft style after progress bar

review progress bar in class or style file???


OpenSSL not included anymore

I have CI jobs based on this Docker official image and that are using openssl to generate .htaccess files before inclusion in images. Since 5a196cae40e2a0ab5050cf6d79b697e032352b24, the openssl package is not included anymore.
Is it removed on purpose (and I would be totally fine with this)? Or is it a regression you would rather not have?
Thanks!

Definitely was removed on purpose -- it's not needed by Docker at runtime, so it got pruned in the pursuit of leaner images. :sweat_smile:

(Especially since it's easy to add back, but impossible to actually remove if we include it unnecessarily.)

Sure, it definitely makes sense. Thanks for the feedback and for your work @tianon!


Update index.md: add adrs

This is a first cut at an adr-tools compatible Rust version, with some current extras and a few more things in the works.

@joshrotenberg Thank you for the PR. I hope that the upcoming version MADR 4.0. will be supported, too!


Error while importing collect_app: ERROR: Plugin with id 'com.github.spotbugs' not found.

Steps to reproduce:

Create New Project
Import custom work manager from this https://github.com/Samagra-Development/mobile-forms
Added custom work manager in dependencies
Importing collect_app, then its throwing an error ERROR: Plugin with id 'com.github.spotbugs'

Moved this here and hence closing this.


Question to speed up tests execution

Question
I try to organize my tests so that each file is associated to a spec one. For instance, add.ts is associated with add.spec.ts.
My will would be that the spec file fully covers the source one. Hence, if a mutation occurs in the source, I would assume that running its spec file is enough to detect it.
My understanding of the current execution scheme is that all tests are executed for every mutant. Is it true ?
If so, would it be possible to add an option to restrict the tests execution to the associated spec file ?
Stryker environment
    "@stryker-mutator/core": "^6.4.2",
    "@stryker-mutator/jest-runner": "^6.4.2",
    "@stryker-mutator/typescript-checker": "^6.4.2",

    "jest": "^29.5.0",

Additional context
https://github.com/progbots/engine

Thanks for supplying a link to the repo. Since the jest test runner plugin currently doesn't support hot reload (see #3455), it relies on jests --findRelatedTests feature to filter test files to load. Since you've disabled that in your Stryker config, it loads all test files for each mutant.
It should still only run the tests that actually cover a mutant, but the heavy lifting of loading the file is already done by that point.
Is there a way you could make jest --findRelatedTests work? See also https://stryker-mutator.io/docs/stryker-js/troubleshooting/#mutants-survive-but-should-be-killed---jest-runner for a possible work around for you.

Very good point, I remember disabling this feature in another project so I just copied the setting here too. I will remove it to see if it works. Thanks for the prompt answer (and this amazing tool).

So I removed the settings and ran the mutation tests again (I even tried setting it to true).
The results and performance are still the same : same number of tests ran per mutant on average.

Maybe something that could help you reduce the amount of tests that are being executed is described at: https://stryker-mutator.slack.com/archives/CTYUW4B0E/p1681306803311799 where you can specify a function that defines how jest resolves it dependencies

@ArnaudBuchholz
Hello. I had the same problem. In my case, dependencyExtractor can solve this.
ref: https://github.com/jestjs/jest/issues/14000
--findRelatedTests usually returns a lot of tests due to complex dependencies.
$ npx jest --findRelatedTests operators/add.ts --listTests
/home/ubuntu/workspace/engine/state/State.spec.ts
/home/ubuntu/workspace/engine/state/callstack.spec.ts
/home/ubuntu/workspace/engine/state/MemoryTracker.spec.ts
/home/ubuntu/workspace/engine/objects/Array.spec.ts
/home/ubuntu/workspace/engine/state/parser.spec.ts
/home/ubuntu/workspace/engine/operators/get.spec.ts
/home/ubuntu/workspace/engine/operators/set.spec.ts
/home/ubuntu/workspace/engine/operators/throw.spec.ts
/home/ubuntu/workspace/engine/objects/dictionaries/Dictionary.spec.ts
/home/ubuntu/workspace/engine/operators/add.spec.ts
...
/home/ubuntu/workspace/engine/operators/count.spec.ts

For example, by setting the dependencyExtractor as follows, it will return the only associated spec file.
// jest.config.js
module.exports = {
  ...
  dependencyExtractor: "<rootDir>/dependencyExtractor.js",
};

// dependencyExtractor.js
const crypto = require("crypto");
const fs = require("fs");

module.exports = {
  extract(code, filePath, defaultExtract) {
    if (filePath.endsWith(".spec.ts")) {
      const set = new Set();
      set.add(filePath.replace(".spec.ts", ".ts"));
      return set;
    }
    return new Set();
  },
  getCacheKey() {
    return crypto
      .createHash("md5")
      .update(fs.readFileSync(__filename))
      .digest("hex");
  },
};

$ npx jest --findRelatedTests operators/add.ts --listTests
/home/ubuntu/workspace/engine/operators/add.spec.ts

As a result, the number of tests is reduced, and mutation testing can speed up. Note that mutation scores may decrease.

Exactly. As @mkizka points out, you can use jest to first debug the findRelatedTest issue. Once you've got that covered, Stryker should run optimally

Awesome, thx guys, I will try that.
@nicojs I was also wondering if there is a way to leverage the  __stryker__ structure to know which mutation is enabled in which file ? this way I could condition the describe to be skipped :-)

I don't think so, the file name isn't stored there.

You are probably already too late by that point anyways, since the heavy lifting is already done (transforming and loading).
The its without coverage will be skipped using a spec filter, so that should yield as much performance as skipping describes.

Last update (and I will close this issue) : the dependencyExtractor works like a charm : from 30 minutes down to 2.
Yet, I have some adjustments to do but the methods opens lots of door I will explore.
Thanks @nicojs and @mkizka for your help on that matter, very valuable !


Adding Azure Pipelines CI and HQRM module checks

Pull Request (PR) description
Next step in the Azure pipelines CI, merge the changes in dev to master.
This Pull Request (PR) fixes the following issues
None

This change is

Awesome work on this! Just a tiny fix then this looks ready for you to merged! 😄


Fix iap promoted product from cold start

It's not working in the latest version when user come from the terminate state it's not working(listener not called).

On which platform are you experiencing this issue, and what is the exact version of react-native-iap you are using? Providing more detailed information would be very helpful.

I am facing this issue in version 8.6.7 I am updating my library from 7.5.6 to 8.6.7 Because in previous version, I also facing this issue, so I try new reason which have better downloads, but still facing this issue

Library is working when APP is on background mode but if I killed APP and open via promotional link, then it’s not work

### I called that function in componentDidMount
async SubscriptionPromotion() {
   RNIap.initConnection().then((canMakePayments) => { console.log('Can make payments:', canMakePayments); }).catch((error) => { console.error('Error initializing connection:', error); });
   try {
     this.subscription = RNIapEmitter.addListener('iap-promoted-product', async () => {

       if (Message.STAGING) {
         this.props.navigation.navigate(Message.screen_sales_page);
         await RNIap.buyPromotedProductIOS();
       }
       const productId = await RNIap.getPromotedProductIOS();
       console.log("🚀 ~ RNIapEmitter.addListener ~ productId:", productId)

       if (productId !== null) {
         try {

           this.props.navigation.navigate(Message.screen_sales_page);
           await RNIap.buyPromotedProductIOS();
         } catch (error) {
           console.log("🚀 ~ RNIapEmitter.addListener ~ error:", error)
         }
       }
     });
   } catch (e) {
     console.log("🚀 ~ SubscriptionPromotion ~ error:", e)
   }
 }

### Remove the listener in componentWillUnmount
   componentWillUnmount() {
    this.subscription.remove()
  }

React native version :- 0.63.4
React native IAP Version :-^7.0.3
- I am encountering an issue where the listener does not work when I terminate app and open by this link itms-services://?action=purchaseIntent&bundleId=com.example.app&productIdentifier=product_name.

Help me out for this issue because I have dependent your library
@ngocdaothanh @rikur @jgillick @neilco @0916dhkim @13arturbruno @AmauryLiet @breathingearth @chloe-codes1 @cometkim @cristoferfb @dipinarora9 @edTheGuy00 @emilioicai @fjcaetano @geoseong @ghsdh3409 @hankkuu @heyman333 @hyochan @jeebb @jeremybarbet @kwmt @lgraubner @LinusU @M46N3 @maxgmer @MehndirattaPiyush @mifi @mym0404 @pauluhn @pietro909 @RaeesBhatti @rinku-k @Rockvole @RZulfikri @sajithneyo @sayem314 @unolife @vshab @vuonghv @xPutnikx @yjb94 @yoali11 @Zamorite @ZeroCho @zxcpoiu

Please stop spamming.  Creator already replied on your issue and give him time to help. No one gets paid for developing such free and open source modules.

Hi,
I sincerely apologize for my previous message; it was not my intention to spam. I have been working on this issue for many days, and my app relies heavily on this functionality. If possible, please help me out.

@KP-MobileTechie I'm not related to this library. Why did you mention me? If you have problems that are very urgent, fix yourself if you are a programmer.


SVM Classification Model

Project Request

To use SVM to build and train a model using cell records, and classify cells are benign (mild state) or malignant (evil state).

Field
Description

About
SVM to build and train a model using human cell records, and classify cells to whether the samples are benign (mild state) or malignant (evil state).

Github
NisargPipaliya

Email
<EMAIL_ADDRESS>

Label
Project Request

https://github.com/NisargPipaliya

Define You

[x] GSSOC Participant
[x] Contributor

Project Name
Cancer Cell Detection System
Description

[Description of the project, its goals, and expected outcomes]
Scope
[The project's boundaries, including its objectives, deliverables, and constraints]
Timeline
[The project's estimated start and end dates, milestones, and deadlines for deliverables]
Video Links or Support Links
[Links that can support the project in anyway]

I would like to contribute, can you please assign this to me ?

Hi @NisargPipaliya  , iam a GSSOC23 contributer and I would like to resolve this issue
Can you assign me this issue? Or any other issues you might have?
Heres My Resume which you might find useful: Resume
Here is my background in ML:

6 months plus experience in working under college professors for research project on medical image classification.
Got 228 global rank in Amazon ML Challenge 2023 out of 30000+ teams participating.
Experienced with trainig machine Learning Models. Including image preprocessing techniues such as histrogram equilization, augmentation, stationary wavelet transformation, image segmentation. Along with feature extraction from models like resnet50 inceptionv3 vgg16 etc

Looking forward to hear from you.

Hi @NisargPipaliya , I am a GSSOC23 contributor and I would like to resolve this issue
Can you assign me this issue or any other issue that is available ?
this is my resume
khushikantulaResume.pdf

Hey @NisargPipaliya r , I am a GSSOC contributor . I would like to work on this issue.

Hi! @NisargPipaliya , I am a GSSOC Contributor and have experience with ML. I would like to work on this issue!

hi @NisargPipaliya
I would really like to work on this issue. Please assign this issue to me. I have worked on projects in the same field. I am a contributor of GSSOC'23.

Hi, I would like to contribute. Please assign the task to me.

hi @NisargPipaliya
I love to work on this issue. Please assign this issue to me. I have worked 1 project in  binary classification . I am a contributor of GSSOC'23.

hi @NisargPipaliya
I would really like to work on this issue. Please assign this issue to me. I have worked on projects in the same field. I am a contributor of GSSOC'23.

@adithya-s-k
I am a GSSOC'2023 contributor, I created this issue, and this is the suggestion from my side.
Can you Please assign me this issue?

@adithya-s-k I am a GSSOC'2023 contributor, I created this issue, and this is the suggestion from my side. Can you Please assign me this issue?

can you give me more details about the project like

data set
duration
deliverables
scope

give me these details then i will assign this issue to you

I would really like to work on this issue. Please assign this issue to me. I have worked on projects in the same field. I am a contributor of GSSOC'23.

@adithya-s-k
Dataset -> https://s3-api.us-geo.objectstorage.softlayer.net/cf-courses-data/CognitiveClass/ML0101ENv3/labs//cell_samples.csv
Duration -> 5days
Scope -> it will help us to identify cancer cells.


Don't run benchmarks against Ruby 3 for now

Unfortunately adding Ruby 3 support seems to have broken the benchmark CI jobs. The number of allocations doesn't appear to be "stable," i.e. can change between test runs. I'm going to spend some time this week looking into it, but for now let's stop running benchmarks on Ruby 3 so our CI isn't broken.

Is this the same fix as https://github.com/primer/view_components/pull/753 ?

@jonrohan I don't think so? #753 includes ruby 3.0 in the list of ruby versions.

Oh wait, I missed that version-specific code. I suppose it is the same, yeah.


Cleanup to client initialization in Kubelet

Watching invalid label/field selectors should error
Watch locks restrict ability to test certain things
Kubelet does not properly distinguish between sources, prepare for API change

Extracted from #846, @erictune this is all stuff you'll hit
@lavalamp review please

As people are fixing all the watch-related bugs, I'd really appreciate someone to take a look at kube2sky.go and see what mistakes I made :)

@lavalamp can I take this review off your hands?

LGTM


Analogue input mappings cause digital ones for the same action to be eaten

Godot version
v4.0.stable.official
System information
Windows 11
Issue description
When an action in the input map has both key (or button) events and analogue stick events, the key and button events are sometimes dropped, acting as if the button was released when it wasn't.
This happens only when a controller is plugged in (tested with ps4 & xbox 360).
Affects both Input.is_action_pressed and Input.get_axis, unsure about other functions/events.
Steps to reproduce
run the repro project with a controller plugged in and use left & right arrow keys & left & right on the dpad to move the sprite.
it should stop unexpectedly, sometimes starting again after a moment and other times requiring the button to be released & repressed.
seems to happen fairly frequently but may take a few seconds. may be more noticeable with the dpad than keyboard.
i have also noticed the same issue in the official platformer demo project.
Minimal reproduction project
project.zip

oh, this may be #45628. apologies for the duplicate if so, didnt show up in my initial search.

Duplicate of https://github.com/godotengine/godot/issues/45628 indeed. No worry, we prefer duplicate reports to not knowing about bugs ;)


Check problem with NiftyMoMo

I stumbled upon a problem with NiftyMoMo, upgrading from SIRF 2.2.0 to master. This is due to https://github.com/SyneRBI/SIRF/issues/784

this will need the update script to remove the include directory, as per https://github.com/SyneRBI/SIRF/issues/784

this will need the update script to remove the include directory, as per https://github.com/SyneRBI/SIRF/issues/784


Copy:: Bot or Skill???

Describe the bug

The fly out modal should have consistent messaging. If we are calling this a skill, we should make sure we do not interchange the terminology with bot. Also the copy can be improved in general.
Also, when I select new project > Open a new skill

I get the following model.. that asks me to open a bot..

[ ] Electron distribution

OS

[ ] macOS

To Reproduce
Steps to reproduce the behavior:

Click on "..." of a skill
See the fly out menu

Closing this. (The Composer 2.0 UI uses "Add a bot" instead of "Create a new skill" and "Connect to an existing skill")