Load a number of components on a given path ?

Is there a way for me to load any given number of different components for a certain path?
Something in the lines of:
<Route name="Foo" path='/foo' handler={comp1 comp2 comp3}/>

Or should I always create Views with Components and then load the Views?
With Views it feels a little bit redundant sometimes. Aspecially if a certain Components moves to a different path - than I need to make the change also in the Views...
I guess Im looking both for a correct approach and a way to load multiple Comps.
Thanx!

Yes, in the 1.0 API (current master) you can specify an object of components to load.
<Route component={App}/>
  <Route ... components={{ header: Header, sidebar: Sidebar }}/>
</Route>

Then, in App#render use this.props.header/this.props.sidebar to access the element created using that component class.


[WFCORE-3834] Upgrade WildFly Discovery to 1.1.1.Final

https://issues.jboss.org/browse/WFCORE-3834

Merge after #3286


Chat could be a simple IRC server

Is your feature request related to a problem? Please describe.
I think having this as a simple IRC server also allows easy bot development in the future.
Describe the solution you'd like
Make an IRC server
Describe alternatives you've considered
Something like WebSockets is not that reliable for bots in my experience with another platform.
Additional context
I got this idea from Twitch, not only does it minimize the delay a bit but the IRC protocol itself is made for this.

I am going to close this issue as IRC is ran on WebSockets in most cases (like twitch [wss://irc-ws.chat.twitch.tv]).


Replace TransformerEncoder in torchtext with better transformer (#1700)

Summary:
X-link: https://github.com/pytorch/text/pull/1700
Replace the usage of TransformerEncoder by BetterTransformerEncoder
In theory we should be able to remove torchtext.TransformerEncoderLayer after this diff.
Reviewed By: parmeet
Differential Revision: D36084653

cc @ebsmothers


Account for fine components when integrating models

Fine components such as infinitely fine lines should be considered when the model is binned, before folding it in ARF & RMF

Fixed in #45, fine components are systematically computed within a bin for additive components


Cleaned Up VMCI sources to enable shared-lib

This patch cleans up the VMCI C-sources to enable the VMCI C client to be utilized as a shared library. Since it used to directly include C files instead of headers and lacked pragma directives, types were being declared multiple times and causing compiler errors when importing the Go package that links to this package.
I also fixed a bug in the esx_vmdkcmd.go file after speaking with @pdhamdhere. He noted that it was the intention to provide a sane default for the port instead of leaving it zero. I assigned it a default of 1019 since that is the default if the program is entered through its main file.

CC/ @govint @msterin

@shuklanirdesh82 - there is binary junk in test logs again. Can we *please get it fixed ? https://ci.vmware.run/vmware/docker-volume-vsphere/2324

You could consider doing what I do and defining the C sources along side the Go code so that the Go package is built statically with the C code and Go's own import logic worries about not importing things more than once.

I think there are not many reason to worry about shared libs if we only use it once and link statically, so the rearrangement seems good to me. (FWIW I think we did have C alongside GO code at some point but I moved it out to have more-or-less consistent dir structures with C code. Maybe it was not so wise)
BTW, the CI is failing in go unit test .... The PR does not seem to impact it but it was passing reliably so worth a look.

Hi @msterin,
I know the PR is failing the CI pipeline, and it was caused by me including the new vmci_client.h instead of vmci_client.c. I realized of course that fails because I'm not linking to an object with the implementations of the header's functions. That's when I realized the crux of the issue, that we either need to make the C code a shared lib or make sure it's statically linked exactly once. I will refactor the sources to achieve the latter as I do with my copies of them.

Hi,
I'm going to close this PR so as not to create countless builds while I work out the kinks in the refactor work I'm doing.


Issue with training

Hi!

I'm having this problem trainng LECO... any solution to this?
Thanks in advance

Obviously something is wrong with the version of xformers.
You need to verify the version of your cuda and Pytorch to check whether they are compatible with your current xformers.

Obviously something is wrong with the version of xformers.
You need to verify the version of your cuda and Pytorch to check whether they are compatible with your current xformers.
pip install torch torchvision --index-url https://download.pytorch.org/whl/YOUR_CUDA_VERSION

Obviously something is wrong with the version of xformers.
You need to verify the version of your cuda and Pytorch to check whether they are compatible with your current xformers.
In setup, you should try:
pip install torch torchvision --index-url https://download.pytorch.org/whl/YOUR_CUDA_VERSION


refactor(docker,ci): rename autoware-openadk to autoware and adkit to openadkit

Description
This PR is a subset of https://github.com/autowarefoundation/autoware/pull/4673
It renames autoware-openadk to autoware and adkit to openadkit.
Tests performed
https://github.com/autowarefoundation/autoware/actions/runs/9264954323
Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@youtalk @oguzkaganozt
these should be updated too:

https://github.com/autowarefoundation/autoware.universe/blob/7bebb1a69f6e703bdf04bad08e525487c0573a0a/.github/workflows/build-and-test.yaml#L24
https://github.com/autowarefoundation/autoware.universe/blob/7bebb1a69f6e703bdf04bad08e525487c0573a0a/.github/workflows/build-and-test-differential.yaml#L31

And their arm64 counterparts. Please keep in mind the universe CI heavily depends on these docker images.

Oh, good catch.
I've made the fix https://github.com/autowarefoundation/autoware.universe/pull/7179
I keep in mind from now on.


Update icon color, add empty view for facts, fix e2e tests

Description
added the empty view to the facts page, updated the color of the icons on the compile details page to match PF color scheme. I used the hex-code because the svg weren't working with the variables.
Also fixed the E2E tests in this branch.

Processing this pull request

Merged into branches iso7, master in 676156001eacd76eca627e45458f8d3daca33db1


TypeError: Cannot set property keys of # which has only a getter

npm install<EMAIL_ADDRESS>可以临时解决

npm install<EMAIL_ADDRESS>may be resolve your problem

npm install<EMAIL_ADDRESS>may be resolve your problem

https://github.com/koajs/koa/commit/287e589ac773d3738b2aa7d40e0b6d43dde5261b
fix了

when will the patch be released?


Run code freeze bots on pull requests made to release branches

This PR enables the Code Freeze bot on release branches such as v2023.01. A recent PMC conversation suggested that this would make sense to add.

@andrew-m-leonard / @steelhead31 for the release branch part. good to have it in before next release. and maybe document a bit

/thaw


promql: Refactor abstract syntax tree traversion

This PR adds a Childs() function to the AST Node interface. This makes traversing the syntax tree less complex and prevents code duplication.
Note that these changes are implemented on top of #6061, so it doesn't make sense to merge it until the other PR is merged. Also only the last three commits are actually new here.

Closed in favour of #6362


Pre-Translation volume is too large to process

I bought pro version and it works well last week. But today it shows me that. Please repair it.

This is open source bug tracker, not Pro support. Please use<EMAIL_ADDRESS>


As a developer I want to store SNARKs on disk rather than in memory.

This is a memory use optimisation also implemented in OCaml nodes: https://github.com/MinaProtocol/mina/blob/develop/rfcs/0063-reducing-daemon-memory-usage.md.
The idea is that a node needs to keep a lot of SNARK proofs, but accesses them rather infrequently. Because they tend to occupy a lot of space, it's better to keep them on disk to save RAM. Furthermore, the moment when they are needed (block production/application) is predictable, so we will be able to load them into memory in advance so that we're not losing time due to slower disk access.

I have created a separate SNARK-storage service on branch feat/snark-persistent-storage. It's a crude in-memory storage for the moment. I just need it in place so that I can integrate it with the rest of the system. It's isolated enough that moving the storage to the disk later won't be a problem, but first I want to get the interface right, which is the most challenging part.

Update: Still working on deduplication (so that each snark exists only once in memory and never verified again if it has been verified before). Once complete I will continue with moving them to persisted storage (filesystem and probably IndexedDB for the webnode).


when i add this on chrome. this err found

Manifest version 2 is deprecated, and support will be removed in 2023. See https://developer.chrome.com/blog/mv2-transition/ for more details.
{
"name": "WhatsAllApp Community Edition",
"version": "2.0",
"description": "UI overlay for WhatsApp Web to enumerate phone numbers, profile pics, online statuses and status texts.",
"permissions": ["declarativeContent", "activeTab", "storage"  ],
"background": {
"scripts": ["background.js"],
"persistent": false
},
"content_security_policy": "script-src 'self' 'unsafe-eval'; object-src 'self'",
"web_accessible_resources" : ["/bundle.js","note.mp3"],
"manifest_version": 2,
"page_action": {
"default_popup": "popup.html",
"default_icon": {
"16": "images/icon_16x.png",

Sorry, We no longer maintain this project


activitiesInterval parameter makes no difference on battery consumption

I've been testing ANDROID_ACTIVITY_PROVIDER changing the activitiesInterval parameter but it have not made great differences in the results of battery consumption.
Your Environment

Plugin version: 2.2.4

Platform: Android

OS version: 4.0.3

Device manufacturer and model: HUAWEI Ascend G 300 NFC

Cordova version: 6.3.1

Cordova platform version: 5.1.1

Plugin configuration options:
1:
{
desiredAccuracy: 10,
debug: false,
stopOnTerminate: true,
locationProvider: backgroundGeolocation.provider.ANDROID_ACTIVITY_PROVIDER,
interval: 30 * 60000, // poll for position every 30 minute
fastestInterval: 30 * 120000,
stopOnStillActivity: false
}
2:
{
desiredAccuracy: 10,
debug: false,
stopOnTerminate: true,
locationProvider: backgroundGeolocation.provider.ANDROID_ACTIVITY_PROVIDER,
interval: 30 * 60000, // poll for position every 30 minute
fastestInterval: 30 * 120000,
activitiesInterval: 10 * 60000,
stopOnStillActivity: false
}

Context

I've been getting the same results of battery consumption when activitiesInterval parameter is set than when is not set.
When it is not set by default takes the value of 10000?
Expected Behavior

Expect changing parameter (config 2) battery consumption would be lower, but what I have observed remain the same.

Doing a fast research on code I've seen this:
(ActivityRecognitionLocationProvider class)
private void attachRecorder() {
        if (googleApiClient == null) {
            connectToPlayAPI();
        } else if (googleApiClient.isConnected()) {
            if (isWatchingActivity) { return; }
            startTracking();
            if (config.getStopOnStillActivity()) {
                ActivityRecognition.ActivityRecognitionApi.requestActivityUpdates(
                    googleApiClient,
                    config.getActivitiesInterval(),
                    detectedActivitiesPI
                );
                isWatchingActivity = true;
            }
        } else {
            googleApiClient.connect();
        }
    }

Maybe, activitiesInterval only applies when stopOnStillActivity is true?

You can always check defaults here:
https://github.com/mauron85/cordova-plugin-background-geolocation/blob/master/android/plugin/src/main/java/com/marianhello/bgloc/Config.java#L49
And yes 10000 is the default value. Setting up proper value depends on your use case,  but 10000 is IMHO good default.

Maybe, activitiesInterval only applies when stopOnStillActivity is true?

yes,

My concern now is about battery drain.
On STILL status drain will be higher in stopOnStillActivity=TRUE than stopOnStillActivity=FALSE?
When device will be moving battery usage will be higher in stopOnStillActivity=FALSE than stopOnStillActivity=TRUE?
Thank you.


crashes with 10 or more png images

Hi,
the Debian packaged version of trimage has received a bug report.  If you try to compress 10 or more images Trimage crashes with this output:
 File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 286, in data
    data = self.imagelist[index.row()][index.column()]
  File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 340, in __getitem__
    return self.d[key](self.image)
  File "/usr/lib/python3/dist-packages/trimage/trimage.py", line 308, in <lambda>
    'filename_w_ext': lambda i: self.statusStr() % i.filename_w_ext,
TypeError: not all arguments converted during string formatting

Kind regards, Andreas.

I patched with that code on my Debian installation and works.


Wire up message logic + resolve outstanding //TODOs

[ ] Update new GAMM refactor messages

Waiting for the GAMM module to be published.


[QUESTION]: Titel Genre

Which tool
TIDAL downloader gui
Describe your question
Hallo,
steht gutes toll, warum werden die Titel Genres nicht heruntergeladen?
Add screenshots
No response

Can you elaborate? Maybe add screenshots with explanations?

Can you elaborate? Maybe add screenshots with explanations?

Genre field is empty. But I think that's because Tidal doesn't display the genre on the album page. I just run everything through a tagging program to sort out missing information.

@aric-ley thank you.
I checked, in their API Tidal does not return genre in the metadata.
Unfortunately, we should close this issue.


CM-22206 Add "auth check" command

rework of auth cmd planned in CM-22207

@MichalBor I start thinking about the move --output option to global space. It should be cycode --output json for example. Otherwise, the option position will be dynamic and depend on the command space. There is cycode scan --output. And in this PR cycode auth --output. What do you think?

@MichalBor I start thinking about the move --output option to global space. It should be cycode --output json for example. Otherwise, the option position will be dynamic and depend on the command space. There is cycode scan --output. And in this PR cycode auth --output. What do you think?

@MarshalX sounds good

@MichalBor the option was moved to the global space. I saved backward comparability with scan --output option too. The cyclient was refactored and all error handling happens in the base class. Also I migrate a few direct calls of "requests" lib to cyclient

force pushed. re sign commit due to manipulation from GitHub side


[BUG]: References across schemas does not include schema name in generated migrations

What version of drizzle-orm are you using?
0.23.10
Describe the Bug
When creating a reference to a table in a different schema the foreign key constraint generated in the migration does not include the custom schema name resulting in an error.
const authSchema = pgSchema("auth");
const publicSchema = pgSchema("public");

const users = authSchema.table("users", {
  id: uuid("id").primaryKey(),
});

const userProfiles = publicSchema.table("user_profiles", {
  id: uuid("id").defaultRandom().primaryKey(),
  userId: uuid("user_id").references(() => users.id),
});

results in the below foreign key constraint
DO $$ BEGIN
 ALTER TABLE "user_profiles" ADD CONSTRAINT "user_profiles_user_id_users_id_fk" FOREIGN KEY ("user_id") REFERENCES "users"("id") ON DELETE no action ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

adding the schema name "auth"."users"("id") allows the migration to run successfully.

This also happens when defining only a single pgSchema() attribute. Table creation works, but all ALTER TABLE statements are missing the schema reference.

Fixed in<EMAIL_ADDRESS>

Hello,
drizzle-kit: v0.19.12
drizzle-orm: v0.28.2
The bug seems to be back :(
With this schema:
const authSchema = pgSchema("auth")

const authUsers = authSchema.table("users", {
	id: uuid("id").primaryKey().notNull(),
})

export const users = pgTable("users", {
	id: uuid("id").primaryKey().notNull().references(() =>authUsers.id),
})

Generated SQL:
CREATE TABLE IF NOT EXISTS "users" (
	"id" uuid PRIMARY KEY NOT NULL
);
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "users" ADD CONSTRAINT "users_id_users_id_fk" FOREIGN KEY ("id") REFERENCES "users"("id") ON DELETE no action ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

@rphlmr, I now understand why you see an issue here. We have one final major issue with drizzle-kit in PostgreSQL only. If different schemas have tables with the same name, drizzle-kit will not function as expected. We are aware that this is the primary purpose of schemas in PostgreSQL. We will work on fixing it as soon as possible
For example, this one will work as expected
const authSchema = pgSchema("auth")

const authUsers = authSchema.table("auth_users", {
	id: uuid("id").primaryKey().notNull(),
})

export const users = pgTable("users", {
	id: uuid("id").primaryKey().notNull().references(() =>authUsers.id),
})

CREATE TABLE IF NOT EXISTS "users" (
	"id" uuid PRIMARY KEY NOT NULL
);
--> statement-breakpoint
DO $$ BEGIN
 ALTER TABLE "users" ADD CONSTRAINT "users_id_auth_users_id_fk" FOREIGN KEY ("id") REFERENCES "auth_users"("id") ON DELETE no action ON UPDATE no action;
EXCEPTION
 WHEN duplicate_object THEN null;
END $$;

drizzle-kit: v0.19.12
drizzle-orm: v0.28.2
const tableToNameWithSchema = statement.schema ? `"${statement.schema}"."${tableTo}"` : `"${tableTo}"`;
const alterStatement = `ALTER TABLE ${tableNameWithSchema} ADD CONSTRAINT "${name}" FOREIGN KEY (${fromColumnsString}) REFERENCES ${tableToNameWithSchema}(${toColumnsString})${onDeleteStatement}${onUpdateStatement}`

in my case, generates
ALTER TABLE "core"."login_log" ADD CONSTRAINT "login_log_app_site_id_app_site_id_fk" FOREIGN KEY ("app_site_id") REFERENCES "core"."app_site"("id") ON DELETE set null ON UPDATE cascade

which should be
REFERENCES "test"."app_site"("id")

since app_site is in test schema, not core.
seems like need a statement.toSchema to use in tableToNameWithSchema when it's different from statement.schema.
seems like the author's case would still be broken also, or at least any case where from table and to table are in schemas other than public.  and it's not because the tables are the same name, because mine are not.


Upgrade to .NET Core 3.0.0 Preview 6 - June 12, 2019

.NET Core 3.0.0 Preview 6 - June 12, 2019
AspNetCore feed
Still not supported in this release
Microsoft.AspNetCore.Mvc.Versioning, Version=<IP_ADDRESS> , ApplyAsync does not have an implementation in .NET Core 3.0 preview6-012264
[BUG] - AspNet Core 3.0 #499

https://github.com/kdcllc/Bet.AspNetCore/commit/180dbd661ae88f9e2d25617dfd3a6abb316beff5


Remove showModal, add receiptId to purchase handler

Hi @sthielen, while updating the package readme files, I found a few misc updates that affect the docs. Can you please review and let me know if changes are needed?

lgtm!


Bug 🐛: Favicon.ico update

WebMasterLog Repository (Proposing new issue)
:red_circle: Project Title :
:red_circle: Bug :
:red_circle: Category :
:red_circle: Changes :
Screenshots 📷

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
What is your participant role? (Mention the Open Source Program name. Eg. GSOC, GSSOC, SSOC, JWOC, etc.)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@RamakrushnaBiswal what's the logo are you considering?
And for further communication purpose, join the discord server.


Typo in step 4 under "Install the Azure Pipelines Agent Azure VM extension"

subacription should be subscription.

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

ID: 09fa0c14-9937-41bc-cc34-179edb379083
Version Independent ID: 10fe3600-21a5-12db-5e21-5ade3a8fa484
Content: How to provision agents for deployment groups - Azure Pipelines & TFS
Content Source: docs/pipelines/release/deployment-groups/howto-provision-deployment-group-agents.md
Product: devops
GitHub Login: @alexhomer1
Microsoft Alias: ahomer

Nevermind, already fixed in the source.

Thank you for your feedback. I will update the topic.


Meeting Summaries holiday

I'll be AFK for the IRC meetings of: 16/02, 23/02, 02/03, 09/03, 16/03 and 23/03.
It would be great if someone could take over writing the meeting summaries during those meetings.

I'm happy to do it.


Deluge API is temperamental resulting in incorrectly skipping incomplete torrent

Have you checked for any existing open/closed tickets that are the same or similar to your issue?

[X] I've searched far and wide!

I have gone to the Discord server for support and/or acknowledge that this is a bug and not a support issue

[X] I've tried to solve this already

What's happening surrounding the bug? (context)
When executing a search with cross-seed using deluge the logs are filled with warnings of skipping incomplete torrent despite these torrents being 100% downloaded and seeding.
This occurs for both v5.9.2 and v6.0.0-10.
Reproducing the bug
Following these steps to manually inspect the deluge API response with CURL
curl -d '{"method": "web.update_ui", "params": [["state", "progress", "save_path", "label"], {"hash": "**TORRENT HASH**"}], "id": 1}' -K curl.cfg | jq '.result.torrents'

Shows the  API  will occasionally response with state and progress omitted.
{
  "**TORRENT HASH**": {
    "save_path": "**PATH**",
    "label": "**LABEL**"
  }
}

Repeating the request will eventually respond:
{
  "**TORRENT HASH**": {
    "save_path": "**PATH**",
    "label": "**LABEL**",
    "state": "Seeding",
    "progress": 100
  }
}

As these fields are absent this causes cross-seed to assume the torrent is incomplete.
https://github.com/cross-seed/cross-seed/blob/0ab8741a5fdbab23db8c743d6ba8a6152ae2c460/src/clients/Deluge.ts#L470-L471
What should be happening?
I would suggest that if those fields are absent from the response then cross-seed could attempt to retry the API request a few times, if still no luck then it should report "unable to torrent status" or similar which would be more accurate than incorrectly warning skipping incomplete torrent
Your setup
- OS: Ubuntu 20.04 LTS
- Docker: Yes (ghcr.io/cross-seed/cross-seed:master)
- Deluge: v2.1.1 https://fleet.linuxserver.io/image?name=linuxserver/deluge

config.js (REDACT SENSITIVE INFORMATION)
N/A
verbose logs
No additional verbose logs other than repetitions of:
2024-06-10 14:25:08 warn: Found TORRENT NAME [HASH...] on TRACKER by MATCH from torrentDir (NAME [HASH...]) - skipping incomplete torrent
Failure or refusal to provide the information we require to address bugs will result in potential closure of the issue.

[X] I acknowledge that i have searched existing issues, read the documentation and faq, read the logs to see if the answer was provided in error messaging, and attempted to get support via the Discord prior to submitting this issue.

This is a known issue I have faced with docker containers, particularly with large amounts of torrents. I've looked into it a fair amount and discussed with one of the active developers on Deluge's team (I am a moderator on their support forums and wrote the Deluge integration in cross-seed).
The solution I've come up with is that you can disconnect the web daemon (it is an entirely separate process and appears to be getting desync'd somehow) from the RPC daemon, and reconnect it and the instance will act normally for some time.
I, myself, have a script scheduled to disconnect and reconnect the web daemon every couple of days. This usually is only a problem with older torrents, so if you're doing a full search or something you may run into it. I haven't seen it crop up many times during completion script calls.
It does seem to only affect containers, though, given that they have separate web and daemon processes.

 [

We use update_ui with specified keys, so it only returns exactly what we need. If you do not specify keys, it returns everything.

My current thought is that if the keys are missing from the response, I could reconnect the web daemon and retry...however I'm not sure how this interaction could possibly backfire.
My initial concern would be in the rare case that there are multiple instances in the web daemon config, although this would be extremely rare and I doubt would ever actual cause problems. Currently on startup, if the web daemon is disconnected from the deluge daemon, it will automatically connect it to the first entry, which is going to be the only one in 99.9999% of cases.
@mmgoodnow might have some thoughts on this, as I've discussed this issue with him previously.

Can we just get the root cause issue fixed?

Cas isn't really that active for personal reasons. He currently devotes only a day or two per month to actual development on Deluge. The other dev, who I've spoken about this with wasn't really sure where the problem was sourced from, but I was able to determine that it seems to be present only where the web daemon and client daemon are separated, although I can't be sure this is the case, I've never seen it in standalone mode where the two are combined.
I can only speculate since my architectural knowledge outside of the API itself is somewhat limited. I've already messaged one of the devs with this issue link, although I'm not entirely sure how quickly it would get to stable either way.
It is not a cross-seed issue, as I said this presents itself in the webui itself as well as occasionally in the thin client. You will see NaN% or blank names.
I'm convinced it has something to do with deluge's caching of the torrent list, but I have only speculation to base this off.

To clarify, I've only ever seen this in Docker implementations. Both binhex and lsio containers are affected, as well as my personal develop branch container I maintain.
Docker is generally the most common implementation of the processes being ran seperately.

@zakary do you know where the code lives for the web daemon and client daemon? I could poke through the code and see if I can find anything.
Would it be possible to write a docker image that runs them together rather than separate?

Repeating the request will eventually respond:

How many times would you expect to need to repeat this request before the problem appears, I only ever encountered it "by chance" and I may have a solution - but finding this "in the wild" is not ideal.
If you could give me like, an interval and number of times repeated before you reliably saw SOME problem, that would be helpful.

I may have a better solution, but I need the information about timeframes to replicate....right now I'm just sitting here waiting to see if it happens with my scripts turned off.
I'd rather find a valid solution than a workaround, but if this doesn't work that may be how we go.
Yes there is a way to see which host it is connected to.

I just did the curl with no hash key, its been ~18hr since I switched to what I think may fix the issue.
I haven't approached binhex or any lsio maintainers about this yet, I don't think it's particularly ideal of a solution for them, but it may be the solution that's necessary.
If you'd like to also try this to double our reproduction surface, feel free to hop on the discord and I can explain it to you, my name is zakary in our server.
If you don't have discord I can at some point today write out some basic instructions. I think based on our conversation here you'd be able to get it working in the same manner I am testing fairly easily.
Either way, I'll continue to monitor what I'm trying right now.

Also of note, with the connection (session_id) connected, you should not use the same id value repeatedly.
It does not have to be incremental, and it does not have to be anything particular, just a number and different.

After you login, you can use the following command to see if any of the state or progress values are missing from your entire list.
curl -d '{"method": "web.update_ui", "params": [["state", "progress", "save_path", "label", "name", "total_remaining"], {}], "id": 3}' -K curl.cfg | jq '.result.torrents | to_entries | map(select(.value.state == null or .value.progress == null)) | from_entries'

add an or .value.whatever == null as you desire to find other missing values.
I've opened a PR to maybe "help" with the issue, although depending on what I've dubbed a desynchronization it may not entirely fix the problem. So far I've not found an issue - going on 24hr.

Just a note, this commit in the latest pre-release has the potential to help, although doubt it will 100% eliminate the possibility by itself.

It has to do with the container itself and Deluge and the WebUI - the commit I made is sort of an attempt to improve the situation as best I can in the interim.
Something I've found over the last 8 or so months I've been aware of this is that it tended to be older torrents that got less traffic, and thus received fewer torrents_status_update() calls....repeatedly hitting it with requests is going to do nothing but prolong the time it takes to reproduce - if it even will (just my experience though, yours may differ).
I tend to check every 3-6 hours right now. I'll probably extend that to every 8-12 if it doesn't happen within a day or two now.
Restarting the container and reconnecting the webUI to the daemon also "resets" (only term I know for this) the process....so don't do those either if you're trying to replicate it.
If you use IRC, I'm also on frequently and can meet you on a neutral server like freenode or efnet or something.

I'm curious if that could indeed be the case, in which case I do how a solution could be implemented...however I'm not entirely sure this solves it as I also have a script that sorts my labels and pulls the entire list every 15m.
I've never just run them independently without the other (my disconnecting/reconnecting script) - so I'm not sure if one or the other independently solves this.
I'm still exploring this, but if this is a "solution" of sorts - then that would be good.

So I've concluded that running the webui plugin as opposed to the web daemon itself (separate deluge-web process) or the fact that I'm pulling the entire torrent list somewhat regularly (every 15-30m for a script) - prevents this.
I have not been able to once replicate this yet during my testing the last ~10 days, and I'm not sure which solved it or if its just being temperamental about being temperamental.
I'm tempted see switch back to the web daemon and see if it presents itself.
Any update on your end?

I restarted the VM and deluge container about 10 hours ago and now I have a large number of torrents - 30% - in a state of desync. The web.update_ui request for these torrents doesn't have the state or progress keys but it does have "total_remaining": 0 so #715 probably does fix the issue.

Yep, looks about right for what ive seen. Also seen name go missing, as well as label.
Would you be able to get deluge to use the webui plugin instead of the daemon and test if this persists?

Well if checking a box in a client and fixing all your problems isn't stable enough I'm not sure what is... Mine's been running 11d with no sign of a problem.
Up to you though.
Running deluge-web separately from the main deluge core daemon is a bit of a docker-specific implementation. I'm not sure why it was chosen as such for the containers, but there isn't any real reason I'm aware of to do this specifically over the plugin, and no drawbacks to switching to one over the other functionally.


NIFI-8124 Added cookie redirect handling to InvokeHTTP

Description of PR
NIFI-8124 Adds support for persistent cookies within the InvokeHTTP processor. Previously, cookies weren't being carried over during redirects. This addition adds a new property "Enable Cookie Redirects", which will create a persistent cookie jar file that will properly handle cookies during HTTP redirects. By default, this is set to false, which will produce the current behavior of the processor.
See https://issues.apache.org/jira/browse/NIFI-8124
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[x] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

Thanks for adjusting the property naming and approach @marcus41495, I will take a closer look at the changes soon.


Stats API bug fix

Description
The stats API broadcasts requests to all nodes and renders node responses using toXContent. For the local node, the stats API's calls toXContent on the node response directly. For remote node, the coordinating node gets a serialized content from
ADStatsNodeResponse.writeTo, deserializes the content and renders the result using toXContent. ADStatsNodeResponse.writeTo uses StreamOutput::writeGenericValue that only recognizes built-in types (e.g., String or primitive types). It throws exceptions for types such as java.time.Instant and Entity. This PR fixes the bug by converting non-built-in types to built-in types in node stats response.
This PR also removes model id from Entity.toString as it is random across different runs and keeps only attributes.  This can help locate the same node in hash ring.
This PR also removes unused fields in ADStats.
Testing done:

Verified stats API response on a multi-node cluster for a multiple-category field detector.
Added unit tests.

Issues Resolved
https://github.com/opensearch-project/anomaly-detection/issues/87
Check List

[ X ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

LGTM - can you confirm the issue with ADStatsNodeResponse.writeTo is limited to responses from the stats API? No other responses have risk of returning non-built-in types?

confirmed this is the only place using StreamOutput::writeGenericValue.


File size limit increase for bagpipes

I'd like to distribute a piece of astronomical software through PyPI, but it includes a large data table which is > 60MB, would it be possible to get the size limit for this project increased?
The name of the project: bagpipes
The size of your release, in megabytes: 210
Which index/indexes you need the increase for: PyPI

Hi @ACCarnall, I've increased the limit for bagpipes to 250MB on PyPI.
This is on the larger side as far as packages go, so please be mindful of how often you make a new release.


Add SSH agents for Cloudbees connection timeout bug

Adds an SSH viable Dockerfile for persistent (non-ephemeral) agents.

Usurped by subsequent PR


6581 remove dummy services

longhorn/longhorn#6581
We used to deploy the CSI components in StatefulSets, which require a service (even though in our case the service was nonfunctional). Since we are now using Deployments, do not deploy dummy services and clean up the dummy services that exist.
I thought about handling the cleanup of erroneous services in the driver deployer instead, but it's cleaner to remove all references from csi package in this PR and delete the services one time while walking the upgrade path.
There are some reports of these services not cleaning up nicely during driver upgrades in the issues linked to longhorn/longhorn#6581. Since the services are completely nonfunctional, I wrote the upgrade path to do a best effort background deletion.


NOT_FOUND Error thrown by default

What version of Elysia.JS is running?
0.8.17 and tested on 1.0.0-rc.16
What platform is your computer?
m1 mac
What steps can reproduce the bug?
use  elysia.onError(({code, error})=>{     console.log(error) });
What is the expected behavior?
The expected behaviour is by default, Elysia shouldn't throw random errors
What do you see instead?

Additional information
No response

The error was caught for
http://localhost:3000/favicon.ico

The error was caught for http://localhost:3000/favicon.ico

Where must favicon.ico be placed to get rid of this error?


Update Type definitions to with getPopupContainer

TimePicker takes a getPopupContainer which is passed directly through to Trigger from rc-trigger.
This change copies the type definition from Trigger.getPopupContainer to TimePicker.

Any idea when this will get merged?


errors and warnings

where should we put this topic

I feel like this one can be dispersed throughout, showing common errors on purpose that we see in practice. The general idea of Googling error messages has some value but I'm not sure how best to tackle this other than showing examples.

I have a whole section on how to deal with errors as a novice in my material in session 2, and I’ve gotten very positive feedback from participants. I would suggest you and Joe look at that and cannibalize most or all of it. :)
Sent from my iPhone

On Apr 24, 2019, at 2:22 AM, Patrick Mathias<EMAIL_ADDRESS>wrote:
I feel like this one can be dispersed throughout, showing common errors on purpose that we see in practice. The general idea of Googling error messages has some value but I'm not sure how best to tackle this other than showing examples.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Support GraalVM 21.0.2

GraalVM JIT Compiler 21.0.2 changes the compiler interface for some of the IR nodes:
This feature should update the compiler with the latest version.
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project tornado-drivers-common: Compilation failure: Compilation failure:

[ERROR] C:\dev\TornadoVM\tornado-drivers\drivers-common\src\main\java\uk\ac\manchester\tornado\drivers\common\compiler\phases\guards\ExceptionSuppression.java:[63,22] error: cannot find symbol
[ERROR] symbol: method getAnchoredNode()
[ERROR] location: variable anchor of type ValueAnchorNode
[ERROR] C:\dev\TornadoVM\tornado-drivers\drivers-common\src\main\java\uk\ac\manchester\tornado\drivers\common\compiler\phases\guards\ExceptionSuppression.java:[66,22] error: cannot find symbol
[ERROR] symbol: method removeAnchoredNode()
[ERROR] location: variable anchor of type ValueAnchorNode
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :tornado-drivers-common
Error running 'mvn clean': Command '['mvn', '-T1.5C', '-Dcmake.root.dir=$CMAKE_ROOT', '-Pgraal-jdk-21,ptx-backend,opencl-backend', 'install']' returned non-zero exit status 1.
Traceback (most recent call last):
File "/c/dev/TornadoVM/bin/compile", line 373, in
main()
File "/c/dev/TornadoVM/bin/compile", line 365, in main
mvn_build_result = build_tornadovm(args, backend_profiles)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/c/dev/TornadoVM/bin/compile", line 264, in build_tornadovm
return result
^^^^^^
UnboundLocalError: cannot access local variable 'result' where it is not associated with a value
make: *** [Makefile:15: graal-jdk-21] Error 1

There are some changes with the GraalVM-21.0.2: https://github.com/beehive-lab/TornadoVM/pull/337
The above-mentioned PR solves the issue if you want to use GraalVM-21.0.2.


Some code to fix https://github.com/shahen94/react-native-video-processing/issues/215

Some code to fix https://github.com/shahen94/react-native-video-processing/issues/215

How this PR fixes the issue?

How this PR fixes the issue?

These modifications fix the dependency when they are used with React hooks.
To set any value in hooks, use the prefix "setVariableName" for example.

Perfect!
Thanks for the PR, merging now.


Add modulo to equal_up_to_global_phase

Resolves Issue: https://github.com/quantumlib/Cirq/issues/5980
Adds a modulo operator to the _equal_up_to_global_phase_ function

https://colab.research.google.com/github/quantumlib/Cirq/blob/master/docs/start/start.ipynb#scrollTo=ZslMfLkHrUeS


Get this Error, but still can't see any parse data on heroku?

Parse Server deploy Heroku
2016-04-16 18:24:51.824 ParseStarterProject-Swift[37025:10606060] [Error]: {"code":1,"message":"Internal server error."} (Code: 1, Version: 1.12.0)
Object has been saved.
Help thanks: what to do?

Start again & follow this: https://www.youtube.com/watch?v=Cp3VRKrnZ2o
Sounds like you're missing something somewhere.  You might want to also follow the same guys guide for installing the Parse Dashboard.

nexslab, did you every fix this issue? if so how?

Hi Dameon, i figured out how to fix that problem.You'll need to to create another entry in your heroku settings : add a new key call DATABASE_URI --> and the value should be the same as your MONGODB_URI  save and compile your Xcode project it should work after this if not let me know.

Hi, nexslab, I REALLY appreciate your assistance. I'm up and running now.
Thanks

@nexslab The MONGO_URI key worked for me to fix the problem. Thanks!

@nexslab you are simply amazing. How did you figure this out? Saved my day man. Thanks a lot!


Fix for Android NDK r11c

Seems like RELEASE.TXT is gone, so arch is now used to determine if we're running on 64bit or not. I'm unsure how to properly check for this on Windows, though.

Awesome, thanks!!

:beers:


set loop and autoplay，navigation is not work

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/p/sandbox/swiper-infinite-loop-forked-gtlh4m?file=%2Findex.html%3A98%2C8-101%2C14
Bug description
set loop and autoplay，navigation is not work
Expected Behavior
I want autopaly with loop and navigation work together
Actual Behavior
set loop and autoplay，navigation is not work
Swiper version
11.1.15
Platform/Target and Browser Versions
Google Chrome 131.0.6778.86
Validations

[x] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a Swiper issue and not a framework-specific issue

Would you like to open a PR for this bug?

[X] I'm willing to open a PR

I have the same problem,Did you solve it?


DISTX-533 Set S3A buffer dir to Yarn local dir

DISTX-533
An escalation ENGESC-3559 identified the problem where spark applications were filling up local disks.
The solution provided was to set fs.s3a.buffer.dir config to YARN local dir so that when spark job finishes YARN can clean those up. But if YARN LOCAL_DIRS is not set then it should fallback to something like /tmp/s3a, hence configuring following in 722, 726, 727 data engineering templates
fs.s3a.buffer.dir=${env.LOCAL_DIRS:-${hadoop.tmp.dir}}/s3a
Testing done:
Have created a DE cluster using a modified 7.2.6 template that includes above mentioned config changes. Cluster creation was successful on AWS using m5d.2xl instance types.

@shwethags @sidseth Can one of you pls approve this?

+1 from me. FWIW been considering making this the default in hadoop common


Moving cdn(13) resources to v1beta1 version

cdn 13

[x]  azurerm_cdn_frontdoor_custom_domain
[ ]  azurerm_cdn_frontdoor_custom_domain_association
[x]  azurerm_cdn_frontdoor_endpoint
[ ]  azurerm_cdn_frontdoor_firewall_policy
[x]  azurerm_cdn_frontdoor_origin
[x]  azurerm_cdn_frontdoor_origin_group
[x]  azurerm_cdn_frontdoor_profile
[ ]  azurerm_cdn_frontdoor_route
[ ]  azurerm_cdn_frontdoor_route_disable_link_to_default_domain
[x]  azurerm_cdn_frontdoor_rule
[x]  azurerm_cdn_frontdoor_rule_set
[ ]  azurerm_cdn_frontdoor_secret
[ ]  azurerm_cdn_frontdoor_security_policy

Deprecated, will be removed from ticket:  [ ]  azurerm_cdn_frontdoor_route_disable_link_to_default_domain


[Feature Request] Pass a model to the Classic and Pro API request methods as the return type.

Proposal
When using the classic_api_request and pro_api_request methods on the client directly users have to take the response and cast it to an SDK model themselves.
resp = jamf_client.classic_api_request(
    method="get",
    resource_path=f"computergroups/name/{group_name}"
)
group = ClassicComputerGroup(**resp.json()["computer_group"])

Both methods should optionally accept an SDK model as an optional response type. When set, the requests response object is not returned, but the method attempts to instantiate the provided model from the data.
group = jamf_client.classic_api_request(
    method="get",
    resource_path=f"computergroups/name/{group_name}",
    return_model=ClassicComputerGroup
)

Makes sense.  Would also be nice to make use of Generic/TypeVar in a few choice places (e.g., Page, Pagination).


Would you take a contribution of telnet access for a CN-1800S

The BB-RS232 module is getting hard to find and very expensive. I tried an experiment where I used a generic Serial to Ethernet server and was able to communicate with a CN-1800S over the serial port. The spec document lists the commands available. Looking at the code the Panamax M4000 support added is essentially what is necessary to communicate using the above Serial to Ethernet server (I've done tests locally to control the device using a telnet connection).
I'd be willing to contribute the changes to support the above configuration, if that is acceptable.

That would be great! I've actually been watching EBay pretty closely to try to find one, so glad to know there's a replacement.
Feel free to start a PR! I can help with whatever you need

Have you looked into the generic-tcp-serial module built into companion? It creates internal TCP server bridge attached to a local USB Serial adapter.

I was trying to avoid a direct serial connection to the device and use a separate Ethernet converter. I had no idea that module existed. I may try to use it to verify functionality.


add warning to confounds description page

if i'm already using aroma cleaned data, it does not make sense to further regress the aroma regressors.
also it may not make sense to use global signal regression and a/t compcor
if i'm doing my own high pass filtering, using the cosine filters could interfere

since it's so easy to add the entire confounds.tsv to a feat or other analysis, it may be useful to add a warning that people should selectively add confounds relevant to their specific analysis.

We should add this to documentation. Maybe in red.

Per the AROMA paper, WM and CSF confounds were regressed after AROMA. How does one do this with fMRIprep? I'm presuming we'll have to extract new timecourses using WM and CSF masks from the AROMA residual nii.gz?

We validated ICA-AROMA by applying it to rfMRI and stop-signal task fMRI data (SST-fMRI). We compared results obtained with ICA-AROMA to two commonly applied motion correction strategies: extensive nuisance regression including 24 RPs, and spike regression. All three preprocessing strategies were complemented by standard nuisance regression including time-series for WM and CSF signal as well as a linear trend to remove residual (non-motion related) structured noise.

Therefore, motion artifacts are preferably removed prior to temporal filtering. To accommodate this, we designed ICA-AROMA to be applied prior to temporal filtering. Moreover, applying secondary motion artifact removal prior to temporal filtering not only prevents ringing artifacts but additionally prevents removal of low-frequency motion-related signal variance which can aid in identification of motion artifacts. Similarly, as signal from WM and CSF time- series might also contain variance related to motion artifacts, we applied ICA-AROMA prior to nuisance regression. Additionally, we applied ICA-AROMA after spatial smoothing. Spatial smoothing will blur motion-related artifacts to neighboring voxels. Yet, as spatial smoothing will increase signal to noise ratio by reducing speckled noise, it will increase the ability of ICA to detect coherent signal patterns, including better separation of structured artifacts. Note that we did not include slice-timing correction in our preprocessing pipeline. Although slice-timing correction might interact with motion-induced artifacts, it is not expected to substantially alter the characteristics of the motion components and therefore impact the ICA-AROMA classification accuracy.

It should be noted that ICA-AROMA is specifically designed and validated with respect to removal of motion-related artifacts. Accordingly, we advise to check your data for any remaining structured artifacts and remove residual structured noise after application of ICA-AROMA. We implemented the removal of residual noise by means of WM and CSF regression. Note that to prevent the risk of removing signal of interest due to spatial smoothing or inaccurate WM and CSF masks, a conservative approach is advisable. Here, we extracted mean WM and CSF signals using masks obtained by multiplying a participant-specific tissue prior with an MNI152-derived tissue prior, both thresholded at a very conservative threshold of 95% tissue probability.

this may help: http://fmriprep.readthedocs.io/en/latest/outputs.html#confounds
but yes, you will need to separately select the useful confounds and regress these out.

This issue/question though, is that the columns in confounds.tsv represent the timecourses extracted from the data PRIOR to AROMA.
So should we 're-extract' timecourses after AROMA using the same ROIs from the AROMA residual?
per #817 and #959
(trying to come up with an ad-hoc solution in the meantime to understand our data.)

ah yes! this would also require transforming the csf/wm masks (*T1w_dtissue.nii.gz) to mni space, since aroma, at present, generates everything in that space. or transforming the mni output of icaaroma to individual space.
@oesteban - it may be useful to add post-aroma operations to generate additional confounds.

What all confounds should be recomputed? Global, WM and CSF signals would be easy. FD and motion parameters don't make much sense, as motion will not be re-computed. I'm not sure about DVARS, aCompCor or tCompCor.

Global, WM and CSF signals would be easy. FD and motion parameters don't make much sense, as motion will not be re-computed.
+1

I'm not sure about DVARS, aCompCor or tCompCor.

i think those would all change post aroma.

I agree they'd change, but would they be sensible to use post-AROMA?
Also, what should we call the recomputed columns? <confound>_variant-AROMA? Or just <confound>_AROMA? Other ideas?

@alexlicohen The paper only clearly states when the regression was performed, but not at which stage the signals were extracted. Would be good to clarify with authors: @maartenmennes in the pipeline from the ICA-AROMA paper did you extract WM and CSF signals prior or post non-aggressive denoising?
@effigies Why not stick to CamelCase to keep names consistent? WhiteMatterPostAROMA?
Finally I just thought about one more approach that @alexlicohen might want to try: orthogonalizing WM and CSF regressor against the noise ICA AROMA regressors already present in the confounds file.
As a side note I have an impression that we are splitting hairs here and there is no clear answer how much the order of signal extraction steps influences the result and which order is the best one (+1 to what @satra said).

To me, this is largely trying to avoid the "I'm doing the analysis a second way to address the concerns of Reviewer 2" problem...

@effigies Why not stick to CamelCase to keep names consistent? WhiteMatterPostAROMA?

I was thinking of it from a FitLins perspective, such that if people pass in --variant=AROMA (or whatever we're calling the variant), to adjust CSF to CSV_variant-AROMA automatically, but the exact indicator doesn't need to match that on the filename.
So anyway, whatever people decide on is fine with me. From the perspective of the functional derivatives spec, we should discuss this case and, settling on some spec-endorsed separator <sep> (e.g. "Post"), define <confound><sep><method> as a variant of <confound> calculated after <method> was applied to the original data. Then we should have a table of <method>s that might be used (I assume AROMA isn't the only one), and it would probably be worth noting which confounds make sense to calculate and apply post-<method>, so that downstream projects can have an expectation of what to look for.

If I interpret correctly, we also need to apply ICA-AROMA on the original time-series without motion correction, is that correct? @alexlicohen @satra

no, they ran MELODIC after motion correction, intensity normalization, and 6mm FWHM smoothing. (no slice timing, but I would not advocate getting rid of it in fmriprep of course).
ICA-AROMA takes the place of regressing out the motion parameters, be they 6, 9, 12, 24, or 72:

We defined a 72RP model, including the standard 24RP model (6 standard RPs, their derivatives, and the quadratic terms of these 12 RPs), as well as a single time-point backward and a forward shifted version of the 24RP model to reflect possible non-linear effects.

they ran MELODIC after motion correction

Okay, cool. Otherwise we could feed AROMA directly with motion-UNcorrected images and then apply motion correction on the AROMA-denoised outputs

Aloha, two points:

yes, any further variable you want to regress out is taken from the data after AROMA denoising. Obviously, if you want to include WM, CSF regression together WITH the regression of the AROMA identified components, you would extract these regressors from the preprocessing step just before doing that regression. In that sense, we assigned priority to regressing out motion-related components before regressing out other noise. (which relates to the whole discussion about aggressive vs. non-aggressive denoising)

the 6mm smoothing kernel is a bit unfortunately displayed in the paper. We should have left the exact kernel out of that figure. For the data in the manuscript (3.5mm isotropic), we used 6mm smoothing, which comes from ceil(1.5 * the voxelsize), which is what we typically use as our smoothing kernel. So for 3mm data, we'd use 5mm.

third minor point: under the KISS principle I would advocate getting rid of slice timing correction (we never apply that in our preprocessing). But that is a whole other discussion... :-)


Unecessary permlink suffix?

I've posted an article and the permalink got a random suffix @steemscript/steemconnect-3-a-better-way-to-sign-63826a07f8f44est (see the -63826a07f8f44est) The post has been published from a draft. It would be cooler if Surfer don't add this extra chars on the end of the title.

Thanks, this is to keep randomness on permlink as well as helps our curators to detect the links. Medium.com uses similar approach...
Do you think it is discouraging you from sharing a link or makes url not attractive?

Yeah the url look less attractive, Medium does not seem to care much about the first part of the permlink for example this https://medium.com/byteball/b35964feee8e redirect to https://medium.com/byteball/bringing-identity-to-crypto-b35964feee8e perhaps i would prefer a url like @steemscript/63826a07f8f44est

fixed with latest release 2.0.1


Address data for Biella (Italy)

Adding/Updating it-lo-biella.json

In this case I need assistance, on the shapefile there's the address number (CIVICO), and the way is described by its ID. The way name is in the CSV file, so it would need a join between the DBF and the CSV.

Hey @sabas. By "way" I assume you're talking about the street name.  The current processing pipeline is not able to perform table joins.  But if you're able to join the address names to the shapefile we could host the data.  If not, you could provide a link to the csv here in case someone else wanted to tackle it.

Yes, I can do it, the csv is inside the zip file.. You'd need to point at a fixed host or I can upload it somewhere?

@sabas If you host it somewhere like a Dropbox account and provide the link the maintainers can pull it into the Amazon S3 bucket.

@geobrando here it is
http://toolserver.openstreetmap.it/openaddresses/biella_joined.zip
I made a field NOME_VIA with the street name (CIVICO has the housenumber)

@sabas Great. Could you update the street field with the new name?
Would someone with credentials to the S3 like to take this and update the data field with the new path? You could also take care of #263 while you're at it.  @kelvinabrokwa @ingalls @sbma44

Done!

Here's the URL:
http://data.openaddresses.io.s3.amazonaws.com/cache/it-lo-biella.zip

I made it look like the polish file

:+1:!

Still not sure that's correct but we should just accept this.   Thanks @sabas


adding payment system when brands submit post collab form in their profile Added

Description:
razor pay payment integration for brand collab open post
Issue
Issue Link resolve #257

@Kajol-Kumari  @RohitGupta1237 can you please check.


Potential issues from parent.timestamp == block.timestamp

With the current protocol implementation, if two L2 blocks are proposed within the same L1 block, these L2 blocks will have the same return value for block.timestamp, which is not the case in Ethereum's client spec.  However, we do not think this is an issue at all or it will have any impact to developer experience.
Taiko's developer documentation does need to mention this explicitly.

We have an internal document to keep trace of the differences between Ethereum and Taiko -- it will be made into a document later on. This very difference is covered there.


How to run Linux shell command using webSocket?

WebSocket app which runs Linux command on a dedicated server/cloud.
For eg., logging into the app should run a command on Linux server.
Thanks.

Look for these things online.


ServiceBus - Service side connection idle timeout is not surfaced, and can be compromised with improper values of autorenewer renew_period

Package Name:
azure-servicebus
Package Version:
0.50.3 (Same issue will occur in 7.0.* as well)
Operating System:
All
Python Version:
All

Describe the bug
The ServiceBus Service has a connection idle_timeout of 240000 ms (4 minutes).  Not only is this unclear to users, but if renew_period for autolockrenewal is set to >4 minutes, (when max lock duration is theoretically 5 minutes) the connection will time out silently.
To Reproduce
Steps to reproduce the behavior:

Create a queue with lock duration of >4 minutes.
Send and receive a message, attaching an autolockrenewer with a period >4 minutes.
Observe that the message is now unable to be completed due to lock expiry.  With all logging on, observe "the connection was inactive for more than the allowed 240000 milliseconds"

Expected behavior
There are a few options here of varying rigidity.

Disallow improperly large renew_period.
Warning/better docstring on renew period
"secretly" run our own keepalive in the 4 minute interval if a large renew period is specified. (should this be a function of the receiver potentially flag-enabled?  I'm spitballing.)
Document this in our README (we should do this anyway)
Potentially coupled with any of the above strategies, find a more immediate way to surface connection idle expiry. (@annatisch I hate that I keep finding myself saying "I wish we had an on error handler"; although this could be an issue with pull mode as well.  Consider this a note to see how/if the other languages addressed this issue)

Additional context
Initially noted with the user in this thread
A final note I'd append here:  We noticed very odd symptoms when trying to use a 5 minute service side lock_duration, wherein the expires_at time on the message would appear to be >5 minutes in the future, resulting in guaranteed lock renewal failures if you trusted it.  This should be investigated in parallel with the core issue to see if we're just dealing with clock skew, or if there's actually some odd edge case there.

This should be largely mitigated per #12307 , which among other things makes renew_period internal as it should not need to be adjusted for proper functionality, and adjustment only opens room for pitfalls as described.
This notably also adds on-failure callback capabilities to better alert if a lock renewal failure DOES occur nonetheless, as another component of the exchange that spawned this issue initially.
The 5 minute lock duration issues remain to be investigated, after which this can be closed.

bumping to September sprint, PR is out for keeping connection alive to mitigate the problem

closing this issue as the PR for keeping connection alive is merged.


Mof file parsing

Implementation of some kind of parsing of mof files, as the basis for compatibility with current DSC for Window Powershell.
It should return a PsCustomObject with the necessary information and structure to be used by the agent itself. Using a standard internal structure should be the best idea, since it would allow future parsers for other formats.

Implemented by #6.


Add LibreSSL to TravisCI build

Currently, we only build s2n with Openssl's libcrypto in TravisCI: https://github.com/awslabs/s2n/blob/master/.travis/install_openssl.sh#L33 . If we're going to advertise support for other major libcrypto's, we should include them in our builds.

The steps needed to build with LibreSSL are already documented in https://github.com/awslabs/s2n/blob/master/docs/USAGE-GUIDE.md . We just need to add those steps in the Docs to a .travis/install_libressl.sh that builds and installs LibreSSL in the same place as .travis/install_openssl_*.sh and add it to the .travis.yml file.

#410 should make this change easier. We can build/cache libressl and set LIBCRYPTO_ROOT as needed.


tag-autocomplete suggests tags for deleted files (to verify)

So one user on discord had this situation where they deleted all wildcards and started chiselling their own. Valid use case. They complained that tag-autocomplete still suggested old tags to them. Not sure if that's the case. I think the index of tags is built on each web-ui start in the install extension step. Not sure now and too tired to check.
ToDo later.

I will likely be removing all the preview images in the Umi 2.0 update. That will take a while, but not TOO long. Less than a month from now I bet.
It should also fix all the existing issues Umi AI has.


Wellness Wave Navigation

When the user clicks on Wellness Wave in the navbar, he/she must be directed to the home (index) page.
Correct this navigation in all the existing pages.

Assign me under JWOC 2024

kindly assign this issue under jwoc @ritika728

Assign  me under JWOC
@ritika728  Sorry for this issue navbar is created by me
but i feel and many of this website use this technique to move home page as logo in navbar


OK, no process is listing/bound to port 8888
Starting daemon pigpiod ...
2023-11-26 15:00:42 initCheckPermitted:
+---------------------------------------------------------+
|Sorry, you don't have permission to run this program.    |
|Try running as root, e.g. precede the command with sudo. |
+---------------------------------------------------------+

Can't initialise pigpio library
... daemon stopped unexpectedly.
netstat -tlep | grep 8888
sleeping for 20 sec - we hope that this releases the bound TCP port 8888
end of sleep
netstat -tlep | grep 8888
... start.sh terminated
localhost:~#

With --privileged
localhost:~# docker run -it -p 8888:8888 --privileged zinen2/alpine-pigpiod
Unable to find image 'zinen2/alpine-pigpiod:latest' locally
latest: Pulling from zinen2/alpine-pigpiod
e14425cf8fb9: Pull complete
aa5bf1b6f601: Pull complete
97ec19dce31d: Pull complete
4f4fb700ef54: Pull complete
62689cf4fe6a: Pull complete
Digest: sha256:9a73f9843e499bbf3d6d6fd3ef0ab661761349d650498dd4df2f01b9499ec7af
Status: Downloaded newer image for zinen2/alpine-pigpiod:latest
Checking who is listening/bound to port 8888 ...
...OK, no process is listing/bound to port 8888
Starting daemon pigpiod ...
2023-11-26 15:05:43 initPeripherals: mmap gpio failed (Invalid argument)
Can't initialise pigpio library
... daemon stopped unexpectedly.
netstat -tlep | grep 8888
sleeping for 20 sec - we hope that this releases the bound TCP port 8888
end of sleep
netstat -tlep | grep 8888
... start.sh terminated
localhost:~#

Could you try to see if this will run?
docker run -it -p 8888:8888 --privileged zinen2/alpine-pigpiod pigpiod -g -s 10
The above is a fix for used on 64bit CPUs. I'm curios if this would fix your issue on a Raspberry Pi 2 Model B V1.1. Note that console logs will be none existing using the above as this will modify the CMD part of the Dockerfile. But if it runs and dont throw an error message... Then the solution is easy,

No luck.


Eextension of the issus #479, chatbot.py cannot load the bloom model

Eextension of the issus #479, I only pass the step1_supervised_finetuning, use bloom-3b model.
And I run the following program:
python chat.py --path output/actor-models/bloom3b
I get the following error message：
Traceback (most recent call last):
File "./inference/chatbot.py", line 102, in
main(args)
File "./inference/chatbot.py", line 73, in main
generator = get_generator(args.path)
File "./inference/chatbot.py", line 34, in get_generator
model = OPTForCausalLM.from_pretrained(path,
File "/workspace/anaconda3/envs/deepspeed/lib/python3.8/site-packages/transformers/modeling_utils.py", line 2629, in from_pretrained
model = cls(config, *model_args, **model_kwargs)
File "/workspace/anaconda3/envs/deepspeed/lib/python3.8/site-packages/transformers/models/opt/modeling_opt.py", line 817, in init
self.model = OPTModel(config)
File "/workspace/anaconda3/envs/deepspeed/lib/python3.8/site-packages/transformers/models/opt/modeling_opt.py", line 749, in init
self.decoder = OPTDecoder(config)
File "/workspace/anaconda3/envs/deepspeed/lib/python3.8/site-packages/transformers/models/opt/modeling_opt.py", line 492, in init
self.layerdrop = config.layerdrop
File "/workspace/anaconda3/envs/deepspeed/lib/python3.8/site-packages/transformers/configuration_utils.py", line 260, in getattribute
return super().getattribute(key)
AttributeError: 'BloomConfig' object has no attribute 'layerdrop'
May I ask, does this mean that the programs provided by the github can only run OPT models?
If I want the program to use bloom model, how can I fix the above error?

I also encountered this problem！！！

@korlin0110 , are you still stuck on this issue? what's the zero version you use? if you use zero 3 try to switch to zero 2 to see if it works.


[DO NOT MERGE] Normalize IR for profiler for debugging

While debugging yolov3 with AOT, I found that something weird is going on it normalize_ir.
This PR called normalization for the simple fx_profiler. I am able to repro the yolov3 error with this
python torchbench.py --only=yolov3

@anijain2305 https://github.com/facebookresearch/torchdynamo/commit/a9a894b8c514b1a0f239d4441fcb01e26f340870 should fix the issue you have here.
Though it introduces a new type of "indirect_mutation" that is not unhandled.  Here is an example:
def indirection_mutation(x):
    tmp = x * 10
    torch.sigmoid_(tmp[3])
    return tmp

Before it would change the sigmoid_ to sigmoid.  Now it won't.

Thanks! yolov3 is not passing with AOT Autograd!

Hi Jason, can you explain what indirect_mutation means here? Currently, it is preventing the functionalization of simple examples like there
import torch
import torch.fx
import torchdynamo
from torchdynamo.optimizations.normalize import normalize_ir
from torchdynamo.optimizations.analysis import has_mutation

inputs = [torch.randn(4, 5) for _ in range(4)]

def f(p, q, r, s):
    mul = torch.mul(p, q)
    mul.add_(r)
    sub = mul - s
    return sub

fx_mod = torch.fx.symbolic_trace(f)
print(fx_mod)

res = normalize_ir(fx_mod, inputs)
print(res)

assert not has_mutation(res, inputs)

indirect_mutation means the thing you mutated is reused elsewhere under a different name.  It was mainly trying to catch cases like:
b=a.view(1,2,3)
b[5:] = 10
<use a -- which was indirectly mutated via b>

I can see why your example is triggering that.  I think you want to add a pass to rewrite it to something like:
def f(p, q, r, s):
    mul1 = torch.mul(p, q)
    mul2 = mul1.add_(r)
    sub = mul2 - s
    return sub

Or modify the indirect mutation detection to not fire on _ or inplace methods.


Review By_Column in selectors and using Column within APIs

This task is automatically imported from the old Task Issue Board and it was originally created by James Dunkerley.
Original issue is here.

The current By_Column in selectors works by picking a matching name. This functionality should be removed.
When a column is passed to functions (such as Sum and Average) the column is only valid if in the table.
Derived columns would need to be set in the table.
Once expressions are supported they should be able to be used here.

Additionally: Add Vector_Editor attribute to Table.select_columns


MRG: Use new verbose argument

Should clean up our examples that use PySurfer.

Simplified log output:
https://5927-1301584-gh.circle-artifacts.com/0/tmp/circle-artifacts.StvdLfV/html/auto_tutorials/plot_mne_dspm_source_localization.html

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7d74ace). Click here to learn what that means.
The diff coverage is 62.5%.

@@            Coverage Diff            @@
##             master    #4611   +/-   ##
=========================================
  Coverage          ?   87.09%
=========================================
  Files             ?      349
  Lines             ?    66199
  Branches          ?    10267
=========================================
  Hits              ?    57655
  Misses            ?     5650
  Partials          ?     2894

thx @larsoner


Look into compressing hero and other images

Reported by @ascott1

a lot of the loading of the landing page is caused by the size of the hero image. can we compress that image? it should lead to significant savings:

(326.7 KB, compressed = 50.0 KB - savings of 276.7 KB) - http://www.consumerfinance.gov/static/img/home-hero_lg.jpg
(132.5 KB, compressed = 22.7 KB - savings of 109.8 KB) - http://www.consumerfinance.gov/static/img/home-hero_sm.jpg

Closed by #2178


Ghost API: Post content not showing

Issue Summary
When using Ghost API to send post data, using field "plaintext" shows content text in text snippet (visible from admin page), but when you open the post itself, it shows just "null".
Steps to Reproduce

Add post using Ghost API.
Send data using "plaintext" field.

@acburdine that is not very intuitive. Nevertheless thanks for your explanation!
I have one more question, how do you upload media files (images) using API?

that is not very intuitive

That's why it's private API and not yet officially public 😉

how do you upload media files

Can't remember the endpoint offhand, but if you look at the network request Ghost-Admin sends when uploading an image you should be able to see what that endpoint is and what to send to it 😄

@acburdine  thanks! 👍

Closing this as it's not an issue with Ghost itself.


How to change colour of starts? I am getting black on my side.

Hi...
Its very nice plugin. Could you plz tell how should we change the colour of stars.

I am still working on proper themes for all the ngxlite components for now you can add this to your global CSS file
ngx-input-star-rating {
  --color-star-highlight: gold !important;
}

thanks for your valuable reply.
On Wed 6 Jun, 2018 10:41 am Cory Rylan<EMAIL_ADDRESS>wrote:

I am still working on proper themes for all the ngxlite components for now
you can add this to your global CSS file
ngx-input-star-rating {
--color-star-highlight: gold !important;
}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/coryrylan/ngx-lite/issues/6#issuecomment-394942114,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AcuLNh_FM2DfaR5xtBgA9j8TOvOWx1-Vks5t52SFgaJpZM4UZjg0
.


Support all ADF Date/Time functions for debugging

support all functions listed here where parsing a ADF project for debugging:
https://docs.microsoft.com/en-us/azure/data-factory/data-factory-functions-variables

first set of functions is now supported, basically those which exist in the C# class DateTime

excuse my ignorance.. does this mean the latest version now supports WindowStart / WindowEnd ?

WindowStart/WindowEnd is currently not supported. To be honest, I do not know if this was ever fully implemented in ADFv1 at all?
Whats actually the difference between WindowStart/End and SliceStart/End?
as the slices of a dataset have to match the slices of the activities and pipelines, it is actually the same - no?

I think that was the original idea - having Slices split into Windows (or the other way round) to allow the combination of daily and hourly data for example. But thats just a wild guess.
For usability, I will add 2 new optional parameters for WindowStart/End where the defaults will be derived from SliceStart/End


Caddy HTTPS proxy to HTTPS Backend

Is there a way to pass (via caddy proxy) directly to a HTTPS backend website? If possible id like the backend to handle the SSL connection.

You can use the net server type plugin to make a TCP server: https://caddyserver.com/docs/net


Update community tutorial on RB

Update the tutorial:
https://github.com/Qiskit/qiskit-tutorials-community/blob/master/ignis/RB_overview.ipynb

[x] The API is not updated (it uses assemble_circuits)
[x] Relate to new RB algorithms: interleaved and purity RB

PR was merged in: https://github.com/Qiskit/qiskit-tutorials-community/tree/master/ignis


fastlane init for Android is borked

fastlane init in a Flutter project android directory produces this error.
I installed fastlane with brew cask install fastlane following these instructions. https://flutter.io/docs/deployment/fastlane-cd
I know nothing about Ruby.
Using addressable 2.6.0
Using commander-fastlane 4.4.6
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

To see why this extension failed to compile, please check the mkmf.log which can
be found here:

/Users/lukepighetti/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/extensions/x86_64-darwin-15/2.2.0-static/unf_ext-<IP_ADDRESS>/mkmf.log

extconf failed, exit code 1

An error occurred while installing unf_ext (<IP_ADDRESS>), and Bundler
cannot continue.
Make sure that `gem install unf_ext -v '<IP_ADDRESS>'` succeeds before bundling.
[21:35:35]: Exit status: 5
[21:35:35]: Something went wrong when running `bundle update` for you
[21:35:35]: Please take a look at your Gemfile at path `Gemfile`
[21:35:35]: and make sure you can run `bundle update` on your machine.

Same here (but with a standard Android project):
✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.3

Ruby
2.2.4

Bundler?
false

Git
git version 2.7.4 (Apple Git-66)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.14.3 (18D109)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
true

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
~/../../Applications/Xcode7.app/Contents/Developer/

Xcode Version
7.3.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.116.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

CFPropertyList
2.3.5

addressable
2.5.1

atomos
0.1.3

babosa
1.0.2

bigdecimal
1.2.6

bundler
1.14.6

claide
1.0.2

colored
1.2

colored2
3.1.2

commander-fastlane
4.4.6

declarative
0.0.10

declarative-option
0.1.0

digest-crc
0.4.1

domain_name
0.5.20170404

dotenv
2.2.0

emoji_regex
1.0.1

excon
0.55.0

faraday
0.12.1

faraday-cookie_jar
0.0.6

faraday_middleware
<IP_ADDRESS>

fastimage
2.1.0

gh_inspector
1.1.3

google-api-client
0.23.9

google-cloud-core
1.3.0

google-cloud-env
1.0.5

google-cloud-storage
1.16.0

googleauth
0.6.7

highline
1.7.8

http-cookie
1.0.3

httpclient
2.8.3

hurley
0.2

io-console
0.4.3

json
1.8.1

jwt
1.5.6

libxml-ruby
3.0.0

little-plugger
1.1.4

logging
2.2.2

memoist
0.16.0

mime-types
3.1

mime-types-data
3.2016.0521

mini_magick
4.5.1

minitest
5.4.3

multi_json
1.12.1

multi_xml
0.6.0

multipart-post
2.0.0

nanaimo
0.2.6

naturally
2.2.0

nokogiri
1.5.6

os
0.9.6

plist
3.2.0

power_assert
0.2.2

psych
2.0.8

public_suffix
2.0.5

rake
10.4.2

rdoc
4.2.0

representable
3.0.4

retriable
2.1.0

rouge
2.0.7

rubygems-update
2.5.2

rubyzip
1.2.2

security
0.1.3

signet
0.11.0

simctl
1.6.5

slack-notifier
2.3.2

sqlite3
1.3.13

terminal-notifier
1.7.1

terminal-table
1.7.3

test-unit
3.0.8

tty-cursor
0.6.0

tty-screen
0.6.5

tty-spinner
0.9.0

uber
0.0.15

unf
0.1.4

unf_ext
<IP_ADDRESS>

unicode-display_width
1.1.3

word_wrap
1.0.0

xcodeproj
1.8.0

xcpretty
0.3.0

xcpretty-travis-formatter
0.0.4

generated on: 2019-02-18

And the --verbose:
DEBUG [2019-02-18 11:41:28.03]: Checking if there are any plugins that should be loaded...
ERROR [2019-02-18 11:41:28.87]: It looks like there is no iOS project in the current directory, though we did find one in a sub-directory
ERROR [2019-02-18 11:41:28.87]: Please `cd` into the directory of the intended Xcode project you wish to use.
/Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in `user_error!': [!] Please `cd` into the directory of the intended Xcode project you wish to use and run `fastlane init` again (FastlaneCore::Interface::FastlaneError)
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane_core/lib/fastlane_core/ui/ui.rb:17:in `method_missing'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane/lib/fastlane/setup/setup.rb:93:in `start'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane/lib/fastlane/commands_generator.rb:121:in `block (2 levels) in run'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in `call'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in `run'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in `run_active_command'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in `run!'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in `run!'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane/lib/fastlane/commands_generator.rb:333:in `run'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane/lib/fastlane/commands_generator.rb:41:in `start'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/fastlane/lib/fastlane/cli_tools_distributor.rb:113:in `take_off'
	from /Users/me/.fastlane/bin/bundle/lib/ruby/gems/2.2.0/gems/fastlane-2.116.0/bin/fastlane:23:in `<top (required)>'
	from /Users/me/.fastlane/bin/bundle/bin/fastlane:22:in `load'
	from /Users/me/.fastlane/bin/bundle/bin/fastlane:22:in `<main>'

Hi @FireZenk, your problem looks very different. Can you please open a new bug report issue and include all the information it asks for? Thanks.

Dona @janpio https://github.com/fastlane/fastlane/issues/14261 thank you

Sorry everyone, I hung up fastlane for the time being due to this bug. Will update this thread when I have more time.

Hey everyone, I'm going to close this. Will reopen if I run into it again next time I try out Fastlane.


Stasis Render on Heroku

Hi there.
I'm trying to get Stasis to render on Heroku, but am not being very successful. Whenever I run stasis . from the Heroku console, it returns this error:
NameError: uninitialized constant #<Class:0x00000002167900>::Thin::Controllers::Controller::Logging
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:23:in `<class:Controller>'
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:22:in `<module:Controllers>'
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:19:in `<module:Thin>'
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:3:in `_add'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis/scope/controller.rb:30:in `instance_eval'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis/scope/controller.rb:30:in `_add'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis.rb:100:in `block in initialize'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis.rb:97:in `reject!'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis.rb:97:in `initialize'
	from (irb):4:in `new'
	from (irb):4
	from /usr/local/bin/irb:12:in `<main>'

Same happens when I manually create a new Stasis object:
irb(main):004:0> s = Stasis.new(".")

NameError: uninitialized constant #<Class:0x00000002167900>::Thin::Controllers::Controller::Logging
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:23:in `<class:Controller>'
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:22:in `<module:Controllers>'
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:19:in `<module:Thin>'
	from /app/vendor/bundle/ruby/1.9.1/gems/thin-1.3.1/lib/thin/controllers/controller.rb:3:in `_add'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis/scope/controller.rb:30:in `instance_eval'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis/scope/controller.rb:30:in `_add'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis.rb:100:in `block in initialize'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis.rb:97:in `reject!'
	from /app/vendor/bundle/ruby/1.9.1/gems/stasis-0.1.14/lib/stasis.rb:97:in `initialize'
	from (irb):4:in `new'
	from (irb):4
	from /usr/local/bin/irb:12:in `<main>'

I do not have this issue locally and I have no idea why this is happening. Does anyone else?
Thanks!

I don't think you can get stasis to work at Heroku. The problem you hare having is probably tied to the fact that heroku rewrites your logging output, but even if you could solve that, you still have to deal with the fact that Heroku has no (usable) write permission for your app. So stasis can never save the generated files.

@JeanMertz I actually decided to use MiddleMan for my static website. It's very similar to stasis in some aspects. I also wrote out a little multi-file gist explaining how to get the static site to run on Heroku.
It actually is possible and Heroku does have a writable filesystem since Celadon Cedar was released months ago. Although it isn't a persistent file system, since processes are moved around, everything you write should be considered "temporary".
This however is no problem. I just tell Heroku to pre-compile the whole static website before booting the Thin app server every time a process (re)starts. I added a little Rack Middleware to serve the pre-compiled static pages afterwards. So you have to run a very small layer of Rack middleware, but it's extremely fast and static pages are cached by Heroku.
See: https://gist.github.com/1718367 (this could also work with Statis, but I keep running in to the above issues)
The key to doing all this lies mainly in using an app server like Thin, plus Rack::TryStatic plus Procfile with Celadon Cedar to customize process boot-behavior.

A config.ru like this should allow you to use stasis-generated sites on Heroku.
use Rack::Static,
  :urls => ['/images', '/javascripts', '/stylesheets'],
  :root => Dir.pwd

run lambda { |env|
  [
    200,
    {
      'Content-Type'  => 'text/html',
      'Cache-Control' => 'public, max-age=86400'
    },
    File.open('index.html', File::RDONLY)
  ]
}


Fix Dockly::History#push_content_tag!

@tlunter
Before, we were looking for the $SSH_AGENT_PID, which only exists when
the SSH agent is on the same host the commands are running on. However,
this doesn't exist when using remote ssh agent forwarding. This commit
instead inspects the correct environment variable, $SSH_AUTH_SOCK,
before failing.

:+1:


feature(razzle): new writeCssDev razzle option

resolves jaredpalmer/razzle#1509
This option adds stylesheet link tags in the header for the development build, similar to the production build. It allows to
test this functionality in development (and avoid the Flash Of Unstyled Content effect), but prevents hot reloading when the css is updated. It is turned off by default.

For 5.0 I think make everything plugins.

For 5.0 I think make everything plugins.

Ah, the  diff confused me. all ok

Ah, the  diff confused me. all ok

Are you on discord? If so come here https://discord.gg/pJSg287

Are you on discord? If so come here https://discord.gg/pJSg287

Is this a good place to move up the two options in the documentation? I also updated the comment.
    cssPrefix: 'static/css',
    jsPrefix: 'static/js',
    mediaPrefix: 'static/media',
    **staticCssInDev: false, // static css in header in development build (incompatible with css hot reloading)
    browserslist: undefined, // or what your apps package.json says**
    enableReactRefresh: false,
    enableTargetBabelrc: false, // enable to use .babelrc.node and .babelrc.web

Is this a good place to move up the two options in the documentation? I also updated the comment.
    cssPrefix: 'static/css',
    jsPrefix: 'static/js',
    mediaPrefix: 'static/media',
    **staticCssInDev: false, // static css in header in development build (incompatible with css hot reloading)
    browserslist: undefined, // or what your apps package.json says**
    enableReactRefresh: false,
    enableTargetBabelrc: false, // enable to use .babelrc.node and .babelrc.web

Yes

Yes


ls command has no output in mounted drives

Environment
Microsoft Windows [Version 10.0.19042.746]
PRETTY_NAME="Kali GNU/Linux Rolling"
NAME="Kali GNU/Linux"
ID=kali
VERSION="2020.4"
VERSION_ID="2020.4"
VERSION_CODENAME="kali-rolling"
ID_LIKE=debian
Linux version 4.4.0-19041-Microsoft<EMAIL_ADDRESS>(gcc version 5.4.0 (GCC) ) #488-Microsoft Mon Sep 01 13:43:00 PST 2020
Windows build number: [run `cmd.exe /c ver`]
Your Distribution version: [On Debian or Ubuntu run `lsb_release -r` in WSL]
Whether the issue is on WSL 2 and/or WSL 1: [run `cat /proc/version` in WSL]

Steps to reproduce
sudo mkdir /mnt/z
sudo mount -t drvfs Z: /mnt/z
cd /mnt/z
ls

strace: command not found

WSL logs: cannot be provided
C:\Users\localadmin\Downloads>wpr -start wsl.wprp -filemode

        Error code: 0xc00cee4f

Additional Information
Output of mount:
rootfs on / type lxfs (rw,noatime)
none on /dev type tmpfs (rw,noatime,mode=755)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,noatime)
devpts on /dev/pts type devpts (rw,nosuid,noexec,noatime,gid=5,mode=620)
none on /run type tmpfs (rw,nosuid,noexec,noatime,mode=755)
none on /run/lock type tmpfs (rw,nosuid,nodev,noexec,noatime)
none on /run/shm type tmpfs (rw,nosuid,nodev,noatime)
none on /run/user type tmpfs (rw,nosuid,nodev,noexec,noatime,mode=755)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tmpfs on /sys/fs/cgroup type tmpfs (rw,nosuid,nodev,noexec,relatime,mode=755)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
C:\ on /mnt/c type drvfs (rw,noatime,uid=1000,gid=1000,case=off)
Z: on /mnt/z type drvfs (rw,relatime,case=off)

Tab autocomplete of files and paths doesn't work too.
Expected behavior

I expect to see my files and folders on this drive listed.
Actual behavior
Instead I have no output.
The exit code of ls is 0 though.

I think the cause is the absence of mount metadata options. Try this command
sudo mount -t drvfs Z: /mnt/z -o metadata,uid=1000,gid=1000

Sadly this doesn't fix the problem.
Also he docs say that metadata is enabled by default.

Maybe this additional information is helpful:

The problem is in Virtual Box Windows VM on a Win10 host (I have no rights to use WSL outside a VM).
The Z drive is the mounting point of a shared folder between Host and VM.

Landing zone /dupe #2896.


production ?

The readme stipulates that we shouldn't use this plugin in production. What's preventing this ?
Just trying to gauge whether to use this package in out project.
Cc @feugy

I think that is just a leftover from the initial documentation

@rjrodger @nherment
My target this week is to prepare this project to be production ready, including documentation and some other small changes.

Super, thanks !


[Question] Availability on Maven Central ?

Hello,
Do you plan an availability of the library availability on Maven Central to directly import it on new maven projects by simply putting the reference in the POM, and automatically downloaded ?
Thanks,
Regards.

https://github.com/rithms/riot-api-java/issues/61


navigate() with a space in the url triggers route even when {trigger:false} in Firefox

Consider this example:
$(function(){
var AppRouter = Backbone.Router.extend({

    routes: {
        '(count/:count)': 'home',
    },

    home: function(currCount) {
        var counter = 0;
        var thisObj = this;

        $("body").html($("
Click me
").on('click', function() {
            console.log("clicked "+counter);
            counter++;
            thisObj.navigate('count/'+counter, {trigger:false, replace: true});
        }));

        console.log('home route: '+currCount);
    },
});

window.app = new AppRouter();
Backbone.history.start();
});

This should log "home route: null" and then proceed to log "click #" for every click on "Click me".
Now, make one small modification. Add a space to the url in navigate():
thisObj.navigate('count/ '+counter, {trigger:false, replace: true});

Try again and you will find that that "home route: #" will also start being logged, and the counter will reset two out of every three clicks.
This is in the 1.1.2 release and I am testing on the latest Firefox 33.1. I am not having this issue in Chrome - it could be because Chrome maybe does something to encode spaces in the URL. I'm not sure though.
I realize that the space character should not be in a URL in the first place, but this behavior is odd and should at the very least be documented. (i.e. "The navigate() may not behave as expected with URLs containing spaces (or other unsafe characters??).")
I am not sure if there is an easy fix for this, but I hope that at least by documenting this bug I save other developers time in trying to hunt it down.

I actually have seen this exact same issue, but am unable to share my code.  I'll see if I can mock up some test code to replicate this, but I've discovered that the issue is most definitely browser based.  All modern versions of IE and Chrome work fine, but at least on Firefox v31.5.0 (don't ask, I hate the infrastructure we're stuck on), it definitely triggers without even adding the trigger option.

Here's what I've discovered.  In Firefox, if you check the variable "this.location.href", any whitespaces in the variable are encoded into %20's.  Chrome (and presumably IE) leaves them as whitespace.  This is an issue in Backbone, since when you go to navigate, "checkUrl()" does a comparison of "this.fragment" against the returned value of "this.getFragment()" to determine whether or not to call "this.loadUrl()", if they don't match.  this.getFragment() returns the value of this.location.href, with the %20's in place of any spaces in Firefox (or any encodeings for that matter).  this.fragment returns an decoded equivalent.  this.fragment remains decoded, regardless of whether or not you use encodeURI() on your URL's, because in the "navigate()" function, this.fragment is assigned by calling "this.decodeFragment()" on the URL that gets passed in, removing any attempts at forcing encoding.
Therefor, if this.fragment is always a decoded URL due to the use of this.decodeFragment(), and the URL contains any characters that encodeURI() would change (in this case spaces), it will never match the returned value of this.getFragment() in Firefox, since Firefox encodes the value of this.location.href, whereas other browsers don't.  Since these two values don't match, this.loadUrl() gets called in checkUrl(), regardless of whether or not the trigger parameter in router.navigate is true or false.

Still needed with last version so thank you !

I have the same issue when trying to use non-standard characters in the URL, in my case åäö (characters that are in the Swedish alphabet).
sjmiller85's solution worked for me as well. Thanks a bunch!

@Aggror pathStripper is, according to the documentation, a cached regex for stripping urls of hash.
// Cached regex for stripping urls of hash.
var pathStripper = /#.*$/;

So it's the equivalent of your solution, only more neat and efficient :)

avoid adding the  simultaneous same hash to your router and also take care of initial condition , I will show you a code
(to handle initial case)  (to prevent adding simultaneous same routes)
if ( routes.length === 1 || routes[routes.length-1] === getHash() ) {
return false;
}
else{
routes.push(getHash())
};