Console firing off ollama and other errors (using openrouter and claude)

Describe the bug
hey guys,
my local instance of bolt, is having issues creating anything but basic text..
I initially tried with importing a folder, which didn't work, which made me create a detailed MD file (which I needed to do anyway).
I installed ottodev in a new folder, not in docker, have changed the my env.whatever-it-was to just .env, and I can see openrouters is taking credits away from me, from both Qwen 2.5 coder, and then thinking that was the main issue, cluade 3.5 latest.
console is as follows:
C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm  main  -1  git pull
remote: Enumerating objects: 210, done.
remote: Counting objects: 100% (187/187), done.
remote: Compressing objects: 100% (40/40), done.
remote: Total 126 (delta 100), reused 104 (delta 78), pack-reused 0 (from 0
Receiving objects: 100% (126/126), 18.34 KiB | 2.29 MiB/s, done.
Resolving deltas: 100% (100/100), completed with 37 local objects.
From https://github.com/coleam00/bolt.new-any-llm

[new branch]      pr/332     -> origin/pr/332
Already up to date.
C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm  main  -1  pnpm install
Lockfile is up to date, resolution step is skipped
Already up to date

bolt@ prepare C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm
husky

Done in 1.6s
C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm  main  -1  pnpm run dev

bolt@ dev C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm
remix vite:dev

warn  Data fetching is changing to a single fetch in React Router v7
┃ You can use the v3_singleFetch future flag to opt-in early.
┃ -> https://remix.run/docs/en/2.13.1/start/future-flags#v3_singleFetch
┗
➜  Local:   http://localhost:5173/
➜  Network: use --host to expose
➜  press h + enter to show help
Error getting Ollama models: TypeError: fetch failed
at node:internal/deps/undici/undici:13179:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Object.getOllamaModels [as getDynamicModels] (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:318:22)
at async Promise.all (index 0)
at Module.initializeModelList (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:389:9)
at handleRequest (C:/Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/entry.server.tsx:30:3)
at handleDocumentRequest (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:340:12)
at requestHandler (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:160:18)
at C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:70:25 {
[cause]: AggregateError:
at internalConnectMultiple (node:net:1116:18)
at afterConnectMultiple (node:net:1683:7)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ECONNREFUSED',
[errors]: [ [Error], [Error] ]
}
}
Error getting Ollama models: TypeError: fetch failed
at node:internal/deps/undici/undici:13179:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Object.getOllamaModels [as getDynamicModels] (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:318:22)
at async Promise.all (index 0)
at Module.initializeModelList (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:389:9)
at handleRequest (C:/Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/entry.server.tsx:30:3)
at handleDocumentRequest (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:340:12)
at requestHandler (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:160:18)
at C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:70:25 {
[cause]: AggregateError:
at internalConnectMultiple (node:net:1116:18)
at afterConnectMultiple (node:net:1683:7)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ECONNREFUSED',
[errors]: [ [Error], [Error] ]
}
}
Error getting Ollama models: TypeError: fetch failed
at node:internal/deps/undici/undici:13179:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Object.getOllamaModels [as getDynamicModels] (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:318:22)
at async Promise.all (index 0)
at Module.initializeModelList (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:389:9)
at handleRequest (C:/Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/entry.server.tsx:30:3)
at handleDocumentRequest (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:340:12)
at requestHandler (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:160:18)
at C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:70:25 {
[cause]: AggregateError:
at internalConnectMultiple (node:net:1116:18)
at afterConnectMultiple (node:net:1683:7)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ECONNREFUSED',
[errors]: [ [Error], [Error] ]
}
}
Error getting Ollama models: TypeError: fetch failed
at node:internal/deps/undici/undici:13179:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Object.getOllamaModels [as getDynamicModels] (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:318:22)
at async Promise.all (index 0)
at Module.initializeModelList (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:389:9)
at handleRequest (C:/Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/entry.server.tsx:30:3)
at handleDocumentRequest (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:340:12)
at requestHandler (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:160:18)
at C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:70:25 {
[cause]: AggregateError:
at internalConnectMultiple (node:net:1116:18)
at afterConnectMultiple (node:net:1683:7)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ECONNREFUSED',
[errors]: [ [Error], [Error] ]
}
}
Error getting Ollama models: TypeError: fetch failed
at node:internal/deps/undici/undici:13179:13
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at Object.getOllamaModels [as getDynamicModels] (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:318:22)
at async Promise.all (index 0)
at Module.initializeModelList (C:/_Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/utils/constants.ts:389:9)
at handleRequest (C:/Vault-G14/AI/BetterBolt/3/bolt.new-any-llm/app/entry.server.tsx:30:3)
at handleDocumentRequest (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:340:12)
at requestHandler (C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+server-runtime@2.15.0_typescript@5.7.2\node_modules@remix-run\server-runtime\dist\server.js:160:18)
at C:_Vault-G14\AI\BetterBolt\3\bolt.new-any-llm\node_modules.pnpm@remix-run+dev@2.15.0@remix-run+react@2.15.0_react-dom@18.3.1_react@18.3.1__react@18.3.1_typ_zyxju6yjkqxopc2lqyhhptpywm\node_modules@remix-run\dev\dist\vite\cloudflare-proxy-plugin.js:70:25 {
[cause]: AggregateError:
at internalConnectMultiple (node:net:1116:18)
at afterConnectMultiple (node:net:1683:7)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
code: 'ECONNREFUSED',
[errors]: [ [Error], [Error] ]
}
}
Sorry for all that, wasn't sure what would be best to use.
I did notice when I was using bolt.new, that from my current location in SEA, I was unable to use it. So I tried VPNing into US/AU/IE but nothing...
If I go into the bolt terminal, and CTRL C, it autoreboots to what seems to be an earlier version of the code when it was just testing sime text to let me know it was working. Asks me to press the stop button to kill the server, but I can't see one.
I'm sure this is a me issue and not a bolt issue.
Standard install was done with Admin PS:
git clone https://github.com/coleam00/bolt.new-any-llm.git
pnpm install
pnpm run dev
I have api's setup in the .env for more than one LLM (currently OpenAI, Anthropic, Gemini, Open Router and XAI) was unsure whether the values needed to be contained within the quotation marks which Open Router is, and is woking, so I've stuck to that.
I have Ollama installed on my PC, but not running, as in killed from system tray.
Upon start I do get this everytime:
warn  Data fetching is changing to a single fetch in React Router v7
┃ You can use the v3_singleFetch future flag to opt-in early.
┃ -> https://remix.run/docs/en/2.13.1/start/future-flags#v3_singleFetch
but as it all loaded okay, didn't think it was an issue.
It's got to be a me issue. OpenRouter is taking next to nothing money wise, I notice that the node_module folder isn't there, try to run a npm install, but nothing.
It's gotta be a me thing. Just don't know where, hope ya'll can help me, or someone else like me who may run into this in the future.
Here's some images:
https://tinyurl.com/28hfkv2f
https://tinyurl.com/2yqwywhv
https://tinyurl.com/2ab3cvsd
PS tried shadcn, tailwind, and others...
Link to the Bolt URL that caused the error
https://k03e2io1v3fx9wvj0vr8qd5q58o56n-fkdo--5173--fc837ba8.local-corp.webcontainer-api.io
Steps to reproduce
Just what was mentioned above
Expected behavior
creation of a visual component otheer than just text
Screen Recording / Screenshot
No response
Platform
Windows 11 Pro
Chrome Latest as of Dec 4
Provider Used
Anthropic
Model Used
Cluade Sonnet 3.5 new, but tried others
Additional context
No response

ollama error is fine its just an warning, as it tried and failed to load ollama models because ollama is not running on your system


Relax arithmetic rules in case only one audio object is involved

Which issue(s) are closed by this pull request?
Closes #587
Changes proposed in this pull request:

Bypass rules for fft norm if only one audio object is involved in the opeeration

For discussion
I discovered that we had a test that explicitly does not allow 1/signal if the FFT norm is not 'none'. I did not remove this test yet. Do we want to stay hard?
ToDo

[ ] check/add tests

Thank you for fixing! How about testing if its really working, to make sure it will work in future as well.

I did a quick check locally, and everything works. I'll add it if we decide to change the behaviour - I added a todo in the PR description to make sure we dont forget. Just didn't want to do too much work that might be discarded :)

@ahms5 implemented your changes as suggested. Now I'm waiting for the weekly before changing any tests


Add questionnaire customization documentation in wiki

Describe the Issue
After adding questionnaire customization support in #633. We need documentation in the wiki on how to customize the questionnaire.
The documentation is ready and can be retrieved from here
Would you like to work on the issue?
It should be someone that has permission to edit the wiki

Closing this since it has been added


Write a guide

Write user manual for the software like what steps a user should follow in order to use the software.

I would like to work on this issue.


Add API for pdf preview

Description

Added a pdf/preview API that simply returns the generated PDF as application/pdf instead of saving to storage. This is currently disabled in prod just in case, since there is no distinction between the preview and the "real" PDF. And currently the intent is only to be able to get proper PDF preview in dev tools. It also looks for a frontendVersion cookie and passes this along if the app is running in LocalTest; it also rewrites locahost -> host.containers.internal so podman and docker can access a locally running app-frontend.
To check for prod I used IWebHostEnvironment.IsProduction(), I have not tested this in prod, but I saw the equivalent IsDevelopment() was used elsewhere so I assumed this was the way to do it.
Related Issue(s)

#{issue number}

Verification

[x] Your code builds clean without any errors or warnings
[x] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Ja, da gjenstår det "bare" å skrive noen tester.

Ja, da gjenstår det "bare" å skrive noen tester. (Jeg kan se på det. Ikke nødvendig at du setter deg inn i dotnet testing om du ikke har veldig lyst)

Jeg gir det gjerne et forsøk først, har skrevet noen tester før

Kjør på men spør i stedet for å bruke masse tid på å stå fast da.


INearbyExposureNotificationService.aidl looks wrong

Hi, I don't use microg myself, but did some reversing work on GMS EN Binder interface.
https://github.com/microg/android_packages_apps_GmsCore/blob/master/play-services-nearby-api/src/main/aidl/com/google/android/gms/nearby/exposurenotification/internal/INearbyExposureNotificationService.aidl
In the file above some methods are missing, also I wonder why the transaction codes start from 0 (instead of 1).
I have attached a screenshot from my code for comparison (for code 14 and 19, the 'Params' suffix has to be removed).
Hope this helps, cheers MaMe82

The interface file you are referring to is in AIDL format. The first valid transaction code for user commands in binder transactions is 1 (see FIRST_CALL_TRANSACTION). The number in AIDL specifies the offset from FIRST_CALL_TRANSACTION, thus 0 in AIDL means 1 in the binder interface.
AIDL interfaces do not need to include all methods. It's completely fine if some of them are missing as long as the associated transaction number matches. The reason why some methods show up in your reverse engineered list and not in microG's AIDL, is probably that these methods are not exposed in the gms client library but only used internally within Google apps (e.g. the resetAllData is called by a menu option in Google Settings, but cannot be invoked by apps using EN API). In microG we don't expose internal functions in public AIDL interfaces, so there is no need to reproduce them.
With regards to the name: AIDL interfaces do not include any method names, but instead only use transaction call codes. As such it doesn't matter at all how we name the method, it still stays completely compatible as long as we associate the same semantic meaning with a transaction call code. As the method names are typically obfuscated in the published gms binaries, it's actually very common for those names to mismatch as they are only "guessed" either from the client function call involved or by their meaning.

Thank you for clarifying the relevant aspects on AIDL.
In fact I was totally unaware that the numbering describes the offset from IBinder.FIRST_CALL, instead of the transaction code used in BINDER_WRITE_READ IOCTLs (I am aiming at the latter in my project).
This also helps me to sort out some past issues I ran into, when manually interpreting publicly available AIDL files, to conclude for corresponding transaction codes.
Thx for shedding some light, gonna close this


Simplifying Homebrew terminology

Provide a detailed description of the proposed feature
Homebrew should reduce the number of metaphors it uses in its user interface and documentation.
We currently demand that users internalize several metaphors when interacting with Homebrew. These include:

Formula (how to build a bit of software)
Bottle (pre-built software)
Cask (pre-built software on macOS)
Tap (a collection of software)
Keg (where software installs itself)
Cellar (where all my software install themselves)

As well as an additional number of less-common metaphors that contributors and maintainers need to know, like Rack, Tab, and Formulary.
I propose that we reduce the number of user-facing metaphors to Formula, Bottle, Cask, and Tap. That is to say, the output of any given brew command, and all documentation on docs.brew.sh, should avoid mentioning kegs or cellars. The only exception should be for maintainer-focused documentation and commands, and there the metaphors should only be used if they would otherwise cause unnecessary confusion.
What is the motivation for the feature?
As we no longer support commands like brew diy and brew switch, the Keg/Cellar/Formula distinction is unnecessarily confusing. Formula should only be "something I want to install" and the only additional bits of information users need to know about them is "where do I get it from" (Tap), "do I need to build it myself" (Bottle), and "will it be put in my PATH" (keg-only).
We can convey the information about whether something will be in their PATH without needing to introduce an entirely new metaphor for it. There is already a suitable metaphor we commonly use, and one that is more obvious for existing Terminal users: "linked". Note that the Cellar metaphor doesn't come up at all here, since the real path of where a bit of software is installed is arguably not relevant for users.
I therefore believe Keg and Cellar are less-useful concepts for users. The only need for those two terms, with respect to users, is whether some software they are interested in is linked into HOMEBREW_PREFIX or not. Asking users to learn two new metaphors for a feature that only provides one bit of information is unnecessary.
 % brew info openssl
<EMAIL_ADDRESS>stable 1.1.1j (bottled) [keg-only]
<EMAIL_ADDRESS>stable 1.1.1j (bottled) [unlinked]
 Cryptography and SSL/TLS Toolkit
 https://openssl.org/
<EMAIL_ADDRESS>(8,071 files, 18.5MB)
<EMAIL_ADDRESS>(1.1.1j, 8,071 files, 18.5MB)
   Poured from bottle on 2021-02-19 at 15:57:12
 From<EMAIL_ADDRESS> License: OpenSSL
 ==> Caveats
 A CA file has been bootstrapped using certificates from the system
 keychain. To add additional certificates, place .pem files in
<EMAIL_ADDRESS>
 and run
<EMAIL_ADDRESS>
<EMAIL_ADDRESS>is keg-only, which means it was not symlinked into /usr/local,
-because macOS provides LibreSSL.
-
<EMAIL_ADDRESS>was not linked into /usr/local because macOS provides LibreSSL.
 If you need to have<EMAIL_ADDRESS>first in your PATH, run:
   echo 'export PATH="/usr/local/opt/openssl@1.1/bin:$PATH"' >> ~/.zshrc

 For compilers to find<EMAIL_ADDRESS>you may need to set:
   export<EMAIL_ADDRESS>   export<EMAIL_ADDRESS>
 % brew unlink openssl
-Unlinking<EMAIL_ADDRESS>0 symlinks removed.
<EMAIL_ADDRESS>is already unlinked, because macOS provides LibreSSL.

How will the feature be relevant to at least 90% of Homebrew users?
Less cognitive load when learning and using Homebrew from novel metaphors.
What alternatives to the feature have been considered?
Retaining our currently terminology.

I like the idea of simplifying terminology. However, I think "keg-only" is one of the few pieces that don't need simplification. I've seen very little confusion about what exactly it means, most likely because it's already explained clearly in any instance where a user encounters it. That explanation is useful for users who go on to read formula files that say keg_only.

Another thing I've seen is how the word "formula" can refer to either the file itself (e.g. the contents of homebrew-/Formula/*), or what it installs in /usr/local/Cellar (aka Kegs) or as a general term encompassing both traditional formula files and cask files; each of which usually relies on context to distinguish.

I'm definitely in favor of doing something like this. Tbh I still don't really understand why Formulary is called Formulary 😅
I'm torn about using keg-only vs unlinked. I think there's still a slight distinction between the two. keg-only means "unlinked by default" while unlinked, to me, just means "not linked due to either being keg-only or manually unlinking". So even if the terminology keg-only is dropped (which I would be fine with), I think it's still good to have that distinction.
Also, if keg-only is dropped, I think I'd push to deprecate and rename the keg_only formula DSL.

To me, the weird thing about Formula and Cask are that I see them as similar types of "things" (i.e. software) but their names don't quite fit the same analogy. To me, Formula makes me think "recipe for some software", so it seems like it should refer to the formula definition (i.e. the file). Cask, on the other hand, feels like a more physical object (i.e. the actual "finished product") seemingly referring to the installed application.
Documentation/messaging-wise, I think we can certainly use terms like "installed formula", "formula definition", "installed cask", and "cask definition" to help eliminate potential confusion. I don't think major code changes that rename classes and stuff are necessarily a good idea, though.

End of important stuff, no need to keep reading. I wrote the following and then realized it's not really useful to us unless we decide to re-make Homebrew and change a whole bunch of stuff, but figured I'd leave it in just because.
I guess if I were making Homebrew from scratch and needed to follow the beer theme, I'd make Formula refer to any software definition. Cask would then be a type of Formula that installs native apps, and something else would also be a type of Formula that refers to the software in the homebrew/homebrew-core repo. I'm not going to bother researching beer-related things to figure out what that should be, though, because it doesn't matter.

I think this is one of the cases where if we could do a usability study it would help a lot in terms of figuring out what actually is confusing for users. Based on just what I see from the years of reading twitter, reddit, and the orange site, keg-only and cellar are the terms that cause the most confusion, followed by the formula vs cask distinction. I don't think there's a whole lot we can do for the latter but certainly for the former we can simplify things.

Another thing I've seen is how the word "formula" can refer to either the file itself (e.g. the contents of homebrew-/Formula/*), or what it installs in /usr/local/Cellar (aka Kegs) or as a general term encompassing both traditional formula files and cask files; each of which usually relies on context to distinguish.

My idea for this would be to simply drop the use of "formula" to refer to the file on disk (=build recipe) and instead use the proposed definition in the original issue ("something I want to install"). Older terminology that's mostly been excised from the codebase refers to "software built from a Formula (=build recipe)" as "brews", in the sense that "brews that homebrew distributes" (=bottles), but I don't really want to revive that since that only increases confusion.

I'm torn about using keg-only vs unlinked. I think there's still a slight distinction between the two. keg-only means "unlinked by default" while unlinked, to me, just means "not linked due to either being keg-only or manually unlinking". So even if the terminology keg-only is dropped (which I would be fine with), I think it's still good to have that distinction.

This is basically what I'm proposing -- the only info that "keg-only" provides is linked by default vs not linked by default. We can convey this knowledge without introducing jargon like keg-only. We can do this because (to my knowledge) the links present in /usr/local/opt stay there even if you run brew unlink wget for example.

To me, the weird thing about Formula and Cask are that I see them as similar types of "things" (i.e. software) but their names don't quite fit the same analogy. To me, Formula makes me think "recipe for some software", so it seems like it should refer to the formula definition (i.e. the file). Cask, on the other hand, feels like a more physical object (i.e. the actual "finished product") seemingly referring to the installed application.

Yeah, the formula <-> bottle <-> cask distinction is extremely confusing as both bottle and cask are talking about binary redistributions of software, but they are very different in practice.

Documentation/messaging-wise, I think we can certainly use terms like "installed formula", "formula definition", "installed cask", and "cask definition" to help eliminate potential confusion. I don't think major code changes that rename classes and stuff are necessarily a good idea, though.

What is also quite confusing is that we actually have a distinction between “formula definition” (Formula) and “installed formula” (Keg) in code but for casks both use the Cask class.

Tbh I still don't really understand why Formulary is called Formulary 😅

A factory for formula.

I'm torn about using keg-only vs unlinked. I think there's still a slight distinction between the two. keg-only means "unlinked by default" while unlinked, to me, just means "not linked due to either being keg-only or manually unlinking". So even if the terminology keg-only is dropped (which I would be fine with), I think it's still good to have that distinction.

Agreed.

To me, the weird thing about Formula and Cask are that I see them as similar types of "things" (i.e. software) but their names don't quite fit the same analogy. To me, Formula makes me think "recipe for some software", so it seems like it should refer to the formula definition (i.e. the file). Cask, on the other hand, feels like a more physical object (i.e. the actual "finished product") seemingly referring to the installed application.

I think it would be good to have a name we use consistently when we describe both e.g. "package".

Despite the (brilliant) write up by @jonchang I'm mildly 👎🏻 on this. I think the ship has somewhat sailed here and we run a risk of further confusing people by removing the keg/cellar metaphors. I feel more strongly about not removing references to "cellar" than "keg" because the prior is literally the name of a location on disk.

That is to say, the output of any given brew command, and all documentation on docs.brew.sh, should avoid mentioning kegs or cellars. The only exception should be for maintainer-focused documentation and commands, and there the metaphors should only be used if they would otherwise cause unnecessary confusion.

A middle ground I'd be neutral (maybe even positive if you catch me on a really good day) rather than 👎🏻 on would be removing them from all end-user documentation focused and commands but keeping them in all contributor/developer documentation and commands.

This has been over a year with no movement so we're gonna pass for now. Thanks for the discussion, all.


Remove references to desktop app

Closed with https://github.com/ubiq/pyrus/commit/4ea5aca2504937f282793465f0d7f7da76e04998


Expose BrowserPerformanceClient and BrowserPerformanceMeasurement artifacts as public

Expose BrowserPerformanceClient and BrowserPerformanceMeasurement artifacts as public.
Remove redundant BrowserPerformanceClient params.

Codecov Report

Merging #6273 (7e6def5) into dev (81d34b4) will increase coverage by 10.64%.
Report is 220 commits behind head on dev.
The diff coverage is 96.63%.

Flag
Coverage Δ

msal-angular
96.73% <96.63%> (+0.22%)
:arrow_up:

msal-browser
?

msal-common
?

msal-core
?

msal-node
?

msal-node-extensions
?

msal-react
94.24% <ø> (-0.45%)
:arrow_down:

node-token-validation
?

Files Changed
Coverage Δ

lib/msal-angular/src/msal.guard.ts
90.78% <90.78%> (+0.64%)
:arrow_up:

lib/msal-angular/src/msal.navigation.client.ts
93.33% <92.85%> (+0.47%)
:arrow_up:

lib/msal-angular/src/constants.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/msal.broadcast.service.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/msal.interceptor.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/msal.module.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/msal.redirect.component.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/msal.service.ts
100.00% <100.00%> (ø)

lib/msal-angular/src/packageMetadata.ts
100.00% <100.00%> (ø)

... and 219 files with indirect coverage changes


Should maybe use a null-prototype object instead of {} as the start?

This probably deserves some discussion but that would be my inclination.

The thing with ES5 is that descriptors don't suffer inheritance, descriptor does.
Meaning that Object.prototype.writable = true affect every single descriptor, even if returned by Object.getOwnpropertyDescriptor but it will be ignored in both Object.defineProperties and Object.create second argument.
The TL;DR version is that starting from null won't add any value but it will cause easy troubles when an object is cast as string (or some hasOwnProperty is used on it).
So the current status is developer friendly, starting the descriptors object from null won't be.

It's simply that I think the committee agrees that any time you use objects as maps in new APIs it should be null prototype.

In descriptors cases it won't add much value, but if that's the only way to go then it's OK.
I think  this should be discussed so I'll leave it for now open as it is.
Thanks for the ultra-quick come back on pretty much everything else, I'm up for diner now but I'll come back ASAP to other issues.

Are there any other examples in the spec of producing an object with a null prototype?

FYI I've added this question under FAQs
@ljharb after discussing with @rwaldron he agrees if you could be the Champion it'd be great so I've updated the README with your name too.
Gonna authorize you to access this as well, in case it's needed.

OK, in committee there was no real enthusiasm for a null-prototype object, so closing this.
Let me be the first to say congratulations on your new stage 2 proposal!

awesome news, thanks!


Add 'breakable' optional argument to report_build_html_table method

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1428536
Needs to merge with (UI): https://github.com/ManageIQ/manageiq-ui-classic/pull/3681

Add 'breakable' optional argument to report_build_html_table method for fixing bad formatting of VM Chargeback Preview Report table (unset word-break css attribute). The purpose was not to break/edit any other tables if not needed.
Before:

After:

@miq-bot add_label bug

@skateman @epwinchell @himdel Could you please someone look at it? Thanks! :star2:

Looks good

@miq-bot add_label formatting/styling

@miq-bot add_label formatting/styling


Stack checks

Cretonne doesn't currently generate stack overflow checks in its prologues. See previous discussion.

Here's a design we can start with. When translating wasm to cton, we create a global variable representing the stack limit and insert a stack check instruction at the top of each function:
stack_check gv0

This instruction will expand into something along the lines of:
v0 = global_addr gv0
v1 = load.i64 v0        ; load stack limit from gv0.
v2 = ifcmp_sp v1        ; compare v1 to %rsp, set flags.
trapif uge v2, stk_ovf  ; trap(stk_ovf) when limit >= %rsp.

This style of stack checking doesn't make use of the stack guard page that most operating systems have now. In SpiderMonkey, using the guard page is tricky because we need a minimal stack for the trap handler, so the stack limit includes that minimal stack.
Does this work for you @pchickey ?

Yes that approach will work well. Thank you!


[Scheduled Maintenance] Site down for transfer

Additional context
Who/what/when/where/why is this maintenance happening

FINALLY completed!!


Allow append/prepend of list values

Adds two new functions: appendList and prependList. Each takes
a list argument and appends or prepends it to an existing value at
the specified attribute name.
The previous methods, append and prepend, are unchanged: they
take a value, cast it to a list of a single element, and then
append/prepend it. This does not allow for list concatenation;
appending a list would result in a nested list, thus likely causing
any custom deserialization that expected a flat list for the updated
attribute to fail.
I messed around with ways to allow the existing append to take either a list or a single argument with varargs and things like that but couldn't get anything working. Since the argument is a tuple I wasn't able to do something clever like overload def append[V: DynamoFormat](fieldValue: (AttributeName, V*) or things like that.

Sorry for the delay responding. This looks good. Would appendAll/prependAll be a bit more conventional, or is that just in my head?

Hi @philwills Any chance getting a release for this in the near future? Can do a local in the mean time, but I don't think there's currently a way to append to a collection.

@philwills appendAll, prependAll sounds better to me too. I've gone ahead and changed it.

Great, thanks @prurph
Yes, I'll try and work with @davidfurey to get a release out before too long, but I can't promise a date.

This should now be available in 1.0.0-M5

Great thank you!


feat: add support for client roles with composite role references

This adds support for defining client roles, with optional support for making it a composite role, consisting of other roles.
As an example terraform configuration:

resource "keycloak_client_role" "my-awesome-role" {
  realm = "${keycloak_realm.my-realm.id}"
  client_id = "${keycloak_client.my-awesome-api.id}"
  name = "AWESOME_ROLE"
}

resource "keycloak_client_role" "another-role" {
  realm = "${keycloak_realm.my-realm.id}"
  client_id = "${keycloak_client.my-awesome-api.id}"
  name = "ANOTHER_ROLE"
}

resource "keycloak_client_role" "my-composite-role" {
  realm = "${keycloak_realm.my-realm.id}"
  client_id = "${keycloak_client.my-awesome-api.id}"
  name = "MyCompositeRole"
  composite_role_ids = [
    "${keycloak_client_role.my-awesome-role.id}",
    "${keycloak_client_role.another-role.id}"
  ]
}

resource "keycloak_user_role_mapping" "another-api" {
  realm     = "${keycloak_realm.my-realm.id}"
  client_id = "${keycloak_client.another-api.id}"
  name = "${keycloak_client_role.my-composite-role.name}"
}

I will continue testing this, but any early feedback on the code would be great, as I have not dabbled to much in Golang.
@phillipj @mahpatil

At first glance this looks really promising!
Is using a user role deliberate in the last example you included in the PR description?

Is using a user role deliberate in the last example you included in the PR description?

Yeah, the idea was to show how to assign that to a given user. I did however not provide the correct parameters, so I will fix that.


Update deep-source.yml

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

☢ Does this introduce a breaking change?

[ ] Yes
[x] No

ℹ Additional Information

Summary by Sourcery
CI:

Remove the pull_request_target trigger from the DeepSource workflow.

Description by Korbit AI
What change is being made?
Remove the pull_request_target triggers and related condition checks from the deep-source.yml configuration file.
Why are these changes being made?
The pull_request_target event is unnecessary for this workflow since it complicates the logic by checking the repository of the PR's head, and its removal simplifies the workflow configuration, reducing potential security risks associated with elevated privileges granted by the pull_request_target event.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

Summary by CodeRabbit

Chores

Updated GitHub Actions workflow configuration for Deep Source
Simplified event handling for workflow triggers, focusing on pull requests from the main repository and manual triggers

:white_check_mark: Build GuiStracini.Mandae 8.0.753 completed (commit https://github.com/guibranco/GuiStracini.Mandae/commit/1d2de8a58f by @gstraccini[bot])


cannot require('electron-prebuilt')

Hi all,
I want to open an external url using shell.openExternal however, when I add const shell = require('electron-prebuilt').shell; I get an error in the dev tools console saying:
Uncaught Error: ENOENT: no such file or directory, open '/path.txt'
I have validated that the path.txt file exists in node_modules/electron-prebuilt. My assumption is that this is something to do with trying to read path.txt whilst in the context of the browser.
Is there some other way of requiring electron-prebuilt?

const shell = require('electron').shell;

shell.openExternal('https://github.com');

see https://github.com/atom/electron/blob/master/docs/api/shell.md#shell

That worked! Thanks!


Suport for Kibana 8.9 in dev mode

Hello.
I need to make changes to the tables (translation into Portuguese, for example) but I can't make the plugin work in a development environment.
I'm following the guidelines in the README and using Elasticsearch through the 'yarn es snapshot' command.
When I remove the plugin from the kibana/plugins folder, Kibana starts correctly, however, when I add the plugin, Kibana does not start and presents an error message, as if Elasticsearch is not responding to requests.
Could you please help me.

Hi,
To make it work with Kibana 8.9.0, I strongly recommend you to use official elasticsearch package 8.9.0:
https://www.elastic.co/fr/downloads/past-releases/elasticsearch-8-9-0
Or use Elasticsearch official Docker image:
https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html
Concerning Kibana, I strongly recommend you to just checkout 8.9 branch and use the very last commit.

Hello.
Unfortunately it didn't work. I tried in different ways and was unsuccessful. I can start Elasticsearch and Kibana but when I add the plugin and restart Kibana it stops working

By the way, I just published Enhanced Table package for Kibana 8.9.1 here:
https://github.com/fbaligand/kibana-enhanced-table/releases/tag/v1.13.4

Thank you for your attention and support. Follow the sequence of commands. I'm using Ubuntu.
//terminal 1
git clone --depth 1 -b v8.9.1 https://github.com/elastic/kibana.git
cd kibana
nvm use
yarn install
yarn kbn bootstrap --no-validate
//other terminal
yarn es snapshot
//terminal 1
yarn start
//open Kibana in Firefox - ok
// stop kibana and add plugin
cd kibana/plugins
git clone https://github.com/fbaligand/kibana-enhanced-table.git
cd kibana-enhanced-table/
yarn install
cd ../..
yarn start
//open kibana in Firefox - error
Elastic did not load properly. Check the server output for more information.
//Firefox logs:
O recurso de “http://localhost:5601/dbp/9007199254740991/bundles/plugin/enhancedTable/kibana/enhancedTable.plugin.js” foi bloqueado devido ao tipo MIME (“application/json”) não corresponder (X-Content-Type-Options: nosniff).

I ran the following sequence of commands, but it didn't work. Still with the same error message
git clone --depth 1 -b v8.9.1 https://github.com/elastic/kibana.git
cd kibana/plugins
git clone https://github.com/fbaligand/kibana-enhanced-table.git enhancedTable
cd ..
yarn kbn bootstrap
cd plugins/enhancedTable
yarn install
yarn start
Browser message:
Elastic did not load properly. Check the server output for more information.

Well, I'm very surprised, as it works fine for me, and also sad for you.
I have one last suggestion: when you clone, can you checkout 8.9 branch instead of v8.9.1?
git clone --depth 1 -b 8.9 https://github.com/elastic/kibana.git

Thanks again for your attention.
I did the "git clone" as you suggested, but I still get the same error message. In Chrome the message is more complete:
{"statusCode":401,"error":"Unauthorized","message":"missing authentication credentials for REST request [/.kibana_8.9.2/_doc/config%3A8.9.2]: security_exception\n\tRoot causes:\n\t\tsecurity_exception: missing authentication credentials for REST request [/.kibana_8.9.2/_doc/config%3A8.9.2]"}

Well the message seems to be very different. There’s nothing about enhanced table and error says that credentials are missing.
Personally, in dev mode, I disable elasticsearch security and also https. That is in elasticsearch .yml.

Yes, but when I remove the plugin, Kibana works and this error message does not appear.

Security is disabled, I used the following parameters in the elasticsearch.yml file:
xpack.security.enabled: false
xpack.security.transport.ssl.enabled: false
xpack.security.http.ssl.enabled: false

The error message 'Elastic did not load properly. Check the server output for more information.' it continues to appear, but what calls attention is that in the console (firebug) the message appears

I found a similar problem
https://github.com/elastic/kibana/issues/157440

This issue is interesting.
It gives me two ideas:

in enhanced table plugin directory, could you try to execute « yarn compile » before to run kibana
Try to start kibana with —watch option.

I have good news.
The first option worked, after a few tries!
I will review all the steps and share them here.
I still need to test the process of changing the code and generating a new build.
Thanks again.

Thanks for all your tests and all the time you spend on it.
Once you shared the steps, I will update documentation.

This is the sequence of commands I used
git clone --depth 1 -b 8.9 https://github.com/elastic/kibana.git
cd kibana/plugins
git clone https://github.com/fbaligand/kibana-enhanced-table.git enhancedTable
cd enhancedTable
yarn install
cd ../..
nvm use
yarn kbn bootstrap
cd plugins/enhancedTable
yarn compile
yarn start

Great! Thanks for the share!
I will update documentation in this way.

I just fixed documentation here:
https://github.com/fbaligand/kibana-enhanced-table/#development

I close the issue as it is fixed


Add support for LDAP authentication (fixes #264)

Signed-off-by: Jérémie Dumas<EMAIL_ADDRESS>What does this PR do?

Adds support for LDAP authentication.
Simply provide a service_id when creating a client to use LDAP authentication with the corresponding service_id.

What ticket does this PR close?
Resolves #264
Checklists
I'm not familiar enough with the testing framework to add a unit test for this. Readme/changelog can be updated if you're ok with the change.
Change log

[ ] The CHANGELOG has been updated

Test coverage

[ ] This PR includes new unit and integration tests to go with the code changes, or
[ ] The changes in this PR do not require tests

Documentation

[ ] Docs (e.g. READMEs) were updated in this PR, and/or there is a follow-on issue to update docs

First off, thank you for your contributions @jdumas! Great work
A couple of notes:

Could you explain the motivation behind this addition?
Unit/Integration tests for the LDAP flow - I would highly recommend that we add tests, beit unit tests or integration so that this ensures that there is no breakage in the code for future enhancements. Especially since we are touching the api component. We should make sure that when a user adds service_id that the request is funnelled to the LDAP flow etc. Please see this section from our CONTRIBUTING.md page on how to deploy and run ours tests. If you experience any difficulties please let me know

If any of my comments are not clear, would be happy to expand on them! Thanks again 😃
FYI @eladkug @InbalZilberman heads up

Thanks for the comments. Let me answer your general questionss:

The motivation is I have to use Conjur with LDAP authentication... not sure what more you need there.
Yes I agree adding a unit test is important. But I have no idea how to setup a Conjur server with a LDAP authentication just for unit test purposes. If I have to do it myself it may take a while before I get down to it...
Those are good suggestions and I'll address those refactorings soon.

@jdumas

Yes I agree adding a unit test is important. But I have no idea how to setup a Conjur server with a LDAP authentication just for unit test purposes. If I have to do it myself it may take a while before I get down to it...

If it is not possible to write those integration tests with a Conjur server with LDAP configured or you believe it will take too much time, then unit tests would suffice at this time validating the flow described in my message above
We should make sure that when a user adds service_id that the request is funnelled eventually to the LDAP flow etc.
In other words, you should be adding tests to the following files, unit_test_api.py unit_test_client.py unit_test_endpoints.py

Hi @jdumas, I'm taking over this PR now that @sigalsax isn't at CyberArk anymore.
Can you please rebase your branch with main and address @sigalsax's review comments? I can work on writing some tests for it. Once that's done I hope we can get this merged very soon.
Thanks again for your contribution!

Hi. Sorry I kinda left this one unattended for a while. I can't promise I'll be able to update it soon, but I'll see what I can do.

@jdumas That's fine. I would like to get this moving forward. Do you mind if I take over the PR?

Yes please do!

Hi @jdumas, sorry for the long delay. We decided to implement LDAP support in the CLI as part of a larger refactoring effort which is progressing and should be done in the next few weeks. I have a draft PR (#411) which should be the last PR needed to get this fully supported. You can follow that PR for any updates.

Closing in favor of #411 which is now merged.


test: Test restoring historic cluster backups

This adds script/generate-backups which bootstraps a Flynn cluster at various versions, deploys the Node.js example app, adds a Redis resource and backs up the cluster to a file.
There is also a test which iterates through those backups, bootstraps a cluster then checks the app came up with Redis correctly.
We probably want to expand this a little going further (e.g. use docker push, provision different resources etc.) but this at least gives us a good starting point to start avoiding cluster restore regressions.

Amazing! LGTM

Woah! LGTM

@titanous @josephglanville I made some changes to make this more reliable:

Mount the backups dir as a 9P filesystem inside the VMs at /mnt/backups
Use different flannel networks for each backup test to avoid conflicts
Add new env vars to system apps during restore (e.g. the new NETWORK var for flannel)
Add some retries the the HTTP / Redis checks as user services aren't guaranteed to be up when the restore finishes

I have tested this 20 times in custom CI without error.

@titanous comments addressed

LGTM


How to change the ngf-drop div  background color when drag over and the color change back after drop?

How to change the ngf-drop div  background color when drag over and the color change back after drop?

@LUJULIANG2016, use ngf-drag-over-class="'dragover'" and css something like that:
.dragover {
  background-color: red;
}

Thanks a lot


Skip parsing undefined values

Fixes #35. @Kerumen can you double check that this addresses the issue you raised?

Yes it fixes the issue! Thanks :)


Swift 3 branch without any API changes

Hello, LayoutKit is awesome, but I would like to develop apps with Swift 3, unfortunately LayoutKit has no Swift 3 support yet, so I create a new branch for that reason. It's migrated by Xcode 8 beta, I don't touch any API names but I'm not sure if the migrations affect the API names, and fix some un-migratable errors manualy.

Cool, thanks for doing this work! I added some comments to the code.
Can you also update .travis.yml to run Xcode8 so we can verify that tests pass?
osx_image: xcode8

Will also need to add/update the destinations appropriately in .travis.yml

Looking good, can you rebase on master so tests get run? I think there is a merge conflict because I modified .travis.yml in master due to some test flakiness.

Looks like we need to remove iOS 8 & 9 simulator destinations from .travis.yml. Xcode 8 currently only includes iOS 10.

Can you remove | xcpretty for the test command. It looks like something is failing during tests and we don't get a useful error message. Could be a bug in Xcode 8.

Still fails. Not sure how to deal this issue.

Can you please turn off whole module optimization and also add --destination-timeout 300 to the xcodebuild commands in .travis.yml

None or Fast, Single-File Optimization, which option do you prefer?

And .travis.yml will be changed like this, is it OK?
language: objective-c
osx_image: xcode8
script:
  set -o pipefail &&
  xcodebuild build -project LayoutKit.xcodeproj -scheme LayoutKitSampleApp -sdk iphonesimulator10.0 --destination-timeout 300
    -destination 'platform=iOS Simulator,name=iPhone 6,OS=10.0'
    -destination 'platform=iOS Simulator,name=iPhone 6 Plus,OS=10.0' &&
  xcodebuild test -project LayoutKit.xcodeproj -scheme LayoutKit -sdk iphonesimulator10.0 --destination-timeout 300
    -destination 'platform=iOS Simulator,name=iPhone 6,OS=10.0'
    -destination 'platform=iOS Simulator,name=iPhone 6 Plus,OS=10.0'

after_success:
  - bash <(curl -s https://codecov.io/bash)

.travis.yml looks good.
For optimization, I just want this line to disappear from the diff: SWIFT_OPTIMIZATION_LEVEL = "-Owholemodule". Default should be fast I think. It probably doesn't matter but I would like to minimize the diff when trying to debug issues like this.

fyi, I pushed this as swift3 branch. Will continue to try to get test to pass on travis.


Any instructions for m1 builds

I know that we're not ready to prebuild on github actions, but it would be wonderful to be able to do locally
Thanks :)

I know that we're not ready to prebuild on github actions

You mean it Github Actions isn't ready for Apple M1 , since it sounds like it doesn't have support for it yet: https://github.com/actions/virtual-environments/issues/2187
In the meantime, you can try doing the following locally to see if v8 will build:

Checkout the v8go repo
Clone the submodules git submodule update --init --recursive
Build the v8 binary for your OS and architecture deps/build.py

If that works, then you can try modifying cgo.go and add a deps/*/vendor.go file so the built libv8.a can be used.

We also needed M1 support and were able to get it building locally using the instructions in the README: https://github.com/airplanedev/v8go/pull/5

@colinking Nice!
I couldn't get v8 to build correctly, but I was able to link the dynamic library from homebrew's v8.


Add GRS

Thank you for your PR! Merging!


Add Ellipses on the small Component menu to open the full wheel Component Menu

Add Ellipses on the small Component menu to open the full wheel Component Menu.
Full wheel Component Menu also opens on right click on component

Merged with #8612


Updates for Calico v3.16.1

Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 2bf8f12a2ca6092d133f39691da09475e79c7d5e
https://deploy-preview-3985--calico.netlify.app

Deploy preview for calico ready!
Built with commit 93db85e6c421a201ef03e6e17b1d5810b8694f5b
https://deploy-preview-3985--calico.netlify.app


Builds fail with Visual Studio 2022 17.5.2 and clang-cl from LLVM

I have been using ninja with hundreds of projects and thousands of builds for over two years mostly without problems. Today I updated Visual Studio 2022 from 17.4.1 to 17.5.2 and LLVM from 15.0.6 to 16.0.0. Since then I can not build simple project zlib anymore (did not try other builds). The build fails with error:
[...]
Visual Studio Non-Incremental Link
LINK:
C:\BDA\ci\LLVM-16.0.0\bin\lld-link.exe CMakeFiles\zlib.dir\adler32.obj CMakeFiles\zlib.dir\compress.obj CMakeFiles\zlib.dir\crc32.obj CMakeFiles\zlib.dir\deflate.obj CMakeFiles\zlib.dir\gzclose.obj CMakeFiles\zlib.dir\gzlib.obj CMakeFiles\zlib.dir\gzread.obj CMakeFiles\zlib.dir\gzwrite.obj CMakeFiles\zlib.dir\inflate.obj CMakeFiles\zlib.dir\infback.obj CMakeFiles\zlib.dir\inftrees.obj CMakeFiles\zlib.dir\inffast.obj CMakeFiles\zlib.dir\trees.obj CMakeFiles\zlib.dir\uncompr.obj CMakeFiles\zlib.dir\zutil.obj CMakeFiles\zlib.dir\win32\zlib1.res /out:zlib1.dll /implib:zlib.lib /pdb:zlib.pdb /dll /version:1.2 /machine:x64 /INCREMENTAL:NO kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib /MANIFEST /MANIFESTFILE:zlib1.dll.manifest
MT:
C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe /nologo /manifest zlib1.dll.manifest /outputresource:zlib1.dll;#2
ninja: error: FindFirstFileExA(Note: including file:       C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.35.32215/include): The filename, directory name, or volume label syntax is incorrect.

I'm building on Windows 11 latest (updated today) using a Cygwin-shell to orchestrate the build. The actual ninja execution is not via cmake but directly a call to ninja from a DOS command prompt started from Cygwin bash.
I tried this with ninja build from master from 2022.02 and with current master from today (2d9083b). Both fail with the same error.

When I run the same build without clang-cl (only using Visual Studio) the error is gone, so it seems it is related to LLVM 16.0.0.

I have tried now various combinations of build tools. Here is what I tried:

Build with Visual Studio 2022 17.4.1 with clang-cl 15.0.6: works
Build with Visual Studio 2022 17.5.2 without clang-cl: works
Build with Visual Studio 2022 17.5.2 with clang-cl 15.0.6: does not work
Build with Visual Studio 2022 17.5.2 with clang-cl 15.0.7: does not work
Build with Visual Studio 2022 17.5.2 with clang-cl 16.0.0: does not work

Therefore it seems that the problem comes from the combination of Visual Studio 2022 17.5.2 with clang-cl, independent of the clang-cl version.

After downgrading cmake to 3.25.3 (latest before 3.26.x), the problem is gone. Updating the info what I tried:

Build with Visual Studio 2022 17.4.1 with cmake 3.25.x with clang-cl 15.0.6: works
Build with Visual Studio 2022 17.5.2 with cmake 3.26.x without clang-cl: works
Build with Visual Studio 2022 17.5.2 with cmake 3.26.x with clang-cl 15.0.6: does not work
Build with Visual Studio 2022 17.5.2 with cmake 3.26.x with clang-cl 15.0.7: does not work
Build with Visual Studio 2022 17.5.2 with cmake 3.26.x with clang-cl 16.0.0: does not work
Build with Visual Studio 2022 17.5.2 with cmake 3.25.3 with clang-cl 16.0.0: works

So the problem seems to appear in combination with clang-cl (any version) and cmake 3.26.x. It seems the Visual Studio version is irrelevant.

Looks like a CMake bug then. Thanks for reporting, pinging CMake devs: @bradking @mathstuf

Nice @bradking ! Then I will close this issue in favor of the upstream MR.


Add kafka

Which issue(s) this PR fixes:

Fixes #333
Additional comments:

This PR:

Also refactors the zookeeper role to support deploying multiple ZooKeeper versions and adding custom properties to configuration
Does not include the deployment of the Ranger plugin. For further details, see #340.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004 and that you give permission to TOSIT,
you have to acknowledge this by using the following check-box.

[x] I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[x] I hereby agree to grant TOSIT a copyright license to use my contributions.

If this version of Kafka can not use the Ranger inside TDP we should not add it to TDP. The goal of TDP is to offer service which work together. I do not see integration with other TDP product in this PR or maybe in future PR ?.

Closing this PR as Kafka is moved to tdp-collection-extras. See dicussion#27


abbr plugin error?

https://github.com/lepture/mistune/blob/1264a1c954396fa31304bfac39588381f015a5d8/mistune/plugins/abbr.py#L56-L63
maybe here def_abbr and should the same as abbr? I run my code local no error, but on github action error occurs

full log here https://github.com/teedoc/teedoc/actions/runs/3069280480/jobs/4957741255

Do not install the library from the pip repository, as this will download and install v2. To use the newer plugins, you have to pull v3 directly from GitHub:
pip install git+https://github.com/lepture/mistune

We have v3 rc releases in PyPI.


[BUG] Withdrawal attempts through DET keep failing with error

OS : Windows 10 Pro
16 GB RAM
DET version (Windows) : v0.1.3
Dash Core wallet version (Windows) : v21.1.1
During withdrawal i get these kind of error messages :
Error: Withdrawal error: Dapi client error: Transport(Status { code: Internal, message: "Internal error", metadata: MetadataMap { headers: {"grpc-accept-encoding": "identity", "grpc-encoding": "identity", "content-type": "application/grpc+proto", "date": "Wed, 30 Oct 2024 23:23:43 GMT", "x-envoy-upstream-service-time": "45", "server": "envoy"} }, source: None }, Address { ban_count: 0, banned_until: None, uri: https://XXXXXXXX
With only date & "x-envoy-upstream-service-time": xx & uri: changing value with these errors.
And these :
Error: Withdrawal error: Dapi client error: Transport(Status { code: AlreadyExists, message: "state transition already in chain", metadata: MetadataMap { headers: {"grpc-accept-encoding": "identity", "grpc-encoding": "identity", "content-type": "application/grpc+proto", "date": "Thu, 31 Oct 2024 07:02:58 GMT", "x-envoy-upstream-service-time": "10", "server": "envoy"} }, source: None }, Address { ban_count: 0, banned_until: None, uri:
Which i can overcome by lowering the withdrawal amount slightly. But then i get the first error.
Error: Withdrawal error: Dapi client error: Transport(Status { code: Internal, message: "Internal error", metadata: MetadataMap { headers: {"grpc-accept-encoding": "identity", "grpc-encoding": "identity", "content-type": "application/grpc+proto", "date": "Thu, 31 Oct 2024 07:06:49 GMT", "x-envoy-upstream-service-time": "21", "server": "envoy"} }, source: None }, Address { ban_count: 0, banned_until: None, uri
In DET, Platform Explorer and mnowatch i see the correct Evonode balance (for DET i needed to reload my Evonodes). Balance does not change after these withdrawal errors and only my previous withdrawal from previous epoch remains visible in Platform Explorer. I have no problem fetching contested usernames, so rpc wise there is communication between Dash Core and DET. I am using owner privatekey to withdrawal, i did change my payout address from Dash Core software wallet address to a hardware wallet address after previous successful withdrawal 9 days ago.
I also tried it in Ubuntu 14.04 LTS (VirtualBox, on my Windows machine), same problem.
I just can't get a withdrawal out and into queue.
I do wonder if this issue is perhaps related to Core v21.1.1 which i am using both in Windows (to get the Platform Transfers visible in my Core wallet) and in Ubuntu 24.04 LTS (Virtualbox).
** see my second post, contains uploaded explorer.log of DET **

@qwizzie  Ensure that the versions of your Dash Core wallet and DET are fully compatible with each other. Sometimes, even minor version mismatches can cause issues. Look into the detailed logs of both DET and Dash Core. The error message you provided suggests an internal error, which might be better explained in the detailed logs

Tried it also with Dash Core v21.1.0 : same problem
Tried changing my payout address back to Dash Core wallet address instead of hardware address : same problem

@qwizzie given that the issue persists even after changing the payout address back to the Dash Core wallet address, it might be worth checking if there are any specific settings or configurations in your Dash Core wallet that need to be adjusted.

https://github.com/dashpay/platform/pull/2274 fixes state transition already in chain, it will show you a more detailed message about errors in your state transition (i guess in 1.4.2 or 1.5.0, when nodes will deploy that)

Hopefully a new DET version (binaries) will fix these ['internal error' issues](code: Internal, message: "Internal error") that are interfering with withdrawals for me right now.

I managed to get withdrawals out through payout address private key methode. Owner address private key methode is still not working anymore for me. FYI.

Another user describing the same issue --> https://www.dash.org/forum/index.php?threads/how-to-withdraw-evonode-rewards-from-dash-platform.55487/#post-240104

Withdrawals with owner key still not working as of today as reported by @qwizzie


Modify the wrong character

Signed-off-by: zhukj<EMAIL_ADDRESS>Modify the wrong character.

Current coverage is 54.53% (diff: 100%)

Merging #1837 into master will decrease coverage by 0.11%

@@             master      #1837   diff @@
==========================================
  Files           102        102
  Lines         17025      17025
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           9304       9285    -19
- Misses         6585       6599    +14
- Partials       1136       1141     +5

Powered by Codecov. Last update f355ca1...5654c1b

There is another instance of the same typo in manager/orchestrator/replicated/tasks.go. Can you please fix that one as well?

LGTM


Basic relationships support

This adds a basic brooklyn.relationship.Configure relationship for a Tomcat / MySQL application on 2 different compute nodes. Also adds support for capabilities and requirements coming from Brooklyn catalog entities.

This is dependent on this PR. Do no merge before it.

LGTM; merging

This depends on a Brooklyn PR that hasn't been merged. Revert?


Update how-to-migrate-online.md (Typo "flexible server"→"Flexible Ser…

…ver")
https://github.com/MicrosoftDocs/azure-databases-docs/blob/main/articles/mysql/flexible-server/how-to-migrate-online.md #PingMSFTDocs

@SudheeshGH - related #10


Analysis engine missing error case

Enter the following in any Dart file:
class C {
  int v;
  const C(this.v);
}
This should produce an error, but doesn't:
It is a compile-time error if a constant constructor is declared by a class that
has a non-final instance variable

Analyzer now reports:

Can't define a const constructor for a class with non-final fields.


Branch storage tests

Tests added, storage read catches overlapping entries

Codecov Report

Merging #195 (1594f32) into master (7d3dbd1) will increase coverage by 2.26%.
The diff coverage is 62.50%.

@@             Coverage Diff              @@
##             master     #195      +/-   ##
============================================
+ Coverage     41.76%   44.03%   +2.26%
- Complexity      481      505      +24
============================================
  Files           152      152
  Lines          2526     2539      +13
  Branches        295      302       +7
============================================
+ Hits           1055     1118      +63
+ Misses         1414     1356      -58
- Partials         57       65       +8

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/seedu/address/model/entry/Entry.java
69.56% <33.33%> (-0.71%)
17.00 <2.00> (+6.00)
:arrow_down:

...n/java/seedu/address/storage/JsonAdaptedEntry.java
97.61% <100.00%> (+97.61%)
10.00 <0.00> (+10.00)

...u/address/storage/JsonSerializableAddressBook.java
68.18% <100.00%> (+11.03%)
6.00 <0.00> (+2.00)

...main/java/seedu/address/model/entry/EntryName.java
70.00% <0.00%> (ø)
4.00% <0.00%> (+1.00%)

...u/address/model/entry/NonOverlappingEntryList.java
45.65% <0.00%> (+4.34%)
10.00% <0.00%> (+1.00%)

src/main/java/seedu/address/model/AddressBook.java
60.75% <0.00%> (+5.06%)
23.00% <0.00%> (+2.00%)

...main/java/seedu/address/model/entry/EntryDate.java
83.33% <0.00%> (+22.22%)
6.00% <0.00%> (+2.00%)

Continue to review full report at Codecov.

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


enabling redirection in cargo gen

as per https://github.com/ashleygwilliams/cargo-generate/issues/128#issuecomment-443334684

#67 would solve this issue too.

as for today (v0.12.0) we have shortcuts and prefixes like gh-user/repo or gh:user/repo for valid repository urls.
Nobody needs to type any full urls anymore. Hence I think we are past this problem here.


Document news.publish

news.get is missing
Also statistics will not be shown in publish or list

Also add updated_since param to news.list

Issue migrated to our-city-app/mobicage-backend#38


Do not panic if templates not found

Avoid panic if templates/vulns.html or templates/layout.html is not found.
Exit with a fatal instead.

thanks!


[WIP] More pythonic build system while waiting for Aer

Summary
As we are waiting for Aer integration, where C++ code are going to be moved away from Terra to Aer, we still need to deal with CMake build system for non-python code.
Using scikit-build will makes building, testing, and most importantly packaging, a more pythonic experience.
Once this is merged (if we want to), the way for creating packages will change to:
qiskit-terra$ python setup.py bdist_wheel --plat-name manylinux1_x86_64 -- -DSTATIC_LINKING=True -- -j8

... for testing we just need to:
qiskit-terra$ python setup.py test -- -DSTATIC_LINKING=True -- -j8

There's more information in the CONTRIBUTING.md guide.
TODO:

[ ] Static compilation doesn't seem to work due to a bug in CMake (there's a local workaround though)
[ ] Check local tests can run
[ ] Check that travis works
[ ] Check Windows executable
[ ] Check Linux executable
[ ] Check MacOSX executable

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: atilag:x: Juan Gomez MosqueraJuan Gomez Mosquera seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Ok this seems to have fallen quite out of sync, and now Aer is released and the terra doesn't have a  c++ simulator (#1615). @atilag can you see what else is left to do on the build system in Terra? I'm closing this PR in the meantime.


Fix pagination in some endpoints

Motivation and context

Added missing pagination or page parameters in /projects/{id}/tasks, /tasks/{id}/jobs, /jobs/{id}/issues, /jobs/{id}/commits, /issues/{id}/comments, /organizations
Updated SDK, tests and UI

How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@zhiltsov-max , @bsekachev , could you please look at tests?


Fix pdata function table order

The code used to rely on map iteration order which is unpredictable and results in random flamegraphs for ontarget symbolized functions.
In this PR we switch to building a properly ordered function table slice.
Before: https://flamegraph.com/share/7ea36b00-bee5-11ef-9832-26c3e5347170
After: https://flamegraph.com/share/522fade3-bee5-11ef-9832-26c3e5347170

Indeed fixed the problem!
LGTM


add whatwg-fetch to fix promise problems that occurs in special browser (eg. Wechat browser in China )

TODO:

[x] Update CHANGELOG.md with your change
[x] Make sure all of the significant new logic is covered by tests
[x] Rebase your changes on master so that they can be merged easily
[x] Make sure all tests and linter rules pass

Thanks!
I'm adding this for now. Might remove it again later if we find that it's better to solve this by adding whatwg-fetch in the projects that use apollo-client

@helfer can you open an issue to remove the fetch dependency? I think it would be really easy.


Reporting outcome of a call

HTTP POST to /report including

result (must be one of 'unavailable', 'vm', 'contacted')
contact id
issue id

Then save to local persistence (a plist, or maybe Pantry? 😄 ) the outcome of this issue.
Issues that have a saved result show up w/ a green checkmark on the issues list.  This can be done in IssuesViewController by setting the isChecked flag on IssueCell.

Going to integrate this into the Script Detail screen.

I also see location and phone on the backend call, should we also send that?https://github.com/5calls/5calls/blob/241e06aee6d56f0ffe8495043578ae003e35b222/go/report.go#L25

Apparently we need to support logging calls to the reps more than once. So reopening the issue.

Also add support for the 'phone' parameter, which we can capture based on what call button was pressed.


Feature: Add Memos to TxContext

In an entry transaction, be able to attach arbitrary data to the ctx (Transaction Context) as a sequence of bytes. This data can be read by on-chain modules using the tx_context::memo(ctx) API, and it will be logged along with the rest of a transaction's info for reference by off-chain processes.
Off-Chain Example:
Many centralized exchanges (Coinbase) instruct depositors to do a simple transfer of coins to a fixed address (sui::transfer::transfer(coin, address)), and attach a memo to the transaction that specifies the coinbase-account that deposit was intended for.
On-Chain Example:
I would intend to use modules for additional on-chain permissioning. For example, suppose you want to deposit Coin into another person’s vault, but this vault requires permission. It would work something like:
public entry fun deposit(vault: &mut Vault, coin: Coin<Sui>, ctx: &TxContext) {
  if (vault.require_permission) {
    assert!(has_permission(vault, ctx), ENOT_PERMISSION);
  };
  coin::merge_into(&mut vault.balance, coin);
}

public fun has_permission(vault: &mut Vault, ctx: &TxContext): bool {
  let signature_bytes = tx_context::memo(ctx);
  let owner = &vault.owner;
  let nonce = &vault.nonce;
  let sender = tx_context::sender(ctx);
  // Check that the bytes match a signature of nonce from the owner address
  validate_signature(signature_bytes, owner, sender + nonce)
  vault.nonce = vault.nonce + 1;
  ...
}

the has_permission does a cryptographic check like “did the vault-owner-address produce a valid signature of (sender-address + vault.nonce)”? If yes, then return true, otherwise return false.
The bytes could be included explicitly as an argument in the deposit function, but then we’d have to add arguments to both our functions, and a lot of the time we won’t be using those bytes, so callers would be specifying lots of empty u8 vectors for no reason.
Additional idea - Passing Variables Down:
We could allow on-chain functions to attach arbitrary data to ctx, and then pass those down to other functions further down on the chain, without needing to explicitly pass every variable. This would work much like contexts in React do, where you wrap functions in a context, and inside of that wrapper all children can access variables within the wrapping-context. (Because ctx does not have a UID, we are currently unable to use dynamic fields for this purpose.) This should be considered an optional bonus.

In your has_permission example, what would go wrong if signature_bytes were instead a tx argument?

In your has_permission example, what would go wrong if signature_bytes were instead a tx argument?

It could definitely be a transaction argument, but being able to attach arbitrary bytes to the ctx object simplifies APIs. You could imagine serializing optional data that the module then deserializes and uses to fill in the properties of a struct it's building, for example.

It could definitely be a transaction argument, but being able to attach arbitrary bytes to the ctx object simplifies APIs.

Could you help me understand how this simplifies things? It seems like this is expanding the API surface to accomplish things that could already be done with tx arguments. We try really hard to keep API surfaces minimal so that there's a clear way for programmers to accomplish a given task (e.g., "use tx arguments for this" rather than "use tx arguments in this situation and memos in this situation") and only add new ones when they solve well-motivated problems that fundamentally aren't possible with the existing features.

You could imagine serializing optional data that the module then deserializes and uses to fill in the properties of a struct it's building, for example.

E.g., I believe this can already be done with transaction arguments, but let me know if I'm missing something.

Could you help me understand how this simplifies things? It seems like this is expanding the API surface to accomplish things that could already be done with tx arguments. We try really hard to keep API surfaces minimal so that there's a clear way for programmers to accomplish a given task (e.g., "use tx arguments for this" rather than "use tx arguments in this situation and memos in this situation") and only add new ones when they solve well-motivated problems that fundamentally aren't possible with the existing features.

You could imagine serializing optional data that the module then deserializes and uses to fill in the properties of a struct it's building, for example.

E.g., I believe this can already be done with transaction arguments, but let me know if I'm missing something.

Okay, I see what you're saying. My thoughts were that it would add flexibility to entry-functions if callers could attach arbitrary optional binary data along with their call. But philosophically it's probably better to keep all function arguments explicit; I can simply add bytes: vector<u8> as a function argument where needed, and allow callers to pass-in empty-vectors if the argument is considered optional data. Maybe I could use a naming convention like "bytes_opt" with "opt" meaning it should be considered optional data?
How do you feel about memos for offline-purposes though? To leave data behind for indexers to better understand what a transaction was for? For example, a sui-transfer could attach an invoice-number as a memo, so that the merchant can match the transfer they received to a payment-invoice they sent out.

Agree with @PaulFidika.
This concept/feature will be very useful in a sui payment framework as it will make it very easy to find and validate payments off-chain without having to store the payment information on a centralized server.
for a payment framework, it could work like this:

End user initiates a payment
The framework or developer generates a reference and passes it into the transaction memo
The framework polls the blockchain for the transactions and tries to find the reference in the tx memo
If the end user makes the payment, the reference will be found and then the transaction can then be validated
If not, the payment is not yet made and the polling continues (until the transaction is made or cancelled by the user)

PS: this is be similar to how solanapay works
This can also be achieved by writing a custom package and requiring the reference as an argument but It would be a waste because we have the standard coin payment methods provided by Sui already.
Also, this is one of the numerous use cases this feature would bring to Sui and also this could be a starting point for a Sui payment  framework standard.


Add ability to create requests from entities in Python SDK

Let's take the Table entity as an example.
Python SDK provides a CreateTableRequest that can be used to create OR update a table. Currently, there is no way to use the Table entity to construct this request, so it has to be done manually:
table_def = metadata.get_by_name(fqn=table_fqn, entity=Table)

table_request = CreateTableRequest(
    name = getattr(table_def, "name", None),
    displayName = getattr(table_def, "displayName", None),
    description = "New description",
    tableType = getattr(table_def, "tableType", None),
    columns = getattr(table_def, "columns", None),
    tableConstraints = getattr(table_def, "tableConstraints", None),
    tablePartition = getattr(table_def, "tablePartition", None),
    owner = getattr(table_def, "owner", None),
    databaseSchema = getattr(table_def, "databaseSchema", None),
    tags = getattr(table_def, "tags", None),
    viewDefinition = getattr(table_def, "viewDefinition", None),
    extension = getattr(table_def, "extension", None)
)

metadata.create_or_update(data=table_request)

CreateTableRequest expects that developer will list all the fields, and if some field is missing, it will be removed from the entity when the request is executed. However, fields may (and will - https://github.com/open-metadata/OpenMetadata/pull/6416) change, which will cause problems for people who use this API - they will have to check and update their code whenever they upgrade their OM instance to a new version.
It would be great if we could do something like this:
table_def = metadata.get_by_name(fqn=table_fqn, entity=Table)
...
# modify the table here
...
request = CreateTableRequest(table_def)

In this case, SDK should take care of the fields, and no data should be lost during the request execution.

@pmbrull what are your thoughts here? Users need to use CreateTableRequest and use appropriate method to update the table such as PUT in this case it needs to have all the available fields if not use PATCH.
not sure if this is a valid request here if not lets close this out

this will also help in a couple of calls in the code as well to update profiler specific props. Just need the time to add the syntactic sugar for the PUT

Table entity has a lot more information than what is allowed when a table is created using CreateTableRequest. As an example, followers, tests, queries, usage summaries all are available in the Table entity when you GET a table. However, the creation of all this information is done in separate APIs and not during table creation. Marking this as won't fix.


soroban-rpc : add support for fee calculations

What ?
The rs-soroban-env now contains library functions to calculate the fees needed by a transaction, based on it's resources.
Our goal is to integrate that into simulateTransaction endpoint in soroban-rpc. This issue is about the second step in the process:
We need to use the exposed fee calculation method we previously created in https://github.com/stellar/soroban-tools/issues/622, and use it during simulateTransaction in order to calculate the suggested fees. Then, we need to modify the returned json to include the following:
( all the TransactionResources fields, that you've already used when calling compute_transaction_resource_fee )

Number of instructions
Number of reads
Number of writes
Read bytes count
Write bytes count
Metadata size
Transaction size
( plus )
Fee ( Minimal inclusion fee )
RefundableFee

Epic

https://github.com/stellar/soroban-tools/issues/519

Dependencies

https://github.com/stellar/soroban-tools/pull/627
https://github.com/stellar/soroban-tools/pull/628

I think this is fully addressed in https://github.com/stellar/soroban-tools/pull/636

I think this is fully addressed in #636

Just close both when you're done with 636, as this one was supposed to be the go side and the other on the preflightlib side.


@mdx-js/mdx v3 support, possible refactoring of the repository

The entire unified stack and community around it has received major updates to all ecosystem components.
I was looking into maybe using mdx-embed for a project but that project requires mdx v3.
I am offering my help in updating the stack and I think it may be a good time to revisit some fundamental things before proceeding (details below).
Given the low levels of activity on the repository I thought I'd be respectful of everyone's time and reach out first to gauge whether there are currently enough cycles from the maintainers to review and merge changes or if there is already work ongoing in this regard.
Issues
mdx-embed is referenced in the official mdx documentation, but it currently doesn't function with either mdx v2 or v3.
I did see the initial work on v2 support in the feat/mdx-2 branch.
mdx-embed is in need of a good cleanup. Some of the issues I found:

Most of the tooling (cypress, lerna, yarn), scaffolding (storybook) and examples (gatsby, nextjs, storybook) are using outdated versions that create conflicts when attempting to use them with an updated mdx-embed.
The nextjs stuff is pretty trivial, the gatsby stuff didn't work for me and storybook offers a guided migration which I haven't fully tested yet.
Yarn v1 workspaces get in the way when trying to independently work with different aspects of the monorepo, updating them one at a time (e.g. hoisting @types dependencies, such as @types/react or @types/react-dom, which will lead TypeScript to complain about redefined types when building type definitions or building the module). By disabling hoisting for a good portion of dependencies this can be avoided. My experiments with pnpm showed that this would not be necessary there.
Some babel plugins have been renamed after having graduated from proposal status.
eslint configuration needs to be updated.

And those would be the immediate things I stumbled upon in my first pass.
Other than that I'm guessing there would have to be a review of the tests to verify that all of the individual components actually still work.

Bummed this is not compatible, especially being mentioned in MDX docs. Was going to add it to a nextra portfolio project to embed some figma files.


Problematic file permissions in crates.io tar archive

Files in the tar archive at crates.io lack read permissions for other users (chmod o+r). This can be demonstrated by running these commands:
$ curl -L https://crates.io/api/v1/crates/pin-utils/0.1.0/download | tar xz
$ ls -lR pin-utils-0.1.0
pin-utils-0.1.0:
total 28
-rw-r--r-- 1 wsh wsh   835 Jan  1  1970 Cargo.toml
-rw-r----- 1 wsh wsh   314 Apr 22  2020 Cargo.toml.orig
-rw-r----- 1 wsh wsh 10841 Apr 22  2020 LICENSE-APACHE
-rw-r----- 1 wsh wsh  1065 Apr 22  2020 LICENSE-MIT
-rw-r----- 1 wsh wsh  1079 Apr 22  2020 README.md
drwxr-xr-x 1 wsh wsh    62 Oct  8 07:26 src
drwxr-xr-x 1 wsh wsh    50 Oct  8 07:26 tests

pin-utils-0.1.0/src:
total 12
-rw-r----- 1 wsh wsh  326 Apr 22  2020 lib.rs
-rw-r----- 1 wsh wsh 2665 Apr 22  2020 projection.rs
-rw-r----- 1 wsh wsh  633 Apr 22  2020 stack_pin.rs

pin-utils-0.1.0/tests:
total 8
-rw-r----- 1 wsh wsh 564 Apr 22  2020 projection.rs
-rw-r----- 1 wsh wsh 376 Apr 22  2020 stack_pin.rs

This is problematic when one uses cargo prefetch to prefetch the crates and then runs builds as another user. Such builds end up with the following error:
error: couldn't read /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/pin-utils-0.1.0/src/lib.rs: Permission denied (os error 13)

This seems a cargo bug. Could you open an issue in rust-lang/cargo?

Right. It seems this bug is already known for six years :-( Another similar issue is even older. I'll add comment there.

Closing in favor of cargo issue.


File Transfer (not-OTA) (CON-656)

Is there any ability to transfer files between nodes? Matter specifies BDX protocol for this purpose. Are there any BDX usage examples? What is needed to implement it properly?

Diagnostics Logs Cluster uses BDX to send files to the controller, is there any way for the controller to send files to the device outside of OTA?

@Gonta01 I haven't seen any direct bdx example in connectedhomeip repository. You may have to look into the ota-provider and ota-requestor examples for that.
But, As far as I can tell, you will have to register the handler for unsolicited message handler for bdx protocol for receiving them. Construct the BDX message and use the exchange context for sending the it.
This TransferFacilitator.h can be used as well.

@shubhamdp thank you for reply! Custom cluster (similar to ota-provider/ota-requestor/diagnostics logs) must be created to transfer some files from controller to device?

There should be two implementations already in the system: Diagnostics Logs Cluster  which sends files. OTA which receives files. I would suggest working with those first before trying to build a custom cluster.
 I have a couple of devices here which are ignoring the Matter OTA system and they use their own apps to update via a private protocol. Of course that also bypasses Matter security.
I do think it is possible to hack OTA into transferring files. My idea, which I have not tried yet, it to make the user's phone into a temporary OTA provider. Then request an OTA from it filling in the metadata field of the request.  The phone would see that metadata and not send an OTA image back, instead it would send another file. Then the code in the device needs to differentiate between receiving an OTA file and a file for a different purpose.

@jonsmirl thank you for advices!

@Gonta01 If your queries are addressed can you please close this issue.


Allow use of newer npm version

env-linter should not stop process execution if a newer version of npm is used than the npm version that comes with a specific node-version. Compare node-list.
Change the implementation so that this check only fails if the npm-version is older than the node-version (which I guess is only possible with certain node version managers).

Fixed with https://github.com/namics/env-linter/commit/f71e340b50d1731b6c37fdb0ae1c4bd8d23ff68e


DEFNA Board, DSF Election Results and Advent of Code

Use this checklist to walk through all the steps you'll need to complete for each episode

[X] Download the Audio/Video from StreamYard
[X] Share the YouTube link with folks on social media
[X] Break the video into chapters
[X] Update Timestamps in Shownotes Post
[X] Publish podcast episode
[X] Add Github link/podcast url/and YouTube link to content

Episode Date
2022-12-02
Podcast
5a0856a9
Youtube
lWzvb0aLNW0
Issues
#78, #74, #16
Conferences
#75, #76, #77
Newsletter Publish
2022-12-02T08:00-08:00

t


Typo in link

in CUSTOM-SCHEMA.md, there is a typo in the link (it ends with a dot)
http://directory.apache.org/apacheds/1.0/custom-schema.html.

Thanks for the keen eye.


[WIP] abstraction for TableMetadata and ViewMetadata

@nastra would you have any concern with this change?  We looked with @pvary and it seems this would allow us to re-use a ton of code in Hive catalog between table and view persistence.

Also why don't we open this pr on iceberg itself?


book-recommendations - Books to Read on Linux

Added 4 books to read on Linux kernel

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.


Update jsoniter-scala-core, ... to 2.2.0

Updates

com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-core
com.github.plokhotnyuk.jsoniter-scala:jsoniter-scala-macros

from 2.1.15 to 2.2.0.
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 = "com.github.plokhotnyuk.jsoniter-scala" } ]

labels: library-update, semver-minor

Codecov Report

Merging #99 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master     #99   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files          24      24
  Lines         234     234
  Branches        9       9
======================================
  Misses        234     234

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 7969631...9bb88ce. Read the comment docs.


Save nginx logs in a file on host

We also need to rotate it to have a reasonable storage usage.
Update should be replicated on Ansible

We could then parse it using https://learn.netdata.cloud/docs/miscellaneous/monitor-nginx-or-apache-web-server-log-files-with-netdata


WIP load .net system.dll shim into python engine to enable compatibility with .Net8

This PR loads one of the .net shim facade dlls into the process, and importantly into the python engine so that these types are available for import without the users needing to use clr.addReference on assembly names they won't know. They would have to go lookup each type to see where it was moved between .net48 and net8.
Also adds a previously failing test.
The downside here is that

we're loading quite a few types into the process that might be unused(some will fail to load since they were moved to Nuget packages, nothing to do there.) Loading this assembly with reflection seems to take 0 -1ms - so I am not sure if that's deferred, or it's fast because it's just a shim with zero code.
Importing them into the python engine is slower 40 -60 ms on my VM. Unfortunately we do this quite frequently as the IronPython evaluators recreate the python engine whenever it executes different code, in a typical execution that will be for every single node so we will reimport these types as the python evaluator classes are lazy singletons.

So - 60ms * n iron python nodes nodes.
I am thinking I will create a new preference in Dynamo that defaults to off to load these types only if a user encounters issues. We can always change that if we prefer compatibility at the cost of performance. added a config file instead.
Additionally we can look at reusing the python engine - the code has been this way so long I am hesitant to change it without proper time to test with real world graphs using lots of python.
TODO

[x] send a PR to Dynamo repo introducing new python preference for ironPython compatibility - not sure what this should be called - ideas? in discussion with team we decided to move this preference into the package itself so we can decouple ourselves completely from Dynamo releases for these packages. We also want to focus more on PythonNet instead of IronPython.
[x] finish this PR using config file to control loading of system shims.
[ ] similar PR to IronPython2.x repo
[ ] publish new packages

tests passed merging.


java.io.FileNotFoundException: /jacoco.exec

Hello again =)
I am getting this error:
java.io.FileNotFoundException: /jacoco.exec: open failed: EROFS (Read-only file system)
Any idea where this is coming from?
Thrown in  this line:
spotifyApi = new SpotifyApi();
Thanks for the help, great wrapper so far!
Dustin

I'm getting the same error. Have you found any solution to it? Please let me know the procedure to use the library as I think I'm missing something to add.


Footer styling needs correction in home page.

The styling of the footer on the home page is not optimal. it needs some responsive CSS and also alignment.
I want to work on this issue. Please assign me and mark it as hacktoberfest.
thank you.

Hey @farhanalws4u! Thank you for raising an issue 💗 You have been assigned this issue you can start working on this👍🏻😄


Adaptive Height/Width (Fluid Design)

I have noticed that the following features are aimed at a later version:

Variable width
Active height

Is there any workaround to make the slider horizontally fluid? I can use a fixed height for the containing element, but my goal would be to use a background within the slide and anchor it to the center(h)/middle(v), keeping its width always at 100%.
I tried setting width: 100% on slides/images but realized that the containing <ul> for ui-carousel dynamically sets it's width to the sum of all image's widths so it can keep the sliding consistent. (At least on default mode, didn't try the fade option.) - Which means that it isn't that simple.
Are there any "easy" hacks to keep a fluid layout with ui-carousel? Is there any pre-release version with such a feature?

@nmindz Currently, there is no hack to make the fluid layout like variable width. I will focus on it on next version. Wait for me a few days


Setup FAQ for linking

Sets up id for each FAQ question so #hyperlinks work. Sets the id on the <dt> but perhaps we should do it on the <dd>?
Adds analytic event when a user clicks on a link to a question or expands a question

Closes: https://github.com/findthemasks/findthemasks/issues/740

This is very cool. Thanks for doing this @saikatbhadra ! I see you enabling us to link to exact questions.
Would it be possible to adopt this for the header class? We also want to link people sections.
Ideally for the Makers it would be https://findthemakers.com/makers/faq#ftm-faq-makerspace-header

Any id works on the html. Looking at the makers section it looks like it currently has an id of section-makers so if you link to https://findthemasks.com/faq#section-makers then it will go to the makers FAQs.

That’s great! If you have time to write a Wiki for linking using that for the non-devs like me to refer to when interacting with collaborators/partners or on socials. I can also work on that later tonight & ask for your help to edit it?

In this case, we aren't doing anything special, we are just following standard html method for how to link to different parts of a page. Here are two articles that explain how it works, you could link to them on the wiki:
https://blog.hubspot.com/marketing/jump-link-same-page
https://stackoverflow.com/questions/2835140/how-do-i-link-to-part-of-a-page-hash


Feature -- Build Script for Scratch Org

Changes made:

Addition of basic project files
Addition of bin.install-scratch.* scripts modeled after the trailheadapps/dreamhouse-lwc app.

@afawcett  -- FYI on this PR.


Add interface which is to be used by end users

Would be good to have an interface, which end user could implement to be able to use async/await keywords.

Done by https://github.com/botsman/hxasync/commit/baa6fa0f10e2c26e5547de34ef1a7484cfcb1497

Done by https://github.com/botsman/hxasync/commit/baa6fa0f10e2c26e5547de34ef1a7484cfcb1497


Cover RomanNumeralExtensions with unit tests

I'll take it

No apparent progress on this, so I created Pull Request.


Custom handler for RSpec tests?

Hi,
I'm trying to write an extension that will document my rspec tests. Eg,
RSpec.describe "Aggregated status" do
  # Test aggregated status request, by sending a request
  # and verifying that an aggregated status is received.
  it 'responds to aggregated status request', version: '>=3.1.5' do |example|
    # do stuff
  end
end

I'm looking at https://yardoc.org/guides/extending-yard/writing-handlers.html but feel stuck. I'm trying something like this:
class RSpecSpecificationHandler < YARD::Handlers::Ruby::Base
  handles method_call(:it)		# this seems to work for method calls, but not the rspec 'it'
  def process
  	# what goes in here?
  end
end

Are there any examples or pointers that can help me, or do you have some tips?
I found this very old repo https://github.com/burtlo/yard-rspec, but it seems it was not working even back then.

I've looked at existing plugins, but only found things 10+ year old, and haven't been able to get any of then to generate anything.
Can anyone help me with a small working example, or tell me why my attempt above doesn't work?

Looking more at https://github.com/lsegal/yard-spec-plugin I got it to generate something. But it seems to to assume that specs are linked to a specific instance method, and are nested inside an rspec descibe() block.
My use case is very simple, as described above: rspec it() blocks documented with a comment. The specs are not linked to a class or method.

I've worked more with the yard-rspec plugin and think I understand a bit more.
One thing I don't understand is how I can add a new main section in the resulting html. I would like by RSpec tests to show up under a new main section called eg. "Specifications", because my tests are not linked to instance methods.
Do I need to create a new subclass of CodeObject or can I just work with the template system?


Producer : No ressource production even with enought space

Some ressource producer stop working even if there is enought space

(fake ressources ;p )
Le ven. 31 mai 2019 à 17:20, ludoc17<EMAIL_ADDRESS>a écrit :

[image: image]
https://user-images.githubusercontent.com/35073850/58715900-1e815100-83c8-11e9-8c6a-773317e929ca.png
Some ressource producer stop working even if there is enought space
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kluthen/upsilon_cities_go/issues/90?email_source=notifications&email_token=AAFXDBL4QCSR7G2WZSIK7BTPYE63RA5CNFSM4HR3VTT2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GW7ONUQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFXDBPEXBVCJAH7WFSRQ33PYE63RANCNFSM4HR3VTTQ
.


Updates the http proxy

This update adds a command to manually start the http proxy. It also adds the GetAddr() function to the interface.

I've approved, but are you sure that GetAddr() returns nil rather than panic, if the the server isn't started?

I've approved, but are you sure that GetAddr() returns nil rather than panic, if the the server isn't started?

That wasn't the case, but I've changed the implementation to behave like so.