Import on local component

This will enable one to import it on local components where he/she might want to use it.
https://forum.vuejs.org/t/npm-install-use-local-component/22062/2

Hi, thanks for the PR.
So the proposed usage would be...
// foo.vue
import {FullCalendar} from 'vue-full-calendar'
export {
  components: { FullCalendar },
  ...
}

is importing the component directly not working or bad practise?
// foo.vue
import FullCalendar from 'vue-full-calendar/src/FullCalendar.vue'
export {
  components: { FullCalendar },
  ...
}

It is working but it is not immediately obvious that someone should import it in this way
import FullCalendar from 'vue-full-calendar/src/FullCalendar.vue
I personaly think
import {FullCalendar} from 'vue-full-calendar'
Is more straight forward when someone wants to use it in a local component

I agree that it looks neater but I think we would still need something in the readme as I don't believe this is any more obvious, unless this is common pattern that has completely passed me by?

It is a common pattern in many vue components. And its true that we would need something in the readme.

Ok, thanks for this.
I have merged this in to a feature branch so I can add something to the readme and add some tests before merging it into master
Cheers
Brock


Analyzer should warn when A is assign to A<?>

On sdk>=2.0 there should be a hint/error for things like:
void main() {
  List<String> l1 = List<void>(); // should be an error because it's an error at runtime
  List<String> l2 = <void>[]; // strangely there's already an error today
  List<dynamic> l3 = List<void>(); // OK for dynamic
}

These are downcasts, and are legal in the language.
Otherwise, this is duplicate of https://github.com/dart-lang/sdk/issues/33372.

Also will drop in to say that this was intended to be illegal by dart 2 with "voidness preservation" (basically a form of illegal implicit downcasts that was on by default but limited to this case). Unfortunately we didn't have time to land it, but it may get a lint or be in dart 3.


A possible typo in the repo name

I think you meant detection by detetion, right?

Thanks for the feedback @JafarAbdi
Will fix it.

Thanks @giyaseddin for open-sourcing your work


feat: migrate aws kms flow to v5

PR-Codex overview
This PR introduces support for AWS KMS signer and account handling.
Detailed summary

Added aws-kms-signer dependency
Renamed getAwsKmsWallet to getAwsKmsAccount
Implemented getAwsKmsAccount function in getAwsKmsAccount.ts
Added new imports and functions for AWS KMS handling

The following files were skipped due to too many changes: yarn.lock

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@d4mr lets get this in ser


Removed spaceapi sub-crate

It has moved to https://github.com/coredump-ch/spaceapi-rs.
Can someone review this?

Refs #70.

Awesome! Looks good to me :smiley: And still compiles, runs and passes CI

Sorry I just had to rebase and correct the commit message :wink:

Ahaha.


stellar/quickstart stuckin fail retry loop

I am having an issue with the latest stellar/quickstart docker image. I started the container with the following: docker run -p 8000:8000 -v /Users/jhancock/Desktop/stellar:/opt/stellar --name stellar -it stellar/quickstart:latest --standalone.
The first transaction that i attempt causes the system to get stuck in the WORK_RUNNING -> WORK_FAILURE_RAISE,  WORK_PENDING -> WORK_RUNNING loop. This was a fresh instance of the container. If i destroy the container, remove the local volume, and rerun a new instance the same thing happens.  I am not sure how to start diagnosing this issue.
stellar-core.2018.08.15-19:13:17.log

logs attached looked normal (node was applying transactions from history)


harcoded navigation on layout template

Currently Navigation is hardcoded in:
https://github.com/spring-io/sagan/blob/master/sagan-site/src/main/resources/templates/layout.html
Would be nice to support at least Authenticated and Non-Authenticated requests and have the uih to be able to retrieve that "List" and iterate over it and automatically generate that html content.

We've redesigned the website and I can't reproduce this issue now. Thanks!


Video testing

Pull Request Test Coverage Report for Build 1497

9 of 25 (36.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 24.325%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/workspace/side-content/VideoDisplay.tsx
5
21
23.81%

Totals

Change from base Build 1487:
0.03%

Covered Lines:
1178

Relevant Lines:
4041

💛  - Coveralls

Can we import the p5 library via npm? I would rather not bloat the source code with the p5 library when you can install it via npm. https://www.npmjs.com/package/p5

I have changed the p5 libraries to minified versions.
Some code in the p5 library needs to be edited, so we cannot import it via npm.

Last time I used the video tool, there was an issue with my mac heating up even when I didn't use the video. Could it be that somehow recording continues to happen, after starting VIDEO? Is there a way to turn off the video processing when no one is watching?

Hmm, can you be more specific, what you had to change in p5.dom?
I'm concerned about the long run: Once we include a library literally like that, we are cut off from future improvements and bug fixes.

I deleted one line in p5.min.js:
this.createCanvas(
this._defaultCanvasSize.width,
this._defaultCanvasSize.height,
'p2d');
Doing this stopped the problem of excessive ram usage.

Hmm, can you be more specific, what you had to change in p5.dom?
I'm concerned about the long run: Once we include a library literally like that, we are cut off from future improvements and bug fixes.

I deleted one line in p5.min.js:
this.createCanvas(
this._defaultCanvasSize.width,
this._defaultCanvasSize.height,
'p2d');
Doing this stopped the problem of excessive ram usage.

Looks like a rather desperate way to solve the problem. Are you sure there is no other way to prevent excessive ram usage? Can the canvas size be set in other ways?

The problem was that a default canvas would be created on every page, even if I didn't actually call the function "createCanvas".
I tried removing that line of code and it seemed to solve the problem.
I'm not sure how we would deal with this in the long run.

The problem was that a default canvas would be created on every page, even if I didn't actually call the function "createCanvas".
I tried removing that line of code and it seemed to solve the problem.
I'm not sure how we would deal with this in the long run.

@JJiahui I don't dispute that your change solves the problem at hand. What I'm saying is that the solution comes at a high cost: We lose connection to the p5.dom development effort and cut ourselves from future p5.dom improvements and bug fixes.
My hunch is that there should be a better way. Can you investigate more?

I've investigated two ways, putting the p5 library in the source code and importing via npm.
Both ways I found that merely loading/importing the library would cause excessive ram usage, without any additional code from me.
This was what led me to think that the bug lies within the p5 library itself.

Hmm, a cursory search leads me to thing that p5 has had cpu usage issues, which is not surprising per se. You may be able to find reports on the specific performance issue that you faced. Literally copying the library is a drastic measure. If you are convinced that this is a bug in p5.dom, can you file a bug report with p5? See what they say. Is p5.dom the only library that provides the service that you need?

Just took a closer look at this: P5 is distributed under the LGPL, see
https://github.com/processing/p5.js/blob/master/license.txt
This means we cannot do what you propose: include a modified minified version of the library. We would need to apply LGPL explicitly to our modification. This would complicate the licensing of our entire system.

As I have discovered a way to make it work without the p5 libraries, I have removed them entirely.

Can you resolve the conflicts, @JJiahui ? Thanks!

I'm getting this error and no video is displayed.

I'm getting this error and no video is displayed.

Hmm, works for me. Can you be more specific, @geshuming ?

If I set the size to 1000x700 (I know: quite large), I get tons of errors like this in the console:
video_lib.js:199 [Violation] 'requestAnimationFrame' handler took 67ms
video_lib.js:199 [Violation] 'requestAnimationFrame' handler took 55ms
video_lib.js:199 [Violation] 'requestAnimationFrame' handler took 51ms
We may be able to catch these and issue a warning for the user.
Also maybe we should suggest some common screen dimensions? Is there a way to get the native pixel size of the camera?

Yup I'm using chrome latest version. Firefox latest version was also giving me the same error

Did you give permission to use your camera?

@JJiahui can we be more specific with error messages? What are possible error codes from navigator.mediaDevices.getUserMedia ?
Here is a starting point: https://blog.addpipe.com/common-getusermedia-errors/

Did you give permission to use your camera?

Yep permission is given. The error above is all i'm getting.

My recent changes:

changed default resolution to 400x300
changed textinput to NumericInput
added some icons from the list in https://evergreen.segment.com/components/icons/
changed the pause button to a "snap picture" button
changed apply_filter so that it updates the snapped picture

A couple of remaining issues:

Re-sizing should update the snapped picture, but currently, the picture goes black, and the user has to press "snap" again. @JJiahui can you take a look?
The formatting of the buttons is poor: I just inserted some "nbsp;", but that's obviously not the right way. @alcen can you see if there is a better way.

A couple of remaining issues:
Re-sizing should update the snapped picture, but currently, the picture goes black, and the user has to press "snap" again. @JJiahui can you take a look?
The formatting of the buttons is poor: I just inserted some "nbsp;", but that's obviously not the right way. @alcen can you see if there is a better way.

Ok, I'll look into it!


sendgrid.send gives {"code":"EPROTO","errno":"EPROTO","syscall":"write"}

Issue Summary
My nodeJS integration is returning a lot of the following errors when calling sendgrid.send:
{"code":"EPROTO","errno":"EPROTO","syscall":"write"}
I don't know what this error message means or whether this has prevented my email from being sent. Any idea what this means, what it's impacts are or how I can address it?
Technical details:

sendgrid-nodejs Version: version: "2.0.0",
Node.js Version: 4.5.0

Hello @danielflippance,
I have not seen this issue myself (seems its dependent on your server settings), but in this epic thread, it looks like there are several possible solutions: https://github.com/nodejs/node/issues/3692
I hope that helps.


Mega Breloom + Custom Move & Ability

I also tweaked a few smaller things :)
Still needs to be tested in showdown but I think I coded it correctly fingers crossed

Since it took so long for yall to put this pull request through, I also added in Mega Togekiss and Mega Mimikyu bc why not


Add selector function

Motivation
Most interactors use CSS selectors to locate the pertinent elements on the page. However, there are some interactors where it would be great if we could call a method to return the elements. An example would be a Label interactor, which would operate on the labels associated on a field. We would want to implement the interactor like this:
const Label = HTML.extend('label').selector((e) => e.labels));

Another example is the keyboard interactor, which would really like to use document.activeElement as its selector.
Adding this option makes interactors even more powerful, since they are no longer constrained to just CSS selectors.
Approach
Optionally, selector can take a function which gets as its argument the parent element, and must return a list of elements of the appropriate type.
Alternate Designs
None
Possible Drawbacks or Risks
Adds additional complexity

Let's wait for #127 to be merged, and we can extend this PR with an addition to the guides.


leiden clustering fails on pbmc3k tutorial

I am trying to  follow the pbmc3k tutorial. I pushed through the regres_out error mentioned in #1010 , but now it fails at line:
sc.tl.leiden(adata)

with error :
running Leiden clustering

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-46-a9ad6348435f> in <module>
----> 1 sc.tl.leiden(adata)

~/miniconda3/envs/i529/lib/python3.7/site-packages/scanpy/tools/_leiden.py in leiden(adata, resolution, restrict_to, random_state, key_added, adjacency, directed, use_weights, n_iterations, partition_type, copy, **partition_kwargs)
    138     adata.obs[key_added] = pd.Categorical(
    139         values=groups.astype('U'),
--> 140         categories=natsorted(np.unique(groups).astype('U')),
    141     )
    142     # store information on the clustering parameters

~/miniconda3/envs/i529/lib/python3.7/site-packages/pandas/core/arrays/categorical.py in __init__(self, values, categories, ordered, dtype, fastpath)
    383
    384         else:
--> 385             codes = _get_codes_for_values(values, dtype.categories)
    386
    387         if null_mask.any():

~/miniconda3/envs/i529/lib/python3.7/site-packages/pandas/core/arrays/categorical.py in _get_codes_for_values(values, categories)
   2574     _, cats = _get_data_algo(categories)
   2575     t = hash_klass(len(cats))
-> 2576     t.map_locations(cats)
   2577     return coerce_indexer_dtype(t.lookup(vals), cats)
   2578

pandas/_libs/hashtable_class_helper.pxi in pandas._libs.hashtable.StringHashTable.map_locations()

TypeError: Expected unicode, got numpy.str_

Versions:
scanpy version is 1.4.4.post1, everything was installed using conda in a freshly created environment.

Could you check your pandas version?
I believe we've seen this being cause by pandas 1.0, and have addressed it here: https://github.com/theislab/scanpy/pull/1015.

Yes, thank you, I was on pandas 1.0 and the tutorial does work with Pandas 0.25.3

That being said, maybe this better be reflected in the conda dependencies, so pandas 1.0 is not pulled with scanpy?


More robust session count checks

Closing this as these changes were incorporated in https://github.com/bugsnag/bugsnag-php/pull/579/


Login credential error message update

Now it says: Failed to get token for<EMAIL_ADDRESS>Please replace this with: "Invalid login credentials. Please double-check your username and password and try again."

@lal issue is fixed


compiling thing

Describe your problem here.
what do i do
source/Main.hx:78: characters 61-65 : Float should be Int
source/Main.hx:78: characters 61-65 : ... For optional function argument 'updateFramerate'
source/Main.hx:78: characters 61-65 : ... For function argument 'child'
source/FreeplayState.hx:78: characters 57-58 : Int should be flixel.util.FlxAxes
source/FreeplayState.hx:78: characters 57-58 : ... For optional function argument 'repeatAxes'
source/PlayState.hx:1552: lines 1552-1585 : Warning : This case is unused
source/PlayState.hx:1667: characters 78-84 : Warning : This pattern is unused
source/PlayState.hx:7956: characters 78-81 : Warning : This pattern is unused
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

Set your Flixel version to 4.11.0 with the command:
haxelib set flixel 4.11.0
After, accept the questions that will appear in the terminal.

Sorry for my English lol

well then if you do that then

Also for main.hx, copy the new main from psych engine here

Wait NVM, It does work, sorry If I confused anyone.

close this issue


Update b2d cache in PreCreateCheck

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "2189-update-b2d-cache-in-precreatecheck" git@github.com:dgageot/machine.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Fixes #2189

LGTM

:+1:

LGTM


CustomView Support

Is custom Views Supported

Yes @poovarasanvasudevan, you can plug in custom views into proteus. Let me get back to you with a demo app and add documentation in the GitHub repo.

@poovarasanvasudevan hey man go ahead and check this out. Do go through the readme.

Closing this issue.


Write logic for visualizing bead plots

All the required info should be contained in clusters.json.

Done with some issues


install.bash: better coding style

Hm, for some reason, the PR can't be auto-merged. Could you please fix this?

I will do a new PR.


Working with CONNECT tunnels

Hi,
I am currently writing a toy HTTP proxy using hyper with tokio (current master). While plain HTTP proxying was easy to write, I am struggling with how to handle CONNECT tcp tunnels (typically used to proxy https without ssl interception).
How would you proceed to switch from the Http service to a raw tcp proxy service (such as the one demonstrated in tokio-socks5) on the same socket ?
Solving this issue would also be beneficial for switching protocols to websockets or cleartext http2.
Thank you in advance for any advice.
Florent

This is something that Tokio needs to figure, since hyper is using Tokio internally. I've discussed the concept before with the Tokio devs, but apparently there wasn't a tracking issue, so I've filed https://github.com/tokio-rs/tokio-proto/issues/138.

Thank you! I'll think of a workaround in the meantime.

I'm also interested in CONNECT support. Looking to correlate TLS SNI with the domain name passed to CONNECT, to (dynamically) whitelist and also map the name to another for the resolution of the next hop.
Context an in-bound forward proxy for one platform to reach other platforms within an enterprise network across DMZs and fronted by reverse proxies.
Another protocol switch example is to support the proxy protocol (aka ELBs) stripping and insertion.

I think this has been resolved by https://docs.rs/hyper/0.12.1/hyper/client/conn/struct.Connection.html#method.poll_without_shutdown, right?

Yep, this can be done now with the server::conn module, and in the next release, could also be done thanks to #1563.


[DO NOT MERGE] LLM-based crash triaging - 1

Experiment based on #221, #253, and #374.

/gcbrun exp -n dg

Missing triaging
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-avahi-avahi_string_list_add_pair/08.html
Require manual validation

https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-hunspell-_zn8hunspell8generateepppcpkcs4_/02.html
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-hunspell-_zn8hunspell8generateepppcpkcs4_/10.html
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-libusb-libusb_get_string_descriptor_ascii/01.html
...

Maybe manually validate if they are real bugs in the project. If not, what info can we provide to rectify LLM?

I will manually pick more benchmarks that may have bugs from:

https://llm-exp.oss-fuzz.com/Result-reports/scheduled/2024-06-21-weekly-all/
https://llm-exp.oss-fuzz.com/Result-reports/scheduled/2024-06-26-weekly-all/

As discussed, I will merge this and reiterate in future PRs.

/gcbrun

/gcbrun

/gcbrun skip

Missing triaging
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-avahi-avahi_string_list_add_pair/08.html
Require manual validation

https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-hunspell-_zn8hunspell8generateepppcpkcs4_/02.html
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-hunspell-_zn8hunspell8generateepppcpkcs4_/10.html
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-libusb-libusb_get_string_descriptor_ascii/01.html
...

Maybe manually validate if they are real bugs in the project. If not, what info can we provide to rectify LLM?

Thanks, I would take a deep look at it.

Thanks!

Missing triaging
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-avahi-avahi_string_list_add_pair/08.html
Require manual validation

https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-hunspell-_zn8hunspell8generateepppcpkcs4_/02.html
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-hunspell-_zn8hunspell8generateepppcpkcs4_/10.html
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-26-375-dg-comparison/sample/output-libusb-libusb_get_string_descriptor_ascii/01.html
...

Maybe manually validate if they are real bugs in the project. If not, what info can we provide to rectify LLM?

Thanks, I would take a deep look at it.

The reason for missing triage is that ofg currently does not consider memory leaks as crashes, relevant code is here. The premise of triage is to have crash_info, and the premise of retrieving crash_info is to be considered as a crash, relevant code are triage_crash and extract_crash_info
Perhaps we can ease the conditions for being considered a crash, such as including memory leaks in crashes?

The reason for missing triage is that ofg currently does not consider memory leaks as crashes, relevant code is here.

Thanks for looking into this, @fdt622!

Perhaps we can ease the conditions for being considered a crash, such as including memory leaks in crashes?

I would prefer not to triage memory leaks.
We do not report it as a crash because it is likely non-exploitable.
Hence, triaging it has little benefit.
WDYT?

The reason for missing triage is that ofg currently does not consider memory leaks as crashes, relevant code is here.

Thanks for looking into this, @fdt622!

Perhaps we can ease the conditions for being considered a crash, such as including memory leaks in crashes?

I would prefer not to triage memory leaks. We do not report it as a crash because it is likely non-exploitable. Hence, triaging it has little benefit. WDYT?

OK, let's not triage the unlikely exploitable crash. If needed for future research and experiments, I will create another branch.


Weird Screen after starting EmulationStation

Installed EmulationStation on my Windows 8 PC and get this screen as soon as I start the program. EmulationStation never runs pass this point. Have looked everywhere for a fix. What does this mean? What do I do?

Hi - have you seen this? https://github.com/Aloshi/EmulationStation/issues/460

Thanks buddy!
No I didn't see that. I'll check it out when I get home. 🤓

i get similar on my windows 10 just install the softwareand won't start

saying we can't ------------------
check that your path are correct on the systems
configuration and you games directory has at least
one game wth the correct extension

Hi @frenchiefr  - this is the default screen when you don't have any systems configured. Take a look at the README.md for details on how to set those up: https://github.com/Aloshi/EmulationStation#writing-an-es_systemscfg

Apologies for hitting an older thread but I had the same problem as Monkey76, however lowering my screen resolution sorted it. Thought I would share in case anyone else finds this thread looking for a solution, as I initially did.


release woodwork v0.4.0

Merged into main and released

https://github.com/alteryx/woodwork/releases/tag/v0.4.0


feat(instagram): implement instagram watcher

this PR resolves #3

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


npm run visualization Issue

Description
Npm run Visualization is erroring out
Steps to Reproduce

npm run hello-visualization

Expected behavior
[What you expected to happen]
Expecting to get localhost URL of weback dev server, to view the visualization
Actual behavior
[What actually happened]

<EMAIL_ADDRESS>hello-visualization C:\Users\Santosh Chavan\Downloads\core-get-started-master
webpack-dev-server --config ./src/hello-visualization/webpack.config.js

events.js:183
throw er; // Unhandled 'error' event
^
Error: listen EACCES <IP_ADDRESS>:8080
at Object._errnoException (util.js:1024:11)
at _exceptionWithHostPort (util.js:1046:20)
at Server.setupListenHandle [as _listen2] (net.js:1334:19)
at listenInCluster (net.js:1392:12)
at doListen (net.js:1501:7)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
at Function.Module.runMain (module.js:678:11)
at startup (bootstrap_node.js:187:16)
at bootstrap_node.js:608:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>hello-visualization: webpack-dev-server --config ./src/hello-visualization/webpack.config.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>hello-visualization script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
Environment
Library
[ ] Node.js

Operating system
[ ] Windows

### Versions

* Node.js:
* Browser:
* Operating system:
* [Other relevant versions]

Hi!
It looks like you may have another process listening on the 8080 port. What if you modify this line to another port (e.g. 8081) and try again?
https://github.com/qlik-oss/core-get-started/blob/master/src/hello-visualization/webpack.config.js#L13

Hello Peol,
Thanks for your help it got resolved the issue.


Add Leaflet.HighlightableLayers and Leaflet.DraggableLines plugins to docs

@cdauth
Please resolve conflicts

@johnd0e @Falke-Design Fixed.


Add froze system

since mods & admins have Team Grief utility, we can add a frozing system just like you want, maybe isn't useful 😕 and sorry if is 🙈

This is not something we are going to implement into the main plugin

@CaptainElliott  Why did you say "the main plugin" (sorry if you mean another thing)

I believe @ShinyDialga45 is making a utility plugin with things that we don't want to have in this plugin

@CaptainElliott Oh i didn't knew it sorry 🙈

CommandBook have freeze command and is comaptible with SB


Esun366 task 24 - sign up page

Hi Mr. Sun,
I have completed the sign up page. Could you please code review?
Thanks,
Eric Sun

@esun366, could you please change email to email/username,  so the username not need to be an email address?


jsr310 Not Working in Maven Plugin

I apologize if this isn't the appropriate place to raise this issue.
I see that in this issue JSR310 (java Time API) support was added, but I'm not seeing a way to use it from the Maven plugin. The wiki didn't specify it but looking at the source I assumed I'd just have to add something like this:
<dateTimeType>java.time.LocalDateTime</dateTimeType>
 <dateType>java.time.LocalDate</dateType>
to my Maven plugin configuration. I'm building under Java 8, but the plugin isn't generating java.time.* class members, just java.util.Date ones. The plugin works fine otherwise.
What do I need to do to get the Maven plugin to generate pojos with java.time.* class members ?

My first guess would be that the this feature is not working correctly in combination with another configuration option you are using.
It might be useful to take a look through the integration test for this feature:
https://github.com/joelittlejohn/jsonschema2pojo/blob/de57cc68d6fbaf46eb131aa790270550066d1b16/jsonschema2pojo-integration-tests/src/test/java/org/jsonschema2pojo/integration/config/CustomDatesIT.java
and the schema that this test uses:
https://github.com/joelittlejohn/jsonschema2pojo/blob/de57cc68d6fbaf46eb131aa790270550066d1b16/jsonschema2pojo-integration-tests/src/test/resources/schema/format/formattedProperties.json
It would be useful if you could provide the full configuration you're using to invoke the plugin.

Sure thing, here's the relevant section of the POM. I should note we've been successfully using the plugin since 0.4.16, with Joda support. We're only trying to use this feature now that we've moved to Java 8. Joda support worked in Java 8 before the configuration change too.
<plugin>
    <groupId>org.jsonschema2pojo</groupId>
     <artifactId>jsonschema2pojo-maven-plugin</artifactId>
     <version>0.4.20</version>
     <configuration>
        <includeToString>false</includeToString>
        <initializeCollections>true</initializeCollections>
        <annotationStyle>none</annotationStyle>
        <includeHashcodeAndEquals>false</includeHashcodeAndEquals>
        <includeDynamicAccessors>false</includeDynamicAccessors>
        <includeJsr303Annotations>true</includeJsr303Annotations>
        <sourceDirectory>${basedir}/src/main/resources/schema</sourceDirectory>
        <sourcePaths>
             <sourcePath>request/MyRequest.json</sourcePath>
             <sourcePath>response/MyResponse.json</sourcePath>
        </sourcePaths>
        <targetPackage>com.mypackage</targetPackage>
        <outputDirectory>${basedir}/src/main/java</outputDirectory>
        <removeOldOutput>true</removeOldOutput>
        </configuration>
	<executions>
		<execution>
		    <goals>
	                <goal>generate</goal>
		   </goals>
	        </execution>
	</executions>
</plugin>

Also, it doesn't look like there's an integration test for java.time.* classes. Am I reading the test wrong ?

Yes, there's no test for those classes as the project itself doesn't
require Java 8. I thought it might be useful to just check the general
approach. Interesting that this only affects those classes but not the Joda
classes, I can't think why this would be.
I'll have a play around and see if I can work out what's happening here.
Thanks for reporting this. I might add a couple of tests that run only when
Java 8 is detected. These would at least be runnable by Travis CI.
On 23 Feb 2016 4:54 p.m., "jharnach"<EMAIL_ADDRESS>wrote:

Sure thing, here's the relevant section of the POM. I should note we've
been successfully using the plugin since 0.4.16, with Joda support. We're
only trying to use this feature now that we've moved to Java 8. Joda
support worked in Java 8 before the configuration change too.

org.jsonschema2pojo
jsonschema2pojo-maven-plugin
0.4.20

false
true
none
false
false
true
${basedir}/src/main/resources/schema

request/MyRequest.json
response/MyResponse.json

com.mypackage
${basedir}/src/main/java
true

generate

Also, it doesn't look like there's an integration test for java.time.*
classes. Am I reading the test wrong ?
—
Reply to this email directly or view it on GitHub
https://github.com/joelittlejohn/jsonschema2pojo/issues/511#issuecomment-187788491
.

What about bindings (as a new feature)? This could enhance the usage of the plugin and remove some complexity.
E.g.
<formatBindings>
    <binding>
        <jsonType>date-time</jsonType>
        <javaType>java.time.ZonedDateTime</javaType>
        <typeAdapter>my.package.DateTimeAdapter</typeAdapter>
    </binding>
    <binding>
        <jsonType>utc-millisec</jsonType>
        <javaType>java.time.Instant</javaType>
        <typeAdapter>my.package.UtcMillisecAdapter</typeAdapter>
    </binding>
</formatBindings>

Comparable things can be done for media encoding and also for user defined types. The typeAdapter above is gson specific. For Jackson one woulde define serializer and deserializer elements. In both cases the adapters or (deserializer) would be optional if the used json library natively supports the (de)serialization of the defined javaType.

@dadrus this could certainly be useful, although I do think we have most use-cases covered by the current configuration options (we do need to work out what the underlying issue is here).

I agree. My comment is not really related to the issue. One thing I remember to have encountered in the code is that usage of defaults with java.time  seems to be impossible. The implementation assumes, the corresponding classes are constructable via constructor, which is true for joda and java Date, but not for java.time classes. But this is also not related to the issue here

@dadrus https://github.com/FasterXML/jackson-datatype-jsr310

@jharnach Could you please test this again with 0.4.22?

@joelittlejohn Excellent, I'm able to use the Java 8 Time API with this plugin now. Thanks!

@jharnach Thanks go to @mmyslyvtsev !


Unable to startup after upgrading existing setup to 0.9.59 release

I updated the tag of my existing deployment to 0.9.59 and I am getting the following error.  If I force create the install.ed file it says the same.  I don't have a test environment setup with a scheduler, so I will work on that so that I can help provide any additional information if needed.
scheduler  | [1726015909.434][TRANSACTION][put] global/servers/0 ({"elapsed_ms":3.983})
scheduler  | Record successfully saved: global/servers/0
scheduler  |
scheduler  | [1726015909.44][TRANSACTION][get] global/servers/0 ({"elapsed_ms":2.252})
scheduler  | {
scheduler  |    "type": "list_page",
scheduler  |    "items": [
scheduler  |            {
scheduler  |                    "hostname": "main",
scheduler  |                    "ip": "<IP_ADDRESS>"
scheduler  |            }
scheduler  |    ]
scheduler  | }
scheduler  |
scheduler  | Docker Env Fixed.
scheduler  | [1726015909.712][2024-09-10 20:51:49][388da58b1a3f][1][Cronicle][debug][2][Cronicle v0.9.59 Starting Up][{"pid":1,"ppid":0,"node":"v18.20.4","arch":"x64","platform":"linux","argv":["/usr/local/bin/node","/opt/cronicle/bin/docker-entrypoint.js"],"execArgv":[]}]
scheduler  | [1726015909.716][2024-09-10 20:51:49][388da58b1a3f][1][Cronicle][debug][9][Writing PID File: logs/cronicled.pid: 1][]
scheduler  | [1726015909.716][2024-09-10 20:51:49][388da58b1a3f][1][Cronicle][debug][9][Confirmed PID File contents: logs/cronicled.pid: 1][]
scheduler  | [1726015909.718][2024-09-10 20:51:49][main][1][Cronicle][debug][2][Server IP: <IP_ADDRESS>, Daemon PID: 1][]
scheduler  | [1726015909.719][2024-09-10 20:51:49][main][1][Cronicle][debug][3][Starting component: Storage][]
scheduler  | [1726015909.719][2024-09-10 20:51:49][main][1][Storage][debug][5][Setting up storage system v3.2.2][]
scheduler  | [1726015909.72][2024-09-10 20:51:49][main][1][Filesystem][debug][2][Setting up filesystem storage][]
scheduler  | [1726015909.721][2024-09-10 20:51:49][main][1][Filesystem][debug][3][Base directory: data][]
scheduler  | [1726015909.721][2024-09-10 20:51:49][main][1][Cronicle][debug][3][Starting component: WebServer][]
scheduler  | [1726015909.722][2024-09-10 20:51:49][main][1][WebServer][debug][2][pixl-server-web v2.0.2 starting up][]
scheduler  | [1726015909.727][2024-09-10 20:51:49][main][1][WebServer][debug][2][Starting HTTP server on port: 3012][]
scheduler  | [1726015909.733][2024-09-10 20:51:49][main][1][Cronicle][debug][1][Uncaught Exception: Error: ENOENT: no such file or directory, open '../conf/install.ed'][Error: ENOENT: no such file or directory, open '../conf/install.ed'     at Object.openSync (node:fs:596:3)     at writeFileSync (node:fs:2322:35)     at /opt/cronicle/bin/docker-entrypoint.js:57:13     at constructor.shutdown (/opt/cronicle/node_modules/pixl-server-storage/engines/Filesystem.js:730:3)     at /opt/cronicle/node_modules/pixl-server-storage/storage.js:1078:34     at __construct.waitForAllLocks (/opt/cronicle/node_modules/pixl-server-storage/storage.js:951:8)     at /opt/cronicle/node_modules/pixl-server-storage/storage.js:1075:9     at __construct.waitForQueueDrain (/opt/cronicle/node_modules/pixl-server-storage/storage.js:922:26)     at __construct.shutdown (/opt/cronicle/node_modules/pixl-server-storage/storage.js:1072:8)     at /opt/cronicle/bin/docker-entrypoint.js:54:19]
scheduler  | Error: ENOENT: no such file or directory, open '../conf/install.ed'
scheduler  |     at Object.openSync (node:fs:596:3)
scheduler  |     at writeFileSync (node:fs:2322:35)
scheduler  |     at /opt/cronicle/bin/docker-entrypoint.js:57:13
scheduler  |     at constructor.shutdown (/opt/cronicle/node_modules/pixl-server-storage/engines/Filesystem.js:730:3)
scheduler  |     at /opt/cronicle/node_modules/pixl-server-storage/storage.js:1078:34
scheduler  |     at __construct.waitForAllLocks (/opt/cronicle/node_modules/pixl-server-storage/storage.js:951:8)
scheduler  |     at /opt/cronicle/node_modules/pixl-server-storage/storage.js:1075:9
scheduler  |     at __construct.waitForQueueDrain (/opt/cronicle/node_modules/pixl-server-storage/storage.js:922:26)
scheduler  |     at __construct.shutdown (/opt/cronicle/node_modules/pixl-server-storage/storage.js:1072:8)
scheduler  |     at /opt/cronicle/bin/docker-entrypoint.js:54:19 {
scheduler  |   errno: -2,
scheduler  |   syscall: 'open',
scheduler  |   code: 'ENOENT',
scheduler  |   path: '../conf/install.ed'
scheduler  | }
scheduler exited with code 0

thank you @nguyenmp
@DerekF35 try docker pull soulteary/cronicle:0.9.63  :D

Yay!  Thanks for merging!


#379 - Fix 'File is not part of a jME project'

Fixes (hopefully) #379
Problem was caused by newer underlying version of Netbeans Gradle tooling returning the Asset sub-project name as :assets rather than assets

Looks like it works. And still works in Ant projects as well as expected. Super! Thank you!


Juno init create file type

Try to detect the project type (React etc.) on juno init and directly creates the correct configuration file like juno.config.mjs

Note: same issue in vanilla example so maybe the issue is vite expecting module, period.


version 48: debugger fails in python input

VSCode Version: 1.48
OS Version: Ubuntu 18.04

Steps to Reproduce:

A simple python program with "test = input("Test:") " hangs after printing during debugging
Also more complicated python Command Line Interfaces fail

In VSCode 1.47.3 it worked flawlessly.

Does this issue occur when all extensions are disabled?: not applicable since python extension needed for debugging

/extPython


Deploying DockerEngine Vagrant box behind proxy

Hi Folks,  I'm trying the https://github.com/oracle/vagrant-boxes behind oracle proxy, the Oracle Linux 7 vagrant box works like a charm, but  DockerEngine vagrant box doesn't, I found that Oracle Linux 7 Vagrantfile has vagrant-proxyconf instructions, Who could update the DockerEngine box's Vagrantfile?, thanks in advance

Closing as #149 has been merged


:green_apple: fixbug:: windows os error

run windows10 x64, error "The handle is invalid."
core line:210
fd := int(os.Stdin.Fd()) in windows
https://github.com/golang/go/issues/27743

testing ok!~

PR ok!~

close

Merge pull request #1 from 48474/devlop


[Bug] Candlestick border mode issue

Version
5.5.0
Link to Minimal Reproduction
none
Steps to Reproduce
          type: "candlestick",
          data: data.values,
          itemStyle: {
            color: undefined,
            color0: undefined,
            borderColor: this.upColor,
            borderColor0: this.downColor,
          },

Current Behavior

Expected Behavior

Environment
- OS:
- Browser:
- Framework:
mac 13.1 (22C65)
chrome
vue2

Any additional comments?
Hi ,can I remove the middle line in the candlestick when I just want show borders?

data order should be OCLH - Demo

thx


#495: Merge history only when alter_history is set

Coverage increased (+0.02%) to 90.951% when pulling d1f55603fee8c257662f81b509e1f128afa0b1bc on scorphus:history-merge into f74bbb7a9ab4a9a91dbea31388b11b9db484cf17 on nvbn:master.

Thanks for pointing that out, @nvbn :+1:

Coverage increased (+0.03%) to 90.956% when pulling 96f7e53aa27f60938bbe4f2e1eb792fcb70cfcb9 on scorphus:history-merge into f74bbb7a9ab4a9a91dbea31388b11b9db484cf17 on nvbn:master.

Thanks!


docs: add wiki with examples

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Script not showing up - Please help

Hey! I am fairy new to stable diffusion world and I try to make sense of everything. I've respected all the installing steps but for some reason I can't make depth map to work. Check below:
Launching Web UI with arguments:
No module 'xformers'. Proceeding without it.
Error loading script: depthmap.py
Traceback (most recent call last):
File "C:\Users\chitu\stable-diffusion-webui\modules\scripts.py", line 229, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "C:\Users\chitu\stable-diffusion-webui\modules\script_loading.py", line 11, in load_module
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "C:\Users\chitu\stable-diffusion-webui\extensions\stable-diffusion-webui-depthmap-script\scripts\depthmap.py", line 54, in
from inpaint.mesh import write_ply, read_ply, output_3d_photo
File "C:\Users\chitu\stable-diffusion-webui\extensions/stable-diffusion-webui-depthmap-script/scripts\inpaint\mesh.py", line 22, in
from inpaint.utils import path_planning, open_small_mask, clean_far_edge, refine_depth_around_edge
File "C:\Users\chitu\stable-diffusion-webui\extensions/stable-diffusion-webui-depthmap-script/scripts\inpaint\utils.py", line 18, in
from skimage.feature import canny
File "C:\Users\chitu\stable-diffusion-webui\venv\lib\site-packages\skimage\feature_init.py", line 4, in
from ._cascade import Cascade
ImportError: DLL load failed while importing _cascade: The specified module could not be found.
Thanks!

I googled around, and some similar issues with skimage were solved by installing the  Microsoft Visual C++ Redistributable for Visual Studio : https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Solution for Mac
brew install ffmpeg

Thank you both. I could make it work later the same day by simply closing and opening SD probably for 2 times and anytime I have opened it it have downloaded more and more probably essential files.

Restarting the webUI solved the issue for me. It downloaded requirements upon opening that it had not installed when providing the link for webUI to install it in the extensions tab.


3.8.2 toOrderedMap and toOrderedSet incorrectly flowtyped

In version 3.8.2, flow typings of these functions are:
toOrderedMap(): Map<K,V>;
toOrderedSet(): Set<V>;

in here:
https://github.com/facebook/immutable-js/blob/v3.8.2/type-definitions/immutable.js.flow#L70
https://github.com/facebook/immutable-js/blob/v3.8.2/type-definitions/immutable.js.flow#L72
OrderedMap and OrderedSet types are even defined but they are not used:
https://github.com/facebook/immutable-js/blob/v3.8.2/type-definitions/immutable.js.flow#L545-L547
https://github.com/facebook/immutable-js/blob/v3.8.2/type-definitions/immutable.js.flow#L587-L589
This seems to cause flow errors anywhere where Immutable 3.8.2 is used with those functions (in latest 0.70 flow-bin versions). I tried to convert draft-js to use 3.8.2 and encountered this. Could we just simply convert to:
toOrderedMap(): OrderedMap<K,V>;
toOrderedSet(): OrderedSet<V>;

Here's what I mean (I'd make a PR but I can't target current master with this change based on 3.8.2 tag)
https://github.com/TomiS/immutable-js/commit/7521908c61e3c6c8f475dc466f216627a1a7b274

Unfortunately there are no plans to release new builds of v3 - all efforts are going towards a v4 release, where this issue has been fixed.
I believe the third-party flow types repo for immutable-js has corrected this issue?


Overhaul spec file

Do not try to own /usr/bin by claiming %{_bindir} in %files section.

Cease using %defattr(-,root,root,-), which does not set or alter any permissions due to twice "-" and root:root should be the automatically set by a recent rpm (v4.14 since SailfishOS 2.2.1) for files deployed to common directories.  %defattr is also mostly obsolete, see https://docs.fedoraproject.org/en-US/packaging-guidelines/#_file_permissions and https://pagure.io/packaging-committee/issue/77
→ Deferred for later, in order to have more time to thoroughly check that rpm automatically sets the correct permissions for all files sailfishos-chum-gui deploys without %defattr.  Another reason is, "not too many changes at once", even though they are trivial (because also typos are trivial (errors)).

No rm -rf  %{buildroot} in %install section: This is long obsolete (just as %clean is)!  rpm / rpmbuild does both automatically since long ago.

Only remove repositories via ssu rr when package is removed (not also when package is updated) in %postun section.

Formatting: Fix / enhance indentation at multiple places.

Increase version.

Append exit 0 to %postun scriptlet for safety and clarity.

Use shorter and simpler link to SVG icon.

Drop -n %{name}-%{version} for %setup, because that always has been the default.

lgtm

BTW, as @piggz correctly denoted, the old MR #124 should be reviewed (and maybe merged), first.
P.S.: Please mind the other open MRs for sailfishos-chum/main and sailfishos-chum-gui.

A maybe dumb question, because I may stick to a rule I do not fully comprehend and which may: "devel packages should be build-depended upon via pkgconfig(<package>)
So is BuildRequires:  PackageKit-Qt5-devel in line 27 correct or should it better be BuildRequires:  pkgconfig(PackageKit-Qt5)?
I know a .pc file has to exist for a devel-package to be supported by pkgconf / pkgconfig, but have no spontaneous idea where to look (reading documentation may alleviate that, some day).  Though I suppose thattere is one,
because pkcon -p search name pkgconf | grep -E '^Available|^Installed' | tr -s ' ' | cut -f 2 -d ' ' | grep PackageKit-Qt5
and pkcon -p search name pkgconfig | grep -E '^Available|^Installed' | tr -s ' ' | cut -f 2 -d ' ' | grep PackageKit-Qt5
both yield, e.g., PackageKit-Qt5-devel-0.9.6+git-1.3.1.jolla.armv7hl.

Oh, and I also wondered, if the two
%if 0%{?sailfishos_version} && 0%{?sailfishos_version} < 40?00 would be easier to comprehend if rewritten as
%if %{defined sailfishos_version} && 0%{?sailfishos_version} < 40?00 because that what they means, IIUC.
IMO both are equivalent, but I had to look at it for a while to understand that this is (supposedly) supposed to mean: IF sailfishos_version is defined AND sailfishos_version < 40?00`, THEN …
If I get a "go", I will also address this and / or the comment before this one.

A maybe dumb question, because I may stick to a rule I do not fully comprehend and which may not be applicable here: "devel packages should be build-depended upon via pkgconfig(<package>)"

I guess that is the recommended way, but it's not a strict rule, it depends on the build system of the dependee. IT might not be using pkgconfig, or prefer another way of finding the information such as cmake or qmake.

So is BuildRequires: PackageKit-Qt5-devel in line 27 correct or should it better be BuildRequires: pkgconfig(PackageKit-Qt5)?

~/tmp $ pkcon download . PackageKit-Qt5-devel
~/tmp $ rpm -qPp PackageKit-Qt5-devel-0.9.6+git-1.5.2.jolla.aarch64.rpm
PackageKit-Qt5-devel = 0.9.6+git-1.5.2.jolla
PackageKit-Qt5-devel(aarch-64) = 0.9.6+git-1.5.2.jolla
pkgconfig(packagekitqt5) = 0.9.7

Therefore, the correct dep is pkgconfig(packagekitqt5) for this package.

Thanks a lot @nephros for this concise explanation.
nephros commented 2 weeks ago:

I guess that is the recommended way, but it's not a strict rule, […]
[…], a possible correct dep is pkgconfig(packagekitqt5) for this package.

As pkgconfig is always deployed on SailfishOS and Jolla heavily uses it (this recommendation / rule I remembered is actually from a sailor), there seems to be no reason not to express this dependency as BuildRequires: pkgconfig(packagekitqt5).
OTOH I gather, that the current way of specifying this dependency is also 100% correct.

So ultimately I intend to defer these three changes to later, in order to get the safe and easy changes in, first:

BuildRequires: PackageKit-Qt5-devel in line 27 → BuildRequires: pkgconfig(packagekitqt5)
%defattr(-,root,root,-) →  , see second point of my original message here for details.
%if 0%{?sailfishos_version} && … → %if %{defined sailfishos_version} && …, see this message here for details.

Therefore, a possible correct dep is pkgconfig(packagekitqt5) for this package. But as Chum-GUI is CMake-based, the more generic -devel dep is fine, …

Unfortunately this turned out not to be true, see https://github.com/sailfishos-chum/sailfishos-chum-gui/issues/150#issuecomment-1426162902.

Well. There's the issue of build deps specification, and actual dependencies of a binary.

Oops, ACK.
So wrong consideration on my side, but still took a correct action.
Sorry, it is Friday night after an eventful working week.  My brain works at less than two thirds of its usual capacity.  Still I wanted to have these issues resolved, hence … "tunnel view".

(Btw: I wrote you an email about these dependency issues of this and another package you maintain, together with the solution (purpose-built binaries) very shortly after 4.5EA was announced, but it seems not to have arrived in time or at the correct place.)

Oops again, that was last Friday, which was worse than today, because the SFOS 4.5.0 EA release was published at noon that day.  Thanks for then email and the hint today, I now read it.  Ultimately I did the right thing last Friday night: Rebuild it against the SFOS <IP_ADDRESS> DoD repo at the SFOS-OBS.
But aaargl, just realised that the GitHub CI run builds will not install on SFOS 4.5.0 for all packages, which have a build time dependency on libsolv or PackageKit-Qt5-devel, because … Coderus did his job, but I did not update the CI workflow configuration files, yet.
Thank you very much!


url-0.5.9: could not parse input as TOML

As seen in rusoto at 76c7c56, where we're still using an old version of url, 0.5.9:
$ cargo tree gives
error: unable to get packages from source

Caused by:
  failed to parse manifest at `/Users/matthew/.cargo/registry/src/github.com-1ecc6299db9ec823/url-0.5.9/Cargo.toml`

Caused by:
  could not parse input as TOML
/Users/matthew/.cargo/registry/src/github.com-1ecc6299db9ec823/url-0.5.9/Cargo.toml:14:3 expected a newline after table definition

error:

Line in file specified:
[[test]] name = "format"

Updating url to the latest version, 1.1.1, allows cargo tree to work as expected.  Is this a bug in pre-1.0.0 url or cargo-tree?

That's a bug in pre-1.0.0 url, I believe due to a fix in the toml crate to stop parsing invalid syntax: https://github.com/alexcrichton/toml-rs/pull/94

Thanks, sounds like this issue is invalid and should be closed. 😄


Suggest Configurator

I can suggest to create one configuration file to choose where the file must be write.
It is possible

Thanks for your suggestion.
Because it is a "library" and it doesn't support configurable files.
But you can load log file path from configuration file in your app, then pass it to adapter:
// Attach single or multiple adapters
$logger = new Logger();

// Load log file path
$logFilePath = '/path/to/file.log';

$logger->attachAdapter(new FileAdapter($logFilePath));

// You can pass message to these log levels
$logger->emergency('Something did not work');

Is it what you want?


Movement speed for groups isn't working

Describe the bug
I noticed group speed is supported. However, it's not working in my game.
To Reproduce

Create a group actor with a movement speed
Drag the token on a map

Expected behavior
The token's movement speed should be colored correctly.
Screenshots

Additional context
From what I can see, the data needed is in token.document.actor.system.attributes.movement, even for group tokens.

Thank you, the system must have changed it at some point. Fixed in 1.9.4.


Update get-started-analyze-storage.md

Fixed typo

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

Thanks for the grammar/typo fix, @SanderVHGD.


Support switching cloud profile referenced in Shoot from NamespacedCloudProfile to parent CloudProfile.

How to categorize this PR?

/area usability
/kind enhancement
What this PR does / why we need it:
Allow for switching between related NamespacedCloudProfiles as well as back and forth between the related CloudProfile and NamespacedCloudProfiles.
As noted here.
Which issue(s) this PR fixes:
Part of https://github.com/gardener/gardener/issues/9504
Special notes for your reviewer:
/cc @timuthy
Release note:

Allow changing `shoot.spec.cloudProfile` between `CloudProfile` and its descendant `NamespacedCloudProfile`s.

/lgtm
/approve


cmd: Use HTTP roundtripper from scorecard

When scorecard moved to v2, support for older GitHub clients in
CheckRequest was dropped, which means any means of GitHub
authentication instantiated within allstar gets dropped as well.
Specifically, this affects the binary artifacts policy check.
Here, we opt to use scorecard's HTTP roundtripper in
NewGHClients, which should allow us to seed GitHub credentials
in the same way that scorecard does.
Unfortunately, this has the mild side-effect of temporarily
introducing zap as a logger for a small portion of the code (but
this will be removed again once we move to scorecard/v4).
Signed-off-by: Stephen Augustus<EMAIL_ADDRESS>

From https://twitter.com/stephenaugustus/status/1493660282886967297:

I wrote some code yesterday and then realized (the second I closed my laptop), "Wow, this does not solve the problem at all!"

I think I need to expose some options in the scorecard GitHub client for these to play nicely together...

I don't think we want to use the scorecard transport, we want to override it and provide our own. I just opened https://github.com/ossf/scorecard/pull/1644 which is what I think we need to then update the Allstar code.

I don't think we want to use the scorecard transport, we want to override it and provide our own. I just opened ossf/scorecard#1644 which is what I think we need to then update the Allstar code.

Agreed! Superseded by https://github.com/ossf/scorecard/pull/1644 and https://github.com/ossf/allstar/pull/101.


FEAT-#6735: Make Modin on MPI through unidist component more obvious

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #6735
[x] tests passing
[x] module layout described at docs/development/architecture.rst is up-to-date

Blocked for merging but open for review. Once unidist 0.5.0 is available both on PyPI and conda-forge, I will rebase on master to run CI again to check if tests pass.

@YarShev with the new Unidist release, all of Modin’s previous releases on Unidist break (at least installation with pip). I only know a way to fix it using an explicit unidist pin: <0.0.5. Do you know a better solution?

@YarShev with the new Unidist release, all of Modin’s previous releases on Unidist break (at least installation with pip). I only know a way to fix it using an explicit unidist pin: <0.5.0. Do you know a better solution?

@anmyachev, I want to say that this is not a bug. This is a feature, which allows to use more recent MPICH and Python versions, as well as use other MPI implementations to run on. As of unidist 0.5.0 it is required to have a working MPI implementation installed beforehand. As far as I can tell, there is no anything we can do with the previous releases of modin-unidist working out of the box other than 1) specify the exact version of unidist when installing (pip install modin-unidist unidist-mpi<=0.4.1) or 2) wait for mpi4py releases on PyPI that have a pre-built MPI implementation and thus work out of the box.
Note: we are talking only about pip.

@YarShev CI is failed

@YarShev CI is failed

I see, looking into this.

Rebased just to rerun CI.


[1.18.2] Game Crashes when opening the Config

hi,
the game instantly crashed when I open the config. I tried it through "Options > MoreCommands" and through Mod-Menü and the setting button
Game Version: 1.18.2
Fabric 0.13.3-1.18.2
MoreCommands-3.10_1.16.4-22w15a
Modlist:

This player seems to have the same problem:
https://www.curseforge.com/minecraft/mc-mods/morecommands?comment=469
crash-2022-04-23_23.31.14-client.txt
.

This is known and has been fixed in the upcoming release.
No issue has been made for this bug as it has been reported to me via Discord.


can upgrade-assistant support to convert VB.net winforms to C# winforms or web application

can upgrade-assistant support to convert VB.net winforms to C# winforms or web application?
we have an application in VB.net winforms. our goal is to convert to C# web application and migrate to .NET 5 version. Please suggest the best approach.

Hi @ajaybabuthota, we're working on adding VB support right now. With the next release of Upgrade Assistant, it should be possible to upgrade VB.NET WinForms apps to target .NET 5. They will still be VB WinForms apps after upgrade, though (just targeting .NET 5). If you want to migrate to C# or a web application, those changes will need to be done outside of the tool.


Pain moans ignore arousal level

Hello!
It looks like currently (actually it's like this for quite some time) pain moans ignore arousal level.
I tried debugging and it seems here
 function M_MOANER_miscReactions(data) {
        var Factor = Math.floor(Player.ArousalSettings.Progress / 20);
        //get the moan type to apply
        //data to generate the moans
        if (reaction == 1) {
            var moan = getPainMoan(Factor, Math.random() * 300);
        }

expectation is, that getPainMoan(Factor, seed) will be called, but it's actually getPainMoan().
Turns out (surprising to me) JavaScript doesn't support function overloading and that's probably why it didn't work as I assume is expected.
The most simple way to fix this would be giving these two functions different names.
Same problem probably exists with getTickleMoan() and getTickleMoan(Factor, seed). I'm not sure if there are other cases.

Thanks for reporting the issue ... I will take a look and make some tests

Well, renaming one of the functions will not make the Moaner work as you think, because actually the arousal level is not linked to specific moans for the spank or the tickle activity, but to specific moans to the change of vibe level (and activities considered as similar). It was designed like that since the beginning in the original stand-alone Moaner for the Spank activity and I've followed the same approach when adding the Tickle activity.
If you look at the Moaner profiles, you will see that the arousal levels are independant from the spank and tickle activities.

But apparently, the function was getSpankMoan(Factor, seed) { in the original Moaner. So I guess the confusion comes from a change I've made later.

Anyway, I will leave it as it is. Changing names of one of the functions has as effect nothing or that no any moan is produced, according the function whose name is changed.

I'm still doing tests ... Maybe I will find the trick!

Thanks for looking into it.
The thing is, I remember it working differently before in UBC/QAM. Originally when my character was spanked it were pleasure moans. I assumed it was because of activity preference settings, so GetActivityTaste seems like a good lead.
The part about changing function names was just a guess to be honest as I didn't
want to make a working fork just to test a simple change. And also didn't manage to make local script override work.

It's probably wrong since Ben has compressed Player.ArousalSettings.Activity
So the conditions to distinct pain and pleasure need to be written differently!

Finally found how to fix that. Your first guess was useful too, I need indeed to change the name of the 'simplified' function, but it was not enough: I had to read differently the content of Player.ArousalSettings.Activity.
I will make later a hotfix.

Hotfix done :)
Thanks again for your report!


Make pyproject.toml a selectable option when creating environments

Type: Bug

Behaviour
Expected vs. Actual
Expected: Leaving all dependency sources (requirements.txt, pyproject.toml) unchecked should not build and install any dependencies from these files.
Actual: Dependencies in pyproject.toml are built and installed during the creation of the virtual environment.
Steps to reproduce:

Clone the repository https://github.com/abetlen/llama-cpp-python (with submodules!) and open it in Visual Studio Code.
Open the Command Palette and run Python: Create environment
Choose to create a .venv type environment.
In the dialogs that follow, make sure that none of the requirements.txt or pyproject.toml files are selected for installing dependencies, e.g. hit Enter while keyboard focus is in the topmost edit box, without any of the checkboxes checked.

Note that I had to run these steps twice to even get a working Python virtual environment, because installing the dependencies from pyproject.toml forced me to install some tools which I didn't have installed at the time (because I don't need them for what I want to do (edit and lint Python code)) before I could retry creating the virtual environment.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2023-09-16 15:56:39.738 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-09-16 15:56:39.738 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-09-16 15:56:39.738 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2023-09-16 15:56:39.738 [info] Experiment 'pythonTestAdapter' is active
2023-09-16 15:56:39.738 [info] Test server listening.
2023-09-16 15:56:39.738 [info] > conda info --json
2023-09-16 15:56:39.739 [info] Found: /bin/python3 --> /bin/python3.10
2023-09-16 15:56:39.739 [info] Found: /bin/python3.10 --> /bin/python3.10
2023-09-16 15:56:39.745 [info] Found: /usr/bin/python3 --> /usr/bin/python3.10
2023-09-16 15:56:39.745 [info] Found: /usr/bin/python3.10 --> /usr/bin/python3.10
2023-09-16 15:56:40.940 [info] > /bin/python3 -I ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/interpreterInfo.py
2023-09-16 15:56:41.045 [info] > /usr/bin/python3 -I ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/interpreterInfo.py
2023-09-16 15:56:41.118 [info] Python interpreter path: /bin/python3
2023-09-16 15:56:43.168 [info] Starting Pylance language server.
2023-09-16 15:58:57.288 [info] Selected workspace /mnt/d/git/llama-cpp-python for creating virtual environment.
2023-09-16 15:59:14.887 [info] Selected interpreter /bin/python3 for creating virtual environment.
2023-09-16 15:59:49.677 [info] Running Env creation script:  [
  '/bin/python3',
  '/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py',
  '--git-ignore',
  '--toml',
  '/mnt/d/git/llama-cpp-python/pyproject.toml'
]
2023-09-16 15:59:49.718 [info] Running: /bin/python3 -m venv --without-pip .venv

2023-09-16 15:59:50.284 [info] CREATED_VENV:/mnt/d/git/llama-cpp-python/.venv/bin/python

2023-09-16 15:59:50.284 [info] Creating: /mnt/d/git/llama-cpp-python/.venv/.gitignore

2023-09-16 15:59:50.318 [info] CREATE_VENV.DOWNLOADING_PIP

2023-09-16 15:59:50.643 [info] CREATE_VENV.INSTALLING_PIP
Running: /mnt/d/git/llama-cpp-python/.venv/bin/python /mnt/d/git/llama-cpp-python/.venv/pip.pyz install pip

2023-09-16 15:59:54.912 [info] Collecting pip

2023-09-16 15:59:54.912 [info]   Obtaining dependency information for pip from https://files.pythonhosted.org/packages/50/c2/e06851e8cc28dcad7c155f4753da8833ac06a5c704c109313b8d5a62968a/pip-23.2.1-py3-none-any.whl.metadata

2023-09-16 15:59:55.008 [info]   Downloading pip-23.2.1-py3-none-any.whl.metadata (4.2 kB)

2023-09-16 15:59:55.024 [info] Downloading pip-23.2.1-py3-none-any.whl (2.1 MB)

2023-09-16 15:59:55.134 [info]    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.1/2.1 MB 20.3 MB/s eta 0:00:00
2023-09-16 15:59:55.134 [info]

2023-09-16 15:59:55.145 [info] Installing collected packages: pip

2023-09-16 16:00:51.997 [info] Successfully installed pip-23.2.1

2023-09-16 16:00:52.527 [info] VENV_INSTALLING_PYPROJECT: /mnt/d/git/llama-cpp-python/pyproject.toml
Running: /mnt/d/git/llama-cpp-python/.venv/bin/python -m pip install -e .

2023-09-16 16:01:04.076 [info] Obtaining file:///mnt/d/git/llama-cpp-python

2023-09-16 16:01:04.107 [info]   Installing build dependencies: started

2023-09-16 16:01:20.585 [info]   Installing build dependencies: finished with status 'done'

2023-09-16 16:01:20.586 [info]   Checking if build backend supports build_editable: started

2023-09-16 16:01:20.965 [info]   Checking if build backend supports build_editable: finished with status 'done'

2023-09-16 16:01:20.967 [info]   Getting requirements to build editable: started

2023-09-16 16:01:22.228 [info]   Getting requirements to build editable: finished with status 'done'

2023-09-16 16:01:22.264 [info]   Installing backend dependencies: started

2023-09-16 16:01:37.826 [info]   Installing backend dependencies: finished with status 'done'

2023-09-16 16:01:37.827 [info]   Preparing editable metadata (pyproject.toml): started

2023-09-16 16:01:38.908 [info]   Preparing editable metadata (pyproject.toml): finished with status 'done'

2023-09-16 16:01:39.497 [info] Collecting typing-extensions>=4.5.0 (from llama_cpp_python==0.2.4)

2023-09-16 16:01:39.497 [info]   Obtaining dependency information for typing-extensions>=4.5.0 from https://files.pythonhosted.org/packages/ec/6b/63cc3df74987c36fe26157ee12e09e8f9db4de771e0f3404263117e75b95/typing_extensions-4.7.1-py3-none-any.whl.metadata

2023-09-16 16:01:39.604 [info]   Downloading typing_extensions-4.7.1-py3-none-any.whl.metadata (3.1 kB)

2023-09-16 16:01:40.070 [info] Collecting numpy>=1.20.0 (from llama_cpp_python==0.2.4)

2023-09-16 16:01:40.070 [info]   Obtaining dependency information for numpy>=1.20.0 from https://files.pythonhosted.org/packages/71/3c/3b1981c6a1986adc9ee7db760c0c34ea5b14ac3da9ecfcf1ea2a4ec6c398/numpy-1.25.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata

2023-09-16 16:01:40.100 [info]   Downloading numpy-1.25.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (5.6 kB)

2023-09-16 16:01:40.399 [info] Collecting diskcache>=5.6.1 (from llama_cpp_python==0.2.4)

2023-09-16 16:01:40.399 [info]   Obtaining dependency information for diskcache>=5.6.1 from https://files.pythonhosted.org/packages/3f/27/4570e78fc0bf5ea0ca45eb1de3818a23787af9b390c0b0a0033a1b8236f9/diskcache-5.6.3-py3-none-any.whl.metadata

2023-09-16 16:01:40.442 [info]   Downloading diskcache-5.6.3-py3-none-any.whl.metadata (20 kB)

2023-09-16 16:01:40.483 [info] Downloading diskcache-5.6.3-py3-none-any.whl (45 kB)

2023-09-16 16:01:40.497 [info]    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 45.5/45.5 kB 4.4 MB/s eta 0:00:00
2023-09-16 16:01:40.497 [info]

2023-09-16 16:01:40.528 [info] Downloading numpy-1.25.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (18.2 MB)

2023-09-16 16:01:40.930 [info]    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 18.2/18.2 MB 67.9 MB/s eta 0:00:00
2023-09-16 16:01:40.930 [info]

2023-09-16 16:01:40.965 [info] Downloading typing_extensions-4.7.1-py3-none-any.whl (33 kB)

2023-09-16 16:01:40.993 [info] Building wheels for collected packages: llama_cpp_python

2023-09-16 16:01:40.995 [info]   Building editable for llama_cpp_python (pyproject.toml): started

2023-09-16 16:01:47.571 [info]   Building editable for llama_cpp_python (pyproject.toml): finished with status 'error'

2023-09-16 16:01:47.576 [info]   error: subprocess-exited-with-error

  × Building editable for llama_cpp_python (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [26 lines of output]
      *** scikit-build-core 0.5.0 using CMake 3.27.4 (editable)
      *** Configuring CMake...
      2023-09-16 16:01:42,035 - scikit_build_core - WARNING - libdir/ldlibrary: /usr/lib/x86_64-linux-gnu/libpython3.10.so is not a real file!
      2023-09-16 16:01:42,036 - scikit_build_core - WARNING - Can't find a Python library, got libdir=/usr/lib/x86_64-linux-gnu, ldlibrary=libpython3.10.so, multiarch=x86_64-linux-gnu, masd=x86_64-linux-gnu
      loading initial cache file /tmp/tmpiik4z0u5/build/CMakeInit.txt
      -- The C compiler identification is unknown
      -- The CXX compiler identification is unknown
      CMake Error at CMakeLists.txt:3 (project):
        No CMAKE_C_COMPILER could be found.

        Tell CMake where to find the compiler by setting either the environment
        variable "CC" or the CMake cache entry CMAKE_C_COMPILER to the full path to
        the compiler, or to the compiler name if it is in the PATH.

      CMake Error at CMakeLists.txt:3 (project):
        No CMAKE_CXX_COMPILER could be found.

        Tell CMake where to find the compiler by setting either the environment
        variable "CXX" or the CMake cache entry CMAKE_CXX_COMPILER to the full path
        to the compiler, or to the compiler name if it is in the PATH.

      -- Configuring incomplete, errors occurred!

      *** CMake configuration failed
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.

2023-09-16 16:01:47.576 [info]   ERROR: Failed building editable for llama_cpp_python

2023-09-16 16:01:47.576 [info] Failed to build llama_cpp_python

2023-09-16 16:01:47.577 [info] ERROR: Could not build wheels for llama_cpp_python, which is required to install pyproject.toml-based projects

2023-09-16 16:01:47.812 [info] Traceback (most recent call last):
  File "/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py", line 84, in run_process

2023-09-16 16:01:47.812 [info]     subprocess.run(args, cwd=os.getcwd(), check=True)
  File "/usr/lib/python3.10/subprocess.py", line 526, in run

2023-09-16 16:01:47.813 [info]     raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/mnt/d/git/llama-cpp-python/.venv/bin/python', '-m', 'pip', 'install', '-e', '.']' returned non-zero exit status 1.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py", line 250, in <module>

2023-09-16 16:01:47.814 [info]     main(sys.argv[1:])
  File "/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py", line 241, in main
    install_toml(venv_path, args.extras)
  File "/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py", line 113, in install_toml
    run_process(
  File "/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py", line 86, in run_process
    raise VenvError(error_message)
__main__.VenvError: CREATE_VENV.PIP_FAILED_INSTALL_PYPROJECT

2023-09-16 16:01:47.824 [error] Error while running venv creation script:  CREATE_VENV.PIP_FAILED_INSTALL_PYPROJECT
2023-09-16 16:01:47.824 [error] CREATE_VENV.PIP_FAILED_INSTALL_PYPROJECT
2023-09-16 16:11:09.598 [info] Selected workspace /mnt/d/git/llama-cpp-python for creating virtual environment.
2023-09-16 16:11:19.758 [info] Selected interpreter /bin/python3 for creating virtual environment.
2023-09-16 16:12:01.514 [info] Deleted venv dir: /mnt/d/git/llama-cpp-python/.venv
2023-09-16 16:12:01.523 [info] Running Env creation script:  [
  '/bin/python3',
  '/home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/create_venv.py',
  '--git-ignore',
  '--toml',
  '/mnt/d/git/llama-cpp-python/pyproject.toml'
]
2023-09-16 16:12:01.584 [info] Running: /bin/python3 -m venv --without-pip .venv

2023-09-16 16:12:01.783 [info] CREATED_VENV:/mnt/d/git/llama-cpp-python/.venv/bin/python

2023-09-16 16:12:01.783 [info] Creating: /mnt/d/git/llama-cpp-python/.venv/.gitignore

2023-09-16 16:12:01.908 [info] CREATE_VENV.DOWNLOADING_PIP

2023-09-16 16:12:02.011 [info] CREATE_VENV.INSTALLING_PIP
Running: /mnt/d/git/llama-cpp-python/.venv/bin/python /mnt/d/git/llama-cpp-python/.venv/pip.pyz install pip

2023-09-16 16:12:06.020 [info] Collecting pip

2023-09-16 16:12:06.020 [info]   Obtaining dependency information for pip from https://files.pythonhosted.org/packages/50/c2/e06851e8cc28dcad7c155f4753da8833ac06a5c704c109313b8d5a62968a/pip-23.2.1-py3-none-any.whl.metadata

2023-09-16 16:12:06.021 [info]   Using cached pip-23.2.1-py3-none-any.whl.metadata (4.2 kB)

2023-09-16 16:12:06.029 [info] Using cached pip-23.2.1-py3-none-any.whl (2.1 MB)

2023-09-16 16:12:06.039 [info] Installing collected packages: pip

2023-09-16 16:13:02.609 [info] Successfully installed pip-23.2.1

2023-09-16 16:13:02.822 [info] VENV_INSTALLING_PYPROJECT: /mnt/d/git/llama-cpp-python/pyproject.toml
Running: /mnt/d/git/llama-cpp-python/.venv/bin/python -m pip install -e .

2023-09-16 16:13:14.394 [info] Obtaining file:///mnt/d/git/llama-cpp-python

2023-09-16 16:13:14.433 [info]   Installing build dependencies: started

2023-09-16 16:13:30.261 [info]   Installing build dependencies: finished with status 'done'

2023-09-16 16:13:30.262 [info]   Checking if build backend supports build_editable: started

2023-09-16 16:13:30.610 [info]   Checking if build backend supports build_editable: finished with status 'done'

2023-09-16 16:13:30.611 [info]   Getting requirements to build editable: started

2023-09-16 16:13:31.879 [info]   Getting requirements to build editable: finished with status 'done'

2023-09-16 16:13:31.911 [info]   Installing backend dependencies: started

2023-09-16 16:13:46.620 [info]   Installing backend dependencies: finished with status 'done'

2023-09-16 16:13:46.620 [info]   Preparing editable metadata (pyproject.toml): started

2023-09-16 16:13:47.648 [info]   Preparing editable metadata (pyproject.toml): finished with status 'done'

2023-09-16 16:13:48.220 [info] Collecting typing-extensions>=4.5.0 (from llama_cpp_python==0.2.4)

2023-09-16 16:13:48.220 [info]   Obtaining dependency information for typing-extensions>=4.5.0 from https://files.pythonhosted.org/packages/ec/6b/63cc3df74987c36fe26157ee12e09e8f9db4de771e0f3404263117e75b95/typing_extensions-4.7.1-py3-none-any.whl.metadata

2023-09-16 16:13:48.222 [info]   Using cached typing_extensions-4.7.1-py3-none-any.whl.metadata (3.1 kB)

2023-09-16 16:13:48.633 [info] Collecting numpy>=1.20.0 (from llama_cpp_python==0.2.4)

2023-09-16 16:13:48.634 [info]   Obtaining dependency information for numpy>=1.20.0 from https://files.pythonhosted.org/packages/71/3c/3b1981c6a1986adc9ee7db760c0c34ea5b14ac3da9ecfcf1ea2a4ec6c398/numpy-1.25.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata

2023-09-16 16:13:48.635 [info]   Using cached numpy-1.25.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl.metadata (5.6 kB)

2023-09-16 16:13:48.901 [info] Collecting diskcache>=5.6.1 (from llama_cpp_python==0.2.4)

2023-09-16 16:13:48.902 [info]   Obtaining dependency information for diskcache>=5.6.1 from https://files.pythonhosted.org/packages/3f/27/4570e78fc0bf5ea0ca45eb1de3818a23787af9b390c0b0a0033a1b8236f9/diskcache-5.6.3-py3-none-any.whl.metadata

2023-09-16 16:13:48.903 [info]   Using cached diskcache-5.6.3-py3-none-any.whl.metadata (20 kB)

2023-09-16 16:13:48.908 [info] Using cached diskcache-5.6.3-py3-none-any.whl (45 kB)

2023-09-16 16:13:48.943 [info] Using cached numpy-1.25.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (18.2 MB)

2023-09-16 16:13:48.963 [info] Using cached typing_extensions-4.7.1-py3-none-any.whl (33 kB)

2023-09-16 16:13:48.984 [info] Building wheels for collected packages: llama_cpp_python

2023-09-16 16:13:48.985 [info]   Building editable for llama_cpp_python (pyproject.toml): started

2023-09-16 16:14:02.724 [info]   Building editable for llama_cpp_python (pyproject.toml): finished with status 'done'

2023-09-16 16:14:02.726 [info]   Created wheel for llama_cpp_python: filename=llama_cpp_python-0.2.4-cp310-cp310-manylinux_2_35_x86_64.whl size=921377 sha256=a18eb9ea296782fa2ff07b765d218acda0f1450c307a6622dc06da244376f058

2023-09-16 16:14:02.726 [info]   Stored in directory: /tmp/pip-ephem-wheel-cache-_u077z2v/wheels/c6/c9/22/31bac3ad9c62a2b3c4db79b3a4b417d3614d6dce3cbd3d47df

2023-09-16 16:14:02.728 [info] Successfully built llama_cpp_python

2023-09-16 16:14:02.759 [info] Installing collected packages: typing-extensions, numpy, diskcache, llama_cpp_python

2023-09-16 16:15:16.018 [info] Successfully installed diskcache-5.6.3 llama_cpp_python-0.2.4 numpy-1.25.2 typing-extensions-4.7.1

2023-09-16 16:15:16.301 [info] CREATE_VENV.PIP_INSTALLED_PYPROJECT

2023-09-16 16:15:16.481 [info] > ./.venv/bin/python -I ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/get_output_via_markers.py ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/interpreterInfo.py
2023-09-16 16:15:16.577 [info] Discover tests for workspace name: llama-cpp-python - uri: /mnt/d/git/llama-cpp-python
2023-09-16 16:15:16.578 [info] Python interpreter path: ./.venv/bin/python
2023-09-16 16:15:16.610 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/printEnvVariables.py
2023-09-16 16:15:16.610 [info] shell: bash
2023-09-16 16:15:16.750 [info] > /bin/python3 ~/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/printEnvVariables.py
2023-09-16 16:15:16.750 [info] shell: bash
2023-09-16 16:16:31.825 [info] Running installed packages checker:  /mnt/d/git/llama-cpp-python/.venv/bin/python /home/miki/.vscode-server-insiders/extensions/ms-python.python-2023.17.12582041/pythonFiles/installed_check.py /mnt/d/git/llama-cpp-python/pyproject.toml

User Settings

languageServer: "Pylance"

Extension version: 2023.17.12582041
VS Code version: Code - Insiders 1.83.0-insider (bccfade64adb249f57c8fcf03cba41609f76ce5c, 2023-09-15T05:35:16.508Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i5-12400F (12 x 2496)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.79GB (6.80GB free)

Process Argv
--crash-reporter-id 78c6d751-e4b0-4959-a782-10106e5f6b9d

Screen Reader
yes

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
12th Gen Intel(R) Core(TM) i5-12400F (12 x 2496)

Memory (System)
7.65GB (6.42GB free)

VM
0%

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vsdfh931cf:30280410
vshan820:30294714
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30404738
py29gd2263:30784851
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30618038
a9j8j154:30646983
showlangstatbar:30737417
57b77579:30687741
pythonfmttext:30716741
fixshowwlkth:30771523
showindicator:30805243
pythongtdpath:30726887
i26e3531:30792625
welcomedialog:30812478
pythonnosmt12:30779711
pythonidxpt:30768918
pythonnoceb:30776497
copilotsettingt:30808721
asynctok:30821568
dsvsc013:30777762
dsvsc014:30777825
diffeditorv2:30786206
pythonlinttype:30823781
pythonmpsinfo:30815194
dsvsc015:30821418
pythontestfixt:30826906
pythonfb280951:30830809

Currently, the Create Environment command installs pyproject.toml if it has a build.system table in it. The intent with this command is that it tries to follow the recommendations of the project. The choice you get with TOML currently is only if you have optional.dependencies table.
We discussed this with this team and we plan on making TOML a selectable option. Note that, when TOML is selected we do an editable install with the project. so, it will require and install any dependencies that are required by the project. If you want to create an environment and want to set it up in a particular way you will have to manually create it.

I think this is works now when I have tried something similar- let me know if you are still seeing this and I can re-open. Thanks


Check for username/email duplicate when updating

connects #124

@cheungpat, thanks for your PR! By analyzing the annotation information on this pull request, we identified @rickmak to be a potential reviewer

Merge via c745671


develop php and python code advanced autocompletion speed so slowly

Issue Type: Feature Request
Does anyone else have this problem?I asked a few of my friends, and so it was
VS Code version: Code 1.24.1 (24f62626b222e9a8313213fb64b10d741a326288, 2018-06-13T17:51:32.889Z)
OS version: Windows_NT x64 10.0.17134

This sounds like an issue with extensions you're using for php/python intellisense. Please file specific issues with more details on those extensions.


feature: make all classes in the common module hashable

hashability and comparability is useful in many usecases, e.g. when using results as dict key
hashability could be achieved by setting frozen = True, but that would be an obstacle to backwards compatibility and makes it harder to understand the code, especially for people not familiar with pydantic
implementation of eq is verbose to make it explicit, could use hash(self)==hash(other) as well
hash and comparison of Part classes excludes id field as it generally has no real-world meaning and can be derived e.g. from an objects index in the parent route instance.

While working on the code I also did some refactoring to reduce duplication, i.e. I introduced an abstract base class for the parts which contains the fields that are common to all Part classes

Everything else looks good for me but if we implement hash and eq for basic classes, we'll need to implement for all classes

Everything else looks good for me but if we implement hash and eq for basic classes, we'll need to implement for all response classes too

Absolutely agree with you, and probably for a few others as well. I suggest keeping the PR here open until we step by step added hashability to more classes.
I also added it to ArrivalSearch and DepartureSearch as I had a use case where I wanted to use them as dict key and the corresponsing response as values and I assume that's also a common use case. To make that work the components in the transportation DTOs module  had to become hashable as well.

One more comment:
For me the SDK has two main uses:

automated parsing of API responses into useful objects (especially useful for the deeply nested responses, like the route property of the TimeFilter API)
Pydantic models that reflect what the API accepts so I don't have to check the API documentation all the time
methods to efficiently bundle and unbundle searches into requests

However in the end I need to make own calculations with the response, so when I receive route I might want to calculate the min time between public transport parts. I could use a function for that that accepts a Route instance or a list of Part instances, but that's not good coding practice in my opinion. Instead I'd prefer to have an min_change_time method on the Route class itself. I could do that by creating my own MyRoute clsas but that means I have to convert all Route instances which requires conversion and that's not good for performance.
I could monkeypatch the SDK's Route class but that's ugly as well.
The best option would be to be able to add some sort of config to the SDK class and save subclasses of Route there and to let the __parse_response method make use of either the default classes or whatever has been passed as custom subclasses.

Okey, thanks @MxMartin for you review, I'll think how to do it and add some new issue. If you need something from sdk, write it in issues, please, so we won't forget about it.
And it'd be nice if you could share with us some code samples how you use our sdk and your modifications, so we'll know how to improve it.


build: add an explicit link to BlocksRuntime

The SDK overlay requires the BlocksRuntime but did not explicitly link
to it.  This works on most platforms, however, Windows requires that all
symbols are fully resolved (effectively -z defs on Linux).  Add the
missing dependency.

CC: @MadCoder @ktopley-apple

@swift-ci please test


Invalid Response from URL

Command and response
root@6e1626550a7c:/workspace/poddl# ./poddl http://www.secondfront.com/podcasts/rss.xml ./tmp
poddl 2024.01.26
libcurl/8.4.0 mbedTLS/3.5.0
https://www.fredrikblank.com/poddl/
Fetching URL: http://www.secondfront.com/podcasts/rss.xml
Error: Invalid response from URL
What I've Done
Download compiled source, unzipped and ran command
Have attempted with multiple urls to include

http://www.secondfront.com/podcasts/rss.xml
https://chinahistorypodcast.libsyn.com/rss
https://cowenconvos.libsyn.com/rss

Any ideas on what I am doing wrong?

Thanks!
Feed 1 has no  tags in it. So maybe a another format I need to support.
But feed 2 and 3 seems to work just fine 🤔


Update commands and README

With the naming change, we need to update verticalab commands.
We also need to clean up the README.

@roypaulin do we close this one?

Yes It has already resolved


Update version for the next release (v0.17.0)

This version makes this package compatible with Meilisearch v0.27.0 :tada:
Check out the changelog of Meilisearch v0.27.0 for more information on the changes.
⚠ Breaking changes

Remove jsonindex (#278) @abhizer

🚀 Enhancements

Add cli-app example to meilisearch-rust (#279) @salugi
Ensure nested field support (#273) @bidoubiwa
Add new search parameters highlightPreTag, highlightPostTag and cropMarker (#274) @bidoubiwa
Add User-Agent header to have analytics in every HTTP request (#254) @brunoocasali

Analytics is enabled by default in the server, but you can disable them by following this guide
Also, of course, every analytics data we collect are ANONYMOUS read the guide for more information.
Thanks again to @abhizer, @bidoubiwa,  @irevoire, @salugi and a1! 🎉

bors merge

I merged it but I should have checked before: not all the files required to be up-to-date to for a release are not updated.
https://github.com/meilisearch/meilisearch-rust/runs/6351217073?check_suite_focus=true


How to use folders langs ?

Can I use folders with translates?
Like this:

en (forder)
-- app.json
-- common.json
...

It's not possible. But there is an issue for that already: #498


Accessibility issue with jaws (header and text read in one word instead of two)

Hello,
I am navigating with jaws and IE11 on this example when it's stacked :  http://filamentgroup.github.io/tablesaw/demo/stackonly.html
For exemple, when I navigate to the year 2009 it will read year2009 like so all together.
The html that table saw renders is this :
Year2009
I think you would need a space between the  tag and the  tag.
Thanks!

Thank you for filing this! The fix will be included with upcoming version v3.1.0.


How to check log files

I have sucessful install the docker and run it, but I cant find where the log files are located on docker

/root/.chia/mainnet/log/debug.log
The loglevel is set to INFO by default. If there is no logfile, there are no log messages "higher" than INFO (WARN, ERR, etc)

/root/.chia/mainnet/log/debug.log
The loglevel is set to INFO by default. If there is no logfile, there are no log messages "higher" than INFO (WARN, ERR, etc)

That doesn't show log info from the docker container harvester node. Only on the farm node where the farm node has plot directories pointed to it.

/root/.chia/mainnet/log/debug.log
The loglevel is set to INFO by default. If there is no logfile, there are no log messages "higher" than INFO (WARN, ERR, etc)

That doesn't show log info from the docker container harvester node. Only on the farm node where the farm node has plot directories pointed to it.

It does for me in harvester mode.. set the loglevel to INFO, restart the container, check again..


(better) transition time configuration for lights

It turned out to be easier than I thought to use a settings variable in an adapter. As you can see all adapter files with outbound commands had to be modified. I don't own all of these devices, so I can't test everything. It works fine on my hue lights without disturbing other devices though and I see no reason why it would influence any other adapters. The variable is passed along but not used in most adapters.
I made it a dictionary, so you could add extra parameters in the future, without having to modify the adapters again.

@d-EScape Hi, first of all thank you for the PR. I'm thinking how to better handle this: maybe there is a way to set transition time individually for each device which support it

@d-EScape I will close PR for now, as this option doesn't look so widely useful to make own config for it.


⚠ Bofrost.nl has degraded performance

In 2609da8, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1664 ms

Resolved: Bofrost.nl performance has improved in bf546c0.


Use timestamp from last git commit if available

If you use GitHub Actions to build the site, it will always use the current date for the "updated at" value of each page, because that's the date of the checkout. Instead use the date of the last commit for each file instead, if it is available.

Great catch! 😊
However, while your proposed solution works great within the context of GitHub Actions, it's not ideal in other use cases – take mine:

I've got my personal instance of nyum in a Git repository, but I use the included deploy.sh. Now if there's an .md not (yet) noted in at least one Git commit (which frequently occurs when adding a new recipe and checking whether I've made any typos or messed up the formatting), the git log output will be empty.
Also, I might sometimes happen to deploy before committing – for existing but changed recipes, git log returns the date of the previous commit, before these changes were made.

The first of these could be addressed by checking whether git log has returned an empty string and falling back to date -r in that case. I'm not seeing a non-convoluted way of fixing the second point – presumably you could check whether git diff for that file is empty or not and fallback to date -r in the non-empty case, and I'm sure there's more elegant solutions for this – but I've got another idea:
How about also checking whether the value of the CI environment variable is true as described here – so, if [ -d .git ] && [ "$CI" = true ]? (Perhaps paired with an explanatory comment?)
If you modify your pull request accordingly, I'll merge it!

I changed the build.sh to check for the GITHUB_ACTIONS environment variable. Only if it is run as a GitHub Action, the script will use the date of the last change to a recipe for the timestamp, otherwise it will use the file modification time, just like before.

Brilliant, thank you so much!


PYIC-2215: Update TTL Config

Update create method to take new ConfigurationVariable for the tableTtl
Add new Configuration Variable vcTtl

Proposed changes
What changed

Why did it change

Issue tracking

PYIC-2215

Checklists

Has quick look for updated config… 👍🏼  😅


tests: disable grpc requests from going off

Fixes #1140

Is this why Travis is failing on PRs?

I believe so. The Travis test for Node stable worked, but 0.12 failed: https://travis-ci.org/GoogleCloudPlatform/gcloud-node/jobs/112616727#L2816 -- not sure what that's about.

Looks like a fluke, I re-started it and everything seems fine.


Add 'tag_on_failure' property

It would be great if this filter could optionally add a custom tag upon failure, such as the grok or date filter.  This would be extremely useful in a multi-tenancy environment where the Logstash instance is processing many different json objects as it would potentially allow you to at least isolate which json filter failed, which could allow you to isolate the specific tenant.

fixed in 2.0.4


Engine: update YAML-docs with latest version from 19.03 branch

With this, we can also remove a special-case in the cli.md template, because that issue was fixed upstream (in https://github.com/docker/cli/pull/2454)
This brings in the changes from https://github.com/docker/cli/pull/2453

@usha-mandya @silvin-lubecki PTAL

Not merging yet to give @silvin-lubecki a chance to review before merging.

@usha-mandya you can merge 👍


Non Persistent mode gets connection error

non persistent mode failed, service is not waiting for geckodriver port to open.

fixed by https://github.com/RafalSkorka/wdio-geckodriver-service/pull/3


Please prepare a more descriptive readme file.

I'm pretty new to these issues and I don't fully understand what I have to do. Can you please explain more clearly how to use it?

@ofyalcin
Sorry for the late reply.
I've only written Japanese instruction and it's kinda for older version.
http://ja.katzueno.com/2015/01/3390/
Google Translate does pretty good job translating into English
https://translate.google.com/translate?hl=ja&sl=ja&tl=en&u=http%3A%2F%2Fja.katzueno.com%2F2015%2F01%2F3390%2F
I will try to write some readme docs.
But strongly looking for PR of readme.

I've also added a bit more descriptive readme.
Thx.

Thank you!


Fix overlapping x-labels and alignment of y-labels

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
#1758
What are the significant changes in functionality due to this change request?
Improves SamplePlot  label appearance

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[x] 1. Review all computer code.
[x] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[x] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[x] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[x] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[x] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[x] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[x] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test qsubs sawtooth on f8e789c : invalidated by @PaulTalbot-INL
spurious aiohttp.signals failure

Job Test qsubs sawtooth on f8e789c : invalidated by @wangcj05

Job Test qsubs sawtooth on f8e789c : invalidated by @wangcj05
ModuleNotFoundError: No module named ''aiohttp.signals''

Job Test qsubs sawtooth on f8e789c : invalidated by @wangcj05
time out

Changes are good, checklist is satisfied, thanks for your contribution @greenwoodms06


admin objects filtered with tenant mixin

Tenant model should be like this to handle admin objects filtering in admin panel.
class TenantModel(TenantModelMixin, models.Model):
    # Abstract model which all the models related to tenant inherit.

    **admin_objects = models.Manager()**
    objects = TenantManager()

    class Meta:
        abstract = True

I don't think this will work if the database engine is set as django_multitenant.backends.postgresql.