Upgrade to Docusaurus 2

Summary
Fixes #2261. This should be merged after #2267 (how I wish there were stacked diffs on GitHub)
Migrate the website to Docusaurus 2 which provides the following benefits specific to Draft.js:

Consistency with the other FB Docusaurus websites
Easy way to import Draft.js (bundle via webpack, no more ugly client-side script tags)
Nicer CSS framework
Dark mode (disabled for now until I sort out the dark mode styling for the editor)

Changes made:

I also changed the theme color of Draft.js to be lighter brown so that the contrast is better in general (much better on dark mode). Let me know if this is not ok.

Test Plan

Try it out here - https://build-swart-eight.now.sh

This is looking good - I'd prefer to leave the theme color the same as it affects branding (e.g. Twitter account, sticker designs etc.) and would require broader coordination. The project is indeed screaming for better branding and would love to plan something in H1. Let's keep the impact of dark mode on theme colors in a separate conversation for now.

I think it's okay to leave the current theme color for dark mode for the time being, but I like that you're trying to refresh the look of the website 😃 let's chat about the dark theme for the editor itself on a separate issue.

The dark mode for the editor needs more work - the editor text is still the same shade of gray and can hardly be seen, hence I disabled it. Unless you think it's not an issue at all then I shall enable it :D


Bugfix, add query parameters to list function

http://help.getharvest.com/api/invoices-api/invoices/show-invoices/
Add query parameters to list function

please, merge the fix someone


[hotfix][AIC-py] accept openai response: either dict or pydantic model

[hotfix][AIC-py] accept openai response: either dict or pydantic model

Approving to unblock -- did openai completion api change or did we have a regression here?

It seems we tried to update with the OpenAI API following this: https://github.com/openai/openai-python/discussions/742

Response objects are now pydantic models

but the official openAI docs show it as a dict, not a pydantic model. I confirmed from running the cookbook it's a dict. So I'm not sure exactly what's going on, i.e. why that discussion says its a Pydantic model. @Ankush-lastmile any idea?

official openAI docs show it as a dict
I'm not sure if that has been updated but the api uses pydantic.

The issue here isn't the model parser, but the wrapper
https://github.com/lastmile-ai/aiconfig/blob/main/python/src/aiconfig/ChatCompletion.py#L83

official openAI docs show it as a dict

I'm not sure if that has been updated but the api uses pydantic.
I think The issue here isn't the model parser, but the wrapper
https://github.com/lastmile-ai/aiconfig/blob/main/python/src/aiconfig/ChatCompletion.py#L83
This should be updated to create a new object when dumping the model rather than converting the existing object. The object gets passed forward since its a stream, but it shouldn't be converted for the user

When I run  response = openai.chat.completions.create(**completion_data) directly, it does indeed return a BaseModel. Do we know why it doesn't when run from openai.py?

Do we know why it doesn't when run from openai.py?

From the wrapper, notice when streaming,  this chunk object is getting converted into a dict with model_dump, then gets passed forward with the yield statement. But the user might still be expecting that BaseModel, in openai.py its expecting that basemodel


How to provide the project base directory for sonar scan as we have multiple backend services in the same repo

name: SonarQube Scan
uses<EMAIL_ADDRESS>env:
SONAR_TOKEN: ${{ secrets.- }}
SONAR_HOST_URL: ${{ secrets.- }}
with:
sonarProjectKey: -
sonarProjectName: -
sonarHostname: http://******.com/

I have integrated the sonar scan in our build pipeline. But the repo we are using have multiple backend services in the same repo. when i trigger the sonar scan it cannot able to find the .sln file as it will be available in the nested repo of the backend service.
how can i provide the project base directory path to run the scan
Github Action input parameters
INPUT_SONARPROJECTKEY: -*
INPUT_SONARPROJECTNAME: -*
INPUT_SONARORGANIZATION:
INPUT_DOTNETPREBUILDCMD:
INPUT_DOTNETBUILDARGUMENTS:
INPUT_DOTNETTESTARGUMENTS:
INPUT_DOTNETDISABLETESTS:
INPUT_SONARBEGINARGUMENTS:
INPUT_SONARHOSTNAME: ***
i want to provide the specific path of the backend service to run the scan.
which is available in sonar scan github action
projectBaseDir: App///***

The scan works on single .sln or .csproj file. The scan invokes the dotnet SDK dotnet build command and appends whatever you specify in  dotnetBuildArguments  parameter.
If you have sub-folder with a single .sln or .csproj file you can specify the folder like in this example:
https://github.com/highbyte/sonarscan-dotnet?tab=readme-ov-file#build-subfolder-src-and-include-code-coverage
Or if you want to specify a specific .sln (or .csproj) file in a sub-folder you use it like this: dotnetBuildArguments: ./myfolder/mysolution.sln

thank you. you can close it now


Expose service IP and port as variables in service providers

Summary
This replaces the _serverNameSpace with _serverIP and _serverPort. _serverNameSpace was used back in Orion when it was using named pipes. It is now using TCP and although LeapC still uses a variable called server_namespace, it can be used to connect to a service listening on a different IP/port by passing a JSON payload containing tracking_server_ip and tracking_server_port:
Contributor Tasks

[ ] Create or edit test cases here
[x] Add a CHANGELOG entry for this change.
[x] Ensure documentation requirements are met e.g., public API is commented.
[x] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.
[x] Add any relevant labels such as breaking to this MR.

Reviewer Tasks
Add any instructions or tasks for the reviewer such as specific test considerations before this can be merged.
Use emojis in review threads to communicate intent and help contributors.

[ ] Run all tests associated with the ticket.
[x] Code reviewed.
[x] Non-code assets e.g. Unity assets/scenes reviewed.
[x] Documentation has been reviewed.
[ ] Approve with a comment of any additional tests run or any observations.

Closes JIRA Issue
Closes UNITY-1217

I've tested this with the localhost server and a server on a NUC on the same network (in-Editor and as a built app). It worked successfully.

I think it would be valuable to programmatically set the IP and Port a LeapServiceProvider connects to. Only being able to set this at development time means a developer is always necessary to make that change. If it was doable programmatically, it can be changed in-app or via config with limited technical resources.

I strongly hope this fix will be merged.


New Intersubject Correlation Modules (and related changes)

Hello all,
This PR contains a new intersubject correlation module and some BIDS processing extensions, as well as some minor fixes.
Overview

aamod_intersubject_correlation.m/xml

New module for doing intersubject correlation (voxelwise correlation of timeseries between subject pairs) that includes a number of options (global signal subtraction, save individual maps, convert r-to-Z, etc). It will do on-the-fly implicit masking as well as taking a mask from an input stream or filename.

aamod_render.m/xml

This a generic rendering module that inputs a (renameable) "brainmaps" input stream and will use either the spm, washu, or (new) NeuroDot rendering code. Options are provided for each render. A class interface for the NeuroDot toolbox is included (neurodotClass.m).

aamod_brainmaskcombine.m/xml

Modified to make the input stream renameable.

aas_getstreams.m

Modified to fix an intermittent crash when including modules in a tasklist that have no output streams (see Issue #383)

aas_processBIDS.m

Fixed a comment typo, also made cosmetic changes throughout the code.

BIDS_subjectfilter.m

This is a new standalone tool that will apply a "filter" (e.g., 'sex=F' or 'age<18') to participants.tsv in a BIDS directory and return a cell array of subject ID that satisfy the filter. The cell array can then be passed to aas_processBIDS to only include those subjects in the analysis.

aas_BIDS_boldfilter.m

Similar to BIDS_subjectfilter, but applies a filter to epi json headers to remove epi that fail the filter. It is used after aas_processBIDS and modifies the aap struct. A fair question is why add files in aas_processBIDS and then remove them rather than just not adding the files in the first place; the honest answer is I was never able to get that to work because of the two-pass structure of aas_processBIDS. By the time the json header information is available in the second pass, the file has already been added to various aap structure fields by the first pass. It was simpler to set this up as a separate utility rather than making extensive modifications to aas_processBIDS.

Nice additions! Especially the NeuroDOT.
I wonder whether you want to use the (standard) BIDS-MATLAB library for filtering. You can see an example implementation at https://github.com/reprostat/reproanalysis/blob/master/engine/processBIDS.m.

I agree this is the way to go moving forward; the current subtext is we are submitting a paper that needs this functionality so I'm in a bit of a time crunch to get it into the repo ASAP.

You do not need a PR just for sharing code for a paper. You can cite your repo or a particular branch or even a commit.


fix(scully): render doctype

closes #74
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/scullyio/scully/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Other... Please describe:

What is the current behavior?

<!doctype html> is removed from generated indexhtml.
Issue Number: #74
What is the new behavior?
<!doctype html> remains.
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@aaronfrost I would value your thoughts on this one.


Fix bad transition to museum page when null id

Fixed this one too since I've run into it a few times and its horribly unfriendly to the user

:+1:


Minor cleanup of the AssetLib's asset dialog

Remove an unnecessary Panel node and made the description's minimal size be set directly in its container.

Thanks!


Bindgen doesn't work on with MSVC

I tried to investigate this, but failed. It throws lots of errors. See the attached log: bindgen.zip
This log gives me an impression that it just fails to parse everything.
My Clang version is:
clang version 3.9.0 (branches/release_39)
Target: x86_64-pc-windows-msvc
Thread model: posix
InstalledDir: c:\Program Files\LLVM\bin

@emilio could you have a look?

It's choking to parse some LLVM3.9-specific type that isn't handled. I'm looking into it, shouldn't be hard to fix.
Seems like a good moment to upgrade to LLVM 3.9 by default.

I've been using llvm 3.9 for quite a while, so I suppose that may not be relevant.

The rewrite chokes on errors and doesn't just ignore it, so yeah, it is relevant.

Problems found:

@upsuper was using llvm 3.9 but compiling with llvm_stable, which was the cause for this concrete bug. That's going away soon since I plan to require llvm 3.9 soon.
We found a weird const size_t in nsCSSValueArray that made bindings incorrect. Presumably is parsed as a new type. I'll try to reduce it.
Making _Atomic_Base opaque in MSVC wasn't working.
Found a libclang crash while getting the mangling of a cursor, so it's probably MSVC-specific libclang bug, though difficult to diagnose.

The mangling crash looks very much a clang bug. It always crashes at static const nsRunnableMethodTraits<R(C::*)(As...), Owning, Cancelable>::can_cancel in nsThreadUtils.h. However, if I comment out the line for that, it goes well even for the later nsRunnableMethodTraits<R(C::*)(As...) const, Owning, Cancelable>::can_cancel.
I guess we may want to switch off mangling for now, and probably try to file a bug to clang.

It crashes with this minimal example:
template<class M> struct A;
template<class C> struct A<void(C::*)()> { static int v; };

Wait... but how can a static variable in a template class has a mangling name?! It isn't linkable at all, so it actually makes no sense to try to generate mangling name for it.

Hmmm, bindgen fails to work again on Windows. It panicked for nonexisting item:
thread 'main' panicked at 'Not an item: ItemId(57262)', src\ir\context.rs:402
stack backtrace:
   0:     0x7ff7502c2b6e - _<std..rand..ThreadRng as rand..Rng>::next_u64::h75a21f4cede609ad
   1:     0x7ff7502c0fe3 - std::rt::lang_start::h53bf99b0829cc03c
   2:     0x7ff7502c1a4d - std::panicking::rust_panic_with_hook::h4cbd7ca63ce1aee9
   3:     0x7ff7502c1896 - std::panicking::begin_panic_fmt::hd0daa02942245d81
   4:     0x7ff7502c17f4 - std::panicking::begin_panic_fmt::hd0daa02942245d81
   5:     0x7ff74fdefe0d - bindgen::ir::context::BindgenContext::resolve_item
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\context.rs:8
   6:     0x7ff74fdf8022 - bindgen::ir::item::Item::real_canonical_name
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:361
   7:     0x7ff74fdfd323 - bindgen::ir::item::{{impl}}::canonical_name
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:706
   8:     0x7ff74fdf60d6 - bindgen::ir::item::{{impl}}::canonical_name
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:69
   9:     0x7ff74fdf79bf - bindgen::ir::item::Item::real_canonical_name
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:292
  10:     0x7ff74fdfd323 - bindgen::ir::item::{{impl}}::canonical_name
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:706
  11:     0x7ff74fe3e2c5 - bindgen::codegen::codegen::{{closure}}
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\target\debug\build\bindgen-22479e177d6249bd\out\codegen.rs:2615
  12:     0x7ff74fdef5f7 - bindgen::ir::context::BindgenContext::gen<closure,collections::vec::Vec<syntex_syntax::ptr::P<syntex_syntax::ast::Item>>>
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\context.rs:357
  13:     0x7ff74fe28a1d - bindgen::codegen::codegen
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\target\debug\build\bindgen-22479e177d6249bd\out\codegen.rs:2601
  14:     0x7ff74fe3714a - bindgen::Bindings::generate
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\lib.rs:249
  15:     0x7ff74fd45bc2 - bindgen::main
                        at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\bin\bindgen.rs:242
  16:     0x7ff7502c4d31 - _rust_maybe_catch_panic
  17:     0x7ff7502c088a - std::rt::lang_start::h53bf99b0829cc03c
  18:     0x7ff74fd465a9 - main
  19:     0x7ff7502ceba0 - __scrt_common_main_seh
                        at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253
  20:     0x7fffff088363 - BaseThreadInitThunk

This one looks like a bindgen bug, could you post a RUST_LOG=bindgen
output, and if you can look at what type was "self" in the
real_canonical_name call that fails, that'd be helpful too.
On Oct 19, 2016 7:50 AM, "Xidorn Quan"<EMAIL_ADDRESS>wrote:

Hmmm, bindgen fails to work again on Windows. It panicked for nonexisting
item:
thread 'main' panicked at 'Not an item: ItemId(57262)', src\ir\context.rs:402
stack backtrace:
0:     0x7ff7502c2b6e - _<std..rand..ThreadRng as rand..Rng>::next_u64::h75a21f4cede609ad
1:     0x7ff7502c0fe3 - std::rt::lang_start::h53bf99b0829cc03c
2:     0x7ff7502c1a4d - std::panicking::rust_panic_with_hook::h4cbd7ca63ce1aee9
3:     0x7ff7502c1896 - std::panicking::begin_panic_fmt::hd0daa02942245d81
4:     0x7ff7502c17f4 - std::panicking::begin_panic_fmt::hd0daa02942245d81
5:     0x7ff74fdefe0d - bindgen::ir::context::BindgenContext::resolve_item
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\context.rs:8
6:     0x7ff74fdf8022 - bindgen::ir::item::Item::real_canonical_name
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:361
7:     0x7ff74fdfd323 - bindgen::ir::item::{{impl}}::canonical_name
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:706
8:     0x7ff74fdf60d6 - bindgen::ir::item::{{impl}}::canonical_name
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:69
9:     0x7ff74fdf79bf - bindgen::ir::item::Item::real_canonical_name
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:292
10:     0x7ff74fdfd323 - bindgen::ir::item::{{impl}}::canonical_name
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\item.rs:706
11:     0x7ff74fe3e2c5 - bindgen::codegen::codegen::{{closure}}
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\target\debug\build\bindgen-22479e177d6249bd\out\codegen.rs:2615
12:     0x7ff74fdef5f7 - bindgen::ir::context::BindgenContext::gen<closure,collections::vec::Vec<syntex_syntax::ptr::P<syntex_syntax::ast::Item>>>
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\ir\context.rs:357
13:     0x7ff74fe28a1d - bindgen::codegen::codegen
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\target\debug\build\bindgen-22479e177d6249bd\out\codegen.rs:2601
14:     0x7ff74fe3714a - bindgen::Bindings::generate
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\lib.rs:249
15:     0x7ff74fd45bc2 - bindgen::main
at c:\mozilla-source\stylo\servo\components\style\binding_tools\rust-bindgen\src\bin\bindgen.rs:242
16:     0x7ff7502c4d31 - _rust_maybe_catch_panic
17:     0x7ff7502c088a - std::rt::lang_start::h53bf99b0829cc03c
18:     0x7ff74fd465a9 - main
19:     0x7ff7502ceba0 - __scrt_common_main_seh
at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:253
20:     0x7fffff088363 - BaseThreadInitThunk
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/servo/rust-bindgen/issues/67#issuecomment-254716810,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQwuuXy3xeTVPChWEayPt6zReXCMcyRks5q1a-ogaJpZM4KIbgp
.

I'm somewhat surprised that the latest changes have introduced MSVC-only regressions, but I guess... #85 is the most likely regressor? Either that, or MSVC headers have changed and now have more dark magic.

I'm not aware of any update to MSVC's headers, so I suppose that is not the reason.

The log: log.zip

This is the file in question: xtr1common.zip
Looks like the unrecognized thing is the alias template.

The file in question itself doesn't actually cause the bindgen to panic. Then I have no idea.

So, after reading the log I think I know what's going on, and I don't like that at all.
So turns out clang can generate duplicated usrs, which they promise not doing, so we choke. usrs are platform-dependent I think, so this might be a MSVC-only issue. In any case this sort-of uncovers a flakyness on bindgen, that should be fixed.
Basically, what I think happens after reading the log is something like:

We parse the generic integral_constant<_Ty, _Val>, and store it in the usr map.
Life goes on...
We arrive at integral_constant<bool>, which is a CXType_Unexposed, with usr: c:@N@std@bool_constant. It's an unexposed type, and we see it has a canonical type, also unexposed, called integral_constant<bool, _Val>. This usr happens to be the same as integral_constant<_Ty, _Val>, so we mark it as found (which isn't too bad), and go on.
Something already uses the id we expected for integral_constant<bool>.

In any case, this is fixable (I think), by storing the type we just found as a resolved type refernce to the new type found. I think this is the proper and elegant solution and shouldn't be hard. Another less elegant solution is adding a fallible canonical name to do the whitelist checking, since it seems we choke at that point.

I think we can close this for now :)


About Concurrency issue in FtpClient

FTP Server OS: Debian
FTP Server Type: Vsftpd
Client Computer OS: Windows
FluentFTP Version: ? 47.1.0
Framework: .NET 6
using FluentFTP;
using System.Collections.Generic;
using System.Threading.Tasks;
FtpClient client = new FtpClient(host, username, password);
await client.ConnectAsync();
var remotePaths = new List { remotePath1, remotePath2 }; // 添加你要下载的所有远程路径
var localPaths = new List { localPath1, localPath2 };    // 添加相应的本地路径
await Parallel.ForEachAsync(remotePaths, async (remotePath, cancellationToken) =>
{
var index = remotePaths.IndexOf(remotePath);
var localPath = localPaths[index];
await client.DownloadFileAsync(localPath, remotePath);
});
Does it can work？

Move the
FtpClient client = new FtpClient(host, username, password);
await client.ConnectAsync();

down into the Parallel.FOrEach, then it should work.

Hello,
I comment on my case to see if it has anything to do with it. I have a class to manage our ftp using AsyncFtpClient and AutoConnect with DownloadBytes (all asynchronous).
In our api, I register this class as Scoped. When simultaneously testing calls to our API, we have received some random errors that the connection to the ftp could not be made or certain files did not exist in the ftp (if they exist).
Does it have something to do with it? Are there any undetected errors? my implementation is not correct?

@angelru

Does it have something to do with it?

Are there any undetected errors?

my implementation is not correct?

Open a new issue and provide full documentation. Do not hijcack this issue.

@FanDjango , Does AsyncFtpClient supports Parallell Programming (i.e Parallel.ForEach) and
Multiple Asynchrnous( i.e Task.WhenAll)? Could you please confirm when you are free.

@FanDjango, I tried parallel Programing (ActionBlock) in .net 6  to upload files (around 2000)  with fluentftp which worked fine.

To all:
Parallel programming FluentFTP ( and FluentFTP.GnuTLS ) (aka multithreading) works -
IF and only if
Each FTP process (or thread) instantiates its own FTP-Client object.
There are limits set by memory of the client machine, of course. Also limits as to the amount of TCP connections you can initiate on your client machine, as well as performance issues.
Such an FTP Client object can then sequentially operate against a server, independantly of other FTP-Client objects.
Note: - a server, though, might have a configured limit of concurrent connections that it cannot (or will not) exceed.
How to program parallelism
ActionBlock, etc. are just syntactic sugar that help you set up multithreading (there are various other methods).
The important point is that threadstart will "construct" a new FTP client, which then needs to connect, i.e. use a connection of its own.
Conversely, what does not work in FTP is to use an existing connection (i.e. a single client) and then expect this single client to somehow magically do a number of parallel operations. No way that will work.

There is one important note on this though:
Depending on the server type, using "ASYNC" and more than one thread with SslStream can cause session resume problems.
Solution: Use FluentFTP.GnuTls.


DNS Not Resolving

Thanks for this helpful GH action, I'm using this to connect to an AWS RDS DB for integration test automation. It works fine but I have to use the the DB IP address as the host name will not resolve. I know the zero tier desktop client has a setting on whether the DNS configuration is applied.  Maybe the github action has something similar?

bump?


Linting error due to use of "arguments"

When trying to run the tests with a fresh install of "uppercamelcase" & its dependencies, the tests fail due to a linting error:
uppercamelcase$ npm run test

><EMAIL_ADDRESS>test /tmp/uppercamelcase
> xo && ava

  index.js:5:43
  ✖  5:43  Use the rest parameters instead of arguments.  prefer-rest-params
  ...

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>test: `xo && ava`
npm ERR! Exit status 1

Used versions:

Node v9.4.0
NPM 5.6.0
xo: 0.21.0
ava: 0.25.0

I guess this is due to newer versions of xo using a stricter ruleset. I've created a PR for this.


independent hidden option for file/folder browser

Leaving this mostly for myself as a reminder.
Currently the hidden option applies to both the file & folder browser. I'd like to have the ability to have something like hidden = true for the file browser but hidden = false for the folder browser.
I think turning the hidden option to be able to optionally take a table will be a fairly simple way to accommodate this.
eg. hidden = { file_browser = true, folder_browser = false }.
With this, I'm leaning on changing the default to hidden = { file_browser = false, folder_browser = false }. This will preserve the default behavior but illustrate the capacity to differentiate the hidden option between the browsers.

With this, I'm leaning on changing the default to hidden = { file_browser = false, folder_browser = false }

#210 has pretty much exactly this in broader scope (ie any option). Users will be able to define their own pickers. I just need the time and motivation to finish it 😅


Code generation causes compilation failure for web

On bare template, after running (as per docs):
flutter_rust_bridge_codegen --rust-input native/src/api.rs --dart-output ./lib/bridge_generated.dart --dart-decl-output ./lib/bridge_definitions.dart

I get compilation failure for web. Happens even when using the same version of flutter_rust_bridge_codegen as the template. Might be related to the following lines disappearing from bridge_generated.rs ?:
/// cbindgen:ignore
#[cfg(target_family = "wasm")]
#[path = "bridge_generated.web.rs"]
mod web;
#[cfg(target_family = "wasm")]
pub use web::*;

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.1, on macOS 13.0 22A380 darwin-arm64, locale
    en-NZ)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.3)
[✓] VS Code (version 1.74.3)
[✓] Connected device (2 available)
[✓] HTTP Host Availability

• No issues found!

Full diff: https://github.com/elliotsayes/flutter_rust_bridge_cipher_test/compare/main...codegen-failure-web

Your invocation is missing the --wasm flag, but assuming you came here from the docs it might be worth updating it as well.

True! I'll make a PR to update the docs with this


Running cci org import org1 org1 on circleci throws 'NoneType' object is not subscriptable

Describe the bug
Running cci org import org1 org1 on circleci throws 'NoneType' object is not subscriptable for Scratch Orgs
Edit: The behaviour does also occur on 3.30.
Reproduction steps
I have a windows machine, so I cannot reproduce behaviour.
Context
circleci image: circleci/python:3.7.4-browsers
CumulusCI version: 3.31.0 (/usr/local/bin/cci)
Python version: 3.7.4 (/usr/local/bin/python)

You have the latest version of CumulusCI.

2021-03-20 09:42:48,463 DEBUG Added a stderr logging handler to logger: urllib3
2021-03-20 09:42:48: Getting org info from Salesforce CLI for browsertest-PropertiesAndCalculation
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/cumulusci/cli/cci.py", line 234, in main
    cli(args[1:], standalone_mode=False)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/cumulusci/cli/cci.py", line 173, in new_func
    func(RUNTIME, *args, **kw)
  File "/usr/local/lib/python3.7/site-packages/cumulusci/cli/cci.py", line 1046, in org_import
    scratch_org_config.config["date_created"] = parse_api_datetime(info["created_date"])
  File "/usr/local/lib/python3.7/site-packages/cumulusci/utils/__init__.py", line 41, in parse_api_datetime
    dt = datetime.strptime(value[0:DATETIME_LEN], API_DATE_FORMAT)
TypeError: 'NoneType' object is not subscriptable
> /usr/local/lib/python3.7/site-packages/cumulusci/utils/__init__.py(41)parse_api_datetime()
-> dt = datetime.strptime(value[0:DATETIME_LEN], API_DATE_FORMAT)

CCI org import is a confusing command. It is for importing scratch orgs and only scratch orgs. In a CI context I'd suggest you spin up new scratch orgs. Or you can connect an org (probably persistent, no scratch) as described here:
https://cumulusci.readthedocs.io/en/latest/github_actions.html#connect-a-persistent-org

Thank you.
My bad, I failed to mention I am trying to import Scratch Orgs.
I just cannot fathom why createddate / the command fails since Friday. This isn't a new setup.

@Szandor72 If you run sfdx force:org:display --json -u org1, does that output include createdDate?
How did you create the scratch org?

Thanks for the pointer, David.
The output does not include a createdDate but the org involved is a scratch org.
The scratch org is created in a different circleci step and is re-used in several other steps. We use SFDX auth URLs to authenticate org(s) and prepare some test data. Finally we do a cci org import to run robot tests.
I could confirm this works as expected with DX CLI 7.82 but on 7.92 cci org import fails due to createdDate missing in the json response.

@Szandor72 I just created a scratch org using sfdx 7.92, and verified that sfdx force:org:display --json includes a createdDate. So I suspect that the problem is related to authenticating the org to the CLI using the auth url and that in that case the CLI is not retrieving the date that the org was created and adding it to the org properties. I don't see an entry in the Salesforce CLI release notes specifically mentioning this as something that changed, but it seems very possible that it could have been affected by the ongoing refactoring that that team is working on.
I don't really understand why you are using auth urls in this scenario. Isn't the org already in the CLI's keychain in ~/.sfdx from when it was created?
In the short term we are going to add a better error message here, indicating that only locally created scratch orgs can be imported. We'll also look into what changes would be needed to support importing a scratch org even if its creation date isn't known, and to import non-scratch orgs, but it may take longer to get to those improvements.

Thanks again @davisagli,
we are in agreement: the root cause of the issue lies beyond our reach.
There is certainly some legacy aspect involved in our case - yet you surmise correctly, that we are forced to use authUrl because the current keychain in the build step doesn't know the scratch org (yet).

@Szandor72 We have significantly changed the way importing orgs works in the most recent versions of CCI. Do you know if this is still an issue?

Haven't experienced any issues recently. Thanks for the reminder.


Repeater displaying incorrectly when on a wizard pane

I have a wizard with 3 steps and one or two grids on each step. When I click on a step and the grid on that pane is displayed, the headings are wonky and the static height for the grid is not honored. If I resize the window, the headings appear correctly and the grid resizes to the static height.
Short term solution was to call resize on wizard step change:
$('.repeater').repeater('resize');

I wonder if this has to do with the repeater not being visible when you init it.


tiv: new package at 1.0.0

Please fill out the template.
Read: https://k1ss.org/wiki/kiss/style-guide

Description of package
Small C++ program to display images in a (modern) terminal using RGB ANSI codes and unicode block graphic characters.
Installed manifest of package
(cat /var/db/kiss/installed/<pkg_name>/manifest)

/var/db/kiss/installed/tiv/version
/var/db/kiss/installed/tiv/sources
/var/db/kiss/installed/tiv/manifest
/var/db/kiss/installed/tiv/depends
/var/db/kiss/installed/tiv/checksums
/var/db/kiss/installed/tiv/build
/var/db/kiss/installed/tiv/
/var/db/kiss/installed/
/var/db/kiss/
/var/db/
/var/

New package

[x] Latest upstream version.
[x] I agree to maintain this package.
[x] I agree to notify @dylanaraps if I can no longer maintain this package.

Existing package

[ ] I am the maintainer of this package.

Your uploaded manifest seems to be missing things?

Your uploaded manifest seems to be missing things?

corrected build file (per IRC chat) and updated the manifest.  Thanks again =)


原理是什么

请问原理是什么？ 监听Android通知吗？

看文档

文档在哪里？
On 2016/9/6 18:22, Zhongyi Tong wrote:

看文档
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/geeeeeeeeek/WeChatLuckyMoney/issues/158#issuecomment-244910085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2-LhhAqgTw4cb7VQoMrLhkH-UF-hbFks5qnT7TgaJpZM4J1Z6n.

https://github.com/geeeeeeeeek/WeChatLuckyMoney/blob/dev/README.md 这个是文档


Add these

https://github.com/IBM/sveld
https://github.com/metonym/svelte-typeahead
https://github.com/nodegui/svelte-nodegui
https://github.com/tonyrewin/svelte-boilerplate
https://github.com/crewdevio/Snel
https://github.com/denofn/svelte
https://github.com/tiaanduplessis/svelte-autocomplete-select
https://github.com/sveltejs/svelte-loader
https://github.com/benmccann/vite-svelte & https://github.com/benmccann/vite-plugin-svelte
https://github.com/ticruz38/svelte-sheets

https://github.com/MelihAltintas/svelte-slimscroll

https://github.com/EMH333/esbuild-svelte


api-pagination 4.8.0 on rails 4.2.x with kaminari results in "NameError: uninitialized constant Pagy" exception

We don't use Pagy.  We do explicitly specify kaminari in an initializer:
ApiPagination.configure do |config|
  config.paginator = :kaminari

We've temporarily reverted to 4.7.1 to work around this problem.

This is a duplicate of #98 (which is closed), so I'm gonna close this too. I'm waiting for another pull request to be merged before pushing a new release since it's very close to merging; the only change in 4.8.0 is Pagy support, so you're fine to stay on 4.7.1 for now. Sorry about the trouble!


I didn't get my 5*

Hewwo :3
I keep re-rolling >_< But I not get my SSR >:O
Pwease help me get my SSR >:3
nuzzle

Nevermind xD forgot five stars are not guaranteed uwu
Have to keep rerolling ; w ;
1%


jsx-uses-vars breaks eslint prefer-const

I have code like this
function X(props) {
    const { filterList } = props;

    let filters = _.chain(filterList)
        .map((filter, index) =>
            <Z/>
        )
        .value();

    return (

            {filters}

    );
}

but with prefer-const on, the prefer const error on filters is removed when I switch on jsx-uses-vars

I created a repro repo..
https://github.com/lukeapage/eslint-react-bug-prefer-const-716

Thanks for the issue, but if I'm right there is nothing we can do on our side to prevent this, since the issue seems to come from ESLint itself (https://github.com/eslint/eslint/issues/5837), right?

It sounds like with prefer-const there's a (correct) error, and with prefer-const + jsx-uses-vars, there's (incorrectly) not an error.

prefer-const is ignoring variables with eslintUsed set on it. Since that's how we mark a variable as used in ESLint I don't see what we can do here 😐
But:

We mark JSXOpeningElement (<App />) and JSXExpressionContainer ({filters}) as used but ESLint seems to correctly handle JSXExpressionContainer without the help of this rule. Maybe we could remove this? (All tests are still passing without it, but maybe we're missing a pattern?)

This will solve the case described by @lukeapage but we'll still have the problem with JSXOpeningElement:
let App =
; // should warn "'App' is never reassigned. Use 'const' instead" but will not
<App />

Apparently they are not sure if this check on eslintUsed is still useful (https://github.com/eslint/eslint/issues/5837#issuecomment-235490801), so maybe they will remove it? In this case it would solve the entire problem.

Yeah sorry for not updating after tracking down.
I left this open until a solution is found, in case something needs to be done here as welll.

I hit this today. A minimal repro:
function foo() {
  let iCouldBeConst = 6;
  return 	;
}

and eslint config:
{
    "parserOptions": {
        "ecmaVersion": 6,
        "ecmaFeatures": {
            "jsx": true
        },
        "sourceType": "module"
    },
    "rules": {
        "react/jsx-uses-vars": 2,
        "prefer-const": 2
    },
    "plugins": [
        "react"
    ]
}

Sounds like removing eslintUsed on JSXExpressionContainer would be a definite improvement, since that would fix both my situation and OP.

Sounds like removing eslintUsed on JSXExpressionContainer would be a definite improvement, since that would fix both my situation and OP.

Yes, I will remove this. It does not fix the whole issue with prefer-const but it's better than nothing for now.

Keep it open for now due to https://github.com/yannickcr/eslint-plugin-react/issues/716#issuecomment-235762191

Thanks :)

Fixed in ESLint 3.4.0


[docs] Add Config Subscribe example to client doc

Need to add config subscribe example here: https://docs.dapr.io/developing-applications/sdks/js/js-client
Related issue: dapr/docs#2770

👋🏻


fixes call bin of grunt-cli on Windows

NodeJS can not run the script with path to the JS file from the bin
folder (which was, grunt-cli/bin/grunt).
But showing the path to the CMD script it runs normally.
For * nix systems went the way of an SH script.

See https://github.com/sindresorhus/get-grunt-tasks/commit/3fc225f1331c38b5f5fe1f236f69715c39a64d68


make DMatrix subclassable that supports slice mehod

Currently, subclass of DMatrix could not slice normally. slice method on subclass will return a DMatrix instance not the subclass instance.

In my case, I want the DMatrix been attached the index. This make coding simple and convenient. In most of the cases, I use pandas.DataFame that has a datetime index as the raw data, and I need do slice by date range. There is some code sample.
from typing import Any, Self
from functools import wraps
import pandas as pd
import xgboost as xgb

class MyDMatrix(xgb.DMatrix):
    def __init__(self, data: Any, *args: Any, index: pd.Index | None = None, **kwargs: Any) -> None:
        super().__init__(self, data, *args, **kwargs)
        self._set_index(index)

    def _set_index(self, idx: pd.Index | None = None) -> None:
        n_rows = self.num_row()
        if idx is None:
            idx = pd.Index(np.arange(n_rows))
        else:
            assert len(idx) == n_rows
        self._index = idx

    @property
    def index(self) -> pd.Index:
        return self._index

    def slice(self, idx: Any) -> Self:
        index = self.index[idx]
        dmatrix = super().slice(idx)
        dmatrix._set_index(index)
        return dmatrix

    def get_rindex(self, start: pd.Timestamp | None = None, end: pd.Timestamp | None = None) -> list[int]:
        ...

class MyBooster(xgb.Booster):

    def predict(
        self,
        ds: MyDMatrix,
        **kwargs: Any,
    ) -> pd.DataFrame:
        preds = super().predict(ds, **kwargs)
        if len(preds.shape) == 1:
            preds = preds.reshape((-1, 1))
        return pd.DataFrame(preds, index=ds.index)

@wraps(xgb.train)
def train(params: dict[str, Any], dtrain: MyDMatrix, num_boost_round: int = 10, **kwargs:Any) -> MyBooster:
    booster = xgb.train(params=params, dtrain=dtrain, num_boost_round=num_boost_round, **kwargs)
    return MyBooster(model_file=booster)

One more thing, xgb.Booster and xgb.DMatrix are both pure python class not C class from cython or somewhere, I think it's not a big problem to subclass them. If anyone really want to do that just like me, he/she just needs overriding the slice method in case of DMatrix

Thank you for sharing, I think the users would indeed need to override the slice method as you have suggested. The approach used in this PR assumes a correct implementation of the __init__ method from the subclass, which, from my perspective, is more difficult to do than an override.
Will close the PR now. Feel free to continue the discussion.


ollama downloading something in the background

Why is ollama downloading? I just did an update and still its downloading something.  Ollama is supposed to be offline - not using up my mobile data.
I can't even figure out which version of ollama I have, there is no CLI command to report the version.
M2-Air ~ % ollama
Large language model runner

Usage:
  ollama [command]

Available Commands:
  serve       Start ollama
  create      Create a model from a Modelfile
  run         Run a model
  pull        Pull a model from a registry
  push        Push a model to a registry
  list        List models
  cp          Copy a model
  rm          Remove a model
  help        Help about any command

Flags:
  -h, --help   help for ollama

Hi @abulka. Thanks for the issue (and sorry you encountered this)
The Ollama macOS app will download automatic updates when available. These updates are to add support for new models or bug fixes reported by the community here.
You can manually download the latest version here to stop it from downloading an update. Recent versions of ollama have an ollama -v command that will show you which version is running.
Every release also includes a "binary-only" ollama-darwin version that doesn't auto update (if this is of interest for any reason). The Mac app is easiest to set up and stay up to date, but it's entirely up to you!
Hope this helps. I'll close this issue for now, but please re-open if you have any more concerns!

Thanks for the response.
The background download finally finished and has settled down.  And my ollama now has the ollama -v feature, as you say, which is good.  A preferences dialog would be handy where I can temporarily stop background updates.
P.S. I just blew my months quota of 50gb mobile data due to Sonoma downloading gb's of scenic flyover screensavers in the background. So I'm on slow data whilst on the road, for the rest of the month - so am a bit sensitive to my internet usage at the moment!


Jacoco: File name collisions break coverage calculation

Any two files with identical names will make Danger/Shroud output bogus numbers for the coverage percentage.
It's not too strange on a large project (perhaps with many modules) to have a couple files in different packages, but the same name.  Eg,
com.my.app.feature_one.DomainExtensions
com.my.app.feature_two.DomainExtensions

When Shroud parses the jacoco report xml, it only looks at the file name, not the fully qualified path.
https://github.com/livefront/danger-shroud/blob/54fe4c62d182be18250c3b6ff73a9afb6ac5b84a/lib/shroud/plugin.rb#L147
The sourcefilename field in xml is used to add together all the covered/missed lines, but if there happen to be two (or more) files with that name, Shroud will pull all line coverage from each file, leading to a larger denominator than expected.
Instead, Shroud should use the fully qualified class name as the key, which would keep each file as a distinct record when aggregating coverage counts.

I ran into this on a large multi-module project, where a team was orchestrating a code migration across modules and had some temporarily duplicated file names (though with different packages).


Note Python 3.5 Compatibility

I noticed the travis instructions were updated in 2015.  I haven't fully battle tested this myself on 3.5, but I'm curious if the maintainers are ready to advertise the compatibility.  If so, merge away!

Looks like there's multiple problems with python 3.x test suite.  Is it just the test suite, or is it actually not compatible with 3.3? And 3.5?  Are the maintainers interested in help to fix this?

It looks like numpy 1.12 drops support for Python 3.3 which is listed present in qPython Travis config, thus the build is now failing on Travis. There is number of possible solutions here:

drop the support for Python 3.3, add support for 3.5 and adjust required version of numpy,
set the numpy requirement to prevent upgrading to 1.12.

In addition there is an issue with one of unit tests on Python 3.x. I will prepare a fix for this.
Also, the project would benefit from switching to tox for testing multiple Python versions. I plan to prepare a pull request addressing this topic. Unfortunately, I'm now longer actively working on the project, and cannot promise any time boundaries.

I am in favor of dropping support for Python 3.3 and adding support for 3.5

I am in favor of dropping support for Python 3.3 and adding support for 3.5
+1

I pushed a pull request with unit test fix. This also adds support for 3.6 and drops 3.3.
Due to changes in supported Python versions, I would suggest to bump the qpython version to 1.3. This is reflected already in Changelog, but you have to bump the version in __init__.py.


Parse objects conforming the Codable protocol

Resolves https://github.com/xcodeswift/xcproj/issues/83
Short description 📝
Remove Unbox dependency by using the native Codable protocol.
Solution 📦
Update all the elements to conform the Codable protocol and remove the Unboxable conformance.
Implementation 👩💻👨💻

[x] PBXFileElement
[ ] PBXBuildFile
[ ] PBXAggregateTarget
[ ] PBXBuildPhase
[ ] PBXContainerItemProxy
[ ] PBXCopyFilesBuildPhase
[ ] PBXFileReference
[ ] PBXFrameworksBuildPhase
[ ] PBXGroup
[ ] PBXHeadersBuildPhase
[ ] PBXNativeTarget
[ ] PBXProductType
[ ] PBXProj
[ ] PBXProject
[ ] PBXReferenceProxy
[ ] PBXResourcesBuildPhase
[ ] PBXShellScriptBuildPhase
[ ] PBXSourceTree
[ ] PBXSourcesBuildPhase
[ ] PBXTarget
[ ] PBXTargetDependency
[ ] PBXVariantGroup
[ ] XCBuildConfiguration
[x] XCVersionGroup
[ ] XCWorkspace
[ ] XCWorkspaceData

GIF

Can I help you with it? PBXBuildFile is next

Sure @artemnovichkov, you are welcome to help. It'll take us time to migrate all of them, but with help, we'll be faster 😛

I find this extension really useful when using Decodable
extension KeyedDecodingContainer {

    public func decode<T>(_ key: KeyedDecodingContainer.Key) throws -> T where T: Decodable {
        return try decode(T.self, forKey: key)
    }

    public func decodeIfPresent<T>(_ key: KeyedDecodingContainer.Key) throws -> T? where T: Decodable {
        return try decodeIfPresent(T.self, forKey: key)
    }
}

It makes the code easier to write as you don't need to specify the type again:
- self.name = try container.decode(String.self, forKey: .name)
+ self.name = try container.decode(.name)

It also means that support can be added by doing search and replace on the unbox functions

It's very useful! Great idea @yonaskolb. I'll update the code to use it.

I just noticed that this removed the BuildSettings typealias. Was there any particular reason for that?

I came across some issues trying to parse the settings, and I removed it thinking it was related.  Do you think we should keep it?

It’s not strictly needed, but I think it was nice how it unified the types and purpose wherever build settings were used. The factthat it was public means people may have been using it too (as was the case of XcodeGen)


Avoid stderr redirection so GIT_TRACE can be used

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Ensure all commits include DCO sign-off.
[ ] Ensure that your contributions pass unit testing.
[x] Ensure that your contributions contain documentation if applicable.

Description
Redirecting stderr to stdout causes incompatibility while using GIT_TRACE env var.
Example 1
$ gem list git | grep "git "
git (1.17.2)

$ cat test.rb
require 'git'

g = Git.open("/home/jon/src/git-gem/test_git_repo")

$ export GIT_TRACE=1
$ ruby test.rb
Traceback (most recent call last):
/home/jon/src/git-gem/12:48:53.007165 git.c:460               trace: built-in: git rev-parse --show-toplevel
/home/jon/src/git-gem/test_git_repo: path does not exist (ArgumentError)

$ echo $?
1

$ export GIT_TRACE=0
$ ruby test.rb
$ echo $?
0

Example 2
$ export GIT_TRACE=0
$ git -C test_git_repo/ -c core.quotePath=true -c color.ui=false rev-parse --show-toplevel
/home/jon/src/git-gem/test_git_repo
$ echo $?
0

$ export GIT_TRACE=1
$ git -C test_git_repo/ -c core.quotePath=true -c color.ui=false rev-parse --show-toplevel
12:46:37.325649 git.c:460               trace: built-in: git rev-parse --show-toplevel
/home/jon/src/git-gem/test_git_repo
$ echo $?
0

Hello @jonasserrano! Thank you for the contribution.
You are right to point out that simply redirecting STDERR to STDOUT for every command is a weakness of this gem.
#617 is a fix that addresses this issue as well as others. I am waiting for a fix for JRuby on Windows before cutting a new major release that includes that change and others. Even after #617, we would have to explore how using the GIT_TRACE functionality will impact this gem.
There are a few cases where STDERR output is needed by this gem and other cases where STDERR is expected but should be suppressed. I would say that the tests do not capture this well... test coverage is lacking in this regard.
I suggest that you close this PR and open an issue about supporting GIT_TRACE. At the appropriate time we can evaluate its impact on this gem and how it might be accomplished.

Closing as per James recommendation


Add option to apply your own proxy list with command-line args

Description
The app was not using a proxy list from URL when it was applied via command-line argument "-proxylist-url".
The fix allows specifying proxy list url via the command-line argument (without using custom config).
Changes summary:
Add ProxyListURL to GlobalConfig
Make ProxyListURL a priority over ProxyURL
Fix clientConfig.ProxyURLs assign
Make func GetProxylist public
Motivation: Bug that proxy list does not work and similar open issue.
No new dependencies are required
Fixes # (issue)
https://github.com/Arriven/db1000n/issues/34
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Run Http Server locally, make it return the proxy list in the following way:
[
"socks5://<IP_ADDRESS>:1080",
"socks5://<IP_ADDRESS>:1080",
"socks5://<IP_ADDRESS>:1080"
]
Put a link to this local HTTP server as an argument to the db1000n:
go run main.go -proxylist-url http://localhost:8123

Test Configuration

Release version: 0.7.4
Platform: Windows 10 x64

Logs
2022/03/13 16:26:47.079005 http.go:148: Attacking [http://<IP_ADDRESS>:80]()
2022/03/13 16:26:47.079005 http.go:103: List of proxies: [socks5://<IP_ADDRESS>:1080,socks5://<IP_ADDRESS>:1080,socks5://<IP_ADDRESS>:1080]()
2022/03/13 16:26:47.079005 http.go:109: proxyURLs: [[socks5://<IP_ADDRESS>:1080]() [socks5://<IP_ADDRESS>:1080]() [socks5://<IP_ADDRESS>:1080]()]
2022/03/13 16:26:47.079504 http.go:176: GET [https://<IP_ADDRESS>:443]() started at<PHONE_NUMBER>
2022/03/13 16:26:47.079504 http.go:148: Attacking [http://<IP_ADDRESS>:80]()
2022/03/13 16:26:47.079504 http.go:103: List of proxies: [socks5://<IP_ADDRESS>:1080,socks5://<IP_ADDRESS>:1080,socks5://<IP_ADDRESS>:1080]()
2022/03/13 16:26:47.079504 http.go:109: proxyURLs: [[socks5://<IP_ADDRESS>:1080]() [socks5://<IP_ADDRESS>:1080]() [socks5://<IP_ADDRESS>:1080]()]

Screenshots

All right, I will extend the existing system-proxy flag (not sure why the existing -proxylist-url flag is never used though, I didn't add it, it was in the code, just never used from the command-line).
What about making a flag with a proxy list file name, similar to how it's done in MHDDoS? It makes more sense for me than providing all of the proxies in the command line.

@Staskkk the idea with the file seems good but you can kinda already achieve that functionality via the shell. i.e. db1000n --system-proxy $(cat proxylist.txt | tr '\n' ',')

All right, I will try to post the changes later today, thanks!

actually, you can already pass a comma-separated list of proxies into the --proxy flag (misstyped that flag in previous comment, sorry). This won't work if you want the proxylist to be dynamically updated with an interval but even that would better be achieved by letting the commandline to be templated and tweaking the config so that it's reevaluated every 10000 requests or so) - I'll probably even work on that now while the idea is fresh in my head

@Arriven All right, I'll use the --proxy then and make PR for some other issue. BTW, is it always just choosing the random proxy from the list? Maybe it makes sense to use all the proxies in the separate threads (or at least add an option for that)?
Or some other optimization, like use them in order or drop some of the proxies if they become slow?

It's always choosing random proxy from the list, yes, and I think it's better than splitting the list between threads as that would actually make it easier for specific targets to defend - they'd have to block only a sub list of IP addresses rather than full range of them with full range of proxies
As for checking if proxies become slow/unavailable I think it's better to handle that outside of the program as it can be done more efficiently that way

Also see #378 for a draft of proxylist refactoring, I think I'll finish it today a bit later

All right man, thanks for the explanation!


Why does BluetoothListener.AcceptBluetoothClient not wait?

I would like to listen to the serial port of the Bluetooth adapter on a Windows device.
First, I start a separate Task for the listener in the main thread:
BluetoothListener _bluetoothListener;
Task? _bluetoothListenerTask;

...

_bluetoothListener = new (BluetoothService.SerialPort);
_bluetoothListener.Start();

_bluetoothListenerTask = new(new(BluetoothListenerTask));
_bluetoothListenerTask.Start();

This starts a new Task, listening for new connections of remote devices and start a second new Task to handle that conntion:
private void BluetoothListenerTask()
{
    while (_bluetoothListener.Active)
    {
       var client = _bluetoothListener.AcceptBluetoothClient();
       Task bluetoothProcessorTask = new(new(BluetoothProcessorTask), client);
       bluetoothProcessorTask.Start();
    }
}

private async void BluetoothProcessorTask(object? state)
{
    ...
}

Unfortunately, BluetoothListener.AcceptBluetoothClient does not wait for incoming connections. It just gives a null value instead of a BluetoothClient object back.
Because of this, my BluetoothListenerTask tasks runs the whole time and costs a lot of resources.
How can I wait for incoming connections?

What platform are you running this on? Only the Windows platform has an implementation for BluetoothListener and there is a bug in the Android code where it doesn't throw a PlatformNotSupportedException when you call start.

Is there any debug window output which might indicate an error at the underlying Socket level? What windows platform are you building for? Only the Win32 builds support BluetoothListener currently.

I'm developing in the VS 2022 IDE. I can't see any further hint.
I've downloaded your code (via GIT) and tried to use it without the NuGet package.  So I don't have an idea, how I can assist you with more details.

Do you plan to offer the BluetoothListener for Android too?

.Net has a good library for Bluetooth a Android with Bluetooth listening. Why don't you implement it?

I can get incoming Bluetooth connections via your BluetoothListener.AcceptBluetoothClient() right now.
But not via .Net StreamSocketListener.BindServiceNameAsync with the followin code:
listener = new StreamSocketListener();
listener.ConnectionReceived += BtConnection_ReceivedEvent;

await listener.BindServiceNameAsync(rfcommProvider.ServiceId.AsString(), SocketProtectionLevel.BluetoothEncryptionAllowNullAuthentication);

string SdpServiceName = Config.AppName;
const byte SdpServiceNameAttributeType = (4 << 3) | 5;
const UInt16 SdpServiceNameAttributeId = 0x100;

// Set the SDP attributes and start Bluetooth advertising
DataWriter sdpWriter = new DataWriter();

// Write the Service Name Attribute.
sdpWriter.WriteByte(SdpServiceNameAttributeType);

// The length of the UTF-8 encoded Service Name SDP Attribute.
sdpWriter.WriteByte((byte)SdpServiceName.Length);

// The UTF-8 encoded Service Name value.
sdpWriter.UnicodeEncoding = Windows.Storage.Streams.UnicodeEncoding.Utf8;
sdpWriter.WriteString(SdpServiceName);

// Set the SDP Attribute on the RFCOMM Service Provider.
if (rfcommProvider.SdpRawAttributes.ContainsKey(SdpServiceNameAttributeId))
    rfcommProvider.SdpRawAttributes.Remove(SdpServiceNameAttributeId);
rfcommProvider.SdpRawAttributes.Add(SdpServiceNameAttributeId, sdpWriter.DetachBuffer());

// Start Bluetooth advertising
rfcommProvider.StartAdvertising(listener);

Do you have an idea, how this fails?

Added WinRT and Android handlers in 4.0.31


StaffServiceEmails.js (eventually) sends new member notifications with wrong styles

Issue Summary
Sometimes Ghost sends new member email notifications with incorrect styles, resulting in ugly blue backgrounds like this:

The StaffServiceEmails class sends new member email notifications that initially show no problem. However, at some point, it appears the styles Handlebars partial (from ghost/staff-service/lib/email-templates/partials/styles.hbs) gets overwritten with the styles from ghost/email-service/lib/email-templates/partials/styles.hbs. My guess is that they both use the same Handlebars instance, but the partials for StaffServiceEmails are only registered once in its constructor.
Steps to Reproduce

Enable new member email notifications.
Wait for new sign-ups.
Initially the notification messages appear with correct styles.
Eventually the notification messages will show incorrect styles.

Ghost Version
5.59.4
Node.js Version
16.20.2
How did you install Ghost?
Ubuntu 22.04
Database type
MySQL 8
Browser & OS version
No response
Relevant log / error output
No response
Code of Conduct

[X] I agree to be friendly and polite to people in this repository

@daniellockyer  how to setup magic link in local ?

Thank you for reporting this issue! This is fixed and will be released in the next release of Ghost on Friday


4.5 Explain everything related to Girlscript Summer of code #293

Description 📜
4.5 Explain everything related to Girlscript Summer of code
Fixes #293

Type of change 📝

[ ] Au#dio
[ ] Vi#deo
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[x] Open Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Create PR from your_fork_repo :Opensource branch to girlscript : Opensource branch @adityakrm2


This server is all jacked up man!

Andarius reports: This server is all jacked up man!

I know. But I'm working on it.


My production builds are going to dev mode

Describe the bug
I was checking my production code in chrome dev tools and noticed that the Vue extension was enabled and showing all the details.
my vite.config.ts
import { fileURLToPath, URL } from "url";

import { defineConfig } from "vite";
import vue from "@vitejs/plugin-vue";
// eslint-disable-next-line @typescript-eslint/no-unused-vars
import ssgOptions from "vite-ssg";
import generateSitemap from "vite-ssg-sitemap";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [vue()],
  resolve: {
    alias: {
      "@": fileURLToPath(new URL("./src", import.meta.url)),
    },
  },
  build: {
    manifest: true,
    minify: "esbuild",
  },
  ssgOptions: {
    mock: true,
    script: "async",
    formatting: "minify",
    onFinished() {
      generateSitemap();
    },
  },
});

Am I doing anything wrong here?
I'm building with npm run dev which runs npx vue-tsc --noEmit && vite-ssg build
Reproduction
will add
System Info
System:
    OS: Windows 10 10.0.22621
    CPU: (6) x64 AMD Ryzen 5 3500X 6-Core Processor
    Memory: 8.15 GB / 15.95 GB
  Binaries:
    Node: 18.4.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.3.0 - D:\<PROJECT>\node_modules\.bin\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.755.0), Chromium (109.0.1518.70)
    Internet Explorer: 11.0.22621.1

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[ ] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[ ] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[ ] The provided reproduction is a minimal reproducible of the bug.

Found a discussion thread about this #329 . closing this now

Leaving my solution here as well
modify your "build" script to explicitly set node to production mode
Windows
 "build": "set NODE_ENV=production&& vite-ssg build",

Linux
  "build": "export NODE_ENV=production && vite-ssg build",


InverseMelScale in NewDisposeScope

Hello! I'm now using torchaudio.transforms.InverseMelScale to convert a generated mel spectrum to its waveform.
I've found that the following code will continuously occupy more memory without freeing it, which finally crashed my application:

And if I remove NewDisposeScope():

It seems that the dispose scopes will block the GC to release the tensors? I don't know much about that, so could anyone please check whether the behavior is expected?
And if it is, maybe the dispose scopes (or some other memory managment approaches) should be applied inside InverseMelScale.forward to release the tensors in the loop?

Here is my code and file:
using TorchSharp;
using static TorchSharp.torch;

var melPath = "C:\\Users\\yueyinqiu\\Documents\\MyTemporaryFiles\\mymel.dat";
var tensor = Tensor.Load(melPath);
using (NewDisposeScope())
{
    var inverseMelScale = torchaudio.transforms.InverseMelScale(
        n_stft: 2048 / 2 + 1,
        n_mels: 512,
        sample_rate: 24000);
    var spec = inverseMelScale.call(tensor);
}

mymel.zip (The file is generated from a untrained model so it is not a real mel spectrum.)

Thank you for pointing this out. I took a look at the code and there isn't any tensor management going on there, so when you added the dispose scope all the tensors were kept in memory for the entire scope.
I'll rewrite it with more careful tensor management.

The dispose scopes are meant to automatically dispose of the native memory of all tensors created within its lifetime. Tensors are backed by memory allocated in C++, so not subject to GC, and not suppressed.
The forward() in question does look very large, and should probably have a dispose scope around it (or several... :-)), but it's also a good idea to place one around your training and validation loops, etc., just as long as you remember to escaped the tensors that should survive the end of the scope.

The forward() in question does look very large, and should probably have a dispose scope around it (or several... :-)), but it's also a good idea to place one around your training and validation loops, etc., just as long as you remember to escaped the tensors that should survive the end of the scope.

The specific issue in the forward is that it runs a full training loop without any dispose scope, so the critical dispose scope was the one added inside the loop to remove the tensors created with every iteration.

Since this was a pretty serious problem, I'm doing a fast-follower release today. It'll be v0.102.2


SELECT FOR: Unexpected term

Image the following source code within a class method:
SELECT SINGLE FOR UPDATE * FROM /scwm/mfscch
  INTO ls_mfscch
  WHERE lgnum   = ls_mfscch-lgnum
    AND plc     = ls_mfscch-plc
    AND channel = ls_mfscch-channel.

ABAP Cleaner throws an error on execution:

Workaround:
Comment the related sql statement, then execute ABAP Cleaner and uncomment the statement again.

Hi Marius,
thanks again for reporting this – this should now work with version 1.13.1, which was just released!
Kind regards,
Jörg-Michael

Yes, works now - many thanks! 👍🏼


Update smithy4s-http4s, ... to 0.17.14

About this PR
📦 Updates

com.disneystreaming.smithy4s:smithy4s-http4s
com.disneystreaming.smithy4s:smithy4s-http4s-swagger
com.disneystreaming.smithy4s:smithy4s-sbt-codegen

from 0.17.0 to 0.17.14
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.disneystreaming.smithy4s" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.disneystreaming.smithy4s" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #62.


Can't login it.

I'm using the latest version of FB chat using the Python REPL and I cannot log in. I'm entering the email and password correctly and I checked. I'm using the default example in the documentations but whenever I try this happens:
>>> client = Client('email, 'pass')
Logging in...
Attempt #1 failed, retrying
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Library/Python/2.7/site-packages/fbchat/client.py", line 89, in __init__
    if not self.login():
  File "/Library/Python/2.7/site-packages/fbchat/client.py", line 164, in login
    self.payloadDefault['__rev'] = int(r.text.split('"revision":',1)[1].split(",",1)[0])
IndexError: list index out of range
>>>

Edit: 2FA is disabled and i'm not accepted via Email or Password. Scraping Error?

I'm positive that you're not using the latest version of fbchat:
The line self.payloadDefault['__rev'] = int(r.text.split('"revision":',1)[1].split(",",1)[0]) doesn't exist anymore, and this problem has been fixed in earlier versions. How did you install fbchat, and if you did it via. pip, did you make sure you installed/upgraded fbchat for the correct version?

 I should reinstall my OS.


Sync fork with what's currently in main

I think this is how you do it. Base is mine and head is the main and the arrow is pointing into mine

Idk how i did this i just entered what the AI told me to, i thought the command said it was a commit not a merge accept


Lazily evaluate content instead of eagerly evaluating it

This changes content to load only when a component's render?
predicate method returns true. The render? method can still access
content, which will cause it to be evaluated.
~This shouldn't be a breaking change for components themselves, but
attempting to access a slot in before_render or render? may no
longer work.~
This is an alternative approach to https://github.com/github/view_component/pull/559 (but doesn't remove the value of the conversation happening there, imo) and may at least partially close https://github.com/github/view_component/issues/558

I merged https://github.com/github/view_component/pull/576 into this PR to highlight the performance aspect of this change. If this gets merged, I think that PR can be closed.

Just pushed up a change that makes accessing slots from render? and before_render continue to work without having to manually evaluate content.
Here's the benchmark:

We may have gotten a tiny bit slower, but not enough to be a concern.

I just ran this locally against the primer/view_components test suite and getting test failures, presumably due to Slots v1? Looking now though.

Just pushed up https://github.com/github/view_component/pull/613/commits/35e8d6cd037d8fa16266c127c81b83bb77d1dc4d to resolve that issue.

Yep! Adding one now.

Stop this mess now! Look... These are my personal email addresses you are taking as your own to do with my personal content as you please and trying your best to deny my rights to my personal property. I can make a police report if necessary. Which do you prefer?


GenericEtcd not testing as expected

While creating a cluster scoped api resource I noticed that when I passed in a generate name on the object meta I was getting resttest.go:180: Expected an error, but we didn't get one.
This appears to be caused by the rest.BeforeCreate method removing the namespace for any strategy whose NamespacedScoped function returns false coupled with the test that tries to ensure a namespace on a NamespacedScope==false strategy is rejected.  https://github.com/pweil-/kubernetes/blob/6b3a6e6b983f967c88d14d26542ec6e30c49ebd3/pkg/api/rest/create.go#L60-60
While debugging I was looking at the minion tests since they are non-namespace scoped.  I noted two things

It is not using the ClusterScoped version of the resttest
It was not failing like my test was

The second point appears to be caused by https://github.com/pweil-/kubernetes/blob/6b3a6e6b983f967c88d14d26542ec6e30c49ebd3/pkg/registry/minion/etcd/etcd_test.go#L93.  The validation error returned from validation is actually metadata.name: required value, not a failure to validate that a namespace is rejected or is mismatched.
To recreate the first issue, modify the minion's etcd_test.go to pass in a GenerateName field and add ClusterScope() and you will receive a failure from TestCreateRejectsNamespace
func TestCreate(t *testing.T) {
	storage, fakeEtcdClient := newStorage(t)
	test := resttest.New(t, storage, fakeEtcdClient.SetError).ClusterScope()
	node := validNewNode()
	node.ObjectMeta = api.ObjectMeta{}
	node.ObjectMeta.GenerateName = "foo-"
	test.TestCreate(
		// valid
		node,
		// invalid
		&api.Node{
			ObjectMeta: api.ObjectMeta{Name: "_-a123-a_"},
		},
	)
}

[pweil@localhost kubernetes]$ hack/test-go.sh pkg/registry/minion/etcd
Running tests for APIVersion: v1beta1 with etcdPrefix: registry
+++ [0518 18:15:53] Running unit tests without code coverage
--- FAIL: TestCreate (0.00 seconds)
	fake_etcd_client.go:115: generating index 1
	fake_etcd_client.go:201: creating /registry/minions/test, index 1 (ttl: 0)
	fake_etcd_client.go:115: generating index 2
	fake_etcd_client.go:201: creating /registry/minions/test-7g15a, index 2 (ttl: 0)
	fake_etcd_client.go:115: generating index 3
	fake_etcd_client.go:201: creating /registry/minions/foo-tafr2, index 3 (ttl: 0)
	resttest.go:196: Expected an error, but we didn't get one
FAIL
FAIL	github.com/GoogleCloudPlatform/kubernetes/pkg/registry/minion/etcd	0.109s
!!! Error in hack/test-go.sh:156
  'go test "${goflags[@]:+${goflags[@]}}" ${KUBE_RACE} ${KUBE_TIMEOUT} "${@+${@/#/${KUBE_GO_PACKAGE}/}}"' exited with status 1
Call stack:
  1: hack/test-go.sh:156 runTests(...)
  2: hack/test-go.sh:216 main(...)
Exiting with status 1

To recreate the second issue, remove the ClusterScope() portion of the code above and the failure moves to the TestCreateRejectsMismatchedNamespace method:
[pweil@localhost kubernetes]$ hack/test-go.sh pkg/registry/minion/etcd
Running tests for APIVersion: v1beta1 with etcdPrefix: registry
+++ [0518 18:16:52] Running unit tests without code coverage
--- FAIL: TestCreate (0.00 seconds)
	fake_etcd_client.go:115: generating index 1
	fake_etcd_client.go:201: creating /registry/minions/test, index 1 (ttl: 0)
	fake_etcd_client.go:115: generating index 2
	fake_etcd_client.go:201: creating /registry/minions/test-cwtn9, index 2 (ttl: 0)
	fake_etcd_client.go:115: generating index 3
	fake_etcd_client.go:201: creating /registry/minions/foo-qshk5, index 3 (ttl: 0)
	resttest.go:180: Expected an error, but we didn't get one
FAIL
FAIL	github.com/GoogleCloudPlatform/kubernetes/pkg/registry/minion/etcd	0.111s
!!! Error in hack/test-go.sh:156
  'go test "${goflags[@]:+${goflags[@]}}" ${KUBE_RACE} ${KUBE_TIMEOUT} "${@+${@/#/${KUBE_GO_PACKAGE}/}}"' exited with status 1
Call stack:
  1: hack/test-go.sh:156 runTests(...)
  2: hack/test-go.sh:216 main(...)
Exiting with status 1

I actually caught some of these in https://github.com/GoogleCloudPlatform/kubernetes/pull/6201 and forgot to open a separate PR when I closed that one.

/cc @lavalamp @derekwaynecarr

@liggit do you want to pull relevant pieces from the past PR or shall I do it?

I can


Release 1.2.0

Issue #, if available: N/A
Description of changes: beam search capability (PR #35)
Testing done: yes
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're
unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of
what we are going to look for before merging your pull request.

[x] I have read the CONTRIBUTING document.
[x] I have added tests that prove my fix is effective or that my feature works (if appropriate).
[x] I have updated any necessary documentation, including README and docs (if appropriate).

By submitting this pull request, I confirm that my contribution is made under the terms of the
Apache 2.0 license.

@Laurenstc, @patrick22414: please review commit 76ce099 (fix mypy type error): whether tensor device & shape is still correct.

hi @verdimrc

slightly modified the logic of accum_logprobs so that its type is always Tensor instead of Tensor | None, and also fit the name better
fixed this in my test. overwrite_valid_tokens should've be a dict, somehow it was wrapped in a tuple
beam_search_n_steps() is intended to input/output ndarray and only use tensors internally, as is what I found in other Simulator APIs. @yapweiyih please let me know if this is not the desired behaviour

fixed this naming here where seq_tensor is cast back to ndarray which is also causing the mypy error

Hi @songyiy22414: would you like to push your changes to this branch, and let's see the CI/CD results?

I don't have the clearance to push to public repos as per the company's open-source policy, so @Laurenstc has been helping me to push the changes. Apologies for the delay. We intend to push the changes and check the CI/CD results as soon as possible


Update mbedtls configuration - MBEDTLS_GCM_C

Work around to https://github.com/ARMmbed/mbed-os/issues/8893.
Enable MBEDTLS_GCM_C to prevent compile errors.
This commit should be removed once issue #8893 is fixed.

@artokin I believe this change should have gone to the mbed-os-5.11.0-oob branch! As all changes to examples during oob should happen this way, so that when the oob fixes get merged back to master nothing conflicts or is lost..

@adbridge , I'll update the mbed-os-5.11.0-oob with this change.

@artokin thanks :)


Plugin update "unable to find" errors

Description of the problem or steps to reproduce
Running plugin update returns various "unable to find" errors, alternating between various plugins.
Example:

unable to find a matching version for "literate"

Specifications
Version: 1.3.3
Compiled on September 28, 2017
Commit hash: a02ae3c
OS: Arch Linux
Terminal: Konsole
My settings.json has "https://raw.githubusercontent.com/micro-editor/plugin-channel/master/channel.json" as the only channel, with no repo's.

Note that plugin update pluginname works, it's just the "update all" functionality not working.

Looks like the problem is the built in plugin has
VERSION = "1.0.0"

in it and the other built in plugins do not have version numbers in the file.
There is a problem with look up for built in plugins with version number given in the plugin file.
When you type in plugin list
built in ones with no version in the file come up with plugin-name (0,0,0-unknown)
The literate plug comes up with literate (1.0.0) so it will try and up date it.
If you comment out the VERSION = "1.0.0" in the file literate.lua it does not throw the error.
Hope this helps get closer to the problem.

Fixed in https://github.com/zyedidia/micro/pull/939

Hmm. Not sure what update fixed it, but it seems to work again, even when trying a reinstall of filemanager.. Closing.

works fine for now again, very strange

And it's happening again after I bumped the version in filemanager-plugin.
This repo file seems to make micro just give up https://github.com/NicolaiSoeborg/filemanager-plugin/blob/v3.1.2/repo.json

Seems it was all my fault, as https://github.com/micro-editor/plugin-channel/pull/25 seemed to have fixed this. Woops :sweat:


addFile() Encoding Encoded URL Parameters

Describe the Bug
When using addFile(), FilePond changes querystring parameters inconsistently before retrieval.
To Reproduce
Pass a URL containing an already-encoded character.
For example, calling:
filepond.addFile('https://pqina.nl/filepond/docs/images/logo.svg?x=y%2Cz');
Will result in it attempting to fetch:
https://pqina.nl/filepond/docs/images/logo.svg?x=y%252Cz
Expected Behavior
FilePond should either not modify the URL, or it should do so in a predictable manner. For example, FilePond does not convert commas to %2C when passed unencoded (i.e. logo.svg?x=y,z), so it does encode % while ignoring ,.
In my case, the remote server validates the request based on a hash of the querystring, so it needs to be submitted with proper encoding, whether that occurs before or after being passed to FilePond.
Metadata

Browser: Chrome 86.0.4240.198
OS: macOS Catalina 10.15.7
FilePond Version: 4.23.1

Thanks for reporting @CameronSumpter
FilePond runs encodeURI on the URLs of the requests it makes.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURI
Haven't had any issues with this before. Maybe you can set up a custom load method to circumvent the encode call?

will close because inactive


Bot fills the pokebag and throws nothing

Expected Behavior
Only keep best cp / iv depending on config.json
Actual Behavior
Keeping all pokemons untill bag is full (since last update on dev branch) (08/08/2016)
Steps to Reproduce
"release": {
  "any": {"release_below_cp": 0, "release_below_iv": 0, "logic": "or"},
  "any": {"keep_best_cp": 2},
  "Eevee": { "keep_best_cp": 5 },
}

sh run.sh
Other Information
OS: Win7 64
Git Commit: ff380cd0e07f225ad1ae2c739bea9f9f80e2f8ce
Python Version: Python 2.7.12 (v2.7.12:d33e0cf91556, Jun 27 2016, 15:24:40) [MSC v.1500 64 bit (
AMD64)] on win32

Same problem. Most likely the bot's fault and not yours.

"release": {
"any": {"keep_best_cp": 2},
"Eevee": { "keep_best_cp": 5 }
}

oh ok i'll try this now.

@Tetranima You have two "any" lines. Here's my example config for you.
http://pastebin.com/p1FvwXv8
Also, keep the API key blank, it seems to crash if you use one. (for me at least)

Ok i removed the first "all" line and i'll gie it a try.
Are you talking about Gmap API key ? Never had issues with it.

guys... release all below cp0 does that make sense? how many pokemon with cp below 0 do you see? you have to put cp and iv above 0 for it to work :D let's say you put cp 300 and iv0.85 then it will work as magic

Idk if it makes sense but as long as this was the example config, i only changed what i needed and it worked so far.
I prefer to keep on ebest iv and one best cp of each kind, regardless if its under any value.


Fix unterminated strings in Bin2Data

Unterminated strings will prevent simulation from working properly.

Unterminated strings will prevent simulation from working properly.

I have been aware of  this problem. Thank you.
But the default value of str[9] is not defined, i think most compiler may leave str[9] with value 0. So it will not cause any problem, I think.
Did this mistake cause any problems for your simulation? ( I'm just wondered )

Yes. Hexadecimals are followed by messy chars (str is not initialized) and the testbench can't handle them, repeating the same word forever.


Failure converting the official Sigma rule YML file

As described in README.md of this repository, I downloaded sysmon_mimikatz_detection_lsass.yml from the official Sigma rule YML file (My system was WSL Ubuntu 22.04 LTS, Windows 11, 64 bit)
I put that file just in the locally cloned repository directory and ran the command below
./sigma2splunkalert rules/sysmon_mimikatz_detection_lsass.yml

And I got a failure from the program without any contextual information.
# Failure converting the Sigma File: rules/sysmon_mimikatz_detection_lsass.yml

Is there anything wrong with my procedure? Of course, I already installed PyYAML(6.0.1) and Jinja2(3.1.2) via pip to meet the requirements written in your documentation. I appreciate any help you can provide.

Hi, I also bumped into the same issue but solved this failure by installing sigma tools library
pip install sigmatools
as it uses sigmac underneath. When rereading prerequisites page it actually states that sigma needs to be installed. Hopefully that helps :)

Thanks for the help!


Bump pact_broker version to 1.14.0 to resolve twisted dependencies.

I have managed to reproduced this error as reported per #83
Bundler could not find compatible versions for gem "activesupport":
  In Gemfile:
    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      trailblazer (~> 0.1.0) was resolved to 0.1.0, which depends on
        actionpack (>= 3.0.0) was resolved to 3.0.0, which depends on
          activesupport (= 3.0.0)

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      trailblazer (~> 0.1.0) was resolved to 0.1.0, which depends on
        reform (= 1.2.0.beta1) was resolved to 1.2.0.beta1, which depends on
          activemodel was resolved to 5.0.2, which depends on
            activesupport (= 5.0.2)

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      padrino-core (~> 0.12.4) was resolved to 0.12.4, which depends on
        activesupport (>= 3.1)
Bundler could not find compatible versions for gem "rack":
  In Gemfile:
    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      trailblazer (~> 0.1.0) was resolved to 0.1.0, which depends on
        actionpack (>= 3.0.0) was resolved to 5.0.2, which depends on
          rack (~> 2.0)

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      padrino-core (~> 0.12.4) was resolved to 0.12.4, which depends on
        http_router (~> 0.11.0) was resolved to 0.11.2, which depends on
          rack (>= 1.0.0)

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      rack

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      rack

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      rack

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      trailblazer (~> 0.1.0) was resolved to 0.1.0, which depends on
        actionpack (>= 3.0.0) was resolved to 5.0.2, which depends on
          rack-test (~> 0.6.3) was resolved to 0.6.3, which depends on
            rack (>= 1.0)

    pact_broker (~> 1.9.3) was resolved to 1.9.3, which depends on
      padrino-core (~> 0.12.4) was resolved to 0.12.4, which depends on
        sinatra (~> 1.4.2) was resolved to 1.4.8, which depends on
          rack (~> 1.5)

    thin was resolved to 1.7.0, which depends on
      rack (< 3, >= 1)

Tested on:

MacOSX Darwin Kernel Version 16.4.0
Ruby 2.2.6 (2016-11-15 patchlevel 396) [x86_64-darwin16]
Bundler 1.14.6

This should solve #83

Ah! Of course.
Can you think of any reason we can't actually just drop the version specification entirely @tancnle?

Dropping the version spec will ensure a fresh bundle install will pulling in the latest pact_broker version. This however does not guarantee it will pull in the latest if we already downloaded a local version and locked in Gemfile.lock
ie. if I have downloaded 1.14.0 and generated Gemfile.lock, subsequently running bundle install will not download 1.15.0 unless we update pact_broker version specification in Gemfile.
I think it is ok to make sure we update this version spec whenever a new version is pushed. Alternatively we can use relative local path, rather than pulling from gem.

Good points. I actually have a copy of the example directory where I use a relative path to start up the app. My original thought was that the directory would be able to be copied as a standalone thing without the rest of the project, hence the gem reference rather than the relative reference.
I think that the use case for that directory is that someone is new the the broker, and hence, is unlikely to have an old copy of the gem lying around, so I'm going to remove the version restriction.


Update with recent Frontend changes

Inset text no longer deprecated
Correct modifier class for a bold label
Updated font mixin usage

wait until we release new frontend and update the Design system with it?

You can preview this change here:
Built with commit 65c9729d2a8c5afd512f2a3e86e7d853af0b71c4
https://deploy-preview-319--govuk-design-system-preview.netlify.com

I think I may have done this again in the release PR, sorry!


As a developer, I want to modify the database queries to support a fixed amount of cheeps returned.

Acceptance criteria:

The cheeps are filtered through an SQL query.
Relevant tests are added.

Co-authored by:
@AntonFriis
@olinesk
@lanaitu
@JohanSandager

Updated acceptance criteria:

The cheeps are filtered through an SQL query, not C#.
to
The cheeps are filtered through an SQL query.


Some Pal's Passive Doesn't Change.

It seems some creatures doesn't change regardless of the creature type.
I uploaded the sav file. Is it possible to check it? Creatures that can't be used have Useless nickname.
Backup Sav.zip
-Mods I'm using.
Uma Musume - Mihono Bourbon
Uma Musume Matikanetannhauser (Facial and Mouth Expression Support)

Could you elaborate on what you mean? Like the skills don't change? Or the Partner Skill?

Could you elaborate on what you mean? Like the skills don't change? Or the Partner Skill?

Skills (llike Legend/Lucky) doesn't change, not partner skill.
Edit skill is Success, Convert Success, But in-game Some creatures' skills disappear completely.
Not all creatures, but certain creatures occur regardless of type.

Can you check again to see if it is fixed now? We just released the v0.4 update with a lot of bug fixes.

Can you check again to see if it is fixed now? We just released the v0.4 update with a lot of bug fixes.

The problem was resolved in version 0.4. thank you


Adding section to global vars declaration in function "parse_arguments"

or section will be set as "default" in "parse_configuration"

Manually added change and merged


Potential faster gsub for unaccenting

UNACCENT = {
  'Ä'=>'A',  'ä'=>'a',
  'Á'=>'A',  'á'=>'a',
  'É'=>'E',  'é'=>'e',
  'Í'=>'I',  'í'=>'i',
             'ï'=>'i',
  'Ñ'=>'N',  'ñ'=>'n',
  'Ö'=>'O',  'ö'=>'o',
  'Ó'=>'O',  'ó'=>'o',
             'ß'=>'ss',
  'Ü'=>'U',  'ü'=>'u',
  'Ú'=>'U',  'ú'=>'u',
}

PATTERN = Regexp.union(UNACCENT.keys)
def unaccent_gsub(text, mapping)
  text.gsub(PATTERN, mapping)
end

text = "Apples and AÄÁaäá EÉeé IÍiíï NÑnñ OÖÓoöó Ssß UÜÚuüú"

puts unaccent_gsub(text, UNACCENT)

mapping is provided as an argument while PATTERN is generated from the mapping used. So, in theory, it should probably be moved into the function. It depends on whether mapping is actually constant or not.
In that case, I'd suggest a class instance, to cache the PATTERN.

Good point.  I added your optimization in unaccent_gsub_3b and updated the benchmark and readme. Thanks. Cheers.


Fix golint in exporter.go

Following is the link to file where lint error is present :
maya/cmd/maya-exporter/app/command/exporter.go
Lint Issue :
package comment should be of the form "Package command ..."
Help Links :
Contributors guide

@sonasingh46, Can you provide more info as to what the command package does so that I can include it in the package comment?

Well, If I'm correct on this the comment is just wrong... It should just say "Package command" instead of "Package exporter", as the package is command and the file is called exporter.

I thought the same. But then wondered if the comment was written for exporter and package was added by mistake. Wanted to check if that was the case. Nevertheless, raised #562


Support SwiftPM and Swift 6

UIBezierPath-Superpowers is so helpful and I'm currently using it in https://github.com/banjun/AcrylStand for visionOS.
This PR adds Package.swift for SwiftPM, and makes it possible for Swift 6 mode on Xcode 16 to build.
Although it's rather nice-to-have features for now, I would like to use it with Swift 6 language mode and install via SPM.

Thanks for your contribution! 🥳


Side car env vars, and HAPPY_CONTAINER

Similar to https://github.com/chanzuckerberg/happy/pull/2084, but we also need to expose this information inside of sidecars so we can make use of it with tooling (ex: observability).
Also, HAPPY_CONTAINER will allow us to distinguish between different containers in the same pod, and filter accordingly in our Grafana dashboards.

Suggesting that all env vars set by happy to be prefixed with HAPPY_* to avoid collision and clearly denote its origin.


Infinite recursion issue in Exceptions

https://github.com/nickoala/telepot/blob/89a459a49eb1725ffe678006e5e975e8777710e2/telepot/exception.py#L46-L50
It seems as if a BadHTTPResponse in the exception.py module will keep calling its own __str__ method recursively until a RuntimeError: maximum recursion depth exceeded occurs.
Launching excpetions.py and calling this function in the shell will result in the recursion error.
try:
	raise BadHTTPResponse("test","test","test")
except Exception as e:
	print(e)

Thanks.
The reason I override that was because, in the old days, if you supply an obviously wrong token, Telegram redirects to the Bot API home page and gives you an entire page of HTML. To avoid excessive output, I override that to output only the first 500 characters, and made such a terrible mistake in the process.
Today I checked again, it seems Telegram has changed to give a much better response in case of a wrong token. It actually returns a valid JSON object, causing a TelegramError.
So, it seems restricting output to 500 characters is no longer necessary. I will take the easy way out and not do the override at all, thus eliminating the infinite recursion.
Thank you for pointing out this obvious and terrible mistake :blush:


Broken URL to Sync-VSTS and Sync-VSTSGit to the script

Received an "Error 404 - Page Not Found" response to the "Azure DevOps sample runbook" and "Azure DevOps with Git sample runbook" links in PowerShell Gallery.

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

ID: 685bbe99-cd41-e4c1-598a-fed2e91887ac
Version Independent ID: 3d9830d6-b91a-e93f-38af-a893c72c5765
Content: Integrate Azure Automation with Azure DevOps Services source control
Content Source: articles/automation/automation-scenario-source-control-integration-with-VSTS.md
Service: automation
GitHub Login: @eamonoreilly
Microsoft Alias: eamono

@kiazhi Thanks for bringing this to our attention. Your comment has been shared with the content owner for further review. Please stay tuned.

@femsulu please assign this issue to me and close. I have signed off on the PR @kiazhi submitted.  @kiazhi Thanks for submitting the PR, we will make sure this gets merged on Monday.

assigned and closed as requested.


docs: [IAC-2786]: Update IaCM security doc

Description

Update IaCM security doc to make interactive model static, moving the steps above the diagram, and rewriting some descriptions. Also renaming titles for better engagement and SEO.
JIRA

PRs must meet these requirements to be merged:

[x] Successful preview build.
[x] Code owner review.
[x] No merge conflicts.
[x] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6735feded49d5190eddb1a65--harness-developer.netlify.app


package.json needs type module for ESM exports to work in node 13+?

Since upgrading Node to v13 I'm having trouble importing modules from underscore unless I add "type": "module" to underscore's package.json.

Thanks @PeterKnight for reaching out.
Please provide some details:

version of Underscore
code example of your ESM imports
any additional tools that you're using, including versions
configuration code for your tools

Our continuous integration tests run fine on node 14, so at least it cannot be the case that there is an overall compatibility issue.

Oh, and also the error message(s) you're seeing.

Code example:
import { without } from "underscore/modules/index.js";
Version of underscore 1.11.0
Tested on Node v13.11 and again on Node v14.8.0.
On Node v13 the error mentions not finding an export called without
Retested after updating to Node v14.8.0 which gives a more relevant error message:
import { without } from "underscore/modules/index.js";
         ^^^^^^^
SyntaxError: The requested module 'underscore/modules/index.js' is expected to be of type CommonJS, which does not support named exports. CommonJS modules can be imported by importing the default export.
For example:
import pkg from 'underscore/modules/index.js';
const { without } = pkg;
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:98:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:137:5)
    at async Loader.import (internal/modules/esm/loader.js:165:24)
    at async Object.loadESM (internal/process/esm_loader.js:68:5)

Adding `"type": "module" to underscore's package.json fixes the issue.
Let me know if I need to provide more details!

That's enough to confirm my suspicion, thank you.
My suspicion was that you were using Node.js's builtin, experimental support for ESM, which we don't support. As you say, it doesn't work "out of the box"; it requires either that we set the type to module (which breaks the package for the rest of the world), or that we add an exports field (which will basically prevent us from being compatible with everyone we want to be compatible with at the same time), or that we use the .mjs extension for our ES modules. The latter would be an option for us in principle, but since it comes with rather harsh restrictions as well and Node.js's builtin ESM support is still subject to change, I have opted out of it completely for the time being.
Frankly, the experimental ESM support in Node.js is quite a pain at this time. I hope that they will make it much less intrusive in the future. See the official documentation and my mention of it in the article I wrote about the new modules feature.
There is good news, though: you can make it work without having to change your code. Just use the esm loader and everything will work fine. Pretend to Node.js that you're using CommonJS for best results (so use the .js extension instead of .mjs and don't use the --input-type flag).
By the way, as of version 1.11, each function can be imported from a separate module for better selectivity:
import without from 'underscore/modules/without.js';

I recommend using modular imports specifically to compose a custom Underscore-like interface, and using monolithic imports, from either standard Underscore or your own customized Underscore, everywhere else. The article discusses all the ins and outs of monolithic vs. modular imports and customization. I also wrote a TLDR version on Twitter.
I'll close this issue now, but questions and comments are still welcome.

Thanks for the offer of help, I think I've finally got things working again after refactoring code, so the esm package is doing the trick again. And also thank you for making underscore support esm imports in the first place!

Welcome again and glad to hear it's working now!