Flutter Project is not running when using indian domain

I created a project using following command on windows environment
flutter create --org in.myorg helloworld
Project is created successfully
Flutter version is as below
Flutter 1.9.1+hotfix.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 1aedbb1835 (3 weeks ago) • 2019-10-17 08:37:27 -0700
Engine • revision b863200c37
Tools • Dart 2.5.0
When I run the code I get following error
e: D:\Project\test\helloworld\android\app\src\main\kotlin\in\myorg\helloworld\MainActivity.kt: (1, 9): Package name must be a '.'-separated identifier list
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugKotlin'.

Compilation error. See log for more details

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 12s
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                        13.5s
Gradle task assembleDebug failed with exit code 1
.in domains are not allowed in flutter? using an incorrect domain will face issue while publishing app?
Flutter Analyze Output
D:\Project\test\helloworld>flutter analyze
Analyzing helloworld...
No issues found! (ran in 4.0s)
Flutter Doctor Output
D:\Project\test\helloworld>flutter doctor -v
[√] Flutter (Channel stable, v1.9.1+hotfix.5, on Microsoft Windows [Version 10.0.17763.805], locale en-IN)
    • Flutter version 1.9.1+hotfix.5 at C:\src\flutter\flutter
    • Framework revision 1aedbb1835 (3 weeks ago), 2019-10-17 08:37:27 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\Max\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.40.0)
    • VS Code at C:\Users\Max\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.6.0

[√] Connected device (1 available)
    • GM1911 • 9db98713 • android-arm64 • Android 10 (API 29)

• No issues found!

Hi @max202021
could you please provide your flutter run --verbose
thank you

Hi @iapicca ,
Please find attached file. ( it has 1000 lines)
Flutter Run Verbose.log

Follow this #16521
You have to manually go to the file and back ticks like this ->
package `in`.championswimmer.myapp
OR
you can use JAVA instead
Delete android folder and run
flutter create -a java --org in.myorg .

Since in is a keywork in kotlin, the orgname must be escaped if it contains it. Closing as a duplicate of https://github.com/flutter/flutter/issues/16521


Release 0.24.1-rc1

I've updated the prepare-release action, but it won't work until https://github.com/packit/packit/pull/2149 is merged and a new Packit image is built, so I decided to do this pre-release manually in order to test the mentioned Packit PR.

Thinking about it, I should probably move the first commit to a separate PR and merge it first, otherwise the do-release action probably won't work.

Here it is: https://github.com/packit/specfile/pull/309


Check whether it is possible to reach a step (canReachNextStep)

Hi,
when trying to use LexikWorkflowBundle for our project the need arose to be able to check whether a process can reach a next step without actually advancing the model to the next step. In more practical terms, I would like to know whether a user of my system is able to submit a certain web form before actually showing the form to the user. So I probably need something along the lines of:
if ($processHandler->canReachNextState($model, 'validate')) {...}

Like this we avoid duplicating code in the workflow validators and form controllers.
Is there a function like this? I didn't find one.
If there is not, I would probably simply copy $processHandler::reachNextState() and adapt the method to my needs. This rises the next question:
What is the best way to extend the ProcessHandler?
Cheers,
Andreas

Hi, I'm using this project now to implement a workflow in my app. I have exactly the same issue, I want to render a botton to advance de workflow, obviously I only want to show this option to users that actually can advance the process.

Hello, I'm interested in use Workflow Bundle in my Company Project, but I dont know if i can use it together Symfony 3.2.
Could you help me?
Thanks


add a sub-section about optim_m1qn3

What changes does this PR introduce?
docs update
A new sub-section about optim_m1qn3 briefly describes alternative optimization code in
a non-MITgcm repository. Therefore, this description mostly refer to the instructions on that site.
Does this PR introduce a breaking change?
No
Suggested addition to tag-index
add a sub-section about optim_m1qn3

@gaelforget GitHub suggested you might take a look at this. If. you have any comments let us know.

@mjlosch and @hongandyan how is this optim setup related to the latest ECCO pieces?

We've been using M1QN3 for LLC270 optimization for a while (suggested by Matt),
though it's an old check out from Martin's CVS.

@owang01 should confirm or otherwise but I believe that ECCO production is currently using

As far as I can see, there is little difference in the usage.
There is one small difference: I think it is more natural to specify the cost function reduction as a fraction instead of the expect fmin in the first iteration, so I introduced a "new" runtime parameter dfminFrac that is unknown to optim, and hence mitgcmuv_ad. Therefore I need to have different data.optim for mitgcmuv_ad and for my optim.x (see description here: https://github.com/mjlosch/optim_m1qn3).
It would be trivial to include dfminFrac as a dummy parameter in mitgcmuv_ad, because within mitgcmuv_ad only the parameter "optimcycle" is used, as far as I can see (I removed all #include "optim.h" and the only recurring error message was a missing declaration of "optimcycle", except for one "fmin" in ctrl_pack.F, which could be easily avoided, I think, but again it's not really used). I never suggested this, because I had the feeling that this somewhat fragile construction should not be tempered with as long as it is used in ECCO runs. In fact, I'll do it now and you decide if you want to keep it.

@gaelforget That is correct: the ECCO central production is using
http://wwwcvs.mitgcm.org/viewvc/MITgcm/MITgcm_contrib/ecco_utils/ecco_v4_release3_optimization/.

I've been using @mjlosch's offline m1qn3, I think the documentation would be nice!

This whole chapter of doc needs some work and another cleanup pass, but this contribution is helpful and LGTM.


nixdoc: 3.0.2 -> 3.0.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/nix-community/nixdoc/releases.
meta.description for nixdoc is: Generate documentation for Nix functions
meta.homepage for nixdoc is: https://github.com/nix-community/nixdoc
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.0.3 with grep in /nix/store/7ifzf9aafk5g35l9xw37gajsyxyz6fiy-nixdoc-3.0.3
found 3.0.3 in filename of file in /nix/store/7ifzf9aafk5g35l9xw37gajsyxyz6fiy-nixdoc-3.0.3

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
nixdoc

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7ifzf9aafk5g35l9xw37gajsyxyz6fiy-nixdoc-3.0.3 \
  --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 nixdoc https://github.com/r-ryantm/nixpkgs/archive/9c9e6e71035c5184566d4643706fd19c1db13763.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9c9e6e71035c5184566d4643706fd19c1db13763#nixdoc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7ifzf9aafk5g35l9xw37gajsyxyz6fiy-nixdoc-3.0.3
ls -la /nix/store/7ifzf9aafk5g35l9xw37gajsyxyz6fiy-nixdoc-3.0.3/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 --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

nixdoc

Maintainer pings
cc @infinisil @hsjobeki for testing.

After bisecting, it turns out that this broken the Nixpkgs manual build on Hydra (discovered by @K900): https://hydra.nixos.org/build/255867451
This should've been caught by the Nixpkgs manual build workflow, but it didn't because it only runs when ./doc or ./lib changes..
I'll revert

Yep. I too; Discovered some issue this morning. But wasn't sure if it broke the manuals. Since the workflows where all green i didn't catch it either.


DOC: combining datasets with different coordinates

It would be nice to have documentation recipe showing how to combine datasets with different latitude/longitude arrays, as often occurs due to numerical precision issues. It's a little more complicated than just using xarray.open_mfdataset(), and comes up with some regularity.

This is essentially a duplicate of #1391. I am going to close this in favor of that.


[android] Enable SwiftPrivateThreadExtras to build in Android.

Disabled by mistake in #29530.
Started failing in https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-16.04-android-arm64/3636/ and https://ci-external.swift.org/job/oss-swift-RA-linux-ubuntu-16.04-android/5337/
/cc @MaxDesiatov

@swift-ci please smoke test and merge

Sorry about that, my expectation was that LINUX includes ANDROID in that list, I was wrong 😔
I hope that CI checks for all platforms can be triggered for all PRs some day to avoid breakages like this 🙏

Unrelated failure in Linux.
@swift-ci please smoke test Linux platform


Make Payload private and expose APIs to list all the dequeued and failed payloads

There might have been a reason to expose the Payload type for purposes other than testing when it had a createdAt :: UTCTime field, but I don't think there is any reason to currently.
However we need a way to get failed and dequeued payloads, probably always could have used this API but it seems more pressing if we remove the way to get the Payload pStatus :: State field.
I want to use good practices for these APIs and assume they are going to have to limit the rows. I'm thinking of relying on key set paging.
failed :: Value a -> Maybe PayloadId -> Int -> Session (PayloadId, [a])
dequeued :: Value a -> Maybe PayloadId -> Int -> Session (PayloadId, [a])

I don't think I should expose an enqueued function because I think it cause performance issues with dequeue's use of FOR UPDATE SKIP LOCKED.

This implies remove dequeueValues. I can't see why to have enqueue and enqueue_.  withPayload should become:
withPayload :: D.Value a -> Int -> (a -> IO b) -> Session (Maybe b)

I'll remove the APIs in different commits in case I change my mind.


Remove problematic conditional

what

Remove problematic conditional

why

local.deprecated_statements_values can be a tuple, and Terraform does not have a concept of an empty or null tuple to use as an alternative in a conditional, so you can get an error like:

The true and false result expressions must have consistent types. The 'true' tuple has length 0, but the 'false' tuple has length 2.

references

https://github.com/hashicorp/terraform/issues/33303

/terratest


Does the plugin work in Sublime Text 4?

Package Control does not list it in ST4.

Yes, it's ST3+. Do you have any issues?

 Thanks to my dotfiles, ST already silently installed the package. So it didn't show up in the Package Control: Install Package list.
My bad.
Thank you for the quick response.


Revert "[Runtime] Look up Error bridging symbols indirectly through special symbols that won't be stripped in static builds."

Reverts apple/swift#16677
rdar://problem/40378113

@swift-ci please test


drop overlay

This should speed up evaluation by not having to re-import nixpkgs

I see a connection, do I? https://zimbatm.com/notes/1000-instances-of-nixpkgs

Merge in https://github.com/nlewo/nix2container/commit/1f11e4f25e124581684cf526db8dda0d871747d4
Thank you.


Update gem version to 0.4.8

PR Description:
This PR updates the no-style-please theme to maintain compatibility with the latest versions of its dependencies. The changes made in this PR are as follows:

Ruby 3.4.1 (Stable):

Updated the Gemfile to include the following dependencies required by Ruby 3.4.1:

gem "csv"
gem "bigdecimal"
gem "base64"
gem "logger"

csv, bigdecimal, base64 were loaded from the standard library, but are not part of the default gems starting from Ruby 3.4.0.
logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.

Jekyll Version:

Updated jekyll version to 3.10.0 to ensure compatibility with GitHub Pages.

Jekyll Feed:

Updated jekyll-feed to 0.17.0 to remain in sync with the latest stable release of the plugin.

SCSS Updates:

The SCSS files have been updated to replace the deprecated @import rule with the newer @use rule.
This change ensures the theme follows the latest best practices for SCSS, but it does result in the need to manually compile the SCSS to CSS. Consequently, the CSS file size has increased slightly from 1KB (when using @import) to accommodate the changes introduced by @use.

Bug Fixes:

This PR also fixes #12 , improving the overall functionality and stability of the theme.

Hi @riggraz! Do you think we should migrate to @use from @import? If so, this has resulted in the creation of two more CSS files assets/css/main.css and assets/ccs/main.css,map. I think that increases the CSS size.


[FUZZ] JsFuzz - Assertion failed

I've identified a fuzzer crash and am contributing to the security of Ethereum 2!
I've done and provided the following:

[x] Checked to see if any other [FUZZ] issue already refers to that crasher
[x] Attached the crashing input (either attached to the issue as a .zip or .gz, or as a link to a file sharing service)
[x] Noted the beacon-fuzz version or commit used.
[x] Provided crash output
[x] Noted the command or fuzzer used to generate the crash
[x] Name of the original crash file
[ ] (Optional but optimal) Checked if the crash can be consistently replicated by re-running the input.

Info to Reproduce

Command run: e.g. docker run -it -v C:\Users\beacon-fuzz\eth2fuzz/workspace:/eth2fuzz/workspace eth2fuzz_lodestar continuously -q lodestar -t 3600
Crasher file name: crash-4099857b077da452d2e335d436b77653877418e47bdbc2e892a8d6daf0869f5f
Client exercised: lodestar
Fuzzing engine used (if applicable):

Crash output
=================================================================
AssertionError [ERR_ASSERTION]: Assertion failed.
    at ECDSA.verify (/eth2fuzz/node_modules/bcrypto/lib/js/ecdsa.js:1:66376)
    at Object.verify (/eth2fuzz/node_modules/@chainsafe/discv5/lib/enr/v4.js:1:5109)
    at Map.verify (/eth2fuzz/node_modules/@chainsafe/discv5/lib/enr/enr.js:1:32482)
    at Function.decodeFromValues (/eth2fuzz/node_modules/@chainsafe/discv5/lib/enr/enr.js:1:26207)
    at Function.decode (/eth2fuzz/node_modules/@chainsafe/discv5/lib/enr/enr.js:1:26556)
    at Function.decodeTxt (/eth2fuzz/node_modules/@chainsafe/discv5/lib/enr/enr.js:1:26863)
    at Object.fuzz_lodestar_enr (/eth2fuzz/workspace/targets/js/lib.js:1:9181)
    at process.<anonymous> (/usr/lib/node_modules/jsfuzz/build/src/worker.js:63:30)
    at process.emit (events.js:314:20) {
  type: 'AssertionError',
  code: 'ERR_ASSERTION',
  generatedMessage: true,
  actual: false,
  expected: true,
  operator: '=='
}
crash was written to crash-4099857b077da452d2e335d436b77653877418e47bdbc2e892a8d6daf0869f5f
Worker exited

Your Environment

Fuzzer ran: docker run -it -v C:\Users\beacon-fuzz\eth2fuzz/workspace:/eth2fuzz/workspace eth2fuzz_lodestar continuously -q lodestar -t 3600
Version/Commit used: cbee3d9
Operating System and version: windows10

crash-4099857b077da452d2e335d436b77653877418e47bdbc2e892a8d6daf0869f5f.zip

Congratz, look valid to me.
Reported here: https://github.com/ChainSafe/discv5/issues/70

Fixed.
Thanks again @Buttaa


Add support for the FUSE_BATCH_FORGET operation

There are certain Kernel versions which do not send individual
Forget operations after they receive "not implemented" for Batch Forget.
One example is "5.4.0-110-generic" on Ubuntu 20.04. I am sure there are
plenty of others.
This leads to inode "leaks". Where reference counts are never decreased
and the inodes were left hanging around long after they are not needed
any more.
The best way to fix that was adding support for batch operations to the
lib. This way all users will be able to benefit from the batching
optimization.

 I've rebased it to the latest master from 9 minutes ago too. Hope it builds now 😄

Thanks!

Thanks, I did just the same thing yesterday and today I discovered that it's already done here :))
One thing I want to add is #126


Fix flaky Cron integration test

What changed?
Fix flaky Cron integration test

Why?
for https://github.com/uber/cadence/issues/3540
Unfortunatley, it's now also failing for Cassandra(probably builkite is a little overloaded)

How did you test it?
na

Potential risks
na -- I released the assertion but I think it's still in a safe range.  one second buffering is quite normal I think

Release notes

Documentation Changes

Pull Request Test Coverage Report for Build 53722cea-d5f9-4f2c-85e4-95fe726f148b

7 of 7 (100.0%)  changed or added relevant lines in 1 file are covered.
9 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.02%) to 68.005%

Files with Coverage Reduction
New Missed Lines
%

common/task/weightedRoundRobinTaskScheduler.go
2
88.6%

service/history/shard/context.go
2
62.38%

service/matching/matcher.go
2
91.46%

host/taskpoller.go
3
73.37%

Totals

Change from base Build fdb2f8c5-53ad-404e-84bd-4dc7d785074b:
0.02%

Covered Lines:
98744

Relevant Lines:
145201

💛  - Coveralls


How do i get all regions from a country or cities from a region? I want to use this for APIs. I want to select a country then hit an API and get all regions of the country selected. Hope you get the idea

How do i get all regions from a country or cities from a region? I want to use this for APIs. I want to select a country then hit an API and get all regions of the country selected. Hope you get the idea

I think you could add a get_queryset implementation in RegionModelViewSet in the same fashion CityModelViewSet does,  except filter on region id.


Promisify helper functions that depend on a response.

A good example is ArchipelagoClient.locations.scout(), ideally would like to await a response from the server with the list of locations we scouted so we can handle them without needing to listen to the locationInfo packet.
Need to also update for ArchipelagoClient.locations.check(). Same deal.

Added in 2.0.0.


Fixed issue

Description
Complete Easy Python Task.

Additional Context

Description
Complete Easy Python Task.

Additional Context

Code looks good, well done!


Error Weights Objective

from cpmpy import *

model = Model()
test = intvar(0, 1000, name="test")
model.maximize(10*(test*0.5))
model.solve()

print(test.value())

In this case the error returned is
IntVar lowerbound must be integer <class 'float'> 0.0

However if I change slightly the code
from cpmpy import *

model = Model()
test = intvar(0, 1000, name="test")
model.maximize(10*(test//2))
model.solve()

print(test.value())

The code works.

During the bounds calculation in flatten_model.py, for weighted sums we have the following:
            lb, ub = bounds.min(axis=0).sum(), bounds.max(axis=0).sum() # for every column is axis=0...
            ivar = _IntVarImpl(lb, ub)

When the sum is calculated with this, it ends up being a real number instead of an int, when the weight is float. Thus, when in the next line a new intvar is created, the problem occurs due to the lower bound (and the same for upper bound) not being an integer..
This could be solved if when calculating the bounds for wsum, we take these weights into account and then convert the bounds to an int before the initialization of the new IntVar. Also, after that we should check if this creates any other problem.
I can be assigned the issue and check it, in case noone else is working in the same things. Is anyone working on this?

Ok it is related to Pull request #224, @Wout4 is working on it

Model([iv[1] * 0.5>2]).solve() crashes with an ortools error


docs: DEV-2634 Remove Step 2 in "Configure access to your S3 bucket"

I'd add a note that Session Token is only required in case of temporary security credentials, so that there is no confusion.
otherwise lgtm

<EMAIL_ADDRESS>could you test and confirm the change.

lgtm


chore(README): Format local/system parameters as table

Description of changes:
This PR formats local and system parameters in the README as a table, in order to improve reading
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I think it can even be written as

parameter
type
description

aws.region
local/system
specifies the default region for API calls

..
..

s3.spi.endpoint
local
the endpoint to use to access the bucket; this is extracted from the uri by the S3X provider

..
..

What do you think?


Installing things – SCons vs Meson

As requested by @bdbaddog a brief analysis of why Meson is superior to SCons (as at 2019-08-28) for installation.
Meson is an opinionated Ninja build generator, whereas SCons is a generalised replacement for Make. In the same way that Autotools turned Make into a less general but more useful system, Waf tried to turn SCons from a less general, more Autotools like, system. Meson builds on SCons, Waf, and others to create a replacement for Autotools. Clearly CMake is another player in the game with similar goals and arguably more traction.
The Meson language is a domain specific language very similar to Python, but it is not Python – though it allows Python code to be executed if need be. SCons (and Waf) are frameworks built on Python.
Meson assumes out of tree builds, very much like CMake and Waf, Autotools and SCons allow for out of tree builds, but make it quite complicated in comparison.
SCons has installation builders, but they have no model of the platform being executed on – this means all destinations have to be specified, and any platform variation programmed in the build. Meson (and Waf before it) chose to have installation models for the platform of execution. So on Windows and macOS there are conventions for where things get installed, on UNIX and Linux there are the XDG rules defining where things get installed.
With Meson each builder allows for a Boolean field as to whether the build product is installable. If it is installable and "ninja install" is executed, the build product will be installed to the natural installation location for that type of build product. This can be overridden as desired, specifying the exact destination, but this is rarely used as the platform installation models are invariably correct.
For example here is the builder statement for creating an executable form some D sources:
executable(
    'gfontbrowser',
    sources,
    dependencies: dependencies,
    include_directories: includes,
    d_args: d_args,
    link_args: link_args,
    install: true,
)

sources, dependencies, includes, d_args, and link_args are variables defined beforehand. The install property is set to true. So this build product is installed to the right location on "ninja install" – or uninstalled on "ninja uninstall".
Meson is, like Waf and CMake, a system where you must create the build system before building things. I chose to have a BuildArea directory totally separated from the source. In the GFontBrowser subdirectory, executing:
meson --prefix=$HOME/Built ~/Repositories/Git/Master/Public/GFontBrowser

creates the Ninja build. By setting the prefix, just as with Autotools, Waf, CMake, the Ninja build will install everything to the prefix directory. On Linux the XDG convention is assumed and so the gfrontbrowser executable once built will get installed to $HOME/Built/bin.
As far as I am aware SCons currently has no tooling to allow for these platform specific installation models.
I began trying to do something within SCons but when Meson started getting traction, I gave up and switched to Meson.
PS There is a whole similar issue with pkg-config, SCons support for it is vastly inferior to that of Meson – again due to SCons trying to be generalised whilst Meson seeks to have conventions built in.

My PkgConfig experimentation is at https://github.com/russel/SCons_PkgConfig I haven't made the XDG experimentation public, I should do this.

I began trying to do something within SCons but when Meson started getting traction, I gave up and switched to Meson.

Altogether?

I began trying to do something within SCons but when Meson started getting traction, I gave up and switched to Meson.

Altogether?

More or less, yes, but not totally.

More or less, yes, but not totally.

Thank you for reply.


[RFE] Include node overcommittment at least from the live cluster

The oc describe nodes output is not available in the MG, but can be included in the detailed view of the live cluster.

Closing the issue as implemented in 1.2.14


GraplQL error: must be a collaborator

Extension version: v0.66.1
VSCode Version: 1.79.2
OS: windows 11

Steps to Reproduce:

Open Github Pull Request
Press create

@ttduyk13 do you have permission to create pull requests in that repo?


Add best-practices.md

I've started working on Finch's Best Practices. Going to keep adding things there. Right now it's only about JSON libraries so feel free to open PRs with your personal thoughts and advices.

Current coverage is 90.84%

Merging #445 into master will decrease coverage by -3.22% as of 048f03f

Powered by Codecov. Updated on successful CI builds.


Add ORM example with Flask-SQLAlchemy

This PR also ignores the UserWarning from Flask-Marshmallow.

Codecov Report

Merging #39 (6cc4c09) into master (b1f888c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #39   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines          792       798    +6
  Branches       147       147
=========================================
+ Hits           792       798    +6

Impacted Files
Coverage Δ

apiflask/app.py
100.00% <100.00%> (ø)

apiflask/fields.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


cigien: Watch full4kmovies.com

cigien requests the watch of the watch_keyword full4kmovies\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

full4kmovies\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

full4kmovies\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ

Approved by tripleee in Charcoal HQ


Minor refactor & lauren CR nitpick

ok to test

All yours, @llavoie ;-)

Still in Gates meetings, will get to this around 3 at the earliest.

lgtm


Make extractData: and extractDataFromFile: compatible with Swift 2 throws

adding nullable to return values of these functions made them more swifty

Thanks for this! Could you add a couple of Swift unit tests verifying that they throw correctly? Add a test case class ExtractDataTests_Swift.swift and move over testExtractData_NoPassword and testExtractData_InvalidArchive from ExtractDataTests.m, rewriting in Swift. Please be sure to add the new test to the OS X and iOS test targets.
(And check out the minor formatting nitpicks I made inline).
I'll move over the remaining tests later on.

I've updated the indentation issue but for test we should have a test file with correct header and corrupted data. I can't make such file.
Your previous code would crash app in swift but this code can handle this with newly introduced try,catch block:
let thumbData = archive.extractDataFromFile("docProps/thumbnail.jpeg", progress: nil, error: error)
will become:
let thumbData = try? archive.extractDataFromFile("docProps/thumbnail.jpeg", progress: nil)
or
try {
let thumbData = archive.extractDataFromFile("docProps/thumbnail.jpeg", progress: nil)
} catch let error as NSError {
NSLog("Error load resume data: (error.localizedDescription)");
}

If you take the existing tests as a starting point, you need to add do/catch around the UnzipKit call, and set a Boolean variable to true in the catch, asserting that it's true in the body of the test. Does that make sense? I can modify your code above to show you what I mean if it wasn't clear.

Is it okay?

v1.7 is live on CocoaPods now, including this fix. Thanks @amosavian for the work you put in!


Automatically refresh report window once the test is done

As a user I want this page (http://this:3000/report) to be refreshed automatically once testes running in the background are complete.
Right now I have to refresh a page manually.

Done


add the parseEscapeExpression function to fix singleID issue.

CLA is valid!

all feedback has been addressed in this check in
https://github.com/yahoo/secure-handlebars/commit/5dac988445f833f624ca43a7beffbd7c3dda002a

look gd. thanks


Applicants Overview for Events (formerly known as Workshops)

This is basic implementation of the Applicants Overview for the Events Page.
TODO

[x] Add localization via I18n
[x] Only allow Admins, Organizers and Coaches to view the applicants list
[x] Add general information to application details page
[x] Improve UI

Coverage remained the same at 100.0% when pulling 0ca4df294e6002ffcae5fa0ff432f3e49da4cf29 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Although Code Climate can't (currently) check the pull request automatically, it can be triggered through the web view. Maybe you can take a look :)
https://codeclimate.com/github/hpi-swt2/workshop-portal/compare/23_3.3_ApplicantsOverview#issues

Coverage remained the same at 100.0% when pulling<PHONE_NUMBER>e282c14c2415d73e8059c5f32eea71 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Coverage remained the same at 100.0% when pulling 0069238d2f7ffc3454ef288c28181fe6320f2537 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Pull Request now features the updated localization, the right management for pupil, coach, organizer

Coverage remained the same at 100.0% when pulling f329823c2ba7e568d188d335f62ea2a57d223eb1 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Coverage remained the same at 100.0% when pulling bcd18b8761cc261d5be5eacfd39f4cddf24b8efb on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Coverage remained the same at 100.0% when pulling 110282ab9281b87c8599d3f820762e699d791581 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Coverage remained the same at 100.0% when pulling 710e461996fe5657f2bec24686239aea95f3d7e8 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Coverage remained the same at 100.0% when pulling e678c7ec8fb0cb16de04fbaa42aca60da0f9b800 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Coverage remained the same at 100.0% when pulling bfffaa28dc687f582cac1513f14367a3511a0488 on 23_3.3_ApplicantsOverview into 2ce699c024b348e6e9896fee344fda35d267c31b on dev.

Incorrect Age method fixed, refactoring of feature test and removal of not required english language support

Coverage remained the same at 100.0% when pulling 726946601bc2c2e91db1247dcfba6a3e950d8869 on 23_3.3_ApplicantsOverview into 1eb89d753bf1ddd57eb2c5eb4085f59d48326307 on dev.

Coverage remained the same at 100.0% when pulling 92b3827f2cee2b33c602c2f423b442c30a339adb on 23_3.3_ApplicantsOverview into 1eb89d753bf1ddd57eb2c5eb4085f59d48326307 on dev.

Coverage remained the same at 100.0% when pulling 9ff04198f1c5812bc3b2132fe6a0d9ea613cb20c on 23_3.3_ApplicantsOverview into 1eb89d753bf1ddd57eb2c5eb4085f59d48326307 on dev.

Coverage remained the same at 100.0% when pulling 929f2e09f2529826448a089cea22452156c84e0d on 23_3.3_ApplicantsOverview into 1eb89d753bf1ddd57eb2c5eb4085f59d48326307 on dev.


Is then an exemple of defining and registering per-function FuncExtensionBase custom extension?

Question
I would like to define a custom extension that is per function.
This extension would capture the HttpTrigger request and perform some custom processing.
I could not find any sample for that.
Is there any sample?

Thanks for reaching out.
There is already doc available for this.you can refer this below doc.
https://learn.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#customizing-the-http-request

Thanks for reaching out. There is already doc available for this.you can refer this below doc. https://learn.microsoft.com/en-us/azure/azure-functions/functions-dotnet-dependency-injection#customizing-the-http-request

Thanks for the feedback.
My question however relates to Python and not .Net.
Is there any example for creating a custom class inheriting from Fun extension base?

you can try for sample below.
import azure.functions as func
class MyCustomFunction(func.Function):
def init(self):
super().init()
def __call__(self, req: func.HttpRequest) -> func.HttpResponse:

    return func.HttpResponse("Hello, World!")

@bhagyshricompany thanks for the feedback.
Can you please share a more complete sample?
I fail to see where you are showing a FuncExtensionBase-derived class ?

extensions/my_extension/init.py
from .my_extension import MyExtension
def main(req, context):
my_extension = MyExtension()
result = my_extension.func_name(req)
return result
extensions/my_extension/my_extension.py
from azure.functions import FunctionExtensionBase
class MyExtension(FunctionExtensionBase):
def func_name(self, input):
    # Implementation of your function here
    return result

extensions/my_extension/init.py
from .my_extension import MyExtension
def main(req, context):
my_extension = MyExtension()
result = my_extension.func_name(req)
return result
extensions/my_extension/my_extension.py
from azure.functions import FunctionExtensionBase
class MyExtension(FunctionExtensionBase):
def func_name(self, input):
    # Implementation of your function here
    return result

@bhagyshricompany thanks a lot.
This demonstrate how one would go in consuming a custom extension.
However, I’m specifically looking for an example of how to create such a custom extension.
For instance, the official document shows how to create a custom extension using an AppFunctionExtension base class.
import typing
from logging import Logger
from time import time
from azure.functions import AppExtensionBase, Context, HttpResponse
class TimerExtension(AppExtensionBase):
    """A Python worker extension to record elapsed time in a function invocation
    """

…

The document then has this text:

This code inherits from AppExtensionBase so that the extension applies to every function in the app. You could have also implemented the extension on a function-level scope by inheriting from FuncExtensionBase.

However, I cannot find any example of creating such a custom extension from an FuncExtensionBase class.

ok will update for this asap.

You can refer below Link for good sample:
Tutorial: https://learn.microsoft.com/azure/azure-functions/develop-python-worker-extensions

Example extension: https://github.com/census-ecosystem/opencensus-python-extensions-azure/tree/main/extensions/functions

Hazhzeng/python-worker-extension-timer (github.com)

I think the answer gives me a lot of information for going further. Thanks a lot.


didn't call bellhop module in *.F file

Not sure if module works in FORTRAN 77 environment as is

Module works using the ifort and mpifort compilers

See this optfile for CRIOS Sverdruop computer


Time loop bugs

What Happened?
Disabling time loop does not stop background stars from going supernova
Main star does supernova effects but does not explode
Warping back to main system afterwards breaks
What was supposed to happen?
No response
Platform
No response
Mods
Fret's Quest

Logs
No response

I had these bugs in StopTime - I fixed them by emptying some methods, have a look at the code to see

what code

was already copying off stop time but i can look again


✨ Health component w/ grid for demo

#151  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RTLS and the rest of your teammates on  Graphite


tsp compile . --watch only watches the entry point and not imported files within the same project

I have the following file at the root of my project:

main.tsp
uncommon.tsp
common.tsp

The entrypoint is main.tsp.
main.tsp content
import "./uncommon.tsp";
import "./common.tsp";

Expected behavior
Changes to local tsp files that are imported in main.tsp triggers the watch of tsp compile . --watch.
Actual behavior
Only changes to main.tsp cause the compilation to occur.
Environment
Tested in vscode, npm script, and purely from tsp compile to avoid 3rd party interaction.

> tsp -v
TypeSpec compiler v0.45.2

which files to watch?

imported tsp files
javascript files

est: 8


Adding support for glidein to use cvmfsexec in mode 3 when possible

This PR contains changes (additions/modifications) towards enabling the glidein to support the use of cvmfsexec in mode 3 when possible. While this PR primarily encompasses changes pertaining to enabling mode 3 support, it also contains a change to the existing logic for script duplication check.
TODO: Make sure that cvmfsexec is used only if there is a working squid proxy

Dave D will help with the proper procedure to check

Reopening this in draft mode until the changes are ready for review.

Closing this pull request without merging as a new PR (#372) has superseded this.


raw unions

Zig already supports tagged unions (#5) but for better C compatibility Zig needs to support C-style unions as well. Also, tagged unions have the tag field, and if programmers don't want that field, they're out of luck. Supporting raw unions is additional power that is needed to compete with C.
However, we want to encourage programmers to try to use tagged unions (enum) instead. It's not really possible for debug instrumentation to protect against the dangers of unions.

If the purpose is for C interop, then there are other factors.   Take the following example:
union {    int a;    void *b; } foo;
If you are on a 64-bit system with 32-bit ints and 64-bit pointers, then the value you get for 'a' will depend on the alignment requirements and byte order of the CPU and compiler.   To make such a union interoperable between Zig and C, you would need to have Zig match the byte ordering and alignment used by the C compiler.   In practice the byte order is probably not as big of a problem, but the alignment might be different.

extern union is guaranteed to be C ABI compatible.
It's an open question what a non-extern union will look like.

Are there many use cases for a non-extern union that is not enum?

I ran into an LLVM bug with debug info in 5.0.0 when implementing this.

https://bugs.llvm.org/show_bug.cgi?id=35314
http://lists.llvm.org/pipermail/llvm-dev/2017-November/119095.html

I'm looking for a workaround.

Non-extern unions will have the following safety feature:

Every distinct type instance in zig gets a unique type instance id, which is an integer with the smallest number of bits needed to represent it
Non-extern unions which have > 1 unique type in the union, have a secret type_instance_id field, which is initialized to the type instance id of void
Writing through a union field sets the type_instance_id to the appropriate type
Reading through a union field asserts that the type_instance_id is correct
This safety feature is disabled in ReleaseFast mode, and can be disabled per union with comptime { @setDebugSafety(Foo, false); }

if you do this:
const Foo = union {
    name1: u32,
    name2: f64,
};

test "aoeu" {
    var foo = Foo { .name2 = 12.34 };
    bar(&foo.name1);
}

fn bar(x: &u32) {
    *x = 1234;
}

How is zig supposed to know how to write the secret field indicating
that the active union member is name1?
I'll tell you how.
Accessing union fields by name will only give a const pointer to
the field value, and will emit a debug safety check looking at
the secret field.
If you want a mutable pointer to a union field, you do this:
test "aoeu" {
    var foo = Foo { .name2 = 12.34 };
    bar(@mutableUnionPtr(foo, "name1"));
}

@mutableUnionPtr returns a pointer to a union field, and, if the union
has debug safety enabled, modifies the secret field telling which type it is.

More adjustments:
Nevermind about @mutableUnionPtr. We can use normal address operators.

Change the secret field to be which union field is active instead of which distinct type is active.
To change which field of a union is active, reassign the whole union.
Field access of a union field activates the safety check of which field is active.


New release

There are some changes in the readme and type definition files. Might be a good idea to publish a new release to get this to npmjs.com:
https://github.com/robinvdvleuten/vuex-persistedstate/compare/v2.5.4...master

You're absolutely right! https://github.com/robinvdvleuten/vuex-persistedstate/releases/tag/v2.6.0


Status of project

Hi @stnbu : I have a couple of projects I'm working on that depend on urwid_utils, but I see that there's been an active issue requesting python3 support that hasn't been responded to since 2016.  I also see someone else submitted a Python 3 PR last night, so clearly there's interest in the project.
I have been using my own fork of urwid utils with python 3 support  and some other changes for a while, but there's a big difference between having the project hosted on github (and having to manage it through dependency_links in setup.py) vs having it available in PyPi.
So, with that in mind... do you plan on actively maintaining this project?  I think it has some useful components that I've been making use of, and I think at least some of them merit inclusion in urwid itself.  What do you think?

I'd be happy to hand over the project to you wholesale, however that's done. I don't really have time for it. I appreciate the interest! I'd be willing to put up a big sign pointing to your fork... "this project moved here" or whatever works best for you. Not sure what the github way of doing this is. Happy to cooperate.

OK, great!
Logistics-wise: Let me move my current fork aside and clone exactly what you have now, just so there's no regression from what people are getting from your repo or PyPI.  I'll merge my other changes in once we're done transferring ownership.
Then I'll need you to add me as an author in PyPI so that I can publish new versions there.  This needs to be done in the PyPI web interface, probably on both the production and test instances.  My username on PyPI is the same as here.

It looks like GitHub has a "transfer ownership of project" option under the settings tab.  Here's the documentation.  That way anyone who has your repo bookmarked / forked should pull from the new location.

tonycpsu already has a repository in the stnbu/urwid_utils network

that's a confusing error message. "network"? I receive that when I try, if you can fix whatever the issue is, I'll try again.
I'll probably have to change my pypi password or something. That's Phase II

@stnbu : Sorry about that, I thought changing the name would be enough, but apparently not.
I nuked my fork -- go ahead and try again.  Thanks!

OK, looks like it worked!  Thanks much for putting something like this out there and being cool about passing the torch!

No problem! I also added you as an owner on PyPI. I guess if there's an opportunity to attribute me as the "creator" or something in the future...that'd be cool.
Either way, have fun!

No problem! I also added you as an owner on PyPI.

Could you do the same on test.pypi.org as well?

I guess if there's an opportunity to attribute me as the "creator" or something in the future...that'd be cool.

Of course.

Done 👍


BUG: Disabling Models in interpreter doesn't work

Version (please complete the following information):

OS: MacOS 15.1.1
Browser Safari, Chrome
Web Clipper version: 0.10.0
Obsidian version: 1.7.7

Describe the bug
When disabling models in the settings of the interpreter section. they will be still shown in the clipping popup and again in the setting the are enabled
Expected behavior
When models are disabled the shouldn't shown
URLs where the bug occurs
Any specific web pages where the bug can be replicated.
To reproduce
Steps to reproduce the behavior:
Go to the interpreter settings, disable models and check again
Your template file
default + interpreter settings with openai key and local ollama
If you are using a custom template (i.e. not the Default template).  Paste the JSON code below.
{
  "schemaVersion": "0.1.0",
  "name": "Default",
  "behavior": "create",
  "noteContentFormat": "{{\"a summary of the page in German\"|blockquote}}\n\n{{content}}\n\n---\nOrdner: `=this.file.folder`",
  "properties": [
    {
      "name": "title",
      "value": "{{title}}",
      "type": "text"
    },
    {
      "name": "source",
      "value": "{{url}}",
      "type": "text"
    },
    {
      "name": "author",
      "value": "{{author|split:\\\", \\\"|wikilink|join}}",
      "type": "multitext"
    },
    {
      "name": "published",
      "value": "{{published|date:\\\"DD.MM.YY\\\"}}",
      "type": "date"
    },
    {
      "name": "erstellt",
      "value": "{{date|date:\\\"DD.MM.YY\\\"}}",
      "type": "text"
    },
    {
      "name": "description",
      "value": "{{description}}",
      "type": "text"
    },
    {
      "name": "tags",
      "value": "clippings",
      "type": "multitext"
    },
    {
      "name": "geändert",
      "value": "{{date|date:\\\"DD.MM.YY\\\"}}",
      "type": "text"
    }
  ],
  "triggers": [],
  "noteNameFormat": "{{title}}",
  "path": "18 Clippings"
}```

Duplicate of #211. The fix is already implemented and will be in the next version.


Made Hostname nullable

fix #11
public string Hostname { get; set; } = null!;

to ->
public string? Hostname { get; set; }

Thank you so much, I'm really happy that by making this project, we make other libraries better. ❤


Release v2023.2

This PR prepares the release of v2023.2. It should only contain changes from other PRs that have already been approved and merged (and possibly merge commits from the master branch).

What's the current state of this branch? I'm seeing some duplicate commits, but I'm not sure where they came from.

Ah now I'm seeing https://github.com/getodk/central/pull/395#issuecomment-1447571832. Maybe those commits came from fixing the build?

Looks like @yanokwa was in a weird state and then pushed directly to the branch. We should always do PRs even when doing small fixes I think. Maybe now we rebase to remove the redundant commits?

Actually the redundant commits may have come from the original accidental merge.

A rebase to remove redundant commits sounds ideal to me. It's also probably not a big deal to leave things as-is if rebasing would make ongoing development more challenging. I think the most important thing is just that all commits end up getting a ✅.

I have changed history to remove redundant commits and rename e2fd478 which was previously "checkpoint"

@lognaturel, I just wanted to confirm that all commits on this branch have been reviewed. I think that's the case, but it'd be great if you could confirm that in particular for the commits that didn't come from a PR.

Yes, @matthew-white, I reviewed commits that were directly pushed. Most of their contents were eventually rolled back, though.


Fix animationcomplete event name typo

This PR changes

Nothing, it's a bug fix

Describe the changes below:
Fix animation complete event name of Animation component.

👍


Bad docs link

Describe the bug
Docs for route-paths has a bad link to layout-routes
Your Example Website or App
https://tanstack.com/router/v1/docs/guide/route-paths
Steps to Reproduce the Bug or Issue
See: https://tanstack.com/router/v1/docs/guide/route-paths

At the bottom click the link to Layout Routes
observe the link takes you to https://tanstack.com/router/v1/docs/layout-routes
rather than: https://tanstack.com/router/v1/docs/guide/layout-routes

Expected behavior
correct link
Screenshots or Videos
No response
Platform

OS: [e.g. macOS, Windows, Linux]
Browser: [e.g. Chrome, Safari, Firefox]
Version: [e.g. 91.1]

Additional context
No response

It has been fixed


CBL Swift 2.0: LiteCore crash trying to copy prebuilt DB

I'm using this code snippet from Couchbase Document at https://developer.couchbase.com/documentation/mobile/2.0/couchbase-lite/swift.html#database
{code}
let assetPath = Bundle.main.path(forResource: "travel-sample", ofType: "cblite2")!
if !Database.exists(withName: "travel-sample") {
do {
try Database.copy(fromPath: assetPath, toDatabase: "travel-sample", withConfig: nil)
} catch {
fatalError("Could not load pre-built database")
}
}
{code}
It jumped to Fatal error with LiteCore error code 12 "no such file or directory"
CBL version: Swift 2.0 DB21

Wrong place.


Troubles when yarn start a ts react project

Describe the bug
It worked before but today when I was trying to use the cli for a ts project, it gives me the following message on yarn start:
Welcome.

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
USMOOWWM543G8WN:cli-test-ts c3050144$ yarn start
yarn run v1.17.3
$ react-scripts start
/Users/c3050144/Documents/pxblue/cli-test-ts/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239
      appTsConfig.compilerOptions[option] = value;
                                          ^

TypeError: Cannot assign to read only property 'jsx' of object '#<Object>'
    at verifyTypeScriptSetup (/Users/c3050144/Documents/pxblue/cli-test-ts/node_modules/react-scripts/scripts/utils/verifyTypeScriptSetup.js:239:43)
    at Object.<anonymous> (/Users/c3050144/Documents/pxblue/cli-test-ts/node_modules/react-scripts/scripts/start.js:31:1)
    at Module._compile (internal/modules/cjs/loader.js:956:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:973:10)
    at Module.load (internal/modules/cjs/loader.js:812:32)
    at Function.Module._load (internal/modules/cjs/loader.js:724:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1025:10)
    at internal/main/run_main_module.js:17:11
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

But the same steps with a js flag does not induce any error and works like normal.
What is the expected behavior?
No error.
What are the steps to reproduce?

npx -p @pxblue/cli@beta pxb new react --name cli-test-ts --lint --prettier --language ts --template blank
yarn start
(Error message as listed above)

Screenshots or links to minimum reproduction example
N/A
Environment
MacOS, node v12.13.0
Anything else to add?

Refer to https://github.com/facebook/create-react-app/issues/10117
This is an issue with CRA, not our CLI. Note that a default TS app from npx create-react-app myapp --template=typescript gives the same error.
Hopefully it will sort itself out if we just wait a little while.

This is fixed when I tested it today


Rename ILayer.Envelope to ILayer.Extent

IProvider.GetExtent() is derived from the collective IFeature.Extent and ILayer.Envelope is directly derived from IProvider.GetExtent() so better to call it ILayer.Extent.
Map.Envelope is the next logical step.
Don't think IWidget.Envelope should be renamed. This something different.

What is the difference of ILayer.Extent, IProvider.Extent, Map.Extent and IWidget.Envelope? Has the last one a special function? Or describes it something different?

IFeature.Extent is the extent of the geometry (or Raster, or MRect) in the feature. Effectively this is the extent of all its vertices (although curved lines could be an exception).
IProvider.GetExtent() is directly derived from that. It is the combined extent of all the features within the provider
ILayer.Extent returns the combined extent of all features within the layer or the IProvider.GetExtent() if it has a provider.
Map.Extent returns the combined extent of all layers.

IWidget.Envelop is the position where the Widget is placed. It is not related to features. Also an important difference is that it is in Mapsui Screen coordinates while the Extents are in World coordinates.
For IWidget field names we should perhaps look at WPF or Avalonia for inspiration.


pgloader was removed without replacement

Issue description
I want to use pgloader but I can't.
It was partly removed in cd7bfa6f48295f361c691a7520fb122938bd2a68
Steps to reproduce
nix-shell -p lispPackages.pgloader
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

cc @7c6f434c

I am not sure it worked at the moment of removal… It's a bit of a showcase how not to structure dependencies.

Thanks. I hacked together a derivation that works without using this lispPackages madness.
I hope I can find time to upstream it with a pull request.
Until then and for the record here it is: https://gist.github.com/mguentner/a37d33185c6b85b9af01cdf4b6a8cdee

lispPackages are relatively straightforward… quicklispPackages try to get scalability of grabbing packages from Quicklisp, and there is a nasty price, sure.
As an application-only package your expression is fine (it would be nice to have meta before inclusion in Nixpkgs).

@7c6f434c I am trying to work out how to get pgloader into NixOS again.
Currently (master) my derivation does not work because the created bundle w/ all quicklisp dependencies contains a library that uses an internal api of sbcl that was removed/changed in 1.4.11.
You can follow the discussion here:
https://github.com/dimitri/pgloader/issues/832#issuecomment-436645680
From my current point of view, I will wait for the release of 3.6.1 and use the bundle as
I did not manage to create a fixedOutputHash derivation for the dependencies (I even wrote a custom Make step!) that is reproducible.

Oh well, I would accept a PR that would temporarily readd SBCL expression from an old expression as sbcl_1_4_… and use it for pgloader. Waiting for upstream is also a solid plan, of course.

@mguentner pgloader 3.6.1 is out and compiles when built via your expression

@danbst Very well. I will upstream it soon.

As promised :point_up_2:

closed through #61702


tpl: Add some GoDoc info to template func docs

Updates #3418

@rdwatters @moorereason I'm sure the Hugo community is thrilled to see us spend time on this instead of doing "real work", like nested sections etc.
I will wrap this up once I get the JSON in a better shape (need to get an ordered map), but I have added the description and argument names from the source code, both of which I assume can be used if we clean it up, which we should anyway:
https://github.com/bep/hugo/blob/6cc89bd0207f462e67c2bef85562810a0654b1fe/docs/data/docs.json#L306

I don't know that the auto-generated Args are all that useful.  I've prefer to manually set those.
For example, the seq func has these Args:
"Args": ["args"]

That's not helpful.  Compare that to the front matter in the new docs site:
signature: ["seq LAST", "seq FIRST LAST", "seq FIRST INCREMENT LAST"]

I would suggest manually settings Args to get:
"Args": ["LAST", "FIRST LAST", "FIRST INCREMENT LAST"]

Then we can generate the usages in the templates using the Name+Aliases with the Args:
seq LAST
seq FIRST LAST
seq FIRST INCREMENT LAST

collections.Seq LAST
collections.Seq FIRST LAST
collections.Seq FIRST INCREMENT LAST

If you like my suggestion above, build the scaffolding, and I can do the grunt work of adding all the Args values.

I'm not sure what you mean by "manually setting args to get".
In your example the auto value is not useful, but in most other cases it is useful if the argument names is sensible, i.e.:
"Description": "Gt returns the boolean truth of arg1 \u003e arg2.",
            "Args": [
              "a",
              "b"
            ],

The above would be good if the description matched the arguments.

If what you suggest is to add some meta info the description that we can pull out, say:
This is some func.
Args:  "LAST", "FIRST LAST", "FIRST INCREMENT LAST"
Deprecated: Use some other func.

But the thing is; 95% of the funcs will be fine with the default, and the rest would need some prose to be understood (seq, dict etc.). But most of the funcs needs to be short and precise, and that precision is best had if we can maintain the text in one place.


Borgs Cannot See Laws Properly

Description

Had a few reports of players unable to open their laws when pressing the hotkey. One said they were able to make it show but only while their maintenance/module screen was open.

Can confirm. Apparently you can only open your law screen if you have a module selected.

Experienced this myself just now. Seems like you need a module selected in order to open the laws page

As noted on 28582, this also impacts opening computer UIs like the Crew Monitor or wall maps


Hashtags with no spaces.

When creating a post and adding multiple hashtags, ie:
#this #is #a #hashtag #example
insporation will post it without spaces, ie:
#this#is#a#hashtag#example

In current build multiple space divided hashtags have spaces even after posting.


Activate GitHub Pages for nfoTools Documentation

Enable docs/ as the source for nfoTools GitHub Pages.
Introduce placeholder scaffolding.
Determine what publishes absent any theme.
Determine the published location on github.io.
Review other experiments with GitHub Pages and the mapping with respect to docs/, and document that.

orcmid/nfoTools/docs is enabled and access to plaintext such as orcmid.github.io/nfotools/docs.txt as stored at  https://github.com/orcmid/nfoTools/blob/master/docs/docs.txt is confirmed.
There does need to be an index.md page to have the site not provide a 404 in the absence of a home page.

Without specifying a template, GitHub provides default formatting as part of rendering the authored pages in docs/.  This needs to be captured and then allowed for.  I have encountered this before and it is time to account for it in a place where it can be documented.

Folks also need to know that there is not instaneous re-rendering of changes in docs, whether that has to do with internet caching or whatever.  But it does work out.
The other interesting consideration is that GitHub will render Markdown files such as index.md when viewed within the repository.  It will be interesting how that can be different and/or incompatible with the github.io rendering.

The basic operations have been concluded.  The handling of templates is more of a docEng consideration.  It will be handled there.


register tag with safe and mine with no reaction at all

First attempt, it turned out the tag was registered with a different thing. Deleted that registration and tried again.
The reaction is that the field where you enter the tag id is blanked out, but the tag id is not added to the list of those already registered with the thing. There is no error message. So, no indication of what the owner should do next, or why registering the tag failed.

It turns out that safeandmine creates a channel for the tag. This thing already had the channel and so channel creation failed, and the registration aborted at that point
We need to either check for the channel's existence first (and not attempt to create it if already there) and/or delete the channel and/or not abort in this case


REPL on Website fails to map over a list

Hi! I was happy to see that you have a REPL integrated into the website and gave it a shot:
Enter an expression to evaluate, or a definition (like x = 1) to use later.
» List.map [1,2,3] (\x -> x*x)

[1, 4, 9] : List (Num *)
» List.map [0.1,0.2,0.3] (\x -> x*x)

JsValue(CompileError: wasm validation error: at offset 12564: type mismatch: expression has type i32 but expected i64
) :

I asked about it in Zulip earlier before reporting it here: https://roc.zulipchat.com/#narrow/stream/231634-beginners/topic/Question.20on.20the.20Repl.20embedded.20in.20the.20Website/near/410766990
I got quick feedback on the question on Zulip, so thank you for that :-)

this is not really a web repl problem, but a problem with multiplication for Decimal not being implemented
  The rockin' roc repl
────────────────────────

Enter an expression, or :help, or :q to quit.

»  List.map [0.1,0.2,0.3] (\x -> x*x)
…
thread 'main' panicked at 'not yet implemented: NumMulWrap: layout, Builtin(Decimal)', crates/compiler/gen_dev/src/generic64/mod.rs:1500:18
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

it is of course also interesting that it picks mulwrap here instead of mul


Remove level of detail as a concept.

@wally-the-cartographer merge

Merge requested by authorized user SirVer. Merge queue now has a length of 1.


Release 0.6.6

Release new version with Windows support. I am going to let at least 1 nightly build go by first to make sure that works before doing a full release.

@kulibali confirmed the nightly was good.


DAS phase 1

Puts data availability sampling based on the ideas here into a pull request.

Vbuterin really belive in this coin!!!!

Vbuterin really belive in this coin!!!!

https://github.com/ethereum/eth2.0-specs/pull/2254
Included this in above PR, we refactored the phase 1 spec into modules.


WIP - Feat/impl anthropic

Awesome first pass. I generally test the providers using the command line dust first to make sure everything works as expected before moving on to front :+1:

I generally test the providers using the command line dust first to make sure everything works as expected before moving on to front 👍

Thank you ! will do


Add tutorial on behavioral analysis of dependencies

[x] Setup a node project
[x] Add table of past npm packages that were compromised and made outbound calls
[x] Setup a node dependency that does outbound call on post-install step
[x] Use harden-runner to show outbound traffic
[ ] Add reference to the tutorial on restricting traffic from build server

good work @arjundashrath on this. closing it.


Fresh CatchupSubscriptionModel does not write subscription position if Mongo user does not have rights for 'hostInfo' and no new events arrived

Given:

Occurrent v0.16.11
hundreds of events in events collection
MongoDB user not having access to hostInfo() command
the following setup of fresh subscription (subscription never existed/was never executed before):

val connectionString = System.getenv("MONGO_CONNECTION_STRING") ?: DEFAULT_MONGO_CONNECTION_STRING

val mongoClient = MongoClients.create(connectionString)
val dbName = DB_NAME
val database = mongoClient.getDatabase(dbName)

val eventsCollectionName = EVENTS_COLLECTION
val eventStore =
    MongoEventStore(mongoClient, dbName, eventsCollectionName, EventStoreConfig(TimeRepresentation.RFC_3339_STRING))

val nativeMongoSubscriptionModel = NativeMongoSubscriptionModel(
    database,
    eventsCollectionName,
    TimeRepresentation.RFC_3339_STRING,
    Executors.newCachedThreadPool(),
    RetryStrategy.retry().maxAttempts(1),
)
val positionStorage =
    NativeMongoSubscriptionPositionStorage(database, "subscription-position-collection")
val wrappedSubscriptionModel = DurableSubscriptionModel(
    nativeMongoSubscriptionModel,
    positionStorage,
)
val catchupSubscriptionModel = CatchupSubscriptionModel(
    wrappedSubscriptionModel,
    eventStore,
    CatchupSubscriptionModelConfig(useSubscriptionPositionStorage(positionStorage))
)

catchupSubscriptionModel.subscribe("subscription") { e ->
    println("Event number=${e.id} received!")
}.waitUntilStarted()

When:

subscription is started
and no new events are added to events collection AFTER subscription finished initial export

Then: subscription's position does not get written to subscription-position-collection (which leads to duplicated event processing if you restart your code before new events arrive)

I created a repo to easily experiment with this situation: https://github.com/gavvvr/occurrent-148
If you just start docker-compose stack and wait a bit for completion you will see that subscription-position-collection is not created... unless you generate one more event with the test 🤔

@gavvvr Thanks for you report! I'm on vacation and I don't have my computer with me. I'll look at this when I come back, but it'll probably take 2 weeks or so.

I'm sorry for taking this long to look into this. At least I've managed to confirm it (thanks A LOT for your example project). I think I've fixed this problem in the spring implementation so need to look at how it's solved there.

@gavvvr Could you please try the latest very (non-released version) and see you if get the same problem?
I.e. you need to check-out and build Occurrent, it should work by just doing mvn clean install -Dmaven.test.skip=true.

Hi @johanhaleby
I've just tested it from the top of master and, unfortunately, the issue is still present.
To test it on your own easily, don't built the app's image from sources with Docker.
Add mavenLocal() to repositories {} and use jib (./gradlew :jibDockerBuild) to build app's image with Gradle:
jib {
    from {
        platforms {
            platform {
                architecture = "arm64" // <--- make sure to change this, if you have amd64
                os = "linux"
            }
        }
        image = "gcr.io/distroless/java21-debian12:debug-nonroot"
    }
    to {
        image = "dockerized-occurrent-app"
    }
}

@gavvvr Okay, now I finally understand the issue :) The reason why the events will be replayed again when no global position is found is that, well there's no global position to store.. So unless a new event comes in, there's no position to continue from. Thus all the events will be replayed again (until the first new event arrives because then we can get the position of the event in the oplog).
A workaround for this is to instruct the catchup subscription to save the position of the events that it reads from the event store while it's in the catchup phase. In your example, you would need to change:
 val catchupSubscriptionModel = CatchupSubscriptionModel(
        wrappedSubscriptionModel,
        eventStore,
        CatchupSubscriptionModelConfig(useSubscriptionPositionStorage(positionStorage)
    )

to
 val catchupSubscriptionModel = CatchupSubscriptionModel(
        wrappedSubscriptionModel,
        eventStore,
        CatchupSubscriptionModelConfig(useSubscriptionPositionStorage(positionStorage)
                              // This is the workaround!
                              .andPersistSubscriptionPositionDuringCatchupPhaseForEveryNEvents(1))
    )

But even if you did this there was another bug that caused an IllegalArgumentException to be thrown. I've fixed this and I plan to release a new version now :)

I've released a new version, 0.17.1 now so I'm going to close this issue. Re-open if you don't agree! And thanks for our patience :)


cmd/compile: sigill in go_bootstrap on openbsd/arm64

What version of Go are you using (go version)?

$ go version
go version go1.21.3 openbsd/arm64

Does this issue reproduce with the latest release?

I expected a successful build.
What did you see instead?
./all.bash
Building Go cmd/dist using /usr/local/go. (go1.21.3 openbsd/arm64)
Building Go toolchain1 using /usr/local/go.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
go tool dist: FAILED: /home/r/src/go/pkg/tool/openbsd_arm64/go_bootstrap install -pgo=off cmd/asm cmd/cgo cmd/compile cmd/link: signal: illegal instruction (core dumped)

lldb go_bootstrap
* thread #1, stop reason = signal SIGILL
    frame #0: 0x00000000000800f0 go_bootstrap`_rt0_arm64_openbsd
go_bootstrap`_rt0_arm64_openbsd:
->  0x800f0 <+0>:  ldr    x0, [sp]
    0x800f4 <+4>:  add    x1, sp, #0x8
    0x800f8 <+8>:  bl     0x80100                   ; main
    0x800fc <+12>: udf    #0x0

cc @golang/openbsd

I've investigated further and applying the patches from the openbsd ports tree prevents go_bootstrap from failing.
This just happened to be a case where platform specific patches haven't been merged with upstream.


Regression in the way that conflicts are reported by force:source:push --json

For the past several years, conflicts have been reported reliably by force:source:push by specifying a name value of sourceConflictDetected in the failureResponse, all part of the JSON response written to stdout. Suddenly I'm seeing it being reported differently as follows:
$ sfdx force:source:push --json > force_source_push.out 2> force_source_push.err

$ echo $?
1

$ cat force_source_push.out
{
  "name": "DeployFailed",
  "actions": [],
  "exitCode": 1,
  "data": [],
  "result": [],
  "commandName": "Push",
  "warnings": [
    "We plan to deprecate this command in the future. Try using the \"project deploy start\" command instead."
  ],
  "message": "Push Failed.",
  "stack": "DeployFailed: Push failed. \n    at PushResultFormatter.getJson (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@salesforce\\plugin-source\\lib\\formatters\\source\\pushResultFormatter.js:37:27)\n    at Push.catch (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\push.js:165:23)\n    at Push._run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@oclif\\core\\lib\\command.js:112:29)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Config.runCommand (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@oclif\\core\\lib\\config\\config.js:328:25)\n    at async run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@oclif\\core\\lib\\main.js:89:16)",
  "context": "Push",
  "status": 1
}

$ cat force_source_push.err
    sourceConflictDetected: We couldn't complete the operation due to
    conflicts. Verify that you want to keep the existing versions, then run
    the command again with the --forceoverwrite (-f) option.
    Code: sourceConflictDetected

This is not only a breaking change overall, but important information about the result is being written to stderr instead of being part of the structured JSON response written to stdout.
I can certainly update to accommodate for this, but it is a breaking change to a long-standing contract for reporting of conflicts, and a more worrying change to the way these CLI commands actually report their structured output.

For context, I have the following comment in my Salesforce CLI command executor:
// All JSON-formatted responses--success or error--are sent to stdout now, and stderr is used for free-form messages

that was added with the following commit comment on February 9, 2019:

Spring '19 - Updated SFDX CLI execution to handle JSON-formatted responses only on stdout, whether success or failure, and low-level errors/informational text on stderr.

Please tell me that you're not straying way from that long-standing rule of how CLI commands provide their responses...

You'll note that the response also no longer includes the specifics about the actual conflicts which is another regression. Previously all metadata objects which were found to be in conflict were included with a value of Conflict for state.

I have verified that force:source:pull still behaves as it has in the past. Here is the output of that command with the expected/proper information written to stdout and stderr (in this case, stderr is empty):
$ sfdx force:source:pull --json > force_source_pull.out 2> force_source_pull.err

$ echo $?
1

$ cat force_source_pull.out
{
  "data": [
    {
      "state": "Conflict",
      "fullName": "Account-de",
      "type": "CustomObjectTranslation",
      "filePath": "C:\\Users\\Scott\\dev\\projects\\ic-test-projects\\NPSP\\force-app\\main\\default\\objectTranslations\\Account-de\\Account-de.objectTranslation-meta.xml"
    },
    ...
  ],
  "code": 1,
  "message": "We couldn't complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.",
  "name": "sourceConflictDetected",
  "status": 1,
  "stack": "sourceConflictDetected: We couldn't complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.\n    at processConflicts (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@salesforce\\plugin-source\\lib\\trackingFunctions.js:104:17)\n    at trackingSetup (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@salesforce\\plugin-source\\lib\\trackingFunctions.js:36:9)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Pull.preChecks (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\pull.js:41:25)\n    at async Pull.run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\pull.js:27:9)\n    at async Pull._run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@oclif\\core\\lib\\command.js:108:22)\n    at async Config.runCommand (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@oclif\\core\\lib\\config\\config.js:328:25)\n    at async run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.197.8-077a68b\\node_modules\\@oclif\\core\\lib\\main.js:89:16)",
  "exitCode": 1,
  "warnings": [
    "We plan to deprecate this command in the future. Try using the \"project retrieve start\" command instead."
  ]
}

$ cat force_source_pull.err
<nothing>

Note that value for name as sourceConflictDetected and the list of actual conflicting metadata files with a state of Conflict. The force:source:push command should behave identically.

@SCWells72 - thanks for reporting Scott.  I'll fix this asap.  I expect to get it into a nightly as well as the next CLI release candidate.

Thanks, @shetzel. I've implemented a workaround--at least to detect the conflict state even if the conflict details aren't present--for the next IC2 build (this Thursday morning). Once the original behavior is restored, it should use it automatically.
This is obviously another in a growing string of such regressions. I just asked @mshanemc this, but I'll add the same thought here. Would it be helpful for me to provide a list of the commands executed by IC2 for JSON output and the expected contract (exit codes, JSON shape and contents, etc.) based on historical behavior? You all could incorporate validation for those expected contracts into your automated test suite. That would probably take me a bit to put together--hopefully just hours and not days--but if it would save me time later (and my users grief), I think it might be worth it.

@SCWells72 - it's a CLI policy to never break command JSON output shape as it's an API contract (caveat: additions are ok but not removals or change in shape).  We have lots of tests across all our commands that have some JSON output coverage but it's difficult to cover all the usecases, especially all the variations that can happen with the most popular commands, deploy and retrieve (and all their variants).  That said, obviously we missed some.
To answer your question about "Would it be helpful..." - yes, it would but it's also something we should already have and I would not expect that from any customer.  I'll create a story to improve command JSON output test coverage.  If you want to provide usecases you certainly can, but don't feel obligated.
BTW, the fix for this is being tested now.  I expect it will be in the nightly tonight so I'll promote it to the CLI RC tomorrow.

Thanks, @shetzel. I certainly appreciate the policy, but as evidenced by the recent regressions in the JSON CLI-as-an-API interface, there must be some gaps in the current test coverage relative to at least some downstream usage patterns, (from my perspective, notably those used by IC2). And don't get me wrong, I understand that you all have been implementing some HUGE changes in the move to open source, the new command naming conventions, the introduction of the sf CLI,, etc., so some regressions are going to happen. If I can share some information that not only helps to minimize them in the future, but specifically to minimize the ones that might impact me (and therefore my users), it's time well-spent.
Yesterday I created a document that covers all of the CLI commands that IC2 executes (well, except for the Salesforce Functions ones that don't really have a JSON interface anyway) with the args passed and the Java POJOs into which the responses are deserialized. I emailed that document to @mshanemc, so you should be able to get it from him, or if you need, just let me know and I can provide directly to you. The one thing that may be missing from would be details about expected values for some of the properties of those POJOs, e.g., Conflict as the value for state when a conflict is reported. I'm happy to provide that additional detail if you have questions upon reviewing what I've sent. Just let me know.

This fix is in the current sfdx cli release candidate, v7.199.7

Hey, folks. Would you expect this to be fixed in the GA builds? I ask because I'm still seeing it. Here's an example from just now:
{
  "status": 1,
  "failureResponse": {
    "result": [],
    "partialSuccess": [],
    "stderr": "(node:3020) Warning: Deprecated environment variable: SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.\r\n(Use `node --trace-warnings ...` to show where the warning was created)\r\n(node:3020) Warning: Deprecated environment variable: SFDX_JSON_TO_STDOUT. Please use SF_JSON_TO_STDOUT instead.\r\n",
    "status": 1,
    "exitCode": 1,
    "message": "We couldn\u0027t complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.",
    "name": "sourceConflictDetected",
    "commandName": "Push",
    "stack": "sourceConflictDetected: We couldn\u0027t complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.\n    at processConflicts (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@salesforce\\plugin-source\\lib\\trackingFunctions.js:104:17)\n    at trackingSetup (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@salesforce\\plugin-source\\lib\\trackingFunctions.js:36:9)\n    at async Push.prechecks (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\push.js:38:25)\n    at async Push.run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\push.js:31:9)\n    at async Push._run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@oclif\\core\\lib\\command.js:117:22)\n    at async Config.runCommand (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@oclif\\core\\lib\\config\\config.js:329:25)\n    at async run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.201.6-4edd82d\\node_modules\\@oclif\\core\\lib\\main.js:89:16)",
    "actions": [],
    "warnings": [
      "We plan to deprecate this command in the future. Try using the \"project deploy start\" command instead.",
      "The \"-u\" flag has been deprecated. Use \"--target-org | -o\" instead."
    ]
  }
}

Notice that the name is properly set to sourceConflictDetected, but there are no specific files listed as having a state of Conflict. So while it appears to be partially resolved, it doesn't appear to be completely resolved, at least not in providing the end user a good picture of what exactly is in conflict.

Hi @SCWells72
I'm using sf version @salesforce/cli/1.82.0 darwin-arm64 node-v18.15.0.  I changed an apex class in the org and locally, then ran sf force source push --json and the response had a data property that contained the specific metadata conflicts.
My sfdx version is 7.204.6 and it has the same json response when I run the push command.
If you update the cli do you see a good response?

@shetzel, I'm on slightly older versions, but they seem to be the latest released versions as they're the result of running sfdx update and sf update immediately before responding here:
$ sfdx version
sfdx-cli/7.203.6 win32-x64 node-v18.15.0
$ sf version
@salesforce/cli/1.81.0 win32-x64 node-v18.15.0

I just tried to reproduce it a few different ways and wasn't able to, but I've been seeing it pretty often over the past week. Given the recent frequency, I'm assuming it will happen again during my normal work/testing this coming week--at least if it will still happen--and will let you know as soon as it does exactly what I was doing. If I make it through the next week without it happening, that's perhaps a good sign that whatever changed in this most recent update addressed it. I'll keep you posted.

And...it did just happen again:
{
  "status": 1,
  "failureResponse": {
    "result": [],
    "partialSuccess": [],
    "stderr": "(node:21472) Warning: Deprecated environment variable: SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.\r\n(Use `node --trace-warnings ...` to show where the warning was created)\r\n(node:21472) Warning: Deprecated environment variable: SFDX_JSON_TO_STDOUT. Please use SF_JSON_TO_STDOUT instead.\r\n",
    "status": 1,
    "exitCode": 1,
    "message": "We couldn\u0027t complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.",
    "name": "sourceConflictDetected",
    "commandName": "Push",
    "stack": "sourceConflictDetected: We couldn\u0027t complete the operation due to conflicts. Verify that you want to keep the existing versions, then run the command again with the --forceoverwrite (-f) option.\n    at processConflicts (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@salesforce\\plugin-source\\lib\\trackingFunctions.js:104:17)\n    at trackingSetup (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@salesforce\\plugin-source\\lib\\trackingFunctions.js:36:9)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Push.prechecks (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\push.js:38:25)\n    at async Push.run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@salesforce\\plugin-source\\lib\\commands\\force\\source\\push.js:31:9)\n    at async Push._run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@oclif\\core\\lib\\command.js:117:22)\n    at async Config.runCommand (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@oclif\\core\\lib\\config\\config.js:329:25)\n    at async run (C:\\Users\\Scott\\AppData\\Local\\sfdx\\client\\7.203.6-1da7df1\\node_modules\\@oclif\\core\\lib\\main.js:89:16)",
    "actions": [],
    "warnings": [
      "We plan to deprecate this command in the future. Try using the \"project deploy start\" command instead.",
      "The \"-u\" flag has been deprecated. Use \"--target-org | -o\" instead."
    ]
  }
}

That's in direct response to sfdx force:source:push -u username --json. This was setting up a scratch org with a slightly older version of NPSP where I do the following:
$ sfdx force:mdapi:deploy -d unpackaged/pre/account_record_types/ -w 10
Warning: We plan to deprecate this command in the future. Try using the "project deploy start" command instead.
Deploying metadata to<EMAIL_ADDRESS>using the v58.0 SOAP API.
Deploy ID: 0Af8K00000L1LMrSAN
DEPLOY PROGRESS | ████████████████████████████████████████ | 8/8 Components

$ sfdx force:mdapi:deploy -d unpackaged/pre/opportunity_record_types/ -w 10
Warning: We plan to deprecate this command in the future. Try using the "project deploy start" command instead.
Deploying metadata to<EMAIL_ADDRESS>using the v58.0 SOAP API.
Deploy ID: 0Af8K00000L1LN6SAN
DEPLOY PROGRESS | ████████████████████████████████████████ | 8/8 Components

$ sfdx force:mdapi:deploy -d unpackaged/pre/packages/ -w 10
Warning: We plan to deprecate this command in the future. Try using the "project deploy start" command instead.
Deploying metadata to<EMAIL_ADDRESS>using the v58.0 SOAP API.
Deploy ID: 0Af8K00000L1LNLSA3
DEPLOY PROGRESS | ████████████████████████████████████████ | 5/5 Components

$ sfdx force:source:push --json
<conflicts without details as above>

That's using sfdx and sf versioned as above where sfdx update and sf update report no new updates available as of the time of this writing.

Okay, I found the issue. Historically the details in the push failure response were in an array called result, but since being restored, they're in an array called data. So IC2 is losing them during JSON deserialization. I can obviously work around that by adding data as an "alias" for result, but that still seems like a regression. Thoughts?

@shetzel, for context, this is from the Java POJO into which IC2 deserializes failed push JSON responses:
public class SfdxForceSourcePushSuccessResponse {
    public SfdxForceSourcePushResult result;

    public static class SfdxForceSourcePushResult {
        public List<SfdxForceSourcePushPushedSource> pushedSource = new LinkedList<>();
    }

and that's unchanged since 6/29/2017. If I rename result to data everything works fine against the current CLI, but again, that seems to be a regression in the API contract for this command's output, no?

I was going by the pull example you provided in your April 25 comment and was hoping the data property would suffice.  I'll add result back.  Thanks for pointing that out.

@shetzel, it's totally up to you. I've already patched IC2 to allow for both. I don't know if others might already have adjusted for this change and might be frustrated by having it revert. Perhaps before you make any further changes you might poll other integrators? Don't know if you have a direct line to them or not.

I wouldn't replace data with result.  I would just have both.  Though, if you don't need the result property I'll leave it as is.

I wouldn't populate both. In a situation where there are numerous reported errors/conflicts, that could result in quite a large JSON document. I've updated things to work with data or result depending on which is present. I'm good to go. Not sure about others who might be consuming that same output, but my guess is that if you haven't heard from them so far...you're probably okay.

@shetzel, note that the same issue is present for force:source:pull. That's why you used data as a reference point...because I included the output of the modified version of that command. Traditionally both commands have used result, and now both use data. I've updated IC2 to allow for both list property names in both the push and pull commands, but anyone relying on the original result list property name is going to miss the details in both commands.


Translates Submodules vs. Subtrees to Spanish

Overview
TL;DR
Translates Submodules vs. Subtrees to Spanish.
Review
ready for :eyes:
Spanish reviewers:
@CesarAscencioV @alxalmora

Fabulous, thank you @remigioamc! Once this has a review by another person fluent in Spanish, we'll be happy to merge this in. 👍

Fabulous! Thank you so much, @remigioamc, @alxalmora, and @CesarAscencioV!


Per app log-sink

Hello,
the new log-sink feature works very nicely for me. We needed that a long time now. Thank you!
However, log is flooded with the stuff from dashboard and controller. Is it possible to configure log sinks per app?

Not yet, though this is the logical evolution of this feature. We may be able to add a flag filters out logs for system apps from the cluster-wide stream as well.

Thank you. That would be nice.
For the future readers:
In the meantime we are using logs in /var/log/flynn and configure remote syslog directly on the nodes. Quite easy to configure with ansible.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


TypeError: can't pickle module objects

I tried saving the model using sklearn joblib but this error occur, TypeError: can't pickle module objects.
Is this a python pickle problem or library issue?  I do found python had issue on pickling multiprocessing instance https://stackoverflow.com/questions/8804830/python-multiprocessing-pickling-error
Multicore-TSNE is the latest git master version, Python 3.6, Ubuntu 17.04

I have the same issue. How do you pickle Multicore-TSNE models?

Same issue here.

Ok, so. ... let me rephase the question... is it possible to serialize a Multicore-TSNE instance?

Do you save the problem?

Do you save the problem?


Use new Emperor formatting methods

Consolidates all the callbacks in a single file and implements the new methods that are being introduced here.
Note that this build is going to fail unless https://github.com/biocore/emperor/pull/786 is merged.

The following artifacts were built for this PR: empire-biplot.qzv, empire.qzv, empress-tree.qzv

@ElDeveloper something odd seems to happen when playing two different animations.  By that I mean first (on the emperor UI) select gradient=month and trajectory=trajectory. Play the animation. Then change gradient to day. The lines connecting the samples on the emperor plot jump around. The table shows the end of the animations. The images were taken from the linked .qzv.

Just playing day
showing day after month

Thanks for bringing this up, I think this has to do with Emperor's animation trajectory rendering strategy. I just opened: https://github.com/biocore/emperor/issues/787

Thanks all!

Thanks @fedarko!
On (Sep-25-20|18:08), Marcus Fedarko wrote:

Merged #383 into master.
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://urldefense.com/v3/__https://github.com/biocore/empress/pull/383*event-3809906601__;Iw!!Mih3wA!XfN2I46NLzr5XgRdz_wjkY6nLiFQBOiPPLvuFkDYCZbF1e0pv1G2ygtAoCIUTLU$


Promises

Do all browsers support Promises? Maybe use a polyfill?

I hope that's supplied by the ecmascript polyfill. Isn't it ?
On 2015 දෙසැ 25, සිකු at ප.ව. 8.38 zimt28<EMAIL_ADDRESS>wrote:

Do all browsers support Promises? Maybe use a polyfill?
https://github.com/kadirahq/meteor-graphql/blob/f1b9c2dc45a5998b01a356e62dcda1781f0c2e6c/client/lokka_transport.js#L24
—
Reply to this email directly or view it on GitHub
https://github.com/kadirahq/meteor-graphql/issues/1.

I see you have opened a thread on the Meteor Forums, just to keep everyting together.

The polyfill seems to be included :)


Uploading folder

I'm submitting a

[x] feature request

Summary
Folder uploads would be an addon for this package

Added in https://github.com/lmesacademy/dropbox-upload/releases/tag/1.3.0


Inject config into controller context.

This makes the config used to start all the clients available on the context starting the controllers. That enables us to use that config to create secondary clients in the controllers with the same config.
/assign @mattmoor @n3wscott

I have done so many hacks to do this same thing.
/lgtm

I am not sure I can approve but we will try
/approve


Repository Development Status and Integrated Papers

Hi, I would like to know if the repository is fully developed and how many papers' methods are integrated into it because we need this information for further evaluation. Thank you!

Hi,
Thank you for your question! The repository is fully developed for its current functionality, but it remains an ongoing project. This means additional datasets, models, and features will be integrated over time based on feedback and evolving needs. For example, there have been requests to include more datasets and models, which are being considered for future updates.
To date, I’m not aware of any published papers that specifically utilize this toolbox, though several users have indicated they are actively experimenting with it for their research. This includes a new paper of mine that will be released soon.
I hope this provides clarity! Please let me know if you have further questions.


How to sanitize array

I'm getting an non-sanitized input error:
267 | ERROR | Detected usage of a non-sanitized input variable: $_POST

Here's the code:
$taxonomies = isset( $_POST['announcement']['display'] ) ?
                          wp_unslash( $_POST['announcement']['display'] ) :
                          array(); // input var okay

$_POST['announcement']['display'] looks like this:
array (
  'verticals' =>
  array (
    0 => 'life',
    1 => 'politics',
  ),
)

I can't run array_map( 'sanitize_text_field', $_POST['announcement']['display'] ) as that clobbers the array. I do the sanitizing later:
$announcement['display'] = array();

if ( is_array( $taxonomies ) ) {
	foreach ( $taxonomies as $taxonomy => $taxonomy_terms ) {
		foreach ( $taxonomy_terms as $taxonomy_term ) {
			$announcement['display'][ $taxonomy ][] = sanitize_text_field( $taxonomy_term );
		}
	}
}

Is there a way to rewrite this to avoid the warning? If not, how can we improve the sniffer to handle this case?

Is there a way to rewrite this to avoid the warning?

Yes, put the sanitization code into a function, my_sanitize_announcement_data(). Then, add that function to the list of sanitizing functions:
<rule ref="WordPress.VIP.ValidatedSanitizedInput">
		<properties>
			<property name="customSanitizingFunctions" value="my_sanitize_announcement_data" type="array" />
		</properties>
	</rule>

I've just created a wiki page based on this question.


Display library assets only important files

Refer to #54, the library asset only display *.min.js, *.min.css, and
filename field in package.json.
close #54, cc @PeterDaveHello.

@Billy4195 wow, cool! Thanks!

@PeterDaveHello I added a button to show the remaining files, since the library material-design-icons contains too many files, click the button will let browser load files for a long long time.
Otherwise the library JQuery works well as following screenshots.

After click the button:

@PeterDaveHello OK, I changed it.
Now if the number of asset files of a library is less than 40 files, it will display them all, otherwise it only displays files match the rule.

Nice, looks better now, let's further improve the logic here, actually, the assets have different and complex patterns that we can't directly control.
So, if there are no minified css or js files with .min.css/.min.css in a library version, what should be done here?
IMO, the rule that always displays the minified files will not be suitable here, in some cases, they use library.js/library.css directly, and library.src.js/library.src.css for non-minified files.
We don't need to make the rules very complex at the beginning, we can simply display all css and js files if there is no one using .min the suffix in the file name, but if it's fine for you, you can prioritize the file extensions need to be hidden.
It's almost done here 👍

OK, I will do it in two weeks, because I have many projects need to be finished now.

@Billy4195 Hey 👋 Could you possibly resolve conflicts and I can chase this to be merged?

@PeterDaveHello Could we get this merged (I can't merge it) as I believe all issues are resolved and after testing this, I am happy that it is a good change for the site!

@MattIPv4 with all due respect I'll suggest you not directly pinging me on every issues or PRs if they're just waiting for reviews, I'll always do my best to review all of them but I don't have very enough time, pinging everything may just like pinging nothing, and may even break their order in notifications, I personally prefer to handle them by the order ;) Still thanks a lot for the other part like help reviewing!

@PeterDaveHello Just for clarification, a button to essentially toggle whether the hidden files are actually hidden?

cc #54

Correct 💯


Use semidbm

This introduces semidbm to replace the dumbdbm/gdbm setup for offline datasets and empirical distributions on disk.
gdbm has served us well but it's really difficult to install in some systems. Semidbm seems to do a fair job in performance and it doesn't have any library dependencies like GNU dbm.

Can also consider https://lmdb.readthedocs.io/en/release/