text:
rcedit.exe failed with exit code 1. Fatal error: Unable to set icon

Electron packager doesn't accept my icon file even though it is in the right dimensions and format.
Icon.zip
PS C:\Users\abornst\Documents\ovt> electron-packager . CNTKVideoTagger --platform=win32 --icon=Icon.ico --arch=x64
Packaging app for platform win32 x64 using electron v1.6.2
rcedit.exe failed with exit code 1. Fatal error: Unable to set icon
PS C:\Users\abornst\Documents\ovt> electron-packager . CNTKVideoTagger --platform=win32 --icon=.Icon.ico --arch=x64
Packaging app for platform win32 x64 using electron v1.6.2
Wrote new app to C:\Users\user\Documents\ovt\CNTKVideoTagger-win32-x64

Thanks for filing an issue! In order to help you with your problem, we're going to need more information about it. In particular:

Console output when you run electron-packager with the environment variable DEBUG=electron-packager.

Please provide either a failing minimal testcase (with code) or detailed steps to reproduce your
problem. Using electron-quick-start is a good starting point.

Since the original issue reporter has not responded to the request for additional information in over two weeks, I'm going to assume that they either found the answer in another manner or decided not to pursue this issue. If I'm incorrect, they can respond with answers to the questions posed, and I'll reopen.

System
Windows 10 64bit
"asar": "^0.13.0",
"electron": "^1.7.5",
"electron-packager": "^8.7.2"
Problem
Same problem here. I cant understand what do you mean by

Console output when you run electron-packager with the environment variable DEBUG=electron-packager.

Anyway, here are all the logs.
running npm run build when "build": "electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite"
gives
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'build' ]
2 info using npm@3.10.10
3 info using node@v6.9.4
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle electron-tutorial@1.0.0~prebuild: electron-tutorial@1.0.0
6 silly lifecycle electron-tutorial@1.0.0~prebuild: no script for prebuild, continuing
7 info lifecycle electron-tutorial@1.0.0~build: electron-tutorial@1.0.0
8 verbose lifecycle electron-tutorial@1.0.0~build: unsafe-perm in lifecycle true
9 verbose lifecycle electron-tutorial@1.0.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;E:\ElectronTutorial\node_modules\.bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\libnvvp;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Users\windows\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Git\cmd;C:\Program Files\dotnet\;C:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\nodejs\;C:\Program Files\MiKTeX 2.9\miktex\bin\x64\;C:\Program Files\Java\jdk1.8.0_73\bin;C:\OpenCV-3.3.0-vc14\opencv\build\x64\vc14\bin;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin;C:\Program Files\CMake\bin;C:\Ruby24-x64\bin;C:\Users\windows\AppData\Local\Programs\Python\Python35\Scripts\;C:\Users\windows\AppData\Local\Programs\Python\Python35\;C:\Program Files (x86)\Microsoft VS Code\bin;C:\cuDNN;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v8.0\extras\CUPTI\libx64;C:\Program Files\Docker Toolbox;C:\Users\windows\AppData\Roaming\npm;C:\Program Files\MongoDB\Server\3.2\bin
10 verbose lifecycle electron-tutorial@1.0.0~build: CWD: E:\ElectronTutorial
11 silly lifecycle electron-tutorial@1.0.0~build: Args: [ '/d /s /c',
11 silly lifecycle   'electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite' ]
12 silly lifecycle electron-tutorial@1.0.0~build: Returned: code: 1  signal: null
13 info lifecycle electron-tutorial@1.0.0~build: Failed to exec build script
14 verbose stack Error: electron-tutorial@1.0.0 build: `electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid electron-tutorial@1.0.0
16 verbose cwd E:\ElectronTutorial
17 error Windows_NT 10.0.10240
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
19 error node v6.9.4
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error electron-tutorial@1.0.0 build: `electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite`
22 error Exit status 1
23 error Failed at the electron-tutorial@1.0.0 build script 'electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the electron-tutorial package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs electron-tutorial
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls electron-tutorial
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

However running electron-packager . --out=dist/win --platform=win32 --arch=x64 --asar=true --overwrite works absolutely fine.
E:\ElectronTutorial>electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite
Packaging app for platform win32 x64 using electron v1.7.5
rcedit.exe failed with exit code 1. Fatal error: Unable to set icon

I cant understand what do you mean by [debug instructions]

Run SET DEBUG=electron-packager before running the command on Windows.

Please don't paste output of npm run commands, they do not capture the command's stderr/stdout. (This is a long-standing NPM bug.)

Fatal error: Unable to set icon

If it's unable to set the icon, then one of the following is true:

The icon doesn't exist
The icon is corrupted
The icon isn't the correct dimensions
There's a bug in rcedit

I dont think this would be helpful but here you go.
favicon.ico is 256x256
E:\ElectronTutorial>SET DEBUG=electron-packager

E:\ElectronTutorial>electron-packager . --out=dist/win --platform=win32 --arch=x64 --icon=favicon.ico --asar=true --overwrite
  electron-packager Electron Packager 8.7.2 +0ms
  electron-packager Node v6.9.4 +4ms
  electron-packager Host Operating system: win32 (x64) +3ms
  electron-packager Packager Options: {"_":["."],"all":false,"deref-symlinks":true,"download":{"strictSSL":true},"overwrite":true,"prune":true,"quiet":false,"out":"dist/win","platform":"win32","arch":"x64","icon":"favicon.ico","asar":true,"dir":".","protocols":[]} +1ms
  electron-packager Target Platforms: win32 +4ms
  electron-packager Target Architectures: x64 +1ms
  electron-packager Inferring application name from name in E:\ElectronTutorial\package.json +14ms
  electron-packager Inferring appVersion from version in E:\ElectronTutorial\package.json +3ms
  electron-packager Inferring target Electron version from electron in E:\ElectronTutorial\package.json +5ms
  electron-packager Application name: electron-tutorial +1ms
  electron-packager Target Electron version: 1.7.5 +2ms
  electron-packager Ignored path regular expressions: [ '/node_modules/electron($|/)',
  '/node_modules/electron-prebuilt(-compile)?($|/)',
  '/node_modules/electron-packager($|/)',
  '/\\.git($|/)',
  '/node_modules/\\.bin($|/)',
  '\\.o(bj)?$' ] +3ms
  electron-packager Downloading Electron with options {"strictSSL":true,"platform":"win32","arch":"x64","version":"1.7.5"} +62ms
Packaging app for platform win32 x64 using electron v1.7.5
  electron-packager Creating C:\Users\windows\AppData\Local\Temp\electron-packager\win32-x64-template +299ms
  electron-packager Extracting C:\Users\windows\.electron\electron-v1.7.5-win32-x64.zip to C:\Users\windows\AppData\Local\Temp\electron-packager\win32-x64-template +18ms
  electron-packager Initializing app in C:\Users\windows\AppData\Local\Temp\electron-packager\win32-x64\electron-tutorial-win32-x64 from C:\Users\windows\AppData\Local\Temp\electron-packager\win32-x64-template template +2s
  electron-packager Ignored paths based on the out param: [ 'E:\\ElectronTutorial\\dist\\win' ] +4ms
  electron-packager Pruning modules via: npm prune --production +2s
  electron-packager Running asar with the options {} +5s
  electron-packager Renaming electron.exe to electron-tutorial.exe in C:\Users\windows\AppData\Local\Temp\electron-packager\win32-x64\electron-tutorial-win32-x64 +16ms
  electron-packager Running rcedit with the options {"version-string":{},"file-version":"1.0.0","product-version":"1.0.0","icon":"favicon.ico"} +15ms
rcedit.exe failed with exit code 1. Fatal error: Unable to set icon

If everything you say is accurate, then I'm inclined to believe that it's a bug in rcedit. Packager doesn't do anything except pass the icon path to rcedit, and it modifies the executable accordingly.

Related to https://github.com/electron/node-rcedit/issues/6

FWIW, I was seeing this same error when I tried building without an .ico file in the same directory as the .png specified in the config.
  "electronPackagerConfig": {
    "packageManager": "npm",
    "icon": "./src/assets/imgs/icon-1024.png"
  },

Reopen the thread maybe?

I'm not inclined to reopen this issue. This should not be a catch-all for a generic error message by rcedit (which needs to be more specific when possible). For the issue described by @positlabs, it would help to see what the electron-packager debug says is being passed to the rcedit module.

I confirm @positlabs's solution works.

I'm not seeing a solution there.

it's more of a workaround, sorry.

I'm not getting the exact same problem, but it seems pretty close. It's reported from electron forge:
An unhandled rejection has occurred inside Forge:
rcedit.exe failed with exit code 1. Cannot open icon file 's'

Not sure why the file is called 's'. When I try @positlabs' workaround (with an ico file that opens fine in paint at least, I get rcedit.exe failed with exit code 1. Reserved header is not 0 or image type is not icon for 's'.
We can build for windows on a mac, just not on windows due to the above. Does this seem like the same error? Or is it something else?

s is probably because I'm not good at C++ :disappointed:
Regarding the actual error, it appears to be a file that rcedit doesn't consider to be an ICO file  that it can use.

This is how I resolved the issue.
I had an macOS icon file named icons.icns and a Windows icon file named icon.ico. This was my packagerConfig:
"electronPackagerConfig": {
	"packageManager": "npm",
	"icon": "./src/assets/images/icons.icns",
	"asar": true
},

No matter what I specified in my electronWinstallerConfig I was still getting this error, even if I removed the icon key from it. I finally tracked down the issue by finding my globally installed electron-forge and adding a console.log to the rcedit.js file. It turns out that rcedit was taking the the path from electronPackagerConfig and ignoring the electronWinstallerConfig, then just renaming the extension to .ico. So rcedit couldn't find ./src/assets/images/icons.ico because it didn't exist.
Long story short: rename your icon files to have the same base name and in the same folder. In my case I now have these:
src/assets/images/icons.icns
src/assets/images/icons.ico
And everything works.

Following what @jaaromy did. I fixed mine with a config that looks like this:
electronPackagerConfig: {
  icon: "src/assets/images/logo-icon.icns"
},
electronWinstallerConfig: {
  iconUrl: "src/assets/images/logo-icon.ico"
},

Honest question: Are the docs for the icon option incomplete? https://github.com/electron-userland/electron-packager/blob/v12.1.0/docs/api.md#icon
If so, do people have suggestions for improving it?

@malept I know I got here from working with electron-forge. It's difficult to find the documentation that you need when working with things like electron-forge. Now, from your link, I see this which I would've loved to know many, many hours ago.

If the file extension is omitted, it is auto-completed to the correct extension based on the platform
However, an example showing how a Windows and MacOS icon would be set up would be helpful IMO.

It's difficult to find the documentation that you need when working with things like electron-forge.

Hmmm. It's linked in the README... Which Forge docs were you using?

I ended up here: https://github.com/electron/windows-installer#usage from the link in the Make section of the README. My electron-forge package was working but electron-forge make was failing at the time.

The electronWinstallerConfig section wasn't what I was talking about. Additionally, the rcedit errors were updated recently. Were you getting errors like this? https://github.com/electron-userland/electron-packager/issues/621#issuecomment-389590753

authors: Ghost---Shadow Jaaromy TekSiDoT aribornstein davclark hkrware itzsaga malept positlabs

repo: electron-userland/electron-packager


text:
IpcMain listener type needs to be specified

The existing typings on DefinitelyTyped define this:
// https://github.com/electron/electron/blob/master/docs/api/ipc-main.md

/**
 * The ipcMain module handles asynchronous and synchronous messages
 * sent from a renderer process (web page).
 * Messages sent from a renderer will be emitted to this module.
 */
interface IpcMain extends NodeJS.EventEmitter {
    addListener(channel: string, listener: IpcMainEventListener): this;
    on(channel: string, listener: IpcMainEventListener): this;
    once(channel: string, listener: IpcMainEventListener): this;
    removeListener(channel: string, listener: IpcMainEventListener): this;
    removeAllListeners(channel?: string): this;
}

type IpcMainEventListener = (event: IpcMainEvent, ...args: any[]) => void;

interface IpcMainEvent {
    /**
      * Set this to the value to be returned in a synchronous message.
      */
    returnValue?: any;
    /**
     * Returns the webContents that sent the message, you can call sender.send
     * to reply to the asynchronous message.
     */
    sender: WebContents;
}

which allows this code to be written:
ipcMain.on('hello', (event) => {
    event.sender.send('world!');
});

Related to: https://github.com/electron/electron-typescript-definitions/issues/29

If this is documented correctly in the Electron markdown files this can be auto generated.  We just need to change on, once Etc. in the docs to have an event type of IpcMainEvent and document that type as a structure

Any status on this? I get the [ts] Parameter 'event' implicitly has an 'any' type., but as far as I can tell there is no Type yet for the event and so I must explicitly use the any which I'd prefer not to do.

I might be getting confused - but the markdown here:
https://github.com/electron/electron/blob/master/docs/api/ipc-main.md
...suggests the type of the listener's event is IpcMainEvent, but in the typescript definitions imported from the electron package I can only find IpcMessageEvent.
  interface IpcMessageEvent extends Event {
    channel: string;
    args: any[];
  }

Does the IpcMainEvent type exist / contain anything other than the contents of IpcMessageEvent?
So @MarshallOfSound I'm relatively sure that means it isn't documented correctly. Should I open a PR to change that markdown file?

@Mike-Dax We updated the Event docs and generation quite recently on master, this issue will be fixed from 6.0 onwards in the generated types.
The next nightly release of 6.0 will have the correct types in, closing this out as we have fixed it in master

E.g. The IPCMain event docs --> https://github.com/electron/electron/blob/master/docs/api/structures/ipc-main-event.md

@MarshallOfSound

E.g. The IPCMain event docs --> https://github.com/electron/electron/blob/master/docs/api/structures/ipc-main-event.md

What is the difference between calling event.sender.send / send and event.reply?

source: gharchive/issue

authors: GitFlip MarshallOfSound Mike-Dax miniak vladimiry

license: MIT

license_type: permissive

license_source: github-api


text:
Make v8 api forwards compatible with v8 6.7

Cribbed from https://github.com/nodejs/node/commit/2a3f8c3a83e3820d3c601bdf02eda8db462027aa

Why do we need this?

Building 3rd-party modules against the version of node we depend on (v10.2.0) results in modules that are incompatible with the version of v8 in chrome 66 (v6.6.346.32), because node v10.2.0 includes this patch in its vendored v8.
In particular, the thing i ran into is that node v10.2.0 has this signature for v8::FunctionTemplate::New:
Local<FunctionTemplate> FunctionTemplate::New(
    Isolate* isolate, FunctionCallback callback, v8::Local<Value> data,
    v8::Local<Signature> signature, int length, ConstructorBehavior behavior,
    SideEffectType side_effect_type);

but the function signature for v8::FunctionTemplate::New in chromium's version of v8 (v6.6.346.32) is:
Local<FunctionTemplate> FunctionTemplate::New(
    Isolate* isolate, FunctionCallback callback, v8::Local<Value> data,
    v8::Local<Signature> signature, int length, ConstructorBehavior behavior);

So a module built against node v10.2.0's v8 headers won't work with our v8.

So a module built against node v10.2.0's v8 headers won't work with our v8.

Is it expected to do so?
@zcbenz ,can you help us to understand how the thing should work here?

ah, i see that the create-node-headers.py script in e/e overrides nodejs's v8 headers with the headers from chrome. I should probably figure out a way to do that in the gn build.

In the past we've tried to make this work (building native modules for electron by building them on the right node version) but afaik it has sometimes worked on *nix but it has never worked on windows.
We have electron-rebuild and friends to make getting around this problem easy

electron-rebuild doesn't work for development tho (i.e. developing on an unreleased electron)

This is correct but there are helper scripts in the electron repo to rebuild native modules with electron generated headers.

source: gharchive/pull-request

authors: MarshallOfSound alexeykuzmin nornagon

repo: electron/libchromiumcontent

license: mit

license_source: bigquery


text:
model potential attack scenarios

Violet has outlined some potential attack scenarios in this doc:
https://hackmd.io/@VT5KQduBR72gGo7JwYlnJQ/SJLj4hzrs
and this colab notebook:
https://colab.research.google.com/drive/1WOYMqB7IQ141NMWsbTxjAM2-SXenAr1M?usp=sharing
We need to be able to emulate this user behavior in our simulation repo

This is an application of the repo, which we will start tracking outside of github issues.

repo: element-fi/elf-simulations


text:
handling audio streaming from server

Is this the best way to respond with the stream of audio generated through 11labs?
def text_stream():
            yield text

        audio_stream = generate(
            text=text_stream(),
            voice=voice_id,
            model="eleven_multilingual_v2",
            stream=True
        )

        def generate_audio():
            for chunk in audio_stream:
                yield chunk

        return Response(generate_audio(), 200, content_type="audio/wav")

This doesn't actually return the audio chunk when i call the route instead it responds with the full audio when generation is completed
Pls would appreciate some help

Hey @nawed2611, please consider using StreamResponse instead! https://fastapi.tiangolo.com/reference/responses/?h=streaming.
Since this is not an SDK issue, I will be closing this out.

repo: elevenlabs/elevenlabs-python


text:
README correction for JDK17

the JVM option --add-opens java.base/sun.nio.ch=ALL-UNNAMED is missing an equals sign after the option, otherwise the argument isn't recognized

You are correct; Readme is fixed. Thank you!


text:
🛑 UCU - Acceso IS is down

In df73489, UCU - Acceso IS (https://accesois.ucu.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UCU - Acceso IS is back up in b3302e1 after 12 minutes.

repo: elfoche/monitoreo


text:
🛑 UNER - Campus FCAD is down

In 6106dd9, UNER - Campus FCAD (https://campus.uner.edu.ar/fcad/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UNER - Campus FCAD is back up in cec8f6a after 50 minutes.


text:
Consolidate Art code for TMDB and Trakt

Trakt does not return images for a long time and thus we anyway use tmdb api to get images, so it makes sense to move all the code to tmdb package.
Also it solves the issue that trakt code was not using fanart.tv (UseFanartTv) and did not set AvailableArtworks property (for skins).
Also now it prefers language specific arts (was implemented in trakt code but not in tmdb code).
Proof:
"images" field in trakt response is gone long time ago, see https://github.com/scakemyer/plugin.video.quasar/issues/599#issuecomment-268933889
or run:
curl -s -H @trakt-headers.txt https://api.trakt.tv/shows/supernatural/seasons/1/episodes/1?extended=full,images| jq
curl -s -H @trakt-headers.txt https://api.trakt.tv/movies/the-flash-2023?extended=full,images| jq

  "images": {
    "fanart": {
      "full": null,
      "medium": null,
      "thumb": null
    },
    "poster": {
      "full": null,
      "medium": null,
      "thumb": null
    },
    "logo": {
      "full": null
    },
    "clearart": {
      "full": null
    },
    "banner": {
      "full": null
    },
    "thumb": {
      "full": null
    }
  }

ещё случайно нашёл баг когда тракт отдаёт шоу которое уже не существует в тмдб. например в календаре всех шоу (я так проверял картинки).
https://www.themoviedb.org/tv/245369-true-detective-s1
DEBU  tmdb         ▶ ToListItem       show: &{Entity:{IsAdult:false BackdropPath: ID:0 Genres:[] OriginalTitle: OriginalLanguage: ReleaseDate: FirstAirDate: PosterPath: Title: VoteAverage:0 VoteCount:0 OriginalName: Name:} FanArt:<nil> EpisodeRunTime:[] Homepage: InProduction:false LastAirDate: Networks:[] NumberOfEpisodes:0 NumberOfSeasons:0 OriginCountry:[] Overview: RawPopularity:<nil> Popularity:0 ProductionCompanies:[] ProductionCountries:[] Status: ExternalIDs:<nil> LastEpisodeToAir:<nil> Translations:<nil> AlternativeTitles:<nil> ContentRatings:<nil> Credits:<nil> Images:<nil> Seasons:[]}
DEBU  tmdb         ▶ ToListItem       season: &{ID:0 Name: Overview: Season:0 EpisodeCount:0 AirDate: Poster: Backdrop: ExternalIDs:<nil> AlternativeTitles:<nil> Translations:<nil> Trailers:<nil> Credits:<nil> Images:<nil> Episodes:[]}
DEBU  tmdb         ▶ ToListItem       episode: &{ID:0 Name: Overview: AirDate: SeasonNumber:0 EpisodeNumber:0 VoteAverage:0 VoteCount:0 StillPath: ExternalIDs:<nil> AlternativeTitles:<nil> Translations:<nil> Trailers:<nil> Credits:<nil> Images:<nil>}
DEBU  api          ▶ func1            TMDB episode.ToListItem
DEBU  api          ▶ func1            show: &{Entity:{IsAdult:false BackdropPath: ID:0 Genres:[] OriginalTitle: OriginalLanguage: ReleaseDate: FirstAirDate: PosterPath: Title: VoteAverage:0 VoteCount:0 OriginalName: Name:} FanArt:<nil> EpisodeRunTime:[] Homepage: InProduction:false LastAirDate: Networks:[] NumberOfEpisodes:0 NumberOfSeasons:0 OriginCountry:[] Overview: RawPopularity:<nil> Popularity:0 ProductionCompanies:[] ProductionCountries:[] Status: ExternalIDs:<nil> LastEpisodeToAir:<nil> Translations:<nil> AlternativeTitles:<nil> ContentRatings:<nil> Credits:<nil> Images:<nil> Seasons:[]}
DEBU  api          ▶ func1            season: &{ID:0 Name: Overview: Season:0 EpisodeCount:0 AirDate: Poster: Backdrop: ExternalIDs:<nil> AlternativeTitles:<nil> Translations:<nil> Trailers:<nil> Credits:<nil> Images:<nil> Episodes:[]}
DEBU  api          ▶ func1            episode: &{ID:0 Name: Overview: AirDate: SeasonNumber:0 EpisodeNumber:0 VoteAverage:0 VoteCount:0 StillPath: ExternalIDs:<nil> AlternativeTitles:<nil> Translations:<nil> Trailers:<nil> Credits:<nil> Images:<nil>}
DEBU  api          ▶ func1            epi: &{Number:1 Season:1 Title:Episode 1 Overview: Absolute:0 FirstAired:2024-02-12T05:00:00.000Z Translations:[es] Runtime:42 Rating:0 Votes:0 IDs:0xc000157b80}
DEBU  api          ▶ func1            epi.IDs: &{Trakt:11429738 IMDB: TMDB:5119820 TVDB:0 TVRage:0 Slug:}
DEBU  api          ▶ func1            showListing.Show: &{Object:{Title:True Detective (S1) Year:2024 IDs:0xc000157bc0 UpdatedAt:2024-02-04 08:37:39 +0000 UTC} FirstAired:2024-02-12T05:00:00.000Z URL: Trailer: Runtime:42 Overview: Certification: Status:ended Network: AiredEpisodes:0 Airs:0xc0007f0de0 Rating:0 Votes:0 Genres:[] Country:us Language:en Translations:[es]}
DEBU  api          ▶ func1            showListing.Show.IDs: &{Trakt:223824 IMDB: TMDB:245369 TVDB:0 TVRage:0 Slug:true-detective-s1}
DEBU  api          ▶ func1            item: <nil>

так как в фиксе надо менять код связанный с фанарт, а я его тут уже поменял, то чтобы не делать 2 ПРа и потом мерж конфликты ещё решать - сделал фикс тут.

repo: elgatito/elementum


text:
Random Crashing on Kodi 18.9

Hey.
Random crashes when playing.
Can you take a look at my log @elgatito ?
https://paste.kodi.tv/ebuguzehes
Thank you very much.

Closing due to no log provided.


text:
Patch 1, uncomment methods that are still used in activeadmin

Fixes this issue https://github.com/elia/activeadmin-mongoid/issues/95
Also fixes formbuilder klass as @object.object.class returns the mongoid document which will not raise error on _ransackers method call. Thus the removal of the file since activeadmin originally calls the way it is intended.

Looks like the issue will not be completely solved.
Please refer to this issue for a more complete solution with rails 4.2: https://github.com/elia/activeadmin-mongoid/issues/97

repo: elia/activeadmin-mongoid


text:
MSID: 97916 Version: 1 DOI: 10.1101/2023.10.18.562990

MSID: 97916
Version: 1
Preprint DOI: https://doi.org/10.1101/2023.10.18.562990
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=97916
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2023.10.18.562990

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/97916v1
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/2023.10.18.562990
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/97916/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!

repo: elifesciences/enhanced-preprints-import


text:
MSID: 98033 Version: 2 DOI: 10.1101/2023.12.01.569522

MSID: 98033
Version: 2
Preprint DOI: https://doi.org/10.1101/2023.12.01.569522
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=98033
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2023.12.01.569522

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/98033v2
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/2023.12.01.569522
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98033/v2/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!

This one is a mess


text:
Create a timeline

Add a list of all your activities, achievements, work experience. Add as much info as you can remember. In case you don’t have working experience tell about your pet-projects or student projects

### **Experience**

**Balú Hogar C.C. Parque Costazu**l
Store manager | 2015 – 2017
•	Analyze and design sales strategies to achieve a 10% increase in sales per month compared to the previous year.
•	Lead a staff of 9 people, coordinating tasks and execution time of each one to maintain productivity.
•	Capture the client's requirements to carry out consultative advice and offer the product they need.

**Los Inspectores de Venezuela LIV C.A.**
Document controller Project Extension PIGAP I| 2012 – 2014
•	Ensure the quality of engineering documents and drawings (mechanical, civil, electrical and instrumentation disciplines) in the different phases of project execution.
•	Monitor the issuance process and version control of documents, estimating delivery dates.
•	Prepare monthly management reports, with audit reports and corrections of nonconformities.

### **Education**

Diplomado en habilidades de programación con énfasis en aplicaciones web Misión TIC 2021
Universidad de Caldas | 2021 - 2021, Bogotá, Colombia

Título MSc. en Ciencias Administrativas mención Gerencia General
Universidad de Oriente | 2013 - 2017, Monagas, Venezuela

Título Ingeniero de Petróleo
Universidad de Oriente | 2003 - 2009, Monagas, Venezuela

### **Abilities**

Customer service | Problem solving | Results-oriented | Teamwork | Accurate communication | Accountability| Leadership | Adaptability | Time management

repo: elimarrojas/homepage


text:
Stacktrace test

the previous regex created issues for custom adapters because the integration tests are inside the deps directory.

@josevalim I noticed one other thing while trying to help debug the sqlite adapter's integration test failures on the latest Ecto.
Their adapter has to dump booleans to 0/1 which is ok if they belong to a typed field but fails to load properly when for instance they are a value in a map. This made me curious if they would work in embeds, but I noticed that the map values aren't typed even there.
I wanted to investigate keeping the type for embed values but before I wasted a lot of time I wanted to see if you knew a reason not to do this. Thanks!

From a first glance it makes sense that we should try to keep the type as much as possible. :)

authors: greg-rychlewski josevalim


text:
Bump OTP version

https://github.com/elixir-lsp/elixir-ls/actions/runs/5010954095/jobs/8981296694?pr=888
Aha, one failure caused by the map iteration order change in otp 26.

No point in merging it until OTP releases a patch, see https://github.com/elixir-lsp/elixir-ls/issues/886

Yup

authors: lukaszsamson princemaple

repo: elixir-lsp/elixir-ls


text:
Support Starcoder Model

Related to #278 , it would be amazing if somebody could also look into supporting the starcoder model.
The original model is quite big, but there's also a 7B version and a 1B version
I've run it through the repository inspector and got the following result:
🤷♂ Failed to load, reason: could not match the class name "GPTBigCodeForCausalLM" to any of the supported models, please specify the :module and :architecture options.

Tokenizer
🤷♂ Failed to load, reason: could not match model type "gpt_bigcode" to any of the supported tokenizers, please specify the :module option.

Any help is much appreciated <3

This error means that it's not yet implemented in Bumblebee. It looks like GPTBigCodeForCausalLM is very similar to GPT2, but with MQA (which we added for Mistral, it's just a question of how to unify the configuration options to accommodate both) and a couple optimisations (some of them may be applicable, but needs a closer look).

authors: jonastemplestein jonatanklosko

repo: elixir-nx/bumblebee


text:
BUG REPORT ON URGENT REQUIRED

### BUG REPORT ON URGENT REQUIRED
BUG REPORT :
Create a report to help us reproduce and fix the bug. If this doesn't look right, choose a different type
Before submitting a bug, please make sure the issue hasn't already been addressed by searching through the existing and past issues. Describe the bug" Please provide a clear and concise description of the bug.
A critical bug has been identified in the [app/website/system], causing unexpected crashes or performance issues. Users are experiencing slow load times, functionality disruptions, and data inconsistencies. This bug primarily affects [specific features or devices], leading to a poor user experience. It has been reported on both mobile and desktop platforms, impacting [operating systems, browsers]. Our development team is actively working to resolve this issue with an urgent patch update. Stay tuned for fixes! #bugfix #performanceissues #crashfix #userexperience #appupdate #systembug

Phishing links, do not click on it

repo: elixir-tesla/tesla


text:
Make Capitalization consistent

We should probably make all set names capitalized.

Ideally all (including the image) should be capitalized.
On Fri, Jul 19, 2024 at 12:19 PM Ishrat Jahan Eliza <
@.***> wrote:

Should it be the same as the name in the picture on the right? or should
all first letters be capitalized?
—
Reply to this email directly, view it on GitHub
https://github.com/elizaan/Upset-alltx-study/issues/9#issuecomment-2239855161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAPR4T7NSMU3I7C5PSK3CRTZNFJ7PAVCNFSM6AAAAABLCYZM62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZZHA2TKMJWGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Alexander Lex
Associate Professor of Computer Science
Director of Graduate Studies
SCI Institute & Kahlert School of Computing, University of Utah
http://alexander-lex.net | Visualization Design Lab: http://vdl.sci.utah.edu

repo: elizaan/Upset-alltx-study


text:
Graphics issues on wayland

Text is blurry and window flickers on Wayland (+hyprland).

Hey! Just letting you know that elk-native is no longer maintained, much of the team has moved on or is busy with other projects (there's only so much time in a day 😅), so this issue will likely not be fixed.
Please use the actively maintained elk PWA instead.
Thanks so much for your support and understanding so far! ❤

repo: elk-zone/elk-native


text:
Get rid of Format model

On today's meeting with @martinbilek  and @whit we agreed that it will be nice to get rid of photo format altogether and switch to Django settings-based formats. There nothing really useful about the way photo formats are defined as it's usually done only once during the site lifecycle - at the time the site is built.
By using settings-based formats, we will save some DB queries and it will be much simpler to manage the list of formats.

I am strongly against this for several reasons:

we use the format ID everywhere and across sites, how do you synchronize settings for multiple projects?
I really don't want designers in my settings.py or anywhere near python but I really don't want them to bother me to create a Format for them either
how do you then make sure you can share images across sites?
if you want to define them once in code, use fixtures and you lose nothing from the functionality.

how about we just cache all the formats in memory? Do something like Format.objects.get_for_name() which would have similar caching logic as Django ContentType's get_for_id(). I wanted to do that anyways. Also note that when you use cached template loader all the {% img %} tags will load their format on compile time so the Format is cached in memory even now for majority of use cases.

I am closing this. I can see why somebody would want a simpler way of creating thumbnails and am not against that at all, but if we decide we want anything like that, let's built it next to the existing solution which actually works very well for a lot of use cases.

authors: HonzaKral xaralis

repo: ella/ella


text:
_atuin_search_widget suddenly stopped working

_atuin_search_widget doesn't appear when I call eval "$(atuin init zsh)".
Among other things, atuin search and most atuin history commands don't work.
Here's a sneak peak of what I get:

And this is what I get when I hit ctrl + r, even though I binded it to atuin:

This sometimes happens because of a terminal mode change. If you could do "ctrl-v, up arrow" and share the result :)
If you check the source and see what we've bound the widget to, I suspect this will not match what you see

Sorry about this, but I've switched machines and fixed the issue since. Must've forgotten about this issue.

authors: DanKGooGLy Vapourium ellie

repo: ellie/atuin


text:
Publish: Better handling of index letters

Index letters (on the Individuals) page will now not show up if there are no living individuals for that index letter.
This also fixes a bug where the sources were not being published.

This change is

Codecov Report

Merging #267 into master will increase coverage by 0.31%.
The diff coverage is 71.79%.

@@            Coverage Diff             @@
##           master     #267      +/-   ##
==========================================
+ Coverage    65.5%   65.81%   +0.31%
==========================================
  Files         207      207
  Lines        6636     6644       +8
==========================================
+ Hits         4347     4373      +26
+ Misses       2156     2139      -17
+ Partials      133      132       -1

Impacted Files
Coverage Δ

document.go
78.41% <ø> (ø)
:arrow_up:

html/individual_list_page.go
9.83% <0%> (ø)
:arrow_up:

html/publish_header.go
0% <0%> (ø)
:arrow_up:

html/individuals.go
100% <100%> (ø)
:arrow_up:

html/publish.go
78.04% <100%> (+11.38%)
:arrow_up:

html/util.go
48.54% <50%> (+4.85%)
:arrow_up:

html/individual_index_header.go
52.77% <65.21%> (+7.95%)
:arrow_up:

html/source_list_page.go
31.25% <0%> (+31.25%)
:arrow_up:

Continue to review full report at Codecov.

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

authors: codecov-io elliotchance

repo: elliotchance/gedcom


text:
Revert S3 processor addition

Sorry @Justin-Holmes. Couldn't do a Github revert so went in more manually.

No worries, LGTM!

authors: Justin-Holmes jayzes

repo: ello/ello-kinesis-consumer


text:
Empty the error stacktrace

The stacktrace emitted by elm-webpack-loader is mostly useless (at least I don't know of an usecase where it would be benefitial) - this PR clears it.
Before

After

Thank you for this!

authors: Janiczek Skinney

repo: elm-community/elm-webpack-loader


text:
tests

I see that tests are mentioned in the spec. elm-test-rs could fit well with elm-tooling since it is an executable not depending on npm. In such cases, a tests section could be used directly if present. However, by default the command line expects files as arguments, not directories. I can see two convenient ways to spec it. Either globs are authorized in the tests section, or only directories, and the tests runner convert those automatically to something like dir1/*.elm dir2/*.elm ...

The ideal solution is to have no configuration at all: Running just elm-test or elm-test-rs should run all tests, no matter where they are located, without any config.
This is already possible. Instead of defaulting to tests/, we just need to default to all source directories, plus tests/ if it exists.
So why don’t we do that already? Because of performance. I tried this at work, and the compiled JS becomes megabytes, which is parsed over and over in different workers.
I think we should see what it would take to make the no-config approach possible. If it isn’t possible – or it’s too far in the future – I guess we could still add a field in the mean time.
As a side note: IDEs. They could work without config, too:

For packages, allow test-dependencies in any files not in exposed-modules (easy).
For applications, allow values from test-dependencies only in values not reachable from any entrypoint (harder).

Either globs are authorized in the tests section, or only directories

I don't know why I was thinking that, having both files and directories would be fine if a tests field is created.

So why don’t we do that already? Because of performance. I tried this at work, and the compiled JS becomes megabytes, which is parsed over and over in different workers.

Is this because "potential" tests are coming from almost all files? If there was type inference and only actual test values are picked, would the generated file be lighter?

Do you have an example public repo where this problem appears?

Not off the top of my head. I’ll try to look for one.

Is this because "potential" tests are coming from almost all files?

At work, we only have tests in the tests/ folder.
elm-test tests results in a 1.2 MB JS file.
elm-test tests src results in a 5.8 MB JS file – it’s all of our Elm code in there (even stuff that’s never reached from tests). Like you say, this is because the no-elmi approach we currently have requires compiling all given Elm code to JS, because we don’t know what could be tests until runtime.

If there was type inference and only actual test values are picked, would the generated file be lighter?

Yes. Then it would go down to 1.2 MB again. I tested this – node-test-runner@0.19.1-revision4 works that way. It results in a 1.2 MB file even when running elm-test tests src. That’s because elmi-to-json knows which modules contain Test values so we only compile those to JS.
I’ve been toying with the idea of doing partial type inference the last couple of days. Sounds like a fun project, but I’m unsure when I’ll get time to experiment with it.

This is already possible. Instead of defaulting to tests/, we just need to default to all source directories, plus tests/ if it exists.

Becomes "tests/ + files that have anything typed Test" when we have type inference?
I'm asking, cause we need to figure out how to import the deps of test files a bit more correct. See: https://github.com/elm-tooling/elm-language-server/issues/589

Becomes "tests/ + files that have anything typed Test" when we have type inference?

Yes. I’m thinking the algorithm would be:

Find all .elm files in source-directories plus tests/ if it exists.
In those files, find all exposed values of type Test.
That’s all the tests.

elm-tooling.json is no longer a shared config file: https://github.com/elm-tooling/elm-tooling-cli/pull/77
So this discussion does not belong here anymore.
Note: https://github.com/elm-tooling/elm-language-server/pull/629 implements quite good test detection: Some files are tests for sure, some files are not tests for sure and some files could be tests. I’d like to explore having elm-test and elm-test-rs default to “tests for sure + possibly tests” instead of tests/, and as such avoiding configuration altogether. Or come up with something that isn’t so complicated for tools.

authors: Razzeee lydell mpizenberg

repo: elm-tooling/elm-tooling-cli


text:
Package install with malformed package name produced unhelpful error message

I ran elm install elm-geometry in PowerShell using Window 10 and got the following error message:
elm.exe: TODO show possible arg configurations
CallStack (from HasCallStack):
  error, called at ui/terminal/src\Terminal\Args\Error.hs:281:13 in main:Terminal.Args.Error

After a couple minutes I realized that I should have written elm install ianmackenzie/elm-geometry instead but I think it would be more helpful if the error message returned was something along the lines of Failed to install package.  I expected the package name formatted as author/package-name.

Thanks for reporting this! On my development build, I am seeing the following error message:
$ elm install elm-geometry
I am having trouble with this argument:

    elm-geometry

It is supposed to be a <package> value, like one of these:

    elm/browser
    elm/core
    elm/parser
    elm/regex

So it looks like it got fixed as part of the infrastructure improvements there. The fixed version should become available once Elm 0.19.1 is released. Thank you for reporting this case!

I think it can be improved a bit more though. I'll give it a shot and get back to you!

Ah, it's a bit tricky. I know if I really start working on it there is a high chance the project will grow a bit larger than makes sense, so I think it makes sense to wait on it for now.

authors: MartinSStewart evancz

repo: elm/error-message-catalog


text:
Add support to Bun Package Manager

main title talks for itself.
making a simple case-study, could seen that bun package manager has growing up in a large scale.
it's nice to add support for them.
fresh tech to fresh stack.
this opinion it's not only of my own.
att.

here's one more bun lover too🙋♂💜

Memory usage and cold start time are essential since we are using serverless architecture.
It seems like Nodejs is still great for this case.
Here's an example article: https://5ly.co/blog/bun-vs-node-comparison/#bun-vs-nodejs-benchmarks-comparison
We migrated to pnpm from yarn from skeet v2.
I am always happy to integrate better techs!
Let's see how Bun is growing 👀

authors: POPPIN-FUMI matheusdsm weensy

repo: elsoul/skeet-cli


text:
What does items.add do, and where is it defined at?

https://github.com/elucent/SimplyTea/blob/39a58f39eaae514fe98de8167dae54c29845cb28/src/main/java/elucent/simplytea/SimplyTea.java#L667
I'm trying to build a mod at the moment, and SimplyTea is a pretty good example of how some of the basic tasks like adding items can be done.  That said, I'm stumped as to where this comes from.  Eclipse says that "items cannot be resolved."  Where is "items.add" defined?

8 lines above there. It is adding the item to a list so the instances can be created in preInit while still registering them at the proper time. I would personally recommending creating them directly in the block and item events with some small helper functions, though either approache istechnically fine.
Personally, I would not say SimplyTea is the best example for making a mod as Elucent purposely coded it oddly in one class file essentially since it was small enough he could. If you want to learn from something with a similar style, GravelOres might be a better choice, or alternatively own mod Ceramics shows some different methods of handling things.

Ah, thank you!  I'll take a look at the other two.

authors: KnightMiner TheFoss

repo: elucent/SimplyTea


text:
Conversion of IPAddress to non-scalar type

I get the following error with the provided example and changed for my use case

Please upgrade the component

And how do i do that? i guess it pulls the code directly from github?

It does, but you may have to clear cache in esphome in some way.

I deleted everything and redownloaded via homeassistant and manualy and still the same issue

I'm using esphome dev and yes it is updated ... could the issue be the dev esphome addon?

Maybe. Yes. But if it is then i need to figure out why dev doesnt work.

[image: image.png][image: image.png][image: image.png]
Hi,
since i have your attention ... i'm still struggling to get the thing
working ... i have a VVM310 HP, and i cant find the enable MODBUS40 in
settings and i cant get it connected. I guess the modbus connection is ok.
I also tried different ports if some were blocked
V V pon., 30. okt. 2023 ob 17:55 je oseba Joakim Plate <
@.***> napisala:

Maybe. Yes. But if it is then i need to figure out why dev doesnt work.
—
Reply to this email directly, view it on GitHub
https://github.com/elupus/esphome-nibe/issues/48#issuecomment-1785658965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGCU5ZPFNLM4FCRFRIJ7S2DYB7LYJAVCNFSM6AAAAAA6WABOKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGY2TQOJWGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

also i get this error ... even if i have the devices on the same network,
but since i have homeassistant on 192.168.20.3 and esp on 192.168.20.195 it
should be fine
V V sre., 1. nov. 2023 ob 16:47 je oseba Matevž Pivk @.***>
napisala:

[image: image.png][image: image.png][image: image.png]
Hi,
since i have your attention ... i'm still struggling to get the thing
working ... i have a VVM310 HP, and i cant find the enable MODBUS40 in
settings and i cant get it connected. I guess the modbus connection is ok.
I also tried different ports if some were blocked
V V pon., 30. okt. 2023 ob 17:55 je oseba Joakim Plate <
@.***> napisala:

Maybe. Yes. But if it is then i need to figure out why dev doesnt work.
—
Reply to this email directly, view it on GitHub
https://github.com/elupus/esphome-nibe/issues/48#issuecomment-1785658965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGCU5ZPFNLM4FCRFRIJ7S2DYB7LYJAVCNFSM6AAAAAA6WABOKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGY2TQOJWGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

[image: image.png]
V V sre., 1. nov. 2023 ob 18:41 je oseba Matevž Pivk @.***>
napisala:

also i get this error ... even if i have the devices on the same network,
but since i have homeassistant on 192.168.20.3 and esp on 192.168.20.195 it
should be fine
V V sre., 1. nov. 2023 ob 16:47 je oseba Matevž Pivk <
@.***> napisala:

[image: image.png][image: image.png][image: image.png]
Hi,
since i have your attention ... i'm still struggling to get the thing
working ... i have a VVM310 HP, and i cant find the enable MODBUS40 in
settings and i cant get it connected. I guess the modbus connection is ok.
I also tried different ports if some were blocked
V V pon., 30. okt. 2023 ob 17:55 je oseba Joakim Plate <
@.***> napisala:

Maybe. Yes. But if it is then i need to figure out why dev doesnt work.
—
Reply to this email directly, view it on GitHub
https://github.com/elupus/esphome-nibe/issues/48#issuecomment-1785658965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGCU5ZPFNLM4FCRFRIJ7S2DYB7LYJAVCNFSM6AAAAAA6WABOKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGY2TQOJWGU
.
You are receiving this because you authored the thread.Message ID:
@.***>

repo: elupus/esphome-nibe


text:
no skin

Minecraft versions below 1.3 have no skins even though I have my own skin selected. Please help with this issue.

You need to patch versions below 1.7.9 by yourself because these versions do not use Authlib.
Some patches are available at https://ely.by/load

authors: Nik-mmzd horriblejoseph

repo: elyby/accounts


text:
Fix: type example and elysia dependency upgrade to fix types

chore: remove pnpm references and pnpm lock
chore: remove (unused?) build folder
chore: upgrade dependencies, fix test and build scripts
chore: add elysia to .vscode workspace settings for spelling plugins
feat: update types and update the example project's example types
feat: prevents bundling additional versions of graphql or related dependencies

@SaltyAom anything we'd be able to upstream to remove the typescript errors and provide some more in-depth examples?

An ETA to merge @SaltyAom ? This error blocks my build right now 😞

authors: coratgerl vincentvella

repo: elysiajs/elysia-apollo


text:
cargo: improve and unify function regexp

Far from complete but reasonable amount of function syntax added.
Partial(since matching still occurs twice) unification solves signature-name search discrepancies.

Thanks for adding tests! Is this ready to merge since you have mentioned in the PR description that it's "far from complete"? These days I use treesit-beginning-of-defun for a similar use case.

Thanks for adding tests! Is this ready to merge since you have mentioned in the PR description that it's "far from complete"? These days I use treesit-beginning-of-defun for a similar use case.

The commit is fully functional and safe enough.
Regexp is incomplete but it is an improvement to previous version.
Treesiter seems like proper solution though, thanks for pointing out, I have been using old customization without it.

Cool, thanks! Yeah, I have completely switched to treesitter now and I find it more reliable. Details here, if you want to switch: https://github.com/emacs-rustic/rustic?tab=readme-ov-file#tree-sitter

Cool, thanks! Yeah, I have completely switched to treesitter now and I find it more reliable. Details here, if you want to switch: https://github.com/emacs-rustic/rustic?tab=readme-ov-file#tree-sitter

Thank you for the merge and the instruction!

authors: masicn psibi

repo: emacs-rustic/rustic


text:
Error when there's a space in the path where this is used

Thanks for this script! It's really useful. I had one small issue because the path I am using it in has a space in it. The fix is to quote the variables used for paths. Here's a diff to save you some time:
http://pastebin.com/kV1cXnKU
I also added OptiPNG to squeeze the files down a bit more: http://pastebin.com/TXjCGYGr
Thanks again!

Awesome, thanks! Those are very useful changes. I see you've made your changes on a fork. If you create a couple of pull requests back to my repository (one for the filenames and one for the optiPNG), I can merge it straight in without needing the patch.

Bump

@emarref Sorry for the very long delay, I'm not very experienced with pull requests. I have everything in a local branch (both as one commit unfortunately, let me know if I should do another branch with multiple). I'll try to get the pull request posted today.

@emarref You should see the pull request now. Thanks for the reminder!

Fixed by #6

authors: bsharper emarref

repo: emarref/webicon


text:
Move process-logs-api to package and more

Move logHandler to embark-utils
move escapeHtml and normalizeInput to embark-utils (in a new file called log-utils, more functions could go there, but those were the two I needed to move for now)
Move process-logs-api to a package

I suggest copying the .npmrc from another package into packages/embark-process-logs-api.

Quick heads-up @jrainville I've created a separate PR with your util commits so we can move on with other refactorings that depend on the same changes: https://github.com/embark-framework/embark/pull/1538
You might want to rebase against that one and/or change PR base for this PR

Branch now based on top of refactor/utils (https://github.com/embark-framework/embark/pull/1538)  as @PascalPrecht suggested

repo: embark-framework/embark


text:
refactor(@embark/cmd): make build command work again

This commit refactors the build command to use the newly refactored
event APIs.

Let's wait for #1784 to land first as it introduces compileAndDeploySmartContracts(engine) which can be used in build() as well.


text:
rp2040: add {tx,rx}-only constructors to UART

As discussed with @henrik-alser on Matrix. I also added an example, feel free to remove it if it's too much.

For buffereduart, this is already available as BufferedUart{RT}x::new(). I don't think we should have 2 different constructors to do the same thing.
They're missing for the non-buffered uart indeed. Could you change them to `Uart{RT}x::new(), like the existing BufferedUart ones?

They're missing for the non-buffered uart indeed. Could you change them to `Uart{RT}x::new(), like the existing BufferedUart ones?

Right. I was following @henrik-alser's idea of .new_{t,r}xonly methods, but if you guys think it's better that way, no problem.

PR Updated.

Perfect. Thanks for reviewing this so quickly!

authors: Dirbaio pferreir

repo: embassy-rs/embassy


text:
[Feature Request] Prompt Customization

This is also part of #105, currently this is the prompt that's always used:
prompt = f"""Use the following pieces of context to answer the query at the end. If you don't know the answer, just say that you don't know, don't try to make up an answer.
        {context}
        Query: {input_query}
        Helpful Answer:
        """

this should be customizable. I think everyone agrees. The question is whether it should be a class attribute of the app, or on a per question basis.

I would like to see #63 merged first, so we don't have a merge conflict. Then I can work on this.

The question is whether it should be a class attribute of the app, or on a per question basis.

Although it does add more (optional) boilerplate, the per question basis allows for higher customization. Also, we have not thought of a way to implement "global" class attribute settings, so this also speaks for the per question variant.

Waiting to see if we can merge #63, then this should be easy.

repo: embedchain/embedchain


text:
mmteb | Arabic | Retrieval Task

Checklist for adding MMTEB dataset

Reason for dataset addition:

This is a dataset for mmteb initiative.

The Dataset is for Arabic Retrieval tasks

The Dataset is for Keyword-Based searching tasks (The retrieval part in the RAG pipeline)

Although the promising capabilities of using embeddings for semantic search of queries, we still notice some challenges when the query becomes too short and in keywords style.

[x] I have tested that the dataset runs with the mteb package.

[x] I have run the following models on the task (adding the results to the pr). These can be run using the mteb run -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).

[x] If the dataset is too big (e.g. >2048 examples), considering using self.stratified_subsampling() under dataset_transform()

[x] I have filled out the metadata object in the dataset file (find documentation on it here).

[x] Run tests locally to make sure nothing is broken using make test.

[x] Run the formatter to format the code using make lint.

[] I have added points for my submission to the points folder using the PR number as the filename (e.g. 438.jsonl).

@bakrianoo looks like the tests fail - will you have a look at this

Hi @bakrianoo
I faced a similar error. These steps that I did to fix it:
go to the file tests/test_TaskMetadata.py
add 'SadeemKeywordRetrieval', to the list of _HISTORIC_DATASETS manully.
save the file and run make test

Please do not do this. We specifically have exceptions for _HISTORIC_DATASETS but the test is intended to fail for new dataset @Ruqyai if you have done this for a previous dataset please make a PR the fix.

Hi @bakrianoo
I faced a similar error. These steps that I did to fix it:
go to the file tests/test_TaskMetadata.py
add 'SadeemKeywordRetrieval', to the list of _HISTORIC_DATASETS manully.
save the file and run make test

Please do not do this. We specifically have exceptions for _HISTORIC_DATASETS but the test is intended to fail for new dataset @Ruqyai if you have done this for a previous dataset please make a PR with the fix.

Thanks @KennethEnevoldsen .. I am doing.
Please check if you could merge my PR without needs to comment the test_all_metadata_is_filled function.

authors: KennethEnevoldsen Ruqyai bakrianoo

repo: embeddings-benchmark/mteb


text:
Introduces ability to extract pragma tag from the template

Current pragma tag proposal is {{use-component-manager "<manager-id>"}}. Before compiling the template "" part would be extracted and set on template's metadata.

It might make sense to pull ast plugin into a separate file along with PRAGMA_TAG constant. Let me know if you want me to do that.

repo: ember-cli/ember-build-utilities


text:
Option for enabling onlyRemoveTypeImports

https://babeljs.io/docs/babel-plugin-transform-typescript#onlyremovetypeimports
https://github.com/embroider-build/ember-auto-import/issues/611#issuecomment-1984990158

Example of this problem: https://github.com/jmurphyau/ember-truth-helpers/issues/206

repo: emberjs/ember-cli-babel


text:
upgrades ember-test-helpers to 3.0.2

If merged, this PR updates ember-test-helpers to 3.0.2 (including peer dep declaration).

I'd like to merge these PRs first https://github.com/emberjs/ember-qunit/pulls/@me
all the PR descriptions can give context, and the needed breaking changes are throughout the PRs.

I'd like to merge these PRs first

This link might work better for people who aren't you 😅 : https://github.com/emberjs/ember-qunit/pulls/NullVoxPopuli

Whoops, thanks!

Right so my plan is to do two releases:

drop old node, upgrade ember-test-helpers version, release new major
merge in the PRs from @NullVoxPopuli then do a new major after that

BECAUSE of all the issues we faced with ember-test-helpers, it feels a little more pragmatic to do it this way.

looks like @ember/string needs to be added to the test app

authors: MelSumner NullVoxPopuli gilest

repo: emberjs/ember-qunit


text:
What decides loading files order at file input plugin?

When I use embulk-input-file(embedded plugin) with following files
imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv
imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv

then "Loading files" order is different in server A and B.
(both environments are CentOS 6.4 / Java 1.8.0_112 / embulk 0.8.15)

Server A

imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv
imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv

Server B

imitation_matter__c_load1_4_all.csv
imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv
imitation_matter__c_load1_4_minimal_null.csv

"Loading files" order seems to be the same find command(find <path> -name "imitation_matter__c_*") result. And find command result is different in server A and B.
I expected "Loading files" order is decided by filename order but it' not. so what decides loading files order?(or order differs just in the logs?)

Could you double check the locale setting on the server A and server B.
The locale setting affects sort ordering.
Do the filenames are the following, don't you?

imitation_matter__c_load1_10000_minimal_null.csv
imitation_matter__c_load1_11000_minimal_null.csv
imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv

export LANG=C ; ls
imitation_matter__c_load1_10000_minimal_null.csv
imitation_matter__c_load1_11000_minimal_null.csv
imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv

export LANG=en_US.utf-8 ; ls
imitation_matter__c_load1_10000_minimal_null.csv
imitation_matter__c_load1_11000_minimal_null.csv
imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv

See also.
http://rcmdnk.github.io/blog/2015/08/10/computer-linux/ (Japanese text).

And one more thing.
If the locale is same,
The embulk-file-input plugin read files with multi-thread. so It processes another order.

Thanks for your prompt reply.
I'll check locale settings and retry with max_threads: 1.

Server A and B are the same filesystem?
Default order of find (also ls -U) is depend on it.
http://unix.stackexchange.com/questions/13451/what-is-the-directory-order-of-files-in-a-directory-used-by-ls-u
My test result on Arch Linux with ext4 filesystem is the same of Server B.

FYI
Get file list part.
https://github.com/embulk/embulk/blob/master/embulk-standards/src/main/java/org/embulk/standards/LocalFileInputPlugin.java#L123-L146
Filename sort part.
https://github.com/embulk/embulk/blob/master/embulk-standards/src/main/java/org/embulk/standards/LocalFileInputPlugin.java#L92
The last path compares part.
https://github.com/embulk/embulk/blob/master/embulk-standards/src/main/java/org/embulk/standards/LocalFileInputPlugin.java#L151
https://github.com/embulk/embulk/blob/master/embulk-standards/src/main/java/org/embulk/standards/LocalFileInputPlugin.java#L129

locale settings: same (checked by locale command)
max_threads: 1: same result (it's not multi-thread case)
filesystem: same (ext4)

I also check different servers and I find filesystem mount options are different with different sort order.

? : Server A(I don't have permission to check) and Windows7

imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv
imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv

default :  Server B order

imitation_matter__c_load1_4_all.csv
imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv
imitation_matter__c_load1_4_minimal_null.csv

default,nobarrier :

imitation_matter__c_load3_10004_minimal_null.csv
imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load1_4_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv
imitation_matter__c_load1_4_all.csv

default,relatime,nobarrier :

imitation_matter__c_load2_10000_minimal_null.csv
imitation_matter__c_load3_11000_minimal_null.csv
imitation_matter__c_load1_4_all.csv
imitation_matter__c_load1_4_minimal_null.csv
imitation_matter__c_load3_10004_minimal_null.csv

I think this may affect sort order.
Anyway

This may be not embulk issue
"Loading files" order with single-thread follows find (also ls -U) order.

So I close this issue. Thanks @hiroyuki-sato @uu59

@noissefnoc
Thank you for sharing the information.
Could you clarify the "Loading files" meanings?
It is the following in embulk run? Correct?
Loading files [/private/tmp/hoge/csv/sample_01.csv.gz, /private/tmp/hoge/csv/sample_02.csv.gz]

I think, this list will sort after output the logs.
"Loading files" output part.
https://github.com/embulk/embulk/blob/master/embulk-standards/src/main/java/org/embulk/standards/LocalFileInputPlugin.java#L64
sort part.
https://github.com/embulk/embulk/blob/master/embulk-standards/src/main/java/org/embulk/standards/LocalFileInputPlugin.java#L92

authors: hiroyuki-sato noissefnoc uu59

repo: embulk/embulk


text:
Test with maxHeapSize=2048m

AppVeyor tests are really frequently failing by Java heap size error. It's not a "solution", but let's get maxHeapSize up...
Can you have a look, @muga?

#714 might have fixed the testing problems. Closing this PR without merging.


text:
Update README

The Markdown Readme for rexray is outdated after we moved the vagrant files into one repo

@jonasrosland Can you tackle this one?

Will do.

Fixed.

authors: clintonskitson jonasrosland koensayr

repo: emccode/vagrant


text:
Creazione blog post per raccolta dati

Fare un post che riporti richiesta per persone che raccolgano informazioni relative al terremoto (quelle che popolano Google spreadsheet per  #intenderci).
Successiva condivisione del post sui social - come fatto per il post dal titolo "Sei uno  sviluppatore?"
Categoria BLOG.
Istruzioni nella pagina wiki.

Io ho preparato questa base, se può andare bene ottimo, se no disponibile a rifarla!
2016-8-27-Aiutaci-ad-individuare-le-informazioni.zip

@Manfro GRAZIE!!!! A me sembra ottimale (cambierei solo "pù" in "più" - che ci sta, vista l'ora in cui hai fatto il lavoro), ma chiedo rilettura anche a @iltempe

@ValeriaV Ottimo! Grazie a te
Qui ho corretto l'errore segnalato.
2016-8-27-Aiutaci-ad-individuare-le-informazioni.zip

occhio ragazzi il layout è POST non blog. l'ho committato.

authors: Manfro ValeriaV iltempe

repo: emergenzeHack/terremotocentro


text:
Add settings info on readme

Reference: Issue #3

Thanks!

repo: emersion/meltsub


text:
Using local API to retrieve current track

Hey,
I made first version of changing API for retrieving current track to use local system api for spotify player as was suggested here: https://github.com/emilioastarita/lyricfier/issues/103 by @patrolez.
I only tested it on Linux but clients are for the most part taken from this project:
https://github.com/panz3r/hyper-spotify/tree/master/src/lib
Please take a look and let me know what you think.

I am not a TypeScript developer, but I can only say well done! :+1:
It works under Linux for me also!

I've tried this in macOS Mojave and it's not working for me 😢

Thank for testing! I will take a look and see what I can do about it

Not working for me on Windows 10. In the cmd prompt, when clicking Try Again I get this
[10628:1012/232907.571:INFO:CONSOLE(6)] "Uncaught TypeError: Spotilocal is not a constructor", source: C:\Users\myles\lyricfier\render\spotify\SpotifyWindows.js (6)
I have spotify version 1.0.91.183.g259b84fa, but I also use Spicetify to customize my Spotify a bit. Could that be why this isn't working?
Thanks!

I fixed issue on macOs Mohave so linux+macOs should work now.
Unfortunately, I had to remove support for windows as i have no idea how to do it locally. As MPRIS does not exists on windows and it seems SystemMediaTransportControls is not alternative that would allow accessing currently played track. I vote for dropping windows support until we find working alternative and in the meantime have working app for other platforms. What shall we do @emilioastarita?

It works now! Thank you so much!
Is there a way you could put together a release so that it's easier to launch the app (not requiring the command line)?

Here is release in my forked repo: https://github.com/jakub-tucek/lyricfier/releases/tag/v0.3.0

Is windows support a priority, because all other lyric apps for Spotify are abandoned

(electron:15339): Pango-ERROR **: 22:07:44.628: Harfbuzz version too old (1.4.2)
I just done quick googling and find out that it's probably common electron problem.

authors: Agusum jakub-tucek mendel3 patrolez wappyn

repo: emilioastarita/lyricfier


text:
Table Demo and Strip Demo window height grow when mouse cursor moves

Even if I refresh my browser, the egui.rs demo page windows for the Table Demo and Strip Demo grow on their own when the mouse cursor moves. Using Latest Firefox 113.0.2 64-bit on an M1 running MacOS Ventura 13.4.

Watch the bug in action: https://youtu.be/ES4Mj6taq00

The same bug applies to the Strip Demo — the window grows on any interaction.

With the help of git-bisect, this behaviour first shows up in commit 94f8b02286d141147fa0f7177487091cbdca4c45.
Previous good commit: 089c7b46f37d76381eddf258de220cba08b8f126.
Tested locally using egui/crates/egui_demo_app on a Mac M1 (MacOS 13.4)

One can see this behaviour even without moving the mouse: if egui is set to "continuous" mode, "Table demo" and "Strip demo" frames will continuously grow vertically.

‘Table Demo’ window doesn't grow if any of these statements is commented out.

https://github.com/emilk/egui/blob/9478e50d012c5138551c38cbee16b07bc1fcf283/crates/egui_demo_lib/src/demo/table_demo.rs#L112-L116

https://github.com/emilk/egui/blob/9478e50d012c5138551c38cbee16b07bc1fcf283/crates/egui_demo_lib/src/demo/table_demo.rs#L107-L111
Demos

Both statements are present (9478e50d012c5138551c38cbee16b07bc1fcf283)
https://github.com/emilk/egui/assets/17462/8a7cd847-ae6c-456c-8993-e58c53802333

Statement 1 is commented out
https://github.com/emilk/egui/assets/17462/3d474513-5555-4f8e-bcce-90f556e7ab08

Statement 2 is commented out
https://github.com/emilk/egui/assets/17462/cc020b93-034b-401d-8f38-e847ca931a2c

Both statements are commented out
https://github.com/emilk/egui/assets/17462/50954202-4bec-4d63-a814-245e4f8f127b

I am unclear from the description, was this an issue only with the demo itself or was there an underlying problem with the egui library itself? I see that area.rs and rect.rs were modified.

@rustrust I have replied in the PR.

the egui.rs demo page is still doing this,... are we waiting for this to be rolled out to the demo page or is it expected to be fixed now?

I still get this issue with egui_demo_app compiled for linux from latest master (627e1b3d5054df9961b5a467ac7c7b866a04d913).

authors: jccampagne olanti-p rustrust vvv

repo: emilk/egui


text:
loosing connection to single player worlds

this is 100% just an incompatibility with another mod but i found it strange enough to at least ask if this has been seen before.
when attempting to load into a single player world the screen goes completely black, the mouse becomes visible, and after 8 seconds the following message appears
connection lost
Internal exception : java.lang.NoClassFoundDefFoundError: dev/emi/emi/emireloadmanager
back to server list
(clicking back to server list takes me to the multiplayer server list)
using quilt 1.19.2 client with emi 1.0.0 1.19.2 fabric/quilt. i've never seen an error like this, with the game confusing whether im in single player or not.

One of the mods in your modpack uses Polymer.
Polymer uses EMI internals and (uniquely) broke in the 1.0.0 update; install Polymer-0.2.28 and it should be fixed.

Kat was correct, as Polymer uses EMI internals it occasionally breaks when it shouldn't. Polymer is often included by other mods, but if you include your own updated version, it should fix this issue.

works perfectly now, thank you very much.

Bluberry-Kat, you legend! That was the fix I needed as well. Thank you! :D

authors: Bluberry-Kat Nitron-picarla WimpieRatte emilyploszaj

repo: emilyploszaj/emi


text:
Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗****

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

Efficient Ridesharing Order Dispatching with Mean Field Multi-Agent Reinforcement Learning. 2019. WWW
大佬大佬，有这篇论文的源码吗，能发我一份吗

继续更新啊

继续更新啊

请问找到了吗   你是做taxi dispatch的吗

repo: emliang/RL-for-Transportation


text:
First changes

Well done:wink:
The project is clear.
Congratulations!

Hey Emmanual, the project seems to be perfect. There's nothing I can suggest you to change since you've done a great job here.

thank you for your honest reviews

authors: Dorcas126 emmanuelsteven omer-creator

repo: emmanuelsteven/Portfolio


text:
Cleanup the old main code

All code now uses the Rust main as main entry. Would be good to remove all the other code which isn't used anymore.

Most of this has been fixed now

repo: emoon/ProDBG


text:
SourceCodeView 0.1

Features for 0.1:

Just displaying text pretty much, later on we need to support highlighting, etc

Moved to https://prodbg.phoreplay.com/T25


text:
auth_http

Describe the bug
A clear and concise description of what the bug is.
认证配置如下：
sources = [
{
type = simple
enable = true
users = [
{
username = "admin"
password = "public"
},
{
username = "client"
password = "public"
}
]
},
{
type = http
enable = true
auth_req {
url = "http://host.docker.internal:8088/mqtt/auth"
method = POST
headers.content-type = "application/json"
params = {clientid = "%c", username = "%u", password = "%P"}
}
timeout = 5s
connect_timeout = 5s
pool_size = 32
}
]
启动hauth_http后，认证链不生效，simple类型的认证没有起作用。
Expected behavior
根据认证链依次认证。
Actual Behavior
Describe what occurred.
To Reproduce
If possible include actual reproduction test code here.
Minimal C test cases are perferred.
** Environment Details **

NanoMQ version
Operating system and version
Compiler and language used
testing scenario

Client SDK
If possible include the mqtt sdk you used to connect to nanomq
Minimal C test cases are perferred.
Additional context
Add any other context about the problem here.

Hi Bro  @AetheWu，I suspect you are the victim of our inconsistency doc. We are in a rushing mode of updating the Docs, for now, docs is not matched with the most updated version 0.18.2, if you are using such ver. Recommend to use the classical way of configuration nanomq start --old_conf nanomq_old.conf.
Hi 兄台， 我怀疑你被错误的文档误导了，目前nanomq正处在文档和配置重构阶段，文档里的HOCON 配置文件描述与之前发布的0.18.2 版本并不匹配，是我们即将发布的 0.19.0 版本。 目前推荐您使用 原有的配置文件格式：nanomq start --old_conf nanomq_old.conf。

nanomq-auth.txt
My old configuration file is attached.
I can successfully query my HTTP server for authentication:

close due to idle

authors: AetheWu JaylinYu

repo: emqx/nanomq


text:
Add debugging hooks/ways to extract and manipulate state at runtime

Would be awesome to have for instance voice solo/mutes, individual voice output, etc.

This is all being done progressively on the dbg branch for this project: https://github.com/yupferris/snes-apu-dbg

repo: emu-rs/snes-apu


text:
FORTECH-61: Bug fixing for caption position overlay

Fixed position for caption when 'captionPosition'=overlay
Changed 'line-height' according to GUI design
Enact-DCO-1.0-Signed-off-by: Adrian Cocoara adrian.cocoara@lgepartner.com

@adrian-cocoara-lgp , Thanks for fixing! Please find my comments below.
The box that contains the overlay caption looks smaller than the image.

I'm not sure but shouldn't the caption starts from the bottom of the image? If the caption is short, it looks too above.

Should the overlayed caption marquee or not? WDYT?

Hello @MikyungKim
Regarding your first comment about caption starting from bottom. I agree, for this I added a min-height and max-height for .captionOverlay
And the second, if we apply Marquee for overlayed caption, we won't be able to display caption on multiple rows.
What do you think?

authors: MikyungKim adrian-cocoara-lgp

repo: enactjs/agate


text:
Interpret Early Rewards not Possible tx error

this error is not caught yet for some reason, and we display the plain enum as tx error, which does not mean much to the end user.

Use in context website anchor link.

authors: Malixxa clangenb

repo: encointer/encointer-wallet-flutter


text:
EoL of .NET Core 3.1 is final

Removed the note. I don't this is true (anymore)

LTS releases get free support and patches for 3 years.

https://dotnet.microsoft.com/platform/support/policy/dotnet-core

You are right, that changed for .NET Core 3.1, thanks for the update.


text:
[postgresql] Automate releaseDate and eol retrieval

Based on https://www.postgresql.org/support/versioning/.

Expected diff:
diff --git i/releases/postgresql.json w/releases/postgresql.json
index 1059123..407c64d 100644
--- i/releases/postgresql.json
+++ w/releases/postgresql.json
@@ -1,5 +1,141 @@
 {
-  "releases": {},
+  "releases": {
+    "9.6": {
+      "name": "9.6",
+      "releaseDate": "2016-09-29",
+      "eol": "2021-11-11"
+    },
+    "9.5": {
+      "name": "9.5",
+      "releaseDate": "2016-01-07",
+      "eol": "2021-02-11"
+    },
+    "9.4": {
+      "name": "9.4",
+      "releaseDate": "2014-12-18",
+      "eol": "2020-02-13"
+    },
+    "9.3": {
+      "name": "9.3",
+      "releaseDate": "2013-09-09",
+      "eol": "2018-11-08"
+    },
+    "9.2": {
+      "name": "9.2",
+      "releaseDate": "2012-09-10",
+      "eol": "2017-11-09"
+    },
+    "9.1": {
+      "name": "9.1",
+      "releaseDate": "2011-09-12",
+      "eol": "2016-10-27"
+    },
+    "9.0": {
+      "name": "9.0",
+      "releaseDate": "2010-09-20",
+      "eol": "2015-10-08"
+    },
+    "8.4": {
+      "name": "8.4",
+      "releaseDate": "2009-07-01",
+      "eol": "2014-07-24"
+    },
+    "8.3": {
+      "name": "8.3",
+      "releaseDate": "2008-02-04",
+      "eol": "2013-02-07"
+    },
+    "8.2": {
+      "name": "8.2",
+      "releaseDate": "2006-12-05",
+      "eol": "2011-12-05"
+    },
+    "8.1": {
+      "name": "8.1",
+      "releaseDate": "2005-11-08",
+      "eol": "2010-11-08"
+    },
+    "8.0": {
+      "name": "8.0",
+      "releaseDate": "2005-01-19",
+      "eol": "2010-10-01"
+    },
+    "7.4": {
+      "name": "7.4",
+      "releaseDate": "2003-11-17",
+      "eol": "2010-10-01"
+    },
+    "7.3": {
+      "name": "7.3",
+      "releaseDate": "2002-11-27",
+      "eol": "2007-11-27"
+    },
+    "7.2": {
+      "name": "7.2",
+      "releaseDate": "2002-02-04",
+      "eol": "2007-02-04"
+    },
+    "7.1": {
+      "name": "7.1",
+      "releaseDate": "2001-04-13",
+      "eol": "2006-04-13"
+    },
+    "7.0": {
+      "name": "7.0",
+      "releaseDate": "2000-05-08",
+      "eol": "2005-05-08"
+    },
+    "6.5": {
+      "name": "6.5",
+      "releaseDate": "1999-06-09",
+      "eol": "2004-06-09"
+    },
+    "6.4": {
+      "name": "6.4",
+      "releaseDate": "1998-10-30",
+      "eol": "2003-10-30"
+    },
+    "6.3": {
+      "name": "6.3",
+      "releaseDate": "1998-03-01",
+      "eol": "2003-03-01"
+    },
+    "16": {
+      "name": "16",
+      "releaseDate": "2023-09-14",
+      "eol": "2028-11-09"
+    },
+    "15": {
+      "name": "15",
+      "releaseDate": "2022-10-13",
+      "eol": "2027-11-11"
+    },
+    "14": {
+      "name": "14",
+      "releaseDate": "2021-09-30",
+      "eol": "2026-11-12"
+    },
+    "13": {
+      "name": "13",
+      "releaseDate": "2020-09-24",
+      "eol": "2025-11-13"
+    },
+    "12": {
+      "name": "12",
+      "releaseDate": "2019-10-03",
+      "eol": "2024-11-14"
+    },
+    "11": {
+      "name": "11",
+      "releaseDate": "2018-10-18",
+      "eol": "2023-11-09"
+    },
+    "10": {
+      "name": "10",
+      "releaseDate": "2017-10-05",
+      "eol": "2022-11-10"
+    }
+  },
   "versions": {
     "16.2": {
       "name": "16.2",


text:
Update http4s-async-http-client, ... to 0.23.3

Updates

org.http4s:http4s-async-http-client
org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-client
org.http4s:http4s-core
org.http4s:http4s-dsl

from 0.23.1 to 0.23.3.
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Superseded by #913.


text:
better error responses

Fix: Nested filter breaks without load option
Add: Included load_path on sort and filter error types to show which subquery these errors belong to
Use sqlite

Pull Request Test Coverage Report for Build 5ac72e163d6f71f0290f8a468f5169e20d4ea328-PR-7

26 of 26 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 0356b35feed5e165b5fd6533382820dbeb7f1ef8:
0.0%

Covered Lines:
127

Relevant Lines:
127

💛  - Coveralls

authors: coveralls enewbury

repo: enewbury/quarry


text:
Add a License

Hey, @engamo, I wonder what type of license you want to add to this project.

Thanks @engamo, you are the best I added the license file.

repo: engamo/github-project-testing


text:
pkg(php): Added php 7.4.15 8.0.2

#101

I get:
== Run ==
STDERR
    /piston/packages/php/8.0.2/run: line 1: php8.0: command not found

Exit Code: 127

I assume the run file shouldn't be containing ${VERSION_MINOR}

closing and opening to test CI

authors: HexF ThreshMain

repo: engineer-man/piston


text:
Attaching to Matrix returns error

First off, great plugin! It works when I attach it to an entry, but I would like to attach it to matrix blocks within the entry. When I do though, I receive the following error:
Internal Server Error
Property "Craft\MatrixBlockModel.author" is not defined.
My code within my block loop is:
 {% set params = {order: 'dateCreated asc',} %} {{ craft.comments.form(block.id, params) }}

Cool idea! I haven't testing things out with Matrix, so there's bound to be a few issues like that. I'll test and organise support for this.

@engram-design Awesome! Glad I could contribute, I was worried you had already implemented this and I was just missing something.

I've put some checks in place for comments on Matrix (and other fields with an owner) in 0.4.6, but please re-open this issue (or create a new one) if you have any more issues.

authors: engram-design tosegard

repo: engram-design/Comments


text:
🛑 Econtips is down

In 2739d87, Econtips (https://econtips.com) was down:

HTTP code: 500
Response time: 598 ms

Resolved: Econtips is back up in 249ceee after 10 minutes.

repo: enlivenonedrive/upptime


text:
Throw Error in _do_exploit_run

https://github.com/enowars/enochecker_test/blob/21b255fc2a1cb13cbf252990f71605d4821e21f7/enochecker_test/tests.py#L541
It catches all errors, also if e.g. the Request times out:
https://github.com/enowars/enochecker_test/blob/21b255fc2a1cb13cbf252990f71605d4821e21f7/enochecker_test/tests.py#L560-L561
It shouldn't

That's by design (even if YOLO): we don't specify which exploit belongs to which flagstore, so we just run them all and ignore failures.
We could store all exceptions and log them if all fail, I guess?

well, that's the only place there is an except, every other function throws.

authors: DanielHabenicht domenukk


text:
Update rules.mdx

Include hyperlink to Working Group Rules
Link to PR: https://github.com/ensdomains/docs/pull/207

Merged #207

repo: ensdomains/docs


text:
Improve calls to user profile and load times.

This PR fixes a bug where the user profile was fetched on every single change of pagination on a user's gallery.
It also removes a loading state from the whole page.
Here is a video to see the improvements in action
https://share.vidyard.com/watch/AvB2BMhMGvYHiidvQWa5ca?

Looks great, thanks!

authors: dabitCoder entmike

repo: entmike/fd-web-ui


text:
[Documentation] Clarify if the files specified by -e are read in addition to, or instead of the default ones

As per the title, this passus in the README is unclear. I don't know if the word "another" is used in the sense of "a different one", or in the sense of "one more". Depending on the exact sense, it would mean that the file specified with -e will be processed instead of the default one or in addition to the default one, respectively.

Updated

authors: entropitor rulatir

repo: entropitor/dotenv-cli


text:
Support windows

Fixes #134
This makes it possible to install StackMaster natively on Windows. It requires that when we release a Gem though that we build two versions, one on Mac (also works on Linux) and one on Windows. By shipping both versions to RubyGems, when a user runs gem install stack_master it will prefer one that is specifically built for their platform over the universal gem. If however we just release the universal gem, users on Windows will get the same error they do today and will have to run gem install stack_master --platform x86-mingw32.
I'm thinking of having some internal build servers at Envato do this for us, so we don't have to spin up a Windows machine just to build a Gem, but at the moment I am just doing this on a WorkSpace host.
EDIT:
In 2.0 we plan to remove dotgpg support for something else. When that's done we can have the same gem for all platforms.

Looks like we have some code that isn't native either, I'll put this in WIP for now https://github.com/envato/stack_master/blob/master/lib/stack_master/commands/terminal_helper.rb#L5

The tests pass on Windows now, although Travis CI doesn't support it so you'll just have to take my word for it.

Any thoughts on rewriting the GPG secret resolver to shell out instead of use GPGme? Then the resolver will work on all platforms and you can keep a single global release. Just a thought - I have no horse in this race 😄

Shelling out is a path to the dark side. If there's no other option I'd be OK but I suspect there are better options I have not explored yet.

I have no objection. It just seems like a lot of work setting up build servers and maintaining two different code paths just to continue supporting a resolver.
Another option would be to remove the secret resolver from stack_master itself, but give directions on how to incorporate it locally in a project for anyone who is using it.
Or you could cut a 2.x branch that removes the resolver and supports windows and maintain two versions. This also introduces complexity, though.
These are just ideas. What you have looks great...it just seems it's going to introduce the overhead of pipelines to release a new version.

@rbayerl oh yes, I added this to the PR description after the fact:

In 2.0 we plan to remove dotgpg support for something else. When that's done we can have the same gem for all platforms.

authors: patrobinson rbayerl


text:
🛑 Envesko Cloud - HTTPS is down

In 4777e54, Envesko Cloud - HTTPS (https://envesko.cloud) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Envesko Cloud - HTTPS is back up in 9790bc6 after 1 hour, 16 minutes.

repo: envesko/status


text:
bazel 3.7.0 iOS issues

Updating bazel to 3.7.0 or later creates the following errors in the iOS builds:
ERROR: /Users/jnino/src/envoy-mobile/library/swift/src/BUILD:5:23: every rule of type _swift_static_framework implicitly depends upon the target '@bazel_tools//tools/objc:libtool', but this target could not be found because of: no such target '@bazel_tools//tools/objc:libtool': target 'libtool' not declared in package 'tools/objc' (did you mean 'libtool.sh'?) defined by /private/var/tmp/_bazel_jnino/e2e6858b12cc5d95c5e2dcf9dce57ac4/external/bazel_tools/tools/objc/BUILD
ERROR: Analysis of target '//:ios_dist' failed; build aborted: Analysis failed
INFO: Elapsed time: 17.452s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (12 packages loaded, 11 targets configured)

I have tested with the 0.18.0 release of rules_swift and the 0.21.2 release of rules_apple.

cc @keith

cc @keith

Is envoy using the toolchain from rules_cc? if so that needs to be updated

Is envoy using the toolchain from rules_cc? if so that needs to be updated

Upstream Envoy? If I understand the bazel definitions correctly, yes. All the cc_* defs in envoy use cc_* defs loaded from @rules_cc under the hood.

Upstream Envoy? If I understand the bazel definitions correctly, yes. All the cc_* defs in envoy use cc_* defs loaded from @rules_cc under the hood.

not just the rules but the toolchain itself, rules_cc has a crosstool checked in that's kinda sorta a copy of the one from bazel

not just the rules but the toolchain itself, rules_cc has a crosstool checked in that's kinda sorta a copy of the one from bazel

it required an update at the time https://github.com/bazelbuild/rules_cc/pull/82

it required an update at the time https://github.com/bazelbuild/rules_cc/pull/82

Ah nevermind, this is invalid now https://github.com/envoyproxy/envoy-mobile/blob/9543bd6a84297df02652b84c16f19a4c9b1633c7/bazel/swift_static_framework.bzl#L135

Ah nevermind, this is invalid now https://github.com/envoyproxy/envoy-mobile/blob/9543bd6a84297df02652b84c16f19a4c9b1633c7/bazel/swift_static_framework.bzl#L135

I removed it from bazel here https://github.com/bazelbuild/bazel/commit/f8b51ffc2a8a953f64657ae4a21c9e1f1793dae2

I removed it from bazel here https://github.com/bazelbuild/bazel/commit/f8b51ffc2a8a953f64657ae4a21c9e1f1793dae2

Can you test your upgrade branch with this? https://github.com/envoyproxy/envoy-mobile/pull/1234

Can you test your upgrade branch with this? https://github.com/envoyproxy/envoy-mobile/pull/1234

repo: envoyproxy/envoy-mobile


text:
http and threading: split Http::Dispatcher monolith into parts

The Http::Dispatcher has grown quite a bit since its inception. It currently handles

upstream HTTP bridging
downstream HTTP bridging
cross-thread dispatch to Envoy across engine lifecycle

At minimum it would be good to split 3) into a generic dispatch mechanism, but likely 1) and 2) can be split out as well. This would help separate concerns and make dispatch generally available to non-HTTP calls.

Fixed by https://github.com/envoyproxy/envoy-mobile/pull/1416


text:
How to see the circuit breaker statistics of  dynamic cluster from SDS ?

@mattklein123  Looking forward to your help.
The envoy version is 1.10.  By following the wiki  Statistics overview, I can't see the circuit breaker  statistics of dynamic cluster from SDS, such as my-foo-cluster , via the GET /stats command in envoy container, but I can see the statistics  of  the cluster xds-grpc that is static cluster.

It's likely you didn't have the correct statsMatches including what you expected.
BTW: 1.10 is an ancient version and it has been EOL for more than 6 months.

repo: envoyproxy/envoy