Error when running cargo install

I am running cargo install on a binary indirectly dependent on typeshare and I get this error:
error: expected serde try_from attribute to be a string: `try_from = "..."`
   --> /home/martinmr/.cargo/registry/src/github.com-1ecc6299db9ec823/typeshare-1.0.1/src/integer.rs:34:28
    |
34  |           #[serde(try_from = $untruncated_str)]
    |                              ^^^^^^^^^^^^^^^^
...
114 | / truncated_type!(
115 | |     U53,
116 | |     u64,
117 | |     "u64",
...   |
120 | |     "The 53-bit unsigned integer type. Purpose of this type is to mimic JavaScript's integer type."
121 | | );
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `truncated_type` (in Nightly builds, run with -Z macro-backtrace for more info)

error: expected serde try_from attribute to be a string: `try_from = "..."`
   --> /home/martinmr/.cargo/registry/src/github.com-1ecc6299db9ec823/typeshare-1.0.1/src/integer.rs:34:28
    |
34  |           #[serde(try_from = $untruncated_str)]
    |                              ^^^^^^^^^^^^^^^^
...
126 | / truncated_type!(
127 | |     I54,
128 | |     i64,
129 | |     "i64",
...   |
132 | |     "The 54-bit signed integer type. Purpose of this type is to mimic JavaScript's integer type."
133 | | );
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `truncated_type` (in Nightly builds, run with -Z macro-backtrace for more info)

error: could not compile `typeshare` due to 2 previous errors
warning: build failed, waiting for other jobs to finish...
^C  Building [======================>  ] 278/294: tantivy, cargo-lock, libgit2-sys(build)

I didn't get it the first time I ran the command, but I get it every time after. Running cargo clean doesn't help.

It's this commit if that's helpful: https://github.com/trane-project/trane-cli/commit/97bb86986304fdeb26928f08ba14ac71064267f3

Building the project that actually uses typeshare works fine though

Same issue when trying to run cargo build on this commit https://github.com/trane-project/trane/commit/f514d797d9068d2b231d56f6b1149ea64dad92cc in the CI pipeline but not on my machine.
For the other project, it fails on my machine.

With the verbose options, this is the command that fails (when running cargo install):
 Running `rustc --crate-name typeshare --edition=2021 /home/martinmr/.cargo/registry/src/github.com-1ecc6299db9ec823/typeshare-1.0.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=c4b0fdffe14b4c70 -C extra-filename=-c4b0fdffe14b4c70 --out-dir /home/martinmr/workspace/trane-cli/target/release/deps -L dependency=/home/martinmr/workspace/trane-cli/target/release/deps --extern chrono=/home/martinmr/workspace/trane-cli/target/release/deps/libchrono-0e2048e71587b9a1.rmeta --extern serde=/home/martinmr/workspace/trane-cli/target/release/deps/libserde-87bdc9edf8e487c8.rmeta --extern serde_json=/home/martinmr/workspace/trane-cli/target/release/deps/libserde_json-47ebd281091542fa.rmeta --extern typeshare_annotation=/home/martinmr/workspace/trane-cli/target/release/deps/libtypeshare_annotation-21829e58750ce549.so --cap-lints allow`

And this command succeeds (when running cargo build --release):
 Running `rustc --crate-name typeshare --edition=2021 /home/martinmr/.cargo/registry/src/github.com-1ecc6299db9ec823/typeshare-1.0.1/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=e5ce113263e3518a -C extra-filename=-e5ce113263e3518a --out-dir /home/martinmr/workspace/trane-cli/target/release/deps -L dependency=/home/martinmr/workspace/trane-cli/target/release/deps --extern chrono=/home/martinmr/workspace/trane-cli/target/release/deps/libchrono-3c55daee8812e281.rmeta --extern serde=/home/martinmr/workspace/trane-cli/target/release/deps/libserde-822396222001a2f4.rmeta --extern serde_json=/home/martinmr/workspace/trane-cli/target/release/deps/libserde_json-7cb68a3d609e826c.rmeta --extern typeshare_annotation=/home/martinmr/workspace/trane-cli/target/release/deps/libtypeshare_annotation-0710c1877a4ad673.so --cap-lints allow`

The paths to serde, etc are different, but I am not sure if that's expected.

I've reverted the addition of typeshare for now to unblock my project, but the commits linked above are still available for helping you debug the issue. I also saw docs.rs fail to build the previous release (the first one to introduce typeshare), so I don't think the issue is specific to my machine.

same

Hi @martinmr. I've tried to reproduce your with first commit (https://github.com/trane-project/trane-cli/commit/97bb86986304fdeb26928f08ba14ac71064267f3), on current Arch/Manjaro Linux x64 kernel 6.2.7-2 (standard target x86_64-unknown-linux-gnu), with either

yesterday's nightly: rustc 1.70.0-nightly (1db9c061d 2023-03-21) and
recent stable: rustc 1.68.0 (2c8cc3432 2023-03-06), but both build (cargo build) and install (cargo install --path .`) well:

# with stable:
trane-cli (97bb869) is 📦 v0.13.2 via 🦀 v1.68.0 took 6m3s
❯ trane --version
...
Trane Version: 0.13.2
CLI Version: 0.13.2
Commit Hash: 97bb86986304fdeb26928f08ba14ac71064267f3

trane >>

Please, share about your rustup, toolchains, architecture... anything.

I've tried to reproduce the second commit ()
❯ # stable
trane (f514d79) is 📦 v0.13.3 via 🦀 v1.68.1
❯ cargo clippy
Checking cfg-if v1.0.0

@martinmr Please provide steps (ideally with a new local user) to get to the point when you could run the above rustc --crate-name typeshare --edition=2021 /home/martinmr/.cargo/registry/src/github.com-1ecc6299db9ec823/typeshare-1.0.1 ....
Why? After I run cargo build (with stable) under the same trane-cli commit as your local (97bb869), I do not have any ~.cargo/registry/src/github-com*, only /home/pkehl/.cargo/registry/cache/index.crates.io-6f17d22bba15001f (after my previous cleanup). Any chance you have global dependency overrides (instead of crates.io to GIT) or anything else?
trane-cli (97bb869) is 📦 v0.13.2 via 🦀 v1.68.1
❯ find ~/.cargo/registry/* -name "typeshare*"
/home/pkehl/.cargo/registry/cache/index.crates.io-6f17d22bba15001f/typeshare-1.0.1.crate
/home/pkehl/.cargo/registry/cache/index.crates.io-6f17d22bba15001f/typeshare-annotation-1.0.2.crate
/home/pkehl/.cargo/registry/index/index.crates.io-6f17d22bba15001f/.cache/ty/pe/typeshare
/home/pkehl/.cargo/registry/index/index.crates.io-6f17d22bba15001f/.cache/ty/pe/typeshare-annotation
/home/pkehl/.cargo/registry/src/index.crates.io-6f17d22bba15001f/typeshare-annotation-1.0.2
/home/pkehl/.cargo/registry/src/index.crates.io-6f17d22bba15001f/typeshare-1.0.1

I am no longer able to reproduce it either after I upgraded from rust 1.68.0 to 1.68.1. I'll try to readd my typeshare changes to master and see if I can perform the commands I could not before.

Readded the typeshare changes to my project and I was able to make it work after upgrading to 1.68.1


[FIRStorageUploadTask] putData completion is not called when internet connection is offline

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.4.1
Firebase SDK version: 6.25.0
Firebase Component: Storage
Component version: 3.6.1
Installation method: CocoaPods

[REQUIRED] Step 2: Describe the problem
Completion of putData of FIRStorageReference is not executed when uploading to storage when the terminal is offline (airplane mode).
Steps to reproduce:
Put your device in airplane mode and run the code below.
let reference: StorageReference = self.storageReference
let task: StorageUploadTask = reference.putData(data, metadata: metadata) { (metadata, error) in
    // Not called
}

@Masataka-n Thanks for taking the time to open this issue!
The Storage SDK retries uploads. When your device goes back online, putData will execute and the callback will be called. If this behavior does not suit your needs, you need to manually verify the network status before invoking any Storage APIs.


Unicode Support(Encoding) For Output

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author
Version

python
donjayamanne
0.6.2

cpptools
ms-vscode
0.10.5

csharp
ms-vscode
1.8.1

java
redhat
0.1.0

cmake
twxs
0.0.17

cmake-tools
vector-of-bool
0.9.4

Output console dosn't support unicode characters
also there is no settings for output encoding.

I believe this is a duplicate of #3550


ld: symbol(s) not found for architecture arm64

I am not sure if this is the correct project to file this issue, but after updating to Flipper 0.96.1, a new package called Flipper-Boost-iOSX was added, and that causes this error:
Undefined symbols for architecture arm64:
  "___cxa_increment_exception_refcount", referenced from:
      folly::cxxabi_cxa_exception_sans_reserve() in libFlipper-Folly.a(Exception.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

** BUILD FAILED **

The following build commands failed:
	Ld /Users/kasra/Library/Developer/Xcode/DerivedData/InflationCalc-fmwbpshgatctktepfxhturrnjevn/Build/Products/Debug-iphoneos/InflationCalc.app/InflationCalc normal
(1 failure)

System:
    OS: macOS 11.4
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
    Memory: 35.37 MB / 8.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.3 - ~/.nvm/versions/node/v14.15.3/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.18.1 - ~/.nvm/versions/node/v14.15.3/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.10.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
    Android SDK:
      API Levels: 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.2
      System Images: android-28 | Google APIs Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.2 AI-202.76<IP_ADDRESS>86908
    Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_275 - /usr/bin/javac

Flipper  0.96.1
Flipper-Folly 2.6.9
Flipper-RSocket 1.4.3
FlipperKit  0.96.1
OpenSSL-Universal 1.1.1100

Only these versions work, as you can see, the Flipper-Boost-iOSX is removed and then everything start to work:

It doesn't look like a Boost issue. ___cxa_increment_exception_refcount is likely a part of standard C++ library, not Boost. Anyway, this project just for building Boost, and any issues like this (if they have something to do with Boost) should be addressed to related Boost library developers.

I think the problem is in Flipper (https://github.com/facebook/flipper) project,  or more precisely in https://github.com/facebook/folly/blob/master/folly/lang/Exception.cpp . It uses the function abi::__cxa_increment_exception_refcount that is not defined in the current arm64 ios platform. Or perhaps there is some additional system library that should be included at the link stage.

You are right, I need to file this there. I will close this issue. Thanks a lot.


⚠ ClamAV has degraded performance

In 4b648ff, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 223 ms

Resolved: ClamAV performance has improved in 0fae043.


.Exec memory leak ?

Consider the following code:
package main

import r "gopkg.in/rethinkdb/rethinkdb-go.v5"

func main() {
	session, err := r.Connect(r.ConnectOpts{Address: "localhost:28015"})
	if err != nil {
		return
	}
	execOpts := r.ExecOpts{NoReply: true}
	insertOpts := r.InsertOpts{Conflict: "update"}
	t := r.DB("test_db").Table("test_table")

	for {
		err = t.Insert(r.JSON(`{"id":"xxx", "a": 1}`), insertOpts).Exec(session, execOpts)
		if err != nil {
			return
		}
	}

}

when running this for around 1-2 minutes memory usage reaches 15GB
when using .Run instead of .Exec memory usage stays at ~10MB
Is there a memory leak here or I'm doing something wrong ?

It's connection leak. It seems that Exec doesn't close cursor or something. I need to investigate this.

Thank you.
Is there any workaround ATM ? We have a huge amount of writes and Run (even with durability:soft) is too slow for that.

Try to parse json into go map[string]interface{} on the client side, it seems that server's r.JSON doesn't so effective. Also batch inserts are much faster. For example insert array of 1000 document in a single query.

thanks a lot!


feat(atomic): atomic-pager component completion

https://coveord.atlassian.net/browse/KIT-372

Similar to https://vapor.cloud.coveo.com/#/components/Pagination

I think the page numbers would look better circular like on the docs website https://docs.coveo.com/en/search/#q=facet&t=All&sort=relevancy but that's just a matter of opinion I guess.

I think the page numbers would look better circular like on the docs website https://docs.coveo.com/en/search/#q=facet&t=All&sort=relevancy but that's just a matter of opinion I guess.

Might be an illusion, but it looks like the numbers are not well aligned within the center of the circle ? 🤔

Might be an illusion, but it looks like the numbers are not well aligned within the center of the circle ? 🤔


Improved Tokenisation Efficiency + Added Templates folder to check

The initial filtering now checks for non-ASCII characters
More concise and effective regex patterns
Minor adjustments in tokenization

!bounty 250


Setup data-model comparison

Given a set of parameters, simulate the model, and then simulate it with each of the knockouts (which can occur by setting that species to degrade at a very high rate). Calculate the sum of squared error across all these measurements.

@mlwahl you can take lead on this, but it'll be helpful to work with Zhan since he put together the model.


Singleplayer integrated server only allows crawl control from the host.

Describe the bug
An "Open to LAN" integrated server only has crawl control assigned to the host. The host determines if all other players can crawl based on if the host is crawling. Client-side crawling is not affected. The server doesn't acknowledge player guests are crawling, both visually and mechanically. When the host crawls, the player guests receive a slight pose stuttering, indicating the server is attempting to put them into crawl mode, but it is quickly overridden by the client.
Mod version affected
1.0.2
Other mods used
Unknown except for fabric api
Minecraft version used
1.20
To Reproduce
Set a single-player world "Open to LAN", have another player on, and have the host shift.
Additional information
Other mod versions and Minecraft versions are likely affected as well

It's such an annoying bug. The real issue is that behavior on dedicated servers and integrated servers should be the same since both versions are basically identical, but it isn't. In all my testing, nothing has been amiss logically, so it's a very frustrating discrepancy.

Crawling functionality is handled by the client-side implementation when using the integrated server for multiplayer. Both ServerPlayer and LocalPlayer instances are handled this way.
Since the client wasn't programmed to expect multiple players (and rather delegate that task to the server), it automatically forces all player instances to crawl at the request of the integrated server host. Because the client handles all player instances, the server-side doesn't process crawl request packets from guest clients, meaning they can only crawl through 1-block holes when the server host is crawling.

The Crawl mod solves this issue by injecting a custom enum into the player pose states and passing it on the network. The Crawl On Demand mod solves this issue by using Forge's capability system.

The Crawl mod solves this issue by injecting a custom enum into the player pose states and passing it on the network. The Crawl On Demand mod solves this issue by using Forge's capability system.

Although sadly (to my knowledge) your is the only one that works whether the player has the mod installed or not. I was using the Crawl mod, but it uses a custom EntityPose so every time someone who does have the mod installed (obviously on the server as well) crawls, the person without the mod installed client side would get kicked. Your mod uses the SWIMMING EntityPose, so it doesn't do that. Sadly I do like the custom entity pose, but it wont do for my use case.


ng2 Datepicker dates displayed incorrectly

Hello jkuri,
I am really impressed by the code and the work you have done for creating this datepicker. Recently I used the datepicker but I noticed that there is problem with this datepicker its not showing the correct calendar. You might want to look into this issue.

i get the same problem，i think it's a bug ,but you can set the options.firstWeekdaySunday= true to solve it

@tejassawant54 thanks for notice, I'll make a fix.

@CK110 Thanks for replying i will try this
@jkuri No problem :)

@jkuri I have a quick question can we change the format depending on the requirement by just passing an attribute to the ng2-datepicker component ?

its hard coded at this moment, PRs welcome

@jkuri  ok thanks ... sure :)

Solution for viewFormat:
Use:
<ng2-datepicker [(ngModel)]="date" [viewFormat]="DD-MM-YYYY" >
Default format set in datepicker-options.class.ts
this.format = obj && obj.format ? obj.format : 'dddd MMMM DD, YYYY';
ng2-datepicker.component.ts
export class DatePickerComponent implements ControlValueAccessor, OnInit {
@Input() viewFormat: string;
Inside ngOnInit() {
if( this.viewFormat){
  this.options.format = this.viewFormat || this.options.format;
}

}

Hi @tejassawant54, this should be resolved with https://github.com/jkuri/ng2-datepicker/commit/740f220f38d101e5dded52ac21a258a8a31ffd43. Can you please confirm?

I'm still having the same issue with wrong dates. I also see the Demo remains one day off.
How are the options intended to be passed into the ng2-datepicker element? It says with property bind in the docs, so I'm not sure how to pass property + key + value? Something along these lines?:
<ng2-datepicker id="date-picker" ngModel name="date" #date="ngModel" [options]="autoApply?.true"></ng2-datepicker>
How would I pass style 'bold' which takes a string?
Thanks for the help and open-source contribution. The picker looks great.

@sbroways <ng2-datepicker id="date-picker" ngModel name="date" #date="ngModel" [options]="customoptions"> , the customoptions is a variable， and you define this customotions in the ts class
like this：
export class A{

customoptions: DatePickerOptions;

ngOnInit(){
        this.customoptions =new DatePickerOptions({
            autoApply:true,
            style:'bold'
        })
}

}

or you can just wirte in template ,like this:
<ng2-datepicker id="date-picker" ngModel name="date" #date="ngModel" [options]="{autoApply:true,style:'bold'}"></ng2-datepicker>

@CK110 Worked brilliantly! Thank you! The option to set firstWeekSunday also aligned dates to day of week for me, so calendar is functioning properly now.

Thank you @sbroways and @CK110 it's work.
About the language, does it support pt-BR?

@lidiooliveira , you can just try DatePickerOptions.locale='pt-br' , and maybe you need import the pt-br.js or   locales.js

@lidiooliveira  what I did was go to your project folder: node_modules\ng2-datepicker\src\components
In the file "ng2-datepicker.component.ts" you change what you want, "Select Year" I converted to "Selecionar Ano",
div class="datepicker-calendar-day-names"
Change the names T S Q to or whatever: Dom. Seg. Ter. Qua. Quin.
div class="datepicker-buttons" *ngIf="!options.autoApply"
Change "Today" to "Hoje", "Apply" To "Confirmar"
After that, you must have Typescript installed "npm install -g typescript", then you type: on the PATH (ex.: C:\Users\USERNAME\Desktop\Projects\ProjectName\node_modules\ng2-datepicker\src\components) folder tsc ng2-datepicker.component.ts then it will compile and you just reboot the server, in my case ionic serve.
I hope that helps.

@killerengel Thanks a lot for the help.

pls help me for my issue ::
when i am submiting form, inserting the date by one day behind
i.e 2017-04-02  to 2017-04-01.
I am using ng2-datetime-picker by importing .
Below is my form input , how i am using datepicker ::

thank you in advance.

+himajaM
moment.utc(YourdateString).format('YYYY, MM, DD')
maybe the format above is not the same of yours, but 'utc' usually solve this problem.

Any body can suggest me for my doubt please..!
Using ng2-datetime-picker, i want to disable  all dates before current date
Below is my input tag how i am using datePicker :

Thanks in Advance


Format of ConvertTo-Json is not matching what document states

Steps to reproduce
Get-Date | Select-Object -Property * | ConvertTo-Json

Expected behavior
Example 4 - https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/convertto-json?view=powershell-6

Actual behavior

Environment data

Name                           Value
----                           -----
PSVersion                      5.1.17763.497
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.497
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

@prbans Your environment data shows PS 5.1 and the documentation link is for PS 6
The good link for your version is here

How do I upgrade my powershell to be v6 in that case?
Is there an option I can pass to V5 that enables V6 behavior?

Download and install V6 from the repo here: https://github.com/PowerShell/PowerShell/releases
And no, there are no further features being added to v5, so if you want v6 behaviour, you have to use v6. 🙂


Config override per request doesn't work

Axios allow only some keys to be passed in request config check them here https://github.com/axios/axios/blob/master/lib/core/mergeConfig.js
Unfortunately cashe is not one of these keys, so the function mergeRequestConfig receive req parameter without cache object and the default cache config isn't overridden.

Oh damn, I think this was not the case before as I know the per request cache config worked.

This is due to the axios last update v0.19, they released it a couple of weeks ago.

It's going to be solved in this PR https://github.com/axios/axios/issues/2203

Any news on this?

This is being tracked in the https://github.com/axios/axios/pull/2207 PR now. They merged the changes this week but haven't released due to some test failures.

Is this actual ?

Yep, looks it's been merged: https://github.com/axios/axios/pull/2207

Hmm... 🤔 the package.json says it's been updated:
https://github.com/RasCarlito/axios-cache-adapter/blob/137f392ffcfe1a3d00a2e950f0317130bb44b2e7/package.json#L82-L84

It's working, but haven't been released yet. You can install new version by:
yarn remove axios-cache-adapter
yarn add RasCarlito/axios-cache-adapter

Workaround for anyone else trying this with axios 0.20 or above: instead of using setup just use axios.create + setupCache, so it doesn't rely on the axios version stated in the package.json of this cache adapter.

it's working fine with axios 0.19.2 https://codesandbox.io/s/axios-cache-api-testing-wk3o4

is this still an issue?

We use 0.19.2 without a problem.
I do know we had to use axios.default.adapter to get the adapter to conditionally reset, that's not cache's fault but axios arcane resolution logic for the config merge.
    const response = await Instance.get(uri, {
      adapter: axios.defaults.adapter,
      validateStatus: status =>
        (status >= 200 && status < 300) || (status >= 401 && status <= 404),
    });

I think axios 0.20, changes this again.

What is the current state of this issue? Can it be used with axios versions above 0.18.1? Has the package version been fixed, to avoid having multiple versions of axios being used?

What is the current state of this issue? Can it be used with axios versions above 0.18.1? Has the package version been fixed, to avoid having multiple versions of axios being used?

Should now be fixed with lastest release https://github.com/RasCarlito/axios-cache-adapter/releases/tag/2.6.0


Usage with vue3 + composition API

I'm trying to use your component on my Vue3 app with composition API and I'm not able to make it work even with the minimal setup.
I've got this very simple component and stuck with the following error Uncaught (in promise) TypeError: t3.component is not a function
<script setup>
import VueEllipseProgress from 'vue-ellipse-progress'
</script>

<template>
    <VueEllipseProgress :progress="90"/>
</template>

What am I doing wrong ?

@dcp-dev Helllo,
please make sure to refer to the documentation for Vue 3 compatible version
// install
npm i vue-ellipse-progress@next
// import
import { VeProgress } from "vue-ellipse-progress";
// use
<ve-progress :progress="50"/>


Minimum size of markers ways and relations

When I zoom out to see a full European country all the nodes preserve a minimum marker size so at to make it easy to click on it. But ways and relations has no minimum marker size, so it become an almost impossible task to click on the only pixel in the image when the way or relation is small as a house.
(It can be an other excuse to work on the leaflet version. ;) ).

Related to #2.
Agree that small ways are hard to see and click on smaller zooms (esp. z11-12 IMO). The general way-styling can probably be improved, but it should also work for many changes in dense areas.
So there should probably be a size-dependant styling, e.g. based on the line/polygon pixel bounding box. Either by increasing the line width or replacing the line with a point symbol. E.g. Overpass Turbo has an option to style small features like POIs.
(And you guessed it, I think it's a waste of time figuring out how to best do this with the currently used OpenLayers version. But priority are #9 and #10, got stuck there before, will see how that goes.)


Need improve error msg for importing data of unsupported data type

Enhancement
Use insert into select statement, select 1 and insert into a bitmap data type column.
The error msg is: ERROR 1064 (HY000) at line 18: Vectorized engine does not support the operator
Not clear enough.

@jaogoy how can i reappear this? thank you!


Persist trie nodes to database

[x] Persist trie nodes to database
[x] Tests
Closes #244

You should sync with David before merging this, I think classes like NibblesToBytes shouldn't exist anymore in favour of util classes handling the same functionality.


Artifact actions v3 will be closing down

I got an email from github:

Artifact actions v3 will be closing down by January 30, 2025. You are receiving this email because you have GitHub Actions workflows using v3 of actions/upload-artifact or actions/download-artifact. After this date using v3 of these actions will result in a workflow failure. Artifacts within their retention period will remain accessible from the UI or REST API regardless of the version used to upload.
To raise awareness of the upcoming removal, we will temporarily fail jobs using v3 of actions/upload-artifact or actions/download-artifact. Builds that are scheduled to run during the brownout periods will fail. The brownouts are scheduled for the following dates and times:
January 9th, 12pm - 1pm EST
January 16th, 10am-2pm EST
January 23rd, 9am-5pm EST
What you need to do
Update workflows to begin using v4 of the artifact actions as soon as possible. While v4 improves upload and download speeds by up to 98% and includes several new features, there are key differences from previous versions that may require updates to your workflows. Please see the documentation in the project repositories for guidance on how to migrate your workflows.

@pitmonticone does this affect us?

claim

In any case, we are not using those two specific GitHub Actions. Nothing to worry about.
I have added the dependabot workflow mentioned above, so we can safely close this issue.


There is something wrong with the map of the world in the Demo

Issue type
I'm submitting a ...  (check one with "x")

[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Issue description
Current behavior:
Taiwan is not a country, it is just a part of China!!!

Expected behavior:
Correct the map in the Demo: Taiwan is not a country, it is just a province of China!!!

Take it easy, it did say Country/Region! Leave the political stuff out of
GitHub pls!
On Tue., 27 Aug. 2019, 16:51 Kevin<EMAIL_ADDRESS>wrote:

Issue type
I'm submitting a ... (check one with "x")

bug report
feature request
question about the decisions made in the repository

Issue description
Current behavior:
Taiwan is not a country, it is just a part of China!!!
[image: image]
https://user-images.githubusercontent.com/29921884/63747566-04c5ac00-c8da-11e9-9ad5-66c1dd03f0a9.png
Expected behavior:
Correct the map in the Demo: Taiwan is not a country, it is just a
province of China!!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/akveo/ngx-admin/issues/5493?email_source=notifications&email_token=ACAP3XLUW7Q5Z5KW5KSVY4TQGTFGNA5CNFSM4IP6V5MKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHR6RUQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACAP3XP7I2YOWFY3MRPGLBLQGTFGNANCNFSM4IP6V5MA
.


Add rule to check message body for only links or references

Don’t allow commits with only “close # 124” message bodies. Or with full links to an issue.
It can also give a hint if no links to issues are present, to promote linking to issues. This was added in version 0.7.0.
Accepted link types:

full link to something GitHub/GitLab/etc. (Or just any link?)
references like #123 (any other systems use other formats?)
references like JIRA-123

Duplicate of #34, which was added.


Looking for maintainer: esp-hal-smartled

The intention of this repository is to allow the community to manage packages which the team at Espressif do not consider to be priorities, allowing us to focus on building out the HAL and surrounding ecosystem. I had originally added myself to CODEOWNERS for the esp-hal-smartled package just to get the ball rolling here, but I would like to find one or more volunteers to take over so that I can distance myself from this process.
Maintainership will require reviewing, testing, and merging relevant PRs, as well as handling new releases. Volunteers will be given the required permissions on GitHub and crates.io to perform these duties.
If you are interested in volunteering to maintain this package, please open a pull request replacing my username in the CODEOWNERS file with your own, and I will take care of the remaining administrative work prior to merging it.
If you have any questions, please feel free to comment below.

@horho77


openssl.bin depends on perl because of c_rehash

Trying to build a small docker image of a nodejs project I noticed that openssl depends on perl:
3.4M    /nix/store/55azyw1bcrzn8q5ganaav0cnqs2viwdn-openssl-1.0.2i
48M     /nix/store/xcp6lrq3ynj75cqcyy7b32jgizf9jr4b-perl-5.22.2

The reason for this runtime dependency is the inclusion of c_rehash:
# Perl c_rehash script, scan all files in a directory
# and add symbolic links to their hash values.

There are no references to c_rehash in nixpkgs. Would any oppose dropping this from openssl-bin?
/cc @edolstra

Actually, it seems that nodejs does not need to depend on openssl.bin. All the references I see in the resulting binary are to ${openssl.bin}/include and ${openssl..bin}/lib, neither of which exists.

@vcunat Hm, while this of course not the core issue you are indeed right I suppose. I guess this could be fixed by passing in openssl.lib to the nodejs derivation instead of openssl?
/nix/store/7agkqzpq2qnb1ab6gq7chmjf8x42hqcx-nodejs-6.6.0
+---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
+---/nix/store/ly5dbisg2h0k3xnfdbk955m3pc4knvjk-gcc-5.4.0-lib
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/ly5dbisg2h0k3xnfdbk955m3pc4knvjk-gcc-5.4.0-lib [...]
+---/nix/store/09rfjicwds107wknldxjhi3swwml1pig-http-parser-2.7.0
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/ly5dbisg2h0k3xnfdbk955m3pc4knvjk-gcc-5.4.0-lib [...]
+---/nix/store/55azyw1bcrzn8q5ganaav0cnqs2viwdn-openssl-1.0.2i
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/55azyw1bcrzn8q5ganaav0cnqs2viwdn-openssl-1.0.2i [...]
+---/nix/store/47ddkjfrphqp8zxd8cq9xa10l0xr8qkv-openssl-1.0.2i-bin
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/55azyw1bcrzn8q5ganaav0cnqs2viwdn-openssl-1.0.2i [...]
|   +---/nix/store/xcp6lrq3ynj75cqcyy7b32jgizf9jr4b-perl-5.22.2
|       +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|       +---/nix/store/zhhb02yrp03xzfrpk06ixb0gmwrjmjff-coreutils-8.25
|       |   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|       |   +---/nix/store/6h29qi09p6p4kh04n3pyg7wa0sn7gryv-acl-2.2.52
|       |   |   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|       |   |   +---/nix/store/scblgh0h3sh65s0rp0nv79rr82mjd6cm-attr-2.4.47
|       |   |   |   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|       |   |   |   +---/nix/store/scblgh0h3sh65s0rp0nv79rr82mjd6cm-attr-2.4.47 [...]
|       |   |   +---/nix/store/6h29qi09p6p4kh04n3pyg7wa0sn7gryv-acl-2.2.52 [...]
|       |   +---/nix/store/zhhb02yrp03xzfrpk06ixb0gmwrjmjff-coreutils-8.25 [...]
|       +---/nix/store/xcp6lrq3ynj75cqcyy7b32jgizf9jr4b-perl-5.22.2 [...]
+---/nix/store/b5mwbrx8cldkchiqgwgkaagw91xfjr89-zlib-1.2.8
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
+---/nix/store/mh7snrv03k9d6pz7xz7ysc98l6r8phnl-libuv-1.9.1
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/mh7snrv03k9d6pz7xz7ysc98l6r8phnl-libuv-1.9.1 [...]
+---/nix/store/nyj6xd7s1n1w8c0xdwk5ddhi7bjcyi9x-bash-4.3-p46
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/nyj6xd7s1n1w8c0xdwk5ddhi7bjcyi9x-bash-4.3-p46 [...]
+---/nix/store/w9020qsqapllmfcdh2x686y8ng6n15mh-python-2.7.12
|   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   +---/nix/store/55azyw1bcrzn8q5ganaav0cnqs2viwdn-openssl-1.0.2i [...]
|   +---/nix/store/9jplq6zqlfixn2drgq07jgvcabjrmn47-bzip2-<IP_ADDRESS>.1
|   |   +---/nix/store/6fix3zqpnahyml8zp2sxi2rwan55rgb8-glibc-2.24 [...]
|   |   +---/nix/store/9jplq6zqlfixn2drgq07jgvcabjrmn47-bzip2-<IP_ADDRESS>.1 [...]
|   +---/nix/store/b5mwbrx8cldkchiqgwgkaagw91xfjr89-zlib-1.2.8 [...]
|   +---/nix/store/nyj6xd7s1n1w8c0xdwk5ddhi7bjcyi9x-bash-4.3-p46 [...]
|   +---/nix/store/zhhb02yrp03xzfrpk06ixb0gmwrjmjff-coreutils-8.25 [...]
|   +---/nix/store/w9020qsqapllmfcdh2x686y8ng6n15mh-python-2.7.12 [...]
+---/nix/store/7agkqzpq2qnb1ab6gq7chmjf8x42hqcx-nodejs-6.6.0 [...]

I do have a solution already; I'm just polishing it.

@vcunat :+1:

I'm having a bit of hard time with nodejs trying to inject include paths into the output binary.

@vcunat i would still say that the core issue is that openssl-bin which in itself is just 3MB introduces a 48MB dependency via perl because of that c_rehash script- regardless of whether nodejs needs openssl or not. The same obviously applies for anything else using openssl-bin.

But nodejs doesn't need openssl-bin at all, same as most other packages. They use the libraries.

Yes I get that. Those are two separate issues though - both of which should be fixed I guess.

Further splitting openssl-bin to two outputs would seem confusing to me – the current convention is that if pkg.bin exists, it contains all the executables.

Well this perl script really does not seem like an integral part of openssl to me. I am doubtful that most people want that when they install openssl

Then again I am certainly not an openssl expert. Wonder if other distributions openssl packages include it

Debian and Arch do so; Fedora splits away openssl-perl "output" that also contains some more utilities.

BTW, another big dependency is python, referred only from lib/node_modules/npm/node_modules/node-gyp/gyp but I know too little about nodejs to get into such internals.

@gilligan: for now I'd fix up nodejs at least. Can you test the change 95a0766dd1e with the stuff you use?
It builds, but there seems to be a tiny chance that some node package actually relied on some ability to query which include paths were used.

@vcunat will do so later and report back.

BTW, another big dependency is python, referred only from lib/node_modules/npm/node_modules/node-gyp/gyp but I know too little about nodejs to get into such internals.

Yep, I have a PR for that ready. It adds a slim variation that packages node without npm. Which is a common variation anyway.

@vcunat I tried the change to nodejs and from what I can tell from testing it is working just fine!

By the way I created #19973 to address the  nodejs -> npm -> python dependency

@vcunat I incorporated your change into #19973

Great; I was just about to suggest that.

Maybe just stick c_rehash into an output by itself, and make $bin/bin/c_rehash into a script that tells you where to find the real one?

Interesting idea with the script, but it apparently has some downsides with which c_rehash and environment collisions. I didn't want to act on this myself, as I didn't see much to gain:

there are very few explicit openssl.bin references in nixpkgs and I don't expect many more implicit ones;
perl is a very common dependency – in particular, nixos users are forced to depend on it anyway.

(triage) was this fixed by now?

It seems to be the same, but I personally don't consider it wrong.

Well, “wrong”..  the fact remains that openssl itself is < 4MB and the perl dependency increases the closure size by almost 50MB for something i haven’t even ever heard anyone mention anywhere ever so.. i guess “meh”

Could we add a flag withPerlScripts ? true to control the existence of c_rehash?
Context: I am working on a space limited embedded system.  I do need the 600kB binary found in openssl.bin, but I don't need c_rehash and its 50MB perl dependency.

It seems this has been fixed!
Here's the closure of openssl.bin -- no Perl, and total size <8MB excluding glibc:
$ nix path-info -s $(nix-store -qR $(nix-build -A openssl.bin))
/nix/store/0gr5bsynx3qnxwplqdzgj0gb60mhnzy0-libunistring-0.9.10	    1634416
/nix/store/2lygwhmhagpi7k6pxnw8wimh6aiih5z2-openssl-1.1.1d     	    4146504
/nix/store/5ljnwy2i3gg6irysjyqacj61qs90y9cr-openssl-1.1.1d-bin 	     771744
/nix/store/7s4pysk2smm1xdp787lkfz31l39l5lvf-libidn2-2.3.0      	     222672
/nix/store/9rabxvqbv0vgjmydiv59wkz768b5fmbc-glibc-2.30         	   31082264

I got here from looking at #83446. @oxalica observes there:

now the perl script c_rehash produced by openssl.bin has shebang #!/usr/bin/env perl, which means we don't need to substitute it anymore.

and I think that same change in the (upstream?) shebang line would also have fixed this issue.

I confirm this seems fixed on all maintained branches (i.e. including 19.09).

This seems to be broken again on master, could we reopen this issue?
nix path-info -sh $(nix-store -qR $(nix-build -A openssl.bin))
/nix/store/176gh50y24c0lx2bnnmsvf9wazb73php-coreutils-9.0          1.8M
/nix/store/5b40cks3m9nhkxiy4g9jsaqbp1vipc6g-attr-2.5.1            78.7K
/nix/store/6wcdxh3h5jp9qgrccq3n71wnalca5mf5-perl-5.34.0           53.1M ***
/nix/store/f472rqx45rdhq2dl8xhjlwwj56wjpjsj-openssl-1.1.1m-bin   760.5K
/nix/store/nq7z9djyxaj6j7w9mgp94a6sds1jppi4-libidn2-2.3.2        254.7K
/nix/store/rf9d67pk49l2sq26qiwwp1wl727qf11f-acl-2.3.1            108.9K
/nix/store/s9qbqh7gzacs7h68b2jfmn9l6q4jwfjz-glibc-2.33-59         29.8M
/nix/store/y8v9k1mjr73ns140bfzfyf3sm5avh4gc-openssl-1.1.1m         4.0M
/nix/store/ymr28y3gfbjp25cwn7nqihbciasxxgna-libunistring-0.9.10    1.6M

I notice that this was fixed for the cross-compiling case in https://github.com/NixOS/nixpkgs/pull/115911. But what about the non cross-compiling case when using something like nodejs-slim?
There's an assert keeping you from overriding the withPerl arg that was added. I'd suggest this assert should be removed to use with things like nodejs-slim where you know you don't need c_rehash.

From Arch Linux bug #54887:

We could probably just either

make Perl an optdepends "for the c_rehash script"
replace the c_rehash script with a tiny shell script that invokes openssl rehash "$@"

The latter relies on the fact that openssl-rehash is an identical, modern built-in C implementation of c_rehash.pl

Arch now lists perl as an optional dependency for openssl. But I like the other suggestion better: just drop Perl. You don't lose any functionality and, unlike with Arch, you don't need to worry about breaking anyone's workflow.

replace the c_rehash script with a tiny shell script that invokes openssl rehash "$@"

Sounds amazing, want to make the PR?

might be relevant: https://github.com/vmware/photon/commit/875d985717579e0042e356cf59bd9d9190b36200#diff-d65f4e155b4acda25e9e4c7c87be1ee83a6537666e3a0f1c52a8bdbef2f0d507R8


[API Rest] Redirecting to /login when doing a POST to /api/v1/database/import/

Hello!
I tried to import a zip file of my databases (previously obtain using the /export route of the API) to my superset server but I keep getting redirected to /login (I tried something with csrf_token but I get the same redirection)
There is may be something I am missing.
Expected results
I expect to be able to see my databases added to my superset server and receive a 200 OK response
Actual results
I am getting a redirection to /login
How to reproduce the bug
I am using this curl:
curl -H "Authorization: Bearer $token" -H 'accept: application/json' -H 'Content-Type: multipart/form-data' -F "formData=@databases.zip;type=multipart/form-data" -X POST http://localhost:8088/api/v1/database/import/
Note: token is an access_token generate by the route /security/login

superset version: 1.3
python version: 3.7.9
node.js version: 14
any feature flags active: "ALERT_REPORTS": True, "VERSIONED_EXPORT": True

Hi,
we are facing the same issue.
any potential solution ?

Hi! Thanks for reporting, can you help verify this is still an issue on master? if so, lmk with a screenshot or videos, we will look into it right away 🙏

thanks @junlincc
#token compute
[cs_superset@superset-vm ~]$ token=curl -k -H "Content-Type: application/json" -d '{"password": "#masked#","provider": "db", "refresh": true, "username": "admin"}' -X POST http://localhost:8088/api/v1/security/login | jq -r .access_token
#api call using the token to import superset_export.zip file
[cs_superset@superset-vm ~]$ curl -H "Authorization: Bearer $token" -H 'accept: application/json' -H 'Content-Type: multipart/form-data' -F "formData=@superset_export.zip;type=multipart/form-data" -X POST http://localhost:8088/api/v1/database/import/

Redirecting...
Redirecting...
You should be redirected automatically to target URL: /login/.  If not click the link.[cs_superset@superset-vm ~]$

thanks here is a screenshot of what I get, it is pretty similar to the above

HI @junlincc ,
Any progress here? I am facing the same issue with current docker latests image while importing dataset, here is verbose curl output.
> Host: superset.janantos.com
> User-Agent: curl/7.64.1
> accept: application/json
> Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpYXQiOjE2MjkyODY1NTUsIm5iZiI6MTYyOTI4NjU1NSwianRpIjoiMGZmODU0YzktY2QxMy00ZTljLTgwY2EtMGRmZTk0NjI1MDc5IiwiZXhwIjoxNjI5Mjg3NDU1LCJpZGVudGl0eSI6MywiZnJlc2giOnRydWUsInR5cGUiOiJhY2Nlc3MifQ.7OrFU8CjrV7BXvddLVCui0BCOCtybmuq7tExdW0pNbE
> Content-Length: 3506
> Content-Type: multipart/form-data; boundary=------------------------0fcee28eab4e279a
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
} [3506 bytes data]
* We are completely uploaded and fine
< HTTP/2 302
< content-type: text/html; charset=utf-8
< date: Wed, 18 Aug 2021 11:35:55 GMT
< location: http://superset.janantos.com/login/
< server: gunicorn/20.0.4
< content-length: 221
<
{ [221 bytes data]
100  3727  100   221  100  3506    863  13695 --:--:-- --:--:-- --:--:-- 14558
* Connection #0 to host superset.janantos.com left intact
* Closing connection 0
api_response: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <title>Redirecting...</title>
Redirecting...

You should be redirected automatically to target URL: /login/. If not click the link.

@MrAmonix
may be X-CSRFTOKEN?
csrf_token : GET /security/csrf_token
headers = {"Authorization": "Bearer Token", "X-CSRFToken": "cstf token"}

Thanks for the response,
I succeeded to get my csrf_token but I still have the redirection to /login even with the csrf_token in "X-CSRFToken" header
Here is the request I tried

HI @junlincc, any idea what can be done, can you please point me to the fraction of code my engineer should investigate?

Hi, all.
Any progress on this issue? I'm trying to overcome it rigth now =/

Hi @pedrohdemedeiros
You can try this workaround (at least it works for me)
  export SUPERSET_BASE_URL=#your superset endpoint
  export URL_AUTH=$SUPERSET_BASE_URL"/api/v1/security/login"
  export URL_CSRF_TOKEN=$SUPERSET_BASE_URL"/api/v1/security/csrf_token/"
  export URL_DATASET_IMPORT=$SUPERSET_BASE_URL"/api/v1/dataset/import/"
  curl -H "Content-Type: application/json" -X POST --data "{\"username\":\"$SUPERSET_AD_USER\",\"password\":\"$SUPERSET_AD_PWD\",\"provider\":\"db\"}" $URL_AUTH >> auth_token.json
  export ACCESS_TOKEN=$(jq '.access_token' auth_token.json | sed 's/"//g')
  curl -c cookies.txt -H "Authorization: Bearer $ACCESS_TOKEN" -L $URL_CSRF_TOKEN >> csrf_token.json
  export CSRF_TOKEN=$(jq '.result' csrf_token.json | sed 's/"//g')
  value=$(cat cookies.txt) && found=${value##*session} && export COOKIE=$(echo $found | sed -e 's/\t//g')

 curl --location --max-redirs 5 \
       --request POST $URL_DATASET_IMPORT \
       --header "Cookie: session=$COOKIE" \
       --header "X-CSRFTOKEN: $CSRF_TOKEN" \
       --header "Authorization: Bearer $ACCESS_TOKEN" \
       --form 'overwrite="true"' \
       --form<EMAIL_ADDRESS> # or
  curl -b cookies.txt --location --max-redirs 5 \
       --request POST $URL_DATASET_IMPORT \
       --header "X-CSRFTOKEN: $CSRF_TOKEN" \
       --header "Authorization: Bearer $ACCESS_TOKEN" \
       --form 'overwrite="true"' \
       --form<EMAIL_ADDRESS>
After investigating, I think the root cause is that superset try to check valid token together cookie which has been provided while getting csrf token.

@long-tranvan is correct, you need to provide an auth token and a CSRF token. If you're working on local testing, which seems to be the case, you can disable CSRF checking by setting WTF_CSRF_ENABLED = False in config.py but obviously you won't necessarily want to do that with production deployments. At this point, this seems to be more of a support/Q&A discussion than an actual bug/issue. I'm going to close this, but it can be continued on Discussions or Slack.


Update API docs with typescript syntax (migration doc/ readme)

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@cacheung  I have addressed comments except for Identity-related docs. I'm not familiar with identity extension, can you create a new PR to fix those issues when you're testing the beta builds?

Ok, will open a new PR for Identity.


OSError: [Errno 75] Value too large for defined data type

$ python3.8 FileSystemSearcher.py --volume=GlacierNationalPark --output_format=csv --output_file=${HOME}/GlacierNationalPark.csv /media/lbp/GlacierNationalPark
Traceback (most recent call last):
File "FileSystemSearcher.py", line 251, in
main()
File "FileSystemSearcher.py", line 241, in main
for record in crawler.path_crawler(base_path):
File "FileSystemSearcher.py", line 175, in next
'dropbox_hash': dropbox_hash(p),
File "FileSystemSearcher.py", line 23, in dropbox_hash
chunk = f.read(HASH_BLOCK_SIZE)
OSError: [Errno 75] Value too large for defined data type
$

Linux Mint
$ uname -a
Linux death-valley 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$ python3.8 --version
Python 3.8.0
$

4 TB NTFS USB HD
$ df -h
Filesystem      Size  Used Avail Use% Mounted on
...
/dev/sdb2       3.7T  3.3T  389G  90% /media/lbp/GlacierNationalPark
$ mount
...
/dev/sdb2 on /media/lbp/GlacierNationalPark type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
$

Instrumented dropbox_hash() and zip_dropbox_hash() so that if/when the error occurs again we have enough information to write a test program.  Also, when the error occurs, the dropbox_hash value in the output record will be an empty string.

$ python3.8 FileSystemSearcher.py --volume=GlacierNationalPark --output_format=csv --output_file=${HOME}/GlacierNationalPark-1.csv /media/lbp/GlacierNationalPark
OSError: [Errno 75] Value too large for defined data type
File Name: /media/lbp/GlacierNationalPark/CampFires-20191231/WIDEBODY/Backup Set 2019-10-09 101506/Backup Files 2019-10-09 101506/Backup files 3252.zip
Hash List Length: 17
...
$
$ head GlacierNationalPark-1.csv
created,dropbox_hash,file_name,full_path,hostname,mime_encoding,mime_type,modified,relative_path,size,suffix,volume
...
$
$ grep 'Backup Set 2019-10-09 101506/Backup Files 2019-10-09 101506/Backup files 3252.zip' GlacierNationalPark-1.csv
2020-01-02T09:10:55.317527+00:00,,Backup files 3252.zip,/media/lbp/GlacierNationalPark/CampFires-20191231/WIDEBODY/Backup Set 2019-10-09 101506/Backup Files 2019-10-09 101506/Backup files 3252.zip,death-valley,,application/zip,2019-10-10T00:11:26+00:00,CampFires-20191231/WIDEBODY/Backup Set 2019-10-09 101506/Backup Files 2019-10-09 101506/Backup files 3252.zip,173407561,.zip,GlacierNationalPark
$
HASH_BLOCK_SIZE is 4,194,304
file size is 173,407,561
42 total reads expected but only 17 succeeded.

What I learned:  When reading large blocks in Python, if the block size being read is larger than the default Python buffer size, bad things can happen.  Might be a bug.  The solution is to turn off buffering which is done on the open statement - ```open(filename, 'r-b', 0) - by using zero for the buffer size.


Adding SpectralFlux class

This adds a class which can do flux calculations with proper error propagation.
There is a new example, Flux_Calculations, which demonstrates the usage.
There is additionally, a small change in the TTELike class which adds some additional print out info.

This is very nice!
However, the best way to compute the flux error for the MLE case is using the integral of the function as a parameter of the fit, so that the error on the flux can be asymmetric as it is computed as usual as the range which gives a likelihood of (best fit likelihood) +/- 0.5 (for a 1-sigma error). This method gets rid of the assumptions of the error propagation, which are: 1) symmetric errors, 2) linear correlations among parameters (i.e., the contour between any two parameters is a 2d Gaussian).
Implementing that is straightforward for a single component (I could write down the math, it's pretty easy), but it requires a little more thoughts for a multicomponent model.

Yes. This method is a bit general. I think it is good to have option of both perhaps? One can always use the flux as a parameter. This is similar to e.g., fitting the background with source to "properly" propagate the errors. I think we could keep these separated.  In reality, there is not a method to asymmetrically propagate errors unless you make a grid or use Bayesian sampling.
The other advantage of "post-fit" flux calculation with this method, is that you can recalculate the parameter ranges on the fly. If one wants the asymmetric errors, then they could build a function that includes the flux (even for components).

I'm merging the pull request right now, this is all very nice.
Let's keep thinking about how to implement the functionality I was talking about, which would probably be part of this new class you made.


[ISSUE 315] Move apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1

Signed-off-by: hantmac<EMAIL_ADDRESS>
Move apiextensions.k8s.io/v1beta1 to apiextensions.k8s.io/v1
fix Issue 315

We need to use kubectl conver to convert the apiextensions.k8s.io/v1 to apiextensions.k8s.io/v1beta1 in function-mesh/config/crd/patches, but the kube version in my machine can't do this beacause I don't have the lower version.

So can you do the kubectl convert ?

@hantmac I have tried with the convert plugin, seems we need to use a lower version's kubectl and related client release to do this. lets try use the kubectl image like https://hub.docker.com/r/bitnami/kubectl

@hantmac I have tried with the convert plugin, seems we need to use a lower version's kubectl and related client release to do this. lets try use the kubectl image like https://hub.docker.com/r/bitnami/kubectl

Yes, I have done this convert. But we need to modify the k8s version in github ci, wait for me.

@freeznet I guess the helm chart of local-storage-provisioner is not newest, the version of DaemonSet in it is extensions/v1beta1, I have made this issue

thanks @hantmac, from my experience, the local-storage-provisioner might not a MUST have service in the test environment, so maybe we can simplifier the Github Action script to make the Pulsar install minimal (see https://github.com/streamnative/function-mesh/pull/331)

@freeznet  Copy that.


jpa doc Customer entity code invalide "[" token

In Jpa document, Customer entity code has wrong token "[" in "setLastName" method. Replacing "[" to "{" make setLastName method become  valid.

Ah, thanks for spotting that one!
Looks good to me.

I'll just merge this, thanks again!


Issue 165 bs modal

Pull Request Description:
(Description in grammatically correct, complete sentences)
New Pull Request Checklist:

[x] Reviewed contributing guidelines.
[x] good commit messages
[x] Github issue added, if it exists.
[ ] Added an entry to the Changelog.
[ ] All tests passing and new component tests include ember-a11y-testing to test accessibility.

Still need to look at this in more detail, can you get a heroku deploy up so we can view/test it?

@Samsinite @jweakley This is ready for review.
It is a very basic modal that follows the bootstrap 4 concepts for modal.

Give me a few days to do an in depth review, but in the meantime can you get a PR deploy for this?

@Samsinite I do not have access to the Heroku pipeline for this. I'll ask Joe to add me and see if I can get a PR instance up for review.

https://github.com/wildland/ember-bootstrap-controls/pull/197 should be addressed before this is finished being reviewed.

I'll pull this down and take a look locally

@jweakley I wanted to review this before getting it merged

Sorry @jweakley, nothing to get overly frustrated about. I'll review and provide feedback today if any, and if there is any we can discuss adding issues for them.


Log in/ Log out to existing user profile flow

It should allow to log in already existing users

forgot password - as restore in beam wallet.
For logout - a new screen is needed

Restore flow and Log in screen are checked.
The logout will be checked after completing https://github.com/SOURC3XYZ/sourc3/issues/131

Checked


Could not find module ... for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator,

Description
Hello.
Context
We have RN iOS project with CocoaPods dependecies, but we want to add some dependencies via SPM.
In our Podfile, we have following lines:
 installer.pods_project.build_configurations.each do |config|
      config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end

Without this lines — build fails by different errors from Pods
Right now if we will try to add SPM package to project, we have two scenarios:

Option 1 : Rosetta — turn on, project with connected SPM + Pods builds correctly. We don't want to use Rosetta at all
Option 2 : Rosetta — turn off, project build with connected SPM + Pods fails with an error Could not find module PACKAGE NAME for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator

What we want to achive
We want to be able to add SPM packages to Xcode project, continue to use Pods and don't use Rosetta . Does any one faced with this problem or has some solutions?
React Native Version
0.7
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.1
CPU: (10) x64 Apple M1 Pro
Memory: 227.15 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.20.0 - /usr/local/opt/node@16/bin/node
Yarn: 1.22.11 - ~/Documents/WORK/Breadfast/ReactNative-customer-app/node_modules/.bin/yarn
npm: 6.14.13 - ~/Documents/WORK/Breadfast/ReactNative-customer-app/node_modules/.bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: Not Found
Python: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce

Xcode project generated by RN tools
Any SPM package
Turn off Rosetta on Mac

Snack, code example, screenshot, or link to a repository

Hi, you can use this in your podfile :
post_install do |installer|
      installer.pods_project.targets.each do |target|
        target.build_configurations.each do |config|
          config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
        end
      end
end


Umar/4903 external resources false broken

What are the relevant tickets?
closes https://github.com/mitodl/hq/issues/4903
Description (What does it do?)
Fixes the false is_broken flag in case of Ignored HTTP status codes. And adds the functionality to update is_broken flag on each check rather waiting to be set manually.
How can this be tested?

switch to branch 'umar/4903-external-resources-false-broken'
Restart containers.
From celery logs, verify a repeated task should be added in the celery with name check-broken-external-urls. Task is set to repeat every week. Frequency can be modified by changing CHECK_EXTERNAL_RESOURCE_STATUS_FREQUENCY in main/settings.py
Go to http://localhost:8043/admin/external_resources/externalresourcestate/. This should already be created.
External Resource States should have been populated with existing url checks after first execution of task.

Additional Testing
To manually test the functionality locally with a batch of urls

Spin up containers
Get into Django shell: docker-compose exec web ./manage.py shell
Run following commands to import necessary code:

from external_resources.tasks import check_external_resources
from websites.models import WebsiteContent
from websites.constants import CONTENT_TYPE_EXTERNAL_RESOURCE

Get website content data:
external_resources = list(WebsiteContent.objects.filter(type=CONTENT_TYPE_EXTERNAL_RESOURCE).values_list("id", flat=True))
(Optional) check length of data and splice if necessary: len(external_resources) and external_resources = external_resources[:1]
run checking task: check_external_resources(external_resources)
to validate resource was updated or created, retrieve resource from.DB:

resources = WebsiteContent.objects.filter(id__in=external_resources).select_related("external_resource_state")
resource = next(resources.iterator())
str(resource.external_resource_state.last_checked)
resource.metadata['is_broken']

To test if flag is updated on each try, manually update flag and save.

resource.metadata['is_broken'] = not resource.metadata['is_broken']
resource.save()

execute step 6
Validate last_checked and flag again of the updated resource.

resource = WebsiteContent.objects.get(id=resource.id)
print(str(resource.external_resource_state.last_checked), resource.metadata['is_broken'])

To manually execute task in celery

Spin up containers
Get into Django shell: docker-compose exec web ./manage.py shell
Run following commands to import necessary code:

from external_resources.tasks import check_external_resources_for_breakages
results = check_external_resources_for_breakages.apply()

** This might produce large number of urls to check and may take some time to complete.

I'm still confused about the business logic around the backup_url. Do we have a process yet for setting backup_url? When do we use the backup_url, if ever?

I'm still confused about the business logic around the backup_url. Do we have a process yet for setting backup_url? When do we use the backup_url, if ever?

No, we do not have any process yet.
Backup URL is used when the link checker marks the main url as broken. It was kinda contingency to keep the resources working until someone can check and update main URL.
@pdpinch If there is no plan to add a process for backup URL, I'll drop it. Currently, it's serving no purpose.

Thanks for the reminder Paul.
We decided that we weren't ready to do any automated failover to back_url. Without that, I don't think it makes sense to include the backup_url in the calculation of whether or not the link is broken.
We could remove it altogether, but one of our next issues in this epic is to work on "when publishing a course, submit external links to the Internet Archive" at which point it may be convenient to have a field to store the internet archive URL on, even if there is no automated failover.


Codec Settings missing

What version of Music Assistant has the issue?
2.0.0b129
What version of the Home Assistant Integration have you got installed?
2024.3.5
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
As TuneIn streams via Chromecast stutter I wanted to change Codec Settings. These are somehow gone. Is this a Bug or did the way of changing Codec Settings change?
How to reproduce
Goto Settings -> Player -> select any Chromecast player or group -> No Codec Settings
Music Providers
Any
Player Providers
Chromecast
Full log output
No response
Additional information
I remember I had the Codec settings in a previous version
What version of Home Assistant Core are your running
2024.3.3
What type of installation are you running?
Home Assistant Supervised
On what type of hardware are you running?
Raspberry Pi

As MA is designed with high quality playback in mind that option was removed. If your problem is bandwidth related then you need to improve your wifi coverage.


signed-by option is not supported for ar+https

Documentations instructions are like following:
echo "deb ar+https://<location>-apt.pkg.dev/projects/<project> <repository> main" | sudo tee -a  /etc/apt/sources.list.d/artifact-registry.list
curl https://<location>-apt.pkg.dev/doc/repo-signing-key.gpg | sudo apt-key add -
sudo apt update

This would work, but managing GPG keys by apt-key is currently deprecated. Using /etc/apt/keyrings/... is recommended, but ar+https handling by this plugin looks not supporting signed-by=... option.
...
W: ar+https://<location>-apt.pkg.dev/projects/<project>/dists/<repository>/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

Expected flow is following.
echo "deb [signed-by=/etc/apt/keyrings/<location>-artifact.gpg] ar+https://<location>-apt.pkg.dev/projects/<project> <repository> main" | sudo tee -a  /etc/apt/sources.list.d/artifact-registry.list
sudo curl https://<location>-apt.pkg.dev/doc/repo-signing-key.gpg -o /etc/apt/keyrings/<location>-artifact.gpg

But this causes error:
...
Err:5 ar+https://<location>-apt.pkg.dev/projects/<project> <repository> InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY <GPG-KEY-NAME>
...
W: GPG error: ar+https://<location>-apt.pkg.dev/projects/<project> <repository> InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY <GPG-KEY-NAME>
E: The repository 'ar+https://<location>-apt.pkg.dev/projects/<project> <repository> InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

Confirmed in Ubuntu22.04 Google Cloud Compute Engine environment. Thanks

Thanks for reporting, we will investigate updating the signing method

That would be great, thanks!

@hopkiw Any update on this?


Tests for the new OCF API

This PR introduces tests to cover the new spec and a grunt plugin for using the test runner more conveniently.
@zolkis could you PTAL at the tests?

Looks OK. We'll need to update it, but merging now.


nextEventMatchingMask should only be called from the Main Thread!

My NSApp is spawn from a Swift macOS app via a C-Bridge, so when I run the example code I get this on repeat:
2021-08-16 06:21:50.969117-0400 FileVacuum[91744:1673051] [General] nextEventMatchingMask should only be called from the Main Thread!
2021-08-16 06:21:50.970995-0400 FileVacuum[91744:1673051] [General] (
	0   CoreFoundation                      0x00007fff204a883b __exceptionPreprocess + 242
	1   libobjc.A.dylib                     0x00007fff201e0d92 objc_exception_throw + 48
	2   AppKit                              0x00007fff22c328a6 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 4389
	3   AppKit                              0x00007fff22c24049 -[NSApplication run] + 586
	4   FileVacuum                          0x0000000109b04084 _ZN11file_vacuum22image_capture_core_mod22image_capture_core_mod4init17h10b6b7d5e76aef8eE + 564
	5   FileVacuum                          0x0000000109ae2d33 _ZN11file_vacuum17init_loop_volumes17h715758eb3a44f7eeE + 387
	6   FileVacuum                          0x0000000109b1b0d8 _ZN4core3ops8function2Fn4call17h9752bcaecc8b4485E + 40
	7   FileVacuum                          0x0000000109b1a358 _ZN13opentelemetry5trace6tracer6Tracer7in_span17h5a26264b6eb7eb0aE + 1256
	8   FileVacuum                          0x0000000109b0b8e0 _ZN11file_vacuum7metrics7metrics12sunrise_span17h1c89c7b016c5cce2E + 256
	9   FileVacuum                          0x0000000109b18c78 _ZN13opentelemetry5trace6tracer6Tracer7in_span17h2176a53700f9ffcdE + 904
	10  FileVacuum                          0x0000000109ae4511 mac_fv_init + 241
	11  FileVacuum                          0x000000010989bce3 $s10FileVacuum0aB9OperationC4mainyyF + 10419
	12  FileVacuum                          0x000000010989bf25 $s10FileVacuum0aB9OperationC4mainyyFTo + 85
	13  FileVacuum                          0x000000010995f31e $s10FileVacuum14AsyncOperationC5startyyF + 590
	14  FileVacuum                          0x000000010995f435 $s10FileVacuum14AsyncOperationC5startyyFTo + 85
	15  Foundation                          0x00007fff2119d2af __NSOPERATIONQUEUE_IS_STARTING_AN_OPERATION__ + 17
	16  Foundation                          0x00007fff2119d182 __NSOQSchedule_f + 182
	17  libdispatch.dylib                   0x000000010c029264 _dispatch_client_callout + 8
	18  libdispatch.dylib                   0x000000010c02ca75 _dispatch_block_invoke_direct + 286
	19  libclang_rt.tsan_osx_dynamic.dylib  0x000000010b0a75ac _ZN6__tsanL24invoke_and_release_blockEPv + 12
	20  libclang_rt.tsan_osx_dynamic.dylib  0x000000010b0a7302 _ZN6__tsanL22dispatch_callback_wrapEPv + 306
	21  libdispatch.dylib                   0x000000010c029264 _dispatch_client_callout + 8
	22  libdispatch.dylib                   0x000000010c02c0b8 _dispatch_continuation_pop + 577
	23  libdispatch.dylib                   0x000000010c02b17b _dispatch_async_redirect_invoke + 743
	24  libdispatch.dylib                   0x000000010c03d2be _dispatch_root_queue_drain + 334
	25  libdispatch.dylib                   0x000000010c03dd3f _dispatch_worker_thread2 + 127
	26  libsystem_pthread.dylib             0x000000010c0d1ac7 _pthread_wqthread + 244
	27  libsystem_pthread.dylib             0x000000010c0d0ae3 start_wqthread + 15
)

Like, 200 of them in under a second, they come really fast!
Any insight would be greatly appreciated @brandonhamilton 🙇 🌞

I think https://github.com/SSheldon/rust-dispatch/ could be applied to resolve. Tinkering now... ⏳

Solved wrapping the example in some async dispatches:
    pub fn init(queue: Queue) {
        unsafe {
            queue.clone().barrier_async(move || {
                let main = Queue::main();

                main.barrier_async(|| {
                    let _pool = NSAutoreleasePool::new(nil);
                    ...

See https://github.com/SSheldon/rust-dispatch/tree/master/examples
and the Rust-Dispatch docs for barrier_async (not sure if barrier_async was required but sounded safer from the docs).


State of this project / Fork

After submitting a pull request, i noticed that there are 46 open pull requests. Is nobody even accepting contributions for this project anymore?
I've read the statement, that they are shifting to Propel 3, but i can't agree with this mentality. It's never a good idea to start over and completly rewrite your project. Chances are high, that this will be the end of it.
Also i don't see much sense in stating that ActiveRecord is not modern anymore. This is not fashion. I have many commercial projects, that rely on Propel2. And i think it's a great peace of software which offers a better over all solution than any other ORM.
So if this project is dead for real, who's in for creating a fork and keep Propel 2 going under a new name?
@marcj

Is nobody even accepting contributions for this project anymore?

Correct. Propel2 is a enormously complex peace of software because it covers so many concerns and functionality. Managing PRs mean you have to have constantly in your mind all implications that new code brings in. Just merging without caring about side effects is easy. Keeping the quality up is hard work. And it's an unrealistic goal if you don't even use the library anymore in your own projects, even more if you don't use that PHP technology as whole anymore.
Feel free to create a fork and merge all pull-requests there. I'm more than happy to link to it once the fork reached a release and when it has same feature-set. But to be honest, why would someone invest time creating a fork and redo all the release/doc stuff, when they can just take over the project? We're looking for a new maintainer for years, but nobody wanted to invest that time. I mean here as well, taking the position is easy, but doing the actual work is a tough job. And you don't even need a position title or permission in order to handle issues, test PRs, give feedback, etc. Obviously nobody wanted to do it. What could be the reason for this is left to speculation.

I've read the statement, that they are shifting to Propel 3, but i can't agree with this mentality.

You don't have to agree, that's ok.

It's never a good idea to start over and completely rewrite your project.

That's where I disagree :)

Chances are high, that this will be the end of it.

That (Propel2 death) was the sole purpose of creating Propel 3. But latter died due to same reason as v2: Lack of contribution for a really sophisticated project that doesn't subsidize its work in any way.
It was even tried to find sponsors for the project, but nobody wanted to pay for it. So there it goes: A project where people contribute PRs, sometimes event without comments, just throw in code. Nobody checks PRs, nobody checks issues, nobody wants to pay, usage decreases. I can only summarize with: Propel had its best time and many people invested hundred of thousands dollars in it. That changed and it's time to move on.

Also i don't see much sense in stating that ActiveRecord is not modern anymore. This is not fashion.

Code is like fashion. And ActiveRecord has its objective flaws.

I have many commercial projects, that rely on Propel2.

Guess what: I invested many ten thousand $ and you earn with it money. It's either time to invest back or let the project die. Complaining why someone else does not want to do even more free work is not enough. Taking action is the only way to keep it alive.

@marcj WHAT? You don't want to do more free work, so i can make money off of it?  For me it's just that i have many commercial projects relying on Propel and i think it's very good for what it does. Still better than what most other ORMs offer. But no customer in the world is paying me to migrate to another ORM, because they won't get anything out of it. Customers only pay for features.
So i would be willing to help out this project and merge the PRs and fix at least the issues, my customers are paying for. May not be much, but at least better than it is now.


A general data structure for n-dimensional arrays

I think we should re-think the array data structures we have. Most other libraries have a general tensor notation, including views. In particular, we should investigate how we can use external code for this.
Main functions should be

Easy data structure for I/O over interfaces.
Support for views and slices so that we for example dont have to copy things around when we do subsets of dimensions, see @lambday in #2530

Or can we solve this otherwise somehow? In any case, we should aim for some major clean ups there. The current SGMatrix structure is polluted with lots of linear algebra operations, and not very flexible.

@karlnapf I would like to take this issue, how to start working ?

This is nontrivial, please only attempt if you have an idea what you are doing.
Googling libraries for this is the first step. Note that we want just memory management of such structures, math operations will be done via linalg


Errors found with linter.

I thought I'd share some errors I found with the linter.  Please review.

I've added that last commit #20d781f in order to actually fix my problem but it isn't clear why you'd call load with no arguments and also why it causes the widget to break ONLY when mootools is on the page.

Thank you for these fixes.
I will double-check the load() call again today. I see that it's not required, but I want to double-test this. Will merge this then.
Kind regards,
Tim

Okay you are right. expose() returns the jQuery object and not the inbound mask object. So calling load() on it is not calling $.mask.load() but rather $.load(). Since no url is given, it does not do anything (thankfully).
Thanks for these suggestions. Merging them.


HHH-10341 - Specification violation in Implementation of TupleElement

https://hibernate.atlassian.net/browse/HHH-10341

Looks good.

applied upstream


Official Operator on operatorhub.io

Any plans to create an official operator for NATS on the newly minted www.operatorhub.io?

Would be great to list it there, looks like this has to be followed: https://www.operatorhub.io/contribute
And also need to confirm support for OLM for the operator https://github.com/operator-framework/operator-lifecycle-manager

+1. Just bumped into the project. Didn't notice it before as it wasn't on the hub.

Hi, is there any timeline for when nats-operator and nats-streaming-operator would be provided on operatorhub? Thanks.


[Issue-1617] - Traffic Ops Keeps track of configuration differences between database and Traffic Servers

PR for feature #1617

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

ok to test

@KevinMackenzie this PR has a lot of merge commits,  which makes it difficult to examine.   Can you use git rebase -i master and get rid of those?

I rebased my fork to remove all of the merged commits and then merged the routes.go as the last item.  Is  this OK?

@KevinMackenzie Github still shows conflicts in the PR. Can you please take another look?


Increase the serial limit for RKE2 agents play (or make it configurable)

In site.yml the 'Agent Play' has serial: 3 set. This makes creating clusters with hundreds or thousands of agents painfully slow (on the order of hours or days).
Earlier versions of this did not have such a limit on the agents play. Is there a reason such a small limit was set on the agents? Can this number be increased to something more reasonable like 50 or made a variable like
serial: "{{ agent_play_limit | default(3) }}"

@aaron-iles Thank you for the suggestion. This limit was originally imposed due to a bug in an older RKE2 implementation where the ETCD database joining process would hit a race condition if more than one was trying to join the cluster at one time. If this condition lasted long enough the joining process would time-out and the member would be permanently rejected. I believe this problem has since been resolved and we can increase the limit. It will now initialize the first server in the inventory list and do the rest up to 5 at a time and 10 at a time for agents.
see #227


Is it possible to record internal audio not microphone?

When I run wf-recorder -a my laptop microphone gets recorded. The manual suggest to run pactl list sinks which gives alsa_output.pci-0000_00_1b.0.analog-stereo in my case. But wf-recorder -a alsa_output.pci-0000_00_1b.0.analog-stereo still records my microphone and Using PulseAudio device: default gets printed to the console.

See issue #39.

Thanks a lot! Either wf-recorder -a0 or wf-recorder --audio=0 does what I want.


[Feature] Offer certain methods that merge data from multiple registries

For example getSchemes.

@nichtich Can you think of any other case where it is necessary to merge results from multiple registries? I could think of a getConcept method that uses the list of previously loaded schemes to determine the right registry where a certain concept can be loaded from. But that isn't used anywhere right now, so we can add it later if necessary.


expand the type system, part 1

[ ] Arbitrary expressions in range types
[x] Nominal types
[ ] Type functions
[ ] Records
[ ] Constructors & pattern matching
[ ] Existentials (in particular, functions)

Nominal types are mostly done in 95c476a2666e40c922e7dae5c8984689d5f92e97. There's still a fairly important bit missing, which is that
type A = 0 upto 10
type B = A
let x: A = 5
let y: B = a

will error with "incompatible types", even though it shouldn't. This is because the Unifier does not have access to the context. Fixing that might require some rearchitecting.
Error messages are also subpar, since check_int_type for instance very eagerly expands types. As such, something like
type A = 0 upto 10 -> 0 upto 10
let x: A = 10

will give an error message like
error[ET04]: cannot create non-numeric type with a number
  ┌─ test.z:2:11
  │
2 │ let x: A = 10
  │            ^^ a number cannot initialize '10 -> 10'

which is true, but a better message might be
error[ET04]: cannot create non-numeric type with a number
  ┌─ test.z:2:11
  │
2 │ let x: A = 10
  │            ^^ a number cannot initialize 'A'

46e2b05b7ef8889e2e4582a8ea919016f335541e did the initial implementation. The basic idea is that range types contain arbitrary expressions, which are lifted to top-level bindings just before type checking. This means that the elaborator is mostly unchanged, and can handle the range values like any other value. I didn't do the code generator, so it just panics when using integer types (as if you have any other choice hehe), and pretty-printing for types is terrible (_t5 upto _t10 is not useful).

I think explicit coercions (#22) will be useful for checking range types. This would move the responsibility of checking range compatibility to *somewhere* in the elaborator, instead of doing it in the unifier. Presumably this would be after partial evaluation with a run time check if the ranges are incompatible, but that needs more thought.

Nominal types (pretty much) done in 12a3b951fa309fc1317c8d2143420e59b3326151.

Range types with arbitrary expressions done with 280c100838b8598531bf98555b130f36c9577cfe.


Migrate to GO module and Use offficial compiler for cross-compiling

Since Module has become the official dependency manager for Golang, and Golang has provided cross-compiling ability in the official compiler, there's no need to rely on third party tools like Godeps or gox.
Is there any plan to remove Gox and Godeps? If I submit a PR about this, would it be accepted?

Hey @QuantumGhost, I don't have a plan to remove Gox and Godeps, but PRs are welcome :)

Ok, I'll send a PR once I have finished cleanup.

resolved in #28

I got errors below after running go get -u github.com/git-hooks/git-hooks
❯ go get -u github.com/git-hooks/git-hooks
# github.com/git-hooks/git-hooks
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:27:13: cannot use bind(list) (type func(*cli.Context)) as type cli.ActionFunc in assignment
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:31:4: unknown field 'ShortName' in struct literal of type cli.Command
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:33:4: cannot use bind(install, true) (type func(*cli.Context)) as type cli.ActionFunc in field value
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:38:4: cannot use bind(uninstall) (type func(*cli.Context)) as type cli.ActionFunc in field value
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:43:4: cannot use func literal (type func(*cli.Context)) as type cli.ActionFunc in field value
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:54:4: cannot use bind(uninstallGlobal) (type func(*cli.Context)) as type cli.ActionFunc in field value
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:59:4: cannot use func literal (type func(*cli.Context)) as type cli.ActionFunc in field value
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:72:4: cannot use func literal (type func(*cli.Context)) as type cli.ActionFunc in field value
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:73:15: cannot use c.Args() (type cli.Args) as type []string in argument to run
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:78:4: unknown field 'ShortName' in struct literal of type cli.Command
/Users/momo/.cache/go/src/github.com/git-hooks/git-hooks/cli.go:78:4: too many errors

I believe I have fixed this issue in my PR #28, so I guess @CatTail you need to tag the master branch in order to make git-hooks go gettable.

@QuantumGhost I tag the latest master with v1.3.0, but the error is still there.

It seems that go get -u -v github.com/git-hooks/git-hooks works for me now.

@QuantumGhost 👍