loop or previous error loading module 'tds'

when try to require tds, failed as below:
th> require 'tds'
/home/davinci/torch/install/share/lua/5.1/trepl/init.lua:389: loop or previous error loading module 'tds'
stack traceback:
[C]: in function 'error'
/home/davinci/torch/install/share/lua/5.1/trepl/init.lua:389: in function 'require'
[string "_RESULT={require 'tds'}"]:1: in main chunk
[C]: in function 'xpcall'
/home/davinci/torch/install/share/lua/5.1/trepl/init.lua:661: in function 'repl'
...inci/torch/install/lib/luarocks/rocks/trepl/scm-1/bin/th:204: in main chunk
[C]: at 0x00406670
Help me please...

After update lua to 5.2, can work now


Separate tiller into pkg and cmd so we can use tiller as a library.

The motivation behind this PR is that we wanted to use tiller to deploy charts directly to target k8s clusters without installing it. So we needed tiller as a library for integration.
The patch is pretty straight forward, I just moved files in cmd/tiller into pkg/tiller and renamed releaseServer to ReleaseServer in order to use it out side of the package.

This change is

Just signed the linuxfoundation CLA

Thanks @adieu!


AudioVoice setADSR() method

PolySynth is designed to work with an AudioVoice array, but it calls setADSR() on the voices, and setADSR() is not an audiovoice method.
examples

https://github.com/processing/p5.js-sound/blob/4bbe4ef0455219112360f52246ff385ca220bcc4/src/polysynth.js#L181-L185
https://github.com/processing/p5.js-sound/blob/4bbe4ef0455219112360f52246ff385ca220bcc4/src/polysynth.js#L207-L211

so shouldn't AudioVoice have a setADSR() method? such as the play(), triggerAttack(), triggerRelease() and amp() methods
https://github.com/processing/p5.js-sound/blob/4bbe4ef0455219112360f52246ff385ca220bcc4/src/audioVoice.js#L18-L24

It looks like right now only the subclasses of AudioVoice have that method, e.g.: https://github.com/processing/p5.js-sound/blob/5bad8cbf3bd1f94d07d7854dec7a6379180a41d5/src/monosynth.js#L297
I think it can make sense to have a default stub implementation like the ones above, just so it's clear when implementing any future AudioVoice subclasses that we need to implement that method.

And I think all the Audiovoice methods  need documentation, so that you can implement a subclass without reading the source code.


vercel deploy problem

Hi, I have a problem with deploying the code on vercel. There are some picture for my process. Could you give some advice? Thanks!

Thanks a lot! There is still some problem here maybe about the output directory. Could you please also tell me how to config output directory, install command and development command? Thanks!

And here is the picture that made by some people successfully deploy. Should I add environment variable?

@li-yingfei the output directory is public also mark check the below option 👇🏻

Ok Thanks!

closing this as its resolved


Regarding the variance regulation term

Thanks for the great work! It is stated in the paper (Sec.4.1) that the hinge function encourages the variance to be equal to \gamma. I think it should be above \gamma instead. Is that correct? Will there be a situation where the variance becomes too large?

The hinge loss encourages the standard deviation to be at get close to \gamma but there is no force encouraging it to be much greater than \gamma. Indeed, the hinge is the max between 0 and \gamma - std so when std is greater than \gamma the loss is 0. In practice we observe that std will be slightly lower than \gamma without reaching exactly \gamma, which is enough to effectively maintain the variance of the embeddings and prevent the collapse.
I hope this answer your question, I am closing the issue since it is not related to the code. If you have additional questions fill free to contact me by e-mail at<EMAIL_ADDRESS>

Hi, thanks for the great work!
Would you please post a figure of the std_loss changes with respect to the training epochs? It would be very helpful. Because my std_loss decays very slowly, changed from 23 to 21.
Thanks!


Numeric fields accept negative values

Actual Results
The system is accepting negative values for numeric fields such as age, household number, number of children
Expected results
The system should not allow negative values for these fealds
Steps to reproduce
Login > Social > Social info > Info Social e Conjugal add negative value for the "No de conviventes" or in the children tab
Screenshot/Attachment (Optional)
A visual description of the unexpected behaviour.

@Benilde any constraints for the age of the mother or father?

 Numeric fields accept negative values #640

 Numeric fields accept negative values

Age (Mae A, Pai A) is still accepting negatives. I'm updating the steps to include this scenario.


Recommendation: Add a Changelog to the project

Adding a Changelog (preferably in markup format) would provide a centralized place to look at all releases/updates and could be added to the help book.

You mean as a section in the help book? I can see that.

Yes for the version history.
So far I have:

ReadMe

Version history
System requirements
Installing, updating, uninstalling
License agreement
Credits

Usage
Settings

General
Exclude List
Advanced

Glossary

I suspect there is no need for official versioning info in the help book until a 1.0 style release. Any idea what version you're going to call it? I'm sure the 2.x means something to you, but I came in late so it's all seems pre-1.0 to me. ;)
That said, it's  damn good app and very usable as is now.

Yeah, 1.0 was a super bad app. I changed it to 2.0 when I rewrote it with a better design. But to go to 3 is too much of a leap, even if the app has had somewhat of a new design and changed a lot of the code. But I see 2.5.X as the release version. In the past I did go by semantic versioning, but it's started to make less and less sense to me, so instead I now go more by build version for bug fixes and small to medium size updates.
With the cancel buttons I'm thinking it warrants incrementing to 2.5.4.

I assume this includes the cell cancel/clear buttons as well?

Yes (if Apple allows one to cancel an operation already in the queue, haven't had the chance to research that).

The Unarchiver does this. Perhaps look at that code?


you want flutter dev in this 🤷♂?

looking good , but wasting time starups around the world might need it if we polish it better so ping me at +91-9952977500 whatsapp or telegram me at kingsmen732

Happy to accept PRs if you have any! Closing this issue


amCalendar causes protractor to timeout on waiting async Angular

Description of the Issue and Steps to Reproduce:
Did you search for duplicate issue? [Yes]
Please describe the issue and steps to reproduce, preferably with a code sample / plunker:
e2e protractor tests fail after amCalendar pipe is used:
Timed out waiting for asynchronous Angular tasks to finish after 50 seconds.
Ensure your issue is isolated to angular2-moment. Issues involving third party tools will be closed unless submitted by the tool's author/maintainer.
Environment:
Please answer the following questions:

Angular version: 4.0.0-rc.2
TypeScript version: 2.2.1
moment version: 1.1.0
Are you using moment-timezone: no
Are you using the angular-cli: yes
Using Rollup/Webpack/System.js/Ionic/similar?

Hi, thank you for reporting this. Can you please check if wrapping the setTimeout in initTimer() with runOutsideAngular fixes this issue and send a PR?
https://github.com/urish/angular2-moment/blob/c20b846934f440db3d56b9c9f644e46957750951/src/calendar.pipe.ts#L73

Yes, it helps :)
Unfortunately I don't know how to pass ngZone to the static method(which initTimer is) so I converted it to non-static and removed refs as we don't need then anymore in this case. That can cause performance issues but I don't have good environment to test near at hand. May you have some?
Please review and let me know if it is OK to leave initTimer as non-static or may be you know a good way how to pass ngZone to static methods. Thanks for helping.

Awesome, thanks for the PR!
As for passing the ngZone instance to the initTimer(), I think the best way would just be to add it as a parameter - it is called by the CalendarPipe constructor, and you can pass the ngZone you have there. Does this make sense?

Great idea! I have updated PR passing ngZone and ChangeDetectorRef as parameters.
Not sure if we really need ngZone.run(() => cdRef.markForCheck()); inside setTimeout so would be nice if you could review and let me know if the code is good or can be improved further.

True, we don't need it - I left you a comment. We can entirely skip the ChangeDetectorRef parameter to initTimer, also, we can remove the runOutsideAngular call from the constructor (but keep that part that's inside - the subscribe call)


Add wrappers for GtkFlowBox and GtkFlowBoxChild

This is a widget added in gtk 3.12. Wanted to use it in a project, but didn't see wrappers for it, so I've added some. Hopefully this can be merged in. Let me know if there are any issues. Thanks.

Got a small demo here https://github.com/hitchfred/gotk3-flowbox


add feature - press r to restart with the last timer

This pull request adds a feature to restart with the last timer when the r key is pressed when the last timer runs out or after esc is pressed.
Saving a few keystrokes several times a day can really add up !

Works great. Thanks @mxgc


Implement index RFCs: RFC 1017, RFC 1018

https://github.com/edgedb/rfcs/blob/master/text/1017-abstract-index.rst
https://github.com/edgedb/rfcs/blob/master/text/1018-extending-indexes.rst
This is in progress in #4889

This is finished, right?


Wrong file structure in existing TypeScript projects

In a fresh TypeScript project that has some unit tests under ./test I created a new wdio project using the following command:
$ npm init wdio ./test

With the following answers:
? Where is your automation backend located? On my local machine
? Which framework do you want to use? mocha
? Do you want to use a compiler? TypeScript (https://www.typescriptlang.org/)
? Where are your test specs located? ./e2e
? Do you want WebdriverIO to autogenerate some test files? Yes
? Do you want to use page objects (https://martinfowler.com/bliki/PageObject.html)? No
? Which reporter do you want to use? spec
? Do you want to add a plugin to your test setup?
? Do you want to add a service to your test setup? vscode
? What is the base url? http://localhost
? Do you want me to run `npm install` Yes

Which resulted into this file structure:

It seems that:

the ./test/e2e folder is not generated
the example test is in a wrong directory
a package.json is generated even though the project already has one

We have improved the wizard capabilities in the latest beta release. It includes a fix for this as well.


GraphQL requests never reach the server for TestFlight/App Store React native app.

Since ApolloServer 0.2.x (previously I was using 0.1.x with apolloServer(), now I'm using apolloExpress()) all GraphQL requests made from the React Native app doesn't reach the server. However in Simulator, the requests work and everything is OK with same code.
My server code looks like this with 0.2.x
const PORT = 4000;
const executableSchema = makeExecutableSchema({
  typeDefs: Schema,
  resolvers: Resolvers,
});

app.use(passport.initialize());
app.use(passport.session());

app.use( '/graphql', bodyParser.json(), apolloExpress( (req, res, next) => {
  ...
}));

Again, everything works fine in SIMULATOR, in AppStore/TestFlight, it does not work.

This almost certainly isn't a bug in apollo server. It's probably because you're not configuring something right.


After testing, I found out the code work when basicModel_neutral_lbs_10_207_0_v1.0.0.pkl is put on the root of the directory. Maybe bug in the PHALP?

          After testing, I found out the code work when `basicModel_neutral_lbs_10_207_0_v1.0.0.pkl` is put on the root of the directory. Maybe bug in the PHALP?

Originally posted by @maxso-216 in https://github.com/shubham-goel/4D-Humans/issues/121#issuecomment-2135458151

After the discussion here https://github.com/shubham-goel/4D-Humans/issues/121 I additionally tried several options to add the model file to the correct directory, but it still doesn't work.
I tried throwing the file directly into the directory, and also via gdown, having uploaded the file to google drive beforehand.

If you run the demo on images (python demo.py ...) after moving the basicModel_neutral_lbs_10_207_0_v1.0.0.pkl file to the ./data/ folder, then you should be good to go.

i fixed this error， you need to copy the basicModel_neutral_lbs_10_207_0_v1.0.0.pkl file from “./data" folder to /home/{user}/.cache/phalp/3D/models/smpl, and then rename the file "SMPL_NEITRAL.smpl"

If you run the demo.py first, it should transfer the smpl model in the right location for you to run track.py afterwards.


Performance Issue on using pax-logging 1.11.3 with log4j2 async logging.

Hi All,
When we use pax-logging 1.11.3 with async logging we see the high latency introduced in the following stack trace due to push log events into the OSGi service. Is there any configuration available to stop this service as I go through the code will not able to find any configuration.
org.eclipse.equinox.internal.event.EventHandlerTracker.getHandlers() (line: 162)
org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent() (line: 110)
org.eclipse.equinox.internal.event.EventAdminImpl.postEvent() (line: 70)
org.eclipse.equinox.internal.event.EventComponent.postEvent() (line: 39)
org.ops4j.pax.logging.spi.support.EventAdminTracker.deliver() (line: 102)
org.ops4j.pax.logging.spi.support.EventAdminTracker.postEvent() (line: 64)
org.ops4j.pax.logging.log4j2.internal.PaxLoggingServiceImpl.handleEvents() (line: 322)
org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.doLog0() (line: 358)
org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.doLog() (line: 337)
org.ops4j.pax.logging.log4j2.internal.PaxLoggerImpl.inform() (line: 149)
org.ops4j.pax.logging.internal.TrackingLogger.inform() (line: 120)
org.ops4j.pax.logging.jcl.JclLogger.info() (line: 108)
org.apache.synapse.mediators.MediatorLog.traceOrDebug() (line: 82)
org.apache.synapse.mediators.AbstractListMediator.buildMessage() (line: 150)
org.apache.synapse.mediators.AbstractListMediator.mediate() (line: 95)
org.apache.synapse.mediators.AbstractListMediator.mediate() (line: 71)
org.apache.synapse.mediators.base.SequenceMediator.mediate() (line: 158)
org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler.mediate_aroundBody0() (line: 73)
org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler.mediate() (line: 58)
org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler.handleRequest_aroundBody2() (line: 90)
org.wso2.carbon.apimgt.gateway.handlers.ext.APIManagerExtensionHandler.handleRequest() (line: 79)
org.apache.synapse.rest.API.process() (line: 368)
org.apache.synapse.rest.RESTRequestHandler.apiProcessNonDefaultStrategy() (line: 149)

Good point and thanks for the report!
I was thinking about disabling EventAdmin, but initially I wanted to focus on specification compliance. I'll check tomorrow!

OK @tharindu1st I've checked the problem and I've added one configuration option:
org.ops4j.pax.logging.eventAdminEnabled

If you set it as either system (Karaf: etc/system.properties) or bundle context (Karaf: etc/config.properties) property with value false, Event admin will be skipped ENTIRELY.
This has to stay as defaulted to true (even if you omit the option entirely) for spec compliance...
What version of pax logging (1.11.x, 1.12.x, 2.0.x, 2.1.x) would you like to see the option in?
Now I'm going to have it only in 2.1.x and 1.12.x (the versions without Log4j1 backend).

Hi @grgrzybek ,
Thanks for your prompt reply, We will waiting for the fix in 1.11.x range release.

@tharindu1st 1.11.15 should be available in Maven Central soon. I'll send an announcement email tomorrow.


Updates 02/09

^ bigfan, cloak, meat fields, jar it, grapple, SUS

One more blocking update to go then we can get building!!!


implement status conditions

ex: update status when app is being upgraded

link to https://github.com/opdev/l5-operator-demo/pull/38


[Parse] Trivial tweaks to 'type(of:)' parsing

Dead code elimination
Fix potential crasher

@swift-ci Please smoke test and merge

@swift-ci Please smoke test and merge


docker ulimits

Question:
Some of our nextflow pipelines end up hitting nofile ulimit issues within docker.  In order to avoid this when utilizing the former aws templates we would add the following to the provision.sh script.
# common provisioning for all workflow orchestrators cd /opt sh $BASEDIR/ecs-additions-common.sh sed -i 's/nofile=.*/nofile=65536:65536"/' /etc/sysconfig/docker
can this be set in a context?
Related issue here
https://github.com/aws-samples/aws-genomics-workflows/issues/150

In that case the best strategy here would be to have Nextflow request a higher limit when requesting the run. See the ulimits section of https://docs.aws.amazon.com/batch/latest/userguide/job_definition_parameters.html#containerProperties
If Nextflow cannot do this it would be worth raising a ticket with them as the problem is much more generic than just AGC.

As a work around, if you clone the repository you could specify the limit in the LaunchTemplate. The content of the LaunchTemplate is in https://github.com/aws/amazon-genomics-cli/blob/main/packages/cdk/lib/constants.ts#L11-L106
I don't think changing it here should be a long term fix though.

As @markjschreiber suggested it may be worth cutting a ticket to next flow to increase the limit when requesting a run. Closing the issue due to inactivity.


date_format validating correct date format incorrectly.

I have a datepicker component that I use in my templates like this:
<datepicker
       v-model="toDate"
       v-validate="toDateValidator"
       name="To Date"
       data-vv-name="To date"
       :propClass="this.$validator.errors.has('To Date') ? 'input-validation-error' : ''"
       :propDate="toDate"
       :includeTime="true"
       @input="toDate = $event">
</datepicker>

the v-model property is a string that conforms to the default moment format: "YYYY-MM-DDTHH:mm:ssZ" which actually looks like "2017-11-08T19:00:00-08:00"
the v-validate object toDateValidator is defined like this:
get toDateValidator(): any {
       return {required: true, date_format: 'YYYY-MM-DDTHH:mm:ssZ', after: this.fromDate }
 }

When I call this.$validator.validateAll() the date_format validation passes correctly. I can change the date on the datepicker and again the date_format passes validation.
The issue I am faced with is if the utcOffset is changed to something different from what was set initially say "2017-11-09T16:00:00+13:00" the validation of the string will fail.
When the utcOffset is changed I have tried resetting the validator like so:
this.$validator.errors.clear();
this.$validator.reset();
this.$validator.pause();
setTimeout(() => {
      this.$validator.resume();
}, 400);

I can see the aria-invalid attribute equals false, but as soon as I call validateAll() it fails.
Is there something I'm doing wrong here.

Would be great to get a response to this, thanks in advance.

try using a Date object in v-model instead of a string.

Thanks for the reply, I actually realised this is more an issue to do with the vee-validate rather than vuejs-datepicker. Sorry...


Feature request: pyproject.toml & pypi package

The other repository has a pypi release but it doesn't even run nor does the regular install without editing some files, would imagine it would be a pretty important feature to allow people to use this repo more easily via pip install (though it'd have to be tree-of-thought-llm as the other repo took the name tree-of-thought). Would be happy to help out with this, just making an issue to see if the maintainers are already working on it or what the status of things is.

hi @elliottower thanks! we are in the process of reclaiming the tree-of-thoughts pip package: https://github.com/pypi/support/issues/2928

Hi @elliottower please check out https://github.com/princeton-nlp/tree-of-thought-llm/tree/pypi
Feel free to test run and let me know if there's any issues. I plan to merge it into master, and have a tot pip package by this week.


Make sure query-response and query-error events contain _knexTxId

The docs said that these events contain both __knexUid and __knexTxId but I found that it were lacking __knexTxId

Thanks!

Released in 0.21.14


failed to load source for dependency libc

Problem
I am trying to install old version for transformers with "pip install transformers==3.3.1", when additional tokenizer package needs rust compiler I so followed the steps on this page: https://huggingface.co/docs/tokenizers/installation, then re-running the installation command find that rust could not find "libc":
ransformers==3.3.1) (8.1.3)
Requirement already satisfied: joblib in /scratch/yerong/.conda/envs/reason/lib/python3.11/site-packages (from sacremoses->transformers==3.3.1) (1.2.0)
Building wheels for collected packages: tokenizers
 Building wheel for tokenizers (pyproject.toml) ... error
 error: subprocess-exited-with-error
 × Building wheel for tokenizers (pyproject.toml) did not run successfully.
 │ exit code: 1
 ╰─> [55 lines of output]
     /tmp/pip-build-env-bfzcki16/overlay/lib/python3.11/site-packages/setuptools/dist.py:519: InformationOnly: Normalizing '0.8.1.rc2' to '0.8.1rc2'
       self.metadata.version = self._normalize_version(
     running bdist_wheel
     running build
     running build_py
     creating build
     creating build/lib.linux-x86_64-cpython-311
     creating build/lib.linux-x86_64-cpython-311/tokenizers
     copying tokenizers/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers
     creating build/lib.linux-x86_64-cpython-311/tokenizers/models
     copying tokenizers/models/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/models
     creating build/lib.linux-x86_64-cpython-311/tokenizers/decoders
     copying tokenizers/decoders/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/decoders
     creating build/lib.linux-x86_64-cpython-311/tokenizers/normalizers
     copying tokenizers/normalizers/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/normalizers
     creating build/lib.linux-x86_64-cpython-311/tokenizers/pre_tokenizers
     copying tokenizers/pre_tokenizers/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/pre_tokenizers
     creating build/lib.linux-x86_64-cpython-311/tokenizers/processors
     copying tokenizers/processors/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/processors
     creating build/lib.linux-x86_64-cpython-311/tokenizers/trainers
     copying tokenizers/trainers/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/trainers
     creating build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/implementations/sentencepiece_bpe.py -> build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/implementations/char_level_bpe.py -> build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/implementations/byte_level_bpe.py -> build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/implementations/bert_wordpiece.py -> build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/implementations/base_tokenizer.py -> build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/implementations/__init__.py -> build/lib.linux-x86_64-cpython-311/tokenizers/implementations
     copying tokenizers/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers
     copying tokenizers/models/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers/models
     copying tokenizers/decoders/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers/decoders
     copying tokenizers/normalizers/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers/normalizers
     copying tokenizers/pre_tokenizers/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers/pre_tokenizers
     copying tokenizers/processors/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers/processors
     copying tokenizers/trainers/__init__.pyi -> build/lib.linux-x86_64-cpython-311/tokenizers/trainers
     running build_ext
     running build_rust
     cargo rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --release -v --features pyo3/extension-module -- --crate-type cdylib
     warning: unused manifest key: target.x86_64-apple-darwin.rustflags
         Updating crates.io index
     warning: spurious network error (2 tries remaining): bad packet length; class=Net (12)
     error: failed to get `libc` as a dependency of package `tokenizers-python v0.8.1-rc2 (/tmp/pip-install-8814ldyi/tokenizers_cbab6a736f314261bfaeb5b456c7afe8)`
     Caused by:
       failed to load source for dependency `libc`
     Caused by:
       Unable to update registry `https://github.com/rust-lang/crates.io-index`
     Caused by:
       failed to fetch `https://github.com/rust-lang/crates.io-index`
     Caused by:
       error reading from the zlib stream; class=Zlib (5)
     error: `cargo rustc --lib --message-format=json-render-diagnostics --manifest-path Cargo.toml --release -v --features pyo3/extension-module -- --crate-type cdylib` failed with code 101
     [end of output]
 note: This error originates from a subprocess, and is likely not a problem with pip.
 ERROR: Failed building wheel for tokenizers
Failed to build tokenizers
ERROR: Could not build wheels for tokenizers, which is required to install pyproject.toml-based projects

Steps

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
 source "$HOME/.cargo/env"
pip install transformers==3.3.1

Possible Solution(s)
No response
Notes
No response
Version
No response

#10303 contains some debugging steps and potential workarounds
Debugging steps

Re-run with CARGO_HTTP_DEBUG=true and CARGO_LOG=cargo::ops::registry=trace env variables
Does it run with CARGO_NET_GIT_FETCH_WITH_CLI?
Does it run with CARGO_HTTP_MULTIPLEXING=false? Some proxies have problems with http2

If either of those last two work for you, they can also serve as workarounds.
Another potential workaround if you have a new enough cargo is to enable sparse registry support which changes how we do network communication and might bypass the root cause of this problem

Thanks.
CARGO_HTTP_DEBUG=true; CARGO_LOG=cargo::ops::registry=trace; pip install transformers==3.3.1
works for python 3.7 (conda)  but not python 3.11 (same conda)
Not sure what is the difference between these two though.


Update Pages “home”

Automatically generated by Netlify CMS

👷 Deploy Preview for tech-works-for-us processing.

Name
Link

🔨 Latest commit
da0a39b1bbb9d108e134099da5225da796e297b8

🔍 Latest deploy log
https://app.netlify.com/sites/tech-works-for-us/deploys/63769ab28b5112000873a65f


[USDU-245] Adds Test case for EditorOnly tag object not being exported

Purpose of this PR
Ticket/Jira #:
USDU-245
Objects tagged as "EditorOnly" are still exported #303
Testing
ExportObjectWithEditorOnlyTag_DoesNotExportEditorOnly

Create a root object
Creates a default object - set it as 1st child of root object
Creates an EditorOnly Tag object - set it as 2nd child of root object
Exports it as a USD file
Open and iterate over the exported USD file
Make sure the EditorOnly Tag child object does not exist

Complexity:
1
Halo Effect:
1
Additional information
Note to reviewers:
Currently set as Ignore due to USDU-245
Will remove the ignore attribute once ticket is solved
Reminder:

[ ] Add entry in CHANGELOG.md (if applicable)

Thanks for the reviews @vickycl !


Web docs

We want docs with rendered notebooks so users can get the gist of bridge-ds quicker.

Closed with #9


[FEATURE] use json field in for widget

Description of the requested feature
Use json fields with the for widget
Proposed configuration syntax
(for workspace in ${var.list}
and/or
(for workspace in var.list

Additional context
I think it would make many widgets with non-trivial state a lot easier when you do not have to use multiple listeners instead of one larger state. To effectively use that larger state you would have to be able to use array fields of JSON objects for the for-widget.
I think this would have a great synergy with allowing field updates, like in  #322

This should already work, I'd you use the correct syntax to embed a simplexpr in yuck code, via {foo.bar}:
(for x in {foo.bar}
 ...)

I see, so my syntax was off, thank you for the heads up


oh-my-zsh: 2016-04-06 -> 2016-04-20

Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Looks fine to me, thank you!


Not working for Javascript file

Code map is not showing the methods in javascript file.

Seems like it does.

I have the same problem - the codemap explorer is empty when editing javascript files.

It would be great if any of you guys can provide some data that can help to reproduce the problem. Like a file content.
The JS parsing for CodeMap is rather very generic as it does not use and industry grade parsers like Roslyn. Thus addressing any parsing problems without and context is close to impossible.

One thing that is obvious from your image is the absence of the keyword function. If it is used then parsing works as expected:

Though I am a wrong person to comment on JS syntax ambiguities.
CodeMap is using a TS parser so most likely it will miss some edge cases of valid but less canonical JS syntax. Thus ideally I would like to get the community help here. If someone can contribute a proper JS mapper (either regex based or a dedicated one). I wil gladly incorporate it.


HTTP ERROR 403

So i have changed the admin = 1 in sql but i still get "HTTP ERROR 403"

fixed the problem


add proxy env to the pods

task: https://github.com/open-cluster-management/backlog/issues/16121
Signed-off-by: Zhiwei Yin<EMAIL_ADDRESS>

/lgtm


Pakage Announcement is missing for "EquivalentCircuits.jl"

First of all thank you very much for your great package!!!
It was not easy to find the package.
Therefore, I propose that you make an anouncement for your package in:
discourse.julialang.org/c/package-announcements
Best regards,
Stefan

Thanks for your suggestion. I'll be sure to make an announcement there upon the next release.
Best regards,
Maxime

I am looking foreward :-)


Added an optional timeout to the Mailbox.take method

This required changes to the  underlying Mutex.runLocked and ConditionalVariable.wait methods.

[X] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

The changes are backwards compatible simply adding an optional 'timeout' argument to each of the noted methods.
The changes provide greater flexibility in how the methods are used and will also aid in debugging dead locks (which is what prompted me to do the work).

I've released a temp package to pub.dev if anyone needs this functionality urgently
https://pub.dev/packages/native_synchronization_temp

changes as requested and merged with main.

I've just had to raise an issue with the dart team as ffi seems to be crashing with the latest merges from main.
https://github.com/dart-lang/sdk/issues/56412
So perhaps best no to merge this pr until we see a response on the noted issue.

I've removed the check for a closed mailbox from Mailbox.take() with a timeout to side set the FFI crash.
Do we wait for an fix to ffi before we release?

Tests are not passing and there are still unresolved comments.

Hi - thanks for the PR. FYI that the source-of-truth for this package has moved to our dart-lang/labs monorepo; https://github.com/dart-lang/labs/tree/main/pkgs/native_synchronization.
I'll close this PR, but feel free to re-create it against the new package location if this PR is still active.

The PR was stalled mostly because I was distracted - I will take a landing this code in the monorepo when I get a chance.


feat (DOCS-CODE-017): [sign-in] add canonical blazorserver app

@mmacy it seems we are now ready for the Content Dev review.

Hope it was okay to merge, @ferantivero, if not let me know and I can revert. :)


Configure for React 18

React 18 needs to be installed and configured for this app

React 18 config completed


feat: assist to generate documentation templates

Closes #10878, #1915 and #4767
Full description is in #10878, better read the tests to understand what this feature does.

[x] There is one remaining thing about non-pub functions, what do you think about it?
[ ] In this PR empty examples are generated for trait functions, but maybe no examples should be provided at all. Then trait function documentation will be enabled even if the function is not declared pub if the trait is declared pub.
[ ] If there is already a documentation, add another one with a separator (currently done) or simply disable this assist?
[x] I will check once more that the generated examples are correct (ie. they are easy to fill before that they are built and tested)

Comments appreciated :smile:

except for sections "Aborts" and "Undefined Behavior" which look like "Panics" and "Safety" (I may not understand the goal of these two sections) and therefore are not generated

"Aborts" is similar to "Panics", but more final: you can catch a panic, but if something goes really bad, a function might decide to abort the process directly.
"Undefined Behavior" seems indeed quite similar to "Safety". It's probably not worth including either of the two.
And I like how you only generate the Safety section if the function is unsafe.

Thanks for your comment! Indeed Safety section is only generated when applicable, and Errors and Panics are generated according to a… "heuristic" :grin:
What do you think about the two remaining points above, examples in trait functions and already documented functions?
The current behavior of this assist for trait functions is as below, I am wondering if the Examples section should be removed for them. (I am discovering pub in trait is not interesting (removed when formatting) but needed to apply the assist. I will fix this after we agree on a behavior for trait functions)
trait MyTrait {
    /// .
    ///
    /// # Examples
    ///
    /// ```
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// ```should_panic
    /// // Example template not implemented for trait functions
    /// ```
    pub fn function_trait();

    /// .
    ///
    /// # Examples
    ///
    /// ```
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// ```should_panic
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// # Safety
    ///
    /// .
    pub unsafe fn unsafe_function_trait();

    /// .
    ///
    /// # Examples
    ///
    /// ```
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// ```should_panic
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// # Panics
    ///
    /// Panics if .
    pub fn function_trait_with_default_panicking() {
        panic!()
    }

    /// .
    ///
    /// # Examples
    ///
    /// ```
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// ```should_panic
    /// // Example template not implemented for trait functions
    /// ```
    ///
    /// # Errors
    ///
    /// This function will return an error if .
    pub fn function_trait_returning_result() -> Result<(), std::io::Error>;
}

The current behavior for documented functions is as below, I wonder if we should just disable the assist in this case.
/// .
///
/// # Examples
///
/// ```
/// use doc_gen_tester::documented_function;
///
/// documented_function();
/// ```
/// --- OLD VERSION BELOW ---
/// This function does blah blah blah, old documentation
pub fn documented_function() {
    unimplemented!()
}

I think it would make sense to not offer the assist if the function already has a doc comment on it.

Thanks a lot for the conversion to hir::Fn tip! It seems to be exactly what I was looking for for paths and pub-ness, but I could not find it because these concepts are new to me. I am reading the Guide to Rustc Development so I am discovering these interesting concepts. I will apply the modifications suggested (fearlessly thanks to Rust's testing feature :wink: I love this language).
Actually for this PR I started by reading the beginning of the "expand into all callers" assist to understand how to make an assist which is applicable on functions, I have seen the ast::Fn::cast then I did everything from that ast::Fn :laughing:

About this discussion, I think trait associated functions should be exemplified but I think this assist should not be able to do this because the example would use a specific type implementing the trait and only the author can choose one.

In this PR empty examples are generated for trait functions, but maybe no examples should be provided at all.

I think this PR is okay now, tell me if things are missing

Thanks!
bors r+


Fully support Windows on Travis

It looks like this is much easier than originally anticipated - all we really need to do is support generating all the required stages based on the os setting.
The generated shell scripts run as expected on travis windows.

We should also figure out how to deal with conditionally adding .exe or .bat where required, see https://github.com/dart-lang/webdev/pull/712/files#diff-b1de5166a13e970c48aaa8bfb6775ef8R5 for one hack around this for some general tools which might be enough to start at least.

I thought we'd just move to generating and running a Dart script and use it
in both places...
On Fri, Oct 4, 2019 at 2:56 PM Jacob MacDonald<EMAIL_ADDRESS>wrote:

We should also figure out how to deal with conditionally adding .exe or
.bat where required, see
https://github.com/dart-lang/webdev/pull/712/files#diff-b1de5166a13e970c48aaa8bfb6775ef8R5
for one hack around this for some general tools which might be enough to
start at least.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/mono_repo/issues/170?email_source=notifications&email_token=AAAEFCWNXW7CKOHEDUURJ7TQM63ZLA5CNFSM4ICQVEE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAM7RKI#issuecomment-538572969,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAEFCW6JOWEJ346C3YH66TQM63ZLANCNFSM4ICQVEEQ
.

That was the original thought yes and I am fine with that but there is no reason to block windows support on that. It almost fully works already today.


Fix creation of SHA512 Crypto service

I'm using this library in my project and it thows an error if the SHA512CryptoService is created using the constructor
using (SHA512CryptoService sha = new SHA512CryptoService())
{
    byte[] licenceBinary = ToBinary(false);

    if (privateKey is RSACryptoServiceProvider rsa && !rsa.PublicOnly)
    {
        // The following line throws an ArgumentException saying the sha argument is not a valid crypto provider
        byte[] signature = rsa.SignData(licenceBinary, sha);
        Signature = signature;
        return true;
    }
}

In NET Framework 3.5, the class SHA512CryptoService throws
an error when instantiated in the regular way. If I replace the
new SHA512CryptoService() with a SHA512.Create(), it works fine. I don't know for other NET versions, since I'm currently working with that.
Also, all the official microsoft documentation examples are using SHA512.Create(). I don't know a lot about cryptography so I don't really know if this change is a breaking change (I don't think so).
This PR fixes this issue. If you can review it it would be awesome.

@TwoTenPvP


Is it planned to have an unblocked client for Rust developpers?

Hi,
For the moment there is only blocked client for Rust developers. In the update of Solana version 1.10.*, is it planned to integrate the non-blocking client in Anchor? Maybe with two features: blocking and non-blocking. And by default we have blocking one.

No current plans but would love to see this!

A bit confused what do you mean by blocking/unblocking in terms of the client ? (noob here)

A bit confused what do you mean by blocking/unblocking in terms of the client ? (noob here)

sync vs async

Added in https://github.com/coral-xyz/anchor/pull/2488


Create a new pull request by comparing changes across two branches

Description

Motivation & Context

Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[ ] I have read the contributing guidelines
[ ] My code follows the code style of the project (using npm run lint)
[ ] My change introduces changes to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Live previews

https://deploy-preview-{your_pr_number}--twbs-bootstrap.netlify.app/

Related issues

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 95.989%

Files with Coverage Reduction
New Missed Lines
%

js/src/util/focustrap.js
1
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
2019

Relevant Lines:
2070

💛  - Coveralls


f-string used in transifex.py, but python 3.5 doesn't support f-string

Checking the Actions log, I saw the CI failing in Python 3.5 with rasing SyntaxError exception because there of {TRANSIFEX_CLI_MINIMUM_VERSION} in the code block in the line 85 of sphinx_intl/transifex.py:
        msg = textwrap.dedent(f"""\
        An unsupported version of the Transifex CLI was found.
        Version {TRANSIFEX_CLI_MINIMUM_VERSION} or greater is required.
        Please run the below command if you want to use this action:
            $ tx update
        """)

f-strings are available since Python 3.6, see PEP 498.

See full error log

  py35 installdeps: -e.[transifex,test]
  py35 inst: /home/runner/work/sphinx-intl/sphinx-intl/.tox/.tmp/package/1/sphinx-intl-2.1.0.dev20221021.zip
  py35 installed: DEPRECATION: Python 3.5 reached the end of its life on September 13th, 2020. Please upgrade your Python as Python 3.5 is no longer maintained. pip 21.0 will drop support for Python 3.5 in January 2021. pip 21.0 will remove support for this functionality.,alabaster==0.7.12,attrs==22.1.0,Babel==2.9.1,certifi==2021.10.8,chardet==4.0.0,click==7.1.2,docutils==0.16,idna==2.10,imagesize==1.4.1,importlib-metadata==2.1.3,iniconfig==1.1.1,Jinja2==2.11.3,MarkupSafe==1.1.1,mock==3.0.5,packaging==20.9,pathlib2==2.3.7.post1,pluggy==0.13.1,py==1.11.0,Pygments==2.11.2,pyparsing==2.4.7,pytest==6.1.2,pytz==2022.5,requests==2.25.1,six==1.16.0,snowballstemmer==2.2.0,Sphinx==3.5.4,sphinx-intl @ file:///home/runner/work/sphinx-intl/sphinx-intl/.tox/.tmp/package/1/sphinx-intl-2.1.0.dev20221021.zip,sphinxcontrib-applehelp==1.0.2,sphinxcontrib-devhelp==1.0.2,sphinxcontrib-htmlhelp==1.0.3,sphinxcontrib-jsmath==1.0.1,sphinxcontrib-qthelp==1.0.3,sphinxcontrib-serializinghtml==1.1.5,toml==0.10.2,urllib3==1.26.9,zipp==1.2.0
  py35 run-test-pre: PYTHONHASHSEED='1964382961'
  py35 run-test: commands[0] | py.test -v --durations=25
  ============================= test session starts ==============================
  platform linux -- Python 3.5.10, pytest-6.1.2, py-1.11.0, pluggy-0.13.1 -- /home/runner/work/sphinx-intl/sphinx-intl/.tox/py35/bin/python
  cachedir: .tox/py35/.pytest_cache
  rootdir: /home/runner/work/sphinx-intl/sphinx-intl
  collecting ... collected 8 items / 3 errors / 5 selected
==================================== ERRORS ====================================
____________________ ERROR collecting tests/test_cmd_pot.py ____________________
.tox/py35/lib/python3.5/site-packages/_pytest/python.py:571: in _importtestmodule
mod = import_path(self.fspath, mode=importmode)
.tox/py35/lib/python3.5/site-packages/_pytest/pathlib.py:517: in import_path
importlib.import_module(module_name)
/opt/hostedtoolcache/Python/3.5.10/x64/lib/python3.5/importlib/init.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:985: in _gcd_import
???
:968: in _find_and_load
???
:957: in _find_and_load_unlocked
???
:673: in _load_unlocked
???
.tox/py35/lib/python3.5/site-packages/_pytest/assertion/rewrite.py:171: in exec_module
exec(co, module.dict)
tests/test_cmd_pot.py:13: in
from sphinx_intl import commands
.tox/py35/lib/python3.5/site-packages/sphinx_intl/commands.py:18: in
from . import transifex
E     File "/home/runner/work/sphinx-intl/sphinx-intl/.tox/py35/lib/python3.5/site-packages/sphinx_intl/transifex.py", line 93
E       msg = textwrap.dedent(f"""
E           An unsupported version of the Transifex CLI was found.
E           Version {TRANSIFEX_CLI_MINIMUM_VERSION} or greater is required.
E           Please run the below command if you want to use this action:
E             ^
E   SyntaxError: invalid syntax
___________________ ERROR collecting tests/test_transifex.py ___________________
.tox/py35/lib/python3.5/site-packages/_pytest/python.py:571: in _importtestmodule
mod = import_path(self.fspath, mode=importmode)
.tox/py35/lib/python3.5/site-packages/_pytest/pathlib.py:517: in import_path
importlib.import_module(module_name)
/opt/hostedtoolcache/Python/3.5.10/x64/lib/python3.5/importlib/init.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
:985: in _gcd_import
???
:968: in _find_and_load
???
:957: in _find_and_load_unlocked
???
:673: in _load_unlocked
???
.tox/py35/lib/python3.5/site-packages/_pytest/assertion/rewrite.py:171: in exec_module
exec(co, module.dict)
tests/test_transifex.py:16: in
from sphinx_intl import transifex
E     File "/home/runner/work/sphinx-intl/sphinx-intl/.tox/py35/lib/python3.5/site-packages/sphinx_intl/transifex.py", line 93
E       msg = textwrap.dedent(f"""
E           An unsupported version of the Transifex CLI was found.
E           Version {TRANSIFEX_CLI_MINIMUM_VERSION} or greater is required.
E           Please run the below command if you want to use this action:
E
E               $ tx update
E
E           """)
E
E
E
E
E
E
E
E             ^
E   SyntaxError: invalid syntax
=========================== short test summary info ============================
ERROR tests/test_cmd_pot.py
ERROR tests/test_cmd_transifex.py
ERROR tests/test_transifex.py
!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!
============================== 3 errors in 0.67s ===============================

Should we go with str.format() instead?


bump to 1.3.0

Coverage: 57.081%. Remained the same when pulling 7ee4194b2168da3f75fb5ddc5b79be3967028a44 on version_1_3 into c92c6079c91b57051332a6ae8aec79262a3db0e0 on main.


Facing an issue using MatTable

I am using MatTable in project.
Please have a look at my demo project created on stackblitz
project
What i did in this project is that I am creating run time object of rows as it is required for implementation? Can anybody look into this and let me know where i am going wrong?

I found the issue. Please have a look at the code. Its my mistake
Project


fix: RNDeviceInfo is adding AD_ID permission through play-services-iid

Description
Fixes https://github.com/react-native-device-info/react-native-device-info/issues/1671
Compatibility

OS
Implemented

iOS
✅

Android
✅

Windows
✅

Checklist

[x] I have tested this on a device/simulator for each compatible OS
[x] I added the documentation in README.md
[x] I updated the typings files (privateTypes.ts, types.ts)
[x] I added a sample use of the API (example/App.js)

@mrpmohiburrahman
Thanks for the PR!
I'll review in a few.

Proposed commit message (while waiting for CI):

fix(android)!: remove AD_ID permission requirement by removing auto-addition of play-services-iid
BREAKING CHANGE: removed default fallback getDeviceId via play-services-iid dependency
This dependency has the unfortunate side effect of including AD_ID permission, which is
not permissible for many types of applications.
If you relied on this functionality, you will need to define googlePlayServicesIidVersion in your
android gradle build files ext version block. We previously used version 17.0.0 but there may be
newer versions you could use if they work for

Proposed commit message (while waiting for CI):

Just to clarify, Should I amend the last commit message using
git commit --amend

No - not necessary, I do rebase-merge for some repos I run and that would be appreciated, but this repo we're fine squashing so I get a chance to splat a commit message in there exactly as I like :)

passed android CI already ✅  so merged it in, will kick the release off if it doesn't go automatically


compat: move check for closure cellvar update wrapper function

This sanity checking code ended up getting decoupled from the old implementation in a18b3957d55c669de56799a9a72ea31febe93ce4 when a new, much simpler method was added. This check can fail spuriously in certain environments where it doesn't even need to be run because the newer approach is used.
This is noticeable when using python scripts compiled by nuitka. Since next-gen attrs uses slots on everything by default, the use of this fixup function is now pervasive, as well.
Here's the simplest reproduction I came up with (tested on Python 3.10.9 and nuitka 1.4)
# problem.py

# pip install attrs nuitka ordered-set
# nuitka3 --standalone --onefile problem.py
# running `python problem.py` without this patch succeeds
# running nuitka's output `problem.bin` without this patch fails. With this patch it succeeds.

import attrs

@attrs.define
class Parent:
    a: int

    def __attrs_post_init__(self):
        assert self.__class__ is Child, f"{self.__class__} is not {Child} ({id(self.__class__)}, {id(Child)})"

@attrs.define
class Child(Parent):
    b: float

    def __attrs_post_init__(self):
        assert __class__ is Child, f"{__class__} is not {Child} ({id(__class__)}, {id(Child)})"

        super().__attrs_post_init__()

Child(a=1, b=0.0)

Because nuitka compiles the python code to C, I guess it loses the introspection through the __code__ attribute, which is why the sanity check causes a problem. Fortunately, that's apparently entirely unneeded with any python version 3.8 or above.
(Annotated) Pull Request Check List

[x] Added tests for changed code.

I am not sure how to reasonably add a test case for this in-tree because my reproduction requires a heavyweight external process (compiling with nuitka).

[x] Updated documentation for changed code.

the changed code is an internal function with minimal documentation. There doesn't seem to be anything to add here

[x] Changes (and possible deprecations) have news fragments in changelog.d.

Thanks!


Add display endpoint

Proposed Changes

(Describe the changes and rationale behind them)

Related Issues

(Github link to related issues or pull requests)

Checklist

[ ] Change has been tested and works on my device(s).

Can't run node in electron with sudo. App made for non-node users. Closing for now


[ENH] deep argument for get_fitted_params

This adds a boolean deep argument to get_fitted_params which behaves precisely as the argument of the same name, of get_params (see docstring in this PR). Mirror of https://github.com/sktime/sktime/pull/4113
Besides the additional user option, this would make a subsequent translation of the get_params and get_fitted_params interfaces for the meta-estimator much simpler due to the congruence of the meta-estimator utility, see https://github.com/sktime/sktime/pull/4110

Codecov Report

Merging #117 (b3f7cc6) into main (929314d) will decrease coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #117      +/-   ##
==========================================
- Coverage   77.93%   77.83%   -0.10%
==========================================
  Files          23       23
  Lines        1867     1868       +1
==========================================
- Hits         1455     1454       -1
- Misses        412      414       +2

Impacted Files
Coverage Δ

skbase/base/_base.py
82.60% <100.00%> (+0.06%)
:arrow_up:

skbase/testing/utils/_dependencies.py
56.43% <0.00%> (-1.00%)
:arrow_down:

skbase/lookup/_lookup.py
95.13% <0.00%> (-0.35%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Hmm, about the two options:

Use tag to record this functionality

Don't understand this one, could you explain?

Move to a more duck-typing approach. If a component implements get_fitted_params, we get its fitted parameters.

Agreed - that's what sklearn also does on get_params. if hasattr("get_fitted_params") etc.
That would allow interaction with any interface compliant object, although the main doubt I had about it was, what if it has the attr but it does not return a dict, or does not have deep? Additional check on signature inspect?

Hmm, about the two options:

Use tag to record this functionality

Don't understand this one, could you explain?

Realized after re-reading that it was confusing. I was specifically thinking about self.GET_FITTED_PARAMS_NESTING. That is a class variable in BaseEstimator, but that actually seems like it should be a tag or possibly config.

Also -- on line 976 there is a call to get_fitted_params if the component is a BaseEstimator. Shouldn't that pass in the deep call? If there is an estimator nested in an estimator that is nested in an estimator, I'm guessing we'd want to pass the deep parameter down a level in the call, right?

Also -- on line 976 there is a call to get_fitted_params if the component is a BaseEstimator. Shouldn't the deep call get passed down there? If there is an estimator nested in an estimator that is nested in an estimator, I'm guessing we'd want to pass the deep parameter down a level in the call,  and gather all the fitted parameters, right?

Strictly speaking no, it wasn't logically wrong, because the False case is treated on line 962/963 by an early return, so if we arrive there we already know that deep is True (which is the default).
However, I agree that it is more error prone in changes, e.g., to the default of get_fitted_params, or moving of paragraphs, so I've added the argument for safety.
The test that certified that "all was good" is the line assert set(comp_f_params_shallow) == {"foo"} in test_get_fitted_params.

Realized after re-reading that it was confusing. I was specifically thinking about self.GET_FITTED_PARAMS_NESTING. That is a class variable in BaseEstimator, but that actually seems like it should be a tag or possibly config.

I see, thanks for explaining.
I would agree that it should be a tag or config. I would tend towards a config, since it is not a "property of the estimator" but behaviour modifying in a way that a user or interface may want to repeat with different values.

(comments are addressed - no.1 by explanation & change in code; no.2 by saying, let's do this once we have config interface if you agree)

(comments are addressed - no.1 by explanation & change in code; no.2 by saying, let's do this once we have config interface if you agree)

Totally agree on that. I'll make an issue about that.

This LGTM. Will merge once tests have run and passed.


Tests for msmtools/GPCCA

These would be very nice - it would reduce my fear breaking everything... See https://github.com/msmdev/msmtools/issues/4

we can look into the original tests written for the matlab implementation, see
https://github.com/msmdev/gpcca/blob/master/regressionTest.m and
https://github.com/msmdev/gpcca/blob/master/unitTests.m
However, these are really very long, we can restrict ourselves to the most relevant aspects here.

Apparently this function is important : https://github.com/msmdev/gpcca/blob/66b3cb079847328b01fe61361c952f8b1093f3a9/regressionTest.m#L1434

@michalk8 , this would be super important - maybe you could start with setting up tests, I will contribute once I'm back. This is the groundwork we're building on - if we want our package to be in use longterm, we need to make sure it is build on solid grounds. On the CellRank side, we by now have an amazing testing system - let's carry some of that over to msmtools.

We're getting there!

Will be fixed with #465

Will be fixed with #465


The 1.0.1 version rename update

I noticed that with the latest update the rename function gets the fullPath, the third argument, as an absolute system path now, as opposed to the project relative path.
So /Users/username/long/path/to/project/folder/file/path instead of folder/file/path;
Should there be a way to control this?
It's kind of a breaking change.

The parameter name is fullPath and I expect it to be a absolute path. Returning a relative path was a bug. In addition, it only did that in some cases.)
https://github.com/sapphi-red/vite-plugin-static-copy/blob/69544bd14f50a150591b89da1c92f3e6f89f8c48/src/options.ts#L5-L9
At this stage, I'm not thinking to add an option to revert to the previous behavior.

Alright, fullPath makes sense. I'll adapt my code.
It would be great to add a note to the changelog. My build broke because of this.


ERROR Testing Part 1

Basic Unit Tests with some hardcoded values, that combines curl and chainlink EA calls, and ideally also runs the API locally automatically. Checking that success count and error codes are correct.

@jonahkaye can this be closed yet?


release v0.7.1 Windows VST3 right-click SoundFont & preset chooser not working properly

If I use version 0.7.1 of the plugin for Windows downloaded from the GitHub release, FluidSynthPlugin's SoundFont and preset chooser both fail to set the appropriate text in the plugin window (tested in REAPER). If I choose a SoundFont, after clicking "Open", the following will appear in the text box:
 = /path/to/soundfont.sf2

Of course, this should instead be showing:
soundfont = /path/to/soundfont.sf2

After correcting the text by adding the missing "soundfont" key, then the preset browser exhibits the same problem. Selecting preset 003 adds the following to the text box:
 = 0:3

...but it is supposed to be showing:
preset = 0:3

I have created a video showing the problem: https://github.com/prof-spock/FluidSynthPlugin/assets/6825789/58c7d077-934e-4814-a6b9-80d02ee2565c
This problem does not occur if I compile FluidSynth Plugin from source.
OS: Windows 10 Professional (within VirtualBox) and Windows 10 Home (on a desktop PC)

Hello mrbumpy409,
sorry for the late answer, but I have been busy last week.
I can reproduce your findings; unfortunately those errors were hidden in my development system by another FluidSynth plugin version in the canonical search path (used elsewhere for testing purposes ☹).
I have updated all platforms without any functional changes; please have a look at the Linux and Windows versions provided now.
Best regards,
Prof. Spock

Thanks, Prof. Spock! The Windows version now works correctly. The Linux version still fails to scan, however.


Add Wil and Charlie to OWNERS

Signed-off-by: Jose Fuentes<EMAIL_ADDRESS>

Thanks Jose :+1:

/lgtm

I guess this won't work til it's in master...

Ahh cooooool. :shipit:

Ahh cooooool. :shipit:

It worked because if an owner's PRs can be lgtm'd by external people (I think).


Support opacity in all styling rules

Currently some styling rules don't support the opacity property, for example ol.style.Fill or ol.style.Circle. In order to make it transparent you would need to use an rgba() color. This feels counter-intuitive to me as you have an opacity property on ol.layer.Vector.
In addition the styling feels a lot like CSS which also supports the opacity property.

I agree with this, I think we have discussed it in the past but not everyone was in favour or something

Hi vmx, so, its nice to see that  I am not the only one with that issue. Check my suggestion and this SO issue


Atom.Object.defineProperty.get is deprecated.

atom.workspaceView is no longer available.
In most cases you will not need the view. See the Workspace docs for
alternatives: https://atom.io/docs/api/latest/Workspace.
If you do need the view, please use atom.views.getView(atom.workspace),
which returns an HTMLElement.
Atom.Object.defineProperty.get (/Users/cabdi/Downloads/Atom.app/Contents/Resources/app/src/atom.js:54:11)
StatusBarSummaryView.render (/Users/cabdi/.atom/packages/linter/lib/statusbar-summary-view.coffee:11:21)

This was fixed by https://github.com/AtomLinter/Linter/commit/526bcc5ab381f3ee2d4c057dcd6571083bc31e58 and will go away by upgrading the linter package.


glance: init at 0.3.0

Description of changes

Adds Glance

A self-hosted dashboard that puts all your feeds in one place

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

[nix-shell:~/.cache/nixpkgs-review/pr-310955]$ ls results/glance/bin/
build-and-ship  glance

build-and-ship probably doesn't need to be included in the package?

build-and-ship probably doesn't need to be included in the package?

good catch

build-and-ship probably doesn't need to be included in the package?

Okay fixed here https://github.com/NixOS/nixpkgs/pull/310955/commits/bdde1ad2928561e85e94ff4c467824403fa8796b


[BEAM-4761] Handle skipped tests in parallel Nexmark

I dropped this check in refactoring, it breaks Nexmark on SQL, which skips some tests.

Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[x] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---
---

@akedin I broke nexmark on SQL by dropping the check for null results (which indicates a skipped test). This fixes it.

LGTM


Bug: input paths with dots

This line... https://github.com/up2code/yaml2props/blob/20f33898c36818aeea2c25c6181e2d65b22bbce3/yaml2props.py#L75
causes an unexpected behavior when the input filepath has dots, for example:
/home/foo/bar.d/moo.oo/fuuu/my_file.yaml

It writes a /home/foo/bar.properties file instead of a /home/foo/bar.d/moo.oo/fuuu/my_file.properties file
I guess that is better using libraries that deals with file paths instead of regular expressions
Also it could be much better to append the .properties extension. In my example it would be my_file.yaml.properties

Fixed and I had add option for let user specific output path by themself

Fixed and I had add option for let user specific output path by themself


Error installing Ionic Deeplinks plugin

When I tried to install deeplink plugin (http://ionicframework.com/docs/v2/native/ionic-deeplinks/) in my Ionic 2 project I got the following error message:
$ ionic plugin add ionic-plugin-deeplinks
(node:3784) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
 0=13, 1=10, 2=89, 3=111, 4=117, 5=32, 6=104, 7=97, 8=118, 9=101, 10=32, 11=98, 12=101, 13=101, 14=110, 15=32, 16=111, 17=112, 18=116, 19=101, 20=100, 21=32, 22=111, 23=117, 24=116, 25=32, 26=111, 27=102, 28=32, 29=116, 30=101, 31=108, 32=101, 33=109, 34=101, 35=116, 36=114, 37=121, 38=46, 39=32, 40=84, 41=111, 42=32, 43=99, 44=104, 45=97, 46=110, 47=103, 48=101, 49=32, 50=116, 51=104, 52=105, 53=115, 54=44, 55=32, 56=114, 57=117, 58=110, 59=58, 60=32, 61=99, 62=111, 63=114, 64=100, 65=111, 66=118, 67=97, 68=32, 69=116, 70=101, 71=108, 72=101, 73=109, 74=101, 75=116, 76=114, 77=121, 78=32, 79=111, 80=110, 81=46, 82=10
 0=70, 1=101, 2=116, 3=99, 4=104, 5=105, 6=110, 7=103, 8=32, 9=112, 10=108, 11=117, 12=103, 13=105, 14=110, 15=32, 16=34, 17=105, 18=111, 19=110, 20=105, 21=99, 22=45, 23=112, 24=108, 25=117, 26=103, 27=105, 28=110, 29=45, 30=100, 31=101, 32=101, 33=112, 34=108, 35=105, 36=110, 37=107, 38=115, 39=34, 40=32, 41=118, 42=105, 43=97, 44=32, 45=110, 46=112, 47=109
 0=13, 1=10
Error: Variable(s) missing (use: --variable URL_SCHEME=value --variable DEEPLINK_SCHEME=value --variable DEEPLINK_HOST=value).

Caught exception:
 undefined

Mind letting us know? https://github.com/driftyco/ionic-cli/issues

Could you provide me with the output from ionic info from within your project directory? Thanks, this should help in troubleshooting.

Hello! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!


Simple CSS in

Hi, I have following html and css code:

My title

And I get zero styling in my pdf. What am I doing wrong?

Ok, I just had to use the whole  wrapper.

@molerat619 I did not understand what you meant by "use the whole html wrapper".
My html looks like this:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>RoutEasy - Relatório Personalizado</title>

Lorem ipsum dolor sit amet consectetur our

What I meant by that was that I used only the code that was inside the body-tag. Not the whole .... stuff.

@williamknn Did you manage to find any way around it, I am facing the same issue


Added Button-Like ToolBar

Fixes: #136
Description:
Added improved ToolBar by making the UI Component look more like Buttons on the New Profile Screen.
Screenshot of Current Screen:

Screenshot of Improved Screen:

This has been addressed in #202 , so I am closing this PR.


Add More Options To Hide Alarm, Manual Arm Switch, and Enabled Switch

add options for Hiding Alarm, Manual arm switch and enabled switch.

"hide-alarm": true,
"hide-manual-arm-switch": true,
"hide-enabled-switch": true,

@colinbendell you may have to make some more changes, but it would be awesome if we could get this PR merged.

@colinbendell any thoughts?

Heya @donavanbecker - I've been cherry picking your PR since it includes a bunch of different changes and the code format change causes merge issues. I'm going to reopen the PR more for a sanity check as I prep for release.

@colinbendell Sounds good


"Options pattern - .NET" is not clear about when updated options are read

[Enter feedback here]
In section "Bind hierarchical configuration", the example code for ConfigurationBinder.Bind is immediately followed by the comment, "In the preceding code, changes to the JSON configuration file after the app has started are read."  Since the example code is specifically for Program.cs, the program has just started and there has hardly been any time for the JSON configuration file to be changed, so it's not clear what is meant by the comment.
The following example for ConfigurationBinder.Get<T> is also followed by the same comment.  In this case, the code is not set specifically in Program.cs, but it does start with configuration.Build() which presumably reads the configuration file.  Does the comment mean that in order to read changes to the configuration since the app started, one needs to rebuild the configuration?
My understanding is that the JSON file configuration provider will update the built configuration when it detects changes to the file.  If so, then perhaps it's not the call to configuration.Build() that needs to be repeated, but only the call to ConfigurationBinder.Get<T>.  Or is there some magic in Bind() and Get<T>() that will maintain a reference to the returned object and update it should the configuration change? Unfortunately, the comment doesn't make any of that clear.
The section then continues with the use of .Configure<T> to inject configuration into a DI container, providing both the code to use when configuring the DI container as well as class that takes an IOptions<TransientFaultHandlingOptions> in the constructor and assigns its .Value to a readonly field.  The example is followed by the comment, "In the preceding code, changes to the JSON configuration file after the app has started are not read. To read changes after the app has started, use IOptionsSnapshot."  In this case, what is the value of the ExampleService class taking an IOptions<TransientFaultHandlingOptions> class instead of simply taking TransientFaultHandlingOptions?
The documentation should clearly answer the following questions regarding how updated configuration values can be read:

What reads updated configuration values?
What calls must be repeated to get the updated values?
With dependency injection, what interfaces need to be used to get updated values?

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 433988ea-fda9-aa83-f6ee-221a5521a422
Version Independent ID: 00449cdc-b8fc-a9ff-3f20-0ef0994db354
Content: Options pattern - .NET
Content Source: docs/core/extensions/options.md
Product: dotnet-fundamentals
GitHub Login: @IEvangelist
Microsoft Alias: dapine

Associated WorkItem - 39307

Hi @SEnglishSMP - thank you for posting this issue, I'm working through updating this article to address these concerns.

In this case, what is the value of the ExampleService class taking an IOptions<TransientFaultHandlingOptions> class instead of simply taking TransientFaultHandlingOptions?

The IOptions<T> interface is registered with DI, to allow injection of any generic options type. Larger apps will likely have several different config classes, it's better to wrap them this way.

Your updates to the documentations clarify several things.  Thanks!

In this case, what is the value of the ExampleService class taking an IOptions<TransientFaultHandlingOptions> class instead of simply taking TransientFaultHandlingOptions?

The IOptions<T> interface is registered with DI, to allow injection of any generic options type. Larger apps will likely have several different config classes, it's better to wrap them this way.

Simple Injector recommends against using IOptions<T> in application components for several reasons.  Your answer is something that would be generally true of library components that can be used in a variety of applications and even other library components, each of which may need to manipulate configuration data.  If one is writing library components, I can see how using IOptions<T> could be of benefit there.
IOptions<T> also provides validation of configuration. This is mostly useful when there's distributed configuration (and possibly the need for distributed validation).
I'm don't see how these features make any real difference for option classes used only in the application in which they are defined.  My take is that IOptions<T> is good for library components and their configuration but brings no benefit for components configured and used only in the application for which they are defined.  Am I missing something?


Send a sign of life to all users

Hi @TrianguloY :wave:
Your effort to revive Lightning Launcher is much appreciated! I'm aware of the timeline you've posted on the forum, but I'm proposing something different here... :)
When a project has been inactive for that long, I'd imagine it to be pretty hard to regain attention and awareness. So I'm proposing to release a new version on the Play Store just with updated URLs (pointing to GitHub) and an announcement, that it's now an Open Source project. Although there are no code changes, this would definitely bring much-needed attention to this project – and maybe also some code contributions.
Additionally (or as an alternative?) you may release the current version on F-Droid, because this seems to be a good place for open source launchers.

My main concern is that Play Store forbids publishing apps that doesn't work and use an old android version, so just changing a couple strings and publishing is not possible. That's why my step 2 was to make sure the app compiles with the newer versions.
The play store version is also still in Pierre's account, and I'd rather not bother him anymore (at least for now). Changing the description could be an easy solution,   not sure if play store allows doing it with old apps though.
The f-droid may be a solution too, but that was already on my step 3.
In any case, since anyone can modify it now, if someone wants to try they are more than welcomed to do so, and share it back for all of us to benefit!

I am also interested in contributing! I'm pretty familiar with the application and the API already, and have a few useful ideas.

I am also interested in contributing! I'm pretty familiar with the application and the API already, and have a few useful ideas.

My main concern is that Play Store forbids publishing apps that doesn't work and use an old android version, so just changing a couple strings and publishing is not possible. That's why my step 2 was to make sure the app compiles with the newer versions.

I go through a lot of devices (mostly Pixels) and Lightning Launcher certainly hasn't been defunct on any of my 6+ phones - even if it felt much less stable on one newer devices, one especially in particular.

The play store version is also still in Pierre's account, and I'd rather not bother him anymore (at least for now). Changing the description could be an easy solution, not sure if play store allows doing it with old apps though. The f-droid may be a solution too, but that was already on my step 3.

I'd love to contribute code, but managing play store listings is not my area of expertise.
Perhaps until we have a significant number of user-noticeable changes in a fork, we should just leave it a sort of "community edition"?
Even though Lightning Launcher recently went open source, it is still making Pierre $4.99 per install. But Pierre going out of his way to open source it at all is certainly a nod for anyone (us) to legally/ethically do whatever we want with the code.
I just think it's at least impractical to have two separate Play Store listings - basically identical to each other. There is also the fact that the original developer only gets paid for one of those listings - even though, as I've mentioned, we do have his blessing.

In fact the app is still listed on the Play Store but nobody can buy it. At some point I stopped accepting Google's agreement and conditions, and as a consequence my account basically get locked. I cannot modify or unpublish applications until I accept the conditions. New users cannot pay and download the app, in app purchases are disabled too. So to be clear, I don't earn money at all, and quite fortunately this remove possible conflicts with publishing the app elsewhere.
Publishing new versions of the app on the Play Store also means code upgrade and (from what I recall) quite hard requirements in terms of SDK support.
As for myself I don't wish to deal with Play Store constraints yet. Managing the listing is already a lot of work. At the moment I would rather publish the app on F-Droid or similar but probably some code maintenance should be done first, at least to bring the app to a SDK level not too old and solve some basic compatibility issues with newest devices.

Life sign received, acknowledged and happy about. Thank you, Pierre, for re-releasing Lighting Launcher as free software.

Still using Lightning Launcher on my phone

Looking forward to updating my favorite launcher! What I miss the most is switching between light and dark themes

That is great news. Thanks @TrianguloY for keeping my fav launcher alive and thanks to @pierrehebert for the initial work.
I noticed a few years ago that there are no more updates and thought maybe it could be open sourced. But life got in the way, moving to another country and all. Today I gave it another go to find out what happened, I am still using it on all my devices, but worried, that new Android versions might not allow older apps.
Being just a hobbyist in Android coding, I might not be able to contribute to the public. But it certainly feels good to know that someone cares about this wonderful launcher and it hopefully will be around (functional) for future Android releases
Thanks


fix: fix lsp watcher

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

11 of 12 (91.67%)  changed or added relevant lines in 1 file are covered.
67 unchanged lines in 6 files lost coverage.
Overall coverage decreased (-0.1%) to 70.749%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

kclvm/tools/src/LSP/src/state.rs
11
12
91.67%

Files with Coverage Reduction
New Missed Lines
%

kclvm/tools/src/LSP/src/request.rs
2
66.14%

kclvm/sema/src/advanced_resolver/mod.rs
2
95.46%

kclvm/sema/src/namer/mod.rs
2
99.23%

kclvm/sema/src/core/global_state.rs
6
91.81%

kclvm/tools/src/LSP/src/hover.rs
7
89.27%

kclvm/tools/src/LSP/src/state.rs
48
74.26%

Totals

Change from base Build<PHONE_NUMBER>7:
-0.1%

Covered Lines:
52750

Relevant Lines:
74559

💛  - Coveralls


PR: Update core dependencies for 5.4.0

Description of Changes

Missing updates to core dependencies and subrepos

spyder-kernels >=2.4.0; <2.5.0
qtconsole >=5.4.0; 5.5.0
python-lsp-server >=1.6.0; <1.7.0

Update RELEASE.md instructions (spyder-kernels max/min version plugin constants location)
Remove manual installation of  docstring-to-markdown on CI and MacOS standalone installer (py2app based)

Issue(s) Resolved

Fixes #19893
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: dalthviz

Note: Seems like the test are failing due to conda-forge dropping support for Python 3.7. The new spyder-kernels version is not available on conda-forge for Python 3.7. I think this doesn't affect qtconsole or python-lsp-server since they are no-arch packages. See https://conda-forge.org/docs/user/announcements.html#dropping-python-3-7

Note: Some tests where failing due to the subrepo update of the python-lsp-server, however, talking with Ryan, the thing making the conda-based installers workflows to fail was also not having that subrepo updated. Besides that we needed to patch the spyder-feedstock recipe dependencies to take into account when building the spyder conda package the new requirements contraints.
Thanks @mrclary for helping me to fully understand what was happening here!

Merging this one to proceed with the release


Music

How do I make it exit voice chat when no one is in the channel?

https://github.com/saiteja-madha/discord-js-bot/pull/275


Update readme

Several changes have been made to the code.  These changes include:

Left reviews and line comments
Created a file and made a commit
Opened a pull request


Update PPP

Update ppp and slight change to code quality.

Codecov Report

Merging #202 (ef31043) into master (293d804) will decrease coverage by 0.26%.
The diff coverage is 28.57%.

@@             Coverage Diff              @@
##             master     #202      +/-   ##
============================================
- Coverage     62.97%   62.71%   -0.27%
- Complexity      621      623       +2
============================================
  Files           100      100
  Lines          2304     2312       +8
  Branches        285      289       +4
============================================
- Hits           1451     1450       -1
- Misses          751      757       +6
- Partials        102      105       +3

Impacted Files
Coverage Δ

...a/seedu/address/model/person/FormatPersonUtil.java
85.14% <11.11%> (-7.33%)
:arrow_down:

.../seedu/address/logic/parser/CopyCommandParser.java
88.23% <60.00%> (-5.89%)
:arrow_down:

Continue to review full report at Codecov.

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


Add struct SingletonPortgraph containing a single node.

In https://github.com/CQCL/hugr/issues/1652 we found that constructing single-node-SiblingSubgraphs is very expensive, requiring iteration over all nodes in the parent graph.
If we had a
struct SingletonSubgraph{ ...}

impl SingletonSubgraph{
  pub fn new(g: &impl PortView, node: Node) -> Self { ... }
}

We could, in the single node case, construct a SingletonSubgraph and work with that rather than using portgraph::views::subgraph.

The optimizations in #157 should remove the need for an specialized singleton structure.


Ensure gateway gas metering is consistent with authority

This should fix https://github.com/MystenLabs/sui/issues/1742.
The existing gas metering code on the gateway isn't consistent with authority. This leads to the case where gateway passes gas check, but failed on authority, leaving the objects locked on the gateway.
This PR moves all the transaction input checking logic into one single function in transaction_input_checker, and call it from all different places. This ensures consistency.

@lxfind so this is not really adding new functionality but rather unifying existing ones for consistency right?

@lxfind so this is not really adding new functionality but rather unifying existing ones for consistency right?

Correct!


Select all comes true by default on multi-select

Version
1.9.1
Here's what went wrong:
Whatever multi-select I add the select all checkbox comes checked by default. I'm not sure if it is a bug or I'm doing something wrong. The example below illustrate the issue.
import React from 'react'
import Picky from 'react-picky'

class Select extends React.Component {
  constructor (props) {
    super(props)
    this.state = {
      selected: null
    }
  }

  render () {
    return (
      <Picky
        multiple
        numberDisplayed={1}
        includeSelectAll
        includeFilter
        value={value}
        onChange={onChange}
        options={options}
        valueKey='value'
        labelKey='label'
        placeholder='Selecionar'
        selectAllText='Tudo'
        />
     )
  }
}

Hi @rgercp,
I'm not able to replicate, could you please provide a CodeSandbox, you can use this as a base if it helps: https://codesandbox.io/s/oo8z2qy4my
Alternatively, if you could provide more details in your example:

What options you are supplying?
What is your onChange
What is your value.

It currently looks like it's an error in implementation, not a bug. If you're providing a value that means you intend on using it as a controlled compoment, so your value will be something from state, onChange will update that state.

@rgercp Did you work out your issue, is it a bug or did you do something wrong?

Closing - No reproduction.


For .MSI: use $JAVA_HOME% in windows path

Currently the msi installer sets the JAVA_HOME variable to the install directory and the full path to the bin directory in the windows path environment variable.
If it would use %JAVA_HOME%\bin in the path, it would be possible to switch Java versions just by switching the JAVA_HOME variable.

I don't know if it can work and work without drawback

https://superuser.com/questions/27826/why-cant-windows-handle-an-environment-variable-in-path

but

FeatureJavaHome | Update the JAVA_HOME environment variable
is an option not set by default

and changing PATH to use JAVA_HOME will add some complexity ..
I even don't know if it possible as FeatureJavaHome is a feature Level=2 set after FeatureEnvironment Level=1
In case of multiple msi install ( 8 + 11 ) , MSI actually remove (on uninstall)  the corresponding part from the PATH with the real bin path corresponding to 8 or 11.
If all MSI use the same bin path %JAVA_HOME%\bin .. i assume the installer will probably remove it on uninstall and break the two java 8 and 11 .. (I haven't tested it though)
Seems difficult and risky to me

This issue has not get any comment from the author or likes from the community since more than one year.
I consider to close it as "won't fix" due to the lack of global interest.

@douph1 just close it as such, and the reporter can reopen if required.


Port awapi awiv adapter to .auto

Description

Review Procedure

Remarks
これのマージが必要。https://github.com/tier4/autoware_iv_msgs/pull/58
Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Read pull request guidelines
[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the guidelines.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

パッと見良さそうな感じがしました。
msgsがマージされてビルドが通るのを待ちたいと思います。

@isamu-takagi
rebaseかmergeか何かでこちらの取り込みお願いします
https://github.com/tier4/AutowareArchitectureProposal.iv/pull/558


Simple Question (not an issue)

Great project! Thanks!
I would like to ask what you think is better to use: (less sound glitches, less decoding formats..etc)

The VS1053 to do all the steam decoding on all supported formats
An I2S -> DAC

I would like to design a pcb and I can't choose what is better in the long run.
Thanks

I think option 1 is the best.  It will save some CPU power.  The second option will save some PCB/housing space.
If you already have the VS1053, go for option 1.
For the lowest price, or for a commercial project, go for option 2.

Thanks for your quick response.
Against functionality? Decoding glitches and stability?
Which one will do a better job?


chore: Use setup-node action to cache dependencies

Signed-off-by: jongwooo<EMAIL_ADDRESS>Description
Updated workflows to cache dependencies using actions/setup-node. setup-node@v3 or newer has caching built-in.
AS-IS
- uses: actions/setup-node@v3
  with:
    node-version: 18.x

- name: Use cached node_modules
  uses: actions/cache@v3
  with:
    path: node_modules
    key: nodeModules-${{ hashFiles('**/yarn.lock') }}
    restore-keys: |
      nodeModules-

TO-BE
- uses: actions/setup-node@v3
  with:
    node-version: 18.x
    cache: yarn

It’s literally a one line change to pass the cache: yarn input parameter.

References

https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows

thank you!


User cancelled the login - Swift 3 bug

Hi! I'm facing the following issue: After clicking the Uber Login Button in my app, I get redirected to the native Uber app where I click "Allow". However, I see the following error in the console once I am redirected back to my app:
Error Domain=com.uber.rides-ios-sdk.ridesAuthenticationError Code=25 "User cancelled the login process." UserInfo={NSLocalizedDescription=User cancelled the login process.}
Using Swift 3. Would appreciate any help!

This happens to me also.

Duplicate of #90. I'll be looking into this as part of enhancements to the SDK. However, I don't anticipate that we will update the Swift 2.3 version with any fixes.


Issue 148

@strokine thank you for your suggestions, I implemented them and released them right now. Instead of having an empty array for roles, I decided to put {"*"} as default value. Available in a few hours on maven central.


create output writer interface

in order to harmonize benders outputs, create an (class) interface (OutputWriter) inherited by the actual JsonWriter class.

the JsonWriter class will be used by the Sequential benders and by the master proc (world.rank =0) of Mpi benders.
a "void" class (voidWriter) that write nothing has to derive from OutputWriter if world.rank !=0.

linked to #251


Text mismatch fix

Fixes issue #12

For sure an interesting idea, I just didn't like how if you missed one character early in the test it would not let you finish until you backed up and fixed the letter and then needed to repeat all the characters after all the backspacing.


Support for AWS VMC

Hi
We would like to have a breakup cost for pricing of AWS VMC ( Vmware on cloud ) .If its possible to add support for that be great

Hi @ravithinknyx, is there a Terraform provider for this? We're not focussing on adding new cloud providers at the moment, but in the future we want to work out how we can build a plugin system so the community can add these.

Hi Alistar
Yes there is
https://registry.terraform.io/providers/vmware/vmc/latest
Thanks and Regards,
Ravi Singh | Devops Consultant
Thinknyx Technologies LLP

From: Alistair Scott @.>
Sent: Tuesday, June 7, 2022 9:23:32 PM
To: infracost/infracost @.>
Cc: Ravi Singh @.>; Mention @.>
Subject: Re: [infracost/infracost] Support for AWS VMC (Issue #1689)
Hi @ravithinknyxhttps://github.com/ravithinknyx, is there a Terraform provider for this? We're not focussing on adding new cloud providers at the moment, but in the future we want to work out how we can build a plugin system so the community can add these.
—
Reply to this email directly, view it on GitHubhttps://github.com/infracost/infracost/issues/1689#issuecomment-1149128797, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN4ZYENHCDXZUG3QWE3SLA3VN6VUJANCNFSM5XBIWD3A.
You are receiving this because you were mentioned.Message ID: @.***>


rustfmt can't load some dynamic libraries on macOS

Using rustfmt-nightly  v0.1.3 and rust nightly 1.19.0-nightly (258ae6dd9 2017-06-15)
whenever I try to run rustfmt I get this error
dyld: Library not loaded: @rpath/libsyntax-714ca9b0aa3bf580.dylib
  Referenced from: /Users/Khaled/.cargo/bin/rustfmt
  Reason: image not found
Abort trap: 6

Although that cargo fmt seems to work

Are you using the nightly toolchain when running (e.g., by setting the rustup default toolchain to nightly or by running cargo + nightly run ...?

Yes

This error also occurs on my Ubuntu machine. Strangely enough, it only happens when I run rustfmt, but it works fine when I run cargo fmt.
This is an issue for me because rust-mode in Emacs uses the rustfmt executable to format the code. This bug means I cannot easily format my code within my editor and instead have to rely on calling for cargo fmt manually.
For context I use rustup with nightly as default:
$ rustc --version
rustc 1.20.0-nightly (445077963 2017-06-20)

In Linux environment, export LD_LIBRARY_PATH=$(rustc --print sysroot)/lib:$LD_LIBRARY_PATH should work.

Given this issue, the similar/duplicated windows issue #1736, and my issue on Linux it seems like the documention should address it somehow that we need to link that library manually

For Atom users who are getting this issue when using atom-beautify, see here.
The solution for now is to checkout the rustfmt syntex branch and compile from source.

I did what @topecongiro suggested with DYLD_LIBRARY_PATH and it works on macOS

I also did what @topecongiro suggested. Works on Linux Mint

I'm having this problem too. I can't successfully run rustfmt at all. I've tried uninstalling and reinstalling nightly Rust and rustfmt-nightly, to no avail. Here is the behavior I'm seeing:
$ rustup show
Default host: x86_64-apple-darwin

installed toolchains
--------------------

stable-x86_64-apple-darwin
nightly-x86_64-apple-darwin (default)

installed targets for active toolchain
--------------------------------------

wasm32-unknown-emscripten
x86_64-apple-darwin

active toolchain
----------------

nightly-x86_64-apple-darwin (directory override for '/redacted')
rustc 1.20.0-nightly (c9bb93576 2017-06-24)
$ cargo install rustfmt-nightly
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading rustfmt-nightly v0.1.7
  Installing rustfmt-nightly v0.1.7
 Downloading term v0.4.6
 Downloading toml v0.4.2
   Compiling log v0.3.8
   Compiling regex-syntax v0.4.1
   Compiling diff v0.1.10
   Compiling utf8-ranges v1.0.0
   Compiling unicode-segmentation v1.2.0
   Compiling serde v1.0.9
   Compiling num-traits v0.1.39
   Compiling dtoa v0.4.1
   Compiling unicode-xid v0.0.4
   Compiling quote v0.3.15
   Compiling void v1.0.2
   Compiling libc v0.2.24
   Compiling term v0.4.6
   Compiling lazy_static v0.2.8
   Compiling getopts v0.2.14
   Compiling rustfmt-nightly v0.1.7
   Compiling itoa v0.3.1
   Compiling synom v0.11.3
   Compiling strings v0.1.0
   Compiling unreachable v1.0.0
   Compiling memchr v1.0.1
   Compiling thread_local v0.3.4
   Compiling syn v0.11.11
   Compiling aho-corasick v0.6.3
   Compiling serde_json v1.0.2
   Compiling toml v0.4.2
   Compiling regex v0.2.2
   Compiling serde_derive_internals v0.15.1
   Compiling serde_derive v1.0.9
   Compiling env_logger v0.4.3
    Finished release [optimized] target(s) in 105.85 secs
  Installing /Users/redacted/.cargo/bin/rustfmt
  Installing /Users/redacted/.cargo/bin/cargo-fmt
$ rustfmt --write-mode overwrite expand.rs
dyld: Library not loaded: @rpath/libsyntax-dbe71c0fd2acf87f.dylib
  Referenced from: /Users/redacted/.cargo/bin/rustfmt
  Reason: image not found
Abort trap: 6

It hangs forever if I run it via rustup run:
$ rustup run nightly rustfmt --write-mode overwrite expand.rs

Here's an excerpt of the syscalls the hung process is making (via dtruss):
open("/redacted/expand.rs\0", 0x1000000, 0x1B6)		 = 3 0
dtrace: error on enabled probe ID 2134 (ID 154: syscall::read:return): invalid kernel access in action #12 at DIF offset 92
mmap(0x0, 0x200000, 0x3, 0x1002, 0xFFFFFFFF, 0x0)		 = 0x103200000 0
madvise(0x102871000, 0x21000, 0x5)		 = 0 0
madvise(0x10350D000, 0x81000, 0x5)		 = 0 0
dtrace: error on enabled probe ID 2134 (ID 154: syscall::read:return): invalid kernel access in action #12 at DIF offset 92
close_nocancel(0x3)		 = 0 0
madvise(0x102948000, 0x11000, 0x5)		 = 0 0
madvise(0x1031AC000, 0x41000, 0x5)		 = 0 0
madvise(0x10360C000, 0x182000, 0x5)		 = 0 0
madvise(0x10320C000, 0x101000, 0x5)		 = 0 0

I removed some occurrences of the "error on enabled probe ID 2134" message, which occurs a few hundred times in a row each time it's shown above.

Just chiming in to say that @topecongiro's suggestion worked for me, and that it may be worthwhile updating the README with an installation note for macOS users.

Sorry for the negative tone in this post but I want to add my perspective as a Rust user who at the moment have no interest in being a contributor to the language or the surrounding tools. The new nightly requirement for rustfmt has been pissing me off (yes I know, there are reasons) and now this. Could rustfmt instead be shipped as a prebuilt binary with the normal rustup installer?
I only want to be a normal rustfmt user, not a contributor.

Could rustfmt instead be shipped as a prebuilt binary with the normal rustup installer?

This is the plan, it will take a while though. Hopefully should be there in the next few months.
You can also continue to use the old Rustfmt (i.e., not the nightly version) which continues to work on stable Rust (but isn't getting updated).

I don't quite understand why ef63830 closed this issue. This is just a workaround, not a proper fix. Why is it even needed to define DYLD_LIBRARY_PATH if the only toolchain I installed is nightly and it is the default one?

Just a note I was getting these errors on macos and I seem to have solved it with brew uninstall rust. I had from hombrew: rust and rustup-initand via rustup I had nightly installed. Something about that combination breaks but uninstalling the homebrew rust seems to have made cargo fmt work again running under rustup nightly toolchain.


Update openstack_loadbalancer.go

Correct some typos in returned messages:
Line 444,467: alloted->allotted
Line 889,963: occured->occurred

/assign @jsafrane

/lgtm
/approve
ty


Run the latest version?

Can the latest game version be used?

Yes it should work, the Universal Installer will try to compile against current binairies, and if it cannot compile, it will display an error.

@sailro it doesn't compile, since the installer it's looking for a new branch matching the EFT binaries version:

Ah ok interesting. I'm going to have a look.

Ok fixed, this is working now with latest <IP_ADDRESS>60:

You just need to run the installer again (no need to re-download it).
I advise you to not use this trainer with the 'live' version (only with spt-aki). BattleState / BattlEye will ban you if you try to use it 'live'.


Pipeline parameter type integer or float cannot take negative number as input

First of all, thanks for adding pipeline parameters to Elyra. On to the issue.
When I add a integer or float pipeline parameter, I'm not able to specify a negative number as input. Is this a design or a bug?
If number >= 0: OK

If number < 0: NOT OK

Deployment information

Elyra version: 3.14.1
Operating system: linux
Deployment type: Kubeflow [notebook server]
Kubeflow version: 1.6.0

Pipeline runtime environment

Kubeflow Pipelines

You are right! It looks like the current implementation does reject negative values, but this is not the desired behavior.