Upgrade k8s-openapi to 0.16

[x] cargo upgrade k8s-openapi --workspace for 0.16.0
[x] remove references to api resources gone in 1.25
[x] bump our MK8SV and local pin of k8s-openapi to v1_20 using just bump-k8s
[x] fix k3d CI issue
[x] reproduce v1_25 issue #997 (it's worse than expected)
[x] report findings upstream  https://github.com/kubernetes/kubernetes/issues/111985

TL;DR: upstream bug is bad, breaking, and we need to do something to support v1_25, but we cannot detect it, so it needs to be user-opt in. Have left the evar-based fix in a branch. See comments below.

Codecov Report

Merging #1008 (2954ae8) into master (cc2a2b9) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 2954ae8 differs from pull request most recent head 0954e00. Consider uploading reports for the commit 0954e00 to get more accurate results

@@           Coverage Diff           @@
##           master    #1008   +/-   ##
=======================================
  Coverage   71.89%   71.89%
=======================================
  Files          65       65
  Lines        4637     4637
=======================================
  Hits         3334     3334
  Misses       1303     1303

Impacted Files
Coverage Δ

kube-core/src/request.rs
96.07% <100.00%> (ø)

Integration test failure from an integration test in derived_resource_queriable_and_has_subresources:
https://github.com/kube-rs/kube-rs/blob/master/kube/src/lib.rs#L234-L303
with

Error: Api(ErrorResponse { status: "Failure", message: "Object 'Kind' is missing in '{}'", reason: "", code: 500 })

looks veeery similar to the original bug, but it's actually happening on get_status...

Error: Api(ErrorResponse { status: "Failure", message: "Object 'Kind' is missing in '{}'", reason: "", code: 500 })
happens exactly on the
foos.delete_collection(&DeleteParams::default(), &Default::default()).await?

line. so we can reproduce Arnav's issue on k3d locally with k3d flag: --image=rancher/k3s:v1.25.0-k3s1-amd64

Ok, I think the only thing we NEED to do here is to force in the kind and apiVersion of DeleteParams:
apiVersion: meta.k8s.io/v1
kind: DeleteOptions

to the output. Never done this before, but how hard can it be.

Well, great. Serializing with kind/api_version fails in Kubernetes v1.20 (our MK8SV) with:

Error: Api(ErrorResponse { status: "Failure", message: "no kind "DeleteOptions" is registered for version "meta.k8s.io/v1" in scheme "k8s.io/apiextensions-apiserver/pkg/apiserver/apiserver.go:52"", reason: "", code: 500 })

Guess it could be wrapped in an k8s_openapi::k8s_if_ge_1_25! check... Will look at it more tomorrow.

Well, this is really quite bad. It's not even trivial for users to deal with this because it effectively forces the user to deal with a zero version skew (against our versioning policies).
We have two error cases:
Serializing kind/apiVersion breaks on Kubernetes < 1.25
api.delete_collection returns:
(Error: Api(ErrorResponse { status: "Failure", message: "no kind \"DeleteOptions\" is registered for version \"meta.k8s.io/v1\" in scheme \"k8s.io/apimachinery@v1.24.1-k3s1/pkg/runtime/scheme.go:100\"", reason: "", code: 500 })

Not serializing kind/apiVersion breaks on Kubernetes >= 1.25
api.delete_collection returns:
Error: Api(ErrorResponse { status: "Failure", message: "Object 'Kind' is missing in '{}'", reason: "", code: 500 })

So the user gotta pick the v1_25 feature just as they upgrade to it...
we also would need to propagate k8s-openapi features in integration tests for just this.
I don't see any good solutions for this at the moment. Comments welcome.

Have reported findings upstream in https://github.com/kubernetes/kubernetes/issues/111985 .
In the mean time, options as I see are:

release with the caveat that v1_25 is likely broken for delete_collection calls
release with zero-version-skew requirement and do a (currently untestable) cfg(feature = "v1_25") in the middle of core
hold off releasing until upstream is dealt with

I don't like 3, because historically it is always very confusing for users to have to pick an older k8s-openapi.
I don't like 2, as it's super awkward, gives the impression that all is good, when it really breaks the version skew requirements (which people definitely do not expect to break on them during cluster upgrades).
So Leaning towards 1 with a caveated release and hope pressure can help upstream.

Ok, have added an unstable evar to track this because there's no good way to support v1_25 without the user making a choice here.
Why?

if we detect Kubernetes version via k8s-openapi features, it's still broken if user is running on a newer cluster
if we detect Kubernetes version via an api call, it might be broken when/if Kubernetes actually resolves this

Thus, we need to make this an opt in thing. Either via an unstable EVAR or via an unstable feature.
Went with an evar rather than a feature because it's less taxing on our setup, and it doesn't break when/if upstream fixes the bug and we have to remove the feature.
Planning on removing the hacky evar in api.delete_collection when upstream fixes the bug.

Honestly I'd just say upstream K8s is broken here and let them fix it (option 1). Especially since it looks like they're already working on a fix, and that I'd wager that there isn't a single K8s cluster in the world that is only running kube-rs clients.

Honestly I'd just say upstream K8s is broken here and let them fix it (option 1). Especially since it looks like they're already working on a fix, and that I'd wager that there isn't a single K8s cluster in the world that is only running kube-rs clients.

It's not too different from what we are doing now tbh. We don't have to announce the evar as a workaround, but we do need to work around it to keep CI happy for now.

we should really have the workaround there for us to at least keep CI happy.

Does it still fail with https://github.com/kube-rs/kube-rs/commit/f44041560e350b2276e44ba9632ee3455a3adf31 ?
I think integration tests are all using the default.

Does it still fail with f440415 ?
I think integration tests are all using the default.

Think the e2e test which is using background deletion.

https://github.com/kube-rs/kube-rs/blob/cc2a2b9a9fa27167f988474d14a925cb8a96afc8/e2e/job.rs?rgh-link-date=2022-09-20T18%3A09%3A54Z#L44-L45
So delete is also affected?
Don't we need to work around this?
https://github.com/kube-rs/kube-rs/blob/cc2a2b9a9fa27167f988474d14a925cb8a96afc8/kube-core/src/request.rs#L126-L134
But apparently it's already passing the tests.

Ah, sorry, I am wrong.

delete is not affected (just tested)
e2e does not fail on this in 1.25 (because it's using delete)

So we can technically remove all this evar gunk for ci :thinking:
Personally, I feel like having valid work around for an actual release is useful here. Otherwise users have no way around this it if they are testing with v1_25 - save for recreating their cluster with an older version - and we can take out the hack when they fix it upstream without much ceremony. But it is an awkward evar lookup on the other hand.
Will remove the workaround if both of you feel the same.

Anyone for an approval for this?

I'm still debating whether this workaround should be included or not.
Options:

Include this workaround and let users test against 1.25 with evar
Don't include this workaround, but mention this in release note, so users can create a temporary fork with it to test against 1.25
Don't include this workaround, but create a branch that users can use to test against 1.25

1 is most convenient for users, but I'd prefer not to include this hack, especially because most users won't be using 1.25.
2 may be annoying for users, but I don't think many will need 1.25 now.
3 seems like a nice middle ground.
I'm leaning towards not including (3).

I really don't think it is a big deal either way, I just don't want us to say we don't support a fully released Kubernetes version because we don't think it's needed yet. That sends a bad signal.
Happy to move the workaround out to a branch though, that is workable for keen users. And since both of you have reservations about including it, it'll at least be less controversial :-)

Released in 0.75.0.
Release notes are currently stashed in the draft release for 0.75.0. Will publish that tomorrow (with updated code links) at some point after the docs.rs build completes. Tried to highlight on user actions needed and made a fourth point for all the improvements.


Can ProcessBuilder be used to run sendctrlc.exe?

Currently, sendctrlc.exe is spawned in winp.cpp.
Is it possible to use java.lang.ProcessBuilder to spawn sendctrlc.exe and, thus, simplify code?
If no, it'd be great to write a comment in code explaining decision.

@oleg-nenashev @stephanreiter Any thoughts? I would appreciate your feedback.

Sorry, missed the previous notification.
IIRC there was a discussion about that in the pull request, will try to find it.
Native code is not considered as API, so we can always change it without breaking changes.

Using ProcessBuild is no problem. Good idea! Less native code ...
SendCtrlC ended up in native because it started there with some implementation that didn't use a separate EXE.

@oleg-nenashev Thanks. I meant something like
  public static boolean sendCtrlC(int pid) {
    Process process = new ProcessBuilder("sendctrlc.exe", pid).start();
    return waitFor(process, 5000) != null;
  }

  @Nullable
  private static Integer waitFor(@NotNull Process process, int timeoutMillis) {
    long stop = System.currentTimeMillis() + timeoutMillis;
    while (System.currentTimeMillis() < stop) {
      TimeoutUtil.sleep(100);
      try {
        Thread.sleep(100);
        return process.exitValue();
      }
      catch (Exception ignore) {
      }
    }
    return null;
  }

This way, ProcessBuilder is not exposed in winp's API, so it can be changed without breaking changes too.

Will that terminate the sendctrl.exe process after 5secs? That shouldn't be left lingering.

Same should be (made) true for the native code! :)

I don't know much about ProcessBuilder anymore. :)
And sendctrlc.exe will first detach from its console, then attach to the  process to avoid what you describe w.r.t. the parent process.
 FreeConsole();   if (!AttachConsole(pid)) {     return GetLastError();   }

@stephanreiter Sorry for not being clear. Yes, sendctrlc.exe deattaches from its initial console to be able to attach to a console of  the specified process. But what if several processes are already attached to the console, sendctrlc.exe tries to attach to? For example, parent_pid and pid are attached to the same console and sendctrlc.exe pid is spawned. Looks like parent_pid will receive CtrlC event as well. Honestly, I haven't managed to reproduce such case, just wondering if it's possible.

Ah, now I understand. Well, then the Ctrl+C will go to the parent as well. I guess that should be documented to make it obvious.


Rotate the Meals sheet to read more like a calendar

This is the current layout:

A layout like this would be more easily readable at a glance, as it matches the way a standard calendar is read.

In fact, the "Day" on the top left could be replaced with "Week Jan 07"

This issue was fixed with the transpose menu PR. The menu now appears as formatted in the second image


Implement pubsub_publish_ordered_messages sample

https://github.com/googleapis/nodejs-pubsub/blob/dcdec71e3a496b041dc8d1d0f03eda85d5d0cf63/samples/publishOrderedMessage.js#L46-L81

This sample (pubsub_publish_ordered_messages) does not exist, it seems to have been a typo that I picked up when collecting samples from other languages. Recent versions of nodejs call it pubsub_publish_with_ordering_keys, like all other languages:
https://github.com/googleapis/nodejs-pubsub/blob/85fec09bfd956adbeeb8a819af796a3cedb3befe/samples/publishOrderedMessage.js#L47-L89
Furthermore, we have this in C++ already:
https://github.com/googleapis/google-cloud-cpp/blob/4b12aea940d4abb1d502fb7cd41419d3c7d1feac/google/cloud/pubsub/samples/samples.cc#L722-L753
Closing as duplicate.


Re-evaluate Qwen 2.5 Coder

New weights: https://www.reddit.com/r/LocalLLaMA/s/iLL9bNRkJo

32B complete, still need to re-do the others.

Done.


Add arrow to Python overview

I am also in the process of adding 3 more guides for Arrow: SQL on Arrow, Import from Arrow, Export to Arrow (following the Pandas guides structure). I'm going to try to cover all the types of Arrow objects we can read/write there (Tables, datasets, recordbatches, and any others I'm missing?).

@Alex-Monahan We also support Scanners.

Great feedback! I will likely just list all of the Arrow types we can read here, but refer to a guide that will have an example for each type!
Good call out on the different ways to fetch also - I can mention that here and refer to the upcoming guide as well.

Ok, I made some changes - let me know if that looks better!

Alright, now it's ready for another review. Thanks for the feedback - it's a lot more thorough this way!

@pdet is this ready to merge?

Yes, looks great! :)


event.target no longer hold text-editor-element from 1.13.0-beta0

Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
What event.target is holding was changed from Atom v1.13.0-beta0.
Which was hold text-editor-element in v1.12 but its changed to hold hidden-input-element.
So code like event.target.getModel() no longer work from v1.13.
Is this intentional change or accidential change?
Steps to Reproduce
Define following command in init.coffee, and invoke it via command-pallette or via keymap(both results are same).
atom.commands.add 'atom-text-editor', 'dev:show-event-target-of-text-editor-scope', (event) ->
  console.log event.target
  # following line throw exception from v1.13.0 since its no longer hold texxt-editor-element
  # console.log event.target.getModel()

In atom v1.12.0: <atom-text-editor class="editor vim-mode-plus normal-mode" tabindex="-1" data-grammar="source coffee" data-encoding="utf8"></atom-text-editor>
In atom v1.13.0-beta: <input class="hidden-input" tabindex="-1" data-react-skip-selection-restoration="true" style="transform: translateZ(0px); top: 155px; left: 84px; width: 7px; height: 18px;">

So package code event.target.getModel() no longer work from v1.13.0
Versions

atom-beta

$ atom-beta --version
Atom    : 1.13.0-beta1
Electron: 1.3.6
Chrome  : 52.0.2743.82
Node    : 6.3.0

apm-beta

$ apm-beta --version
apm  1.14.1
npm  3.10.5
node 4.4.5
python 2.7.6
git 2.7.4

When I clicked editor, event.target also hold text-editor-element which was very useful, but from v1.13.0-beta0 it just return <div> or <span>(just exact element which was clicked), which is not useful.
My package need big rewriting to fix this, before that I want to confirm this change is intentional and also want to know alternative way to get editorElement clicked from event.

I think there's a .closest() method you can use?  /cc @as-cii

Thanks @50Wliu , I'll try, but I'm also curious if code like this still work on latest atom? If event.target point exact clicked element, its no longer point to paneElement which this line of code assuming.

@t9md thanks for the report, and apologies for breaking your package!

but I'm also curious if code like this still work in latest atom?

This change should apply only to editor elements, so I think PaneElement should still work fine.

My package need big rewriting to fix this, before that I want to confirm this change is intentional and also want to know alternative way to get editorElement clicked from event.

Yes, the change was intentional and was caused by removing the shadow DOM boundary from atom-text-editor elements. However, I wonder if, while we're still in beta, we should provide a shim when packages try to access the .target property on an Event object, although that would be somewhat inconsistent with document.activeElement, which we cannot provide a shim for.
Searching for usages of target.getModel() in packages yielded the following results:

atomic-emacs/lib/atomic-emacs.coffee
choose-pane/lib/main.coffee
context-git/lib/command.js
cursor-history/lib/main.coffee
elmjutsu/lib/autocomplete-provider.js
expand-region/lib/selector.coffee
extract-component/lib/extract-component.js
finalbuilder/lib/finalbuilder-utils.coffee
gherkin-table-formatter/lib/gherkin-table-formatter.coffee
haskell-ghc-mod/lib/upi-consumer.coffee
haskell-pointfree/lib/haskell-pointfree.coffee
ide-haskell/lib/ide-haskell.coffee
ide-haskell-hasktags/lib/ide-haskell-hasktags.coffee
ide-haskell-repl/lib/ide-haskell-repl.coffee
line-ending-selector/lib/main.js
line-ending-selector-unix/lib/main.js
nvatom/lib/notational-velocity.coffee
open-html-in-browser/lib/main.coffee
quick-file-actions/lib/quick-file-actions-view.js
quick-query/lib/quick-query-result-view.coffee
vertical-motion/lib/vertical-motion.coffee

Interestingly, the line-ending-selector:convert-to-LF and line-ending-selector:convert-to-CRLF commands seem to be broken on beta because of the same problem, so I am going to change that package to use target.closest('atom-text-editor') instead, and prepare a hotfix to release later today.
@nathansobo: what do you think? I am a little concerned about packages breakage at this point, although (based on the search above) it seems like only a few are using event.target and assume it is a TextEditorElement, so hopefully they can be fixed during the beta period. Still, a shim is probably warranted, as there might be usages of the .target property that are difficult to catch with a regular expression.

@as-cii

This change should apply only to editor elements, so I think PaneElement should still work fine.
Got it, thank you for clear explanation, I've already fixed my package using closest('atom-text-editor').


Pass -PesterResults to Coveralls

Hoping to fix #808
Coveralls calls Invoke-Pester -CodeCoverage $Include -Quiet -PassThru, which maps to $Configuration.CodeCoverage in Pester 5.

How did an AppVeyor change break the Travis build?

Ah, yes the PSGallery is down at the moment. Try again later.

Looks like PSGallery is back up.


Prevent "cannot lock ref" git error

> git pull origin master
From github.com:Microsoft/vscode
 * branch                  master     -> FETCH_HEAD
error: cannot lock ref 'refs/remotes/origin/master': is at 2e4bfdb24fd137a1d2e87bd480f283cf7001f19a but expected 70ea06a46fd4b38bdba9ab1d64f3fee0f63806a5
 ! 70ea06a46f..2e4bfdb24f  master     -> origin/master  (unable to update local ref)

This issue occurs when git-radar is doing a fetch in background and user runs git fetch/pull. Git has index.lock to lock index during a fetch, so you cannot corrupt the index by doing concurrent fetches. Your git command fails because of this lock prevents git modifying index.

https://github.com/michaeldfallen/git-radar/issues/81#issuecomment-345191136

Also: fatal: Cannot rebase onto multiple branches.

I'm in a team. Recieving this error. What should I do so I am able to pull again?

@Kalela and For future visitors, This StackOverflow question will help you. https://stackoverflow.com/questions/6656619/git-and-nasty-error-cannot-lock-existing-info-refs-fatal

I still see it

My steps:

Type git pull origin master in the terminal, dont press enter
Run the command Git: Fetch, quickly switch to terminal to press enter on the git pull origin master

Oh this can happen on fetch too. Great catch.

Following @ramya-rao-a steps I do not see any errors in vscode -> verified

This is timing dependent, and I actually tested the build which does not have the fix. So leaving to @ramya-rao-a to verify on her machine


[Android][Production]: java.lang.IllegalArgumentException sectionName is too long

Hi,
A user reported an issue that the app is not opening. Every time he clicks on the launcher icon, the app crashes.
When I checked the Crashlytics for that user_id, it showed the below crash.
Fatal Exception: java.lang.IllegalArgumentException
sectionName is too long

Fatal Exception: java.lang.IllegalArgumentException: sectionName is too long
       at android.os.Trace.beginSection(Trace.java:287)
       at androidx.tracing.TraceApi18Impl.beginSection(TraceApi18Impl.java)
       at androidx.tracing.Trace.beginSection(Trace.java:6)
       at io.flutter.embedding.engine.dart.DartMessenger.lambda$handleMessageFromDart$0(DartMessenger.java:17)
       at io.flutter.embedding.engine.dart.DartMessenger.$r8$lambda$6ZD1MYkhaLxyPjtoFDxe45u43DI(DartMessenger.java)
       at io.flutter.embedding.engine.dart.DartMessenger$$InternalSyntheticLambda$0$75ebfcfd53b0b0a884b1e22267a97587635cd2630d2f814c3024af8922adcf72$0.run(DartMessenger.java:12)
       at android.os.Handler.handleCallback(Handler.java:938)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:210)
       at android.os.Looper.loop(Looper.java:299)
       at android.app.ActivityThread.main(ActivityThread.java:8138)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:556)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1037)

Device
Brand:Xiaomi
Model:M2101K6R
Orientation: Portrait
RAM free: 2.4 GB
Disk free: 64.14 GB

Operating System
Version:Android 12
Orientation: Portrait
Rooted:No

Fatal Exception: java.lang.IllegalArgumentException
sectionName is too long

This seems to be coming from native:
https://android.googlesource.com/platform/frameworks/base/+/refs/tags/android-12.1.0_r1/core/java/android/os/Trace.java#284
The sectionName max need to be 127 unitcode long and in your case / app, it seems to be exceeding the limit and hence the error.

very time he clicks on the launcher icon, the app crashes.

Are you able to replicate this locally ?

no

With no concrete reproducible use case to verify, I'll label it for further insights from the team.
For team's reference: https://github.com/flutter/flutter/issues/99980#issuecomment-1066443358
/cc @chinmaygarde

This seems to be caused by the trace event names being too long. Specifically it is this call here. Depending on how long the channel name is, it is totally possible to make the trace size go over some internal limit.
As @darshankawar pointed out, documentation for tracing says the section name must be 127 unicode code units long.
The easiest quick fix would be to remove the trace. Though ideally, we should make sure trace names are manually truncated or const strings.
These traces were added approximately 5 months ago by @jiahaog and reviewed by @blasten @xster @dnfield with a cross reference to an internal issue. Just a heads up that this could lead to runtime instability.

The goal of adding the channel name into the trace was to assist with reading traces and knowing which channel the trace was happening on.
We should update all those call sites to make sure we don't exceed 127 code units when using any kind of dynamic string.

Starting with a revert to get this resolved ASAP.

Argh. This is not easily revert-able because of conflicts. I'll see if I can manually fix first.

I have a fix forward ready.

Should this be considered a CP candidate?
Alternative question: is there anything we can do to guarantee this ends up in the next beta?  @zanderso

@dnfield We can request a cherry-pick to 2.12. Since there's no tag for it, that would happen directly in the release chat. Does the PR apply cleanly to the 2.12 branch?
It is very late in the cycle for a 2.10 cherry-pick. A few questions:

@darshankawar have you seen any other reports like this? Trying to understand how widespread this issue is.
@dnfield Does https://github.com/flutter/engine/pull/32042 apply cleanly to 2.10?
@dnfield How risky is https://github.com/flutter/engine/pull/32042? If there's any chance that the forward fix could introduce a new problem, then I think I'd say no to a cp. A straight revert would be easier to approve at this stage, but the issue would still need to be quite severe and widespread.

@darshankawar have you seen any other reports like this? Trying to understand how widespread this issue is.

@zanderso No. This was the first report I saw throwing such error. Didn't find any similar reports before.

flutter/engine@c5e958ebde36887f2954c5df5ad3b3dfaf790474 cleanly cherry-picks on to flutter-2.12-candidate.5.
I'm not sure what the right branch or tag to check for 2.10 is.
I avoided doing a revert because a revert would not cleanly apply to main and the conflicts were not super trivial to resolve.


Need to handle confirm:

Type
self confirm: 'hi'

in a workspace. That should raise a Jadeite dialog which the user can return true or false.

Also check as well.
self inform: 'hi'


is model.fit() accumulative?

Hi, I am new to keras and neural network, and I am wondering if model.fit() is accumulative?
So basically, I accidentally killed the program yesterday, but however I do save weights on every epoch. So I was wondering if I could load the last weight into the model and then call model.fit()?

Yes, you can.
On May 12, 2016 6:20 PM, "flyingpoops"<EMAIL_ADDRESS>wrote:

Hi, I am new to keras and neural network, and I am wondering if
model.fit() is accumulative?
So basically, I accidentally killed the program yesterday, but however I
do save weights on every epoch. So I was wondering if I could load the last
weight into the model and then call model.fit()?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/issues/2712

OK, thanks. Just to want to validate one other thing. When fit() in keras/models.py is called, it returned with the fit() in keras/engine/training.py. Am I right?

@fchollet

@flyingpoops Yes, the fit() implementations in keras/model.py do some setting up and then call fit() in keras/engine/training.py.

I think now I have a better understanding of keras, thanks @jfsantos


Add python wheels

@mwestphal please review
The generated wheels can be download here: https://github.com/Meakk/f3d-superbuild/actions/runs/5590519905
You can see the content of wheels using unzip -l foo.whl
You can install it locally using pip install foo.whl (make sure to use the correct one and to run it in a venv)

I suggest we move forward and even if it's not perfect, the wheels are properly generated.
Here is the dispatch workflow run: https://github.com/Meakk/f3d-superbuild/actions/runs/5753444662
We still have many things to do for Python anyway before the release (rework bindings, monkey patching and pytest).
I tested the wheels 3.11 Linux and 3.9 Windows successfully.
I identified these remaining things to do in a (more or less) near future:

[ ] Enable sscache and run the worflow automatically (@mwestphal? ^^)
[ ] Avoid symlink/soversion duplication of zlib (and future shared deps) to reduce Linux/macOS wheel size
[ ] Enable TBB (now that shared libs copy is working, it should work out of the box)
[ ] Enable raytracing? Probably challenging because of dynamic loading
[ ] Add tests of wheels with pytest (can be run automatically by ciwheelbuild after each wheel generation)
[ ] Add more platforms (priority on ARM), cross-compiling is supported by ciwheelbuild
[ ] Add a release workflow for automatic upload to PyPI

Good writeup! it should be put into a issue once this is merged


After every level

After every level there should be a thing on the screen where it says "we morn the many lost in battle" and shamefully shows you how many frogs died, don't add a skip button

Yes!

YES! YES! YES!


Add "online" viewing

It would be incredible if manga-dl could display manga from a website like so manga-dl --online 'NAME_OF_MANGA_SERIES. This could be useful if you wanted to just read a manga series without wasting hard drive space as well as not having to see all those annoying ads that you find on some manga websites. This feature could open the manga in a pdf viewer like zathura.

Hi.
Unfortunately, to open a pdf file, you first need to create it.
And for this you need to download all the images to disk.
manga-py thought of exactly as a means of something that would help you read manga on your phone, without thinking about your mobile traffic.
I understand what you mean, but I am not sure that it is possible to implement it at all.

Cant the images be streamed? I dont have a lot of technical knowledge on this aspect. An example of this could be mpv (the music player), idk how it does it but it can play youtube videos without downloading them. Btw i love your script anyways

Thank.
At the expense of the pipe ... I'm not sure that this can be implemented (I don’t know of any programs for viewing pdf that can read from the standard output)
As for mpv, there’s a slightly different story. He just knows how to open video by url, if my memory serves me (he uses youtube-dl to get links, like)
Technically, manga-py can give links to images, but it often does not make sense (see #184)

Some sites encrypt their images, some do not allow receiving images via direct links.
On some sites, the link lifetime is a few seconds :-)

P.S.
I read #201
Putting something as root is not a good idea.
Better use setting for user or venv (https://docs.python.org/3/library/venv.html)

Thank you so much for the extensive help. I reinstalled the script without root and it worked perfectly fine. Btw would you mind me posting a PKGBUILD of this program to the AUR?

No problems.
Thank you for using it.

I will close it. If you still have questions, feel free to create a new issue.


docs: polish up guide docs

Summary

Changes worth mentioning:
Remove https://www.rspack.dev/guide/tech/nodejs and move the use method of node-polyfill-webpack-plugin to resolve.fallback.
Checklist

[ ] Tests updated (or not required).
[x] Documentation updated (or not required).

👍


Clear unused variables in X509_print_ex()

Clear unused variables in X509_print_ex()
CLA: trivial

This pull request is ready to merge

Merged to master branch. Thank you for your contribution.


When properties appear in propstat with no value, don't call deserializers

Related to #707 #709
@DominikTo

:+1:

:+1:


avoiding potential type's mismatch

avoiding potential type's mismatch during concatenation

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

The only valid type here is string, if there's something else that's a separate issue. Be sure to provide a minimal reproducible example when reporting an issue, or a test when submitting a PR.


Code that detects the label column for a table is case-sensitive

I just noticed that a column called Name is not being picked up as the label column for a table.

Here's the code at fault: https://github.com/simonw/datasette/blob/0a7621f96f8ad14da17e7172e8a7bce24ef78966/datasette/database.py#L288-L291

I'm feeling rushed today so I'm going to fix this without adding a test!


Size change on load [ANDROID]

Hello,
Most of the time, when loading the ad, the size of the ad changes.
It is small then becomes a correct size for display on the screen.
We request multiple sizes
[[320, 460], [300, 250], [320, 160]]

Hi @fooshi69 , please check on latest release 0.5.0. The issue is not reproduced


ThemeProvider issue with Firefox

Hi guys, I've a strange issue with Firefox (it works in Chrome). Both of them in their latest versions.
I'm using ThemeProvider surrounding my app with it.
As you can see in screenshots in Firefox the theme doesn't get injected (console.log).
FIREFOX:

CHROME:

Have you ever faced this kind of issue?

Please refer with usage questions to Stack Overflow, as you're more likely to get quicker and helpful answers there ❤ Repository issues on GitHub are great for that, issues, things that need to be resolved in the library itself, or can't be resolved by anyone but the maintainers. While I (and many others on other repos) are happy to eventually answer usage questions, styled-components is a busy repo and mostly stable and slow moving towards new releases, so you're not likely to get fast responses here


Update metadata annotation

This PR replaces all oboInOwl:created_by and oboInOwl:creation_date annotations by dcterms:contributor and dc:date annotations, respectively.
In addition, wherever possible, “old-style” contributor identifiers (consisting typically of a CRS ID or similar initials) are replaced by proper ORCID IRIs.
There are a few old-style identifiers that couldn’t be mapped to ORCID IRIs: dos, david, and sr544. For those, the annotations have been changed to dcelements:contributor instead (for which there is no requirement that the value is a valid IRI), and the values have been prefixed with FBC:.
There is little doubt, I think, that dos and david both represent David Osumi-Sutherland, but given that at least two other “Davids” have worked for FlyBase over the years, I didn’t change those identifiers for David’s ORCID IRI without confirmation. We can always update them later.
As for sr544 (Simon Reeve), I didn’t follow Nico’s suggestion to create a Wikidata entry: I am reluctant to create an entry for a person I know nothing about apart from the fact that he has worked for FlyBase at some point. Again, we can update the corresponding annotation later if needed.

The job exceeded the maximum log length, and has been terminated.

hmm, wonder if there is a way to hide all the 'Unrecognized tag' output

I think it should be fixed in OboModel.pm: https://github.com/FlyBase/flybase-controlled-vocabulary/blob/9fddeb926956dfdf07bf9a72ea1e9e363cf800e4/external_tools/perl_modules/releases/OboModel.pm#L75
property_value should be added there in the list of recognised tags.

If you are happy doing this then you can try it (I don't know perl)

wow, output looks so much better!

I think this is ok for now, but we should try to sort out outstanding editors soon, so maybe leave #1459 open for now (or make a new ticket).


Split user pw into extra table

In order to never expose a user password we could move the user password into a separate table like we did with the user session (though for another reason). At the moment we are risking with every query to forget about removing the user password and exposing it to the frontend

@tonioriol or @eriklindgren what do you think? Any other ideas or best practices how this stuff is solved?

That was also my thinking to solve this issue, so I like it. It is in fact how it's done in EventBlender db!

You guys know way more about this project than I, but while I think this solution is better than nothing, it does feel wrong to let the libraries we use dictate the database schema. I would prefer to do something like this if possible: https://www.prisma.io/docs/concepts/components/prisma-client/excluding-fields

This is mostly what we already have: the exclude method. So, I guess it's fine to leave it as is in that case.
Of course, another option is to use a select clause. I don't understand why this isn't mentioned in the Prisma docs. I already read about it the other day in those very same docs for this very same reason, and I was surprised they don't mention it.
I even investigated how to use select for that purpose, and it turns out you can't combine it with include, which I used for loading relations. So what you have to do in places where your query needs a relation, and you want to select only some fields is to load the relations also using the select clause. It's weird, but that's how it is.
But both solutions have the same root problem to me, and is that you have to be explicit with either of them. It's too easy to accidentally leak the password to the client if you have to do it by hand. And if/when new developers join the project who may not even be aware of this, it could be too risky.
So, while I agree it sounds bad that the framework forces us to design the schema in a certain way, I don't know, I still think it's the best option.

Yeah absolutely agree with you here Toni!
Its also not just about new people joining. You make a complex query where somewhere we have a user and then you just forget. Its just too risky.
But what would we add to this new table? The email as well? All personal information?

I think this is a great example of why something like the views/templates in Phoenix makes a lot of sense: make sure you explicitly state what data you return from your endpoints. Moves the whole issue away from the db interaction.
Anyway, I rest my case, it seems like you're in agreement over the best path forward ⭐


Merge Roslyn branch to Master

@Microsoft/fsharp-compiler @jaredpar @cyrusnajmabadi

Looks good to me.


[SmartWallet] caller is not an admin

When trying to add a new admin to smart wallet, the method throws a transaction error.
╔═══════════════════╗
║ TRANSACTION ERROR ║
╚═══════════════════╝

Reason: AccountPermissions: caller is not an admin

╔═════════════════════════╗
║ TRANSACTION INFORMATION ║
╚═════════════════════════╝

from:      0x53C0FbFcD60adE11E507912036e6819c2E561FC1
to:        0x53C0FbFcD60adE11E507912036e6819c2E561FC1 (ManagedAccount)
chain:     ERC-4337 Custom Network (80001)
data:      0x4b0bddd20000000000000000000000000037434a053e93f2f35a1e04a8908d8feec787100000000000000000000000000000000000000000000000000000000000000001
method:    setAdmin("0x0037434a053e93f2F35a1E04A8908d8feec78710", true)

╔══════════════════════╗
║ SOLIDITY STACK TRACE ║
╚══════════════════════╝

File: contracts/extension/upgradeable/AccountPermissions.sol

40      using EnumerableSet for EnumerableSet.AddressSet;
41
42      bytes32 private constant TYPEHASH =
43          keccak256(
44              "SignerPermissionRequest(address signer,address[] approvedTargets,uint256 nativeTokenLimitPerTransaction,uint128 permissionStartTimestamp,uint128 permissionEndTimestamp,uint128 reqValidityStartTimestamp,uint128 reqValidityEndTimestamp,bytes32 uid)"
45          );
46
47      modifier onlyAdmin() virtual {
48          require(isAdmin(msg.sender), "AccountPermissions: caller is not an admin");   <-- REVERT
49          _;
50      }
51

Sample code:
const privateKey = process.env.PRIVATE_KEY as string;
const personalWallet = new PrivateKeyWallet(privateKey, Mumbai);

const adminPrivateKey = process.env.ADMIN_PRIVATE_KEY as string;
const adminWallet = new PrivateKeyWallet(sessionPrivateKey);
const adminAddress = await sessionWallet.getAddress();

const config: SmartWalletConfig = {
  chain: Mumbai,
  factoryAddress: process.env.FACTORY_ADDRESS as string,
  secretKey: process.env.SESSION_KEY as string,
  gasless: true,
};

const wallet = new SmartWallet(config);
await wallet.connect({
  personalWallet,
});

await wallet.addAdmin(adminAddress);

Given the stack trace my guess is that the caller (from) is not set correctly (should be personal wallet address, not smart wallet address)

As a workaround, I got this working:
// await wallet.addAdmin(adminAddress);

const sdk = new ThirdwebSDK(Mumbai, {
  secretKey: process.env.SECRET_KEY,
})

sdk.updateSignerOrProvider(await personalWallet.getSigner())
const walletContract = await wallet.getAccountContract();
const contract = await sdk.getContract(walletAddress, walletContract.abi)

const tx = await contract.call('setAdmin', [sessionAddress, true]);
console.log("tx: ", tx);

@alko89 thanks for reporting this, we're doing some changes to allow the smart wallet itself to add other admins gaslessly via UserOp. Should have an update for it this week.
For now, the way to add admins is from the admin EOA itself as you mentioned, you can use this API for it:
await smartWallet.deployIfNeeded();
const walletContract = await wallet.getAccountContract();
await walletContract.account.grantAdminPermissions({{new_admin_address}});

once we ship the updated contract, you'll be able to simply do:
await smartWallet.addAdmin({{new_admin_address}}); // not shipped just yet

Will update here once its shipped


Dark deployments (night)

Deployment integration happens any time, but deployments happen during off hours, like 4 AM.
Initially intended for demo environment.

The typical deployment of a change should be zero outage, as Openshift spins up new nodes with the new version, then after they are healthy brings down the old ones. Unless with the single node database, if it is updated that would cause a brief outage (as I assume it is configured to not have more than 1 node). So probably higher priority to make sure the database isn't touched unless it has an actual change, after which point this particular improvement is likely not necessary.

https://github.com/bcgov/greenfield-template/issues/485

Zero downtime deployments are now in please, leaving the database alone.  Replacing the database, which can be done with overwrite: true or by deleting it, still causes an outage.
See https://github.com/bcgov/nr-fom/pull/306


{ $item } невидимые символы

используем условно такие конструкции

Но при копирование Новачок мы видим

I think you should use English

Конечно в ишью :)

Check last paragraph
You will notice the extra characters \u2068 and \u2069 in the output. These are Unicode bidi isolation characters that help to ensure that the interpolated strings are handled correctly in the situation where the text direction of the substitution might not match the text direction of the localized text. These characters can be disabled if you are sure that is not possible for your app by passing use_isolating=False to the FluentBundle constructor.

Check last paragraph You will notice the extra characters \u2068 and \u2069 in the output. These are Unicode bidi isolation characters that help to ensure that the interpolated strings are handled correctly in the situation where the text direction of the substitution might not match the text direction of the localized text. These characters can be disabled if you are sure that is not possible for your app by passing use_isolating=False to the FluentBundle constructor.

It works, thank you!

Thx


Blurred background

This commit adds a blurred background behind the dropdown menus in the clickgui

Thanks for your commit, I will try this and if it works I will merge the pull request


feat: modified build sql procedure, added brackets for every column

Implement feature #2375

my fault, i did wrong solution: it is doesn't works with aliases
need to refactor


Split entity from record in codegen

Closes: #92

LGTM. I'd like to see something in the README to explain the difference between entities and records.

I will update the readme today in another PR (adding more topics that are missing too)


CI for Node

Nate

Bananas

Initializes with two players
Starts the game with a random player
Sets the current player to be whoever it is not


Allow to delete an object from index only having an identifier

Description
Currently MeiliSearch\Bundle\SearchService exports method for deleting an entity, but there is no way to delete it having an identifier only. The basic use case - delete hundreds of entities in batch, then dispatch a messenger message to remove them from index, but providing only integers, as you cannot load anymore entities that do not exist.
Basic example
public function removeById(ObjectManager $objectManager, $identifier); // not sure about typehint of $identifier

Other
nothing more.

Hello @norkunas, feel free to implement your need in this package :)
We should have test for this function of course

Looking at how the final ID is generated to be stored to meilisearch, I'm not sure how this could work with composite identifiers..
For a basic use case when no composite is used, we could allow to just pass int/string ID and then in the method retrieve the identifier field of the doctrine entity and convert to the meilisearch format and that would work.
But if composite would be used than we'd need to manually provide the values mapping to which fields they belong and also in the same order that is retrieved to convert the composite..
Maybe a basic use case would be enough for now until someone would show an interest?

Maybe a basic use case would be enough for now until someone would show an interest?

Yes, let's keep basic for a first implementation.


Installation af OIOUBL i en North America database

Jeg har installeret NA-version af Business Central til en kunde  med kontor i både DK og USA og vil gerne installere OIOUBL, men den kan ikke installeres da upgrade codeunit forventer at det er en dansk database.
Kan jeg få en version af OIOUBL.app der ikke indeholder codeunit 13623 "OIOUBL-MigrateToExtV2"

Dokumentoplysninger
⚠ Undlad at redigere denne sektion. Det er påkrævet til docs.microsoft.com ➟ GitHub-problemlinkning.

ID: ae54faea-be1d-6d67-8b53-014504925f04
Version Independent ID: 9a9d3538-a636-7c90-d53a-4a128470ed4a
Content: Oversigt over elektronisk OIOUBL-fakturering - Business Central
Content Source: business-central/LocalFunctionality/Denmark/oioubl-electronic-invoicing-overview.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Hej CorpitalFDP,
I'm posting my reply in English so that others can benefit from it as well. The OIOUBL extension was created specifically for the Danish market. The current implementation means that it cannot be applied to a Business Central tenant in North America due to the way that Business Central handles local functionality. If you want to request a change to the extension, then you can suggest that here: https://github.com/microsoft/alappextensions/

Hi Eva
What i your sugestion for a customer operating in several countrries and need localizations for more than one country. I have expected the benefit of moving localizations to apps was that we where able to pick the needed functionality to fit our customers needs.

Hej igen,
Currently, companies operating in multiple countries are expected to sign up for Business Central in each country. As for the strategy and architecture behind moving local functionality to extensions, I must refer to the ALappextensions repo in GitHub that I linked to above. You are also very much welcome to suggest a change as an idea here: https://experience.dynamics.com/ideas/categories/?forum=e288ef32-82ed-e611-8101-5065f38b21f1&forumName=Dynamics%20365%20Business%20Central
Closing the issue for now.


Use QueueFactory instead of specific Queue

Currently a specific queue object is required in the consumer. Thinking about passing a queue factory in the ctor, and accepting a string queue name in the consume method.

Hmm... could work.
If the main script wanted to loop over different queues by name though, it could just as easily grab 'em from the QueueFactory and pass them in as they are now, which gives us a tighter, cleaner API. We could always create a helper class for that in the future anyways. I feel like there'd be some extra behavior folks might want to add there anyways, such as priority or routing etc, which we could allow by replacing that helper class rather than the core consumer.

I think priority should rather be a concern of the backend. Most of them support it.
Actually I am thinking about closing this for a while as the original idea was that by creating a queue object we have to create a factory first, so skipping this step could be a simplification. But I realised that creating a queue object is as easy as a factory.
Also, if we are going to use the "native" consumer then this becomes invalid.

See #9

Became invalid


Progress UI broken in Safari

Bug report
Current Behavior
In Safari (desktop as well mobile on iOS) progress when animating on the left side (start point) loses rounded corners.
Video recorded at https://www.radix-ui.com/docs/primitives/components/progress
https://user-images.githubusercontent.com/1233407/181525575-1ad98743-845e-47d3-aafb-b79df06bdd2b.mp4
Expected behavior
In any browser, Progress component UI should behave the same

Thanks for raising @dominikbulaj , looks like a classic browser transform rendering bug. Setting translateZ(0) or similar on the wrapper will probably resolve it.


Update dependencies to fix install on M1 macs

Thank you for this fun software!
I ran into a number of issues trying to install on an M1 Mac, so here's a PR that addresses them.  I'm happy to upgrade dependencies further, but this is the minimum I found that works.
(1)
npm ERR! /Users/a.ruddick/Documents/github/lineboi3000/node_modules/electron-chromedriver/download-chromedriver.js:19
npm ERR!   if (err != null) throw err
npm ERR!                    ^
npm ERR!
npm ERR! Error: Failed to find Electron v7.0.0 for darwin-arm64 at https://github.com/electron/electron/releases/download/v7.0.0/chromedriver-v7.0.0-darwin-arm64.zip

Fix is to upgrade to electron and spectron
(2)
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install
npm ERR! 404 status code downloading tarball https://github.com/chearon/node-canvas-prebuilt/releases/download/v2.0.0-alpha.14/canvas-prebuilt-v2.0.0-alpha.14-node-v115-darwin-unknown-arm64.tar.gz
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>npm ERR! node-pre-gyp info using<EMAIL_ADDRESS>| darwin | arm64
npm ERR! node-pre-gyp WARN Using request for node-pre-gyp https download
npm ERR! node-pre-gyp info check checked for "/Users/a.ruddick/Documents/github/lineboi3000/node_modules/canvas-prebuilt/canvas/build/Release/canvas-prebuilt.node" (not found)

Fix is to upgrade canvas.  Also drop jest-canvas-snapshot-serializer which has not been updated in 5 years and requires a broken version of canvas
(3)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  opensslErrorStack: [ 'error:03000086:digital envelope routines::initialization error' ],
  library: 'digital envelope routines',
  reason: 'unsupported',
  code: 'ERR_OSSL_EVP_UNSUPPORTED'

This is caused by older versions of webpack using MD5 as a hash, which has been dropped by OpenSSL.  One fix is to force it to use a newer hash (which is what I've done in this PR).  Another would to be upgrade to webpack5, or switch to esbuild.

Superceded by https://github.com/lilkraftwerk/lineboi3000/pull/40


Fix console errors for project.

Amn pretty sure this error:  attribute d: Expected number, "M NaN,NaNL NaN,NaN".
is related to FloatingEdge


Dzongkha Resources

dzo - dz - Dzongkha - http://crubadan.org/languages/dz
Ref: https://github.com/tesseract-ocr/tesseract/issues/654#issuecomment-274269267

https://github.com/tesseract-ocr/tesseract/issues/654#issuecomment-274574951

@theraysmith commented 2 days ago
Update: after going back to the www to get fresh data, I believe that my corpus text is now good for:
chr
dzo
iku
snd
syr
tgk
tir
I have put a lot of time into cleaners/filters for languages that use 'virama' characters.
I am not convinced that they are perfect, but I will add the code to the github repo in due course, so experts/native speakers can offer suggestions/fixes to make them better.

Hello, wanted to request if it would it be possible to add a new font for Dzongkha. The ttf file can be downloaded from here https://www.dzongkha.gov.bt/en/tools


encoding not implemented gzip, deflate, br

Thanks for this lib however some content encoding not implemented gzip, deflate, br , will be much better to add them

Thanks for raising this suggestion @korolossamy. These are definitely features that I plan to implement in the future when I have time. You are always welcome to open a new Pull Request with the suggested changes 🙏 .


Command line tool installation wants 'code' alias removed, no such alias present.

VSCode Version: 0.10.10
OS Version: OSX 10.11.3

On attempting to install 'code' command line, I get the following:
'Please remove the 'code' alias from '/Users/kstevens/.bashrc' before continuing.'
'alias' returns the following:
alias acsdev='ssh -l kcs6 acsdev.acsu.buffalo.edu'
alias cmsdev='ssh -l kcs6 cms-dev.acsu.buffalo.edu'
alias cq_start='cd /Applications/day/5.6.1-custom-v2/crx-quickstart/bin/ && ./start && cd -'
alias gcam='git commit -am'
alias ls='ls -la'
alias rvm-restart='rvm_reload_flag=1 source '''/Users/kstevens/.rvm/scripts/rvm''''
alias sandbox='cd ~/code/src/ubcode/sandbox/kcs6'
alias simple_server='python -m SimpleHTTPServer 9000'
alias tree='tree'
alias ubcms='cd ~/code/src/ubcode/ubcms_local/'
alias ubcode='cd ~/code/src/ubcode'
alias vlt='/Users/kstevens/bin/vault-cli-2.4.34/bin/vlt'
example_bashrc.txt
Steps to Reproduce:

Not sure, it might be machine specific.
I have included my .bashrc file. I have tried commenting out any line with 'code' in it, in case a poorly formed regex was to blame. No joy.

Code is talking about line 30 in your .bash_rc file. If you remove it and install the new CLI via the command you can keep vsc by setting alias vsc=code.

Ah, then the true bug is that commenting the line oiut is insufficient, which is what I tried before filing the issue.

Yeah all great points. I can add those two safeguards:

check whether the line is commented out
provide the line number

Verification: When having the old alias, Code should advise to update to the new symlink. It should report in which file the alias is described, which line within the file and should ignore the line if it is commented out.

João,
Thanks for taking care of this one. I learned a bit about how things work under the covers as I had forked the repo and identified the methods that had to change. I wasn't able to come up with a good way to write a failing test for it, though.
Nice to see bugs picked off so quickly.

No worries, thanks for the effort!

There are no longer docs on how to setup the old alias. Do you still have that somewhere or should I go hunting in vscode-docs history?

vsc () { VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $* ;}

code () { VSCODE_CWD="$PWD" open -n-b "com.microsoft.VSCode" --args $* ;} is the way it used to be on the VSCode setup page, I used vsc because I had another command aliased to code.


[CIT-539] Add a tutorial how to write a new sm-plugin

Signed-off-by: Rina Fujino<EMAIL_ADDRESS>Proposed changes
Doc update.
Types of changes
What types of changes does your code introduce to thin-edge.io?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[x] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[ ] I ran cargo fmt as mentioned in CODING_GUIDELINES
[ ] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

Codecov Report

Merging #448 (5b4b7bf) into main (d1e57dd) will increase coverage by 0.56%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #448      +/-   ##
==========================================
+ Coverage   62.45%   63.01%   +0.56%
==========================================
  Files         107      110       +3
  Lines        6749     6930     +181
==========================================
+ Hits         4215     4367     +152
- Misses       2534     2563      +29

Impacted Files
Coverage Δ

sm/plugin_sm/src/plugin_manager.rs
43.68% <0.00%> (-6.92%)
:arrow_down:

sm/plugin_sm/src/plugin.rs
52.63% <0.00%> (-2.07%)
:arrow_down:

sm/tedge_agent/src/main.rs
0.00% <0.00%> (ø)

sm/tedge_agent/src/agent.rs
0.00% <0.00%> (ø)

sm/plugin_sm/src/logged_command.rs
96.05% <0.00%> (ø)

sm/plugin_sm/src/log_file.rs
75.00% <0.00%> (ø)

sm/tedge_agent/src/operation_logs.rs
94.79% <0.00%> (ø)

sm/json_sm/src/lib.rs
98.52% <0.00%> (+<0.01%)
:arrow_up:

sm/plugin_sm/tests/plugin.rs
98.93% <0.00%> (+0.09%)
:arrow_up:

sm/json_sm/src/messages.rs
85.77% <0.00%> (+1.86%)
:arrow_up:

Continue to review full report at Codecov.

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

As the plugin API spec is not public it may be a little bit confusing when you mention it in the doc, maybe we should make the spec public?

The specs have been made public as a reference guide. See https://github.com/thin-edge/thin-edge.io/blob/main/docs/src/references/plugin-api.md

The specs have been made public as a reference guide. See https://github.com/thin-edge/thin-edge.io/blob/main/docs/src/references/plugin-api.md

That's great, in this case how about a link to this doc somewhere in the guide for reference?

I will add a link to our docker plugin after #447 is merged.


Support Multi-Object Delete

Late last year AWS S3 announced Multi-Object Delete that allows to delete up to 1,000 objects with a single request.
This patch makes delete() method able to take one or more keys (up to 1,000) and fixes a trivial bug of authorization for sub-resource access.
I did want to write a documentation for it also, but I can’t find reStructuredText files.

I think this needs more thorough testing, please advise

I tested it on my private S3 bucket, but I didn’t leave the used test code.  Currently test codes create mock HTTP connections that emulate S3 buckets, but it seems to need also tests that don’t emulate anything but use real S3 buckets.

I agree it would be good to test against the real S3, and I used to do that for the longest time; the problem however is though that this requires we publicize a key pair and I'm certainly not going to do that.
For now these tests work well; applications themselves can test that the S3 connection works as it should.
Thanks for your contribution! You should probably be added some list of authors somewhere.

We don’t have to publicize your key pair.  Leaving a local test configuration file or using environment variables also can be considered.
Thank you!


Add minecraft-autoplug Template

This adds a template for the AutoPlug client, a client for Minecraft servers with additional features. It runs on top of the Minecraft server, hence the client will execute the Minecraft server Java instance. I've added some notes for things that should be changed to make it work, but when that's all done it will work perfectly.

Ohhhh I accidentally edited the purpur files. I will restore them.

Can you please order the properties of the files the same?
Please refer to https://github.com/PufferPanel/templates/blob/v2.6/minecraft-vanilla/minecraft-vanilla.json for a desired ordering.

Can you please order the properties of the files the same?
Please refer to https://github.com/PufferPanel/templates/blob/v2.6/minecraft-vanilla/minecraft-vanilla.json for a desired ordering.

The build and version flags don't apply to this, as the client does only offer the latest build at a time and it isn't the server software itself, just the client that can run it.

Oh sorry, I didn't understand it correctly. I'll look into it this
afternoon. Shall I do the same for the Docker version of the template?
Op do 19 okt. 2023 19:47 schreef Joshua Taylor @.***>:

Can you please order the properties of the files the same?
Please refer to
https://github.com/PufferPanel/templates/blob/v2.6/minecraft-vanilla/minecraft-vanilla.json
for a desired ordering.
The build and version flags don't apply to this, as the client does only
offer the latest build at a time and it isn't the server software itself,
just the client that can run it.
Order as in, the data section is first, then the install section, then the
run section, and so on. The specific variables are not what I meant.
—
Reply to this email directly, view it on GitHub
https://github.com/PufferPanel/templates/pull/241#issuecomment-1771448934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APYNRKW67WEZ67N4F6IXCX3YAFRUPAVCNFSM6AAAAAA6D3GZS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZRGQ2DQOJTGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Can you please order the properties of the files the same?
Please refer to https://github.com/PufferPanel/templates/blob/v2.6/minecraft-vanilla/minecraft-vanilla.json for a desired ordering.

The build and version flags don't apply to this, as the client does only offer the latest build at a time and it isn't the server software itself, just the client that can run it.

Order as in, the data section is first, then the install section, then the run section, and so on. The specific variables are not what I meant.

Although, why does Purpur use this ordering instead?

@LordRalex Done! I fixed the ordering and it should be correct now.

@LordRalex I hope you'll be able to merge this soon.


[BUG] Impossible to generate a new certificat

Hi All,
I update nginx old project with the new : project nginx-proxy-automation
Actually, is impssible to generate a new certificat. I have an error :
[Fri May 21 07:38:22 UTC 2021] Please refer to https://curl.haxx.se/libcurl/c/libcurl-errors.html for error code: 23

[Fri May 21 07:38:22 UTC 2021] Could not get nonce, let's try again.

[Fri May 21 07:38:24 UTC 2021] Giving up sending to CA server after 20 retries.

[Fri May 21 07:38:24 UTC 2021] Register account Error:

grep: /etc/acme.sh/<EMAIL_ADDRESS>No such file or directory

[Fri May 21 07:38:24 UTC 2021] The account url is empty, please run '--update-account' first to update the account info first,

[Fri May 21 07:38:24 UTC 2021] Then try again.

Error: no ACME account was found or registered for<EMAIL_ADDRESS>and https://acme-v02.api.letsencrypt.org/directory, certificate creation aborted.

I have 4 sub-domains and is Ok. But for a new project (Wordpress or another) i have this error.
Exemple for a sub-domain : exemple.domain.com
If I test with the script nginx-proxy-automation/bin/ssl_test.sh I don't have a problem and my sub-domain is ok with a new certificate Let's Encrypt.
For the parameters with the domain manager (OVH) I did not need to make any modifications because I am using a subdomain which was already configured for an old project.
My docker-compose-yml and .env is ok.
# Host
DOMAINS=blabla.nbility.fr
VIRTUAL_HOST=blabla.nbility.fr
LETSENCRYPT_HOST=blabla.nbility.fr
<EMAIL_ADDRESS>#
# Network name
#
# Your container app must use a network conencted to your webproxy
# https://github.com/evertramos/docker-compose-letsencrypt-nginx-proxy-companion
#
NETWORK=proxy

This is a variable in my docker-compose.yml :
      - VIRTUAL_HOST= ${VIRTUAL_HOST}
      - LETSENCRYPT_HOST= ${LETSENCRYPT_HOST}
      - LETSENCRYPT_EMAIL= ${LETSENCRYPT_EMAIL}

For the tests, I changed the name of the subdomain and I have the same error.
Thank you all for your help and don't hesitate to ask me for more information.
I can in PM provide additional, more confidential information.
Have a nice day
Christophe
PS : si vous êtes français, ça sera plus facile pour moi :)

Did you follow this guide:
https://github.com/evertramos/nginx-proxy-automation/blob/master/docs/upgrade-guide.md
I can talk a little and understand french... but not really write it.

I deleted the old folder and performed a fresh install.
What I don't understand is that I relaunched containers (example with Wordpress) and I have no problem. On the other hand, if I want to launch new containers with a domain name that I used before, then it doesn't work.
How can I force the regeneration of a certificate for eg blabla.fr

Did you try to add VIRTUAL_PORT to the environment?
https://github.com/evertramos/nginx-proxy-automation#further-options


commit

committed my name.

Thanks for the PR.
Hope to see more contribution from you in this organization in future.
We will like have you onboard.
Feel free to contact me in case of any doubt.


InvalidSymbolKey error when using symbol keys in schema

Hello,
I'm currently using the activerecord_json_validator gem in a project and I've come across an issue when I use symbol keys in the JSON schema. Here's the code where the issue arises:
validates :data, json: {
  schema: {
    type: :object,
    properties: {
      time: { type: :number, minimum: 0 }
    },
    required: %i[time]
  }
}

When I run this, I get the following error:
JSONSchemer::InvalidSymbolKey: schemas must use string keys
This error seems to be raised from the JSONSchemer::Schema::Base#initialize method when the schema is a Hash, is not empty, and the first key in the schema is not a string. Here's the code block where this happens:
raise InvalidSymbolKey, 'schemas must use string keys' if schema.is_a?(Hash) && !schema.empty? && !schema.first.first.is_a?(String)

Proposed Solution:
As a simple fix for this issue, instead of raising an error when the schema contains symbol keys, the schema could be modified to convert all keys to strings. We can use Hash#deep_stringify_keys (from active_support) method on the schema.
This change would make the gem more flexible and user-friendly by eliminating the need for users to ensure that their schemas only use string keys. I believe this would be a beneficial change and would appreciate if it could be considered for implementation.
Thank you for your time and consideration.
Best,
Stani

Hi @stanig2106,
You’re right, json_schemer produces this error when symbols are used as keys for the schema.
I don’t think we should circumvent this limitation in ActiveRecord::JSONValidator though, we don’t want to add and maintain an additional logic layer between us and json_schemer when passing hashes as the schema.
What I would suggest is that you explicitly convert symbols to strings:
validates :data, json: {
  schema: {
    type: :object,
    properties: {
      time: { type: :number, minimum: 0 }
    },
    required: %i[time]
  }.deep_stringify_keys
}

Hope that helps!

This would be partially covered by upgrading to json_schemer 2.0: https://github.com/mirego/activerecord_json_validator/pull/78
Symbol keys are supported, but not symbol values (eg, type: 'object' works but not type: :object)


Registration and de-registration protocol

Hi,
on the registration and de-registration protocol schema, in the provisioning step, the companion app sends the DeviceKey to the companionAuth Service, but the deviceKey doesn't  appear next to the AuthKey. The deviceKey is stored on the device, isn't it ? So, why the service needs to get the deviceKey ?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cc468ad2-97d4-011a-7155-82db4d495224
Version Independent ID: 4f211ad7-9278-ebff-3eef-4b1604f0320c
Content: Windows Unlock with Windows Hello companion (IoT) devices - UWP app developer
Content Source: windows-apps-src/security/companion-device-unlock.md
Product: windows
GitHub Login: @msatranjr
Microsoft Alias: misatran

It looks like your feedback concerns the product itself, rather than the documentation for the product. Unfortunately, GitHub issues in this repo are only used for documentation issues.
The best way to leave product feedback is through the Feedback Hub app. If you return to the documentation page related to this issue and scroll to the bottom, there is a button to leave feedback about this product
For completeness' sake, here is a list of developer resources:

The Feedback Hub app is the right place to suggest or lobby for a change or feature.
Try our forums and StackOverflow for community assistance with development questions.
The Windows developer support site explains other support options.
The Visual Studio developer community is helpful and responsive. You can also suggest or lobby for a change or feature by clicking the report a problem or suggest a feature buttons.
For developer issues or suspected product bugs, visit Microsoft Support. A support engineer will determine whether the issue is a Microsoft product bug. If it is, the ticket will be free of charge.

If you receive assistance via any support resource and you believe that information would help us improve the docs, then please let us know or consider submitting a pull request.
Thanks,
Shawn


npm install of electron-to-chromium does not install the latest 1.4.17 version

npm view electron-to-chromium shows the latest version is 1.4.16  even though the latest version on https://www.npmjs.com/package/electron-to-chromium is 1.4.17
This is failing our npm install with:
npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'browserslist'
npm ERR! notarget

Hi, you're probably using a mirror of NPM that hasn't updated yet.
1.4.17 was released 16 hours ago and on NPM currently has 200K+ downloads so it's definitely available.

Ye, sorry about that. Nexus probably wasn't updated yet, it's fine now. Thank you


Macie - policyFindingsPublishingFrequency and publishSensitiveDataFindings ignored

Describe the bug
The following Macie configuration options do not get applied when set to non-default values:

policyFindingsPublishingFrequency
publishSensitiveDataFindings

To Reproduce
With this:
# security-config.yaml

centralSecurityServices:
[...]
  macie:
    enable: true
    excludeRegions: []
    policyFindingsPublishingFrequency: SIX_HOURS
    publishSensitiveDataFindings: true
[...]

I end up having this:

Expected behavior

Publish sensitive data findings to Security Hub should be checked
Update frequency for policy findings should be 6 hours

Please complete the following information about the solution:

[x] Version: v1.5.2
[x] Region: eu-west-1
[x] Was the solution modified from the version published on this repository? No
[x] If the answer to the previous question was yes, are the changes available on GitHub? N/A
[x] Have you checked your service quotas for the services this solution uses? N/A
[x] Were there any errors in the CloudWatch Logs? No

Additional information:

Macie-SecurityHub integration is enabled

Hi Sebastian! Thank you for reaching out and using the Landing Zone Accelerator on AWS (LZA) solution. I'm attempting to replicate the behavior that you described in my own environment.

Hi Sebastian! I was able to replicate this issue and filled out a bug report for this behavior. I will keep this issue open in the meantime if you have any other questions or concerns.

Hi Bo and thanks for picking that up.
Taking this opportunity I'd like to understand whether the progress of such bug fixes but also new features can somehow be tracked. Also, have you got any roadmap publicly available to see what's coming? As I'm trying to figure out how capable the LZA solution is one of the things I'd like to get to know is what the development pace is. V. 1.5.0 was released in October and since then there's been only two bug fix releases while the number of enhancement-like issues reported reached 76 and none of them is equally marked as in progress.
Thanks.


UI glitch in OTP screen

After the OTP is sent, there is a UI glitch in VerifyPhoneNumberScreen. Could you please guide me to solve the issue?
Using the example code.
environment:
  sdk: '>=3.1.5 <4.0.0'

firebase_phone_auth_handler: ^1.0.8

Simulator: Pixel 7 API 33
@rithik-dev

Adding screen recording for reference. Please help.
https://github.com/rithik-dev/firebase_phone_auth_handler/assets/8981430/975a6636-2546-4827-bd15-5eed57adbfb5

Hi @JaleelNazir , I just tested the flow on the example app in the repository, and it works as expected. Looks like you missed something while integrating, try referring to the example app here once.
https://github.com/rithik-dev/firebase_phone_auth_handler/tree/master/example

I got the solution. There is an issue with the theme. The problem has been reported earlier in the Flutter repository.
GitHub Issues:

https://github.com/flutter/flutter/issues/70907
https://github.com/flutter/flutter/issues/28882

Solution: https://stackoverflow.com/a/72734482/3177007


WIP char escaping

Requirements

[ ] Entry in CHANGELOG.md was created
[ ] Link to documentation on https://yaml.org/ is provided in the PR description
[ ] Functionality is covered by newly created tests

reminder (from the docs):

Note that escape sequences are only interpreted in double-quoted scalars. In all other scalar styles, the “\” character has no special meaning and non-printable characters are not available.


Failed to connect

Running in a docker, the Wyoming integration in Home Assistant is unable to connect using the IP and Port. It just says failed to connect.
Here is the docker setup:
docker run
-d
--name='OpenWakeWord'
--net='bridge'
-e TZ="America/New_York"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="Tower"
-e HOST_CONTAINERNAME="OpenWakeWord"
-l net.unraid.docker.managed=dockerman
-p '10400:10300/tcp'
-v '/mnt/disks/ADATA_SX8200PNP_2J1420145469/appdata/openwakeword/custom':'/custom':'rw,slave'
-v '/mnt/disks/ADATA_SX8200PNP_2J1420145469/appdata/openwakeword/data':'/data':'rw,slave' 'rhasspy/wyoming-openwakeword'
--preload-model 'ok_nabu'
--custom-model-dir /custom

Looking at the other issue, I don't think it is starting properly. The log just says INFO:root:Ready.

You are mapping port 10400 to the container-port 10300, but openwakeword is listening on 10400. So i think you have to change the line:
-p '10400:10300/tcp'

to
-p '10400:10400/tcp'

I wondered why it was the same as Whisper when the docker first ran, because I didn't set it. I am just realizing it was because I used the whisper template and it pulled that internal port over lol. If it was in a text box I would have figured it out, but I had to delete the port assignment and make a new one.
Thanks, it is connected now. Was driving me nuts.


AIFF Support

Hello, I've added basic AIFF support, however I am not really sure, if it's production ready, but it worked fine when I tested it on multiple files. The error handling isn't also 100% proper, but this is more like working proof-of-concept. I've also attached a barebones AIFF file for testing and test for the crate.
Thank you.

I've made a lot of the changes you wanted, will look at doing the error handling properly tomorrow. Thanks for reviewing

Should be everything now, let me know if you need more changes. Thank you.

Did the changes suggested by @paolobarbolini , thank you.

I think you missed https://github.com/polyfloyd/rust-id3/pull/53#discussion_r548037747 @Marekkon5
Also since small reads are being done here, BufReader should make this more efficient

Hopefully that's all, fixed also the styling errors.


fix: Line fetch some value null

fix: Line fetch some value null

Looks the same as PR https://github.com/apache/incubator-hugegraph-toolchain/pull/321

close it since no update for long time


Model-image(Zoomed Image)-Full screen issue

Hi Team,
I have noted that when we click on the image it should open in the full screen but it's not happening in the legacy. Please look into the below snap and do the needful.
https://www.aldevron.com/our-services/gene-synthesis
https://main--aldevron--hlxsites.hlx.page/qe-test/zoomed-image

@Kummu007 - Please validate

@Vinaykumargujja  as discussed please look into this and do the needful

Hi @Kummu007  THis is the width we can accomodate in first zoom. Fr second level of zoom we are giving 150% by default to get the zoomed functionality. This 2 level zooms are by default.

@Kummu007 - Please validate again and connect with Vinay/Teshu if the issue still persists.

@Kummu007 , Fixed hid the zoom icon after the zoom.
Fixed padding, font-size, border-radius issues for close and zoom icons

This is working as expected.


Logo Proposal for Syntax

Hi, I'm a graphic designer and I like to collaborate with open source projects. Would you like me to design a Logo for Syntax?

Hey! We already have one - do you not like it?

If I like it, I would not change it, I sent you the proposal because I had not seen it. If you need a design for another project you can contact me and I will gladly collaborate.

thank you :)


Fixed #90 -- Added support for switches.

Added support for bootstrap5 switches.
https://getbootstrap.com/docs/5.1/forms/checks-radios/#switches
Here's how it looks on standard (vertical?) forms. Alignment seems ok to other inputs.

I need to investigate Horizontal forms.

I was expecting it to be more like this (with offsets). But that doesn't look quite right either!

Likely need to revisit https://github.com/django-crispy-forms/crispy-bootstrap5/pull/51 which was an attempt at fixing this.

This is how it looks now. It's a slightly wider input than for radio/checkboxes so I'm unsure about the alignment.


haskellPackages.password: use crypton, disable scrypt on non-x86

crypton is maintained, contrary to cryptonite
since the Hackage scrypt package uses SSE2, we can't build it on non-x86 platforms (non x86_64 even probably). The best option is to disable the Scrypt module. To prevent cabal from pulling in scrypt in spite of that, we need to patch build-depends to respect the flag.

Currently untested, waiting for cache to catch up.

Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Confirmed to work on aarch64-linux and x86_64-linux. Darwin is difficult to test at the moment because we don't have any sort of cache from a Hydra jobset.


Dependencies

Update devDependencies to the latest versions and add package-lock.json

Closing due to no response.


cannot find -lbracketPairing

[ 42% 21/38] : && /usr/local/bin/g++10 -O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc10 -fno-omit-frame-pointer  -Wl,-rpath=/usr/local/lib/gcc10 -isystem /usr/local/include -Wall -Wextra -Wshadow -Wconversion -Ofast -std=c++20 -Wno-shadow -O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc10 -fno-omit-frame-pointer  -Wl,-rpath=/usr/local/lib/gcc10 -isystem /usr/local/include -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc10 -L/usr/local/lib/gcc10 ParserGen/CMakeFiles/grammarstrip.dir/GrammarStrip.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/BNFContext.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/Parser.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/ParseFile.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/ParserGenBase.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/Scanner.cpp.o -o ParserGen/grammarstrip -L/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../bux/src   -L/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../CBrackets -Wl,-rpath,/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../bux/src:/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../CBrackets  -lbracketPairing  -lbux  -lfmt  -lstdc++ && :
FAILED: ParserGen/grammarstrip
: && /usr/local/bin/g++10 -O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc10 -fno-omit-frame-pointer  -Wl,-rpath=/usr/local/lib/gcc10 -isystem /usr/local/include -Wall -Wextra -Wshadow -Wconversion -Ofast -std=c++20 -Wno-shadow -O2 -pipe -fno-omit-frame-pointer  -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc10 -fno-omit-frame-pointer  -Wl,-rpath=/usr/local/lib/gcc10 -isystem /usr/local/include -fstack-protector-strong -Wl,-rpath=/usr/local/lib/gcc10 -L/usr/local/lib/gcc10 ParserGen/CMakeFiles/grammarstrip.dir/GrammarStrip.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/BNFContext.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/Parser.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/ParseFile.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/ParserGenBase.cpp.o ParserGen/CMakeFiles/grammarstrip.dir/Scanner.cpp.o -o ParserGen/grammarstrip -L/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../bux/src   -L/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../CBrackets -Wl,-rpath,/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../bux/src:/disk-samsung/freebsd-ports/devel/parsergen/work/parsergen-1.7.0-9-gbda59af/ParserGen/../../CBrackets  -lbracketPairing  -lbux  -lfmt  -lstdc++ && :
/usr/local/bin/ld: cannot find -lbracketPairing
/usr/local/bin/ld: cannot find -lbux
collect2: error: ld returned 1 exit status

CBrackets and bux projects are checked out but libraries there aren't built by cmake.

Sorry to keep you waiting, 1.7.1 is out. The shell commands for from github in any of Linux distros are also changed:
   git clone https://github.com/buck-yeh/parsergen.git
   cd parsergen
   cmake -D FETCH_DEPENDEES=1 -D DEPENDEE_ROOT=_deps .
   make -j
   PSGEN_DIR="/full/path/to/current/dir"

Please let me know if the change works for you.

cmake -D FETCH_DEPENDEES=1
For the purpose of package builder fetch during configure doesn't work, because configure and build aren't allowed to fetch anything for security reasons.
This is why there are git modules, that can be pre-fetched in a uniform way.
Custom fetch during configure just can't add any value that git modules can't.

Also local headers should be included with quotes, not angle brackets.

Which #include <...> do you refer to? I don't quite follow.

#include <bux/...>

I use FetchContent for my own purposes.
As author of all related projects, I put all cloned projects under the same parent folder. This way I can experiment changes between projects without even commit them. The working mode requires no ftech, and submodule too. Submodule forces the dependent repos reside under the root working folder as subfolders (of any depth though). It just dons't apply.

#include <bux/...>

To any project other than bux, parsergen or not, bux/*.h isn't local header.

For the purpose of package builder fetch during configure doesn't work, ...

That is not true, I do use FetchContent to pack ArchLinux AUR package

That is not true, I do use FetchContent to pack ArchLinux AUR package

Arch allows fetch, this is why it isn't a safe distro.
Virtually all major port systems don't allow fetch for security reasons: fetch doesn't guarantee that downloaded files will be exactly same every time.

Virtually all major port systems don't allow fetch for security reasons: fetch doesn't guarantee that downloaded files will be exactly same every time.

That is new to me! So even if I restrict myself to only fetch from github with specific tag, is it still not guaranteed to have the same code ?

That is new to me! So even if I restrict myself to only fetch from github with specific tag, is it still not guaranteed to have the same code ?

The Git protocol itself doesn't guarantee that it would always return the same code even if the same tag is requested. If the Git server is compromised hackers can return different code.
For this reason all required files are downloaded by the package builder before the build. Their cryptographic fingerprints are compared against the stored fingerprints, and then build runs without the network access.
It works this way for RPMs (like in Redhat/Fedora), in Ubuntu, in FreeBSD, in OpenBSD, etc. Arch Linux is an exception, this is what it isn't a secure packaging system.


Issues with how Summaries are written

Summaries should potentially be refactored here are a few issues I found

[Bug] Summary sections should be closed

Current output
/// <summary>
/// <summary>

Correct output
/// <summary>
/// </summary>

[Bug] Summaries should use triple backslashes for message

Current output
/// <summary>
//  Lorem Ipsum
/// <summary>

Correct output
/// <summary>
/// Lorem Ipsum
/// </summary>

[Enhancement] Multi-line Summaries are not blocked

Current output
/// <summary>
//  Lorem
Ipsum
/// <summary>

Correct output
/// <summary>
/// Lorem
/// Ipsum
/// </summary>

[Feature] Support for other tags in Summaries

Summaries support more tags.  These tags can be found in the following  documentation:
https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/xmldoc/recommended-tags

[Feature] Support for auto-wrap on character length.

A method found in the following block can provide an easy way to auto-wrap on character length
 var words = Regex.Replace(description, @"\s+", " ").Trim().Split(' ');
 var lines = new List<string>();
 var line = string.Empty;
 foreach (var word in words)
 {
     var workingLine = $"{line} {word}";
     if (workingLine.Length > characterWidth)
     {
         lines.Add(line.Trim());
         line = word;
     }
     else
     {
         line = workingLine;
     }
 }
 lines.Add(line.Trim());

 var section = string.Join($"{Indent}/// ", lines);

[Bug] Messages that are put into Summaries should be encoded for xml

Current output
/// <summary>
//  Lorem < Ipsum
/// <summary>

Correct output
/// <summary>
/// Lorem < Ipsum
/// </summary>

Escape
Target

&
Ampersand – &

'
Apostrophe – ‘

>
Greater-than sign – >

<
Less-than sign – <

"
Quotation mark – “

Hi, thx for suggestions.
If you are willing to amend those details and make a PR.


Code-Insiders Crashes and won't open

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.90.0-insider 0ead1f80c9e0d6ea0732c40faea3095c6f7f165a x64
OS Version: Ubuntu 24.04 LTS and Pop!_OS

Steps to Reproduce:

Install Code Insiders snap from Snapcraft
Launch Code Insiders by code-insiders on terminal or from Applications

Verbose Output:
code-insiders_verbose.txt
Screen recording:
Screencast from 2024-05-30 02-08-59.webm
The apps works soomothly when installed with a local .deb file. issue only exists when installed as snap

duplicate of #212494

duplicate of #212494

@Rexogamer any update on this issue. not resolved yet.

duplicate of #212494

@Rexogamer any update on this issue. not resolved yet.

Merging to https://github.com/microsoft/vscode/issues/212494


remove old options

See https://github.com/ollama/ollama/pull/1983

Should probably put a note in the next release and do a minor version bump for this.


[Web] Another exception was thrown: Instance of 'minified:fi'

I am on "1.24.0-10.2.pre"
This issue is specific to Web.
I have a simple scrollable list (child of scaffold). I get "Another exception was thrown: Instance of 'minified:fi'" exception when I double click on the browser window to expand to fullscreen and vice versa. When I gradually resize the browser I do NOT get this exception.
After using the app for few minutes ... resizing window takes 5+ seconds to refresh (i am using mackbook pro)

@hivesey can you provide a minimal reproducible code sample

@iapicca
Please provide a complete minimal reproducible code sample as requested above that shows the issue you are facing.
Thanks.

Sorry for the delay.
Scrollbar(
isAlwaysShown: true,
ListView.builder(
controller: _listScrollController,
shrinkWrap: true,
[children .... CheckboxListTile]
)
I get the exception when isAlwaysShown=true; NO exception when it is false
I switch back to "1.23.0-18.1.pre" because of this issue "https://github.com/flutter/flutter/issues/70948" in "1.24.0-10.2.pre"
So i see this exception in both "1.23.0-18.1.pre" and "1.24.0-10.2.pre"

Sorry for the delay.
Scrollbar(
isAlwaysShown: true,
ListView.builder(
controller: _listScrollController,
shrinkWrap: true,
[children .... CheckboxListTile]
)
I get the exception when isAlwaysShown=true; NO exception when it is false
I switch back to "1.23.0-18.1.pre" because of this issue "#70948" in "1.24.0-10.2.pre"
So i see this exception in both "1.23.0-18.1.pre" and "1.24.0-10.2.pre"
Note: I see this exception even with a simple list tile as well

@hivesey
We would need a complete minimal reproducible code sample that we can copy paste and run in IDE to see the issue you are facing.

When creating a simple example I figured the issue is because I have a 'Key' for my Scaffold based on media query. I have this key because my app is reactive for different screen sizes on the Web. I had to have this key without which widgets are being rebuilt appropriately.
Key('${MediaQuery.of(context).size.width} _ ${MediaQuery.of(context).size.height}')
Now I remove this and am wrapping it with Orientation Builder and it seems to work fine.
I am closing this issue for now.


https://github.com/devcontainers/spec/issues/31#issue-1242087243

          https://github.com/devcontainers/spec/issues/31#issue-1242087243

Originally posted by @Jordanwaslistening in https://github.com/devcontainers/spec/issues/31#issuecomment-1732398805

If you have a specific question or request, please let us know. Thanks!


Add backup example

@kmelve Feel free to make/request changes 😊
I pinned the virtual environment to ubuntu-18.04 to be on the safe side. Settingubuntu-latest triggers a warning that ubuntu-20.04 will soon be the new default (which might break workflow).

I have a monorepo with the structure:
studio/
frontend/

How can I use this backup routine with that? Do you know? I can't get the working-directory: to work.

I have a monorepo with the structure:
studio/
frontend/

How can I use this backup routine with that? Do you know? I can't get the working-directory: to work.


Adding embedded video option

Showing users how to embed video would also be helpful.

[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

HI @Sharkyshreds
It seems that similar changes have already been accepted earlier for this article you're editing, sorry about that. 😓
If you feel you have more to add, please feel free to open up a new PR.
Thanks again! 😊

If you have any questions, feel free to reach out through Gitter or by commenting below. 💬


Twitter Home Timeline Scraper

Your task
The goal of this challenge is to create a scraper for Twitter home "for you" timeline. We are interested in capturing relevant to us (according to Twitter recommendation engine) tweets / liked tweets / retweets.
Overview
The scraper will be deployed as a scheduled function that periodically checks timeline updates and sends new tweets to a MongoDB collection. Avoid Twitter's official API, but feel free to leverage their front-end GraphQL API or other reliable ways of obtaining the data. Please keep in mind that the submissions will be evaluated based on the combination of cost/efficiency, security, and stability.
Data Schema
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "type": "object",
  "properties": {
    "timestamp": {
      "type": "number",
      "description": "Unix epoch message timestamp"
    },
    "message": {
      "type": "object",
      "properties": {
        "text": { "type": "string" },
        "id": { "type": "string", "description": "Message ID" },
        "language": {
          "type": "string",
          "description": "Language of the Message"
        },
        "enrichment": {
          "$ref": "./enrichment_fields.json"
        },
        "media": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "type": { "type": "string", "enum": ["image", "audio", "video"] },
              "id": { "type": "string" },
              "title": { "type": "string" },
              "file_name": { "type": "string" },
              "url": {
                "type": "string",
                "description": "URL of the media file"
              }
            }
          }
        }
      },
      "required": ["text", "id"]
    },
    "user": {
      "type": "object",
      "properties": {
        "name": { "type": "string" },
        "id": { "type": "string" }
      },
      "description": "Sender of the Message"
    },
    "geo_coords": {
      "$ref": "https://geojson.org/schema/GeoJSON.json"
    },
    "source": {
      "type": "object",
      "properties": {
        "platform": {
          "type": "string",
          "description": "Telegram/Twitter/Reddit"
        },
        "channel": {
          "type": "object",
          "properties": {
            "name": {
              "type": "string",
              "description": "Name of the message source, such as a Telegram channel"
            },
            "id": { "type": "string" }
          }
        },
        "referenced_post": {
          "type": "object",
          "properties": {
            "url": {
              "type": "string",
              "description": "URL link of the referenced post"
            },
            "id": { "type": "string" }
          }
        },
        "source_specific_fields": {
          "type": "object",
          "additionalProperties": true,
          "description": "Extra source-specific fields"
        }
      },
      "required": ["platform"]
    }
  },
  "required": ["timestamp", "message", "user", "source"]
}

Submission
To participate, submit a pull request with your solution, along with a  .json with sample data, and request a review from @jalmonter. Expanding the pull request description with your methodology can help us better understand your reasoning and evaluate your submission faster.

Where I can find ./enrichment_fields.json?

@Hjklvfr it's an external schema which you don't need here

@jalmonter I committed the solution

@Lavriz Did I do everything right?  I would like to receive feedback

@Lavriz Did I do everything right?  I would like to receive feedback

@Hjklvfr
@jalmonter reviewed your PR. As soon as you reply to comments in case you're still interested, we will proceed further

🎉 @Hjklvfr submitted the winning pull request and claimed the bounty! Congrats!


Tuna cred request

Why are there two open pull requests? Should this be added to the existing PR #2830?

yes, Ian.. i accidentally created a new PR here instead of our own fork. i'll close it soon


Add an ERB Link exception

The initial state generated by superglue_rails is already properly escaped json and can be marked as html_safe. But erblint may call that line out and recommend calling to_json before html_safe. We could add something like the below, or add some documentation on how to use with ERB lint.
<script type="text/javascript">
  window.SUPERGLUE_INITIAL_PAGE_STATE=<%= initial_state.html_safe %>;<%# erblint:disable ErbSafety %>
</script>

I'd like to work on this!


iox-#1345 fix axivion warnings in logger files

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[x] All checks have passed (except task-list-completed)
[x] All touched (C/C++) source code files from iceoryx_hoofs are added to ./clang-tidy-diff-scans.txt
[x] Assign PR to reviewer

Notes for Reviewer

This PR fixes/suppresses most of the Axivion warnings for the refactored logger. There are a few which are not tackled and might need more discussion. It is a good start though and the remaining ones could be fixed in a follow up.
In order to fix one warning, the logging for pointer was refactored.
Checklist for the PR Reviewer

[x] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior
[ ] Public API changes are documented via doxygen
[x] Copyright owner are updated in the changed files
[ ] All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
[x] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Relates to #1345 and #1394

@mossmaurice @FerdinandSpitzschnueffler @elfenpiff friendly ping :)


Cannot hide GPA as it is hardcoded in the template

I have tried to customize the css style in order to hide the GPA score as it is not useful all the cases, but the GPA is not isolated in a dedicated tag.
So how could I change the HTML template ?
is there any projected HTML template change in the future versions ?

@geogeek11 check now, i canghe the template

Sorry may be I was not clear enough.
I mean to split this tag into 2 tags
[Degree] in [Field of Study] | Grade: [Your Grade]
Like in the line below:
[Degree] in [Field of Study]  | Grade: [Your Grade]
so I can hide .entry-grad if not needed

Sorry, I can't!