Bug: Impossible to configure a FIDO2 Security Token

What happened?
I tried to configure multiple Yubikey as security token (2 different Yubikey 5 NFC firmware 5.1.2 and a Yubikey 5C NFC firmwqre 5.4.3) on both 2FAGuard desktop and portable but for all combination I'm having an error message. Those 3 yubikeys are already registered for FIDO2 authentication or passkey and works properly
Provide the error message / stack trace
Error: Assertion failed HmacSecret is null
What version of Windows are you using?
Windows 10 pro 64 bits 22H2
What version of the app are you using?
<IP_ADDRESS> desktop and portable

Thanks for reporting this bug.
The HMAC Secret Extension is the only way to encrypt data securely. After some research I found this article by yubico. Yubikey added support for this extension in firmware version 5.2. This explains why your older keys are not working as expected.
I tested the implementation using a Security Key C NFC with the firmware 5.4.3, so with the same firmware version. I will check it again with a Windows 10 device.
Do you know if you have more than 25 discoverable credentials on your key?
(But according to the FIDO2 specification, it should still work)
Can you please send me the logs of the app? You will find them inside the data folder.

I shall not have more than 25 fido/passkey on the 5.4.3 key, but there is no real way to check :(
Can you tell me the full path of the logs ?

Thanks for the quick reply.
If you are using the portable edition, the logs are inside the 2FAGuard-Data\logs folder.
The logs of the desktop edition they are located in C:\Users\%username%\AppData\Local\2FAGuard\logs.

I just tried again to configure the 5.4.3 but there is no log files for today :/ the last log file is from when I updated to 1.5.1

Hello,
I tried the website, same result as you, could not get "enabled: true". I also tried to uninstall 2FAGuard and resintall it, same result, I can not register any yubikey (and logs are still emtpy).
My yubikeys are register in multiple website (google for, 1password, Facebook, ....)so I'm sure they are working correctly.

Hello,
I will try this on a Windows 10 device soon, maybe it uses a old version of the Win32 WebAuthn api.
There is a difference between the usage of WebAuthn for logging in on a website and local encryption, because the HMAC secret extension is only used for the second one.

Don't hesitate to send me debug version if you need my support to find the root cause

While Windows 11 includes the latest version of the webauthn.dll (version 7), Windows 10 appears to be shipped with version 2 of the Win32 WebAuthn api. According to comments in some Microsoft source code, I believe that at least version 4 is required to use the required secret extension. I have made an enquiry to Microsoft about this, but I assume that 2FAGuard can probably only support login with external security keys under Windows 11.

Update: I haven't received a reply from Microsoft to my message to the Win32 WebAuthn API support email address. The Microsoft Partner Center allows app developers to submit only non-technical support cases to Microsoft. For technical issues / questions, I am told to buy a support plan for several hundred euros. I will keep this issue open until the next release, which will include a better check if the os is supported.

The new release improves a better error handling and checks if the OS supports all necessary features.


Add recommendation for repository branches

Description
It is unclear what the branches semantically mean in a source repository for a ROS package. This PR provides some guidelines in the docs.

Good to go!


Welcome to Print-To-3D Discussions!

Discussed in https://github.com/p3d-dev/Print-To-3D/discussions/2

Originally posted by p3d-dev August  3, 2022

👋 Welcome!
We’re using Discussions as a place to connect with other members of our community. We hope that you:

Ask questions you’re wondering about.
Share ideas.
Engage with other community members.
Welcome others and are open-minded. Remember that this is a community we
build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

Any idea why I get this on any print I try to slice

Hi All
Last questions first.
Using iPad with an Apple processor running IpadOS 16.3.1, I have not made any settings changes I am aware of. Unless something like installing Grammarly can influence things.
I think I may have isolated it to an issue with the Prusa MK3S+ template. The reasoning for this is that, after deleting the app completely and reinstalling on both iPhone and iPad it still would not slice. I tried adding new printer as suggested still without success.
However the eureka moment came on using a different template and with this both iPhone and Ipad sliced successfully on the Ender 3 template file. Tried a few files and all were sliced successfully bar one that sliced but not well.
Hope info below helps,Prusa code template downloaded from templates
I am not ofay of this stuff but Should.  M83                ; set relative positioning for extruder.   Be M84
The stl file below is the one that did not slice properly
Gcode Preamble
M201 X1000 Y1000 Z200 E5000  ; accel
M203 X200 Y200 Z12 E120      ; feedrate
M204 P1250 R1250 T1250       ; accel
M205 X8.00 Y8.00 Z0.40 E4.50 ; jerk
M205 S0 T0                   ; min travel
M107                         ; disable cooling fan
M862.3 P "MK3S"              ; printer model check
M862.1 P0.4                  ; nozzle diameter check
M104 S160          ; set extruder temp
M140 S{bed_temp}   ; set bed temp
M190 S{bed_temp}   ; wait for bed temp
G28 W              ; home all without mesh bed level
G80                ; mesh bed leveling
G90                ; set absolute positioning mode
M83                ; set relative positioning for extruder
M900 K0.04         ; linear advance
G1 F1000           ; set feedrate
G1 Y-3.0 Z0.5      ; park outside print area
M104 S{temp}       ; set extruder actual required temp
M109 S{temp}       ; wait for extruder actual required temp
G1 X60.0 E9.0      ; purge line
G1 X100.0 E12.5    ; purge line
M117 Printing
Gcode Postamble
G0 E-1 F900  ; retract slightly
M104 S0      ; turn off nozzle heat
M140 S0      ; turn off bed heat
M107         ; turn off fan
G0 F3000     ; set feedrate
G0 Y210 Z210 ; serve up print
G4           ; wait
M84          ; disable steppers
M117 Print Done
Gcode Layer
;; LAYER {layer} of {layers}
M117 Layer {layer} of {layers}
Gcode Progress
M73 P{progress}
Gcode Fan
M106 S{fan_speed}

Robin Harper

Great fixed. Had ago at slicing a few items and this was successfully achieved.
However please find attached a couple of photos. Before and after slicing any idea why the slice is unsuccessful.

9 Draw Holder.zip
I have attached a 9 box version with the same issue.

Many thanks for all your help.
Will look to redesign it from one block.
One last question, I am only a hobbyist and I am looking to move to a tablet completely (laptop very old) and this appears a good fit. Are there any tutorials around the “Process Congratulation” looking to design something in line with Prusa slicer draft mode


Uhuru login redirects to blank screen

Tried logging in to Uhuru on the main login page on https://beta.uhuru.me/
and just getting a blank screen after the redirect

@ken-de-moor please follow up here


JoinRelation interface weakens type in method chain

class Foo extends Model {
  prop!: number;
}

async function joinRelationDoesNotSupportChaining() {
  const foo1: Foo | undefined = await Foo.query().first();
  const foo2: Foo | undefined = await Foo.query().joinRelation('any_relation').first(); // won't compile
}

From JoinRelation interface signature foo2 inferred type would be Model | undefined, but, if I'm correct, it's type would never be weaker than Foo | undefined.
So I suggest to change typings from
  interface JoinRelation {
    <QM extends Model>(relationName: string, opt?: RelationOptions): QueryBuilder<QM, QM[]>;
  }

to
  interface JoinRelation {
    <TBase extends Model, QM extends TBase>(this:QueryBuilder<TBase>, relationName: string, opt?: RelationOptions): QueryBuilder<QM, QM[]>;
  }

Ran across this. Unfortunately I don't have time to dig into it at the moment, but looking at the example change you've given @Aksigera I don't think you need TBase.
should work the same with:
  interface JoinRelation {
    <QM extends Model>(this: QueryBuilder<QM>, relationName: string, opt?: RelationOptions): QueryBuilder<QM, QM[]>;
  }

As QM can then be derived directly from the QueryBuilder found in the this context.

Ran across this. Unfortunately I don't have time to dig into it at the moment, but looking at the example change you've given @Aksigera I don't think you need TBase.
As QM can then be derived directly from the QueryBuilder found in the this context.

I don't expect joinRelation() to return type of this, that's why I added TBase.
In your code, output of function is of the same type as, well, input. But join means expanding of type, so we have such hierarchy Model <= TBase <= QM, where <= means smaller or equal.
TBase can be changed to anything, I'm not familiar with naming conventions on this project

adding a note here that this affects the other similar functions rightJoinRelation, etc. Going to tackle this issue this week

Fixed in 2.0


Add support for different service names

Currently, the script assumes that Cosmovisor is installed and controlling the chain's daemon. This should remain the default, with an optional flag, -s/--service, that dictates the service stop/start.

Added Custom Service Option #3


Stop sending emails (and maybe warnings) on PGP signature uploads

In https://github.com/pypi/warehouse/pull/13707 we removed the support for uploading signatures to PyPI, but we added warnings both in email and in twine if someone attempts to upload a signature to let them know that support is gone.
We should remove that at some point in the future. Probably in roughly a year (so May 2024? or so).

It's May 2024, I made https://github.com/pypi/warehouse/pull/15896 to resolve this.


Debate on LaunchTemplateName removal from AWSNodeTemplate

Description
Removal RFC PR: https://github.com/aws/karpenter/pull/4211/files
Slack discussion: https://kubernetes.slack.com/archives/C02SFFZSA2K/p1690502420089729
Launch template drift PR (related but not necessarily important): https://github.com/aws/karpenter/pull/4348
What problem are you trying to solve?
We would like to start a discussion about the plan to remove unmanaged launch templates (launchTemplateName) from the AWSNodeTemplate CRD. We proposing that it should not be removed.
We currently use kOps to manage our clusters, including our own control plane nodes. Since we are not using EKS, we need kOps to properly tag subnets and security groups, which means we have kOps manage an instance group that is set aside for use by Karpenter. We then use launchTemplateName in our AWSNodeTemplate to launch nodes using the kOps-managed launch template created for the kOps-created instance group.
When we brought up the removal of launchTemplateName in Slack, it was proposed that we create a Karpenter-managed launch template that matches the spec of those we create by kOps. However, based on our current understanding, this doesn't work. When we modify a cluster, kOps produces terraform that, amongst other things, creates a new launch template and updates the nodeup script for that launch template in S3. The userdata included in the launch template downloads the nodeup script from S3 and checks that script against a hash that it expects. When we update a cluster, kOps changes the nodeup script stored in S3, and updates each instance group's launch template's userdata with the new hash. Because the Karpenter-managed launch template has not been updated, the nodeup script fails to download and the node is unable to join the cluster.
When we were first exploring and setting up Karpenter, we worked around this by manually copying the userdata from a kOps-managed launch template into our Karpenter-managed launch template. We soon after started using launchTemplateName in the AWSNodeTemplate, which perfectly met our needs.
Because of this, we think the option to use an eternally-managed launch template should remain. We acknowledge the debate around launchTemplateName and the added complexity it brings to Karpenter, so we propose that if launchTemplateName is specified in the AWSNodeTemplate, all other AWSNodeTemplate fields are ignored. Linked above is a PR to allow for drift when new launch template versions are created.
How important is this feature to you?
It's very important to us, as the removal of unmanaged launch templates means that we will have to manually update our Karpenter-managed launch template's userdata.
As an alternative, we're seeking a recommendation for using Karpenter within a kOps-managed cluster.

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

@fffinkel I'm wondering what we could do to get kOps to support Karpenter-managed launch templates upstream. Do we think that it would be possible to have kOps manage the NodeTemplate and the userData inside of it, since it's already context-aware of the Provisioner and is using the instance group mapping to provision and manage a Provisioner in the cluster that maps to the instances assigned to the instance group.

I think by having kOps manage the AWSNodeTemplate and the Provisioner, we lose a lot of the flexibility that's afforded to us by creating Provisioners directly.
@sftim's suggestion of a separate AWSCustomNodeTemplate allows for the expressiveness of Karpenter's Provisioners while still using the LaunchTemplate created by kOps.

we lose a lot of the flexibility that's afforded to us by creating Provisioners directly

Maybe I was mis-understanding the documentation, but, reading about kOps support with Karpenter, I was under the impression that they were doing the configuration and management of the Provisioners. I also don't have a deep knowledge of kOps, so any additional detail here would help me understand what exactly they are doing.

You've read it correctly as far as our experience with it goes. They are generated by this template:

Launch templates, kubelet configuration and other aspects of Provisioner, kOps configuration and AWS resources must match, which is why kOps must own much of this.
Using your own Providers will work, but you must refer to existing launch templates, and some of the configurations must be configured identical as in the respective kOps Instance Group configuration. If not Karpenter will make wrong assumptions about e.g resources available based on kubelet resources reserved settings.
kOps maintainers strongly prefer informing karpenter about the state of things, rather than delegating things like launch template provisioning.

When we update a cluster, kOps changes the nodeup script stored in S3, and updates each instance group's launch template's userdata with the new hash

@ssoriche @fffinkel How frequently are you updating this script? I'm assuming that this script is updated when you make a change to the kOps control-plane configuration, which I wouldn't expect would change that frequently (maybe you are making a change to your control-plane instance type size due to a cluster growing in size or you are upgrading the Kubernetes version).

The scripts are updated any time there's a change to kOps, cluster components (coreDNS, etc) or specifications.
As part of security posture we recompile kOps or cluster components when CVEs are found in dependencies, meaning that we have to deploy more often than with cluster specification changes. This causes us to deploy approximately every 3 to 4 weeks.

@ssoriche @fffinkel @olemarkus I think we definitely want to make sure that we have a shared discussion about what's the best path forward here for both Karpenter and kOps. Hoping to have a discussion on the topic during kOps office hours on September 8.

@ssoriche @fffinkel and I have been discussing a bit in the Kubernetes slack as well as we have opened up discussion with many of the kOps maintainers. The TLDR is that Karpenter v1beta1 will be broken with kOps anyways as part of the API changes based on some reliance on fields that no longer exist as well as reliance on some labels that will no longer exist in v1beta1. We have discussed this and think that there is a path forward to bring v1beta1 compatibility into kOps as well as allowing kOps to hand-off the launch template management to Karpenter so that Karpenter has all the information that it needs and kOps has all the information that it needs.
As a result, we are going to proceed with the plan to drop the launchTemplateName in v1beta1 since we think this is the best forward-thinking move for the Karpenter project with plans to have a contributor open a PR against kOps to build the compatibility with Karpenter v1beta1 and managed launch templates. We're still looking for contributors in the community who would be willing to pick-up the work of restoring this compat.


Promote unknown units to dimensionless in aux factories

🚀 Pull Request
Description
This PR adds graceful behaviour to the creation of auxiliary factories, such that formula terms that have units of unknown but must be dimensionless (1), have their units promoted from unknown to 1.
This concession in behaviour is the result of real-world examples where NetCDF files missing an appropriate units attribute on formula terms variables, cause the failure of the expected auxiliary factory (and derived coordinate) to appear on the cube.
Previously, iris 2.4.0 loaded such files as expected, but as a result of #3795, iris 3.0.0 (advertised this as breaking behaviour) fails to behave as iris 2.4.0.
This PR alleviates this breaking change somewhat for the community, as it would cause major issues that are not easily avoidable.

Consult Iris pull request check list

Closed #3961

Closed #3961

LGTM

LGTM


Future request: select scala-js version when use Scala2.11

Ref #4807
Based on the Scala2.11 supported discussion.
I need to support to Scala2.11 with scala-js 0.6 what other library also supported.
Any method that I can change scala-js's version to 0.6 when I use Scala2.11 in cross build? Now I can just change the source file and it's the same way as what other library done.

Ah, thanks! This solution has met my expectations and is even more reasonable than I expected.

水山清风
@.***

------------------ 原始邮件 ------------------
发件人: "Sébastien @.>;
发送时间: 2023年3月27日(星期一) 晚上11:33
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [scala-js/scala-js] Future request: select scala-js version when use Scala2.11 (Issue #4840)
If you really want to conditionally use Scala.js 0.6.x or 1.x, use an environment variable. Details here: http://www.scala-js.org/news/2020/02/25/announcing-scalajs-1.0.0/#cross-building-for-scalajs-06x-and-1x
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Chore: formatting, explicit imports.

Housekeeping chore: format a few modules (Purity) before changing them.

I am unhappy with ad-hoc decisions here.

Let me undo those decisions that make you unhappy. What is it in particular?

"unhappy" was meant to attach to "ad-hoc" rather than the specific decisions :) I just think it's past time we agreed on a policy.


Update gejulia to Julia v1 series

I updated the gejulia script to use a more idiomatic Julia syntax and compatible with v1 series, ref #3.  This is a draft pull request because I'm still waiting for test jobs on Grace to start, but this should be mostly working.
As a side note, it might be a good idea considering using ClusterManagers.jl

It seems to be working, so it's ready for review


Column users.email does not exist

Hi there,
i'm trying to use discourse_user_importer script for importing users from my blog, but i'm getting the following error:
rake aborted!
ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR:  column users.email does not exist
LINE 1: SELECT  "users".* FROM "users" WHERE "users"."email" = 'edua...
                                             ^
: SELECT  "users".* FROM "users" WHERE "users"."email" =<EMAIL_ADDRESS>ORDER BY "users"."id" ASC LIMIT 1
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/patches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/patches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:614:in `block (2 levels) in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies/interlock.rb:46:in `block in permit_concurrent_loads'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/concurrency/share_lock.rb:185:in `yield_shares'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies/interlock.rb:45:in `permit_concurrent_loads'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:613:in `block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:612:in `block (2 levels) in log'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:611:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:603:in `log'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:612:in `exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:599:in `execute_and_clear'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:79:in `exec_query'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:371:in `select'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:42:in `select_all'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/query_cache.rb:97:in `select_all'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/querying.rb:39:in `find_by_sql'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:667:in `exec_queries'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:546:in `load'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:255:in `records'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:251:in `to_a'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/finder_methods.rb:546:in `find_nth_with_limit'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/finder_methods.rb:531:in `find_nth'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/finder_methods.rb:122:in `first'
/var/www/discourse/lib/tasks/user_importer.rake:9:in `block (3 levels) in <top (required)>'
/var/www/discourse/lib/tasks/user_importer.rake:8:in `block (2 levels) in <top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
PG::UndefinedColumn: ERROR:  column users.email does not exist
LINE 1: SELECT  "users".* FROM "users" WHERE "users"."email" = 'edua...
                                             ^
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/patches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/patches/db/pg.rb:90:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:614:in `block (2 levels) in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies/interlock.rb:46:in `block in permit_concurrent_loads'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/concurrency/share_lock.rb:185:in `yield_shares'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies/interlock.rb:45:in `permit_concurrent_loads'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:613:in `block in exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:612:in `block (2 levels) in log'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:611:in `block in log'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract_adapter.rb:603:in `log'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:612:in `exec_no_cache'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql_adapter.rb:599:in `execute_and_clear'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/postgresql/database_statements.rb:79:in `exec_query'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:371:in `select'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:42:in `select_all'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/query_cache.rb:97:in `select_all'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/querying.rb:39:in `find_by_sql'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:667:in `exec_queries'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:546:in `load'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:255:in `records'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation.rb:251:in `to_a'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/finder_methods.rb:546:in `find_nth_with_limit'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/finder_methods.rb:531:in `find_nth'
/var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/relation/finder_methods.rb:122:in `first'
/var/www/discourse/lib/tasks/user_importer.rake:9:in `block (3 levels) in <top (required)>'
/var/www/discourse/lib/tasks/user_importer.rake:8:in `block (2 levels) in <top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'
Tasks: TOP => user_importer:import

Anything i can do on the script to fix it?

I tried the resolution in #6 and it didn't work in my hands. Rather than spend effort debugging this, I think there are now better solutions to add users through the Discourse API (see https://docs.discourse.org).
There are also a few different programs (on GitHub) that help automate the process using the API. For example:
https://github.com/pfaffman/discourse-user-creator
https://github.com/safisher/discourse_create_user
As well as various helpful threads on the Discourse forum:
https://meta.discourse.org/t/creating-user-via-api/36133
https://meta.discourse.org/t/creating-active-users-via-the-api-gem/33133/36
https://meta.discourse.org/t/creating-a-user-through-restful-users-api/9359
@vindia This program was really useful when I first set up my Discourse install. Thank you!

@safisher Thanks for the kind words. I'm not surprised there are now other (and better) ways of adding stuff to Discourse. The script in the repo was made quite some time ago. I will add your links to the README!


implement db support

Hi @igorwojda. Is there a way of running codacy and codefactor checks locally?

I don't think so

Hi @igorwojda. Did you have a chance to review pr? If there are things you want me to fix or improve, please let me know. I'm willing to spend some time.

Hi @igorwojda. Did you have a chance to review pr? If there are things you want me to fix or improve, please let me know. I'm willing to spend some time.

I will rearrange, the code a bit and merge this soom

I will close this PR and resolve conflicts with another.
https://github.com/igorwojda/android-showcase/pull/149


Updated antlr to Version 4.9.3

Hi @kai-baumann , thank's for your PR.  Since the 2.4.0 release is a few weeks away, we will cherry pick your commit on the 2.3 release branch and release a 2.3.1 next week.

Hi @kai-baumann LogicNG 2.3.1 is now published on Maven Central

Thanks.


Update openapi.yaml

Notes/To do's:

[x] Both POST and GET /zelflux/broadcastmessage need to be looked at. Not sure what the request body should look like nor what should be in the ?data=xxxx parameter. Left media type as text/plain and data as a string. May want to also change the example. Left a hex-encoded in the example commented out that will decode to HelloWorld although I am pretty sure that is not the type of data messages to be sent. Description should also be changed as I have left it as The message as I don't know what data should contain in the message.
[x] Same as above with POST and GET /zelflux/broadcastmessagetooutgoing and POST and GET /zelflux/broadcastmessagetoincoming
[x] A better description for GET /zelid/emergencyphrase as I am not sure in what scenerio this would be used.
[x] Did not document both POST and GET /zelcash/submitblock as not sure what hex-encoded data should be in the parameter.
[x] Check both POST and GET /zelcash/createmultisig permissions level as it is set to PUBLIC at the moment but seems it should be at the ADMIN level. Don't think you could create a multisig without knowing if the keypool of the node has the public key/keys of the addresses and only the ADMIN should know this info. If you try to use an address that don't belong to the node it will return with an error.
[x] Did not document GET /zelapps/zelappregister and GET /zelapps/zelapppull not sure if it's functional. Also GET zelapps/zelappexec as I came across errors since I am not sure what to test with in the cmd and env arrays.
[x] Did not document GET /zelcash/zmergetoaddress as I couldn't get it to work.
[x] Correct spelling of the word successfully as of now it stands as succesfully on response message of zelappstart, ...stop, ...restart, ...kill, ...containerremove, ...pause, ...unpause, ...remove, ...imageremove
[ ] Check description for GET /zelflux/dosstate
[ ] Check if format is set right for GET zelapps/zelshare/getfile
[ ] Check jsonrequestobject parameter example for GET /zelcash/getblocktemplate call and make changes if not correct
[ ] Both POST and GET /zelcash/sendmany needs to be looked at as I wasn't able to make the subtractfeefrom parameter work as an array but seems to work as a boolean. Please check in case I am wrong. Left description for array commented out to make it easier to make changes if needed and remember to delete commented description if boolean method is correct.
[ ] Add to available values of the benchmarktype parameter in the /zelcash/zcbenchmark call. Only listed ones I was able to get a successful response.
[ ] List objects for walletconflicts in components section as I couldn't get figure out what the objects were if it did return one in the case of conflicts
[ ] Possibly give reference credit to https://docs.docker.com/engine/api/v1.40/ as most of the descriptions for /zelapps calls are from their docs.

Some Tick Boxes answers:

broadcasting messages is not yet entirely finalised and may not be available via api in the end. Now they are present just for testing purposes. Fluxes do not react to those messages at all, just sort of say message received and display it. Documentation not needed then

standard /zelid/loginphrase goes through many checks. If zelcash is available, mongo, docker, dos state and many more. It serves the purpose of saying that flux is fully operational. Sometimes we want to log in to the node if flux is not fully operation, for example admin wants to log in to fix the node, restart zelcash and so on. In case of some errors, /zelid/loginphrase responds with the error. But /zelid/emergencyphrase always tries to respond with a login phrase to allow logging in.

An example for creation of multisig address. This method shall remain public.

zelcash-cli createmultisig 2 "[\"023ba403d8b555f09912ec51165fb08b432d409f25f0bfce11932d5f0c4cac69c2\",\"0303574570247096bdd9f1e8c827b71856894757b5dcf669277fefbf48c1b73612\"]"
{
  "address": "t3bxSmVGguUuj8GVGU6mR98dCWzpArT2XtS",
  "redeemScript": "5221023ba403d8b555f09912ec51165fb08b432d409f25f0bfce11932d5f0c4cac69c2210303574570247096bdd9f1e8c827b71856894757b5dcf669277fefbf48c1b7361252ae"
}

As an example for hex encoded data of submitblock we can use any available block already present on zelcash chain. So the data is hex of that block.

zelapps calls are still in development so no need for documentation as of now. Will be corrected with calls finalisation

Seems like z_mergetoaddress is still experimental, so probably shall not be even part of Flux.

Spelling of successfully corrected in Flux v0.61

Others:
Yes some calls are duplicate and available on multiple api endpoints but do the same. This was just to make it more convenient according to some logic. Eg. I want to start zelcash, so Flux needs to basicall execut zelcashd so it is flux/zelnode call to make - thus available on /zelnode/ section as its not using a daemon call. But since its like zelcash related I added it to /zelcash/ as well.

Here are some of my notes to zelcash daemon and findings around them when calls were implemented. Since calls are basically the same as zcashes, it touches both zelcash and zcash.

getblock - correct zcash - verbosity is number, error says its not boolean
gettxout - help does not say if includemempool is false or true by default. Default is true
setgenerate help does not show defaul genproclimit
getrawtransaction - verbose is numeric instead of boolean
listreceivedbyaddress does not show optional inlcudeWatchonly + capital
listsinceblock doesnt show default values
listunspent addressses are not shown as optional
sendmany - amounts, substractfeefromamount are objects, missing '' for defaul comment Furthermore address in help is not valid
sendtoaddress doesnt show default '' values for comments
sendfrom - missing '' defaults for comments
settxfee - what is the default value and is it per kb? Does it reflect to z addresses?
z_getbalance does not says that address is required
z_getoperationsresult help wants array but shown string - doesnt show that empty array is default
z_getoperationstatus help wants array but shown string - doesnt show that emtpy array is default
z_listreceivedbyaddress does not say that address is required
z_listunspent - check
z_setmigration wierd symbols
zcbenchmark help is not documented


提取可自定义部分到环境变量

也包括是否启用rss

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


Invoke-DbaDbDataGenerator - Use Min and Max with Get-DbaRandomizedValue

Type of Change

[x] Bug fix (non-breaking change, fixes #6524 )

Changed Get-DbaRandomizedValue to correctly test against "0".

Talked to sander and he will try but is busy today 👍🏼

Thank you, @sanderstad 🙇🏼

Thanks a lot. Will do the changes later today....

OK, looks good now.

boom! 🔥  🚒


flutter build ios -> Archive -> Distribute | Validate -> Found an unexpected Mach-O header code: 0x72613c21

Steps to Reproduce

flutter upgrade master
Build the flutter project for iOS with flutter build ios
Observe no errors
Open XCode with Generic iOS device as target.
Tap Product -> Archive
Watch archive success
Tap on "Distribute App" or "Validate App" on the generated archive.
Observe almost inmediate failure with Found an unexpected Mach-O header code: 0x72613c21

Target Platform:
iOS
Target OS version/browser:
10.2
Devices:
Generic iOS device
Logs
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.10.15-pre.252, on Mac OS X 10.14.6 18G95, locale
    en-NL)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
[✓] Android Studio (version 3.3)
[✓] IntelliJ IDEA Ultimate Edition (version 2018.3.5)
[✓] Connected device (1 available)

• No issues found!

@lifenautjoe did it work right before you did the update? If yes, do you know approximately what was the previous version?

Hi Stanislav.
We updated in the past days to flutter channel master in order to have most of the iOS13 issues fixes. We had been working with android and iOS devices on development mode so far.
We had to regenerate the Podfile due to a warning saying we should.
We noticed the build system changed and as part of it, it now used the use_frameworks! config.
It broke one extension we were using for push notifications, but we updated the Podfile config of it to also use_frameworks! and removed the manually embedded frameworks and libraries of it. It worked like a charm and built for both iOS and android.
We successfully released the app to Android, and now we're trying to do the same for iOS with no success and the mentioned error.
I've tried removing the use_frameworks! from the Podfile and reverting to the old way we manually linked libraries to the extension, it all builds and runs but same issue when archiving and validating / uploading.
Here's the Podfile if it helps
# Uncomment this line to define a global platform for your project
platform :ios, '10.2'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def parse_KV_file(file, separator='=')
  file_abs_path = File.expand_path(file)
  if !File.exists? file_abs_path
    return [];
  end
  generated_key_values = {}
  skip_line_start_symbols = ["#", "/"]
  File.foreach(file_abs_path) do |line|
    next if skip_line_start_symbols.any? { |symbol| line =~ /^\s*#{symbol}/ }
    plugin = line.split(pattern=separator)
    if plugin.length == 2
      podname = plugin[0].strip()
      path = plugin[1].strip()
      podpath = File.expand_path("#{path}", file_abs_path)
      generated_key_values[podname] = podpath
    else
      puts "Invalid plugin specification: #{line}"
    end
  end
  generated_key_values
end

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  # Flutter Pod

  copied_flutter_dir = File.join(__dir__, 'Flutter')
  copied_framework_path = File.join(copied_flutter_dir, 'Flutter.framework')
  copied_podspec_path = File.join(copied_flutter_dir, 'Flutter.podspec')
  unless File.exist?(copied_framework_path) && File.exist?(copied_podspec_path)
    # Copy Flutter.framework and Flutter.podspec to Flutter/ to have something to link against if the xcode backend script has not run yet.
    # That script will copy the correct debug/profile/release version of the framework based on the currently selected Xcode configuration.
    # CocoaPods will not embed the framework on pod install (before any build phases can generate) if the dylib does not exist.

    generated_xcode_build_settings_path = File.join(copied_flutter_dir, 'Generated.xcconfig')
    unless File.exist?(generated_xcode_build_settings_path)
      raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"
    end
    generated_xcode_build_settings = parse_KV_file(generated_xcode_build_settings_path)
    cached_framework_dir = generated_xcode_build_settings['FLUTTER_FRAMEWORK_DIR'];

    unless File.exist?(copied_framework_path)
      FileUtils.cp_r(File.join(cached_framework_dir, 'Flutter.framework'), copied_flutter_dir)
    end
    unless File.exist?(copied_podspec_path)
      FileUtils.cp(File.join(cached_framework_dir, 'Flutter.podspec'), copied_flutter_dir)
    end
  end

  # Keep pod path relative so it can be checked into Podfile.lock.
  pod 'Flutter', :path => 'Flutter'

  # Plugin Pods

  # Prepare symlinks folder. We use symlinks to avoid having Podfile.lock
  # referring to absolute paths on developers' machines.
  system('rm -rf .symlinks')
  system('mkdir -p .symlinks/plugins')
  plugin_pods = parse_KV_file('../.flutter-plugins')
  plugin_pods.each do |name, path|
    symlink = File.join('.symlinks', 'plugins', name)
    File.symlink(path, symlink)
    if name == 'flutter_ffmpeg'
        pod name +'/full-gpl-lts', :path => File.join(symlink, 'ios')
    else
        pod name, :path => File.join(symlink, 'ios')
    end
  end
end

# Prevent Cocoapods from embedding a second Flutter framework and causing an error with the new Xcode build system.
install! 'cocoapods', :disable_input_output_paths => true

target 'OneSignalNotificationServiceExtension' do
  pod 'OneSignal', '>= 2.9.5', '< 3.0'
  use_frameworks!
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
      config.build_settings['SWIFT_VERSION'] = '5'
    end
  end
end

Have been looking and trying solutions all day for this error from traditional iOS development, no success.

https://stackoverflow.com/questions/33076819/found-an-unexpected-mach-o-header-code-0x72613c21-in-xcode-7
https://github.com/realm/realm-cocoa/issues/4401
https://forums.developer.apple.com/thread/50969

Our code no longer builds on stable (plus its entirely broken for iOS), so we're blocked from releasing...

After a whole day of suffering and questioning our decision to use Flutter, I've come up with a temporary way to upload the archive...

Going back to flutter channel stable
Being unable to build the project with error Frameworks/Flutter.framework: Permission denied and fixing it by manually patching the flutter backend ios with https://github.com/flutter/flutter/issues/40146#issuecomment-546414805
Seeing the project built but failing to validate/upload with the same Mach-O
Reverting back to our old Podfile, the one before the new build system, the one that does NOT use use_frameworks nor the use module headers config
Seeing that still, the project built and ran but failed the Mach-O validation
Reverting back the ios/Runner.xcodeproj/project.pbxproj, the one before the new build system.
Build -> Archive -> Distribute -> Success.

The Podfile and project.pbxproj changes can be seen here

https://github.com/OkunaOrg/okuna-app/commit/1181d6bff965be2b85b77387acf87d54aba6dc45
https://github.com/OkunaOrg/okuna-app/commit/738ae9c9a5b7a34a8ec4d12b57eb701465de99f6
https://github.com/OkunaOrg/okuna-app/commit/d2a79c1acf6156979bc765eeb5d9fae491f8b953

That pointed out, I have little doubt there's something very wrong on the new build system and which is causing this issue.

Your Podfile is missing install! 'cocoapods', :disable_input_output_paths => true which would allow you to use the new build system. https://github.com/flutter/flutter/issues/20685#issuecomment-542322890

Also, this is the first I've seen of https://github.com/flutter/flutter/issues/40146 happening for a non-add-to-app application.  I was going to refer you to https://github.com/flutter/flutter/issues/40146#issuecomment-530470137 where I mention that it was related to using add-to-app and thus wouldn't be hotfixed but I see you already added a reaction to that comment...
I wonder what's different about your setup where you are seeing it in a non add-to-app scenario.

The issue was happening with the Podfile I posted above. That Podfile was generated by removing our old Podfile as mentioned in a warning after changing and upgrading on flutter master. It contained the install! 'cocoapods', :disable_input_output_paths => true statement.
I switched back to stable branch, reverted the new build system changes, the new Podfile and xcode project config, fixed the error with the permission denied for the Flutter.framework and built and got distributed successfully.
Issue is of course, new build system which should roll out I imagine soon to stable, will break this again...
In regards to our custom setup, it's just 3 changes to the as seen on the Podfile above.

We append to the name of a library to retrieve a particular distribution of it with

    if name == 'flutter_ffmpeg'
        pod name +'/full-gpl-lts', :path => File.join(symlink, 'ios')
    else
        pod name, :path => File.join(symlink, 'ios')
    end

We add an specific version range for our push notifications extensions

target 'OneSignalNotificationServiceExtension' do
  pod 'OneSignal', '>= 2.9.5', '< 3.0'
  use_frameworks!
end

We ensure min swift version is 5

      config.build_settings['SWIFT_VERSION'] = '5'

It all works with flutter run --release and development on both virtual and physical iOS device. It builds successfully, issue is when distributing | validating with the app store.

Issue is of course, new build system which should roll out I imagine soon to stable, will break this again...

There is no build system change migration on any branch.  If you regenerate the Podfile you will see install! 'cocoapods', :disable_input_output_paths => true present in the new generated Podfile.  That template change was present in 1.7.4 and made it to stable in July 2019.
I know you're seeing multiple issues, but to at least fix the new build system problem, follow the directions at https://github.com/flutter/flutter/issues/20685#issuecomment-542322890.  The legacy Xcode build system has been deprecated the new build system should be adopted.

Your Podfile is missing some of your build configurations: Debug-production, Debug-development, Release-production, Release-development

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

The OneSignalNotificationServiceExtension "Embed Frameworks' Build Phase (CocoaPods didn't add it, looks like it was added in https://github.com/OkunaOrg/okuna-app/commit/ced3dd13442b9a0dc594d03d54f6275f55c70fe4) is embedding libPods-Runner.a instead of just linking on it since it's a static library.  I believe that's the unexpected Mach-O header code.  When I delete the extension the validation error goes away.

This doesn't look like a Flutter issue, it looks related to your extension and CocoaPods.

I'm going to close this, feel free to file another issue or comment on this one if you think there's a Flutter bug to track down here.

Hi Jenn (@jmagman ), thanks for coming back. I tried your suggestion of linking the library instead of embedding it but it fails to be built and therefore validating and uploading to the store.
What is even more strange is that reverting to the stable version settings and Podfile works both with linking the library instead of embedding it.

I don't think this is a Flutter bug.  I deleted your extension, which has no Flutter bits, and am no longer see the archiving error.
I don't know why your extension doesn't compile.  You may be hitting an issue with one of your pods, or the way your linking is set up, your build phases, your Podfile, or maybe something with CocoaPods.  You may want to try posting your issue to Stack Overflow.

Doesn’t being unable to build a Flutter app with an extension classify as a
flutter bug ?
It’s not a runtime error. The extension works perfectly when testing on
devices across all configurations.
It’s a build error, from Flutter.
Most apps need extensions, this one is for basic push notifications and
added through the default steps of Xcode with no change other than adding
the code ( which once again works perfectly but fails to validate )z
On Tue, 29 Oct 2019 at 22:41, Jenn Magder<EMAIL_ADDRESS>wrote:

Closed #43499 https://github.com/flutter/flutter/issues/43499.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/43499?email_source=notifications&email_token=ADBFXZJDC3X4PD73EY5TW6LQRCUXXA5CNFSM4JFCOWJ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOUQSUCMQ#event-2753904946,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADBFXZKXJFINUSLV6JQJJXTQRCUXXANCNFSM4JFCOWJQ
.

You can build a Flutter app with an extension, and many people have.  This seems to be an issue with your specific extension.  You are embedding a static library in your extension build phase instead of just linking on it, which causes an unexpected Mach-O header code validation error when it's validated with Xcode.

I tried your suggestion of linking the library instead of embedding it but it fails to be built and therefore validating and uploading to the store.

It’s a build error, from Flutter.

What is the compilation error that makes you think it is related to Flutter and not something else in the way you have built your extension?  The extension isn't embedding or linking on any Flutter frameworks.

Hey, any updates on this one? We actually have the same problem.
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15.1 19B88,
    locale en-DE)

[✓] Android toolchain - develop for Android devices (Android SDK version
    29.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 11.2)
[✓] Android Studio (version 3.4)
[✓] VS Code (version 1.40.0)

Hi @EddieRietz , Unfortunately , I was told this was not a Flutter problem so don't expect the Flutter team to provide a solution anytime soon.
The extension I added had no custom code that could have caused this. I'm still convinced it's an  error generated by Flutter's build system.
Since yesterday I've seen some more people complaining about this on the OneSignal repository and some Yandex Map plugin which also used an extension.
Perhaps if we can get enough attention here, they'll re-open the ticket.

@lifenautjoe I believe the Xcode validation Mach-O header error because there's an embedded static library in your extension (static libraries need to be linked, not embedded).  If you can reproduce this issue without linking on a static framework, I'd like to take a look.  "It won't compile without that change" perhaps points to some other linker issue.  If those linker issues are related to Flutter (and not a non-Flutter pod you added to your extension target), I'd also like to take a look.

@EddieRietz Can you create a new issue with an app that reproduces this issue, and the output of flutter doctor -v?

@EddieRietz were you able to work around this?  I don't see a new issue from you.  If I could just see your Xcode project files that might be enough, if you can't share the app that is reproducing this.

i get same error, any help? I use one signal library

We found a "hack" for this, like many other ones we use to keep our Flutter app alive across flutter upgrades and bugs.

Build the app (flutter build ios) with the Pods_Runner.framework marked as Embed & Sign

Once it's built. Go to the same place and set the Pods_Runner.framework to Do Not Embed.

Go to Product -> Archive -> Submit the archive and it will all work as expected.

Given the amount of people experiencing the same issues, I'm convinced there's an issue still here to be addressed at the Flutter level. Being on the fast-paced, short-lived, startup-life, we unfortunately have no time nor engineers to dig into the Flutter build system and try to figure things out, other than just hacking our way through.

We found a "hack" for this, like many other ones we use to keep our Flutter app alive across flutter upgrades and bugs.

Build the app (flutter build ios) with the Pods_Runner.framework marked as Embed & Sign

Once it's built. Go to the same place and set the Pods_Runner.framework to Do Not Embed.

Go to Product -> Archive -> Submit the archive and it will all work as expected.

Given the amount of people experiencing the same issue, I'm convinced there's an issue still here to be addressed at the Flutter level. Being on the fast-paced, short-lived, startup-life, we unfortunately have no time nor engineers to dig into the Flutter build system and try to figure things out, other than just hacking our way through.
Hope this helps someone on a similar situation.

@lifenautjoe You might want to file an issue against CocoaPods, they might be able to help figure out why Pods_Runner has an unexpected Mach-O header.

We found a "hack" for this, like many other ones we use to keep our Flutter app alive across flutter upgrades and bugs.
1. Build the app (flutter build ios) with the **Pods_Runner.framework** marked as **Embed & Sign**

1. Once it's built. Go to the same place and set the **Pods_Runner.framework** to **Do Not Embed**.

1. Go to Product -> Archive -> Submit the archive and it will all work as expected.

Given the amount of people experiencing the same issue, I'm convinced there's an issue still here to be addressed at the Flutter level. Being on the fast-paced, short-lived, startup-life, we unfortunately have no time nor engineers to dig into the Flutter build system and try to figure things out, other than just hacking our way through.
Hope this helps someone on a similar situation.

Thanks! This work for me!

We found a "hack" for this, like many other ones we use to keep our Flutter app alive across flutter upgrades and bugs.

Build the app (flutter build ios) with the Pods_Runner.framework marked as Embed & Sign

Once it's built. Go to the same place and set the Pods_Runner.framework to Do Not Embed.

Go to Product -> Archive -> Submit the archive and it will all work as expected.

Given the amount of people experiencing the same issue, I'm convinced there's an issue still here to be addressed at the Flutter level. Being on the fast-paced, short-lived, startup-life, we unfortunately have no time nor engineers to dig into the Flutter build system and try to figure things out, other than just hacking our way through.
Hope this helps someone on a similar situation.

When i do that, i get a different error, and the fix of that error is to set to 'NO' the buid option : Always Embed Swift Standard libraries on the onesignal target, i think that by doing that the onesignal will no longer works as i would have to rebuild in the xcode (it alreays rebuild anyway when i click on archive) is that right?

Is it a static framework?  See the note in https://flutter.dev/docs/development/add-to-app/ios/project-setup#embed-the-frameworks.

Important: Plugins might produce static or dynamic frameworks. Static frameworks should be linked on, but never embedded. If you embed a static framework into your application, your application is not publishable to the App Store and fails with a Found an unexpected Mach-O header code archive error.

@lifenautjoe i have tried your solution still not working same error
2020-03-04 07:44:35 +0000  Failed to generate distribution items with error: Error Domain=DVTMachOErrorDomain Code=0 "Found an unexpected Mach-O header code: 0x72613c21" UserInfo={NSLocalizedDescription=Found an unexpected Mach-O header code: 0x72613c21, NSLocalizedRecoverySuggestion=}

@mohdkhmais

Is it a static framework? See the note in https://flutter.dev/docs/development/add-to-app/ios/project-setup#embed-the-frameworks.

For me, I tried every solution even the one above of @lifenautjoe  and it really worked but then I tried to only put the PODS framework to "Do Not Embed" and it worked with no errors.


fix(nuxt): do not include <NuxtWelcome> when building

🔗 Linked issue
resolves https://github.com/nuxt/nuxt/issues/29838
📚 Description
This should avoid bundling <NuxtWelcome> - though we can also investigate why it's being included in the main bundle rather than as an async chunk....

Summary by CodeRabbit

New Features

Introduced conditional logic for the NuxtWelcome component, enhancing component management based on user settings.
Maintained the addition of components like NuxtLayout and NuxtErrorBoundary.

Documentation

Added comments for clarity on handling experimental features and component registration.

There's quite a few things that need to be fixed with how we chunk when selectiveClient is enabled. But first i need to finish the rework of island

happy to skip this for now if you want as it's a bit of an edge case.

We can merge it, but i'm pretty sure there's many other components that are probably also included in the bundle


Add temporal coupling post & my name to fan section

Hi @yegor256, I recently read a lot of your posts and I’m kinda motivated to write my own one. The following post talks about “NO for temporal coupling design” and since I come from Android dev background, the post is a bit Android n Kotlin-ish. So I think it’ll be nice and cool if this OOP-related post could be highlighted on this EO site, though I’m not sure if it deserves enough :)
https://proandroiddev.com/stop-crafting-your-time-bomb-39f2d26987e0
Also, I add my name to the fan section. Kindly for your review. Thanks!

@ErickSumargo this pull request is too small, just 3 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @yegor256/z please review this and merge or reject

@ErickSumargo thanks!


Removing comma after after rest element

Breaks for me using Babel.
Is also not allowed in the spec, so worth removing regardless of my issue.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Trailing_commas#Illegal_trailing_commas

Regarding this issue, I will revise it uniformly in the near future


Bull stuck into 'Loading' cause missing .js file

When I develop in my local machine without docker it's work seamless.
But when I move to production server, Bull-board is stuck on loading,
After I inspect, I know cause I have API Gateway inside my production server
Here I attached the screenshot below
I access with http://mydomain.com:8000/serviceName/queue
https://pasteboard.co/HDl7oBQ67cbS.png
I think bull cant resolve the asset file
https://pasteboard.co/0YtAQp4KY4IU.png
Btw I am using bull-board/koa
I mean there is an API for change the static file routes
static monitor(basePath: string): KoaAdapter {
		const serverAdapter = new KoaAdapter();
		serverAdapter.setBasePath(basePath);

		createBullBoard({
			queues: Array.from(queuesList.values()).map(
				(queue) => new BullAdapter(queue)
			),
			serverAdapter: serverAdapter,
		});

		return serverAdapter;
	}

I already look into the source file, but cant find one that suitable for my use case
https://pasteboard.co/Nnx5fNp3zQUz.png

Hi, thank you for reporting this issue.
Looks like it is related to your setup.
Let's try to debug.

Do you have the static assets inside the docker?
The html contains <base> tag, what its value?
When you call serverAdapter.setBasePath(basePath);, what is the value of basePath?
What is the path that the board mounted in?

Ping?

I have the same issue when using the bull-dashboard and the dashboard is behind a gateway.  I am using express adapter.
It works fine if I directly access dashboard on my local environment (http://localhost:3000/v1/xxxx/admin/queues/).
But when accessing the same through gateway, I get Loading... page. (http://localhost:9000/dashboard/v1/xxxx/admin/queues). I have a rule in Gateway that will replace the path /dashboard with '' (empty string).

@yogeshattwic this issue is not related to bull-board, you probably didn't configured your reverse proxy properly, therefore, static assets are not loading.

@felixmosh - I have similar set up for swagger and that is working fine. This is what I see in my html response when I access http://localhost:9000/dashboard/v1/xxxx/admin/queues
<!DOCTYPE html>

        <meta charset="utf-8" />
        <meta name="viewport" content="width=device-width,initial-scale=1,shrink-to-fit=no" />
        <meta name="robots" content="noindex" />
        <base href="/v1/xxxx/admin/queues" />
        <title>Bull Dashboard</title>
        <link rel="alternate icon" type="image/png" href="/v1/xxxx/admin/queues/static/favicon-32x32.png" />
        <link rel="icon" type="image/svg+xml" id="fav-logo" href="/v1/xxxx/admin/queues/static/images/logo.svg" />
        <link href="https://fonts.googleapis.com/css2?family=Ubuntu:wght@300;400;500&display=swap" rel="stylesheet" />
        <link href="/v1/xxxx/admin/queues/static/main.d479e4cc3d1250c7da62.css" rel="stylesheet" />

Loading...

getting 404 for loading all those static assets files. You are right that this is not bull-board issue. I am missing something trivial in my setup.

Hello, any update on this one? I am having the same issue when the bull-board is stuck on "Loading..."

@yogeshattwic What version of bull-board do you use?

@felixmosh - I am using bull-board api and express version 3.11.1. Even though I have not resolved my main issue with this, I figured an alternative way since my bull dashboard is inside a service that is running in Kubernetes pod. I was able to use port-forward to access the service in pod.

@yogeshattwic are you using koa? if not, please open a new issue.
Please try to update bull-board to v4.2.2.

@felixa1996 any update regarding my last questions?

sure, I will try it out @yogeshattwic

For me, it was the fact that I had
serverAdapter.setBasePath('/api/admin/queues');
and then in my server file
app.use('/admin/queues', buildBullBoard())
Having these routes be mismatched caused the asset url requests to go to the incorrect address.

I'm closing this issue, feel free to reopen it if needed.


chore(grafana): Rework the documentation for a release instead of from source.

Here's a preliminary set of changes for the Grafana setup.

Changed it to downloading and installing zipped contents instead of requiring development tooling.
Removed the Docker Compose setup instructions, because they are predicated on the whole development workflow to work.
Removed the development mode callout and replaced it with explicit loading of the unsigned plugin. User's don't need to run their whole Grafana instance in development mode to load unsigned plugins.

Describe your proposed changes here.

[ ] Signed the InfluxData CLA
(if necessary)
[ ] Rebased/mergeable

Thanks @brettbuddin!


Python 3.11: re.error: global flags not at the start of the expression at position

Python 3.11 expect (?i) to be at begging of regex:
abc: /(?i)def/
But lark probably contcatenate several regexes. So it leads to
abc: /(?i)def|(?i)qwe/
Second (?i) flag to be not at the begging of regex. So it raises exception and fail

That's unfortunate!
I think the only solution is to raise an error for Python 3.11 and up.

It is strange: I cannot reproduce it anymore.
Probable lark grammar was wrong

The Python documentation agrees with you: https://docs.python.org/3/library/re.html

Changed in version 3.11: This construction can only be used at the start of the expression.

So, it's strange that you can no longer reproduce it!


Random panics when modifiying hmtl templates

Hello,
When I serve file via gutenberg.exe serve I get panics when I update html templates in the templates/ folder. The behavior is however not consistent.  I will add more precise information in this issue as soon I find them.
Here is the error message :
thread '<unnamed>' panicked at 'this crate accidentally accepted 0-sized slices originally but this was since discovered as a soundness hole, it's recommended to use the `from_bytes` function instead', src\libcore\o
ption.rs:819:4

I am using Windows 10 64 bits Creators' Update

Looks like it's an issue from the ws crate: https://github.com/housleyjk/ws-rs/issues/177

I'll reopen it so I don't forget it


Support for ruby 2.6+

When trying to upgrade to ruby 2.6, I encounter the following error immediately upon boot up of guard.
Error: Unknown Ruby version 2.6 found in `.ruby-version`.
Supported versions: 2.2, 2.3, 2.4, 2.5
18:14:16 - ERROR - The following exception occurred while running guard-rubocop: /home/jason/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/json-1.8.6/lib/json/common.rb:155:in `initialize' A JSON text must at least contain two octets! (JSON::ParserError)

This seems to come from a change in how JSON.parse handles empty values.

The ruby version conflicts were resolved by upgrading rubocop.
The JSON error was part of a long chain. It seems to come from a blank file name on initialization being passed around. I have made changed in the code to get it working again. I will make sure it is the proper implementation and tested. Likely, I'll have a PR for this small fix.

Ignore me. Just needed to upgrade Rubocop. Sorry for the unneeded notifications!


Key resolver doesn't handle shift characters properly.

vim-mode: 0.29.0
atom: 0.175.0
I noticed this behavior quite some time ago (atom 0.130.0 ish?) but I'm just getting around to making this issue now.
It seems that the ambiguous key resolver is not dealing with the shift key correctly.
Correct behavior:
Suppose I add the following to my keymap:
'.editor.vim-mode:not(.insert-mode)':
  'd w w': 'command-palette:toggle'

(Note: you'd have to be crazy to do this, but it illustrates the point well.)
Now I go to a piece of text and type [d w w]. The command palette opens!
Importantly however, if I just type [d w] and wait for a moment, it deletes the following word, just as one would expect! The resolver is doing its best to let me run my [d w w], times out, and deletes a word instead.
This illustrates the correct behavior of the resolver.
The bug:
NOW if I change my configuration to this:
'.editor.vim-mode:not(.insert-mode)':
  'd w !': 'command-palette:toggle'

Now (in command mode in the editor), I type [d w shift+1] the instant I hit shift to make an exclamation mark, vim-mode fires the delete-word. What's more is that the key resolver will actually show my custom "command-palette:toggle" command in the list of potential commands, listing [dw (partial)] in the "Key Binding Resolver:" field at the top of the box.
It would seem that vim-mode's key binding resolver is interpreting the shift key event as its own key, not finding any commands for that in the search space, and taking the last unambiguous action that it knows how to do.
The above scenario is pretty absurd, but for a real life example, this is trampling my vim-surround plugin's keybindings. Specifically in visual mode using vim surround [s "] SHOULD surround the selection in double quotes, but instead (on shift) triggers visual mode's [s] which executes vim-mode:change. Rather than waiting for the shift+' it instantly falls through to the change command.
Thanks, and lemme know if I can provide any more information!

This sounds like what we discovered in #403. It is not a bug with vim-mode, but one in atoms keymap see atom/atom-keymap#65 for more details.

Ah! That bug definitely seems to cover this behavior!


system level "stop the line"

#1328 already calls for time-based allow/disallow of new Freight production and promotions to individual stages.
In a recent conversation with a user, some interest was expressed in a system-level "stop the line" button that might be applied, for instance, in the case of an org-wide code freeze.
If this were implemented at the system level, I couldn't see not implementing it at the Project, Warehouse, and Stage levels also.
"Stop the line" is a tad dramatic, but gets the point across. Maybe we call it "pause."
I'm not committing to this feature yet, but wanted to get feedback from @jessesuen @christianh814 and the community as well.

Re-opening this because it was brought up in discussion of #1328

we need this

Most companies I talked with have some kind of change windows or freezes, including ours. So I would appreciate the option.
It would also require an opt-out for specific applications for hotfixes. Alternatively, it could require another approval step in case of a deployment during a certain time window.


cargo-crev: 0.25.3 -> 0.25.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/cargo-crev/versions.
meta.description for cargo-crev is: A cryptographically verifiable code review system for the cargo (Rust) package manager
meta.homepage for cargo-crev is: https://github.com/crev-dev/cargo-crev
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.25.4 with grep in /nix/store/4b8y0180axq3aqgr96miqzxsi3j5rc3s-cargo-crev-0.25.4
found 0.25.4 in filename of file in /nix/store/4b8y0180axq3aqgr96miqzxsi3j5rc3s-cargo-crev-0.25.4

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
cargo-crev

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/4b8y0180axq3aqgr96miqzxsi3j5rc3s-cargo-crev-0.25.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cargo-crev https://github.com/r-ryantm/nixpkgs/archive/dfbd60ca56c838698bc1fc54b308477704a37187.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/dfbd60ca56c838698bc1fc54b308477704a37187#cargo-crev

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4b8y0180axq3aqgr96miqzxsi3j5rc3s-cargo-crev-0.25.4
ls -la /nix/store/4b8y0180axq3aqgr96miqzxsi3j5rc3s-cargo-crev-0.25.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

cargo-crev

Maintainer pings
cc @B4dM4n @matthiasbeyer for testing.

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

1 package built:

cargo-crev


Self-hosted version: Unable to access with domain name

Always get redirected to
http://localhost:8000/schemadesigner/ShowTable?projectId=00000000-0000-0000-0000-000000000000&tableName=users

Same as here.
Could we edit dockerfile and build docker image?


Added support unresolved socket addresses

Currently trying to connect to the tor network causing DNS resolution through the DNS server specified in the network configuration. In this PR added support unresolved socket addresses to support .onion resources

Hey,
you should be able to do this with a custom DnsResolver.
See https://github.com/TooTallNate/Java-WebSocket/blob/master/src/main/java/org/java_websocket/client/DnsResolver.java and #906
Best regards,
Marcel

I think the problem with DnsResolver is that it returns an InetAddress, not an InetSocketAddress.
If I understand correctly, InetAddress doesn't support unresolved addresses, only InetSocketAddress does that (using createUnresolved).

Hey, you should be able to do this with a custom DnsResolver. See https://github.com/TooTallNate/Java-WebSocket/blob/master/src/main/java/org/java_websocket/client/DnsResolver.java and #906
Best regards, Marcel

Yes, DnsResolver must return InetAddress, so there is no way to create an unresolved address.
It  looks logical that if dnsResolver == null, then it will be created unresolved address. Also there is no BC here
conn = new WebSocketClient(serverUri, httpHeaders) {...}
conn.setDnsResolver(null);

My bad.
Changes look good for me, what do you think @PhilipRoman?

It's not the most elegant solution, but I think it should be merged.


Add center_to_screen option to be used with limit_to_screen

This adds new center_to_screen configuration option which will center the grid to the screen when using limit_to_screen. This is done by calculating screenMargin which is used in calculating the position for the placeholder / items.

I'm going to have to try this to get an idea of what the change does, if that's OK? I think I get it but I'd like to see it for myself first. What col_width/row_height values are you using?

So what this does is that we have the grid set to fill the available space and col_width / row_height are set to 162/136 with margin being 16. And we are using the limit_to_screen so the grid width naturally is not always evenly dividable with the 162+margin so without this feature the grid items would only be centered to the view when the grid width is evenly dividable with 162+margin. With this feature the grid is always center when center_to_screen is set to true.

I pushed the change with the refactoring for the re-positioning of the items. This was my original implementation anyway, but decided to go with the less code replication in the end.

I made a couple little changes, but it's in master now. Thanks 👍

Thanks! Also thanks for this nice library, we tried pretty much all grid related libraries and all others were really buggy and most of them tried to do too much like provide scrolling etc.

Hi, would it be possible for you to make new release with this feature? Since I see that there still hasn't been new release after adding this and we are getting close to releasing our app so would be nice to have only released package versions in the app when we ship it. The feature has been working nicely for us, been using it through our own custom build.

Yes! Apologies, I'll try to get it out this weekend

Released in version 2.1.0


Merge v1.0.0

Description
v1.0.0 has been a preparation branch to make a number of changes for v1.0.0 while allowing changes to made to main.
This PR merges v1.0.0 and main together

A couple more PRs to merge

Need any help reviewing?

@jjshoots That'd be great if you have some time to spare. I'll have to go through it at some point either way, but any bug you find, I won't have to find, so it's definitely helpful

Thanks @jjshoots, it's only a small one 😅 Let me know if there is any part that doesn't make any sense

Missing torch and tensorflow 3.12 support


Flexibly specify the ELBO function and initialization

I'd like to be able to flexibly specify alternative version of the ELBO function for stripe 82, the galsim benchmarks, and ordinary SDSS data.  Right now, the DeterministicVI ELBO is hard coded in a variety of places.
@jeff-regier , you have strong opinions about how to organize things, so I think it's best to let you handle this.  The ideal solution in my opinion would be a user-specifiable callback taking an ElboArgs and returning an optimized ELBO.

I'd rather remove the hard coded settings, and make them variables in ElboArgs, rather than making multiple versions of the source code. Then you'd initialize ElboArgs differently depending on whether your running on stripe 82 or galsim or SDSS. (Since the point of the galsim/stripe82 benchmarks is to validate the code that we're using in production, we want to minimize differences between the environments.) What hard coded settings need to vary depending on the dataset?
It would be even better if we could make the galsim data look so much like the actual SDSS data that we didn't even need different settings.

Sorry, I think I wasn't clear.  I would like to run stripe 82 and the galsim data with my new PSF ELBO, which is both different from DeterministicVI.elbo and requires data not currently in ElboArgs.
Here's how it seems to work now.  The stripe 82 validation function calls ParallelRun.infer_field, which calls ParallelRun.one_node_infer, which calls ParallelRun.parallel_infer, which then calls ParallellRun.one_node_single_infer, which calls DeterministicVi.infer_source, in which the call to DeterministicVi.elbo is hard coded.
The Galsim benchmark calls its own parallel_inference function, which calls ParallelRun.parallel_infer, and from there follows the path above unless it's running joint inference.  If it is, it calls one_node_joint_infer from the Cyclades script, which itself hard codes the call to DeterministicVI.elbo.
On actual data, you call infer_box or infer_rcf, both of which call ParallelRun.one_node_infer and so enter the first chain of functions.
It would be pretty nice if one could somehow specify more flexible initialization and elbo functions without touching all of the functions in this chain.  (You can see the unit tests to see what is necessary.)  It will be especially useful going forwards if I (or other people) are using Celeste as a platform for experimenting with new algorithms and not just a catalog generator.
It also seems to me that perhaps this whole setup could be simplified and clarified some, but that's more up to you.

I didn't realize this before, but you didn't implement this for one_node_joint_infer.  I'll re-open the issue as a placeholder until you get a chance to do that.

I'm working on it but let's make it a new issue. I already spent too long on this one :-(


forwardport  [Monitoring V2] Rebase rancher-monitoring to kube-prometheus-stack 14.x.x

forward port of : https://github.com/rancher/rancher/issues/29871

After an offline discussion, closing this as we will not be validating chart changes separately for master-head as the changes to dev-v2.6 are automatic.


Update Composer dependencies (2024-06-26-00-18)

Visual regression test passed!
View the visual regression test report


Generate text files with lists of chores grouped by tag

After #33.

[ ] Read all active chores with or without alarms
[ ] Keep this data in a defaultdict(list) of tags (keys) and chores (values)
[ ] Create a text file for every tag
[ ] The file location should be configurable (e.g. to store in a Dropbox folder, for instance)

This issue has become obsolete. See #135.


Fixed Header Position issue Android 4.1 - 4.2

Fixed position headers aren't taking the translate position upon opening the menu.
The menus stay in their left:0 position.
This behavior can even be demonstrated using the http://mmenu.frebsite.nl/ site.

Could you show me a screenshot because i'm not sure what you mean.


Feat: Series.shift Pyarrow Backend Implementation

What type of PR is this? (check all applicable)

[ ] 💾 Refactor
[x] ✨ Feature
[ ] 🐛 Bug Fix
[ ] 🔧 Optimization
[ ] 📝 Documentation
[x] ✅ Test
[ ] 🐳 Other

Related issues

Related issue #
Closes #

Checklist

[ ] Code follows style guide (ruff)
[ ] Tests added
[ ] Documented the changes

If you have comments or can explain your changes, please do so below.

thanks @mfonekpo  - could you put a descriptive title please?

thanks @mfonekpo  - could you put a descriptive title please?

Yes Marco. Done.

thanks @mfonekpo - could you name the test so it ends with _test.py please? else it won't run

thanks @mfonekpo - could you name the test so it ends with _test.py please? else it won't run

Ohhhh....how did I miss that.

Alright then.
On Thu, 25 Jul 2024, 06:26 Francesco Bruzzesi, @.***>
wrote:

@.**** commented on this pull request.
In narwhals/_arrow/series.py
https://github.com/narwhals-dev/narwhals/pull/590#discussion_r1690834396
:

def shift(self, n: int) -> Self:

   pc = get_pyarrow_compute()

   return self._from_native_series(pc.shift(self._native_series, n))

This might end up being not so straightforward after all. We should
manually slice the original array and build the new one, this will also
be dependent on the sign of n
—
Reply to this email directly, view it on GitHub
https://github.com/narwhals-dev/narwhals/pull/590#pullrequestreview-2198339943,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOA4GJDXMJF737IFUBBU7QTZOCEA7AVCNFSM6AAAAABLKD7LZSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDCOJYGMZTSOJUGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

There is room for growth, right? Thank you. Is it ok? because you said it
is out of interest. What do I do?
On Sun, Jul 28, 2024 at 2:09 PM Marco Edward Gorelli <
@.***> wrote:

@.**** commented on this pull request.
In narwhals/_arrow/series.py
https://github.com/narwhals-dev/narwhals/pull/590#discussion_r1694244426
:

   # This condition shifts the series by n positions.

   if n > 0:

       # If n is positive, prepend nulls and truncate the end

       shifted_chunks = [pa.array([None] * n, type=dtype)] + [

           chunk.slice(0, len(chunk) - n) for chunk in chunks

       ]

   elif n < 0:

       # If n is negative, append nulls and truncate the start

       shifted_chunks = [chunk.slice(-n, len(chunk) + n) for chunk in chunks] + [

           pa.array([None] * -n, type=dtype)

       ]

   else:

       # If n is 0, return the original series

       shifted_chunks = chunks

cool, thanks - I'm just a bit surprised, as it looks a bit more advanced
than other work you've submitted. if you figured this all out, then well
done 🙌
—
Reply to this email directly, view it on GitHub
https://github.com/narwhals-dev/narwhals/pull/590#discussion_r1694244426,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOA4GJGVBBK57PHKQ75XC43ZOTUQXAVCNFSM6AAAAABLKD7LZSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMBTGQ4DKOBYGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

yup, definitely room for growth :) it's OK, if you add the test I suggested and it passes, then it should be fine

Thanks, I will!
On Sun, Jul 28, 2024 at 2:56 PM Marco Edward Gorelli <
@.***> wrote:

yup, definitely room for growth :) it's OK, if you add the test I
suggested and it passes, then it should be fine
—
Reply to this email directly, view it on GitHub
https://github.com/narwhals-dev/narwhals/pull/590#issuecomment-2254527963,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOA4GJGEKAN6PIUI3FGRY3DZOT2AZAVCNFSM6AAAAABLKD7LZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGUZDOOJWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you Marco, I have taken note of the points you listed. should I
refactor it to meet the standard?
On Wed, Aug 7, 2024 at 2:45 PM Marco Edward Gorelli <
@.***> wrote:

@.**** approved this pull request.
I've added a commit to get this through
A bit of general feedback:

in tests, you should construct expected explicitly, without any
logic. The test case I handed you was like this, there was no need to
modify it
the implementation for shift wasn't quite right. I'd pointed you to
the solution (https://stackoverflow.com/a/78805975/4451315), why not
try to just use that?

Anyway, thanks for your work here 💪 let's ship it
https://camo.githubusercontent.com/1b87ba81f294957cce02b6ad5cb2ab324f25046e1c706c96323f544aa20f81a4/68747470733a2f2f692e666c756666792e63632f716b4e667050306a325074647439764458327171334e435871646b634b3673532e676966
—
Reply to this email directly, view it on GitHub
https://github.com/narwhals-dev/narwhals/pull/590#pullrequestreview-2225176056,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOA4GJHV7XXD6FB2ZXONB7LZQIQH3AVCNFSM6AAAAABLKD7LZSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEMRVGE3TMMBVGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


packaging: do not install empty portusctl

This is a leftover in which the RPM package tried to copy a (now
non-existant) portusctl to /usr/sbin.
Signed-off-by: Miquel Sabaté Solà<EMAIL_ADDRESS>

Merging directly ...


Cannot use MCP servers with npx on Windows 11

Which API Provider are you using?
OpenRouter
Which Model are you using?
Claude 3.5 Sonnet
What happened?

Steps to reproduce

Simply editing MCP settings json by following official MCP docs

Relevant API REQUEST output
No response
Additional context
No response

+1
I have the same error

This is a known issue with mcp on windows, fyi. You can read about it on the mcp-get site.

It works if you just install the package with npm i -g and then run the node script witn nod and the path to the module, its a workarround
They though work fine in Claude desktop on Windows, so seems like a Cline specific issue

They though work fine in Claude desktop on Windows, so seems like a Cline specific issue

Yep, that's correct. Claude App once had this issue but now it fixed. This is Cline specific.

It works if you just install the package with npm i -g and then run the node script witn nod and the path to the module, its a workarround

This does not work for me :(

It works if you just install the package with npm i -g and then run the node script witn nod and the path to the module, its a workarround

This does not work for me :(
npm i -g @modelcontextprotocol/server-sequential-thinking
npm i -g nod
nod C:\Users\xxxx\AppData\Roaming\npm<EMAIL_ADDRESS>nod: The term 'nod' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Try changing \ with / for the path

It works if you just install the package with npm i -g and then run the node script witn nod and the path to the module, its a workarround

This does not work for me :(
npm i -g @modelcontextprotocol/server-sequential-thinking
npm i -g nod
nod C:\Users\xxxx\AppData\Roaming\npm<EMAIL_ADDRESS>nod: The term 'nod' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Try changing \ with / for the path

The problem is that the powershell/command launcher does not find "nod", is the same problem that with "npx"
The error message is "spawn nod ENOENT spawn nod ENOENT"

this is what works for puppeteer on my end - not sure if it helps, just thought to share:
    "puppeteer": {
      "command": "node",
      "args": [
        "C:\\Program<EMAIL_ADDRESS>      ]
    }

I copied the definitions for Windows from claude_desktop_config.json which I got working by following the instructions in this issue.
Filesystem access and Brave search work in the Claude desktop app and the following makes them work for me in cline.
where node outputs C:\Program Files\nodejs\node.exe on my machine
npm root -g outputs C:\Users\<my user>\AppData\Roaming\npm\node_modules
I then specified these paths with double backslashes (\\) in the cline MCP settings
  "mcpServers": {
    "filesystem": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": [
        "C:\\Users\\<my<EMAIL_ADDRESS>        "C:\\Users\\<my user>\\Projects"
      ]
    },
    "brave-search": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": [
        "C:\\Users\\<my<EMAIL_ADDRESS>      ],
      "env": {
        "BRAVE_API_KEY": "<my API key>"
      }
    }
  }
}

Do remember that you need to manually update servers that you address this way by simply running this again:
npm install -g @modelcontextprotocol/server-filesystem
npm install -g @modelcontextprotocol/server-brave-search
npm install -g @modelcontextprotocol/server-<any other nodejs server>

I assume that once the npx command is working it will pull the necessary server updates itself.

I copied the definitions for Windows from claude_desktop_config.json which I got working by following the instructions in this issue.
Filesystem access and Brave search work in the Claude desktop app and the following makes them work for me in cline.
where node outputs C:\Program Files\nodejs\node.exe on my machine npm root -g outputs C:\Users\<my user>\AppData\Roaming\npm\node_modules
I then specified these paths with double backslashes (\\) in the cline MCP settings
  "mcpServers": {
    "filesystem": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": [
        "C:\\Users\\<my<EMAIL_ADDRESS>        "C:\\Users\\<my user>\\Projects"
      ]
    },
    "brave-search": {
      "command": "C:\\Program Files\\nodejs\\node.exe",
      "args": [
        "C:\\Users\\<my<EMAIL_ADDRESS>      ],
      "env": {
        "BRAVE_API_KEY": "<my API key>"
      }
    }
  }
}

Do remember that you need to manually update servers that you address this way by simply running this again:
npm install -g @modelcontextprotocol/server-filesystem
npm install -g @modelcontextprotocol/server-brave-search
npm install -g @modelcontextprotocol/server-<any other nodejs server>

I assume that once the npx command is working it will pull the necessary server updates itself.

This works!
Thanks a lot :)

it works for me by first install uvx then choose a config mcp with uvx  as args like that :
Install uvx through : powershell -c "irm https://astral.sh/uv/install.ps1 | iex

then add your mcp config in cline (check support uvx) 👍
{
  "mcpServers": {
    "mcp-pandoc": {
      "command": "uvx",
      "args": ["mcp-pandoc"]
    }
  }
}

To get github to work on Windows 11:
{
"mcpServers": {
"github": {
"command": "C:\Program Files\nodejs\node.exe",
"args"<EMAIL_ADDRESS>"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_HG...deleted...wx"
}
}
}
}

Thank you all for your input here 🙏 will work on fixing this asap

Seems likely the issue is that npx is a script, not a binary. The fact that calls like node and uvx work fine (when configured correctly on the PATH) supports this suspicion.
The easy solution would be to call npx.cmd on Windows instead, but this option is complicated by https://github.com/nodejs/node/commit/69ffc6d50dbd9d7d0257f5b9b403026e1aa205ee. As expected, trying this changes the error from ENOENT to EINVAL.
A relevant excerpt from that commit:
// Node.js on Windows should not be able to spawn batch files directly,
// only when the 'shell' option is set. An undocumented feature of the
// Win32 CreateProcess API allows spawning .bat and .cmd files directly
// but it does not sanitize arguments. We cannot do that automatically
// because it's sometimes impossible to escape arguments unambiguously.
//
// Expectation: spawn() and spawnSync() raise EINVAL if and only if:
//
// 1. 'shell' option is unset
// 2. Platform is Windows
// 3. Filename ends in .bat or .cmd, case-insensitive
//
// exec() and execSync() are unchanged.

npx also includes a Powershell script, npx.ps1. This option, too, is complicated by the fact that node will be denied PS1 script execution by default.

In the meantime, here's my version of the workaround which doesn't involve fishing around to locate each package's entrypoint:
    "<MCP SERVER NAME>": {
      "command": "node",
      "args": [
        "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npx-cli.js",
        "-y",
        "<NPX PACKAGE ID>"
      ]
    },


Make training silent and disable model autosave

Should I release this version or are other changes coming in?


Membership Application

Name:
Tanner Gooding
Projects:

microsoft/ClangSharp (applied for transfer to .NET Foundation)
microsoft/LLVMSharp (applied for transfer to .NET Foundation)
dotnet/runtime (part of job at Microsoft)
terrafx/* (independent .NET OSS project)

Part of the projects committee.
Admin on the C# Community Discord.
Participate in various OSS design discussions for various .NET OSS repos

Welcome @tannergooding   👋 An invite is on its way to you.

@devlead, should I have gotten an invite to the slack as well? Looks like its not one of the available workspaces for me.

Invite resent to the email in your gh profile

Thanks! Received it this time.

I've never received an invite to the slack either, though, I'm not sure I have access to the slack team in the first place?

@CalvinAllen invite resent

@devlead Got it, thanks!

Same as @CalvinAllen , I didn't get a Slack invite. Could you send one through?

@Turnerj go to https://join.slack.com/t/netfoundation/shared_invite/zt-c7np4gr7-rN5cjBt4iNFOgUE9seOfzA to sign up then join #maintainers-committee