text:
Missing Public Constructor on Type  Elastic.Clients.Elasticsearch.Fields

**Elastic.Clients.Elasticsearch version 8.13.7
**Elasticsearch version 8.12.2
**.NET runtime version .net 8
**Operating system version windows 11
I want to declare a instance of MulitMatchQuery with multiple Fields. The property of MulitMatchQuery.Fields is of Type Fields, which i cannot initialize.
A clear and concise description of what the bug is.
Missing public constructor
Steps to reproduce:

Install nuget Elastic.Clients.Elasticsearch 8.13.7
Try initialize a Fields instance

I see, it inherits from IEnumerable so i can pass that instead of a fieldsinstance. I think this is very confusing tho, is this as expected ?

@DavidHoechtlJH Yes, take a look at the different implicit conversion operators of this class. You can even use lambda expressions to initialize the Fields.
I think it's good practice to have matching static methods for each implicit operator like "Fields.FromStrings(...)" etc. I'll try to add these in one of the next releases.

authors: DavidHoechtlJH flobernd


text:
Avoid doing multiple dictionary lookups

Dictionary lookup involves get key hash, find bucket for hash and iterate bucket for key, so look the value up once, instead of checking if the key exists and then using the indexer to look up the value.
It also reduces the amount of duplicate hardcoded keys in the code.
Could not find any documentation for running the benchmark, so I haven't checked if it actually makes any difference. Haven't analyzed how often the code is executed.
Some places ContainsKey is used before Remove. That is not needed for Dictionary<>, as it will just return false for key not found, but I am uncertain of the specification for IDictionary<> void Remove, so I left it in place.

Thanks @Henr1k80 👍

ported to 5.x: 641df53f5fa646648bc9cfb8d14d5ef11041f30a
ported to master: c159ddffe0592bcc4e38fe8270b11905a6da9c64

source: gharchive/pull-request

repo: elastic/elasticsearch-net

license_type: permissive

license_source: github-api


text:
Refactor ServerError, Error and ErrorCause

With both the low level client and high level client now using the same internal serializer, the deserialization of ServerError, Error and ErrorCause can be simplified.
ErrorCauseMetadata is removed from ErrorCause, and the properties it contains are hoisted onto ErrorCause. It is possible that the JSON for and error cause contains properties that are not mapped on ErrorCause. Currently, these will be ignored. If we feel it is worthwhile, we could also capture these too, by implementing ErrorCause as a dictionary with a formatter to deserialize and set known values

we could also capture these too, by implementing ErrorCause as a dictionary with a formatter to deserialize and set known values

Relates to https://github.com/elastic/elasticsearch/issues/27672
I'd be +1 to rework ErrorCause into a dictionary as a long term plan. Let's track this in a separate issue though.

authors: Mpdreamz russcam


text:
Fix CI resolving to bundled JDK

This works  currently works locally but not on azure devops where it falls back to the installed JRE8 which the snapshots build no longer accepts as a valid java version.
This PR updates abstractions to version that prints JAVA_HOME just before starting elasticsearch and forces it on the Process instance

https://github.com/elastic/elasticsearch/issues/44902
This will now raise an error if a body was sent but was left unconsumed by the server which is a great addition.
SupportsBody now makes it way to our codegen to make sure we never sent a body if no body is documented.


text:
Serialize custom ITokenizer implementations

custom ITokenizer implementations serialize is not expexted.

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

duplicate of #5039

authors: Mpdreamz elasticmachine fate1009


text:
[Backport master] Fix failing transform tests and support dates_as_epoch_millis

Tests were failing due to a change in the transform API which now
prefers ISO dates, rather than epoch milliseconds for dates. This
resulted in a serialisation failure.
This commit addresses that by conditionally producing the requests
based on the version of ES being tested, so that a property of the
appropriate type is used for deserialisation of the preview.
This also adds support for the now dates_as_epoch_millis setting which
allows the original epoch millisecond format to be returned for ES 7.11
requests, when the option is true.
(cherry picked from commit 7994d6fdf7734a5cb7b774e80dfc463fefd2b9cb)
Backport 7994d6fdf7734a5cb7b774e80dfc463fefd2b9cb from #5209

known flakey tests in (WindowsIntegrationTests latest)


text:
undefined method to_hash' for class Elasticsearch::Model::Response::Result'

I cannot use Model.search({}).to_a and similar methods when I am using Mongoid, I have the following code:
# app/models/user.rb
# Code extracted from a devise model, also it is using Mongoid 4.0.2 as its ODM
class User
  include Mongoid::Document
  include Elasticsearch::Model
  include Elasticsearch::Model::Callbacks

  index_name "users-#{Rails.env}"

  field :email, type: String, default: ""
  field :first_name, type: String, default: ""
  field :last_name, type: String, default: ""

  def as_indexed_json
    as_json(except: [:_id])
  end

end

I have created my index like this:
  User.__elasticsearch__.create_index! force: true
  User.import

but the search does not work when I try to use the array's methods
  User.search('allam').to_a
  #=> output error: #<NameError: undefined method `to_hash' for class `Elasticsearch::Model::Response::Result'>

I only can use the following code
  User.search('allam').records.to_a

But I do not want to hit the database for retrieving the searched documents
Perhaps did I miss some step?
Thank you for your support!

Hi, this is really surprising, can you investigate the Mongoid example avaialable here: https://github.com/elastic/elasticsearch-rails/blob/master/elasticsearch-model/examples/mongoid_article.rb ? I've tried it now and it works.
Also notice that you can do User.search('allam').results.to_a to load the documents from Elasticsearch, instead from database.

Hi, yesterday I also tried the option that you suggested me: Model.search({}).results.to_a, but I got the same error.
Today I have tried with the example code, and as you mentioned before, it works!
However, in my case the search is still failing, I have made an example project (it is based on a rails template) and I have pushed it to my github here
my key files are the following:
# app/models/book.rb
class Book
  include Mongoid::Document
  include Elasticsearch::Model
  include Elasticsearch::Model::Callbacks

  index_name "users-#{Rails.env}"

  field :title, type: String
  field :author, type: String

  def as_indexed_json(options={})
    as_json(except: [:id, :_id])
  end
end

# config/initializers/elasticsearch.rb
Elasticsearch::Model.client = Elasticsearch::Client.new url: ENV['ELASTICSEARCH_URL'] || 'http://localhost:9200'

# Book.__elasticsearch__.client.indices.delete index: Book.index_name rescue nil

unless Book.__elasticsearch__.index_exists?
  Book.__elasticsearch__.create_index! force: true
  Book.import
end

This is strange because some days ago I had almost the same configuration but using PostgreSQL and it worked
Also notice that I can perform some actions on the results object, for example (based on my example project)
Book.search('Children').results.count
#=> 1

But when I try to call some array's methods it breaks
Book.search('Children').results.to_a
#=> (pry) output error: #<NameError: undefined method `to_hash' for class `Elasticsearch::Model::Response::Result'>

Hi,
(Sorry for my english...) I have found the error, at the beginning I was thinking that it could be related with my Pry configuration, I'm using the jazz_hands gem, but in summary the problem was focused on this part of code:
Pry.config.print = ->(output, value, _pry_) do
  return if JazzHands._hirb_output && Hirb::View.view_or_page_output(value)
  pretty = value.ai(indent: 2) # <-- ERROR
  _pry_.pager.page("=> #{pretty}")
end

value is an instance of Elasticsearch::Model::Response::Result and the "ai" method is an alias for awesome_inspect, and the real problem was focused on this method (source available here)
what is happening here is that when this method (awesome_inspect) is invoked and the value is a kind of Hash (Hashie in this case) instance there is a method that is invoked for formatting the value  which is named "convert_to_hash" (source available here), inside this method we have the following situation:
Elasticsearch::Model::Response::Result#respond_to? :to_hash
#=> true

but,
Elasticsearch::Model::Response::Result#method :to_hash
#=> NameError: undefined method `to_hash' for class `Elasticsearch::Model::Response::Result'

so this is replicable when for example I use awesome_print directly, (in my example project without the jazz_hands gem)
Book.search('Children').results.to_a # it works!
#=> [#<Elasticsearch::Model::Response::Result:0x007f8b82903f48 @result=#<Hashie::Mash _id="5588213f4a75612cc5010000" _index="books-development" _score=0.4375 _source=#<Hashie::Mash author="Ian McEwan" title="The Children Act"> _type="book">>]

ap Book.search('Children').results.to_a.first  # it does not work
#=> NameError: undefined method `to_hash' for class `Elasticsearch::Model::Response::Result'

Book.search('Children').results.to_a.first.method(:to_hash) # it does not work
#=> NameError: undefined method `to_hash' for class `Elasticsearch::Model::Response::Result'

What I did for solving the problem was to make a method named 'to_hash' inside the Elasticsearch::Model::Response::Result class (source available here), all the tests are running but I don't know if this solution is ok (also I have tested this solution using both ActiveRecord and Mongoid and it works!), however, I have made a pull request but I had a problem with my CLA (I already have one but it does not work, I'll back in 60 minutes).
What do you think about the solution @karmi ?

source: gharchive/issue

authors: Johaned karmi

repo: elastic/elasticsearch-rails


text:
testing, ignore.

testing, ignore.

Pull request acceptance prerequisites:

[ ] Signed the CLA (if not already signed)
[ ] Rebased/up-to-date with base branch
[ ] Tests pass
[ ] Updated CHANGELOG.md with patch notes (if necessary)
[ ] Updated CONTRIBUTORS (if attribution is requested)

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

repo: elastic/puppet-elasticsearch


text:
Update Home Assistant Docker image to version 2024.12.2

This pull request updates the Home Assistant Docker image to version 2024.12.2.

coverage: 99.913%. remained the same
when pulling d6fdde631e040d165082c43cdcd3e40aef26ed2d on update_home_assistant_docker_image
into 7279c0c85ec2dc2669e7580c9a4e11596ef8505e on master.

authors: coveralls elchininet

repo: elchininet/custom-sidebar


text:
Use Repl with usePGLite with typescript

I get the ts error:
Type 'PGliteWithLive' is missing the following properties from type 'PGlite': #private, Modulets(2739)

Most things seem to work if I simply do a:
        <Repl
          // @ts-ignore
          pg={db}
        />

Is Repl supposed to work with usePGLite?

Yep, we want it too, thats a bug. We haven't actually tested the new React hooks with the Repl component.
Looks like it's just a type issue, as you've noted @ts-ignore makes it work.

This is fixed the just published v0.2.1

authors: AntonOfTheWoods samwillis

repo: electric-sql/pglite


text:
[macOS] Module not found: typescript-webpack can 'start' with the 'trash' package, but not 'make'

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

I'm not sure whether this is a problem with ElectronForge or Webpack or @stroncium/procfs, but since start works and make fails, I'm posting this as an ElectronForge issue.
Issue Details

Electron Forge Version:

6.0.0-beta.50

Electron Version:

v8.0.2

Operating System:

macOS 10.15.3 & Linux Ubuntu 18.04 LTS

Expected Behavior
The typescript-webpack template make command can successfully build the trash package (or rather its dependency @stroncium/procfs) on macOS and Linux.
Actual Behavior
It works fine:

on Windows (instead of Linux/macOS)
or when using the default ElectronForge template (instead of typescript-webpack)
or when using start (instead of make)

But otherwise, I get this error:
> test-trash-webpack@1.0.0 make /Users/nathan/dev/test-trash-webpack
> electron-forge make

✔ Checking your system
✔ Resolving Forge Config
We need to package your application before we can make it
✖ Compiling Main Process Code

An unhandled error has occurred inside Forge:
Compilation errors in the main process: Hash: 76c19426585ec5cb1d9f
Version: webpack 4.41.6
Time: 3954ms
Built at: 27/02/2020 14:21:04
                           Asset      Size  Chunks         Chunk Names
                        index.js   115 KiB       0         main
                    index.js.map   459 KiB       0  [dev]  main
      native_modules/macos-trash  9.11 KiB
native_modules/windows-trash.exe    28 KiB
Entrypoint main = index.js index.js.map
 [0] external "path" 42 bytes {0} [built]
 [1] external "fs" 42 bytes {0} [built]
 [2] external "util" 42 bytes {0} [built]
 [5] external "child_process" 42 bytes {0} [built]
[11] external "electron" 42 bytes {0} [built]
[25] ./src/index.ts 1.75 KiB {0} [built]
[26] ./node_modules/trash/index.js 1.21 KiB {0} [built]
[27] ./node_modules/globby/index.js 3.17 KiB {0} [built]
[43] ./node_modules/p-try/index.js 211 bytes {0} [built]
[44] ./node_modules/is-path-inside/index.js 439 bytes {0} [built]
[45] ./node_modules/trash/lib/macos.js 738 bytes {0} [built]
[46] ./node_modules/trash/lib/linux.js 2.2 KiB {0} [built]
[94] ./node_modules/trash/lib/windows.js 563 bytes {0} [built]
[95] ./node_modules/electron-squirrel-startup/index.js 1 KiB {0} [built]
[96] ./node_modules/debug/src/index.js 314 bytes {0} [built]
    + 88 hidden modules

ERROR in ./node_modules/@stroncium/procfs/lib/parsers.js
Module not found: Error: Can't resolve './parsers/' in '/Users/nathan/dev/test-trash-webpack/node_modules/@stroncium/procfs/lib'
 @ ./node_modules/@stroncium/procfs/lib/parsers.js 48:15-42
 @ ./node_modules/@stroncium/procfs/index.js
 @ ./node_modules/trash/lib/linux.js
 @ ./node_modules/trash/index.js
 @ ./src/index.ts
Error: Compilation errors in the main process: Hash: 76c19426585ec5cb1d9f
Version: webpack 4.41.6
Time: 3954ms
Built at: 27/02/2020 14:21:04
                           Asset      Size  Chunks         Chunk Names
                        index.js   115 KiB       0         main
                    index.js.map   459 KiB       0  [dev]  main
      native_modules/macos-trash  9.11 KiB
native_modules/windows-trash.exe    28 KiB
Entrypoint main = index.js index.js.map
 [0] external "path" 42 bytes {0} [built]
 [1] external "fs" 42 bytes {0} [built]
 [2] external "util" 42 bytes {0} [built]
 [5] external "child_process" 42 bytes {0} [built]
[11] external "electron" 42 bytes {0} [built]
[25] ./src/index.ts 1.75 KiB {0} [built]
[26] ./node_modules/trash/index.js 1.21 KiB {0} [built]
[27] ./node_modules/globby/index.js 3.17 KiB {0} [built]
[43] ./node_modules/p-try/index.js 211 bytes {0} [built]
[44] ./node_modules/is-path-inside/index.js 439 bytes {0} [built]
[45] ./node_modules/trash/lib/macos.js 738 bytes {0} [built]
[46] ./node_modules/trash/lib/linux.js 2.2 KiB {0} [built]
[94] ./node_modules/trash/lib/windows.js 563 bytes {0} [built]
[95] ./node_modules/electron-squirrel-startup/index.js 1 KiB {0} [built]
[96] ./node_modules/debug/src/index.js 314 bytes {0} [built]
    + 88 hidden modules

ERROR in ./node_modules/@stroncium/procfs/lib/parsers.js
Module not found: Error: Can't resolve './parsers/' in '/Users/nathan/dev/test-trash-webpack/node_modules/@stroncium/procfs/lib'
 @ ./node_modules/@stroncium/procfs/lib/parsers.js 48:15-42
 @ ./node_modules/@stroncium/procfs/index.js
 @ ./node_modules/trash/lib/linux.js
 @ ./node_modules/trash/index.js
 @ ./src/index.ts
    at cb (/Users/nathan/dev/test-trash-webpack/node_modules/@electron-forge/plugin-webpack/src/WebpackPlugin.ts:250:31)
    at finalCallback (/Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compiler.js:257:39)
    at /Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compiler.js:273:13
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/Hook.js:154:20)
    at onCompiled (/Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compiler.js:271:21)
    at /Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compiler.js:681:15
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/Hook.js:154:20)
    at /Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compiler.js:678:31
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/Hook.js:154:20)
    at /Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compilation.js:1423:35
    at AsyncSeriesHook.eval [as callAsync] (eval at create (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:4:1)
    at AsyncSeriesHook.lazyCompileHook (/Users/nathan/dev/test-trash-webpack/node_modules/tapable/lib/Hook.js:154:20)
    at /Users/nathan/dev/test-trash-webpack/node_modules/webpack/lib/Compilation.js:1414:32

To Reproduce
yarn create electron-app test-trash-webpack --template=typescript-webpack
cd test-trash-webpack
yarn add trash

then add this to index.ts
import trash from 'trash'
(() => trash)(); // Prevent tree-shaking

start runs fine, but make fails with the above error.
Additional Information
The same thing happens when requesting the procfs package directly:
import {procfs} from '@stroncium/procfs'
(() => procfs)(); // Prevent tree-shaking

This is the offending file: https://github.com/stroncium/nodejs-procfs/blob/master/lib/parsers.js

Hey @nathanvogel I've also come across this issue, but on Windows.

Electron Forge Version:

6.0.0-beta.50

Electron Version:

8.1.0

Operating System:

Windows 10 17763.1039 and 18362.657

I currently have a workaround that may work for you. Install string-replace-loader and in your webpack.rules.js add the following rule:
{
  test: /parsers\.js$/,
  loader: 'string-replace-loader',
  options: {
    search: 'module.exports = parsers;',
    replace: 'export default parsers;',
  }
}

Hope this helps!

Thanks @Mac-Genius, it's a bit heavy-handed, but it helped. Afterwards, I still had a few issues:
macOS
I got an EACCESS error when running the trash module afterwards, which I fixed with this:
  hooks: {
    packageAfterCopy: async (config, buildPath, version, platform) => {
      console.log("Platform::::: " + platform);
      if (platform !== "darwin") return;
      // buildPath is something like:
      // /var/folders/mv/vd2n2svd0570b614s31g5h440000gn/T/electron-packager/darwin-x64/MyApp-darwin-x64/Electron.app/Contents/Resources/app
      const trashPath = path.resolve(
        buildPath,
        ".webpack/main/native_modules/macos-trash",
      );
      await fs.chmod(trashPath, 0o755);
      console.log("Applied chmod fix for 'trash' module on macOS.");
    },
  },

Linux
I'm having this error, which I haven't looked into yet:
ProcfsError: Unknown error: parsers[name] is not a function

So there's more to it than that...

This would be solved by using externals which is blocked by #1250

authors: Mac-Genius MarshallOfSound nathanvogel

repo: electron-userland/electron-forge

license: mit

license_source: bigquery


text:
App name and version not set in development mode?

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here). Please include the stack trace if one exists.
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Checking your system +0ms
  electron-forge:lifecycle Process Succeeded: Checking your system +17ms
  electron-forge:runtime-config setting key: verbose to value: false +13ms
WARNING: DEBUG environment variable detected.  Progress indicators will be sent over electron-forge:lifecycle
  electron-forge:lifecycle Process Started: Locating Application +0ms
  electron-forge:project-resolver searching for project in: /Users/vinsonb/scratch/test-electron-app +2ms
  electron-forge:project-resolver electron-forge compatible package.json found in /Users/vinsonb/scratch/test-electron-app/package.json +5ms
  electron-forge:lifecycle Process Succeeded: Locating Application +1ms
  electron-forge:lifecycle Process Started: Preparing native dependencies +1ms
  electron-forge:lifecycle Process Succeeded: Preparing native dependencies +43ms
  electron-forge:hook could not find hook: generateAssets +6ms
  electron-forge:lifecycle Process Started: Launching Application +1ms
  electron-forge:lifecycle Process Succeeded: Launching Application +4ms

What command line arguments are you passing?
start

What does your config.forge data in package.json look like?
"forge": {
            "make_targets": {
                "win32": [
                    "squirrel"
                ],
                "darwin": [
                    "zip"
                ],
                "linux": [
                    "deb",
                    "rpm"
                ]
            },
            "electronPackagerConfig": {
            },
            "electronWinstallerConfig": {
                "name": "test_electron_app"
            },
            "electronInstallerDebian": {},
            "electronInstallerRedhat": {},
            "github_repository": {
                "owner": "",
                "name": ""
            },
            "windowsStoreConfig": {
                "packageName": "",
                "name": "testelectronapp"
            }

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-forge init is a good starting point, if that is not the
source of your problem.
When creating a new project with electron-forge init and then running electron-forge start the methods app.getName() and app.getVersion() return information about Electron itself instead of the values from package.json. They work fine when the application is packaged. This causes application data from all Electron Forge development apps to be put into the same directory, makes them all have the same user agent, etc. This does not happen in development mode with a minimal electron-quick-start application.
If this is the expected behavior, is there any way to override this? My current workaround is to use app.setAppName etc, but that seems quite hacky. I apologize if this is documented somewhere, as it seems pretty basic. I tried searching around, but only found people using the same workaround: https://github.com/felixrieseberg/ember-electron/issues/199

This appears to be a bug in the electron-prebuilt-compile module? I can reproduce the behavior by cloning electron-quick-start and replacing electron with electron-prebuilt-compile, then running npm start after adding the following to the bottom of main.js:
console.log(app.getName())
console.log(app.getVersion())

CC: @paulcbetts

PR up in electron-prebuilt-compile to fix this 👍

authors: BenV MarshallOfSound malept


text:
[WIP] feat(generic): print a warning if the package manager used is not a known good version

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
The version whitelists need to be updated and audited.
Fixes #269.

I take it we should just add NPM/yarn versions as we move forward, then?


text:
Sourcemaps don't seem to be loaded while Debugging main process with Chrome Dev Tools

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Expected behavior
I should be able to debug the main process with Chrome Dev Tools with proper source maps instead I am getting this:

Extremely simple to reproduce.
Just scaffold a new project with the Vite + Typescript plugin
npm init electron-app@latest pure-forge-app -- --template=vite-typescript

Then add a new entry to scripts in package.json.
"dev:main": "electron-forge start -- --inspect-brk"
As suggested here, https://www.electronforge.io/cli#options
Electron Forge version
7.2.0
Electron version
v28.2.1
Operating system
macOS 14.2.1
Last known working Electron Forge version
7.2.0

vite.main.config.mjs
defineConfig({
  build: {
+   rollupOptions: {
+     output: {
+       sourcemap: true,
+     },
+   },
  },
});

@caoxiemeihao Thanks a ton! Shouldn't this be default behaviour for DEVELOPMENT and probably optional for PRODUCTION?

@caoxiemeihao Thanks a ton! Shouldn't this be default behaviour for DEVELOPMENT and probably optional for PRODUCTION?

This is a good idea, and I will improve the sourcemap option in future versions.

@caoxiemeihao Incase you can give me some quick directions, I'd love to attempt a PR myself?

repo: electron/forge

license: MIT


text:
feat: support pnpm

Signed-off-by: Yi Yang yangyi.makeryi@gmail.com

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
Adding PNPM support - picking up where https://github.com/electron/forge/pull/3351 left off.
Related issue: https://github.com/electron/forge/issues/2633

Is this PR ready to go? If so, is there an ETA on when it might get merged?

I wasn't the original author of this code but happy to do what it takes to get this one released - we use PNPM in WDIO and native support here would definitely help.

I think there are some legitimate test failures that we'll have to investigate in slow-tests.
It may be that pnpm is hanging somewhere along the line? It seems like all 3 platforms are hanging and CircleCI is cutting off the CI jobs.

It is hanging on this line, the package step of the import test.
Added more logging to core/api/package.ts and it seems this await never resolves...

I was looking in the wrong place.  All of the tests passed in d334388 and subsequently broke with the merge in cf43b13.  Looking at the latter, it's obvious why.

Not sure what is going on here and at the moment I don't have the time to dedicate to it.  Hopefully I get some more time, happy for someone else to pick this up though.

@goosewobbler please can you resolve conflicts?

authors: emilbon99 erickzhao goosewobbler rtritto


text:
Fix release-image.yml

After moving the workflow to a new file, it seems the environment wasn't copied. So the images variable was set to "/", and so it failed with the error: buildx failed with: ERROR: invalid tag "/:0.6.6": invalid reference format"

Worth a try.

authors: jberkus mscherer

repo: elekto-io/elekto


text:
Minor updates/clean-ups

Rename from SCHED* to Sched (and .org to .com)
Add version to user agent
Bump dependencies
Update README

Thanks alot!

authors: elektronaut reedloden

repo: elektronaut/sched


text:
🛑 Ombi is down

In af65bb9, Ombi (https://ombi.lepallec.tv) was down:

HTTP code: 403
Response time: 83 ms

Resolved: Ombi is back up in 6c419f6.

repo: elepallec/upptime


text:
🛑 UCU - Maraton is down

In 8e96fc4, UCU - Maraton (https://maraton.ucu.edu.ar/) was down:

HTTP code: 523
Response time: 315 ms

Resolved: UCU - Maraton is back up in d37c3fd after 2 hours, 17 minutes.

repo: elfoche/monitoreo


text:
RARBG timed out, Torrentleech login failed 0.0.21

Here is a part of the log file.
RARBG is timed out, Torrentleech cloudhole enabled and the login fail.
 12:07:04.590 T:9308  NOTICE: [script.elementum.burst] Burstin' with RARBG, 1337x, YTS, The Pirate Bay, TorrentLeech, MagnetDL, TorLock
> 12:07:04.592 T:9308   ERROR: [script.elementum.burst] Getting CloudHole key error: AttributeError("'NoneType' object has no attribute 'open'",)
> 12:07:04.671 T:12788  NOTICE: [script.elementum.burst] >>                 YTS returned  0 results in 0.1 seconds
> 12:07:04.697 T:1860  NOTICE: [script.elementum.burst] [rarbg] Using translated 'original' title u'billions'
> 12:07:04.699 T:13920  NOTICE: [script.elementum.burst] [1337x] Using translated 'original' title u'billions'
> 12:07:04.700 T:7724  NOTICE: [script.elementum.burst] [thepiratebay] Using translated 'original' title u'billions'
> 12:07:04.701 T:7192  NOTICE: [script.elementum.burst] [torrentleech] Using translated 'original' title u'billions'
> 12:07:04.702 T:4744  NOTICE: [script.elementum.burst] [magnetdl] Using translated 'original' title u'billions'
> 12:07:04.703 T:7856  NOTICE: [script.elementum.burst] [torlock] Using translated 'original' title u'billions'
> 12:07:04.705 T:13920  NOTICE: [script.elementum.burst] >                1337x search URL: https://www.1337x.to/search/billions+s03e11/1/
> 12:07:04.707 T:7724  NOTICE: [script.elementum.burst] >       The Pirate Bay search URL: https://thepiratebay.org/search/billions%20s03e11/0/99/200
> 12:07:04.710 T:1860   ERROR: Exception in thread Thread-1:
>                                             Traceback (most recent call last):
>                                               File "C:\Program Files (x86)\Kodi\system\python\Lib\threading.py", line 801, in __bootstrap_inner
>                                                 self.run()
>                                               File "C:\Program Files (x86)\Kodi\system\python\Lib\threading.py", line 754, in run
>                                                 self.__target(*self.__args, **self.__kwargs)
>                                               File "C:\Users\ilane\AppData\Roaming\Kodi\addons\script.elementum.burst\burst\burst.py", line 511, in run_provider
>                                                 results = process(provider=provider, generator=extract_from_api, filtering=filterInstance, has_special=payload['has_special'])
>                                               File "C:\Users\ilane\AppData\Roaming\Kodi\addons\script.elementum.burst\burst\provider.py", line 162, in process
>                                                 client.open(token_url.encode('utf-8'), proxy_url=filtering.info['proxyUrl'], charset=definition['charset'])
>                                             KeyError: 'proxyUrl'
> 12:07:04.711 T:4744  NOTICE: [script.elementum.burst] >             MagnetDL search URL: http://www.magnetdl.com/b/billions-s03e11/
> 12:07:04.712 T:7856  NOTICE: [script.elementum.burst] >              TorLock search URL: https://www.torlock2.com/television/torrents/billions-s03e11.html
> 12:07:05.018 T:7192 WARNING: [script.elementum.burst] Status for 'https://classic.torrentleech.org/user/account/login/' : 503
> 12:07:05.018 T:7192 WARNING: [script.elementum.burst] CloudFlared at https://classic.torrentleech.org/user/account/login/, try enabling CloudHole
> 12:07:05.019 T:7192   ERROR: [script.elementum.burst] [torrentleech] Login failed: 503
> 12:07:05.019 T:7192  NOTICE: [script.elementum.burst] >>        TorrentLeech returned  0 results in 0.4 seconds
> 12:07:05.650 T:4744  NOTICE: [script.elementum.burst] >>            MagnetDL returned 18 results in 1.1 seconds
> 12:07:05.920 T:7856  NOTICE: [script.elementum.burst] >>             TorLock returned  0 results in 1.3 seconds
> 12:07:06.251 T:7724  NOTICE: [script.elementum.burst] [thepiratebay] Using translated 'original' title u'billions'
> 12:07:06.252 T:7724  NOTICE: [script.elementum.burst] >       The Pirate Bay search URL: https://thepiratebay.org/search/billions%20s03/0/99/200
> 12:07:06.841 T:13920  NOTICE: [script.elementum.burst] >>               1337x returned 14 results in 2.3 seconds
> 12:07:07.738 T:7724  NOTICE: [script.elementum.burst] >>      The Pirate Bay returned 20 results in 3.1 seconds
> 12:07:12.825 T:2060  NOTICE: [plugin.video.elementum] ERRO  tmdb         ▶ func1            Bad status getting season 22 of show 2190: 404
> 12:07:13.037 T:2060  NOTICE: [plugin.video.elementum] ERRO  tmdb         ▶ func1            Bad status getting S22E01 of 2190: 404
> 12:07:14.705 T:2060  NOTICE: [plugin.video.elementum] [GIN] 2018/08/04 - 12:07:14 | 200 |    2.3089981s |       127.0.0.1 | GET      /shows/trakt/progress
> 12:07:17.755 T:9308 WARNING: [script.elementum.burst] RARBGעבר הזמן
> 12:07:17.768 T:9308  NOTICE: [script.elementum.burst] Providers returned 30 results in 13.18 seconds
> 12:07:17.770 T:2060  NOTICE: [plugin.video.elementum] [GIN] 2018/08/04 - 12:07:17 | 200 |            0s |       127.0.0.1 | POST     /callbacks/203101283895217702
> 12:07:17.848 T:2060  NOTICE: [plugin.video.elementum] INFO  linkssearch  ▶ processLinks     Received 30 unique links.

Try version 0.0.22.

The cloudhole bug for TorrentLeech i think is fixed now, but it still wont login to the site.
[script.elementum.burst] [torrentleech] Login failed: 503
, although everything seems to be corrent.
Even tried adding the 'login': 'submit'
"login_object": "{'username': USERNAME, 'password': PASSWORD, 'login': 'submit'}",
but that didnt help

Error 503 means page is protected with cloudhole and that is not working. They are changing the way to protect pages all the time.
I will not do anything with that. Maybe someone will submit a change, then  Iwill review it.

Hi!
On RARBG have a results from search when i test the search link, but not return results on addon.
Example:
RARBG search URL: https://torrentapi.org/pubapi_v2.php?mode=search&search_string=wonder 2017&category=14;48;17;44;45;47;50;51;52;42;46&format=json_extended&app_id=script.elementum.burst&token=bcp5z47vl9
RARBG returned  0 results in 0.7 seconds
Can you check this?
Thank you in advance!

Can you check this?

Full log file needed.

Hmm... Now return results... Interesting!
Sorry!
Thank you!

Please, check Burst 0.0.31 with Elementum >= 0.0.67.

Elementum burst: rarbg,1337x timed out, no links were found.

@MilePule if you want any help - you have to post log files.

Oh sorry,
https://paste.ubuntu.com/p/R2pJFMNZ8J/

@MilePule
I have tried and both work well.
You can try to increase providers timeout in Elementum.

Already tried it, no go. I reverted to previous versions of elementum&burst and everything just works fine.

@MilePule
I have tried and both work well.
You can try to increase providers timeout in Elementum.

Already tried it, no go. I reverted to previous versions of elementum&burst and everything just works fine.

Can you show the log with previous elementum?

I will soon, I just went out.

Can you show the log with previous elementum?

https://paste.ubuntu.com/p/Y5B8BGF9WG/

Disable in Elementum Settings -> Proxy -> "Enable built in http proxy" and everything works fine!

authors: MilePule Sandbird elgatito ilanerukh martinstz


text:
Use window.localStorage to ensure the lib works in a mocha environment

Simple fix to ensure the library works when being run in a mocha environment which doesn't use window as the global variable

The code around this has a deeper problem: localStorage may not be well defined at all, e.g. in a React Native environment.  I just tried to give redux-localstorage a try in an RN project, but the code in persistState.js (1.0 branch) blows up with "localStorage is not defined", even though I was passing a valid storage to persistState built with adapter(AsyncStorage).

React Native doesn't support localStorage to begin with, so I don't think redux-localStorage will work for you there.

@globexdesigns, redux-localstorage isn't even a little bit specific to localStorage, speaking to the 1.0-breaking-changes branch:

Unopinionated store enhancer that persists state changes (locally).

It explicitly has adapters for several different stores including RN's AsyncStorage.  localStorage is just one of the supported stores and happens to also be the default.
After my prior comment, I discovered that HEAD of 1.0-breaking-changes works correctly with AsyncStorage due to the fix in 61f9db95237a090daff2968ae1cae3b9252d6875.  For my part, I'd like to see either a full 1.0 release, or at least an rc5 containing this fix.
Your issue can be fixed easily in your app code by explicitly using adapter(window.localStorage) instead of relying on the default store code.  You'll probably also need to use HEAD of the 1.0 branch for that to work correctly under mocha.

Merged, thanks!

authors: elgerlambert globexdesigns jwhitley

repo: elgerlambert/redux-localstorage


text:
Compilation error: std::fmt::Debug not implemented for async block in async_trait

I encountered a compilation error while using the async_trait crate in combination with the logfn macro from the log-derive . The error message states that std::fmt::Debug is not implemented for the async block that async_trait generates. Here's a simplified version of the code that's causing the issue:
#[async_trait::async_trait]
trait MyTrait {
    async fn work(&self) -> usize;
}

struct MyStruct;

#[async_trait::async_trait]
impl MyTrait for MyStruct {
    #[logfn(Debug)]
    async fn work(&self) -> usize {
        todo!()
    }
}

The error message I'm receiving is:
the trait `std::fmt::Debug` is not implemented for `[async block@examples/log.rs:30:35: 32:6]`

This issue arises from the fact that async_trait transforms the async function into a function that returns a Pin<Box<dyn Future<Output = usize>>>. The transformed code looks like this:
fn work(&self) -> Pin<Box<dyn Future<Output = usize>>> {
    Box::pin(async { todo!() })
}

The logfn macro is trying to derive Debug for the returned future, but the async block within the future does not implement Debug, leading to the compilation error.
The minitrace-macro crate has some techniques to handle similar situations. It might be useful to consider for a possible solution.
I'd appreciate any guidance or suggestions on how to resolve this issue.

I've made a similar crate https://github.com/andylokandy/logcall to resolve this problem

repo: elichai/log-derive


text:
MSID: 98372 Version: 1 DOI: 10.1101/2024.04.24.590941

MSID: 98372
Version: 1
Preprint DOI: https://doi.org/10.1101/2024.04.24.590941
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98372
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2024.04.24.590941

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98372v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2024.04.24.590941
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98372/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

checking with author which figures made using biorender


text:
[UPDATES] Implementing single queue for assigning room.

Problem Statement
Assigning the candidate and proctors to the room should be persistent and atomic

#44 Closes this one. May be we can reopen later for the single queue implementation.

repo: elitmus/knights-watch


text:
feat(serviceinfo,tes): add models

This PR contains all the autogenerated models created by running the script in the #27
This PR doesn't contain any manually written code, and everything is autogenerated

Summary by Sourcery
Add autogenerated models for the Task Execution Service (TES) API and GA4GH service-info API. Introduce scripts to automate the generation of these models from OpenAPI specifications.
New Features:

Add autogenerated models for the Task Execution Service (TES) API, including TesServiceInfo, TesTask, TesExecutor, TesResources, TesInput, TesOutput, TesState, TesTaskLog, TesExecutorLog, TesOutputFileLog, and TesCreateTaskResponse.
Add autogenerated models for the GA4GH service-info API, including Service, ServiceOrganization, and ServiceType.

Enhancements:

Add a script (utils/script.sh) to automate the generation of models from OpenAPI specifications using the OpenAPI Generator CLI.
Add a build script (utils/build-models.sh) to generate models for multiple APIs by calling the main script with appropriate parameters.

Ok, I will move transport and configuration to utils folder, and will move tes and serviceinfo to a clients folder in further PRs.
@uniqueg, I have merged #30, and have moved to a utils folder in this PR, and moved the models to clients, since the comment regarding changing folders is mentioned here. I think this PR is ready to be merged.


text:
Changeset.cast/3 raises for a list of atom keys from module attribute

Environment

Elixir version (elixir -v):

Erlang/OTP 22 [erts-10.7.1] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe]

Elixir 1.12.1 (compiled with Erlang/OTP 22)

Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): MySQL 8.0
Ecto version (mix deps): ecto 3.7.1 (Hex package) (mix) locked at 3.7.1 (ecto) d36e5b39
Database adapter and version (mix deps): myxql 0.5.1 (Hex package) (mix) locked at 0.5.1 (myxql) 73c6b684
Operating system: MacOS 11.6

Current behavior
The code sample below raises when casting a changeset:

Code Sample
defmodule Quest.Table do
  use Ecto.Schema
  import Ecto.Changeset

  alias Quest.{
    Media,
    Episode,
    User
  }

  schema "table" do
    field :path, :string
    field :title, :string
    field :description, :string

    has_many :episodes, Episode

    belongs_to :media, Media
    belongs_to :user, User

    timestamps(inserted_at: :created_at, updated_at: :updated_at)
  end

  @changeset_fields [:path, :title, :description]

  def changeset(struct, attrs) do
    struct
    |> cast(attrs, @changeset_fields)
    |> validate_required(@changeset_fields)
    |> unique_constraint([:path])
  end
end

Calling changeset/2 raises the error below.
[error] #PID<0.1019.0> running QuestWeb.Endpoint (connection #PID<0.1018.0>, stream id 1) terminated
Server: localhost:8080 (http)
Request: POST /graphiql
** (exit) an exception was raised:
    ** (ArgumentError) cast/3 expects a list of atom keys, got: `[:path, :title, :description]`
        (ecto 3.7.1) lib/ecto/changeset.ex:568: Ecto.Changeset.cast_key/1
        (ecto 3.7.1) lib/ecto/changeset.ex:526: Ecto.Changeset.process_param/7
        (elixir 1.12.1) lib/enum.ex:2356: Enum."-reduce/3-lists^foldl/2-0-"/3
        (ecto 3.7.1) lib/ecto/changeset.ex:513: Ecto.Changeset.cast/6
        (quest 0.1.0) lib/quest/table.ex:36: Quest.Table.changeset/2
        (quest 0.1.0) lib/quest/table/table.ex:78: Quest.Table.update/2
        (absinthe 1.6.6) lib/absinthe/resolution.ex:209: Absinthe.Resolution.call/2
        (absinthe 1.6.6) lib/absinthe/phase/document/execution/resolution.ex:230: Absinthe.Phase.Document.Execution.Resolution.reduce_resolution/1
        (absinthe 1.6.6) lib/absinthe/phase/document/execution/resolution.ex:185: Absinthe.Phase.Document.Execution.Resolution.do_resolve_field/3
        (absinthe 1.6.6) lib/absinthe/phase/document/execution/resolution.ex:170: Absinthe.Phase.Document.Execution.Resolution.do_resolve_fields/6
        (absinthe 1.6.6) lib/absinthe/phase/document/execution/resolution.ex:88: Absinthe.Phase.Document.Execution.Resolution.walk_result/5
        (absinthe 1.6.6) lib/absinthe/phase/document/execution/resolution.ex:67: Absinthe.Phase.Document.Execution.Resolution.perform_resolution/3
        (absinthe 1.6.6) lib/absinthe/phase/document/execution/resolution.ex:24: Absinthe.Phase.Document.Execution.Resolution.resolve_current/3
        (absinthe 1.6.6) lib/absinthe/pipeline.ex:370: Absinthe.Pipeline.run_phase/3
        (absinthe_plug 1.5.8) lib/absinthe/plug.ex:536: Absinthe.Plug.run_query/4
        (absinthe_plug 1.5.8) lib/absinthe/plug.ex:290: Absinthe.Plug.call/2
        (quest 0.1.0) lib/quest_graphql/graphql_plug.ex:16: Quest.Graphql.GraphiqlPlug.plug_builder_call/2
        (phoenix 1.6.2) lib/phoenix/router/route.ex:41: Phoenix.Router.Route.call/2
        (phoenix 1.6.2) lib/phoenix/router.ex:355: Phoenix.Router.__call__/2
        (quest 0.1.0) lib/quest_web/endpoint.ex:1: QuestWeb.Endpoint.plug_builder_call/2

Expected behavior
I'd expect getting this list from the module attribute to work. Maybe I'm overseeing something, but replacing @changeset_fields with [:path, :title, :description] fixes this error.

The @changeset_fields is used internally by Ecto, which causes conflicts with your own attribute. We will rename our fields to avoid conflicts, but meanwhile I recommend you rewriting your module attribute to something else. Thanks!

PS: Just don't rewrite it to @struct_fields :P

authors: Nickforall josevalim

repo: elixir-ecto/ecto


text:
Migration logs redacted fields

Elixir version
1.16.2
Database and Version
any
Ecto Versions
3.11.2
Database Adapter and Versions (postgrex, myxql, etc)
postgrex 0.18.0
Current behavior
Migration:
defmodule CaseManager.Repo.Migrations.FirstUser do
  use Ecto.Migration

  def change do
    execute(fn ->
      repo().insert(
        %CaseManager.Accounts.User{
          email: "EMAIL@EXAMPLE",
          hashed_password: Bcrypt.hash_pwd_salt("EXAMPLE"),
          inserted_at: DateTime.truncate(DateTime.utc_now(), :second),
          updated_at: DateTime.truncate(DateTime.utc_now(), :second)
        },
        log: :error
      )
    end)
  end
end

Log:
10:43:03.340 [error] QUERY OK source="users" db=6.3ms
INSERT INTO "private"."users" ("inserted_at","email","hashed_password","updated_at") VALUES ($1,$2,$3,$4) RETURNING "id" [~U[2024-07-19 08:43:03Z], "first_account_em3ail4@loca.local", "$2b$12$P/59vWqWER.jmqWPuHFFvuJ34V/j508XaXF4Euju.Iv.YuBkRuKAu", ~U[2024-07-19 08:43:03Z]]

Expected behavior
Hashed password should not be printed because the field is marked as redacted

This is the query logging and the query logging always shows the full query, specially because the layer doing the logging does not actually have the information about the fields anymore.
However, you can pass log: false and do your own logging:
    execute(fn ->
      Logger.error("inserting user email@example")

      repo().insert(
        %CaseManager.Accounts.User{
          email: "EMAIL@EXAMPLE",
          hashed_password: Bcrypt.hash_pwd_salt("EXAMPLE"),
          inserted_at: DateTime.truncate(DateTime.utc_now(), :second),
          updated_at: DateTime.truncate(DateTime.utc_now(), :second)
        },
        log: false      )
    end)

authors: josevalim ponychicken


text:
Add parameter to set evaluate_code_expression timeout

When trying to debug some web requests, sometimes the 1 second timeout is too short, I think there should be a way to set the timeout to some other value.

Hmm, we should probably just increase the timeout value. How about 10 seconds?

It shouldn't be difficult to read it from launch config

I think it would be preferable to have it be a config parameter, so as to accommodate every need. 10 seconds would be better than the 1 second timeout it has currently, and would suffice for me, but maybe it wouldn't for someone with a very slow internet connection trying to some function that fetches an API call to a remote server.

I think it would be preferable to have it be a config parameter, so as to accommodate every need. 10 seconds would be better than the 1 second timeout it has currently, and would suffice for me, but maybe it wouldn't for someone with a very slow internet connection trying to some function that fetches an API call to a remote server.
I've just started learning elixir more in-depth, so I might be wrong. But why the need for a timeout when evaluating expressions in the debug console? Wouldn't it be better having the timeout be as large as possible (maybe infinite?), and leave to the user the responsibility of forcing the execution to stop in case the evaluation is taking longer than it should? I don't know exactly the inner workings of ElixirLS debugger though, so it might be difficult to implement a client-side halt to a running expression, or maybe there are good reasons not to leave this responsibility to the user.

Also possibly related, calling functions through the debug console will always timeout if the function (or any other function called inside it) has a breakpoint set.

authors: axelson funnisquares lukaszsamson

repo: elixir-lsp/elixir-ls


text:
Add conversational serving

I'm not sure, but I think I'm gonna go to sleep

I felt that

repo: elixir-nx/bumblebee


text:
Lazy Polars backend functionality

This issue tracks the implementation for full backend functionality for lazy Polars. The intent is to enable splitting things up more easily.
IO read

[x] from_csv (#451)
[x] load_csv (#451)
[x] from_parquet (#451)
[x] load_parquet (#451)
[x] from_ipc (#451)
[x] load_ipc (#451)
[x] from_ndjson (#451)
[x] load_ndjson (#451)
[x] load_ipc_stream (b326afd48)

PS: from_ipc_stream for the Lazy backend is not possible because is not available in Polars.
IO write

[x] Certain IO write operations can be done lazily for streaming: https://genserver.social/notice/AQn5LNxxRIfvNvvkNE - we need to investigate which and break it down
[x] to_parquet (#496)
[x] to_ipc (#497) - available only in main branch of Polars
[x] to_ipc_stream (#497) - It's not streamable, even so the name contains "stream". collect() |> write()
[x] to_csv (#497) - It's not streamable. collect() |> write()
[x] to_ndjson (#497) -  It's not streamable. collect() |> write()

Conversion

[x] lazy (#202)
[x] to_lazy (#202)
[x] collect (#202)

Introspection

[x] names (#202)
[x] dtypes (#202)
[x] shape (#497)
[x] n_rows (#497)
[x] n_columns (#202)

Single table verbs

[x] head (#202)
[x] tail (#202)
[x] select (#202)
[x] filter (#476)
[x] mutate
[x] arrange
[x] distinct
[x] rename (#488)
[x] dummies (#497)
[x] sample (#497) - this one may be possible to implement, but not sure how.
[x] pull (#497)
[x] slice (#450)
[x] drop_nil (#488)
[x] pivot_wider (#497)
[x] pivot_longer (#488)
[x] group_by (#202)
[x] ungroup (#202)
[x] summarise

Two or more table verbs

[x] join (#491)
[x] concat_rows (#492)
[x] concat_columns (#492)

Regarding the IO functions, only half of them need to be implemented, right?

All functions not listed here should raise when invoked saying the lazy operation is not allowed.

FYI I'm working on the IO functions of this issue :)

FWIW, we decided to focus on the non-grouped versions. We will support grouped ones later.

I created #498 to track the groups operations.
I'm closing this issue, since most of the functions were implemented or are explicitly raising error now.

authors: cigrainger josevalim philss

repo: elixir-nx/explorer


text:
Tesla.Mock configuration

HI!
What is the proper way to configure Tesla.Mock in situation described below.
Imagine we have a module which creates client:
defmodule SimpleApi.Client do
  @spec get_client() :: Tesla.Client.t()
  def get_client do
    middleware = [
      {Tesla.Middleware.BaseUrl, get_url()},
      Tesla.Middleware.EncodeJson
    ]
    adapter = {Tesla.Adapter.Finch, [name: MyFinch, recv_timeout: 40_000]}
    Tesla.client(middleware, adapter)
  end
end

To use mock in test, there is a need to configure it in test.exs
config :tesla, <instance_name>, adapter: Tesla.Mock
What should be placed in <instance_name?
BR

The config only works when you use the use Tesla macro. In your case when creating a dynamic client you need to pass the adapter from your own configuration.
adapter = Application.get_env(:myapp, :some_key) || {Tesla.Adapter.Finch, …}

and then configure the mock adapter in config/test.exs
I usually put the default adapter in config/config.exs instead of directly in client module

Thank you @teamon.
Using my own configuration works as expected.
All the best ;)

authors: GGuinea teamon

repo: elixir-tesla/tesla


text:
Proposal: Introduce some hook to change encoding of parsed result

Hi Mitch! First off, thanks for your work on Spitfire. It's shaping up really well and is already a valuable tool!
Second, to hedge a bit, I don't know whether implementing this proposal would be appropriate right now given Spitfire's current state of development, but I wanted to bring it up now regardless.
Proposal
Introduce some hook, be it a callback, behaviour, or something else, that controls the encoding of the parsed result. The default would be to emit Macro.t(), as Spitfire currently does, but the hook would allow parsing Elixir code into a bespoke AST of arbitrary format.
As a concrete example, you might imagine the following:
Spitfire.parse!("1 + 2.5", encoder: &custom_encoder/1) # not sure what actual encoder arity would be
#=>
%BinaryCall{
  op: :+,
  meta: %{...},
  left: %Integer{value: 1, meta: %{...},
  right: %Float{value: 2.5, meta: %{...}
}

Context
Elixir's AST is intentionally minimal. One reason is to facilitate authoring macros. For example:
foo(x: 1, y: 2)

# parses to:
{:foo, [], [[{:x, 1}, {:y, 2}]]}

# as opposed to:
{:foo, [],
 [[{:{}, [], [:x, 1]},
   {:{}, [], [:y, 2]}]]}

This makes it trivial to use keyword lists as options in macros, but also means that code processing an AST has to handle two forms of tuple. This is only one example of where the default AST can be cumbersome, but there are many situations where complex pattern matching, guards, or even metadata inspection are required to precisely differentiate syntax.
Sourceror, for instance, has a long standing issue for an enriched AST.
Additional Considerations

The perhaps obvious alternative is to transform Elixir AST into whatever format you want after the fact. This has two downsides that I can think of:

It is slower to parse, walk, and transform than it would be to parse and output the desired result in one shot.
There is additional metadata/context during parsing that is not included in the Elixir AST but that could be valuable. As a concrete example: when parsing Foo.Bar.\nBaz (note the newline), it's not possible to determine which line Bar occurs on without inspecting the source, but with token data, it would be.

It could be valuable to allow this or another hook to maintain and return an accumulator as well. This might be used to collect lint violations (in additional to parse errors). Based on this comment, it seems like you're already planning to return an accumulated value in addition to the parse result.
I expect, if implemented, parsing in the default case would be measurably slower due to the overhead of the additional call whenever a node is being constructed. I'm not sure what an acceptable amount of performance loss is, but I acknowledge that there is a line somewhere. (My gut says something like 1.1-1.2x would be acceptable, while 2x would almost certainly not be.)

Hi, sorry I've been off the computer for a while due to a back issue, just getting back in.
I'll give this a thorough read this week and reply.

@mhanberg Zero worries! This is low prio. Feel better.

@zachallaun I think the premise is reasonable, not entirely sure how it would look off the top of my head.
Naively, I think you could wrap every line that constructs a node with a function that invokes either the node_encoder or does the default behavior. There are probably some places where the AST is being changed in different places after its constructed, which might make it difficult.
Please submit a spike whenever you get some time, it would be helpful to see what it might look like. It's entirely possible that a pluggable encoder still won't be able to achieve the desire you have, so it'd be good to spike out a more intricate case.

As a concrete example: when parsing Foo.Bar.\nBaz (note the newline), it's not possible to determine which line Bar occurs on without inspecting the source, but with token data, it would be.

Side note, this in particular could potentially be upstreamed to the core yecc parser, and then I could mimic the behavior into Spitfire.

authors: mhanberg zachallaun

repo: elixir-tools/spitfire


text:
url bbcode

maybe this bug?
Example:
http://habrahabr.ru/search/?target_type=posts&q=[perl6]&order_by=date
not parse this part: [perl6]&order_by=date

You mean the "autolinking"? (i.e. you put the url in the message and it converts into a link?)

yes

Then it's one of those "impossible to fix bugs without rewriting a huge chunk of code" (and even then it wouldn't be that easy).
The opening bracket is recognized as starting bbc and the text is split at that point. The part before is autolinked, the part after is parsed in the next cycle of the loop.
Determine if the [ is a starting tag or not beforehand is impossible at the moment, we can know only after the whole processing has been done, but when the processing is done, the previous chunk of text was already parsed (and the autolink created). So it's really impossible to fix... :disappointed:

repo: elkarte/Elkarte


text:
Add option to change styling

If you have a lot of classes the html looks very busy and cluttered. It would be nice if there was an option to change the layout. Instead of a background color maybe a border-bottom color or something like that.

@joostclevis
Sorry. I didn't notice your message.
I'll check.

@joostclevis
You can set a custom style in the extension settings.
Also, If there are classes you do not need, set enabled to false.
https://github.com/ellreka/tailwindcss-highlight#configs
Example:
  "tailwindcss-highlight.configs": {
    "padding": {
      "enable": true,
      "regex": "(?<=[:`'\"\\s])(|-)p(|t|b|r|l|x|y)-[^`'\"\\s]+",
      "options": {
        "backgroundColor": "",
        "borderWidth": "0 0 3px 0",
        "borderStyle": "solid",
        "borderColor": "rgba(187, 196, 136, 1)",
        "color": "currentColor"
      }
    },
  }

authors: ellreka joostclevis

repo: ellreka/tailwindcss-highlight


text:
Processing files one by one results in huge bundle size

At the moment it looks like elm-webpack-loader is processing elm sources one by one, feeding results into webpack. Then it's possible to require() and use elm modules as they were normal JS modules.
In situation where each elm module is mini "application" on it own it leads to rapid growth of bundle size (by ~200-400kb per module uncompressed, ~40kb compressed).
Is there any way to make it process all modules as a whole and after that require() just one module to get Elm object containing all those modules. Not only it is more convenient to have all elm stuff in one place, but that would solve problem with resulting bundle size. As a workaround, I compile my modules with elm-make and then let webpack pick up result of compilation as ordinary js, but there must be better way...
Here's fork of elm-webpack-starter repository that illustrates the issue. You can add more MainX modules and watch bundle size grow. It is impossible to use just one module with entry point as there must be multiple independent Elm applications each replacing corresponding react component.

Isn't this more or less a duplicate of #42?
FWIW, I worked around this limitation by reviving PR #68 (updating and extending it, see this tag in my fork of elm-webpack-loader). Then, in the actual project, I gather all the main Elm modules and pass them via the modules option to the elm-loader. Finally, in the index.js, I require one arbitrary Elm module to trigger the elm-webpack-loader, but I actually get an object which contains all Elm modules that had been specified as modules in the webpack.config.js. I think this is quite close to what @quetz is asking for.
However, the whole business with the module option feels quite alien in a webpack setting. Ideally, it would be possible to just require multiple Elm main modules in your application code and make elm-webpack-loader smart enough to call node-elm-compiler just once,  passing all modules, so that the Elm runtime is only included once.
In #42, @eeue56 says in this comment and this comment that he has some ideas about this - but if i understand the comments correctly, he has a different solution in mind then I outlined above.
I'd be quite willing to do the work that is required for this and put together a PR but I'm not sure which solution would be the best for elm-webpack-loader.

Implemented and released 4.4.0: https://github.com/elm-community/elm-webpack-loader#files-default---path-to-required-file

repo: elm-community/elm-webpack-loader


text:
[localstorage] build data visualization elements for local data

This would inform users about their own usage behavior as well as give us a way of showing them the data that's being kept about them.

Related: https://github.com/elmsln/lrnwebcomponents/pull/263

PR merged, time to play...

repo: elmsln/HAXcms


text:
PaymentHash is not saved in the Invoice despite being part of the Invoice struct

Should it be added here? https://github.com/elnosh/gonuts/blob/main/wallet/wallet.go#L206

Hey, thanks for raising this. I'm using that Invoice struct for both wallet and mint (which is probably confusing) and was using the payment hash only in the mint. But yeah, it can be added there.

authors: elnosh rolznz

repo: elnosh/gonuts


text:
Implement rail station items from latest update

Following items are currently not within the local database.
Details see in the Astroneer wiki: https://astroneer.fandom.com/wiki/Rail_Station

ACC:

The items should be added within the database
The items can be selected within the companion app

Hello. I already partially implemented this here https://github.com/matco/astroneer/commit/00d74ea50cabceebc344534eaad1c70133417f8b. I'm just missing high quality images of the items.

For the record, I merged this commit in my master branch, even without the high quality images (see here https://github.com/matco/astroneer/commit/2ba669d4eabccd3b3f0b946f37af58774fd35fe3)

Thanks for the headsup, have seen it already. Golnna update my fork.

authors: elonmir matco

repo: elonmir/astroneer

license: Unlicense


text:
Use YAML for config files

The syntax is much easier to read and write without fucking it up.

While you're at it, the default db port should be the same as the default Docker Influx port (rather than localhost), if that's our recommendation.

The port is actually the same if you run it with the recommended settings. What I have done in the past is to add a Makefile that creates/starts the container so we don't have to remember which flags are necessary.

authors: adamrothman elsehow

repo: elsehow/moneybot


text:
Support non-BTC starting balances

Running a backtest with starting balances {'ETH': 1.0} doesn't simulate any trades. It's easy enough to convert everything into BTC before running moneybot, but we should let people start with whatever they have.
To reproduce this, set your starting balances as above in examples/backtest.py and run a backtest with the log level set to DEBUG:
python3 examples/backtest.py -c config.yml -s buffed-coin -l DEBUG

You won't see any log lines starting with "Simulating trade:" – compare this to what you get starting with BTC, which has many trades.

Strategy::initial_proposed_trades assumes starting balance is entirely in "fiat" which seems like the thing we need to change.

One solution might be to think less about trades to execute, and more about what distribution of assets we want. In the domain logic of the index fund, that's really what we care about. Of course, that would be a fairly significant refactor....
So, an intermediate hack would just be to check that we have a sufficiently diversified portfolio (in the context of our example strategies, that we have at least some balance of all the coins on Polo).


text:
Add serde attribute rename="Location" to  MPD.locations field

https://github.com/emarsden/dash-mpd-rs/blob/0e543c4a0fba70a5d32bc5602b02922085fab913/src/lib.rs#L1657
The location tag in the dash schema is "Location" but in the MPD struct the field name is "locations".
The field is missing
#[serde(rename = "Location", default)]

Fixed, thanks!

repo: emarsden/dash-mpd-rs


text:
chore(@embark/geth): Add back DevTxs

Add back DevTxs.
DevTxs sends a zero-value tx to push through any pending txs that may get stuck with geth while in —dev mode.
Converted the legacy code in to typescript.

@michaelsbradleyjr - updated the package.json.

Agreed with @jrainville re: making the message more clear and not displaying it when not in dev mode; otherwise good to go, great work!

authors: emizzle michaelsbradleyjr

repo: embark-framework/embark


text:
STM32 SimplePwm: Fix regression and re-enable output pin

PR #2499 implemented timer hierarchy, but removed enable_outputs() from trait CaptureCompare16bitInstance and from SimplePwm.
This functions is required for advanced timers to set bit BDTR.MOE and to enable the output signal.

I left comments in Issue #2409 with my understanding what happened.
It's still unclear to me, whether this approach fits the new timer hierarchy.

Ah, I'm terribly sorry for this mess. I didn't notice that SimplePwm is implmented on TIM_GP16 at that time, thus adding enable_output() to TIM_1CH_CMP is useless for this situation.
You approach is correct on both old and new timer hierarchy. It requires a empty implement enable_output for TIM_GP16, and enable MOE inside the method for TIM_1CH_CMP / TIM_2CH_CMP / TIM_ADV.

Thanks for your fast response and don't worry about the mess.
It's easy to miss the output enable behavior between basic and advanced timers and I only noticed, because I use it in my project.
I can squash the commits, if you agree to the current state.

I can squash the commits, if you agree to the current state.

Yeah! It looks good to me!
And I also test PWM output on my dev board with TIM1(ADV), TIM15(2CH_CMP), TIM16(1CH_CMP), they all output correct waveform.

Thanks. I squashed the commits.

authors: eZioPan jr-oss

repo: embassy-rs/embassy


text:
Create a cargo workspace with testing instructions.

Not very useful, I know, but I'm interested in contributing to this project further.
I might send a couple of PRs similar to this one while taking a look around. Feel free to let me know if that's inappropriate :)

You can't mix different target architectures in the same workspace, so I'm not sure if this is going to work :/

Not sure I 100% follow. Are there cases where you are interested in building separate crates for different targets? And why wouldn't the --target flag work?

It's common for a Rust embedded library to be used in different targets. In this case, cargo workspace won't work. It doesn't support per crate target and per crate features.

It's common for a Rust embedded library to be used in different targets. In this case, cargo workspace won't work. It doesn't support per crate target and per crate features.

Sorry, I don't intend to be rude, but you just repeated Ulf without pointing to any definitive sources.
You can place Cargo.tomls in each crate if workspace commands error due to incorrect target triples. cargo check and cargo test do already work without any issues, and I've not changed how the ci.sh script invokes each example with an explicit target tripple.

You can place Cargo.tomls in each crate if workspace commands error due to incorrect target triples. cargo check and cargo test do already work without any issues, and I've not changed how the ci.sh script invokes each example with an explicit target tripple.

That makes no difference if you use cargo check -p crate_name on each sub-crate in workspace, AND it will break rust analyzer, since different crates may require different version of same dependency, which cannot be resolved by cargo right now. Some related discusses can be found here, here and here. Monorepo is more preferred way by now.

My bad, I meant to write config.toml.  In fact, that is exactly what the closed issue in the second link you sent recommends. So just to clarify, you aren't referring to an issue cargo but an issue in rust-analyzer? In that case https://github.com/rust-lang/rust-analyzer/issues/10021 is the issue that shold be tracked.

since different crates may require different version of same dependency, which cannot be resolved by cargo right now.

Also, this is very very wrong.

My bad, I meant to write config.toml. In fact, that is exactly what the closed issue in the second link you sent recommends. So just to clarify, you aren't referring to an issue cargo but an issue in rust-analyzer? In that case rust-lang/rust-analyzer#10021 is the issue that should be tracked.

The tracking issue is: https://github.com/rust-lang/cargo/issues/9406

Involving config.toml requires use cargo check -p crate_name for each crate, which has no advantage comparing with cargo check --manifest-path path.

Awesome, thanks. Now I understand where you're coming from. I tried this in a toy example, and you're right, cargo doesn't seem to build with per package targets.

The tracking issue is: rust-lang/cargo#9406

Sweet, thank you!

authors: HaoboGu gibbz00 lulf

repo: embassy-rs/trouble


text:
feature request: Reddit Post data type

Should be the post only, but optionally also the comments. That's the reason the web page format won't cut it.
I think for small quantities, the reddit API can be used without auth, we could leave auth up to the user via env vars.

Reddit has 70+ million daily users as of 2024 and contains incredible amount of data
Anyone interested to add this data source to embedchain?

authors: cachho slavakurilyak

repo: embedchain/embedchain


text:
Fix a problem with the styleguide not rendering properly

This fixes a problem with the styleguide rendering a blank page. The problem occurs if you install ember-cli-tailwind inside a project which has the template-only-glimmer-components feature enabled. This changes the way the template is handled. {{namedArgument}} is undefined, unless you use the {{@namedArgument}} syntax.
Should fix #63

It seems I misunderstood the problem. etw/module-section isn't a template only glimmer component, it's a regular component without a .js file 😁. Because our application has the optional template-only-glimmer-components enabled, this behaves different in our app.
rwjblue recommends adding a .js file for the component instead.

Added a .js file for the component instead.

Easy peasy! Thanks for the PR :)

authors: Windvis samselikoff

repo: embermap/ember-cli-tailwind


text:
add images for mesos intro deck

These will be referenced by a draft markdown deck to be added soon
DCO statement
5 of these images in this check-in are original compositions composed by me. the images incorporate public registered trademarks in a way that do not imply sponsorship, or origin of the presentation by the trademark owner.
The other two images are screen captures of a tiny portion of an original work that constitutes fair use by reason of: small portion of content, purpose and character of the use, and lack of negative impact on the market for the original work.
Signed-off-by: [Steven Wong] [steven.wong@emc.com]

Looks great to me! Looking forward to more contributions to this workshop.

authors: cantbewong jonasrosland

repo: emccode/training


text:
Move to zoneinfo instead of pytz

Is your feature request related to a problem? Please describe.
Django 4.0 included a move to zoneinfo instead of Pytz for timezone in datetime/time. Pytz support will be totally remove in Django 5.0
Describe the solution you'd like
Currently a transitional settings USE_DEPRECATED_PYTZ is used to keep pytz usage since we have Django<4.0 support that don't have the zoneinfo support.
We should drop this settings and move to zoneinfo usage instead of pytz everywhere it is directly used.
Describe alternatives you've considered
Including a support for both libraries would be too difficult to manage.

Also now Django>=4.0 there is this warnings:

The django.utils.timezone.utc alias is deprecated. Please update your code to use datetime.timezone.utc instead.

And

The USE_L10N setting is deprecated. Starting with Django 5.0, localized formatting of data will always be enabled. For example Django will display numbers and dates using the format of the current locale.

These should not be difficult to fix but only when dropping Django<4.0 supports.

Done with #34

repo: emencia/django-blog-lotus


text:
progress bars ui

#187
#303

https://github.com/emerald-geomodelling/EmeraldInterpret/issues/187
https://github.com/emerald-geomodelling/EmeraldInterpret/pull/303

https://github.com/emerald-geomodelling/EmeraldInterpret/issues/187
https://github.com/emerald-geomodelling/EmeraldInterpret/pull/303

repo: emerald-geomodelling/BokehGarden


text:
require('net') remains an empty Object

let net = require('net-browserify');

let bundler = browserify(
	{
		entries      : path.join(__dirname, 'foo.js'),
		plugin       : [ net ]
	})

In the source file foo.js:
let net = require('net');

console.log(net);

However, the generated bundle file still prints an empty Object.
Do I miss something?

broserify 2.14.0

OK, got it working by adding in package.json:
"browser": {
  "net": "net-browserify"
}

I've never understood what browserify plugins are...

repo: emersion/net-browserify


text:
UDT buffer error on OS X possibly due to oversized UDP receive buffer

I'm getting an error when calling socket.listen() on OS X:
UdtError {
  err_code: 1003,
  err_msg: "Connection setup failure: unable to create/configure UDP socket: No buffer space available."
}

UNLESS I specify
sock.setsockopt(UdtOpts::UDP_RCVBUF, 5590000i32);

then everything works like magic.

Yeah, this matches what I've seen myself.   For example: https://github.com/eminence/udt-rs/blob/master/tests/test.rs#L11-L15
I admit I don't know why this is necessary

I found this post on the UDT mailing list that talks about this issue:
Yes, this is a known issue too (I should have add a known issue list...)

The reason is that UDT tries to allocate a rather large socket buffer
(setsockopt) that OS X does not support. On Linux or Windows, they will
set the socket buffer to the maximum system value; however, OS X will
return error.

So the solution is, you can either change your system parameter to allow
larger socket buffer size (at least 20MB), or set UDT option (UDT_SNDBUF
and UDT_RCVBUF) to smaller values (e.g., 64KB). See the commented
setsockopt lines in appserver and appclient for examples.

Since this is a known UDT issue, I'm going to find a way to document this and then close this issue.
(As you seem to be the only user of udt-rs at the moment, I'm happy to take suggestions regarding the best/most visible way to document this :smile: )

I wonder if this is something that udt-rs can do by default using some platform-specific code when built for OS X?

Anyone work out a fix for this?

@winkmichael iirc, the workaround was to set the sockopt as mentioned in that first issue description.

authors: eminence mcginty winkmichael

repo: eminence/udt-rs


text:
Prevent update script from overwriting a specific file

I would like to keep my "ts3server_startscript.sh" because i am using the ts3server.ini to configure my server instance. Is this supported?

Hi, I'm not sure if this is a good idea as this file might change in the future and not updating it might break the entire installation.
However, removing the write permissions from this file will probably prevent tar from overwriting it (the scipt uses tar to extract the new files and overwrite old files with the same name): chmod -w ts3server_startscript.sh


text:
Pawns equip, drop and forbid vanilla EMP or smoke weapons

Greetings.
My pawns don't want to carry an EMP-grenades or the same type of launchers, they equip and drop it immediately. Outfit policy allow only EMP (both or either), no hunters/brawlers, no modified weapons or other weapon loadout mods in game. It happens no matter what mod setting I use. The same story with smoke weapons.
I searched in code, but I can't find a propper solution, could you please help me out?
It seems like the mod restrict equiping null-damage weapon (bool compareGuns) or compares range weapons with fists (public static Thing bestGunForPawn). Im not sure, changing some rules didn't help.

The issue should be fixed in d737751
It was the vanilla jobdriver that unequipped the weapon so I added an override for it.
Seems to work as intended now, thanks for the report!

Good news for me! Now it's all fine, many thanks!


text:
show user reddit error message on login failed

usually either rate limit or wrong pw

No longer an issue now it's using oauth, log in happens in the browser

repo: emmaguy/wear-notify-for-reddit


text:
HTTP API Auth dont work

Environment

OS: Windows
Erlang/OTP: R18/7.3
EMQ: 2.0.7

Description
I enabled the plugin:
emq_auth_http	2.0.7	Authentication/ACL with HTTP API
but I cant register any request against my api auth endpoint.
emq_auth_http.conf
##--------------------------------------------------------------------
## HTTP Auth/ACL Plugin
##--------------------------------------------------------------------

## Variables: %u = username, %c = clientid, %a = ipaddress, %P = password, %t = topic

auth.http.auth_req = http://127.0.0.1:3000/mqtt/auth
auth.http.auth_req.method = post
auth.http.auth_req.params = clientid=%c,username=%u,password=%P

auth.http.super_req = http://127.0.0.1:3000/mqtt/superuser
auth.http.super_req.method = post
auth.http.super_req.params = clientid=%c,username=%u

## 'access' parameter: sub = 1, pub = 2
auth.http.acl_req = http://127.0.0.1:3000/mqtt/acl
auth.http.acl_req.method = get
auth.http.acl_req.params = access=%A,username=%u,clientid=%c,ipaddr=%a,topic=%t

auth.http.acl_nomatch = deny

It works. I misunderstood the concept.

repo: emqtt/emqttd


text:
Add protobuf

This should fix https://github.com/emscripten-forge/recipes/issues/184

Also fixes #455

Looking at the CI logs, I'm curious if anything got built at all?
2023-05-13T14:24:14.5757315Z Downloading source
2023-05-13T14:24:14.5757618Z
2023-05-13T14:24:14.5760559Z Source cache directory is: /home/runner/micromamba-root/envs/ci-env/conda-bld/src_cache
2023-05-13T14:24:14.5762722Z INFO:conda_build.source:Source cache directory is: /home/runner/micromamba-root/envs/ci-env/conda-bld/src_cache
2023-05-13T14:24:14.5764131Z Downloading source to cache: protobuf-4.22.3_23452f2fde.tar.gz
2023-05-13T14:24:14.5765115Z INFO:conda_build.source:Downloading source to cache: protobuf-4.22.3_23452f2fde.tar.gz
2023-05-13T14:24:14.5765952Z Downloading https://files.pythonhosted.org/packages/e2/86/44a1e4990a81cb4248a2091a182bb76a6417fddcaff560ceb6b44eb05c55/protobuf-4.22.3.tar.gz
2023-05-13T14:24:14.5767218Z INFO:conda_build.source:Downloading https://files.pythonhosted.org/packages/e2/86/44a1e4990a81cb4248a2091a182bb76a6417fddcaff560ceb6b44eb05c55/protobuf-4.22.3.tar.gz
2023-05-13T14:24:14.7522710Z INFO:conda_build.source:Success
2023-05-13T14:24:14.7522967Z Success
2023-05-13T14:24:14.9200229Z Extracting download
2023-05-13T14:24:14.9200753Z
2023-05-13T14:24:14.9201882Z Preparing environment for protobuf
2023-05-13T14:24:14.9202418Z
2023-05-13T14:24:14.9210015Z
2023-05-13T14:24:14.9210374Z Starting build for protobuf
2023-05-13T14:24:14.9210627Z
2023-05-13T14:24:14.9228184Z source tree in:
2023-05-13T14:24:14.9228974Z /home/runner/micromamba-root/envs/ci-env/conda-bld/protobuf-0_1683987853545/work
2023-05-13T14:24:14.9720104Z number of files: 0
2023-05-13T14:24:14.9720751Z Fixing permissions
2023-05-13T14:24:14.9721215Z
2023-05-13T14:24:14.9721409Z Adding files for protobuf
2023-05-13T14:24:14.9721767Z
2023-05-13T14:24:14.9727588Z ATTENTION: No files added in target protobuf
2023-05-13T14:24:14.9730408Z
2023-05-13T14:24:14.9730415Z
2023-05-13T14:24:15.2078709Z Copying package to conda-build croot.  No packages otherwise alongside yours will be available unless you specify -c local.  To avoid this warning, your package must reside in a channel structure with platform-subfolders.  See more info on what a valid channel is at https://conda.io/docs/user-guide/tasks/create-custom-channels.html
2023-05-13T14:24:15.2080487Z WARNING:boa.core.test:Copying package to conda-build croot.  No packages otherwise alongside yours will be available unless you specify -c local.  To avoid this warning, your package must reside in a channel structure with platform-subfolders.  See more info on what a valid channel is at https://conda.io/docs/user-guide/tasks/create-custom-channels.html
2023-05-13T14:24:15.2954270Z INFO :: Time taken to mark (prefix)
2023-05-13T14:24:15.2954855Z         0 replacements in 0 files was 0.00 seconds
2023-05-13T14:24:15.2956052Z TEST START: /home/runner/micromamba-root/envs/ci-env/conda-bld/emscripten-32/protobuf-4.22.3-h51e9701_0.tar.bz2
2023-05-13T14:24:15.2956656Z Nothing to test for: /home/runner/micromamba-root/envs/ci-env/conda-bld/emscripten-32/protobuf-4.22.3-h51e9701_0.tar.bz2
2023-05-13T14:24:15.2956906Z
2023-05-13T14:24:15.2956930Z
2023-05-13T14:24:15.2956935Z
2023-05-13T14:24:15.2957230Z                   Output: protobuf 4.22.3 BN: 0
2023-05-13T14:24:15.2957480Z                             Variant:
2023-05-13T14:24:15.2958579Z                              Build:
2023-05-13T14:24:15.2958831Z
2023-05-13T14:24:15.2959188Z              ╷                     ╷          ╷       ╷
2023-05-13T14:24:15.2959755Z   Dependency │ Version requirement │ Selected │ Build │ Channel
2023-05-13T14:24:15.2960153Z  ════════════╪═════════════════════╪══════════╪═══════╪═════════
2023-05-13T14:24:15.2960462Z              ╵                     ╵          ╵       ╵
2023-05-13T14:24:15.3044075Z Test recipe: {'package': {'name': 'protobuf', 'version': '4.22.3'}, 'build': {'number': 0}, 'source': [{'url': 'https://files.pythonhosted.org/packages/e2/86/44a1e4990a81cb4248a2091a182bb76a6417fddcaff560ceb6b44eb05c55/protobuf-4.22.3.tar.gz', 'sha256': '23452f2fdea754a8251d0fc88c0317735ae47217e0d27bf330a30eec2848811a'}], 'steps': [{'package': {'name': 'protobuf', 'version': '4.22.3'}}], 'recipe_file': '/tmp/tmp1fhmipc4/recipes/recipes_per_platform/protobuf/recipe.yaml', 'output_names': {'protobuf'}} in work_dir: /home/runner/work/recipes/recipes
2023-05-13T14:24:15.4382145Z Post job cleanup.

Thanks @proppy.
The recipe follows the one from Pyodide available here: https://github.com/pyodide/pyodide/blob/main/packages/protobuf/meta.yaml, which also quite minimal.
But yeah we can try adding tests in a separate PR for example to check imports, to make sure it's built correctly.

authors: jtpio proppy tylere

repo: emscripten-forge/recipes


text:
ENYO-6120: Req: hides border-bottom of the Header

Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[ ] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
There're some cases that cannot use Header because of under line of that component.
Actually, GUI of some applications want to use Header without underline.
Resolution
Added prop hideLine to hide border-bottom in the Header component.
Links
ENYO-6120

Oops, forgot root CHANGELOG.  Fixed.

repo: enactjs/enact


text:
Can I integrate on Angular Frontend?

I want to read cert information which uploaded by user from input type file.  Will I able to read at over there? If yes can you help me out how.
Currently while doing I am facing issue of module not found.
Module not found: Error: Can't resolve 'x509'

You can. You need to import x509.js.

I followed readme step. its throwing error of fs, ___dirname etc not found.

can you provide list which dependency required. I appreciate if you can share steps for angular

You can include this dependency like any javascript dependency. No special steps for Angular are required

authors: Rush shabbir-dhangot


text:
Add Model and Queryset .all() as_dict support

As-Is:
ORM model does not support its own dictionary serialize method
To-be:
ORM model can be serialized to dict like this:
await User.objects.get(id=1).as_dict()
or Queryset.all() that returns ORM model objects' list can be serialized to dict like this:
await User.objects.all().as_dict()

I run lint script

Hello, was this truly implemented?
I see that the pull request was closed, but this doesn't work.
orm 0.3.1

authors: YuriFontella blue-hope

repo: encode/orm


text:
Implement organization API to get base fields

https://data.crunchbase.com/reference#core-entity-collections

Endpoint: https://api.crunchbase.com/api/v4/entities/organization/#{permalink}

Create basic structure
Request, Response
Client
Model

/spend 5h


text:
Initial Open Source Documentation

[x] Update README
[ ] Create Setup Guide/Tutorial/Example - this can be a part from the README, not necessarily a different doc; it must include details how to use the nuget packages and get the product running; part #56
[x] Ensure API Documentation is set up and correct
[ ] Clean the Doc site from non Endatix stuff
[ ] Final documentation verification

Note on the API documentation:

Some changes in the descriptions are made as a part of #72
There are errors on the API Reference section, described in https://github.com/endatix/corp-website/issues/44

repo: endatix/endatix


text:
Add support for JavaScript & Add 2 new products

🚩 Context
I have created 2 PRs on the endoflife.date repo:

[New Product] Add RDS Postgres
[New Product] Add RDS MySQL

In order to collect the data necessary for these PRs I used a scraping script. This script is located over in a repo under my account here. This script collects all minor and major versions data available. However, after a discussion with the contributors, only the major version will be used. I think the script and the data it collects can fit nicely into this repo. The major and minor versions are included.

An important difference in syntax

MySQL (and even PostgreSQL before version 10) uses a uncommon versioning syntax of x.y as major. Meaning x.y.z is the minor.
🏗 Code
This is the first JavaScript file added to this repo. For this reason I needed to edit the github actions. I followed as closely as I could to how Python is ran here.

I keep the dependencies on the root
I allow for running multiple scripts

I am using a package called npm-rull-all which can run scripts in parrallel. Usage for this can be read about here
The basics of it is that you will add a new line in package.json for running any new scripts "NAME_1": "node ./src/ANY_FILE.js" and then once that line is added you can append it onto the start script like so: "start": "run-p NAME_1 NAME_2"

I didn't commit the json output. If you're curious how it will look here they are

amazon-rds-postgresql.json
{
  "8.0.32": "2024-02-01",
  "8.0.31": "2023-11-01",
  "8.0.30": "2023-09-01",
  "8.0.28": "2023-06-01",
  "8.0.27": "2023-04-20",
  "8.0.26": "2023-04-20",
  "8.0.25": "2023-04-20",
  "8.0.23": "2023-04-20",
  "5.7.41": "2023-10-01",
  "5.7.40": "2023-10-01",
  "5.7.39": "2023-09-01",
  "5.7.38": "2023-06-01",
  "5.7.37": "2023-06-01",
  "5.7.36": "2023-04-20",
  "5.7.34": "2023-04-20",
  "5.7.33": "2023-04-20",
  "8.0": "2026-04-01",
  "5.7": "2023-10-01",
  "5.6": "2022-03-01"
}

amazon-rds-mysql.json
{
  "10": "2023-04-01",
  "11": "2023-11-01",
  "12": "2024-11-01",
  "13": "2025-11-01",
  "14": "2026-11-01",
  "15": "2027-11-01",
  "15.2": "2024-02-01",
  "14.7": "2024-03-01",
  "14.6": "2024-01-01",
  "14.5": "2023-11-01",
  "14.4": "2023-09-01",
  "14.3": "2023-08-01",
  "14.2": "2023-03-20",
  "14.1": "2023-03-20",
  "13.10": "2024-03-01",
  "13.9": "2024-01-01",
  "13.8": "2023-11-01",
  "13.7": "2023-08-01",
  "13.6": "2023-03-20",
  "13.5": "2023-03-20",
  "13.4": "2023-03-20",
  "13.3": "2023-03-20",
  "12.14": "2024-03-01",
  "12.13": "2024-01-01",
  "12.12": "2023-11-01",
  "12.11": "2023-08-01",
  "12.10": "2023-03-20",
  "12.9": "2023-03-20",
  "12.8": "2023-03-20",
  "12.7": "2023-03-20",
  "11.19": "2023-11-01",
  "11.18": "2023-11-01",
  "11.17": "2023-11-01",
  "11.16": "2023-08-01",
  "11.15": "2023-03-20",
  "11.14": "2023-03-20",
  "11.13": "2023-03-20",
  "11.12": "2023-03-20",
  "10.23": "2023-04-17",
  "10.22": "2023-04-17",
  "10.21": "2023-04-17",
  "10.20": "2023-03-20",
  "10.19": "2023-03-20",
  "10.18": "2023-03-20",
  "10.17": "2023-03-20",
  "9.6": "2022-04-30"
}

Thanks a lot for your contribution. I didn't like the huge dependency import that this PR added (no fault of yours, jsdom and npm-run-all have heavy footprints), so I gave a shot at rewriting it in Python to avoid the same.
I've committed the result (#86) with your email for authorship info, since it's pretty much the same code.

Agree with you @captn3m0 on this one. And I know you wanted to make things quite open regarding the language used, but I find it easier to stick with Python if we can.
Closing this PR in favor of #86.

authors: CodaBool captn3m0 marcwrobel

repo: endoflife-date/release-data


text:
feat(issuer-api): allow to query certs by generationEnd frame

For 24/7 applications we can have more than 10k certificates. It would be actually really nice to have a way to query only for certificates from given time-span, instead for querying for all of them.

@soanvig could you add some context on why this change is necessary?

I think we could but I'm not sure what may be useful

I think filters by deviceId, generationStartTime (similar to endtime), and creationTime would be useful.

I think filters by deviceId, generationStartTime (similar to endtime), and creationTime would be useful.

done!

authors: JosephBagaric soanvig

repo: energywebfoundation/origin


text:
Doubledown: In round 2, doubledown phase sometimes skips all players except for the first player if they say no

Need to reproduce. Basically Johnny had the chance to say yes or no and selected no. but it didn't get a chance for anyone else to go.

Was just testing this, unable to repro this exact issue, but I had a player asked twice in one round whether to double-down.

authors: jpailthorpe mattwbenson


text:
single page form in pages mode throws error

TypeError : Cannot read property 'add' of undefined

Also no submit button shown

repo: enketo/enketo-core


text:
Update scalafmt-core to 3.7.1

Updates org.scalameta:scalafmt-core from 2.7.5 to 3.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #134.


text:
Enowars8

We should at least cherry pick the general improvements in this branch

Changes not related to the ENOWARS8-Theming shoud've been cherry picked in commit:
https://github.com/enowars/EnoCTFPortal/commit/da660a47070cceb7c47230e3d2a58e5fc2e8a3e7

PR can probably be closed since we salvaged what we need from here

authors: MMunier ldruschk

repo: enowars/EnoCTFPortal


text:
Support for WITH TOTALS

The WITH TOTALS query runs fine but I do not see the totals output anywhere. Is it possible to support this in Metabase?

Hi @eni9889 thanks for your question? Could you please provide an example query and let me know which visualization you have in mind? Thank you 👋

repo: enqueue/metabase-clickhouse-driver


text:
Should we use production bucket and inventory?

I noticed some links refer to:

The aloft bucket, which will be removed. The aloftdata bucket should be used

The aloft-inventory bucket (with subfolder aloft/aloft-hdf5-files-inventory/). This bucket is on UAT. I wonder if the inbo-aloft-prod-eu-west-1-inventory bucket (with subfolder /aloftdata/aloftdata-hdf5-files-inventory/) should be used instead or if that will break tests.

For the 'default' environmental variable when not provided (os.environ.get("DESTINATION_BUCKET", "aloft")) I would not use the prd version but the dev/uat bucket name and sns channels

So that would then be inbo-aloft-uat-eu-west-1-default

For the s3_url_h5 I think it is ok to use the aloftdata  prd bucket name

Ok

In the Examples sections of the docstrings I would sue the aloftdata prd name

Ok

For the tests/ files it should not matter as the S3-bucket is mocked for the tests. So you can choose whatever name you prefer but at the moment some tests did fail due to the name adjustments in the tests (you also adjust the dummy_manifest.json file, https://github.com/enram/vptstools/blob/main/tests/data/inventory/dummy_manifest.json#L9)

I will then use aloftdata-mocked

Updated, but some tests are still failing, so I probably changed something I shouldn't have?

so I probably changed something I shouldn't have?

Main issue was that the default env vars were used in the end2end tests of the CLI commands instead of the dummy-aloftdata and dummy-inventory. I adjusted this and made sure other occurrences of the bucket name use the dummy-aloftdata naming.

authors: peterdesmet stijnvanhoey

repo: enram/vptstools


text:
case of fails to match a constant string against a string coming from JS

Repro showing the issue:
from Standard.Base import all
import Standard.Base.Errors.Illegal_Argument.Illegal_Argument

get_required_field key js_object = case js_object of
    _ : JS_Object -> js_object.get key if_missing=(Error.throw (Illegal_Argument.Error "Missing required field `"+key+"` in "+js_object.to_display_text+"."))
    _ -> Error.throw (Illegal_Argument.Error "Expected a JSON object, but got "+js_object.to_display_text+".")

foo json =
    x = get_required_field "type" json
    IO.println (x == "aws_auth")
    IO.println ("aws_auth" == x)
    v1 = case x of
        "aws_auth" -> "OK"
        other -> "not ok: "+other.to_display_text

    v2 = case ""+x+"" of
        "aws_auth" -> "OK"
        other -> "not ok: "+other.to_display_text

    [v1, v2]

main =
    j = """
        { "type": "aws_auth" }
    IO.println <| foo j.parse_json

Actual behaviour
True
True
[not ok: aws_auth, OK]

While == works we can see that case of fails to match the constant.
However, when we concatenate "", the JS string gets converted into Enso Text and then the match successfully works.
Expected behaviour
The script above should yield:
True
True
[OK, OK]

I've already got a fix for this, so I'll put up a PR in a moment.

repo: enso-org/enso