[Candidate 4v4 Persian Gulf Conflict ZH v5] Civilian structures show as POI on radar

Observed behavior
Civilian structures show as POI on radar.
Expected behavior
Civilian structures do not show as POI on radar.
Screenshots

fixed

Fixed in principle.
There still are towers showing as POI. Perhaps we can replace the unusable towers with another structure?


not working on GL753V

:/
$ rogauracore rainbow
Could not open ROG Aura Core keyboard: LIBUSB_ERROR_ACCESS
(Dae#5125 in discord -<EMAIL_ADDRESS>

Use sudo rogauracore ______
This happens because the current user (even the administrator) restricts the access to devices.

thanks you, i will try


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 196 ms

Resolved: ClamAV performance has improved in 585ae76.


Cannot open map files

Describe the bug
I can't open all output of glim using the offline viewer like below.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Just executed offline viewer and clicked open map
ros2 run glim_ros offline_viewer
Screenshots

Environment (please complete the following information):

CPU/GPU: intel
OS: ubuntu 22.04
ROS: ros2 humble
CUDA: cuda 12.2
Build with CUDA: on

Additional context
Add any other context about the problem here.

I already installed zenity kdialog

sorry.. i have a mistake : <


Airflow 10893 - Clickhouse Operator

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Testing providers with sql and template files(*_tf)


rpc: add node color to NodeUpdate and GetInfo

This adds the node color to both NodeUpdate (as part of aGraphTopologyUpdate) and to GetInfo response. Tested with a Go gRPC client.
Fixes https://github.com/lightningnetwork/lnd/issues/2255 and https://github.com/lightningnetwork/lnd/issues/2268

@halseth I made it with a separate commit per package as you suggested and also added a test. Something I am not convinced though is exposing the utility method EncodeHexColor from the routing package but I wasn't sure where to put it. Seems weird to me, I am open to changes.

Rebased

@halseth rebased with latest master + proto files regenerated

@xsb looks like we have another conflict 😶

@halseth @cfromknecht Rebased again.
Note: While regenerating the proto files I got a different result for lnrpc/invoicesrpc/invoices.pb.go that I ignored it for the sake of cleanliness. It seems to come from the recently merged #3019. Either the author of that PR or myself are not running the correct protoc, etc. Probably not super important but better to clarify before merging this.

Yet another proto conflict 🤕

Note: While regenerating the proto files I got a different result for lnrpc/invoicesrpc/invoices.pb.go that I ignored it for the sake of cleanliness.

If you still see this after rebasing on master, check your proto+tools version. I just tried rebasing this on master, and regenerating the protos doesn't create any changes to that file for me.

@halseth rebased again. No issue regenerating protos this time (tried on master and on my branch).

sorry @xsb, there was a conflict w/ #3082 :/ you'll need to rebase on master and ensure that your protogen version is on 0.1.3 (step 2 of https://github.com/lightningnetwork/lnd/tree/master/lnrpc#generate-protobuf-definitions)
Feel free to ping me when you're ready, hoping to minimize the number of rebases on your end 😬

@cfromknecht  rebased again after upgrading to new protobuf version


How to perisist in  this situation

i have code like this
state: {
left_open: true,
user: {
name: "Addison",
job: "web developer"
}
}
Now how do i persist name

@sra1katta by first reading the documentation


Serial port over bluetooth not working with Ubuntu or macOS but Android app working

I have a Bittle X BiBoard V0_1, and I am using the current default branch of that repo to flash the sketch.
On Android - OK
I can use the Android app after pairing my Bittle with it with no problem:
20:47:33:771 -> Pairing success!!
20:49:04:176 -> Bluetooth connected!
20:49:05:773 -> G
20:49:05:775 -> Bittle
20:49:05:775 -> B01_231206
20:49:05:775 -> ?
20:49:40:628 -> Bluetooth disconnected!

Notice that we can see the message "Bluetooth connected!" coming from the bleUart.hfile.
On macOS - FAIL
I can pair with the Bittle from a macOS M2/3 (after enabling all the macOS security for VSCode/Terminal).
In the Bittle logs I can see "Pairing success!!" but I never see a "Bluetooth connected!" message.
I can see two serial sockets /dev/tty.Bittle67_SSP and /dev/tty.Bluetooth-Incoming-Port and I can also open them but I see no message received and the one I send seems to have no effect on the Bittle.
It might not be related at all, but I also noticed this function called void readBlueSSP() that is commented in io.h.
On Ubuntu - FAIL
I am using Ubuntu 23.10. Here it seems to be something else than the issue seen on macOS, since I cannot pair the Bittle with Ubuntu.
When trying, Ubuntu shows a security popup with a PIN number which is the same as the one printed on the serial port of the Bittle. Then, when I click yes, the process hangs and ends up timing out with a failure. Looking at the Ubuntu logs, it seems to be related to authentication.
It's weird because on macOS, I don't see any popup with a PIN code.

I tried using multiple versions of ESP32 from https://github.com/espressif/arduino-esp32: 2.0.12 (the one recommended), 2.0.13 and 2.0.14.

If you have any idea what's going on or what I am doing wrong, please let me know. ping @borntoleave

/dev/tty.Bluetooth-Incoming-Port is not related to Bittle.
After connecting Bittle in the Bluetooth settings, it would stay connected. Only when you open other programs, such as the PetoiDesktopApp's Calibrator, Skill Composer, and the Python serial API, the port will be visited and connected if the handshake is successful.


Support shorten dataset state store name

Created DatasetUrnStateStoreNameParser for providing the mapping between datasetUrn and state store name.
It currently has two implementations. The default: SimpleDatasetUrnStateStoreNameParser and SHA1 based guid: GuidDatasetUrnStateStoreNameParser.
FsDatasetStateStore has this feature enabled. It is backwards compatible.
Other DatasetStateStore can also have this feature.
@htran1 or @ibuenros  can you take a look?

@htran1 Comments addressed.


Nuxt.js contains a GPL licensed library

What problem does this feature solve?
We should not use GPL licensed libraries as it makes Nuxt.js also GPL. Currently, we have<EMAIL_ADDRESS>@ GPL-3.0-only which makes Nuxt.js GPL.
What does the proposed changes look like?
Update extract-css-chunks-webpack-plugin not to use GPL licensed versions of webpack-external-import.

This feature request is available on Nuxt community (#c10481)

I apologize if the library is only "used" when we build webpacks "locally" and the library is not shipped in it. In that case, the library might not make Nuxt.js GPL though I'm not so sure because I'm not a lawyer.

+1. My project is closed-source, so this matters to me. I've noticed this for some time, but realised it's only used when build, so unless the production environment runs a webpack build, it's ok to use.
To be safe, I'd really want to separate the code required to run Nuxt and code required to build Nuxt into the dependencies and devDependencies sections of my package.json file respectively. This way, I can prove that I am not using this GPL license in production, and only for development.
My proposed solution is instead of simply specifying nuxt in your package.json, be able to split it into nuxt-runtime and nuxt-compiletime dependencies:
{
  "name": "my-project",
  "version": "1.0.0",
  ...
  "dependencies": {
    "nuxt-runtime": "^2.11.0",
    ...
  },
  "devDependencies": {
    "nuxt-compiletime": "^2.11.0",
    ...
  }
}

This effect may already be possible, as the affected code is all within the @nuxt/webpack sub-dependency, but not sure that it will work correctly if I list only these @nuxt sub-dependencies manually:
{
  "name": "my-project",
  "version": "1.0.0",
  ...
  "dependencies": {
    "@nuxt/cli": "2.11.0",
    "@nuxt/core": "2.11.0",
    "@nuxt/opencollective": "^0.3.0",
    ....
  },
  "devDependencies": {
    "@nuxt/builder": "2.11.0",
    "@nuxt/generator": "2.11.0",
    "@nuxt/loading-screen": "^1.2.0",
    "@nuxt/webpack": "2.11.0",
    ....
  }
}

Please confirm whether the method I have proposed would actually work?

Thank you for the suggestion. Although I had to tweak package.json like this:
-    "dev": "nuxt",
-    "build": "nuxt build",
-    "start": "nuxt start",
-    "generate": "nuxt generate",
+    "dev": "nuxt-cli",
+    "build": "nuxt-cli build",
+    "start": "nuxt-cli start",
+    "generate": "nuxt-cli generate",

I think it's working because license-checker --production --summary doesn't output any GPLs.
Also I think it is better for the community to split the packages into nuxt-runtime and nuxt-compiletime.

It actually worked? Lol

I tried dev, build, start and it seemed to work. haha

Hi :)
Actually package name is nuxt-start which you can put in dependencies and nuxt to devDependencies. (see appendix)
Also, nuxt extracts all client bundle library licenses into /_nuxt/LICENSES file (src)
I'm not a lawyer but Generally speaking, GPL is all about code ownership. If a library used for server-side rendering or build phase and only HTML result coming out to the client, it is not subject to GPL unless you, for example, want to publish/distribute the entire nuxt application in a docker image or that library is also used for client-side which means "A GPL code that is running on your system but source is not available". Anyway, it is a confusing issue with GPL. Dear Richard never liked SaaS

Appendix: Current nuxt-start licenses:
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  └─ path: nuxt-start/node_modules/@nuxt/cli
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  └─ path: nuxt-start/node_modules/@nuxt/cli/node_modules/@nuxt/config
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  └─ path: nuxt-start/node_modules/@nuxt/core
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  └─ path: nuxt-start/node_modules/@nuxt/core/node_modules/@nuxt/server
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  └─ path: nuxt-start/node_modules/@nuxt/cli/node_modules/@nuxt/utils
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  └─ path: nuxt-start/node_modules/@nuxt/core/node_modules/@nuxt/vue-renderer
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/chalk/chalk
│  ├─ path: nuxt-start/node_modules/@nuxt/cli/node_modules/chalk
│  └─ licenseFile: nuxt-start/node_modules/@nuxt/cli/node_modules/chalk/license
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/visionmedia/debug
│  ├─ publisher: TJ Holowaychuk
│  ├─ email<EMAIL_ADDRESS>│  ├─ path: nuxt-start/node_modules/@nuxt/core/node_modules/debug
│  └─ licenseFile: nuxt-start/node_modules/@nuxt/core/node_modules/debug/LICENSE
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/bevacqua/hash-sum
│  ├─ path: nuxt-start/node_modules/@nuxt/cli/node_modules/@nuxt/utils/node_modules/hash-sum
│  └─ licenseFile: nuxt-start/node_modules/@nuxt/cli/node_modules/@nuxt/utils/node_modules/hash-sum/license
├─<EMAIL_ADDRESS>│  ├─ licenses: MIT
│  ├─ repository: https://github.com/nuxt/nuxt.js
│  ├─ path: nuxt-start
│  └─ licenseFile: nuxt-start/LICENSE
└─<EMAIL_ADDRESS>   ├─ licenses: ISC
   ├─ repository: https://github.com/npm/node-semver
   ├─ path: nuxt-start/node_modules/@nuxt/cli/node_modules/@nuxt/utils/node_modules/semver
   └─ licenseFile: nuxt-start/node_modules/@nuxt/cli/node_modules/@nuxt/utils/node_modules/semver/LICENSE


Is there a paid version? I want a source code

Is there a paid version? I want a source code

You mean like on the repository you're commenting on?
https://github.com/cambecc/earth/tree/master/public/libs/earth/1.0.0

yes

That's the javascript source code. The other libraries in libs are utilized in order to do various functional things within earth.

I want to know how to realize the function of HTSGW, but I don't know much about it.

I want to know how to realize the function of HTSGW ( Significant Wave Height ), but I don't know much about it

Look at the actual site, browser code inspector. Grep for HTSGW. You'll find createHTSGWPalette in HTSGW.js based on generic buildScaleFromSegments.
`
import {buildScaleFromSegments} from "./palette.js";
export function createHTSGWPalette(resolution = 1000) {
const bounds = [0, 15];  // units: m
const segments = [
    [ 0, [  8,  29,  88]],
    [ 1, [ 37,  52, 148]],
    [ 2, [ 34,  94, 168]],
    [ 3, [ 29, 145, 192]],
    [ 4, [ 65, 182, 196]],
    [ 5, [127, 205, 187]],
    [ 6, [199, 233, 180]],
    [ 7, [237, 248, 177]],
    [ 8, [254, 204,  92]],
    [10, [253, 141,  60]],
    [12, [240,  59,  32]],
    [14, [189,   0,  38]],
];
return buildScaleFromSegments(bounds, segments, resolution);

}
`


(PUP-10815) Add puppet facts diff command

Output when no facts differ:
[root@dental-township ~]# puppet facts diff
2021-01-13 13:04:01.984689 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
{}

Output when facts differ:
[root@dental-township ~]# puppet facts diff
2021-01-13 13:10:05.164558 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
{"facterversion":{"new_value":"\"4.0.43\"","old_value":"\"3.14.14\""},"memory.system.available":{"new_value":"\"5.94 GiB\"","old_value":"\"6.12 GiB\""},"memory.system.available_bytes":{"new_value":"6377148416","old_value":"6572556288"},"memory.system.capacity":{"new_value":"\"22.25%\"","old_value":"\"19.87%\""}}

Prettier puppet facts diff with jq:
[root@dental-township ~]# puppet facts diff | jq
2021-01-13 13:09:44.938110 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
{
  "facterversion": {
    "new_value": "\"4.0.43\"",
    "old_value": "\"3.14.14\""
  },
  "memory.system.available": {
    "new_value": "\"5.94 GiB\"",
    "old_value": "\"6.12 GiB\""
  },
  "memory.system.available_bytes": {
    "new_value": "6376570880",
    "old_value": "6571905024"
  },
  "memory.system.capacity": {
    "new_value": "\"22.26%\"",
    "old_value": "\"19.88%\""
  }
}```

Output when no facts differ:
[root@dental-township ~]# puppet facts diff
2021-01-13 13:04:01.984689 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
{}

Output when facts differ:
[root@dental-township ~]# puppet facts diff
2021-01-13 13:10:05.164558 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
{"facterversion":{"new_value":"\"4.0.43\"","old_value":"\"3.14.14\""},"memory.system.available":{"new_value":"\"5.94 GiB\"","old_value":"\"6.12 GiB\""},"memory.system.available_bytes":{"new_value":"6377148416","old_value":"6572556288"},"memory.system.capacity":{"new_value":"\"22.25%\"","old_value":"\"19.87%\""}}

Prettier puppet facts diff with jq:
[root@dental-township ~]# puppet facts diff | jq
2021-01-13 13:09:44.938110 WARN  puppetlabs.facter - locale environment variables were bad; continuing with LANG=C LC_ALL=C
{
  "facterversion": {
    "new_value": "\"4.0.43\"",
    "old_value": "\"3.14.14\""
  },
  "memory.system.available": {
    "new_value": "\"5.94 GiB\"",
    "old_value": "\"6.12 GiB\""
  },
  "memory.system.available_bytes": {
    "new_value": "6376570880",
    "old_value": "6571905024"
  },
  "memory.system.capacity": {
    "new_value": "\"22.26%\"",
    "old_value": "\"19.88%\""
  }
}```

jenkins please test this

jenkins please test this

Thanks for adding this! I noticed a difference when running in CI. It seems facterng reports the following fact that facter 3.x doesn't. Is that expected (since this is 6.x, puppet defaults to puppet facts find, so I have to query in the .values hash)?
[root@heavy-alchemy ~]# puppet facts . --render-as json --facterng | jq .values.hypervisors
{
  "vmware": {
    "version": "ESXi 6.7"
  }
}
[root@heavy-alchemy ~]# puppet facts . --render-as json | jq .values.hypervisors
{
  "vmware": {
    "version": ""
  }
}

Thanks for adding this! I noticed a difference when running in CI. It seems facterng reports the following fact that facter 3.x doesn't. Is that expected (since this is 6.x, puppet defaults to puppet facts find, so I have to query in the .values hash)?
[root@heavy-alchemy ~]# puppet facts . --render-as json --facterng | jq .values.hypervisors
{
  "vmware": {
    "version": "ESXi 6.7"
  }
}
[root@heavy-alchemy ~]# puppet facts . --render-as json | jq .values.hypervisors
{
  "vmware": {
    "version": ""
  }
}


fixed BlobEntry.normalize_dir()

On windows, expand_path may add "C:/" to the output. Added line strips
off this case.
Test suite is not running on windows.

:+1: Thanks! Can you maybe let us know about your experiences running gollum on windows?

Thanks for the utility, I really loved ability for serving wiki pages inside my repositories.
On windows, I have installed jruby 1.7.20 straight ahead. Then installed gollum easily.
I had to debug with RubyMine until I figured out the problem.

Then I could install the fixed java version of the gem.
I start gollum inside the repo by standard cmd.exe. Now links and everything works fine for me.
I could not run the tests though. That is why no test cases added for the fix. :/

@myukselen What was the error when trying to run tests? On my arch box tests won't run by default either because the 'test-unit' gem is missing by default, you can try adding the following to the end of the Gemfile:
gem "test-unit"

I guess that helped. This is the output of the "bundle exec rake test":
Finished in 72.532 seconds.
267 tests, 450 assertions, 16 failures, 39 errors, 0 pendings, 0 omissions, 0 no
tifications
83.1461% passed
3.68 tests/s, 6.20 assertions/s
rake aborted!
SignalException: 1
D:\dev\ruby\jruby-1.7.20\bin\rake:23:in `(root)'
Tasks: TOP => test
(See full trace by running task with --trace)

The test aimed at normalize_dir was already failing but the change committed fixed the test.
$ bundle exec jruby test/test_page.rb -n test_normalize_dir
io/console not supported; tty will not be manipulated
io/console not supported; tty will not be manipulated
Loaded suite test/test_page
Started
.
Finished in 0.09 seconds.
1 tests, 6 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifica
tions
100% passed
11.11 tests/s, 66.67 assertions/s

Thanks @myukselen ! Very interesting. In the 16 failures and 39 errors, are there any patterns discernible?

It seems most of them are file accessing and modification related issues. Differences between Windows and *nix style file handling. Some of them are burried into rjgit, some are surfaced in fileutils.rb
Also I see utf8 handling issues but these can be related to my locale settings.
If you are intereseted and can suggest a method, I will upload 190k test output.

I suposse lots of things like hardcoded slashes instead of using File::SEPARATOR :) (if I'm correct in assuming Windows still uses backslashes?)
To upload the test output, why not use a github gist? Thanks for the assistance!

You are welcome :)
I have uploaded as gist, here is the link:
https://gist.github.com/myukselen/553d630fadf8da19f652#file-gollum-lib-test-output-on-jruby1-7-windows


Audit log

Audit log, to recover information about accesses made to/from the store.
Log all interaction into an audit DB.
Add the /audit end points
Suggestions:
1 Make it a time series like endpoint with /latest and /since endpoints
2 Filter by sensor ID
3 Filter by sensor type
4 Filter by reads and writes.

Relivent information from @yousefamar in another issue:
"Stores have extra (token-managed) endpoints for exposing their logs to other apps. Depending on how we end up handling the whole config-UI thing, stores probably don't need to host any web stuff, but instead the dashboard could get tokens from the arbiter and query those endpoints to show these logs to the user. Would be useful for debug too"

started in eb0b281caf8777bd1121652c474b4e572318d9f7

v 0.1 in #10


Error using fromFile "TypeError: fs.destroy is not a function"

I am trying to convert a csv file to json using convert.fromFile(<file_path>, callback) . When doing this, csvtojson is throwing the following exception (I modified the file paths):
/node_modules/csvtojson/libs/core/Converter.js:326
fs.destroy();
^
TypeError: fs.destroy is not a function
at <full_path>/node_modules/csvtojson/libs/core/Converter.js:326:12
at Converter. (<full_path>/node_modules/csvtojson/libs/core/Converter.js:366:5)
at Converter.g (events.js:260:16)
at emitOne (events.js:82:20)
at Converter.emit (events.js:169:7)
at writeAfterEnd (_stream_writable.js:161:10)
at Converter.Writable.write (_stream_writable.js:204:5)
at ReadStream.ondata (_stream_readable.js:528:20)
at emitOne (events.js:77:13)
at ReadStream.emit (events.js:169:7)
Looking at the code, I am unsure what is trying to be accomplished. I don't see any "destroy" methods on the filestream object in the documentation. Is it supposed to be "delete fs;" instead of "fs.destroy();"?
I am happy to submit a pull request for that but I am unsure of what the intent of the "destroy" function is .
Thanks!

Hi
Thanks for pointing it out.
It was added last version.
The purpose is to clean file stream. But it should be rs.destroy
I will put a fix.
Keyang
On Thursday, 28 January 2016, Ben Gdovicak<EMAIL_ADDRESS>wrote:

I am trying to convert a csv file to json using convertfromFile(,
callback) When doing this, csvtojson is throwing the following exception (I
modified the file paths):
/node_modules/csvtojson/libs/core/Converterjs:326
fsdestroy();
^
TypeError: fsdestroy is not a function
at /node_modules/csvtojson/libs/core/Converterjs:326:12
at Converter (/node_modules/csvtojson/libs/core/Converterjs:366:5)
at Converterg (eventsjs:260:16)
at emitOne (eventsjs:82:20)
at Converteremit (eventsjs:169:7)
at writeAfterEnd (_stream_writablejs:161:10)
at ConverterWritablewrite (_stream_writablejs:204:5)
at ReadStreamondata (_stream_readablejs:528:20)
at emitOne (eventsjs:77:13)
at ReadStreamemit (eventsjs:169:7)
Looking at the code, I am unsure what is trying to be accomplished I don't
see any "destroy" methods on the filestream object in the documentation Is
it supposed to be "delete fs;" instead of "fsdestroy();"?
I am happy to submit a pull request for that but I am unsure of what the
intent of the "destroy" function is
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/Keyang/node-csvtojson/issues/77.


Decoder_lin in Object Classifier

Hi, I want to make sure for "sgdet" task, why is the decoder_lin not used during testing
Does it mean that the object prediction labels from the faserRCNN are used directly in "sgdet"? Then why is  decoder_lin  trained?

Hi, the object classes are inferred by the FasterRCNN directly. I tried to train the custom classifier, hoping it can optimize the object classification. However, the custom classifier doesn't perform as expected. I think the reasons should be the bad quality of region proposals and overlapped object classes (e.g. bottle/cup).
You could remove the custom classifier for sgdet task by yourself :)  This does not affect the result

Thanks for your reply!


Regression (v4.2.1): AnimationTree: animation_started signal is always emitted twice

Tested versions

Reproducible in v4.2.beta4.official [93cdacbb0], v4.2.1.stable.official [b09f793f5]

System information
Godot v4.2.1.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 860M (nvidia; 535.161.07) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)
Issue description
This is a reboot of https://github.com/godotengine/godot/issues/80118 which was supposedly fixed in v4.2, but I experienced the issue in v4.2.1. Even v4.2.beta4 has the bug, so I'm not sure the fix really worked - or it worked for a very specific version only.
Steps to reproduce

Download the MWE from https://github.com/godotengine/godot/issues/80118 (just upgrade it to v4.2)
Run the scene
Press Space / Enter to trigger ui_accept and see the 2x animated started + 1x animation finished message

Minimal reproduction project (MRP)
Same as https://github.com/godotengine/godot/issues/80118
Here is a direct link for convenience: https://github.com/godotengine/godot/files/12229864/anim_tree_signal_bug.zip

I wonder if the double signal emission is related to switching to RESET animation as an intermediate state... One could try to remove the RESET animation, see if it has any impact.

Can't reproduce in master (4.3.dev6)

OK, will build master and try again today.

@hsandt does it still occur?

I confirm I still have the issue in 4.2.2

Was able to confirm in v4.2.1.stable.official [b09f793f5]

But when trying in latest ( v4.3.beta.custom_build [25ff1306d] ) it doesn't seem present:

Unless someone can reproduce this, I recommend this issue be closed


Provider panics when providing a IONOS_API_URL

Description
I had set the environment variable IONOS_API_URL=https://api.ionos.com/cloudapi/v5 in my terminal and the provider immediately panics during terraform plan
Expected behavior
Expected it not to panic.
Environment
Terraform version:
Terraform v0.15.4
on linux_amd64
+ provider registry.terraform.io/ionos-cloud/ionoscloud v5.1.3

Configuration Files
# main.tf
terraform {
  required_version = ">= 0.15.0"
  required_providers {
    ionoscloud = {
      source  = "ionos-cloud/ionoscloud"
      version = "5.1.3"
    }
  }
}

provider "ionoscloud" {
}

data "ionoscloud_datacenter" "example" {
  name = "my-dc"
}

Run commands:
export IONOS_API_URL=https://api.ionos.com/cloudapi/v5
export IONOS_USERNAME=<redacted>
export IONOS_PASSWORD=<redacted>
terraform init
terraform plan

Error and Debug Output
╷
│ Error: Plugin did not respond
│
│   with provider["registry.terraform.io/ionos-cloud/ionoscloud"],
│   on main.tf line 11, in provider "ionoscloud":
│   11: provider "ionoscloud" {
│
│ The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ConfigureProvider call. The plugin logs may contain more details.
╵

Stack trace from the terraform-provider-ionoscloud_v5.1.3 plugin:

panic: runtime error: index out of range [2] with length 2

goroutine 16 [running]:
github.com/ionos-cloud/terraform-provider-ionoscloud/ionoscloud.providerConfigure(0xc000194a10, 0xc00089dae8, 0x6, 0x1, 0x1, 0xebfd78, 0x1508140)
        github.com/ionos-cloud/terraform-provider-ionoscloud/ionoscloud/provider.go:137 +0x752
github.com/ionos-cloud/terraform-provider-ionoscloud/ionoscloud.Provider.func1(0xc000194a10, 0x0, 0xc0006a1640, 0xc000194a10, 0x0)
        github.com/ionos-cloud/terraform-provider-ionoscloud/ionoscloud/provider.go:102 +0xd1
github.com/hashicorp/terraform-plugin-sdk/helper/schema.(*Provider).Configure(0xc000310b80, 0xc00015de90, 0x137b820, 0xc00015de00)
        github.com/hashicorp/terraform-plugin-sdk@v1.16.1/helper/schema/provider.go:275 +0xf6
github.com/hashicorp/terraform-plugin-sdk/internal/helper/plugin.(*GRPCProviderServer).Configure(0xc000794c10, 0x18d0ea0, 0xc00015d140, 0xc000382080, 0xc000794c10, 0xc00015d140, 0xc000652ba0)
        github.com/hashicorp/terraform-plugin-sdk@v1.16.1/internal/helper/plugin/grpc_provider.go:487 +0x2e6
github.com/hashicorp/terraform-plugin-sdk/internal/tfplugin5._Provider_Configure_Handler(0x14f1c40, 0xc000794c10, 0x18d0ea0, 0xc00015d140, 0xc0008b1800, 0x0, 0x18d0ea0, 0xc00015d140, 0xc000040500, 0x3b)
        github.com/hashicorp/terraform-plugin-sdk@v1.16.1/internal/tfplugin5/tfplugin5.pb.go:3251 +0x217
google.golang.org/grpc.(*Server).processUnaryRPC(0xc000453500, 0x18df9a0, 0xc000702c00, 0xc000314200, 0xc00060db60, 0x22c3358, 0x0, 0x0, 0x0)
        google.golang.org/grpc@v1.31.1/server.go:1180 +0x50a
google.golang.org/grpc.(*Server).handleStream(0xc000453500, 0x18df9a0, 0xc000702c00, 0xc000314200, 0x0)
        google.golang.org/grpc@v1.31.1/server.go:1503 +0xcfd
google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc000796190, 0xc000453500, 0x18df9a0, 0xc000702c00, 0xc000314200)
        google.golang.org/grpc@v1.31.1/server.go:843 +0xa1
created by google.golang.org/grpc.(*Server).serveStreams.func1
        google.golang.org/grpc@v1.31.1/server.go:841 +0x204

Error: The terraform-provider-ionoscloud_v5.1.3 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Additional Notes
the fix is probably just changing the indices to 0 and 1 respectively, unless I did something wrong.

@m2hofi94 , have you tried using the endpoint parameter inside the provider resource as described here?
Or why not leaving it out completely since it seems your are using the default endpoint?

No difference using the parameter inside, see https://github.com/ionos-cloud/terraform-provider-ionoscloud/issues/5#issuecomment-856759889

It's still a bug, regardless of whether or not I need to set it or not ;)
I have to set it at some point anyways thanks to annoying proxies on my way out, I just wanted to provide a simple example here

It's more seroius than it seems in the beginning:
One customer is accessing IONOS via a partner which means that he has to use a rebranded URL to access the API.
Thus it must be fixed asap.

@jbuchhammer - working on it, will have the fix released later today.

@m2hofi94 @jbuchhammer - I've just released v5.1.5 - let me know if it fixes the issue for you.

5.1.5 fixes this issue.
Unfortunately, I now get another crash that I had experienced before, see https://github.com/ionos-cloud/terraform-provider-ionoscloud/issues/5
@m2hofi94 Can you reproduce the other crash?

@larsen0815 will take a look


Object.create(null) causes error

When diffing objects that are created using Object.create(null), DeepDiff throws an exception.
require('deep-diff')(Object.create(null), {});
// => TypeError: undefined is not a function
require('deep-diff')({}, Object.create(null));
// => TypeError: undefined is not a function

Version: 0.3.2
npm-shrinkwrap "dependencies"."deep-diff"."resolved": https://registry.npmjs.org/deep-diff/-/deep-diff-0.3.2.tgz
Exception line: https://github.com/flitbit/diff/blob/0.3.2/index.js#L132

Stack:
    at realTypeOf (node_modules/deep-diff/index.js:132:39)
    at deepDiff (node_modules/deep-diff/index.js:155:36)
    at accumulateDiff (node_modules/deep-diff/index.js:202:5)
    ...

Perhaps an additional check for instanceof Object is needed? (This idea needs a more in-depth examination)
({}) instanceof Object // => true
Object.create(null) instanceof Object // => false

Based on recent PRs, I'm of the opinion that this is no longer an issue:
im5k:deep-diff phillip$ node
> let diff = require('./')
undefined
> diff({wilbur: 'funky'}, Object.create(null))
[ DiffDeleted { kind: 'D', path: [ 'wilbur' ], lhs: 'funky' } ]
> diff(Object.create(null), {wilbur: 'funky'})
[ DiffNew { kind: 'N', path: [ 'wilbur' ], rhs: 'funky' } ]


[Work in progress] translate "How to Contribute"

@3imed-jaberi this PR is in "progress", I think that it doesn't make sense to review an unfinished work since it will have more commits for other parts of the page, and also some corrections when re-reading the translation

@3imed-jaberi this PR is in "progress", I think that it doesn't make sense to review an unfinished work since it will have more commits for other parts of the page, and also some corrections when re-reading the translation

I'm sorry .. I just want to give you some help in your first commit ..

Hi @3imed-jaberi, please review this PR after it's been completed. and merge it when approved.


Component standard configurable filter set up

What type of this PR
feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Specified Reivewers:
/assign @sfwn

/approve


chore: add send notification

:tada: This PR is included in version 0.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[SPARK-24953] [SQL] Prune a branch in CaseWhen if previously seen

What changes were proposed in this pull request?
If a condition in a branch is previously seen, this branch can be pruned.
If the outputs of two adjacent branches are the same, two branches can be combined.
How was this patch tested?
Tests added.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1432/
Test PASSed.

Test build #93705 has started for PR 21904 at commit 4ac3d1e.

Test build #93705 has finished for PR 21904 at commit 4ac3d1e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93705/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1499/
Test PASSed.

Test build #93804 has started for PR 21904 at commit 6915647.

Test build #93804 has finished for PR 21904 at commit 6915647.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3069/
Test PASSed.


On sdk 0.9.6 build 20191006 (today) no way to use MX library

Hi,
I just download the last 0.9.6 build 20191006 to replace my old 0.9.6 (from about 1 week old)
<royale-sdk-description>
<name>Apache Royale</name>
<version>0.9.6</version>
<build>20191006</build>

With this build no way to use Mx library , it seem to be unknow.
Here is my code :
<mx:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
			   xmlns:j="library://ns.apache.org/royale/jewel"
			   xmlns:js="library://ns.apache.org/royale/basic"
               xmlns:mx="library://ns.apache.org/royale/mx"
               xmlns:local="*" initialize="ev_creationComplete()">

On editor (vscode) mx:Application is red hightlighted and tooltip show
"This tag can not be resolved in ActionScript class. It will be ignored. (1450)"
If I switch to 0.9.4 (official release) then it working.
When run compiler this error is shown:  "Error: This tag is unexpected. She will be ignored."
Regards

I think in 0.9.6 you will need to add to the compiler options:
+configname=flex

I tried  adding this in asconfig.json
"js-compiler-option": ["+configname=flex"]
But same issue :(
Why it would be a compiler option ? If I set 0.9.4 sdk without changing anything it is working, so it must be a wrong file in 0.9.6 sdk folder ?

It's not a js-compiler option. If you look at the compiler output, you should see +configname (probably right below +royalelib). You probably have +configname=royale instead of +configname=flex.
When compiling a Royale application, you need to to specify what "type" of application you're compiling. The specified config effects the default SWCs loaded. I believe the current list of configs are: js, node, royale, flex, air, and airmobile.
If none of the default configs fit your use case, you can also specify the necessary SWCs explicitly.

Many thanks, as I'm using  ActionScript & MXML language extension for vscode, I found that I must add the following line to asconfig.json
"config": "flex"
I don't understand why I don't need it when selecting 0.9.4 sdk

That's correct. I didn't know if you were using that.
We used to include all the SWCs, but we found that it sometimes caused conflicts. (It also pollutes the options for code completion.) So we now only include the MX and Spark swcs if you specify flex.

To complement:
If you want to use "config": "royale" (instead of flex) and at the same time MXRoyale you can add that swc so VSCode can recognize it.
"library-path": [
       "${royalelib}/js/libs/MXRoyaleJS.swc"
 ],
 "js-library-path": [
       "${royalelib}/js/libs/MXRoyaleJS.swc"
 ]

Additionally: You would be interested in use MXRoyale for non visual things like HTTPService or RemoteObject, and css from MXRoyale could be not desired. In that case you can exclude that CSS to avoid CSS conflicts between MX/Spark and other ui set, specially Jewel in this way:
-compiler.exclude-defaults-css-files=MXRoyale-${royale.framework.version}-js.swc:defaults.css

This is a VERY VERY usefull complement !!! Many thanks

For vscode users here is what to add in as3config.json:
"additionalOptions":
		"-compiler.exclude-defaults-css-files=MXRoyaleJS.swc:defaults.css",

Does intellisense working for you? In Moonshine with Royale MX project doesn't work.

with configuration=royale only if I add this
 "js-library-path": [
			"${royalelib}/js/libs/MXRoyaleJS.swc"
		],

Here is my as3config.json working
{

	"config": "royale",
	"compilerOptions": {
		"targets": [
			"JSRoyale"
        ],
        "theme": "${royalelib}/themes/JewelTheme/src/main/resources/defaults.css",
        "source-map": true,
        "source-path": [
            "src"
		],
		"library-path": [
			"${royalelib}/js/libs/MXRoyaleJS.swc"
		],
		  "js-library-path": [
			"${royalelib}/js/libs/MXRoyaleJS.swc"
		]

	},
	"additionalOptions":
		"-compiler.exclude-defaults-css-files=MXRoyaleJS.swc:defaults.css",
	"files":
	[
		"src/Main.mxml"
	]

}

note that "library-path": [	"${royalelib}/js/libs/MXRoyaleJS.swc"	], seems useless

Yes, I think the other one is useless for now, since the first one is targeting JS directly.
The other could be for SWF (or both) and should target the appropriate SWC, but again, since Jewel is really JS (although is prepared to be SWF some day if we work on it) is of no use for now.
One effort I started some months ago is separate things in MXRoyale in libs, but I couldn't. Hope some day we can do that separation and this kind of combinations could be more easy. Maybe someone with more time can work on that separation, I think it will be very useful to avoid changes in user projects at a later time.

The SDK contains support for several likely configurations.  One is migrating Flex apps to the MXRoyale/SparkRoyale libraries.  Folks are expected to use +configname=flex and thus load flex-config.xml instead of royale-config.xml.  Royale-config.xml is a configuration to support development without the MXRoyale/SparkRoyale libraries.  Some folks do need to mix in MXRoyale into a royale-config.xml setup, but many won't.
The compiler supports library-path, js-library-path, and swf-library-path options.  If you or any other -config.xml file uses -js-library-path then -library-path is ignored for a JS compile and similar for -swf-library-path.

Hi Alex, I must say that right now the cases of pure migration (flex config) and mixed (royale config with MXRoyale just for AMF or HTTP communication uses) are equally used and needed. I think the effort I started to do months ago about break MXRoyale into pieces is very needed. Another thing we could do is to create a "Jewel config" that uses jewel + MXRoyale", but again, I think that doesn't  remove the need to break the monolithic MXRoyale lib


Do not require pathname to start with '/'.

It turns out not all URL pathnames must have a leading /.  For example, "cannot be a base" URLs like data:foo do not have a leading /.  Therefore we do not force URLPattern pathnames to default to / as an empty string pathname is legal.

@kenchris I believe I have fixed the merge conflicts with this PR and it should be ready for review.


During archive process for ios the following exception occurs

Unhandled exception:
Null check operator used on a null value
#0      Context.embedFlutterFrameworks (file:///Users/macbookpro/flutter/packages/flutter_tools/bin/xcode_backend.dart:235:68)
#1      Context.run (file:///Users/macbookpro/flutter/packages/flutter_tools/bin/xcode_backend.dart:59:9)
#2      main (file:///Users/macbookpro/flutter/packages/flutter_tools/bin/xcode_backend.dart:17:5)
#3      _delayEntrypointInvocation. (dart:isolate-patch/isolate_patch.dart:295:33)
#4      _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)
Command PhaseScriptExecution failed with a nonzero exit code
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.1, on macOS 14.1.2 23B92 darwin-x64, locale
en-PK)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.86.2)
[✓] Connected device (4 available)
[✓] Network resources
• No issues found!

I am closing all older issues. If this issue still exists in the latest version, please let me know.


update from gov.fries.fund to snapshot.fries.fund

Hi! What is your PR about?
Change custom domain from from gov.fries.fund to snapshot.fries.fund
Previous PR to add custom domain: https://github.com/snapshot-labs/snapshot-spaces/pull/1860

To update your fork with the remote version of snapshot-spaces you can try these GIT commands then commit your changes again.
git remote add upstream https://github.com/snapshot-labs/snapshot-spaces.git
git fetch upstream
git checkout master
git merge upstream/master


Add Glossary

Description
we should add a glossary to make things simpler

There's a "concepts" page now: https://kuma.io/docs/dev/introduction/concepts/


iOS Abstract Out the UIView type from winit

[x] Tested on all platforms changed
[x] Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
[x] Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior

There are a lot of changes to iOS in this pull request.

The UIApplication setjmp hacks now happen in Window::new. This allows PlatformSpecificWindowBuilderAttributes to customize the specific UIView class.
The biggest breaking change here is that winit no longer sets up a GLKView. Putting responsibility on other libraries like glutin and vulkano-win to specify the exact UIView subclass.
EventsLoop now explicitly checks that it's created on the main thread. AFAICT this was required before, but it was just UB to create it anywhere else.
Only one Window can ever be created.
EventsLoop cannot be polled until a Window has been created - in order for the CFRunLoopRunInMode calls to work.

I have been testing it with glutin. https://github.com/mtak-/glutin/commit/1a3066f8582ee2881890c7e7297419c8badb2fb3
Let me know what needs to be changed/etc.

This looks fantastic, thanks!


ARM64 Improvements

This PR is a series of improvements for sca-fuzzer for the ARM64 architecture.
New ARM64 Spec Generator
The most notable contribution is the addition of a new get_spec_v2.py for ARM64, which uses information which is stored and actively maintained by the official binutils project to create a comprehensive ISA JSON spec for ARM64. This information is retrieved from the binutils binaries themselves, by leveraging their debug symbols (using a GDB python script to parse this information). This approach leverages the already maintained and "computer-friendly" database (compared to the official English ARM64 ISA document parsed by get_spec.py) provided by binutils to generate an ISA. It should also make adding support for new kinds of ARM64 instructions and operands fairly easy.
Additionally, the new get_spec_v2.py script will only generate instructions which match the features of the currently running processor (for instance, CRC/AES/PAC etc). It retrives this information by relying on the functionality provided by gcc -march=native to detect the supported features, and pass them to the assembler. The list of required features to support each instruction is already embedded in the aarch_opcode_table database from binutils mentioned above (as a bitmap), and is compatible with -march=native information.
For information about implicit operands used by each instruction (which is absent from the binutils database), we use information provided by a file from the capstone-project (generated automatically by LLVM).
Finally the output of get_spec_v2.py is compatible with get_spec.py, and the user may choose to use either. Additionally, for convenience, pre-generated ISA JSONs of both scripts are added to the repo, as an alternative to running either generator manually.
ARM64 Spectre V1/V2/V4 POCs
Similarly to the present X86 examples, we provide pre-generated ARM64 test-cases demonstrating:

Spectre V1 (Bounds Check Bypass)
Spectre V2 (Branch Target Injection)
Spectre V4 (Speculative Store Bypass)

These pre-generated test-cases were tested both on ARM64 Raspberry Pi 4 Cortex A72, which is known to be affected by Spectre V1/V2/V4, and ARM64 Raspberry Pi 3V1.2 Cortex A53, which is known to not be affected by any of the mentioned Spectre vulnerabilities. In addition, each test case has a duplicate with a slight variation which changes/comments-out instructions, so that the speculation problem should not appear.
The results of the pre-generated test-cases are summarized in the table below (✅ - violation detected, ❌ - no violation detected).

Test Case
Cortex A72
Cortex A53

Spectre V1 - BCB
✅
❌

Spectre V1 - BCB [no LDR under speculation]
❌
❌

Spectre V2 - BTI
✅
❌

Spectre V2 - BTI [no LDR under speculation]
❌
❌

Spectre V4 - SSBP
✅
❌

Spectre V4 - SSBP [dependent register store/load]
❌
❌

which match the expected results.
ARM64 Fuzzing Improvements
A new config file (test-spectre.yaml) is given as reference for quickly finding a V1-style violation by fuzzing (this config file is also compatible with the pre-generated test cases mentioned above). It is also good starting point for other fuzzing ideas which is compatible with the new JSON specification (the new JSON does categorize instructions, other than simply putting them under general).
ARM64 Tests Improvements and Bug Fixes
The PR fixes several bugs that failed the existing ARM64 tests (runtests.sh arm64), so now all ARM64 tests should pass. There are some general improvements as well (for instance, the removal of the restriction of the fuzzing to only 4 supported instructions).
Finally, all the pre-generated test-cases mentioned above are added to the ARM64 acceptance tests, as well as a test that fuzzing finds a violation under test-spectre.yaml.

@microsoft-github-policy-service agree

Thanks for the PR! And especially for such a detailed description, it's very much appreciated.
I'll need a bit of time to review the code. I'll get back to you once I'm done.

All looks good, it's ready to merge. I really like the idea of using binutils + LLVM to get the instruction specs. Thanks!


Is there similar pattern in Lit that uses React.useContext (Context propagation)?

Assuming Lit components are written in MVU. Is there an alternative to write code so we don't have to pass t he message between Parent/Child?
https://zaid-ajaj.github.io/Feliz/#/Feliz/React/ContextPropagation

Moving to discussions


Some expand operators not working as expected

Using some of the examples from the CQL Specification some of the expand operators seem to be incorrect or unable to resolve
expand { Interval[@2018-01-01, @2018-01-04] } per 2 days
is expanding out to
[Interval[2018-01-01, 2018-01-03), Interval[2018-01-03, 2018-01-05), Interval[2018-01-05, 2018-01-07)]
Note the extra interval at the end
expand { Interval[10.0, 12.5] } per 1
throws exception Could not resolve call to operator Expand with signature (list<interval<System.Decimal>>,System.Integer)
expand { Interval[10, 10] } per 0.1
throws exception Could not resolve call to operator Expand with signature (list<interval<System.Integer>>,System.Decimal)
expand { Interval[1, 10] } per 2
throws exception Could not resolve call to operator Expand with signature (list<interval<System.Integer>>,System.Integer)
expand { Interval[@T10, @T10] } per minute
is returning null rather than { }

Hi @mholck -- which CQL engine are you using?

1.5
These issues were discovered when updating the tests in cql-engine to try and get all CqlIntervalOperators tests working

They also fail in Atom using the language-cql 2.11.1 plugin


Unable to Use Remote Database

With release 2.0.1 fresh install I want to use Advanced features and store my data on a remote server.  The remote server is a managed web host and a root password is not allowed.  All database admin is done using the assigned user or users created by the assigned user.  I have a number of databases running on the remote server and have had the adsb-receiver running as such since inception.  However, during the install I cannot 'skip' the root password question yet the script isn't actually going to create the database or tables, is that right?  The database and tables I wish to use are already created so I expected to be asked for a username and password and database for the connection string.

Added the ability to specify a non root user to create the database and user using the bash script in commit 1e909927d98951a2da0f1ad0403b00c9f49d8de0.


Button Issue in Stepper with IE11

First off I know that IE11 isn't support but I am hoping someone can help or point me in the right direction to fix this.
Bug Report
When using the stepper in IE11 if you click a button (e.g. in the required state step), it momentarily shifts position and then back again. I have managed to fix a few other issues i was having with layouts etc and flex for my project using Covalent but I am stumped with this one. I'm wondering if this has something to do with the ripple effect?
Screenshot

What is the expected behavior?
Button should not move position when clicking it.
What is the motivation / use case for changing the behavior?
UI issue, a user of the web app should not see the button moving position it should be fixed.
Which version of Angular and Material, and which browser and OS does this issue affect?
Angular 4.1.1
Material 2.0.0-beta.3

Does it happen when you click on Cancel too?..
Trying to figure out if its a stepper state change or the actual click that give that effect.

I can confirm it does not happen when the Cancel is clicked

I'm working on a lot of IE11 support issues, so I'll take a look at this later today.

Unfortunately, I can't reproduce this locally. @Blankinfinity you mentioned that you've made some other IE11 fixes. If you have a branch on github, I'll pull it down and take a look. Maybe some of the other fixes are breaking the stepper.

@mcstepp I have made changes to a project for the company i work for so sadly i can't put any of that on github, however that gif was recorded from the main covalent website https://teradata.github.io/covalent/#/components/steps here, so no changes made by myself and that is the behaviour I am seeing.

It doesn't appear to be just related to the stepper component either, I just checked other pages with buttons and I also see it happening on https://teradata.github.io/covalent/#/components/file-upload.

@mcstepp I think this might be a Material problem, if i change from md-raised-button to a flat md-button the issue goes away

Interesting. I still can't reproduce it from the source on IE11.

@mcstepp Just to let you know I am testing on Windows 10s IE11, i have seen subtle differences with behaviour between the version on Windows 7. I have just tried it on a virtual Windows 7 machine and it behaves as expected. God knows what IE11 in Win 10 is doing!

Good point. I was just about to ask you which OS you were using. I was testing on Windows 7 with IE11. I'll grab a Win 10 machine and see if I can apply any fixes. With it being a dependency issue, it may be best to wait until the owner's fix it. In the mean time, I'll check out those links and see if they include other fixes. I saw one for the button in one (the overflow), and also using the flat button as you mentioned earlier. Keeping this on my radar since my application has to support Windows 10 also.

Just in case there are any differences between windows 10 versions I have replicated this on 1607 and 1703.

Very interesting. I'm testing now with Windows 10 version 1607 on IE11 (physical, not virtual) and I still can't reproduce it. I'll try it again on a VM.

Morning, for now until a fix can be found i've disabled ripple effects using MD_RIPPLE_GLOBAL_OPTIONS.
Information on how to use it can be found here https://github.com/angular/material2/blob/master/src/lib/core/ripple/README.md
This has fixed the issue i was seeing but ideally I would love to have the ripple effects working.

@mcstepp I have tried this on my 1607 machine at work today and the issue does not occur (although i could have sworn it did), so looks like it might be a problem in 1703 only

Hey folks I'm testing for IE11 fixes and can't reproduce any of these issues. I'm thinking it must have been an upstream fix in Angular Material for the ripple.
Can anyone else test and confirm?

@kyleledbetter I'll update to the latest version and check it out to see if it is still a problem and get back to you.

Closing this since we couldnt replicate it and its not a covalent specific issue


TechDocs: Support README.md or docs/README.md to be treated as docs/index.md

Feature Suggestion

Add support for treating README.md or docs/README.md file as the index page for TechDocs (docs/index.md).
Possible Implementation

Before we run mkdocs build to generate a site, we already do some preprocessing here. Another step can be added here with the following flow
If `docs/index.md` is available, do nothing
Else duplicate `README.md` or `docs/README.md` as `docs/index.md`
Proceed

Context
A lot of projects have an existing README.md file which serves as an "index page" for those exploring the repository on GitHub/GitLab/etc. To add an index page on TechDocs, they need to create a separate docs/index.md file which is almost a duplicate of README sometimes. While some projects prefer these separate files for different use-cases, some also prefer to not having to duplicate README and index.md.

Risk
Note that usually README.md files are written in "GitHub flavoured markdown" while TechDocs/MkDocs use "Python flavoured markdown". There are only tiny bits of differences, like using * or - for bullet lists, etc.

Note that usually README.md files are written in "GitHub flavoured markdown" while TechDocs/MkDocs use "Python flavoured markdown". There are only tiny bits of differences, like using * or - for bullet lists, etc.

My suggestion for this is to include mdx-truly-sane-lists in techdocs-core. This plugin is a savour for dealing with the very annoying bullet differences in mkdocs vs commonmark / gf markdown.

@andrewthauer just wanted to check but doesn't look like anyone has started on your suggestion. Would this just be something along the lines of adding this code to https://github.com/backstage/mkdocs-techdocs-core/blob/main/src/core.py#L107
config["markdown_extensions"].append("mdx_truly_sane_lists")

And the necessary dependency? here https://github.com/backstage/mkdocs-techdocs-core/blob/main/requirements.txt

Note that usually README.md files are written in "GitHub flavoured markdown" while TechDocs/MkDocs use "Python flavoured markdown". There are only tiny bits of differences, like using * or - for bullet lists, etc.

My suggestion for this is to include mdx-truly-sane-lists in techdocs-core. This plugin is a saviour for dealing with the very annoying bullet differences in mkdocs vs commonmark / gf markdown.

I'm not aware of anyone else having looked at including this plugin. We are currently not using techdocs core directly, but adding  the sane lists plugin would put us one step closer to being able to.

Hey guys i have latest version of techdocs-cli 0.8.8 and latest version of techdocs-core plugin. The fallback works if the README.md file is in the docs directory, but it doesn't if is in the root of the repository

Pinging since it's 2023 now. Could this issue be reopened?
Having the root README of the repository appear in the Techdocs would be very useful, as my org keeps lots of important information on this. Most people use these to view documentation on Github so it is not reasonable to move all of the documentation into the docs folder. Normally, if we don't have a docs folder, then the documentation is stored in the root README of the repository. Fixing this would improve the usability of Software Catelog components and improve searching for important text.

doesn't https://github.com/backstage/backstage/issues/11838 / https://github.com/backstage/backstage/pull/7080/files#diff-2660b7d30eeef02dfcd3db346b8c9baadb90758fdb1b1d5d7bf3f10761501fed address this?

Can confirm, this doesn't work for me either.
With no docs/ folder I get:
ERROR    -  Config value 'docs_dir': The path '/private/var/folders/n3/vl2_0lg52_z6tyhs0sdt1qm40000gp/T/backstage-xLjwS6/docs' isn't an existing directory.
mkdocs.yml
site_name: 'new-new-service'
site_description: 'Main documentation for new-new-service'
repo_url: https://gitlab.com/....../new-new-service
edit_uri: edit/main

plugins:
  - techdocs-core

nav:
  - Overview:
    - What is new-new-service?: 'README.md'

The README.md is in the root directory as expected, but get no docs generated. If I was to docs/index.md I can see that can generated in the tech docs, but when trying to navigate to What is new-new-service? I get a 404.

Any update on this issue? Can README file be treated as index.md?

We ended up using a UrlPreparer for the job:
export class MyUrlPreparer implements PreparerBase {
    private originalPreparer: UrlPreparer;
    private readonly logger: Logger;

    private constructor(preparer: UrlPreparer, logger: Logger) {
        this.originalPreparer = preparer;
        this.logger = logger;
    }

    static fromConfig(config: PreparerConfig): MyUrlPreparer {
        return new MyUrlPreparer(UrlPreparer.fromConfig(config), config.logger);
    }

    prepare(entity: Entity, options?: PreparerOptions | undefined): Promise<PreparerResponse> {
        return this.originalPreparer.prepare(entity, options).then((response) => {
            const docsPath = resolve(response.preparedDir, 'docs');
            this.logger.info("Running preparer")
            if (!fs.existsSync(docsPath)) {
                fs.mkdirSync(docsPath);
                options?.logger?.info(`Created missing docs directory ${docsPath}`)
                fs.copyFileSync(`${response.preparedDir}/README.md`, `${docsPath}/index.md`)
                options?.logger?.info(`Copied readme to ${docsPath}/index.md`)

                const mkdocs = {
                    "site_name": `${entity.metadata.name} README`,
                    "site_description": entity.metadata.description,
                    "docs_dir": "docs",
                    "repo_url": "",
                    "edit_url": ""
                }
                fs.writeFileSync(`${response.preparedDir}/mkdocs.yaml`, yaml.dump(mkdocs));
                options?.logger?.info(`Wrote standard ${docsPath}/mkdocs.yaml`)
            } else {
                this.logger.info("Docs folder exists, not doing anything.")
            }

            return response;
        })
    }
}

hooked in backend/src/plugins/techdocs.ts:
export default async function createPlugin(
  env: PluginEnvironment,
): Promise<Router> {
  // Preparers are responsible for fetching source files for documentation.
  const preparers = await Preparers.fromConfig(env.config, {
    logger: env.logger,
    reader: env.reader,
  });
  preparers.register('url', MyUrlPreparer.fromConfig({
    logger: env.logger,
    reader: env.reader,
  }))
...

As a simple workaround, I created a symlink inside the /docs directory:
ln -s ../README.md ./README.md

Looks as though this may have already been implemented, although I'm struggling to find documentation:
https://github.com/backstage/backstage/pull/7080


Replace "null" to empty string

On some pages the meta attributes like og:image, author or date have "null" (string) value so this should be replaced with null or empty string.

Would it be possible to add a test case that covers this?

@ageitgey can you merge this? or there is any contraindications?

done

Can you rebuild scripts and update version in git/npm yet? Thanks


Reward amount is wrongly displayed for multiple youtube channels

Bug
When listing available rewards the response contains the following
redacted (see slack)
However the displayed amount is the same for both: https://scrn.storni.info/2019-09-26_20-17-14-016761057.png
To Reproduce
have 2 unclaimed youtube channels to redeem
Expected behavior
Both channels should have their own reward value
Screenshots
the description contains a hacked amount that should be what's displayed on the button.
https://scrn.storni.info/2019-09-26_20-23-32-711972767.png
System Configuration
Master branch, on linux

Closing for https://github.com/lbryio/lbry-desktop/issues/3403


Incorrect display of Cassandra time data type

Config:
DBeaver EE 3.7.5
Cassandra 3.9.0 (official release)
Windows 7 x64
Issue:
SELECT operation does not return (or display) the time data type column correctly, instead it displays something like "3054-10-09 00:53:20"
Datastatx DevCenter shows it correctly as "09:30:32.000000000"

What is exact column data type?
Can you post a DDL?

Create
CREATE TABLE IF NOT exists tidata.test1 (
idx int,
tm time,
PRIMARY KEY (idx));

Insert
INSERT INTO tidata.test1 (idx, tm) VALUES (7,'09:30:32');

Select
SELECT * FROM tidata.test1;

Result

Yes, it is a bug, DBeaver incorrectly handles TIME values (as TIMESTAMP).
Will be fixed in the next version, thanks for report.


False Positive: mjs static files are counted as dynamic assets

mjs isn't counted as an static file and is causing false positives with applications that make heavy use of mjs files (Such as Nextcloud). I don't know where static resources are defined so I'm opening an issue here.

static is defined within the enricher itself via this line:
https://github.com/crowdsecurity/hub/blob/10fb69b2f29c6b96af8b95aaa89ca89fecebae57/parsers/s02-enrich/crowdsecurity/http-logs.yaml#L33

@LaurenceJJones aah that's where it is, I thought it was somewhere in the individual web server parsers
PR incoming


Set ansible_user_dir var from min facts when undefined

On using 01-bootstrap.yml playbook seperatly, user does not
pass ansible_user_dir. It fails the playbook with undefined var
on remote host.
ansible_user_dir var is used in almost all the var.
In order to fix that, let's gather mininum facts on the host so
these vars gets discovered and such issues gets avoided.
This patch also drops ansible_user_dir vars from scenario files.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running

It seems weird to set ansible_ prefixed variables, it seems it could be sometimes missing - but in special cases, not with inventory and fact gathering imo.
Especially it seems this might be some quirk in ansible, as after fact_gathering this is indeed known fact - even for localhost!
Without inventory (so just localhost builtin), with play like:
- hosts: localhost
  gather_facts: yes
  tasks:
    #- debug:
    #    var: hostvars['localhost']
    - debug:
        msg: "hello {{ inventory_hostname }} - {{ ansible_user_home | default('__null__') }}"
    - debug:
        msg: "{{ hostvars[inventory_hostname]['ansible_user_dir'] }}"

it results in:
ok: [localhost] => {
    "msg": "hello localhost - __null__"
}

TASK [debug] ******************************************************************************************************************************************************************************************************************************
ok: [localhost] => {
    "msg": "/var/home/psedlak"
}```

showing that direct variable 'ansible_user_home' is not visible, but it is visible under host specific variables/facts!

So we may need this as workaround i guess?

tiny "nit", but it should really do the trick.

I hit this issue. When I was trying to call the bootstrap playbook directly via zuul.

MAYBE we should consider adding this to all of the playbooks, in order to avoid weird situation?

In other playbooks, we are calling multiple plays and hooks. Not sure it is a good idea.

Still - with the gather_facts: true set on #L3 I don't really understand why we don't get that parameter :/.
No idea.

/lgtm

/hold

That patch would be useless actually:
with gather_facts: true we indeed get the needed ansible_user_dir set. Tested, and it indeed works. It also work if we set it to false and run the ansible.builtin.setup with gather_subset: ['!all', 'min'] without any issue.
After some more digging, it seems the 01-bootstrap.yml is called from a playbook, itself called as a plain ansible-playbook command:
https://github.com/openstack-k8s-operators/ci-framework/blob/main/ci/playbooks/content_provider/content_provider.yml#L2-L3
The exposed error isn't really precise as to WHERE the parameter is missing:
2023-06-12 04:22:25.900687 | controller | ERROR! {{ ansible_user_dir }}/src/github.com/openstack-k8s-operators/ci-framework: 'ansible_user_dir' is undefined. 'ansible_user_dir' is undefined. {{ ansible_user_dir }}/src/github.com/openstack-k8s-operators/ci-framework: 'ansible_user_dir' is undefined. 'ansible_user_dir' is undefined

What we can understand here, it's missing from that call.
Maybe we should investigate a bit more that specific part. It may also be interesting to check out why this is working without issue... While we're consuming the main deploy-edpm.yml playbook, we don't set anything weird in there:
- name: Bootstrap step
  ansible.builtin.import_playbook: ci_framework/playbooks/01-bootstrap.yml

- name: Import infra entrypoint playbook
  ansible.builtin.import_playbook: ci_framework/playbooks/02-infra.yml
[...]

Namely: same code is being consumed. Now, it would be interesting to know a bit more about the specific task that failed. In order to do so, we may want to ensure we're passing the same ansible configuration file consumed by the main run. This can be done like that:
https://github.com/openstack-k8s-operators/ci-framework/blob/main/ci_framework/roles/run_hook/tasks/playbook.yml#L50
That should allow to get the run log in the same ansible.log file, and therefore get all of the needed data.
Care to propose a patch with that, @raukadah, and add the depends-on on the nova job you're trying to get?

/lgtm cancel

It is no longer needed.


Dnyandeo : WorkFlow : 1 Week

Learning Objectives
1. Local Development Without Git
Practice the foundational workflows of software development by learning to write
Markdown locally on your own computer using Visual Studio Code (VSCode), the
Command Line Interface (CLI), and NPM scripts to automate your code's quality
(formatting, linting and spell checking).

[x] Folder Structures: You can explain how files and folders are stored in
your computer and can find, open or create files in your computer without
using the Command Line Interface.
Command Line Interface (CLI): In a Unix shell you can ...
[x] open a new terminal window
[x] navigate up and down directories using cd
[x] list the contents of a directory using ls
[x] view the contents of a file using cat
[x] create new files using touch
[x] create new folders using mkdir
[x] Markdown: You can write a document in Markdown with no syntax mistakes
that renders into a well-formatted document.
VSCode: You can complete these workflows in VScode, and can use keyboard
shortcuts to complete them all:
[x] Opening a repository in a new window
[x] Opening the VSCode terminal
[x] Adding a new file
[x] Adding a new folder
[x] Deleting a file
[x] Deleting a folder
[x] Previewing a Markdown File
[x] Formatting a Markdown document
[x] READMEs: You can write a README file that describes the project you
are working on, why it's helpful, and how someone can use it.
NPM: You can use NPM commands to verify your code's quality, this includes
...
[x] using npm install to install a project's dependencies
[x] reading a package.json file to find which scripts are available for the
project
[x] use npm run <script> to execute an npm script
Formatting Code: You can use Prettier to make sure all the code in your
project is well-formatted:
[x] You can use the Prettier VSCode extension to format a document while you
are writing it
[x] You can use npm run format to format all of the documents in your
project
[x] You can use npm run format:check to make sure all files are
well-formatted
Linting Folder and File Names: You can ...
[x] use npm run lint:ls to check all folder and file names in your project
[x] you can fix all linting mistakes reported by npm run lint:ls
Linting Code: You can ...
[x] use npm run lint:md to check all Markdown files in your folder for
linting mistakes
[x] you can fix all linting mistakes reported by npm run lint:md
Spell Check: You can ...
[x] use the Code Spell Checker VSCode extension to correct spelling mistakes
in your Markdown documents while you are writing
[x] use npm run spell-check to check the spelling in all the files of your
project
[x] update .cspell.json to add words that should be allowed in your project
File and Folder Naming Conventions: You can ...
[x] identify and follow the naming conventions for the project you are working
on.
[x] use npm run lint:ls to check that all files and folders follow the
project's naming conventions.
[x] you can correct any file and folder names to make them match the project
conventions.
[x] File Extensions: You can identify all of the languages covered at HYF
and give the correct file extension. You don't need to know the languages,
just recognize them.
[x] Touch Typing: You can write a Markdown file without looking at your
keyboard to find any letters, numbers or special characters. (slowly is
ok!)

2. Local Development With Git
Practice using Git to save and organize your development process. You will learn
how you can use Git to go back to previous versions of your project, and to work
on different changes in parallel.

Git: Using the CLI you can ...
[x] Initialize a new git repository with git init
[x] stage changes using git add <path>
[x] check what is staged with git status
[x] commit changes using git commit -m <message>
[x] display your repository's git history using git log
[x] create a new branch using git branch <branch-name>
[x] check out a branch using git checkout <branch-name>
[x] create a new branch and check it out using git checkout -b <branch-name>
[x] merge changes from one branch to another using git merge <branch-name>
[x] return to a previous version of your project with git log and
git checkout <commit-hash>
[x] stash and retrieve uncommitted changes with git stash and git pop
.gitignore: You can use a .gitignore file to describe which files you
don't want included in your git history.
VSCode: You can ...
[x] use the Git Graph extension to to visualize your repo's commit history
[x] use the Git Lens extension to investigate your repository's commit
history
[x] explain how the file tree in VSCode can show you which files have
uncommitted changes
[x] Atomic Commits: You can save your development progress using small
commits with clear and helpful message.
[x] Feature Branches: You can organize your development process using
branches. You can create a new branch for each part of your project and
merge those changes to main when they are finished.

3. Local/Remote Development
Learn how you can connect your local Git repositories with a GitHub repository
to add more structure to your development process and to share your projects.

Licenses: You can ...
[x] explain why it's important to include a license for your code on GitHub
[x] choose a license for your projects that matches how you want others to use
your code
[x] GitHub SSH Key: You can connect your computer to your GitHub account
using an SSH key, clone using the SSH link, and push/pull using your SSH
connection.
GitHub Repositories: You can ...
[x] create new repository on GitHub
[x] write a description for your repository
[x] turn on GitHub Pages
[x] configure your repository to block pushing to main
[x] configure your repository to block merging to main until Continuous
Integration (CI) checks have passed
Git Remote/Local Connection: You can ...
[x] clone a remote repository to your computer
[x] initialize a new repository locally and connect it to an empty remote
repository
[x] push and pull changes between remote & local branches
[x] Pull Requests: You can create a pull request between two branches in
your repository and merge changes without causing any conflicts.
[x] PR templates: You can use a PR template to add a checklist to all of
your PRs so you are sure the code is great before merging to main.
[x] Continuous Integration: You can use GitHub Actions to check your
code's quality before merging a pull request to the main branch.
[x] Local/Remote Branching Workflow: You can use a branching workflow that
keeps mistakes away from the main branch and prevents conflicts from
happening in GitHub. For each contribution to the project you can ...

Check out a new local branch and write your code
Check out main on your local machine
Pull changes from remote main to local main
Merge changes locally from main to your new branch

Fix any conflicts on your new branch before pushing!

Format and lint your code
Push your new local branch to your remote repository
Open a Pull Request from the new branch to main

Go through the PR's checklist to make sure everything is correct
Make sure all CI checks pass!

Merge your new remote branch to main

You can delete the branch after it's merged if you want to

4. Remote Collaboration
Learn how to collaborate with a group on a single project hosted in a GitHub
repository. Practice using GitHub's project management features to organize your
group's tasks and to double-check your project's code quality.

[x] Contributor Guidelines: Your group can define contributor guidelines
that describes how everyone can add their work to the project.
[x] Code of Conduct: Your group can write a code of conduct for your
project that describes how everyone should communicate and what behavior
is considered unproductive.
[x] Repository Contributors: You can add group members as collaborators in
a repository.
[x] Issue Templates: Your group can use issue templates to make sure all
issues are complete and relevant to the project. in your repository and
merge changes without causing any conflicts.
[x] Code Review: You can use the PR Template and CI checks to review
another group member's code before merging it to main.
GitHub Project Management: You can ...
[x] use issues to define tasks in a group project. Each issue should have a
helpful title, complete description, and helpful labels.
[x] use a Project Board to organize a project's issues
[x] claim issues and track your progress with the project board
[x] link a PR to your claimed issue
[x] assign someone to review your PR
[x] use GitHub code review features to discuss your code with your reviewer
[x] Fixing Merge Conflicts: You can fix merge conflicts by selecting which
change to keep, or deciding how to combine them. If a conflict occurs in a
GitHub PR you can pull both branches and fixh the conflict locally.

5. Open Source Development
Explore the wider world of Open Source software by learning how communities of
independent developers write and maintain the code we all rely on.

[x] Finding Issues: You can read through an open source project's issues
and determine if there is one you can help with.
[x] Commenting in Issues: You can productively join the conversation in an
open source projects' issues.
[x] Opening Issues: You can open a helpful issue in an open source
repository, following their contributor guidelines and code of conduct.
[x] Contributing: You can create a fork of an open source project and open
a PR that contributes something helpful and follows the Contributor
Guidelines and Code of Conduct.

week 1
Everything is going well.


List of editor integration guides

In the documentation section, let's have an editor integration section.
We can list the common ways to get editor integration, and consult the relevant people for the proper way to do it for a given environment.

Emacs
Spacemacs
Vim
Sublime
Atom
etc

Going to go ahead and put this stake in the ground: don't recommend ghc-mod. It's extremely fragile, wasted a lot of time for beginners, and most would be fine with just the errors from flycheck + Stack (for Emacs anyway. There's an equiv for Vim) and a REPL for the rest.

Going to go ahead and put this stake in the ground: don't recommend ghc-mod. It's extremely fragile, wasted a lot of time for beginners

Sad, but true.

Agreed. I made flycheck-stack because I couldn't get ghc-mod to work.
On 2 May 2016 20:07, "Chris Allen"<EMAIL_ADDRESS>wrote:

Going to go ahead and put this stake in the ground: don't recommend
ghc-mod. It's extremely fragile, wasted a lot of time for beginners, and
most would be fine with just the errors from flycheck + Stack (for Emacs
anyway. There's an equiv for Vim) and a REPL for the rest.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/haskell-lang/haskell-lang/issues/21#issuecomment-216313297

for atom, ghc-mod seems to work reasonably and it's pretty much the only way to have advanced IDE features (?);

@vincenthz ghc-mod works great but is really slow for large projects (much slower than ghci-based tools) Sadly, since ghci, intero, ghcid, ghci-ng , etc don't implement a proper "ide-server" (with proper api), it's a bit harder to develop ide plugins that use them because you have to manage the low level process interraction yourself.

for atom, hdevtools is also easy to setup, but only gives errors, and not much more. the type tooltip  provided by its companion plugin is not great.
for sublime text, sublimehaskell also works decently, but is quite slow as it is based on ghc-mod.
If you only want error messages + notifications in the gutter, you can also use ghcid -o errors-and-warnings.txt along a custom script to pares and print errors and warnings in the errors-and-warnings.txt dump file. works to some extent, but not great

My only hesitation here is that the IDE tooling story is fairly immature and I don't want to give new people the impression things "just work" here — they do not outside of perhaps ghcid and intero. I'm a bad test case for Intero as my work project forces me to restart it manually several times an hour. (I modify dependencies a lot) I think it's quite good for ordinary users, albeit only available for Emacs at the moment.
Looks like there's been some push to make intero work on neovim: https://www.reddit.com/r/haskell/comments/4n27r2/intero_for_neovim/

I also restart intero fairly often for adding dependencies. I'll add some automation around that eventually.

@chrisdone in my case, it's modifying deps rather than adding, but even covering new deps would be lovely. Most folks are more likely to be affected by addition rather than modification as well. Automation for either/or would be great :D


Added other math functions (except random)

and cleaned up argument handling (now abs(2, 3) is an error).  This also includes some minor bug fixes such as floor and ceil returning a Number instead of an Integer.
I'm somewhat concerned about how max and min are handled.  It feels very complicated for what is essentially a fold.  I might be missing some way of properly handling this sort of thing.  I couldn't make the ? operator work like I was expecting.
Tests to come soon (TM)

I don't think there are any Lua stdlib functions that check for extra arguments.
> math.acos(0.0, "foo")
1.5707963267949

Regarding max / min, you can either not use a fold at all, or you can use Iterator::try_fold.

Also behavior of min / max with no arguments:
> math.min()
stdin:1: bad argument #1 to 'min' (value expected)

Just curious, why rand_xoshiro specifically?

Okay, something I'm going to be working on soon is changing both the argument and return types to callbacks to avoid creating intermediate buffers.  There will be a type that callbacks can't create that serves as both the argument and return vector, with operations to move args / returns around in the vector, and callbacks will be required to return it.
This is going to be an involved refactor or every callback, would you like me to make this change before or after merging this PR?

rand_xoshiro was chosen because it is very fast and has decent rng properties.  It is not unique by any stretch of the imagination, it's just the built in random function I thought was best when I glanced once briefly over the built-in engines in the rand crate documentation.

This is going to be an involved refactor or every callback, would you like me to make this change before or after merging this PR?

Either way is fine, I'm OK with changing the callbacks to a new convention myself, or you can at your option.  The only thing that's keeping this PR from being complete is tests for functions alphabetically beyond frexp.  And if I'm keeping you from working on something that needs to get done, just do it, and I'll catch up.  This code isn't the most complicated in the world. :)

Hopefully, this ought to be the rest of the needed tests.  There are a few edge cases that I'm aware of where behavior of the functions does not line up 1 to 1 with lua, such as the min function does not handle nan cases in quite the same way.  And some functions will accept strings with numbers in them where lua just barfs on it (such as the max and min functions), I'm not sure if you want to adhere to the behavior of PUC Lua on this because the documentation and specification do not say that this should be either allowed or disallowed.

I think it's important that all tests pass both luster and PUC-Rio Lua, so if there are any tests that aren't like that we shouldn't codify the current mismatched behavior of luster.
It's fine if it's not perfectly compatible right now in the interests of simple implementations, because there are bigger compatibility fish to fry first, but if you want to leave commented out tests that don't match, that would be excellent.

All test cases work in both luster and PUC-Rio Lua.  I'll add some tests and comment them out where the behavior is mismatched.

I lied about refactoring arguments / returns, I can't come up with a sane API atm and I'm stalled working on it.
I'm going to go ahead and merge this PR.


Subhalo values not being populated in mock when using SubhaloPhaseSpace

When making and populating a model_instance, then looking at model_instance.mock.galaxy_table, all of the halo values for the satellite galaxies are that of their host halos. I'm using SubhaloPhaseSpace, so the satellite galaxies themselves are getting their positions and velocities from their subhalo, but the values in the table (halo_x, halo_y, etc.) refer to their host halos (other than halo_id, which properly references the subhalo; This is how I've been able to get the proper information so far).
This also means when I try to align with the halo, it aligns to the host halo. To get around this, I've made a new alignment model called SubhaloAlignment that overwrites the halo columns with the correct subhalo information, but I thought this might be something we want to fix farther upstream.
As such, I do have some code to replace these host halo values with the subhalo values from the halocat, if that would help resolve this issue.
Thanks!

Adding on some more information. I found that this also affects features like RadialSatelliteAlignmentStrength. In RadialSatelliteAlignmentStrength, the alignment strength is calculated using the distance between the satellite galaxy and the host halo.
If I use the fix I mentioned in the previous comment (Overwriting the satellite galaxy halo information with their subhalos using SubhaloAlignment model) this overwrites the halo_x, halo_y, and halo_z with the values of the subhalo the satellite galaxy resides in rather than the values for the host halo. This causes issues when using RadialSatelliteAlignmentStrength as all the distances are now calculated to be zero.
So I think either we should fix this upstream and fix the RadialSatelliteAlignmentStrength model to account for that (I also have some notes on the form of the equation used there I think we should change), or if keeping the host halo information in the galaxy_table is preferable, we need to make sure the models intended to align with subhalos have the halocat information and properly reference that.

Hmm, ok, thanks for following up. We should probably find a time to have some discussion of this then.


added compiled binaries for the cipher

While I appreciate the PR, I'm going to opt to let any users compile their own binaries for this tool for security reasons. Thanks 🚀


Can you add an experiment result of a single card on librispeech100h?

Hi, I used Wenet to run the conformer-transformer experiment in librispeech 100h with the following settings with one RTX TITAN 24G . The results are as follows(70 epoches):
"dev_clean_attention_rescoring: English -> 14.17 % N=54402 C=47534 S=6046 D=822 I=843
dev_other_attention_rescoring:English -> 30.81 % N=50948 C=36937 S=11930 D=2081 I=1686
test_clean_attention_rescoring:English -> 14.21 % N=52576 C=45963 S=5806 D=807 I=857
dev_other_attention_rescoring:English -> 35.11 % N=52343 C=38074 S=11132 D=3137 I=4107"
This result is far lower than the model with the same parameters I ran on Espnet before on the librispeech 100h dataset.
(https://github.com/espnet/espnet/tree/master/egs2/librispeech_100/asr1)
Can you add an experiment result of a single card on librispeech100h?  If you have time to add this experiment, thank you very much.
network architecture
encoder related
encoder: conformer
encoder_conf:
output_size: 256    # dimension of attention
attention_heads: 4
linear_units: 2048  # the number of units of position-wise feed forward
num_blocks: 12      # the number of encoder blocks
dropout_rate: 0.1
positional_dropout_rate: 0.1
attention_dropout_rate: 0.0
input_layer: conv2d # encoder input type, you can chose conv2d, conv2d6 and conv2d8
normalize_before: true
cnn_module_kernel: 15
use_cnn_module: True
activation_type: 'swish'
pos_enc_layer_type: 'rel_pos'
selfattention_layer_type: 'rel_selfattn'
decoder related
decoder: transformer
decoder_conf:
attention_heads: 4
linear_units: 2048
num_blocks: 6
dropout_rate: 0.1
positional_dropout_rate: 0.1
self_attention_dropout_rate: 0.0
src_attention_dropout_rate: 0.0
hybrid CTC/attention
model_conf:
ctc_weight: 0.3
lsm_weight: 0.1     # label smoothing option
length_normalized_loss: false
dataset related
dataset_conf:
filter_conf:
max_length: 2000
min_length: 50
token_max_length: 400
token_min_length: 1
min_output_input_ratio: 0.0005
max_output_input_ratio: 0.1
resample_conf:
resample_rate: 16000
speed_perturb: true
fbank_conf:
num_mel_bins: 80
frame_shift: 10
frame_length: 25
dither: 0.0
spec_aug: true
spec_aug_conf:
num_t_mask: 2
num_f_mask: 2
max_t: 50
max_f: 10
shuffle: true
shuffle_conf:
shuffle_size: 1500
sort: true
sort_conf:
sort_size: 500  # sort_size should be less than shuffle_size
batch_conf:
batch_type: 'static' # static or dynamic
batch_size: 12
grad_clip: 5
accum_grad: 1
max_epoch: 70
log_interval: 100
optim: adam
optim_conf:
lr: 0.004
scheduler: warmuplr     # pytorch v1.1.0+ required
scheduler_conf:
warmup_steps: 25000

Sorry, we do not have the badwidth to do it recently.

Sorry, we do not have the badwidth to do it recently.

Ok, thanks.

I think for accum-grad, if you only have one gpu you can multiply it by 8 (gpus) compared to the value in original config.

you can try to remove positional emb


[SPARK-48879][SQL] Expand the charset list with Chinese Standard Charsets

What changes were proposed in this pull request?
This PR expands the charset list with Chinese Standard Charsets
https://en.wikipedia.org/wiki/GB_2312
https://en.wikipedia.org/wiki/GBK_(character_encoding)
https://en.wikipedia.org/wiki/GB_18030
https://en.wikipedia.org/wiki/Big5
Why are the changes needed?
Improve the charset list for real-world workloads
Does this PR introduce any user-facing change?
Yes, more charsets are valid
Was this patch authored or co-authored using generative AI tooling?
no

cc @cloud-fan @dongjoon-hyun thanks

If we plan to start a discussion thread in the development, I'd like to expand the scope of this pull request first to make it not only about adding Chinese Charsets but also other standard charsets. Otherwise, it potentially introduces some unnecessary political factors, which is not the original intention of this PR, of course.

You don't need to touch this PR, @yaooqinn .
What we need is a discussion to build a consensus about Apache Spark's direction.

Thank you @dongjoon-hyun


support local paths to input datasets and additional code

Currently the source attribute on Inputdataset only supports URLs to remotely hosted files, while AdditionalCode is described by a source_repo. We should support source strings that are local paths.

URLs to remotely hosted files

Github URLs? Or S3 urls? It's relevant for the idea of using cloudpathlib everywhere (see https://github.com/CWorthy-ocean/C-Star/issues/27)

Not strictly either, anything pooch can fetch - #27 definitely seems relevant here though


caps matter in insert into index command

CREATE INDEX Activities_en FULLTEXT ENGINE LUCENE String,String,String METADATA {"analyzer":"org.apache.lucene.analysis.en.EnglishAnalyzer"}
INSERT INTO INDEX:Activities_en (key,rid) VALUES("a","b","c"],#9:0)
this does not run and produces error
Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error
on parsing command at position #0: Encountered " ":" ": "" at line 1, column 18.
Was expecting one of:
 ...
 ...
 ...
 ...
"(" ...
"cluster" ...
"(" ...
while
INSERT INTO index:Activities_en (key,rid) VALUES("a","b","c"],#9:0)
this runs OK. The documentation also has it with caps.
confirmed on 2.1-rc4

@arisAlexis
Why do you want to use manual index?

hi,
https://groups.google.com/forum/#!topic/orient-database/murrnfw_aZQ
basically I want an index for each supported language. Otherwise I could use a different analyzer each time I want to index something (that's also manual) and stuff everything in the same index.

Lucene manual has not really been tested. Usually goes along with the class
this works
INSERT INTO INDEX:Activities_en (key,rid) VALUES(["a","b","c"],#9:0)

it misses a [
but the retrivial has some problem
I will try to make it support with manual index

I haven't noticed the missing bracket but the bug is still there with the caps.
If there is a bug posting for lucene manual index please post it here so I can follow it thanks.
Would be great if someone could choose the analyzer during indexing.
orientdb {db=exchange}> INSERT INTO INDEX:Activities_en (key,rid) VALUES(["a","b
","c"],#9:0)
Error: com.orientechnologies.orient.core.sql.OCommandSQLParsingException: Error
on parsing command at position #0: Encountered " ":" ": "" at line 1, column 18.
Was expecting one of:
 ...
 ...
 ...
 ...
"(" ...
"cluster" ...
"(" ...
orientdb {db=exchange}> INSERT INTO index:Activities_en (key,rid) VALUES(["a","b
","c"],#9:0)
Inserted record '{rid:#9:0,key:[3]}' in 0.069000 sec(s).
orientdb {db=exchange}>

It is not really a bug, it is a missing feature. Lucene indexes are based on class.
there is an open issue about that
https://github.com/orientechnologies/orientdb-lucene/issues/27
You can follow the development there


console error  when use react quill

console error  when use react quill
#Warning: Use the defaultValue or value props on  instead of setting selected on .
for  react 15.1.0  es6

Please look at the current issues before opening a new one next time. This was already brought up in #87. Thanks!

Fixed in #87


Error in unpacking archive of SROIE dataset

Bug description
When trying to use the SROIE dataset using the API provided, it start downloading the following link: https://doctr-static.mindee.com/models?id=v0.1.1/sroie2019_train_task1.zip&src=0 and then saved the downloaded file in format .zip&src=0 which not recognized by shutil.unpack_archive.
Note:  I already with other datasets such as CORD and FUNSD, with same API and it work successfully.
Code snippet to reproduce the bug
from doctr.datasets import SROIE
train_set = SROIE(train=True, download=True)
img, target = train_set[0]

Error traceback
ReadError                                 Traceback (most recent call last)
[<ipython-input-5-ec50ee844285>](https://localhost:8080/#) in <cell line: 2>()
      1 from doctr.datasets import SROIE
----> 2 train_set = SROIE(train=True, download=True)
      3 img, target = train_set[0]

2 frames
[/usr/local/lib/python3.9/dist-packages/doctr/datasets/sroie.py](https://localhost:8080/#) in __init__(self, train, use_polygons, recognition_task, **kwargs)
     54
     55         url, sha256 = self.TRAIN if train else self.TEST
---> 56         super().__init__(
     57             url,
     58             None,

[/usr/local/lib/python3.9/dist-packages/doctr/datasets/datasets/base.py](https://localhost:8080/#) in __init__(self, url, file_name, file_hash, extract_archive, download, overwrite, cache_dir, cache_subdir, **kwargs)
    115             dataset_path = archive_path.parent.joinpath(archive_path.stem)
    116             if not dataset_path.is_dir() or overwrite:
--> 117                 shutil.unpack_archive(archive_path, dataset_path)
    118
    119         super().__init__(dataset_path if extract_archive else archive_path, **kwargs)

[/usr/lib/python3.9/shutil.py](https://localhost:8080/#) in unpack_archive(filename, extract_dir, format)
   1265         format = _find_unpack_format(filename)
   1266         if format is None:
-> 1267             raise ReadError("Unknown archive format '{0}'".format(filename))
   1268
   1269         func = _UNPACK_FORMATS[format][1]

ReadError: Unknown archive format '/root/.cache/doctr/datasets/sroie2019_train_task1.zip&src=0'

Environment
Note that the working Environment is Google Colab
Deep Learning backend
Pytorch

Hi @HamzaGbada :wave:,
thanks for reporting this.
I see the issue which should be easy to solve by changing the following code in https://github.com/mindee/doctr/blob/main/doctr/datasets/sroie.py to:
    TRAIN = (
        "https://doctr-static.mindee.com/models?id=v0.1.1/sroie2019_train_task1.zip&src=0",
        "d4fa9e60abb03500d83299c845b9c87fd9c9430d1aeac96b83c5d0bb0ab27f6f",
        "sroie2019_train_task1.zip",
    )
    TEST = (
        "https://doctr-static.mindee.com/models?id=v0.1.1/sroie2019_test.zip&src=0",
        "41b3c746a20226fddc80d86d4b2a903d43b5be4f521dd1bbe759dbf8844745e2",
        "sroie2019_test.zip",
    )

    def __init__(
        self,
        train: bool = True,
        use_polygons: bool = False,
        recognition_task: bool = False,
        **kwargs: Any,
    ) -> None:
        url, sha256, name = self.TRAIN if train else self.TEST
        super().__init__(
            url,
            name,
            sha256,
            True,
            pre_transforms=convert_target_to_relative if not recognition_task else None,
            **kwargs,
        )
        self.train = train

Do you want to open a PR for this maybe ? :)


testautomation --filter audio_pauseUnpauseAudio

This test fails in sdl2-compat.
It looks like it's unpausing the audio and expecting the audio callback to run in the background. That works as expected in SDL2, but for some reason that's not happening in SDL3.

This is passing in sdl2-compat for me, with the latest in main for SDL3 and sdl2-compat. Is there a specific audio backend you're using? I could see this maybe failing on one that provides its own thread.

I think I'm using wasapi

This reproduces for me on Windows, now that I've got everything building.

Okay, here's what's happening:
sdl2-compat exposes a single SDL3 audio stream as an SDL2 audio device, bridging the SDL3 stream's callback to the app's SDL2 audio callback.
The stream will fire the callback whenever something (here, the SDL3 audio device's thread) requests more data. It tells the app roughly how much more it needs. If it doesn't need anything, because the stream has enough data to fulfill the current request, it fires the callback asking for 0 more bytes of data.
This 0 is what's upsetting the test. WASAPI is triggering this, but having not looked further, I assume any platform could trigger this, depending on hardware settings and application needs.
So there are several good options for fixing this that can have further effects than sdl2-compat:

We just ignore 0-byte requests in sdl2-compat and call it a day.

We change the SDL3 audio stream callback to only fire when something reads from a stream and the stream needs more data to fulfill the request. Right now it always fires, in case the app wants the status update, since the app isn't required to fulfill a request of any size here, in any case, but that might be silly.

We could have sdl2-compat manage the SDL2 callback itself and feed the audio stream at a consistent rate, and not use the audio stream callback at all.

We could wait to fix this until we add a postmix callback to each logical device in SDL3, which would probably map much more closely to SDL2's audio callback, and make sdl2-compat use that instead. If this gets added, it's going to be unforgiving about data conversion and such, because we just built a whole fancy layer on top of it to handle that. But that would be sdl2-compat's problem, not the SDL2-based app's.

I'm leaning towards 4 at the moment, since we're in theory going to want this for SDL_mixer, and other things.

(Actually, something else is going on, too, because it's taking more than a second to need more than 0 bytes of audio, which also causes the test to fail when ignore 0-byte requests...that part might be an sdl2-compat bug for sure; I'm guessing we need to throw away already-queued data when pausing the SDL2 device.)

And I've pushed some defensive fixes to sdl2-compat that I mentioned. I'll move the other thoughts over to another bug and close this one.


[Mob] sounds like [mob]

Maybe this could just be a generated map? So every new spell has a different mapping of mobA:soundA, but that way all mobs change sounds and all mobAs have soundA.