Trying and failing to install Boost

Hi,
I'm trying to get your software to work, since it is exactly what I'm looking for. Unfortunately, I can't get the Boost to install properly. The installation instructions are basically so vague that I have no clue what to do after downloading it. The bootstrapper gives an error  and the b2 file isn't even in the installation package (I'm assuming the bootstrapper should have created it)
Do you know of a detailed installation guide for Boost? I already looked for help using Google and the Boost website, but I couldn't find one.
The bootstrapper error: " 'cl' is not recognized as an internal or external command, operable program or batch file. " <-- I have no clue what that means or how to solve it.

I think you are on the right way. The command cl (the Visual Studio compiler) is not on your PATH, which causes the bootstrap to fail and the b2 file isn't created. Visual Studio usually comes with a "Developer Command Prompt", which sets all the environmental settings and paths needed for compilation. You can usually find it in the Startmenu under Visual Studio -> Tools. On my computer it is called "Developer Command Prompt for VS2013". Try to open that, and rerun the bootstrap command. Now, bootstrap should work and create the b2 file. Then you can run that to install Boost.
If that still doesn't work, there is the possibility to install pre-compiled binaries. These are available from sourceforge and should work out-of-the-box. However I don't have any experience with those and I'm afraid I can't help you with them.

Thanks for your very quick reply. Unfortunately, the “Developer Command Prompt for VS2015” didn’t solve the problem. I ran bootstrap as “bootstrap.bat mingw”, which solved the cl problem, but gave me the same error for gcc. I’m now looking into the pre-compiled binaries and I’ll let you know when, if ever, I solve it.
From: Hannes Badertscher<EMAIL_ADDRESS>Sent: donderdag 11 februari 2016 8:21
To: HBadertscher/Matlab_BaslerCamDriver
Cc: Bram de Beer
Subject: Re: [Matlab_BaslerCamDriver] Trying and failing to install Boost (#16)
I think you are on the right way. The command cl (the Visual Studio compiler) is not on your PATH, which causes the bootstrap to fail and the b2 file isn't created. Visual Studio usually comes with a "Developer Command Prompt", which sets all the environmental settings and paths needed for compilation. You can usually find it in the Startmenu under Visual Studio -> Tools. On my computer it is called "Developer Command Prompt for VS2013". Try to open that, and rerun the bootstrap command. Now, bootstrap should work and create the b2 file. Then you can run that to install Boost.
If that still doesn't work, there is the possibility to install pre-compiled binaries. These are available from sourceforgehttps://sourceforge.net/projects/boost/files/boost-binaries/ and should work out-of-the-box. However I don't have any experience with those and I'm afraid I can't help you with them.
—
Reply to this email directly or view it on GitHubhttps://github.com/HBadertscher/Matlab_BaslerCamDriver/issues/16#issuecomment-182744953.

The information sent with this e-mail is exclusively intended for the addressee.
If anyone has received this e-mail in error, the receiver is requested to indicate this to the sender and to destroy the e-mail completely without taking notice of the contents in any way or saving it.
Publication, copying, distribution and/or disclosure of the contents to third parties are not permitted.
NTS-Group is not liable for the correct and complete dispatch of the contents, nor for the prompt receipt of this e-mail.
If this e-mail contains so-called computer viruses, NTS-Group is not liable for any damage occurring as a consequence.

I managed to get it to install now. The trick was to change the directory from C:\Program Files\Boost to C:\Boost. Once I did that, it actually installed. Only took me 6 hours to figure that out...
Anyway... now the mex on line 56 gives an error (without message), which might have to do with the fact that you're calling getenv('BOOST_ROOT'),'stage\lib'), but there is no stage\lib directory in the Boost directory.
Has I still not installed it properly?

Really, that did the trick? Good to know!
Uhm yes, I might document that a bit better: Please set an environment variable called BOOST_ROOT which points to your Boost installation. You can create this environment variable by going to Control Panel -> System and Security -> System -> Advanced system settings -> Advanced -> Environment Variables. There, create a new System variable called BOOST_ROOT, and let it point to C:\Boost\boost_whatever_version. Then it should work.

I already did that, since it’s in the Boost installation instructions.
My problem is that none of the directories have the stage/lib directory. There is a ‘libs’ directory, though…
From: Hannes Badertscher<EMAIL_ADDRESS>Sent: donderdag 11 februari 2016 16:55
To: HBadertscher/Matlab_BaslerCamDriver
Cc: Bram de Beer
Subject: Re: [Matlab_BaslerCamDriver] Trying and failing to install Boost (#16)
Really, that did the trick? Good to know!
Uhm yes, I might document that a bit better: Please set an environment variable called BOOST_ROOT which points to your Boost installation. You can create this environment variable by going to Control Panel -> System and Security -> System -> Advanced system settings -> Advanced -> Environment Variables. There, create a new System variable called BOOST_ROOT, and let it point to C:\Boost\boost_whatever_version. Then it should work.
—
Reply to this email directly or view it on GitHubhttps://github.com/HBadertscher/Matlab_BaslerCamDriver/issues/16#issuecomment-182929881.

The information sent with this e-mail is exclusively intended for the addressee.
If anyone has received this e-mail in error, the receiver is requested to indicate this to the sender and to destroy the e-mail completely without taking notice of the contents in any way or saving it.
Publication, copying, distribution and/or disclosure of the contents to third parties are not permitted.
NTS-Group is not liable for the correct and complete dispatch of the contents, nor for the prompt receipt of this e-mail.
If this e-mail contains so-called computer viruses, NTS-Group is not liable for any damage occurring as a consequence.

To test that, I installed the precompiled boost_1_60_0-msvc-12.0-64.exe (as this matches my Visual Studio version). This created a folder lib64-msvc-12.0 in BOOST_ROOT. This folder contains the different libraries, i.e. *.lib and/or *.dll. Do you have such a folder and the corresponding files (only having *.lib is enough)? If yes, please try to replace 'stage\lib' on line 45 in make.m by this subfolder (in case of my test here: 'lib64-msvc-12.0').

It seems you located the problem. I don’t seem to have ANY .lib or .dll files in my BOOST_ROOT directory. I’m assuming something went wrong with the compile, then…? I’ll try to use the precompiled files now and add those to the directory.
From: Hannes Badertscher<EMAIL_ADDRESS>Sent: donderdag 11 februari 2016 17:11
To: HBadertscher/Matlab_BaslerCamDriver
Cc: Bram de Beer
Subject: Re: [Matlab_BaslerCamDriver] Trying and failing to install Boost (#16)
To test that, I installed the precompiled boost_1_60_0-msvc-12.0-64.exe (as this matches my Visual Studio version). This created a folder lib64-msvc-12.0 in BOOST_ROOT. This folder contains the different libraries, i.e. *.lib and/or *.dll. Do you have such a folder and the corresponding files (only having *.lib is enough)? If yes, please try to replace 'stage\lib' on line 45 in make.m by this subfolder (in case of my test here: 'lib64-msvc-12.0').
—
Reply to this email directly or view it on GitHubhttps://github.com/HBadertscher/Matlab_BaslerCamDriver/issues/16#issuecomment-182937634.

The information sent with this e-mail is exclusively intended for the addressee.
If anyone has received this e-mail in error, the receiver is requested to indicate this to the sender and to destroy the e-mail completely without taking notice of the contents in any way or saving it.
Publication, copying, distribution and/or disclosure of the contents to third parties are not permitted.
NTS-Group is not liable for the correct and complete dispatch of the contents, nor for the prompt receipt of this e-mail.
If this e-mail contains so-called computer viruses, NTS-Group is not liable for any damage occurring as a consequence.

Okay, yes seems so... Did any error messages appear during the compilation? Though compilation may continue, there can be erros which cause Boost not to be built. It took me quite a while to set up the first time too... Probably using the precompiled binaries is a faster way. Still, my make.m won't work out-of-the-box.
When I find the time, I'll try to add a check which scans the BOOST_ROOT directory for the libs and gives meaningful error messages and/or installation instructions if they are missing.
Sorry for the troubles you are having, I hope at least it works now, and that the driver does the job.

So far so good. The precompiled binaries installed successfully and I adjusted the path. I also adjusted the path for the pylon library, which seemed to point to the wrong directory too.
Upon running, I got:
=> Creating Libraries
Building with 'Microsoft Visual C++ 2015 Professional'.
Error using mex
cl : Command line error D8003 : missing source filename
So I tried with a different compiler:
(added setenv('MW_MINGW64_LOC','C:/mingw')to the Matlab file)
=> Creating Libraries
Building with 'MinGW64 Compiler (C++)'.
Error using mex
g++: fatal error: no input files compilation terminated.
Any hints on how to solve this latest error?
I really appreciate all your help on this one!
From: Hannes Badertscher<EMAIL_ADDRESS>Sent: donderdag 11 februari 2016 17:23
To: HBadertscher/Matlab_BaslerCamDriver
Cc: Bram de Beer
Subject: Re: [Matlab_BaslerCamDriver] Trying and failing to install Boost (#16)
Okay, yes seems so... Did any error messages appear during the compilation? Though compilation may continue, there can be erros which cause Boost not to be built. It took me quite a while to set up the first time too... Probably using the precompiled binaries is a faster way. Still, my make.m won't work out-of-the-box.
When I find the time, I'll try to add a check which scans the BOOST_ROOT directory for the libs and gives meaningful error messages and/or installation instructions if they are missing.
Sorry for the troubles you are having, I hope at least it works now, and that the driver does the job.
—
Reply to this email directly or view it on GitHubhttps://github.com/HBadertscher/Matlab_BaslerCamDriver/issues/16#issuecomment-182941797.

The information sent with this e-mail is exclusively intended for the addressee.
If anyone has received this e-mail in error, the receiver is requested to indicate this to the sender and to destroy the e-mail completely without taking notice of the contents in any way or saving it.
Publication, copying, distribution and/or disclosure of the contents to third parties are not permitted.
NTS-Group is not liable for the correct and complete dispatch of the contents, nor for the prompt receipt of this e-mail.
If this e-mail contains so-called computer viruses, NTS-Group is not liable for any damage occurring as a consequence.

Well... just a final post, then:
I re-installed MinGW, added C:\MinGW\bin to my path variable, changed the Boost root directory and now it finally doesn't give explicit compiler errors any more.
It does, however, give me a new, blank, error:

make
=> Creating Libraries
Building with 'MinGW64 Compiler (C++)'.
Error using mex

Error in make (line 61)
mex(flags{:},libraries{k,3},ipaths,lpaths,libraries{k,2})   % build
Since there is no actual error description, I can't really continu from here, which makes me very sad...

Trying to build, and stopping at the same line... R2015b with msvc 2013


Firefox 57.0.4 ScrollIntoViewOptions error

In FireFox 57.0.4 on year selection view I got this:

TypeError: 'block' member of ScrollIntoViewOptions 'center' is not a valid value for enumeration Scroll Logical Position.

@material-ui/pickers: "^3.2.7",
date-fns: "^2.7.0",
react: "^16.11.0",

Should be fixed in 3.0.8


docs: clean up readme

remove no needed to top (anchor)
remove road map scope

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Couldn't get keypair from public key

There should be method to get keypair of any public key.
The existing one requires that the one i search for to be already initialized on my keyring.
I expect it to be something like this

    const keyring = new Keyring({ type: sigType });
    signer = keyring.addFromAddress(this.twin.accountId);

I need to verify a signature with knowing only the address or public key.

I don't think it makes sense to make a KeyPair without a private key.
But indeed we are missing a method to verify signatures from other address.
I will make a PR adding a signatureVerify function just like the following: https://github.com/polkadot-js/common/blob/master/packages/util-crypto/src/signature/verify.spec.ts


Awesome Selfhosted

The Awesome Selfhosted list contains many other programs that may be probably addded to the list too
https://github.com/awesome-selfhosted/awesome-selfhosted#communication---email---complete-solutions

Thanks for this really awesome list !


How to prevent the green highlights

I need standard subtitles but the output is the same line multiple times with each individual word highlighted in green.
Any help would be appreciated.

Disable the highlights with word_level=False.
See examples in https://github.com/jianfch/stable-ts#output.


Add image interpolation.

Alessio ? Is it OK ?

Alessio ? Is it OK ?

Can I merge Alessio ?

Can I merge Alessio ?


Adds support for decoding bytes in metadata calls

Even though we're passing strings into the ResultSets, the implementation of Row.getObject turns many of them into bytes because their type is CHAR or VARCHAR (here). Upstream libraries (like liquibase) expect result.getObject to return Strings for things like TABLE_CAT, etc and are throwing exceptions when trying to cast the Object to a String.
This very simple change passes through the Connection into the ResultSet objects created by Metadata requests. This way when we call getObject, the recently added charset decoding code can detect the byte[] and convert them to strings where appropriate. This also makes the constructors more consistent, in my opinion.
This is a bugfix which fixes the following exception for users of Liquibase:
java.lang.ClassCastException: [B cannot be cast to java.lang.String

I added a test case for this, which fails against master but is fixed here

cc @ashudeep-sharma

To accomodate the changes, we are passing connection variable to tthe VitessResultSet. I think its about exposing too much information because one can really execute any query using live connection. Here the information that you mainly require is ConnectionProperties. It would be good if we only expose that while passing to the constructor of ResultSet unless you have any other reason for exposing the Connection object.

@ashudeep-sharma I just pushed a change -- I'm stilling passing in the same object, but VitessResultSet and FieldWithMetadata see it as just a ConnectionProperties not a full VitessConnection. I changed all references to expect a ConnectionProperties and renamed the variable names to match. This should limit the scope enough to be safe.
If someone really wanted too they could still dig around in the code and figure out that they can just cast the ConnectionProperties to a Connection and do what they want. But if we're concerned about that then there is a lot else someone could do with some simple reflection code and there isn't a huge harm. So I think this is fine.

@ashudeep-sharma any other thoughts, or does it look good to merge?

@bbeaudreault : Stucked with some internal issues, will definitely look at it tomorrow.

Thanks!

Looks good to me.
Will wait for @ashudeep-sharma to reply.

Changes looks good in general and I believe you have run the code-coverage as well. I have just one request based on the code changes that have been done recently. I think we are adding too many comments in between the code. Some of the comments are implicit and the logic can be understood based on the calls being made. Should we spend some efforts in cleaning this up.
Also like in tests i saw somewhere in the middle, some comments have been added. Can we ensure that all the comments for the tests being mentioned in the beginning of function and not being in the middle.
Let me know if you have any thoughts/suggestions?

Reviewed 4 of 5 files at r1, 6 of 6 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks pending.

Comments from Reviewable

Thanks for the review and comments @ashudeep-sharma -- in terms of comments in code: I'd be happy to trim it down a bit in some cases. Comments at the top of tests make sense too. However, I think exceptions should be made in other cases. So maybe on a case-by-case basis

yeah i agree on that, if the code is too complicated we should add a comment just above the line else it should be trimmed. Rest looks good to me.

@sougou @alainjobart @michael-berlin This got a LGTM. Could one of you merge when you get a chance? Looking to submit a dependent PR today. Thanks!


Ask for the count data

Hello, I am concerned that your paper has been accepted by the elife magazine.
May I ask you for count data of those single-cell RNAseq data? I am working on single-cell RNA seq of Placenta in patients with eclampsia and would like to refer to your paper.  I have waited for two months, but the phs001886.v1.p1 is not yet available.
I will be very grateful to you. Thanks!
my email address<EMAIL_ADDRESS>

The dbGaP site is in process to being released to the public.
https://www.ncbi.nlm.nih.gov/gap/study/status/35939
They told me that the last step will take about 3 days.

Thank you very much!


Logger context for the log middleware

This PR adds the possibility to add a (static) context to the log message created by the guzzle middleware.

@scuben what about failure case? why you don't use context there? On line 201.

Guess this is ready to merge, isn't it?

Thinking about this: I believe a better solution would be a decorator which adds default context to the log events.
Something like this:
<?php

final class DefaultContextLogger implements \Psr\Log\LoggerInterface
{
    use \Psr\Log\LoggerTrait;

    private $logger;
    private $context = [];

    public function __construct(\Psr\Log\LoggerInterface $logger, array $context = [])
    {
        $this->logger = $logger;
        $this->context = $context;
    }

    public function log($level, $message, array $context = array())
    {
        $this->logger->log($level, $message, $this->context+$context)
    }
}

I would prefer keeping things simple.

Please refer to the solution above.


What is the best way to properly place the toasts to screen on IOS and Android ?

Hi, basically I would like to show the toasts at the similar places according to phone screen and platform. Since android does not have unusable spaces unlike IOS, placing toast at the center of the container looks different and bad in my opinion. There is so much space between top of the screen and the toast in android. Setting justifyContent to flex-start does not resolve my problem neither. In both cases toasts look like this, (when justifyContent=center)

(when justifyContent=flex-start)

red block is the container of the Toastable component on my app.tsx
I am using the renderContent prop to use custom toast like this,
renderContent={(props) => {
          if (!props.status) return;
          if (toastConfig[props.status]) {
            return (
              toastConfig[props.status](props)
            );
          }
        }}

and my toastConfig object is like this,
export const toastConfig: {[key: string]: (props: ToastableBodyProps) => JSX.Element} = {
  info: (_props) => {
    const {message} = _props;
    return (
      <View style={styles.notificationWrapper}>
        <View style={[styles.notificationContainer, {backgroundColor: '#F0F6FE'}]}>
          <InfoIcon />
          <Text style={[styles.notificationTitle, {color: '#4E80EE'}]}>{message || 'Info'}</Text>
          <NotificationCloseIcon fill="#4E80EE" />
        </View>
      </View>
    );
  },
  ...

In the end, what is the best way to render toasts at similar places and not dependent to screen or platform ?

I have managed to get it working with this, but I believe this is not the best way. Also this feature must be in any toast package.
Using justfiyContent=flex-start
and updating the renderContent prop to
renderContent={(props) => {
          if (!props.status) return;
          if (toastConfig[props.status]) {
            return (
              <SafeAreaView style={{marginTop: 12}}>
                {toastConfig[props.status](props)}
              </SafeAreaView>
            );
          }
        }}

@MtyldZ Thank you for your finding, it's fixed in the current version (0.3.0). Now you need to give offset value to Toastable component. Please refer to https://github.com/rnheroes/react-native-toastable?tab=readme-ov-file#usage


chore(TransactionFeedV2): Persist and rehydrate the first page of the feed

Description
10th PR of RET-1207. Adds a new feedFirstPage field to the Redux so the first page of the feed can be persisted and rehydrated on the app init.
Test plan
Added test to check a proper rehydration flow for the first page of the feed
Related issues

Relates to RET-1207

Backwards compatibility
Yes
Network scalability
If a new NetworkId and/or Network are added in the future, the changes in this PR will:

[x] Continue to work without code changes, OR trigger a compilation error (guaranteeing we find it when a new network is added)

@jeanregisser all the redux-related side-effects were moved to the slice in this PR


What about other providers?

As i see, it is uses just one endpoint to get stats?
https://github.com/jasonroman/nba-api/blob/master/src/Request/Stats/AbstractStatsRequest.php#L9
But What about for example this one if i want to use this endpoint? Can it be changed somehow? Or Request classes does not support it?

Hello,
There are endpoints from 6 different domains.  If you look in the Request directory, you will see 6 sub-directories.  Each one of those points to a different domain.  For instance, the endpoint you are looking for is found in this request class:
https://github.com/jasonroman/nba-api/blob/master/src/Request/Data/Prod/General/TodayRequest.php
That request extends a base Data class found here:  https://github.com/jasonroman/nba-api/blob/master/src/Request/Data/AbstractDataRequest.php#L13
You can also check nbasense.com for a full reference aside from sifting through the code.  Let me know if that helps!

Oh, now I get it. But it confuses a little bit. :)
But what about making one request for player stats for example? And just pass enpoint (or class which implements specific interface).
For example:
$request = new PlayerRequest(new NbaDataProvider()); (or new NbaStatsProvider())
$client->request($request);

I know that not all endpoints returns player stats.

I'd love to help but I am not exactly sure what you are asking. Could you clarify? The way I designed this is to have a single request per endpoint. The reason for this is each endpoint is very different in the options you can pass to it and the results that are returned. Many player stats endpoints, for example, use the same parameters but they don't always share the same valid options for those parameters.
I think reading through http://nbasense.com/nba-api/requests will give you a more thorough understanding of the structure.

Nevermind. Yes, you are correct. Each endpoint returns different results.


Remove while loop from search_products

I think that the while loop in search_products is causing more issues than it solves. If someone needs to use the pagination they can use the item_count and items_per_page parameters built into the SDK.
As currently implemented the while loop means that any time a user searches for a product and the search returns fewer than item_count results they're actually making two calls to the API, not one call.
So, if the user searches for a very specific title, and the API returns one result, but we have item_count set by default to ten items, the wrapper makes a second (unnecessary) call to Amazon.

This is solved on #27 on line 289:
if len(response.search_result.items) < items_per_page:
     break


Lost characters from iso-8859-15 on UTF-8 system

With these config, on specific for a web and other general for use readability on all webs, when the web is on iso-8859-15, readability simply drops special characters, so thing like "camión" inserts on the database like "" camin"
{
"elpais.com": {
"type": "xpath",
"xpath": "article",
"cleanup": ["button"]
},
".": {
"type": "readability"
}
}

If you want to usea readability method whit other than utf-8 webs, it's mandatory to put an undocuemented? conf in yout json.
{
"elpais.com": {
"type": "xpath",
"xpath": "article",
"cleanup": ["button"]
},
".": {
"type": "readability",
"force_unicode": "1"
}
}

The force unicode option is "technically" documented as it's in the massive example config on the readme.
The Readme as it is needs a bit of a review and some rationalization.


New version Turing: 0.6.17

Registering: Turing
Repository: https://github.com/TuringLang/Turing.jl
Version: v0.6.17
Commit: 69f54b6c39192461268f770f8bfcd2d268ccdd58
Proposed by: @cpfiffer
Reviewed by: @cpfiffer
Reference: https://github.com/TuringLang/Turing.jl/issues/764

Please add some compatibility constraints, at least on julia.

We've added some bounds to Julia, thanks for catching that.


Update _forms.css

Making radio input:checked circle more clear and bigger thus improving UX.

Appreciate the PR! Unfortunately we have to close this for now because 2.0 has removed the custom form controls


Changing ivy-initial-inputs-alist has no effect on startup

What did you expect to happen?
Changing ivy-initial-inputs-alist should change the initial character on the input.
What actually happened?
Changing works when evaluating manually, but not on startup.
Describe your attempts to resolve the issue
Try setting the variable in many ways, in and outside of use-package!, also tried using after! and setq-default.
Here's one of the attempts:
(after! (ivy counsel)
  (setq ivy-initial-inputs-alist
        '((org-refile . "^")
          (org-agenda-refile . "^")
          (org-capture-refile . "^")
          (Man-completion-table . "^")
          (counsel-M-x . "^")
          (woman . "^"))))

Steps to reproduce
Change ivy-initial-inputs-alist and see if the change is loaded on startup.
System Information
https://pastebin.com/NjFtxjwm

it seems that ivy-initial-inputs-alist is forced to be nil in modules/completion/ivy/config.el.
it's wired that there is variable in modules/tools/lookup/autoload/online.el same as defined in ivy.el.

it seems that ivy-initial-inputs-alist is forced to be nil in modules/completion/ivy/config.el. it's wired that there is variable in modules/tools/lookup/autoload/online.el same as defined in ivy.el.

I'm sorry, I'm not a programmer, what does that mean?

it seems that ivy-initial-inputs-alist is forced to be nil in modules/completion/ivy/config.el. it's wired that there is variable in modules/tools/lookup/autoload/online.el same as defined in ivy.el.

I'm sorry, I'm not a programmer, what does that mean?

Your configuration will not be effective. You can refer to comments in modules/completion/ivy/config.el.

it seems that ivy-initial-inputs-alist is forced to be nil in modules/completion/ivy/config.el. it's wired that there is variable in modules/tools/lookup/autoload/online.el same as defined in ivy.el.

I'm sorry, I'm not a programmer, what does that mean?

Your configuration will not be effective. You can refer to comments in modules/completion/ivy/config.el.

So It's impossible to change that? :/

it seems that ivy-initial-inputs-alist is forced to be nil in modules/completion/ivy/config.el. it's wired that there is variable in modules/tools/lookup/autoload/online.el same as defined in ivy.el.

I'm sorry, I'm not a programmer, what does that mean?

Your configuration will not be effective. You can refer to comments in modules/completion/ivy/config.el.

So It's impossible to change that? :/

i am looking into this issue. but no idea about about it. i will sync with you when i work it out.


Add post: An online book, “Writing Interpreters in Rust: a Guide”

Please add this post:
Post URL: https://pliniker.github.io/post/rust-hosted-langs/
Author Name: Peter Liniker
Categories: Tools and Applications
Blog RSS/Atom/JSON Feed: https://pliniker.github.io/feed.xml
Thank you for your invaluable read-rust service! :bow:

Thanks! Sorry it took so long to post it.


Muse S not found (MS02) under macOS Montery 12.6

Hello,
I was using uvicmuse a while ago to stream data from my muse 2 headset. Now I am on a new laptop (2017 macbook air, macOS Montery) and uvicmuse is not able to find the muse headset with or without dongle. I am running it in an conda environement with nothing but uvicmuse and it's dependencies installed.

same issue here. did you find any solution?

Do you get the error "No BLE module found" or is it a different error?


[CH] Performance regression when reading files from Hive(HDFS)

Backend
CH (ClickHouse)
Bug description
SQL: select count(distinct country) from ttt where day = '2024-08-26' and hour = '00'
Related PR: https://github.com/apache/incubator-gluten/pull/6841
371be6f860c2b409ea70a79e0c2e4e72a2624e38 ok

371d448c3b512b1cbb3272e932cb7a57b9da4ba6 NOT OK

vanila:

About 4.6x slower than vanila 332, and 18x slower than last commit.
Spark version
Spark-3.3.x
Spark configurations
No response
System information
No response
Relevant logs
No response

Thanks for finding the problem, I will fix it as soon as possible.


🚀 [Feature] Handle PID in Frontend

🚀 Feature

We need to handle a PID parameter in the frontend.

The PID is the publisher ID, a referral, from EloPage.
This PID is transmitted via Parameter to our application: ourapplication.com/path?pid=123
The PID is a number(!) of a specific length(?)

We want to:

[ ] Save the PID in our application
[ ] Remove the parameter from URL (?)
[ ] Allow the parameter on every route and handle it properly according to our rules
[ ] Transmit the PID with the register process
[ ] Transmit the PID with the login process
[ ] Allow a revisit of the page without losing a previous PID (?)(cookie)
[ ] Handle different PIDs and have priorities defined
[ ] (Backend) Have a default pid if none present (not really this issue)

It is ok to implement only parts of the mechanic (e.g. do not save it across sessions), but tickets for the missing parts need to be made.
Minimum requirement:

Properly handle the PID on the register process
Allow multiple entry points to the application with a pid and have it available in register.

@ulfgebhardt Is this path example ourapplication.com/path/?pid=123 coorect? I would expect ourapplication.com/path?pid=123

@ulfgebhardt Is this path example ourapplication.com/path/?pid=123 coorect? I would expect ourapplication.com/path?pid=123

You are right. Corrected


A suggestion

I think the fallen player should be weak and should not be able to continue to break blocks, place blocks, and attack other mobs (these options can be added in the configuration file to configure the behavior of the fallen player to attack and place and destroy blocks), and at the same time, the player should be so weak that they can't jump after falling (I think this can also add an option in the configuration to prohibit fallen players from jumping), which is beneficial for some special server games to use this mod, I think adding these features is closer to incapacitated, hope for your update

All of these are features of the latest update. Most of them on by default even.


MissingPluginException(No implementation found for method medium on channel vibrate

use real devices

me too, how to fix?


Running packse fetch and serve,  get UnicodeDecodeError

Steps to Reproduce:

Linux Python 3.12 environment, Pip 24.0
pip install packse[serve]
packse fetch

Output:
Cloning repository https://github.com/astral-sh/packse
Checking out directory 'scenarios' at ref 0.3.7
Found does-not-exist.json
Found example.json
Found excluded.json
Found extras.json
Found incompatible-versions.json
Found local.json
Found prereleases.json
Found requires-python.json
Found wheels.json
Found yanked.json

packse serve scenarios/

Output:
$ packse serve scenarios/
Performing initial build...
Building 'local-simple-5b70bb3c' in directory 'build/local-simple-5b70bb3c'
Building 'package-only-prereleases-85d9c93d' in directory 'build/package-only-prereleases-85d9c93d'
Building 'example-961b4c22' in directory 'build/example-961b4c22'
Building 'local-not-used-with-sdist-207c9df5' in directory 'build/local-not-used-with-sdist-207c9df5'
Building 'local-not-latest-b8eed201' in directory 'build/local-not-latest-b8eed201'
Building 'local-used-without-sdist-ea57116a' in directory 'build/local-used-without-sdist-ea57116a'
Building 'package-only-prereleases-in-range-4c7ed550' in directory 'build/package-only-prereleases-in-range-4c7ed550'
Building 'requires-greater-version-does-not-exist-b33b2dca' in directory 'build/requires-greater-version-does-not-exist-b33b2dca'
Building 'local-transitive-confounding-082fdb86' in directory 'build/local-transitive-confounding-082fdb86'
Building 'requires-less-version-does-not-exist-a71baf60' in directory 'build/requires-less-version-does-not-exist-a71baf60'
Building 'local-transitive-a79dc870' in directory 'build/local-transitive-a79dc870'
Building 'requires-package-does-not-exist-388e8135' in directory 'build/requires-package-does-not-exist-388e8135'
Building 'transitive-requires-package-does-not-exist-ed146f67' in directory 'build/transitive-requires-package-does-not-exist-ed146f67'
Building 'requires-package-only-prereleases-in-range-global-opt-in-8229237e' in directory 'build/requires-package-only-prereleases-in-range-global-opt-in-8229237e'
Building 'requires-package-prerelease-and-final-any-7c7cec06' in directory 'build/requires-package-prerelease-and-final-any-7c7cec06'
Building 'package-prerelease-specified-only-prerelease-available-2b59d4b1' in directory 'build/package-prerelease-specified-only-prerelease-available-2b59d4b1'
Building 'requires-exact-version-does-not-exist-ef648a78' in directory 'build/requires-exact-version-does-not-exist-ef648a78'
Building 'package-prerelease-specified-only-final-available-1284cb1e' in directory 'build/package-prerelease-specified-only-final-available-1284cb1e'
Building 'package-multiple-prereleases-kinds-ca392ea8' in directory 'build/package-multiple-prereleases-kinds-ca392ea8'
Building 'package-prerelease-specified-mixed-available-4204a13b' in directory 'build/package-prerelease-specified-mixed-available-4204a13b'
Building 'transitive-package-only-prereleases-589ddff5' in directory 'build/transitive-package-only-prereleases-589ddff5'
Building 'transitive-prerelease-and-stable-dependency-73a8bb29' in directory 'build/transitive-prerelease-and-stable-dependency-73a8bb29'
Building 'transitive-package-only-prereleases-in-range-opt-in-dc3b4feb' in directory 'build/transitive-package-only-prereleases-in-range-opt-in-dc3b4feb'
Building 'package-multiple-prereleases-numbers-b08385b3' in directory 'build/package-multiple-prereleases-numbers-b08385b3'
Building 'transitive-package-only-prereleases-in-range-91d42144' in directory 'build/transitive-package-only-prereleases-in-range-91d42144'
Building 'transitive-prerelease-and-stable-dependency-many-versions-b550f888' in directory 'build/transitive-prerelease-and-stable-dependency-many-versions-b550f888'
Building 'transitive-prerelease-and-stable-dependency-opt-in-87b86d9c' in directory 'build/transitive-prerelease-and-stable-dependency-opt-in-87b86d9c'
Building 'transitive-prerelease-and-stable-dependency-many-versions-holes-34e5a2d3' in directory 'build/transitive-prerelease-and-stable-dependency-many-versions-holes-34e5a2d3'
Building 'package-only-prereleases-boundary-dd941311' in directory 'build/package-only-prereleases-boundary-dd941311'
Building 'package-prereleases-boundary-16ba0350' in directory 'build/package-prereleases-boundary-16ba0350'
Building 'package-prereleases-global-boundary-ca458d54' in directory 'build/package-prereleases-global-boundary-ca458d54'
Building 'package-prereleases-specifier-boundary-ed960178' in directory 'build/package-prereleases-specifier-boundary-ed960178'
Building 'specific-tag-and-default-0336e09c' in directory 'build/specific-tag-and-default-0336e09c'
Building 'only-wheels-f756804e' in directory 'build/only-wheels-f756804e'
Building 'no-wheels-0bb7827a' in directory 'build/no-wheels-0bb7827a'
Building 'no-wheels-with-matching-platform-c1494f5f' in directory 'build/no-wheels-with-matching-platform-c1494f5f'
Building 'no-sdist-no-wheels-with-matching-platform-46f0c229' in directory 'build/no-sdist-no-wheels-with-matching-platform-46f0c229'
Building 'no-sdist-no-wheels-with-matching-python-7b1e0ba3' in directory 'build/no-sdist-no-wheels-with-matching-python-7b1e0ba3'
Building 'no-sdist-no-wheels-with-matching-abi-2f8e7202' in directory 'build/no-sdist-no-wheels-with-matching-abi-2f8e7202'
Building 'no-wheels-no-build-1db1b462' in directory 'build/no-wheels-no-build-1db1b462'
Building 'only-wheels-no-binary-859a4cea' in directory 'build/only-wheels-no-binary-859a4cea'
Building 'no-build-bb7d81b8' in directory 'build/no-build-bb7d81b8'
Building 'no-binary-b1d20084' in directory 'build/no-binary-b1d20084'
Building 'package-only-yanked-2919761d' in directory 'build/package-only-yanked-2919761d'
Building 'requires-package-yanked-and-unyanked-any-c1d7f24e' in directory 'build/requires-package-yanked-and-unyanked-any-c1d7f24e'
Building 'package-only-yanked-in-range-f1ab2a3f' in directory 'build/package-only-yanked-in-range-f1ab2a3f'
Building 'package-yanked-specified-mixed-available-e9d957b6' in directory 'build/package-yanked-specified-mixed-available-e9d957b6'
Building 'transitive-package-only-yanked-in-range-e2eb8cbc' in directory 'build/transitive-package-only-yanked-in-range-e2eb8cbc'
Building 'transitive-package-only-yanked-fbebea19' in directory 'build/transitive-package-only-yanked-fbebea19'
Building 'transitive-package-only-yanked-in-range-opt-in-637e27eb' in directory 'build/transitive-package-only-yanked-in-range-opt-in-637e27eb'
Building 'transitive-yanked-and-unyanked-dependency-opt-in-b2a53fbd' in directory 'build/transitive-yanked-and-unyanked-dependency-opt-in-b2a53fbd'
Building 'transitive-yanked-and-unyanked-dependency-0abad3b6' in directory 'build/transitive-yanked-and-unyanked-dependency-0abad3b6'
Building 'direct-incompatible-versions-516a39b2' in directory 'build/direct-incompatible-versions-516a39b2'
Building 'transitive-incompatible-with-root-version-c4bc5b1f' in directory 'build/transitive-incompatible-with-root-version-c4bc5b1f'
Building 'transitive-incompatible-with-transitive-4132b57a' in directory 'build/transitive-incompatible-with-transitive-4132b57a'
Building 'python-version-does-not-exist-db416e00' in directory 'build/python-version-does-not-exist-db416e00'
Building 'python-less-than-current-c050f6d5' in directory 'build/python-less-than-current-c050f6d5'
Building 'python-greater-than-current-f9f64a8d' in directory 'build/python-greater-than-current-f9f64a8d'
Building 'python-greater-than-current-many-63ea5ba6' in directory 'build/python-greater-than-current-many-63ea5ba6'
Building 'python-greater-than-current-patch-23c0760c' in directory 'build/python-greater-than-current-patch-23c0760c'
Building 'python-greater-than-current-excluded-2255f47c' in directory 'build/python-greater-than-current-excluded-2255f47c'
Building 'python-greater-than-current-backtrack-f53b1cd6' in directory 'build/python-greater-than-current-backtrack-f53b1cd6'
Building 'incompatible-python-compatible-override-cc53ff2b' in directory 'build/incompatible-python-compatible-override-cc53ff2b'
Building 'compatible-python-incompatible-override-df025f97' in directory 'build/compatible-python-incompatible-override-df025f97'
Building 'incompatible-python-compatible-override-unavailable-no-wheels-161a27c2' in directory 'build/incompatible-python-compatible-override-unavailable-no-wheels-161a27c2'
Building 'incompatible-python-compatible-override-available-no-wheels-6e4d1670' in directory 'build/incompatible-python-compatible-override-available-no-wheels-6e4d1670'
Building 'incompatible-python-compatible-override-no-compatible-wheels-1b13caa9' in directory 'build/incompatible-python-compatible-override-no-compatible-wheels-1b13caa9'
Building 'incompatible-python-compatible-override-other-wheel-497d1feb' in directory 'build/incompatible-python-compatible-override-other-wheel-497d1feb'
Building 'python-patch-override-no-patch-8429e03a' in directory 'build/python-patch-override-no-patch-8429e03a'
Building 'python-patch-override-patch-compatible-b6cdac48' in directory 'build/python-patch-override-patch-compatible-b6cdac48'
Building 'extra-required-bbd42201' in directory 'build/extra-required-bbd42201'
Building 'missing-extra-d7b6e0b1' in directory 'build/missing-extra-d7b6e0b1'
Building 'multiple-extras-required-73ee83b9' in directory 'build/multiple-extras-required-73ee83b9'
Building 'all-extras-required-61571b3c' in directory 'build/all-extras-required-61571b3c'
Building 'extra-incompatible-with-extra-eeb916b5' in directory 'build/extra-incompatible-with-extra-eeb916b5'
Building 'extra-incompatible-with-extra-not-requested-97cf0638' in directory 'build/extra-incompatible-with-extra-not-requested-97cf0638'
Building 'extra-incompatible-with-root-6faf09f6' in directory 'build/extra-incompatible-with-root-6faf09f6'
Building 'extra-does-not-exist-backtrack-05f843a2' in directory 'build/extra-does-not-exist-backtrack-05f843a2'
Building 'excluded-only-version-d5e62e6c' in directory 'build/excluded-only-version-d5e62e6c'
Building 'excluded-only-compatible-version-26dd59e3' in directory 'build/excluded-only-compatible-version-26dd59e3'
Building 'dependency-excludes-range-of-compatible-versions-cb8d51de' in directory 'build/dependency-excludes-range-of-compatible-versions-cb8d51de'
Building 'dependency-excludes-non-contiguous-range-of-compatible-versions-5d038b4f' in directory 'build/dependency-excludes-non-contiguous-range-of-compatible-versions-5d038b4f'
Exception in thread serve-build-scenarios:
Traceback (most recent call last):
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/threading.py", line 1073, in _bootstrap_inner
    self.run()
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/threading.py", line 1010, in run
    self._target(*self._args, **self._kwargs)
  File "/home/damian/.pyenv/versions/packse_testing_312/lib/python3.12/site-packages/packse/serve.py", line 79, in build_scenarios
    build(
  File "/home/damian/.pyenv/versions/packse_testing_312/lib/python3.12/site-packages/packse/build.py", line 88, in build
    results = [future.result() for future in futures]
               ^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/packse_testing_312/lib/python3.12/site-packages/packse/build.py", line 179, in build_scenario
    future.result()
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/packse_testing_312/lib/python3.12/site-packages/packse/build.py", line 232, in build_scenario_package
    package_destination = create_from_template(
                          ^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/packse_testing_312/lib/python3.12/site-packages/packse/template.py", line 63, in create_from_template
    chevron_blue.render(file_path.read_text(), scope, no_escape=True)
                        ^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.1/lib/python3.12/pathlib.py", line 1028, in read_text
    return f.read()
           ^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcb in position 0: invalid continuation byte
Build thread failed..

Interesting thanks I've never seen this I'll try to reproduce.
Can you packse build the scenarios separately from serve?

Sorry I can't reproduce this on Arch Linux or macOS.

Sorry, I've been unable to work on OSS for a few days, as soon as I get a chance I'll create a clean environment and try and reproduce.

Still reproducible in a clean environment. I'm using pyenv because it compiles directly from CPython and, at least with pip, installer tests can be sensitive to changes different distributers make.:

In a fresh directory
pyenv install 3.12 (And fix any compiler errors if there are any)
pyenv virtualenv uv_testing_312
pyenv activate uv_testing_312
pip install packse[serve]
packse fetch
packse build scenarios/

Trackeback:
Traceback (most recent call last):
  File "/home/damian/.pyenv/versions/uv_testing_312/bin/packse", line 8, in <module>
    sys.exit(entrypoint())
             ^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/cli.py", line 44, in entrypoint
    args.call(args)
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/cli.py", line 76, in _call_build
    build(
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/build.py", line 88, in build
    results = [future.result() for future in futures]
               ^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/build.py", line 179, in build_scenario
    future.result()
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/build.py", line 232, in build_scenario_package
    package_destination = create_from_template(
                          ^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/template.py", line 64, in create_from_template
    chevron_blue.render(file_path.read_text(), scope, no_escape=True)
                        ^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/pathlib.py", line 1028, in read_text
    return f.read()
           ^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcb in position 0: invalid continuation byte

I put a breakpoint around line 64, in create_from_template, and I found these values:
(Pdb)  file_path
PosixPath('/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/templates/package/{{ package-name }}-{{ version }}/src/{{ module-name }}/__pycache__/__init__.cpython-312.pyc')
(Pdb) scope
{'scenario-name': 'local-used-without-sdist', 'package-name': 'local-used-without-sdist-ea57116a', 'module-name': 'local_used_without_sdist_ea57116a', 'version': '0.0.0', 'dependencies': [<Requirement('local-used-without-sdist-a-ea57116a==1.2.3')>], 'optional-dependencies': [], 'requires-python': '>=3.8', 'description': 'Even if there is a 1.2.3 version published, if it is unavailable for some reason (no sdist and no compatible wheels in this case), a 1.2.3 version with a local segment should be usable instead.'}
(Pdb) new_file_path
PosixPath('/home/damian/testing_remote/packse/build/local-simple-5b70bb3c/local-simple-5b70bb3c-0.0.0/src/local_simple_5b70bb3c/__pycache__/__init__.cpython-312.pyc')
(Pdb) file_path.read_bytes()
b'\xcb\r\r\n\x00\x00\x00\x00\xa1L\xf2e\x1e\x00\x00\x00\xe3\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x01\x00\x00\x00\x00\x00\x00\x00\xf3\x08\x00\x00\x00\x97\x00d\x00Z\x00y\x01)\x02z\r{{ version }}N)\x01\xda\x0b__version__\xa9\x00\xf3\x00\x00\x00\x00\xfa\xb0/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/templates/package/{{ package-name }}-{{ version }}/src/{{ module-name }}/__init__.py\xfa\x08<module>r\x06\x00\x00\x00\x01\x00\x00\x00s\n\x00\x00\x00\xf0\x03\x01\x01\x01\xd8\x0e\x1d\x81\x0br\x04\x00\x00\x00'

Thanks for the additional details! If you just git clone this repository and run packse build scenarios do you get the same error?
I'll attempt to reproduce again but I was using pyenv on Linux so I think we're pretty close to the same environment.

Okay, I found a differentiator or it working vs. not working, if I install packse from either pypi or source directory then it fails, regardless of whether I packse fetch the scenarios or git clone  the scenarios.
However, it works fine if I git clone packse source and then pip install in editable mode.

git clone https://github.com/astral-sh/packse
cd packse/
pip install .[serve] --force
packse build --force scenarios/

Output:
Building 'dependency-excludes-non-contiguous-range-of-compatible-versions-5d038b4f' in directory '/home/damian/testing_remote/packse/build/dependency-excludes-non-contiguous-range-of-compatible-versions-5d038b4f'
Traceback (most recent call last):
  File "/home/damian/.pyenv/versions/uv_testing_312/bin/packse", line 8, in <module>
    sys.exit(entrypoint())
             ^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/cli.py", line 44, in entrypoint
    args.call(args)
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/cli.py", line 76, in _call_build
    build(
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/build.py", line 88, in build
    results = [future.result() for future in futures]
               ^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/build.py", line 179, in build_scenario
    future.result()
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/build.py", line 232, in build_scenario_package
    package_destination = create_from_template(
                          ^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/envs/uv_testing_312/lib/python3.12/site-packages/packse/template.py", line 63, in create_from_template
    chevron_blue.render(file_path.read_text(), scope, no_escape=True)
                        ^^^^^^^^^^^^^^^^^^^^^
  File "/home/damian/.pyenv/versions/3.12.2/lib/python3.12/pathlib.py", line 1028, in read_text
    return f.read()
           ^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xcb in position 0: invalid continuation byte

pip install -e .
packse build --force scenarios/
Success!

Not looked into why that's happening though.

Stepping back a little bit, it seems that this function is trying to read templated source files and write out concrete source files.
For whatever reason in my environment it ends up reading pyc files, I don't think it should be. I think it would be reasonable to have an exclude (pyc files and __pycache__ directories) filter or an include filter (only py files?).
If I change:
    for root, _, files in template_path.walk():

To:
    for root, dirs, files in template_path.walk():
        with contextlib.suppress(ValueError):
            dirs.remove("__pycache__")

And reinstall, I no longer get an error.
Have you been install with uv pip install rather than pip install? Does perhaps one generate bytecode by default and the other doesn't?

Ah pip install does compile byte-code on install default whereas uv pip install requires opt-in! Nice catch!
We should definitely filter those files from the walk.

It looks like poetry doesn't compile by default either and you need to pass --compile to the install command.
I could raise a PR to add this to the CI test environment and update the code as above, if you'd like?


bug: dashboard duplicate projects

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.2
Operating system/version
Windows 11
Describe the bug
Similar to #171, the projects list shows duplicate entries, but this seems more directly caused by capitalization:

Steps To Reproduce
Install lazyvim, open the same project multiple times
Expected Behavior
Project entries should be unique if theyre on the same path on Windows
Repro
vim.env.LAZY_STDPATH = ".repro"
load(vim.fn.system("curl -s https://raw.githubusercontent.com/folke/lazy.nvim/main/bootstrap.lua"))()

require("lazy.minit").repro({
  spec = {
    {
      "folke/snacks.nvim",
      opts = {
        dashboard = {
          enabled = true,
          sections = {
            {
              pane = 2,
              title = "Projects",
              section = "projects",
            },
          },
        },
      },
    },
    -- add any other plugins here
  },
})

won't fix. sorry


Exception when a command triggers a route change

The AppDrawer will be detached if a command triggered a route change
Check if the AppDrawer is attached before hiding it.

Fixed in commit 558828f32baed9bf398814993748c097b385f0b0


Update 20221024_SouthPole_FF_transaction_1_step3_match.csv

Adjusting allocation_674 from 159 MWh to 80 MWh.

Also double checked the contracts 24,25,26. The attributions work. Thanks for correcting. 👍


Logging on after instance creation challenges

First, thank you for the work you have put into this.
A bit of a backstory, I signed up before all of the 'Out of host capacity' shenanigans. However, I made the mistake of deleting an instance and was unable to create a new one without your awesome script.
I'm having trouble logging in.  I have successfully added a public ip address by going to the attached vnic settings and clicking the three little dots to add an ipv4 address.  I ended up creating a "reserved" one and then attempted to ssh to my new instance and this is what I get:
ssh -i id_rsa_private.pub<EMAIL_ADDRESS><EMAIL_ADDRESS>Permission denied (publickey)
I let your script create the ssh keys for me.
Any idea what I'm doing wrong and how to fix?
Thanks!

Hello,
I'm glad to hear that my script has been helpful to you.
Regarding the issue you are encountering, it seems you are using the public key instead of the private key to SSH into your instance. SSH is expecting the private key for authentication
When you generate SSH keys, you typically have a public key (id_rsa_public.pub) and a private key (id_rsa_private). The private key is what you should use to authenticate yourself when connecting via SSH.

I believe id_rsa_private.pub is the the private key:
ubuntu@la:~/oracle-freetier-instance-creation$ file id_rsa_private.pub
id_rsa_private.pub: PEM RSA private key
This is the rest of the folder.
ubuntu@la:~/oracle-freetier-instance-creation$ ls -al
total 124
drwxrwxr-x  4 ubuntu ubuntu  4096 Mar 22 19:04 .
drwxr-x--- 18 ubuntu ubuntu  4096 Mar 22 19:48 ..
-rw-rw-r--  1 ubuntu ubuntu 16787 Mar 21 18:34 email_content.html
drwxrwxr-x  8 ubuntu ubuntu  4096 Mar 21 18:34 .git
-rw-rw-r--  1 ubuntu ubuntu  3085 Mar 21 18:34 .gitignore
-rw-------  1 ubuntu ubuntu  1679 Mar 21 19:03 id_rsa_private.pub
-rw-rw-r--  1 ubuntu ubuntu   402 Mar 21 19:03 id_rsa.pub
-rw-rw-r--  1 ubuntu ubuntu  8936 Mar 21 23:41 images_list.json
-rw-rw-r--  1 ubuntu ubuntu   219 Mar 21 23:41 INSTANCE_CREATED
-rw-rw-r--  1 ubuntu ubuntu   138 Mar 21 19:17 launch_instance.log
-rw-rw-r--  1 ubuntu ubuntu  1075 Mar 21 18:34 LICENSE
-rw-rw-r--  1 ubuntu ubuntu 13768 Mar 21 18:34 main.py
-rw-rw-r--  1 ubuntu ubuntu  1730 Mar 21 18:37 oci_api_private_key.pem
-rw-rw-r--  1 ubuntu ubuntu   340 Mar 21 18:40 oci_config
-rw-rw-r--  1 ubuntu ubuntu   485 Mar 21 18:42 oci.env
-rw-rw-r--  1 ubuntu ubuntu  7840 Mar 21 18:34 README.md
-rw-rw-r--  1 ubuntu ubuntu    26 Mar 21 18:34 requirements.txt
-rw-rw-r--  1 ubuntu ubuntu   340 Mar 21 18:40 sample_oci_config
-rw-rw-r--  1 ubuntu ubuntu  3238 Mar 21 23:41 setup_and_info.log
-rwxrwxr-x  1 ubuntu ubuntu   601 Mar 21 18:34 setup_init.sh
drwxrwxr-x  5 ubuntu ubuntu  4096 Mar 21 18:57 .venv
Am I using the wrong key?
Thanks!

ahh.. my bad. that's the correct key.
can you try to set the key permissions to 600 and then try logging in ?
chmod 600 id_rsa_private.pub

Same problem:
ls -al id_rsa_private.pub
-rw------- 1 ubuntu ubuntu 1679 Mar 21 19:03 id_rsa_private.pub
ssh -i id_rsa_private.pub<EMAIL_ADDRESS>... Permission denied (publickey).
Any other ideas

It seems like the issue might be related to the SSH configuration or permissions.
you can try this :

Stop the instance and navigate to the boot volume section.
Detach the boot volume.
Go to a VM.Standard.E2.1.Micro instance.
In the block volumes section, attach the previously detached volume to the VM.Standard.E2.1.Micro instance.

After completing these steps, access the .ssh folder of ARM instance volume and inspect the authorized_keys file along with its permissions. You can also generate new SSH keys and append them to the authorized_keys file for access


A ribbon rule integrated with nacos cluster and respect nacos server'…

A ribbon rule integrated with nacos cluster and respect nacos server's weight configuration.

circleci build error.
log.warn("{}服务当前无任何实例", name);

it seems the log is not defined.

circleci build error.
log.warn("{}服务当前无任何实例", name);

it seems the log is not defined.

My fault. I use lombok in my local machine...


The current editing context is lost after refreshing the page

code-server version: 2.1692-vsc1.39.2
OS Version: Ubuntu 18.0.4

Description
The current editing context (opened files, etc, )is not kept after refreshing/reloading the editor page. It used to be OK. The latest version I know that works is 2.1655-vsc1.39.2.
Reloading the editor page is required when the server is shutdown or disconnected and the reconnected
Steps to Reproduce

Open a folder
Select a file to edit,
Disconnect from the server or shutdown the server and restart it
Reconnect to the server and then one get into an initial editing context instead of the previous one with one file open

It seems to work again, don't know why yet. So I am going to close it ...


Discuss with club leaders what curriculum they will run in their meeting and create any materials that are needed

From @jonleung on November 17, 2015 21:42
Copied from original issue: hackedu/hackedu#500

Closing this for now because it is accounted for by collecting curriculum each week.


go get -d has confusing error situation

I am running go 1.4.2 on Linux/amd64 and noticed that I get an error using go get in a situation that doesn't seem to be an error. Here are the commands to reproduce it:
$ mkdir /home/William/go
$ export GOPATH=/home/William/go
$ go get -d golang.org/x/tools && echo "download of source was successful."

In this example, the first time I run "go get -d golang.org/x/tools", I do not get the successful message. Instead, a failure error code is returned along with the message:
" golang.org/x/tools: No buildable Go source files in /home/William/go/src/golang.org/x/tools"
If "-d" is download only, is this a bug, or am I misunderstanding what "-d" means?
Thanks,
William

I get the same error message and failure exit every time if I add the -u option to the "go get" command:
$ go get -d -u golang.org/x/tools

Thanks,
William

go get is for fetching packages, not repositories. golang.org/x/tools is the root of the tools repository, so go get golang.org/x/tools will succeed in checking out the repository but then fail as it tries to build tools package (as there is no such package).
This explains why -d works, as it only tries to download the package but doesn't try to build.
I'm not sure why go get -d -u should be different to go get -d in its error state. Maybe that's a bug?

My thinking was that without -d it should try to build, but with -d it should download only, so "go get -d" and "go get -d -u" should not have an error state if they download the repository. However, "go get" or "go get -u" should have the error state if they try to build.

@adg:
I'm not sure how clear I was in my original description of this issue, so I want to show the sequence of commands I ran along side my questions:
GOROOT is /usr/lib/go
$ rm -fr /home/William/go
$ mkdir /home/William/go
$ export GOPATH=/home/William/go
$ cd /home/William/go
$ go get golang.org/x/tools # this fails because tools is not a package, that makes sense.
$ rm -fr src/golang.org
$ go get -d golang.org/x/tools # Why does this fail the same way as go get without -d?
$ go get -d golang.org/x/tools # Running this a second time in a row succeeds
$ rm -fr src/golang.org
$ go get -d -u golang.org/x/tools # Why does this fail like go get without the -d?
$ go get -d -u golang.org/x/tools # Running this a second time in a row fails the same way, why?
Does all of this make sense?

Yep, it makes sense. The fix is probably quite subtle. We might get it fixed for 1.5; let's see.

I found a way around this that is even more subtle than I thought after experimentation with our packages in Gentoo. If you add "/..." to the end of a repository name, things work as expected, e.g.
$ go get -d -t -u -v golang.org/x/tools/...
Doing this makes "go get" not complain about non-buildable sources at the top level.
So is this just a documentation issue? I didn't see anything about it in "go help" anywhere.

The /... means that it will match the packages inside that repo, so it makes sense that it works.
I don't think it's just a documentation issue. I think there's a subtle difference in how -d is treated depending on whether -u is specified.

They should both fail.
Even with -d, the command needs to read
the package sources to find out what the dependencies are,
since -d also fetches dependencies recursively.
So errors like not having any source files still surface.
The bug is that get -d (without -u) succeeds.
Will fix.


make fill defaultdict an implementation detail

Towards #7159. For v2 we added more complex handling for fill to enable filling with different values based on the type. Internally this is handled by a defaultdict:
https://github.com/pytorch/vision/blob/d805aeaee7651ffb22a98647683605ae5f5c6c1a/torchvision/prototype/transforms/_utils.py#L68
However, there is no need to leak that into a public attribute:
https://github.com/pytorch/vision/blob/d805aeaee7651ffb22a98647683605ae5f5c6c1a/torchvision/prototype/transforms/_geometry.py#L280
This PR simply leaves parameter the user passed in the self.fill attribute and moves the defaultdict to self._fill
cc @vfdev-5 @bjuncek

In the transforms v1 tests we have
https://github.com/pytorch/vision/blob/d805aeaee7651ffb22a98647683605ae5f5c6c1a/test/test_transforms.py#L1871-L1872
That will still not be supported by this change. I don't really understand the whole fill=0 vs. fill=None thing. @vfdev can you chime in here?

I don't really understand the whole fill=0 vs. fill=None thing.

This story is certainly a tradeoff between what was supported at that moment supported values (by Pillow, pytorch) and jit, consistency etc. I do not quite remember but the story probably is the following.
For RandomRotation fill arg, it seems like the story was like that:

Philip introduced fill=0 to the transform here: https://github.com/pytorch/vision/pull/1280/files (there was only Pillow backend at that moment)
Then Philip changed fill=None to support older PIllow versions
When tensor backend was introduced, fill was None as tensors could not support it
Then there was a PR (with a bug) which added fill color support for tensor backend: https://github.com/pytorch/vision/pull/2904
When the bug was discovered we changed default value to fill=0 but to keep previous behaviour we added if fill is None: fill = 0 similarly to  PIL, https://github.com/pytorch/vision/pull/3303

Today there are still few issues and inconcistencies for fill arg:

https://github.com/pytorch/vision/issues/6517
https://github.com/pytorch/vision/issues/6623

Also check this comment: https://github.com/pytorch/vision/issues/6623#issuecomment-1253900210


[docs] ccl setting suggestions doc in chinese

I have read the CLA Document and I hereby sign the CLA

I have read the CLA Document and I hereby sign the CLA


File Format doesn't make sense for works

The file format field is shown for works, but since they can be multiple files, this makes more sense at the fileset level.

@olendorf  Can you attach a screen shot? I'm not seeing the file format field locally or in production. Thanks!

The field is in the search results view.


Can not install latest version 0.3.1

Hello ! @jmoore987
I can not download the 0.3.1 version.
Here my shell output
# pip install sharp_aquos_rc==0.3.1
Collecting sharp_aquos_rc==0.3.1
  Could not find a version that satisfies the requirement sharp_aquos_rc==0.3.1 (from versions: 0.2)
No matching distribution found for sharp_aquos_rc==0.3.1

There is only the 0.2.0 version available. But I see the 0.3.1 on pypi website.
Maybe you  forget something (upload or anything else ?)
Thanks for your help !

It could be also a pypi issue :/

Can you try pip uninstall sharp_aquos_rc ; pip --no-cache search sharp_aquos_rc?
Jeffs-MacBook-Pro-2:zr-hive-udf jmoore$ pip --no-cache search sharp_aquos_rc
sharp_aquos_rc (0.3.1)  - Control Sharp Aquos SmartTVs through the IP interface.
Jeffs-MacBook-Pro-2:zr-hive-udf jmoore$

and also
pip --version

Sorry, this was my bad.  Ignore my previous comment.  I am a noob at pypi and missed a (what appears to be crucial) step.
From a virgin AWS instance, I am now able to install:
[user@ip-xxx-xxx-xxx-xxx ~]$ sudo pip --no-cache install sharp_aquos_rc==0.3.1
You are using pip version 6.1.1, however version 9.0.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
Collecting sharp-aquos-rc==0.3.1
  Downloading sharp_aquos_rc-0.3.1.tar.gz
Installing collected packages: sharp-aquos-rc
  Running setup.py install for sharp-aquos-rc
Successfully installed sharp-aquos-rc-0.3.1
[user@ip-xxx-xxx-xxx-xxx ~]$

Feel free to re-open if you still can't install, but this should do it.


getting  zsh: number expected while running setupMetamask

➜  synpress git:(master) ✗ synpress run setupMetamask('secret phase', 'localhost', 'password')
zsh: number expected

@divyag-RC I can't understand what the issue is, sorry. You have to provide more details.
Also, this is not how you run synpress. Please refer to the README for more details:
https://github.com/Synthetixio/synpress#readme

Please refer the screenshot , I am getting this error , what am i doing wrong

?

@divyag-RC Error is self-explanatory. You're missing SECRET_WORDS or PRIVATE_KEY variable.
Again, please follow the readme as it's explained there:
https://github.com/Synthetixio/synpress#-important


terraform-ls: 0.18.2 -> 0.19.0

Motivation for this change
Bump terraform-ls to 0.19.0
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129657 run on x86_64-linux 1

2 packages built:

terraform-ls
vscode-extensions.hashicorp.terraform


[fix][doc] ConnectorDocGenerator support Java 9+

Java 9 changes ThreadContextClassLoader and SystemClassLoader to AppClassLoader from URLClassLoader.
We should use java.class.path instead to get the related URLs.
Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

Merging...


Can I use blockchain.info wallet??

Can I use address on blockchain.info for this payment gateway?

Yes, place your blockchain.info wallet address as your "External Wallet Address" in https://gourl.io/editrecord/coin_boxes/0


about page

Please Provide The following Details About your PR
Type x Inside the checkbox to tick it
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have checked my code and corrected any misspellings

this is about section

Hi, we follow a css pattern, you need
change css file name, "about.css" to "about.styles.css"
so, you don't needed writting full html, just use django to extends base.html
like: "select_choices.html"...
Please, fix those things  to be approved!
@tejus0

Hi, Pedro! I updated the templates and everything should be good to go. The styling is affecting the other pages, so I commented out the link tag until we can figure that out, but the page works!

Let me know if everything looks good please!

Hi, I reviewed this P.R it's okay! Thanks for contributing!

@kailashchoudhary11


hotfix for incorrect only- logic

This hacks around https://github.com/rust-lang/miri/issues/2206. We don't currently use only-32bit or so, which is why this works.

@bors r+

:pushpin: Commit 66d3ee157ba5192409753e3f4a488f9ab2063e4a has been approved by RalfJung

:hourglass: Testing commit 66d3ee157ba5192409753e3f4a488f9ab2063e4a with merge 46af1f1a6c55db673f68f55ebc857a652c25cb41...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit 89edc355e8229ef8c8083e7974971999386c5ce4 has been approved by RalfJung

:hourglass: Testing commit 89edc355e8229ef8c8083e7974971999386c5ce4 with merge d98bd9838554f3d33512db6fae6fa67cede1afaf...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing d98bd9838554f3d33512db6fae6fa67cede1afaf to master...


What does the "fromAmountOffset" stand for?

What does the "fromAmountOffset" stand for? When I look at the augustusFromAmountOffsetFromCalldata from ../src/augustus, I saw the values. But what does all that mean? and why there are values just for "swapOnUniswap", "multiSwap" and others. I mean don't "simpleSwap" need that?
Thanks.

It is the offset of the fromAmount parameter in the calldata to the AugustusSwapper method.  It is used in ParaSwapLiquiditySwapAdapter only when you want to swap the entire aToken balance (otherwise set to 0).  Since you don't know the balance in advance (it is constantly earning interest) this value needs to be modified by the smart contract within the transaction, and that's why it needs to know the offset, so that the data can be inserted at the right location, before performing the swap.  The simpleSwap method does not support this use case, since it hardcodes the parameters to external contract calls, so that is why the offset for that is not included, and also why the simpleSwap method is excluded in all the swapAll test scripts when using ParaSwap SDK (but if not doing swap all balance, it is fine to use simpleSwap).

Thanks for replying,
I got it properly. so to do a swap, I need to have aToken which is swapFrom an asset in liquidity pool to use Paraswap Adapter. I just want to swap with flashloan. When I saw this contract in Aave adapter folder in github repo I suppose that this contract receives the flashloan then swaps the amount with paraswap and then deposits the srcAmount. I understand it's not like that now. So is there a way to do that? I think I can do that with my contract using BaseParaSwapAdapter. but I just want to ask can I use ParaswapLiquiditySwap contract to just swap?

I'm not sure exactly what you're trying to do, you might find it better to write your own smart contract that fits whatever use case you have in mind (you need to pay back the flashloan somehow).  This is specifically for swapping aTokens for other aTokens, and the flashloan lets you swap when you don't have enough collateral, paying off the loan using the old collateral.


[ci] run test-linux-stable parallel on 3 ci nodes

Nextest has a nice ability to partition or shard tests into buckets
Gitlab can run one job in parallel on several runners
Combining this two approaches and applying them to the test-linux-stable job allows to save time.
It is also required to remove continuous-integration/gitlab-test-linux-stable from Required jobs and add

continuous-integration/gitlab-test-linux-stable 1/3
continuous-integration/gitlab-test-linux-stable 2/3
continuous-integration/gitlab-test-linux-stable 3/3

Closes https://github.com/paritytech/ci_cd/issues/207

bot rebase

@nazar-pc thank you for your suggestion. It'll look nicer but it might be not obvious where details could be found. So now each job has a details link which leads to logs for this particular job. With a cumulative check the only thing which I can think of is to put a link to the whole pipeline in details. But it might be not clear why this check has failed.


Nuget will not include .deployment file during pack command

I have a nuspec specified with the following file and during the pack command, fails to include the file.
 .
I am able to manually add the file using the GUI.

This is by design, since we ignore all files that start with a dot. Thanks!


mopidy-spotify: adopt; modernize; 4.1.1-unstable-2024-02-27 -> 5.0.0a2

Description of changes
Upstream has been using the v5 alpha as the default version to install for a while now, so I think it's time we do here as well. See the changelog of v5.0.0a1 for a better list of all the changes here, but for our purposes this should only be a breakage in dependencies rather than anything user facing
The biggest dependency change is the addition of spotifyaudiosrc from gst-plugins-rs. This should already be covered in mopidy itself here, so I don't imagine we should need to wrap it here as well
Testing would be appreciated, but in any case I'll be trying this on my own machine in a few days
Diff: https://github.com/mopidy/mopidy-spotify/compare/v4.1.1...v5.0.0a2
Changelog: https://github.com/mopidy/mopidy-spotify/releases/tag/v5.0.0a2
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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

Just finished testing this locally. I came across https://github.com/mopidy/mopidy-spotify/issues/388, but this also occurred on the current 4.1.1-unstable release in nixos-unstable so 🤷🏻
Everything else seems to work as intended with the MPD frontend (including the much faster playlist refresh!), so I'd say this is still good to go

Awesome, then let's merge. Btw. I'm maintaining mopidy itself in nixpkgs, feel free to request a review from me for any mopidy extension even when I'm not listed as maintainer.


[Operator] Add conv3d, max_pool3d, avg_pool3d

Hi @hjjq, thanks for the quick PR. I prefer to making a general version convolution operator that support arbitrary number of spatial dimensions n (n >= 1) and subclass them to get the 1d, 2d, and 3d versions of tasks. This would avoid most of the repeatition.
I will let you to decide:

merge this PR and later refactor existing 2d and 3d convs in above way.
or directly implement the general version.

Thanks Yaoyao, I will merge and refactor later.


Fix error when running next start without sources

What is the purpose of this pull request? (put an "X" next to item)
[  ] Documentation update
[X] Bug fix
[  ] New feature
[  ] Other, please explain:
What changes did you make? (Give an overview)
The names of the commits as well as the associated issues speak for themselves. The main change is that if we could not find the folder with the pages, then we do not use the loader (we still attach the config). The essence of the problem was that although the loaders are not used by next start, the code above is still executed, since the configuration itself is generated each time anew.
Which issue (if any) does this pull request address?
#892, #853

The second issue is solved by itself, since the built-in possible paths are taken out in an array and then iterated. If the value at index N is suitable, then N + 1 will not be checked

@StLyn4  I have moved all the code from the branch you made from the TypeScript compiler to the canary branch. I think we can move from experimental to canary 😊
Now there are some conflicts. Feel free to fix them and we'll move this PR directly to the canary branch.
Thank you very much!

@aralroca Done👌
By the way, can you please add me as a contributor? 😄

@StLyn4 of course!!! Thank you so much for all your work!
@all-contributors please add @StLyn4 for code

by the way @StLyn4 , I have this error running yarn example:

have you encountered the same error before? If not, I'll investigate to see what it could be... I have tried with node 16 and node 18, but with both I get this error. Thanks

@aralroca Ran yarn example with node 14.20, node 16.19 and node 18.13. Windows 11. Everything works. It is worth noting that Next.JS reports an error about _middleware.ts, because in version 12.2.0 there were breaking changes regarding middlewares. Also, loading translations does not work ("Critical dependency: the request of a dependency is an expression", blah blah blah)

@StLyn4 I'm trying to run properly all the examples but I have some troubles, can you help me to detect what is happening? Thank you! For example, about this example https://codesandbox.io/s/empty-morning-wqs233?file=/package.json do you now about this Internal Server Error? Thanks

Wow! Ok! Thank you @StLyn4 !


Fix missing deps for sourcemigrator

Fixes https://github.com/pulumi/ci-mgmt/issues/609
Here's what happened. As part of rolling out wheels to providers, we've coded automatic upgrades as part of the source-migrator steps in TypeScript, and these steps assume additional build dependencies:

python
pulumictl

When testing the workflows on gcp,aws,tls,random, the dependencies were added to some but not all of the workflows. That's he omission currently corrected by this PR.
When wheel rollout is complete we remove both the migrations and the dependencies. Separately we might also consider removing update-workflows-ecosystem-providers since the team split is no more and we're now operating under one risk profile/tradeoffs not two.

Thinking out loud, the root cause here is duplication and forgetting to update the copies. Let me quickly look if we can factor out the shared yaml into a callable action using appropriate GHA facilities.

I'm going to test every changed job here before merging. Alas testing finds issues in passing boolean arguments.

Successful test for the bridged provider: https://github.com/pulumi/pulumi-ec/pull/145

Native provider test: https://github.com/pulumi/ci-mgmt/actions/runs/6303007751

As part of trying to reduce copy-paste here I noticed a few things.

rollout-native-provider-workflows.yml has not been used in 8 months, deleting it
update-native-provider-workflows.yml is used intend, including nightly, and it calls a loop over rollout-single-native-provider-workflow.yml - this is now using the shared logic with bridged providers after the change
there are a few subtle differences in native providers

they do not want to automerge the workflows (can we allow them to?)
instead of replacing all workflow files they do a selective replace, that is they're not fully managed

There's perhaps customizations in the original repos drifted from ci-mgmt. This is all kept as-is for now.


Active new dynamic tab

Hi all,
Is there anyway to active a new tab when it's created?
I am using one static tab and a list of dynamic tab, when I push a new tab to the list, it should be active, I tried to used [isActive] but is went to an error with activeClosestTab. I guess this function run before the tab is append to the tab list so the error was raised.
Thanks.

Hi! Could you please setup a plunkr demonstrating what you're trying to do so I can investigate further?
Thanks :)

I've investigated myself a bit further, and have updated the tab activation logic.
Download v0.4.2, and try the following:
<sui-tabset>

            {{ tab.header }}

         {{ tab.content }}

</sui-tabset>

If you use [(isActive)] and set the new tab's active property (or any boolean property linked to that tab) to true the tab will auto activate when added.
Let me know if you have any further issues or can't get this working!

Thanks you.
It worked like a charm.


i18n Spanish translation v2

Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[x] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[x] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[x] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Label: To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description

Updated the Spanish translation to include new strings added on the English language and fix some minor Spanish typos and Spanish words out of context

Changed

Provided Spanish strings for the ones in the English language
changed some minor Spanish typos and Spanish words out of context

Closing due to conflicts, feel free to reopen again!


Remove check source when empty before publishing check result

Fixes #1836
Co-authored-by: Justin Kolberg<EMAIL_ADDRESS>Co-authored-by: Aaron F. Stanton<EMAIL_ADDRESS>Related Issue
#1836

I bundled in the removal of has_rdoc which was causing a deprecation notice in mutator output causing a test to fail.


Heated Body

The Heated body feature, atleast for the Azer, targets the Azer instead of the attacker.

Same thing with salamander ( i cancelled salamander's fire immunity thats why it takes dmg)


Can't run it

$ npx ts-add-js-extension --help
node:internal/modules/cjs/loader:998
  throw err;
  ^

Error: Cannot find module 'typescript'
Require stack:
- /home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/read-write.js
- /home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/index.js
- /home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/bin.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
    at Module._load (node:internal/modules/cjs/loader:841:27)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/read-write.js:44:36)
    at Module._compile (node:internal/modules/cjs/loader:1159:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1061:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/read-write.js',
    '/home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/index.js',
    '/home/spinda/.npm/_npx/9481ecb1b35cd9d7/node_modules/ts-add-js-extension/build/cjs/bin.js'
  ]
}

Node.js v18.12.1

Oh crap @spinda, thanks for pointing it out, I forgot to move typescript into dependencies, thanks for pointing it out! Really appreciate it

@spinda, I published the package again with the fix for this problem, u can try again

@spinda, have u tried the latest version?

Hello, I don't know if this is related to this problem, but I got the following error when trying to use it:
node:internal/modules/cjs/loader:1074
    throw new ERR_REQUIRE_ESM(filename, true);
    ^

Error [ERR_REQUIRE_ESM]: require() of ES Module /Users/darkawower/.npm-global/lib/node_modules/ts-add-js-extension/build/cjs/a.mjs not supported.
Instead change the require of /Users/darkawower/.npm-global/lib/node_modules/ts-add-js-extension/build/cjs/a.mjs to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (/Users/darkawower/.npm-global/lib/node_modules/ts-add-js-extension/build/cjs/bin.js:8:15) {
  code: 'ERR_REQUIRE_ESM'

I'm trying to use the package from the CLI

@Artawower Oh my God, I accidentally committed temp file and published it. I published the latest version, it fixed your problem

Thanks for the quick fix, everything works without error messages. Can you please advise me how I can find out why my imports in the files did not change after the script finished?
I am trying to add extensions to a file for the typescript module-generated code

@Artawower any updates on ur issue?

Sorry for the delayed reply.
Branch for test: https://github.com/Artawower/second-brain-publisher/tree/test/codegen
Command: convert:api2
Expected behavior:
All imports inside src/generated directory have relative paths and *.js extension
Real behavior:
Nothing has changed

@Artawower
I want to clarify that the matter I'm raising is not an issue per se; rather, it's about aligning the purpose of ts-add-js-extension. I am not fully aware of how other tools operate, but in ur particular case, u already have a similar tool called fix-esm-import-path. That tool is capable of modifying the import/export paths of TypeScript (src) code
As a matter of principle, I adhere to the practice of modifying the transpiled code exclusively. Therefore, I focus on adding the JavaScript file extension to the import/export paths in the dist files rather than the src files. This decision stems from the fact that I primarily import/export TypeScript files within the src directory, not JavaScript files, hence I do not modify the import/export path to include build artifacts, when none of it exist
Consequently, for my import/export statements within src, I have two options:

Omitting the file extension
Appending the TypeScript file extension

@Artawower  how are things going? Did I answer your question?

Yes, thanks for the reply, everything is fine! As you noticed above, I am using a different tool and in this post I just wanted to highlight the problem I saw.
I get your point, if your tool was intended that way that's ok
Personally I don't see much difference between dist directory and src directory, ultimately the only difference is the path... In that case it's just a matter of tool flexibility.


The streak should be positive or zero. [Backend Issue]

Streaks Algorithm is not working correctly. it goes in negative as well.
What is should be the streak algorithm?
Number of days user consistently writing journal. if user missed a day, streak reset to zero.

I wanna do this

How to reproduce?


Create Right view of a binary tree.cpp

You are trying to commit in the base folder, that is not encouraged. Please commit at appropriate path, for example, C++/Algorithms/Tree Algorithms/right_view_of_binary_tree.cpp