Completion introduces incorrect entries (version 922)

I upgraded my MacVim version 712 to 922. Now, when I use the keyword completion when writing prose, the list included incorrect entries. This is also the case with vim run from the Mac OS console. See below:
MacVim version 712

MacVim version 922

Running from Mac OS's console

These do not look like incorrect entries. They look like they are using unicode apostroph and used font does not have the necessary glyph. I would say that entries with ’ (U+2019, RIGHT SINGLE QUOTATION MARK, is said to be “preferred character to use for apostrophe”) are more correct then entries with ' (U+0027, APOSTROPHE) which is ASCII symbol with usual “used for everything, thus looks worse then more specialized symbols” problem. You may verify by completing to this entry and using ga on offending symbol: this action should show something like <’> 8217, Hex 2019, Octal 20031.

On Sunday, November 22, 2015 at 8:12:46 PM UTC-5, Nikolai Aleksandrovich Pavlov wrote:

These do not look like incorrect entries. They look like they are using unicode apostroph and used font does not have the necessary glyph. I would say that entries with ’ (U+2019, RIGHT SINGLE QUOTATION MARK, is said to be “preferred character to use for apostrophe”) are more correct then entries with ' (U+0027, APOSTROPHE) which is ASCII symbol with usual “used for everything, thus looks worse then more specialized symbols” problem. You may verify by completing to this entry and using ga on offending symbol: this action should show something like <’> 8217, Hex 2019, Octal 20031.

The OP's screenshot seems to show Vim 7.4.712 using the same font showing fewer entries.  E.g., the former has just "contacts" and "contact's", the latter has those two plus "contact-upside-down-question-mark-s".  So why are the later Vims showing more entries?
-Manny

Because somebody got sane and finally added entries with right symbols? I already saw that apostrophes I am writing make correct words be recognized as errors, not in Vim though (because I do not use spell checking in Vim, not because it does not do this).

ZyX-I, would you mind explaining your answer?

@AmaruCoder Ask specific questions.

AmaruCoder,
If I understand the situation correctly, ZyX is saying that two things are combining to create the behavior you observe.  One is that somewhere between Vim 7.4.712 and Vim 7.4.922 the English spell files acquired the non-ASCII apostrophes.  Two is that whatever font you're using is incapable of rendering these non-ASCII apostrophes.  This is why in the later Vim you're seeing on-screen garbage.
But this is conjecture, because you didn't do the diagnostic steps that ZyX proposed.  If it turns out to be the correct diagnosis, you will have to either live with the on-screen garbage or change your font.
-Manny

Thank you ZyX and Vim-ml. I understand what seems to be the issue. Nevertheless, when I choose the highlighted option:

And I follow ZyX's instructions above (use ga over the offending character), what I get is:

But I can enter the correct apostrophe with the font I am using, as the following image shows, and using ga gives the expected results:

Which leads me to believe that the problem is not my font's lack of support of extended characters.

It seems that this is caused by the update of runtime/spell/en.utf-8.spl with the commit ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7.
(Off topic: I found that this update is not included in vim-mirror.)
:spelldump also lists the strange entries.
cont
cont'd
contact
contact's
contactable
contacted
contacting
contacts
contact¿s/1
contagion
contagion's
contagions
contagion¿s/1
contagious
contagiously
contagiousness
contagiousness's/1345
contagiousnesses/1345
contagiousness¿s/1

(Off topic: I found that this update is not included in vim-mirror.)

Oh, thanks for noticing me. My script did not handle binary diffs. I pushed them manually and updated the script. Should work now

Ken Takata wrote:

It seems that this is caused by the update of runtime/spell/en.utf-8.spl =
with the commit ca63501fbcd1cf9c8aa9ff12c093c95b62a89ed7.
(Off topic: I found that this update is not included in vim-mirror.)
:spelldump also lists the strange entries.
cont
cont'd
contact
contact's
contactable
contacted
contacting
contacts
contact¿s/1
contagion
contagion's
contagions
contagion¿s/1
contagious
contagiously
contagiousness
contagiousness's/1345
contagiousnesses/1345
contagiousness¿s/1

It comes from this entry in the affix file:
SFX M Y 2
SFX M   0     's         .
SFX M   0     ¿s         .
I have no idea why that is here.  The upside-down question mark is
something completely different from the apostrophe.
I suspect this is the result of a failed encoding conversion.
The original download site no longer exists.  Other affix files I can
find don't have the second entry.
The openoffice site does not appear to have direct links, the downloads
are numbered.  Any better place to use?
--
hundred-and-one symptoms of being an internet addict:
157. You fum through a magazine, you first check to see if it has a web
address.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Shouldn't it be possible to use the dictionary from the release prior to commit  ca63501?

The original download site no longer exists.  Other affix files I can
find don't have the second entry.
The openoffice site does not appear to have direct links, the downloads
are numbered.  Any better place to use?

From LibreOffice's site, I found the English dictionaries are being maintained at https://github.com/marcoagpinto/aoo-mozilla-en-dict.

James McCoy wrote:

The original download site no longer exists.  Other affix files I can
find don't have the second entry.
The openoffice site does not appear to have direct links, the downloads
are numbered.  Any better place to use?

From LibreOffice's site, I found the English dictionaries are being
maintained at https://github.com/marcoagpinto/aoo-mozilla-en-dict.

Thanks.  In the affix file there I see:
ICONV 1
ICONV ’ '

I guess that means this quote should be handled like an apostrophe.
Vim doesn't support ICONV.
We could try these spell files, plus the Vim diffs and some work.
--
hundred-and-one symptoms of being an internet addict:
166. You have been on your computer soo long that you didn't realize
you had grandchildren.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///


fix(frontend): fixes hero btc token details

Motivation
If a user selects BTC in the Tokenlist and then clicks on "Token details" in the Hero component, nothing happens, but instead the token details modal should be opened.
Changes

adds btc token details modal

Tests
before:
https://github.com/user-attachments/assets/4b11ec42-060c-4027-b09a-104374845d1e
after:
https://github.com/user-attachments/assets/4fab159c-8da7-4ec0-8c00-ceede3a0ae33

@AntonioVentilii I just opened a PR with the renaming of the ETH token modal.
https://github.com/dfinity/oisy-wallet/pull/3981


Additional Check for Inspect Tool to detect Endline Whitespace

The commits are slightly off, however the product is a clean version of the Endline Whitespace Checker for the inspect tool.

LGTM! Thanks!

I apologize for these seemingly confusing actions, this will be the final time I edit the pull request until instructed otherwise, but otherwise the main repository will lose work.

otherwise the main repository will lose work.

How would the main repository lose work?

The first merge added the recent changes from the main repository into my branch, in order to sync my pull request with the main branch.  However, when the test initially failed, I realized I made a mistake trying to update my branch, so I reverted the changes in my own branch.  However, that made this pull request take away changes made to the main branch, since reverting the changes removed the main branch files.  So with change da67742, not only does it include my initial pull request, but it also deletes some of the changes that were introduced into the master branch since I first opened the request.  So in order to keep those changes, I had to revert the reversion.

Before merging this, I'd like to ask everybody one last time whether there are objections to enforcing a 'no trailing whitespace' policy on our code. This addition was mainly meant as a introductory project for Brandon. Nevertheless I think this policy has some merit and at the same time would not impose too much trouble onto developers as almost every editor can be configured to remove trailing whitespace on every save operation (see also editorconfig which is available for many editors as well).

Since there have not been any objections, I'll go ahead and merge this.


[$500] IOU - IOU reports with draft are not shown in LHN

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Launch New Expensify app.
Go to chat > + > Request money.
Create a money request.
Go to IOU report.
Create a draft.
Go to IOU details page.
Create a draft.
Return to LHN.

Expected Result:
Both IOU reports will be present in LHN as there is draft in each of them.
Actual Result:
Both IOU reports are not present in LHN despite having draft.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/673be90f-190e-46ca-8d36-6d2591c7b43b
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c72df490550ca13a
Upwork Job ID:<PHONE_NUMBER>597559296
Last Price Increase: 2023-12-07

Same as https://github.com/Expensify/App/issues/32648#issuecomment-1845372059: the IOU reports are now hidden from LHN

Closing as expected behaviour!


⚠ Processors has degraded performance

In 1ebfc31, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 57 ms

Resolved: Processors performance has improved in f440f65.


PR: fill() types and backfilling

Added a bit more verbosity for fill() types and explained backfilling in InfluxDB v0.9.

Thanks @pootzko. There are a few edits, but overall this looks good.

Hi, no problem, I was glad to help and I hope it's useful. Sorry for the typos and perhaps clumsy wording at times, English is not my native language. :)
So how does this work from here? Do I update this based on your suggestions and then create a new pull request or?
Cheers

@pootzko No problem. You should update the PR branch (in this case pootzko:master) with a new commit that addresses the feedback. Pushing that commit to the branch will automatically update the PR.

Done. :)
Btw is it ok to add a link the InfluxData.Net lib / NuGet that I'm working on? (basically a fork and upgrade of the previous InfluxDB.Net which seems to not be maintained any more).

@pootzko Thanks for updating the PR. Can you sign the CLA? Then we should be set to merge this PR.

certainly, done :)

I also added InfluxData.Net to clients / api.md, hope that's ok.

@rkuchan can you see if you can resolve the conflicts and merge this PR?

@pootzko, I moved it to a new branch just to fix the merge conflict, but it's all merged now: https://github.com/influxdb/docs.influxdata.com/pull/126. Thank you for your contribution!


Notice of breaking change in npm for packages published with provenance

Version
N/A
Details
We're working on a security improvement for packages published with provenance, @modern-js being one such package! 🙌
Context:
The change will start blocking publishes that come from a publishing source (e.g. repo in github) that is different from a previous version published with provenance. For example, if you move the repo for a package and you use provenance, before publishing the new version you will need to log in to your npm account and "reset" the publishing source for a given package, gated behind 2FA if configured. This will protect against long lived access token compromises taking over packages, as you will also need access to the npm account and/or the original source repo.
In an ideal world you don't even notice this until you need to transfer the package repository or want to stop publishing with provenance (which hopefully should be rare!).
Impact for @modern-js: Currently I can see several test versions published without provenance for @modern-js. Doing this would result in blocked publishes for the versions without provenance unless you manually reset the publishing source, which seems very annoying at your scale.
Couple questions:

Is this a welcome change to the security of packages published with provenance?
Could you change your publishing workflow for test packages to always include provenance? e.g. set this up using a actions trigger
Are these test packages published from local machines currently?

Reproduce link
N/A
Reproduce Steps
N/A

@feelepxyz
Some versions without provenance were published using internal CI machines because I needed to publish these test versions to verify some internal package logic. The pipelines running these tests are not well integrated with Github, and there is also an issue with the slow speed of Github Actions, which can affect verification efficiency.
For a Monorepo repository like Modern.js, which contains over 100 npm packages, it would be very slow to force all packages to be published using Github Actions. In testing and pre-release scenarios, I believe it should not be prohibited to publish locally.

Some versions without provenance were published using internal CI machines because I needed to publish these test versions to verify some internal package logic. The pipelines running these tests are not well integrated with Github, and there is also an issue with the slow speed of Github Actions, which can affect verification efficiency.

Thanks for the context here, this makes sense.

However, it would be even better if we could apply this policy specifically to stable releases, and allow local publish of pre-release versions.

This is good feedback. There's a few options here:

Enforce all versions have provenance and if this can't be done: disable provenance for all versions 😞
Introduce a toggle per package for enforcing that the publishing source matches for every version if publishing with provenance (if disabled: you could still publish with provenance but get no security benefit)
Possibly in addition to the toggle: Introduce a per package/org policy where you enforce which version ranges/tags/types must have matching publishing sources with provenance

Sounds like you need some version of this to get the security benefit here with your current setup
This is definitely the most amount of work and we'll need to think carefully about how we do this without introducing to many foot-guns, e.g. if the policy is too loose, an attacker could just publish a older version, not tagged as latest that would still be installed in lots of projects (e.g. say your package latest is v10, but most users are still requiring v9 - an attacker could then craft several backports that would probably get picked up by a lot of projects trying to find the latest v9 for example).
In your case, if you could write a policy that allowed something like ^0.0.0-pre-releases only but enforced all other versions you would get the security benefit.
Maybe there's a simple toggle to not enforce pre-releases as these are not picked up by the npm resolver by default unless you are currently on a pre-release.

Thanks for the feedback ❤  going to discuss this with the team.


Dependency on Microsoft's OWIN?

Hi,
We have a user at https://gitter.im/SuaveIO/suave who'd like to use this library, but it would seem this library is not OWIN compatible?
Would it be possible to make it OWIN compatible by removing the MSFT shims?
Regards,
Henrik

Hi Henrik, Superscribe is in the process of being reworked to remove the dependency on Microsoft.Owin which will remove the need for the Superscribe.OWIN project entirely... this is still a way away yet but the wheels are in motion. It will also be updated for .net Core 1.0.


#2 [FIX] Refactor IDs from Integer type to Long since they could be more than Integer.MAX_VALUE

Update requests method signature with long instead of int
Update unit tests

Hello @user4me, I agree with your idea, but the build is failing. A Javadoc should be updated in api.deezer.objects.AccessToken.
Old:
/**
 * Deezer access_token. Returned by {@link api.deezer.requests.AuthRequests#getAccessToken(int, String, String)}
 */

New:
/**
 * Deezer access_token. Returned by {@link api.deezer.requests.AuthRequests#getAccessToken(long, String, String)}
 */

Branch has been updated with the JavaDoc sorry for that !


spork/http/middleware asserts incorrectly when number is an argument

https://github.com/janet-lang/spork/blob/19787cc900bbbcc57189e3817599e6245745b331/spork/http.janet#L344
Shouldn't it be (assert msg (string... instead of (assert x (string... ? Since x is a number, this will always be true.
As expected, this following code fails at the wrong level
(def server (http/server (http/middleware 2000)))

Followed by
curl http://localhost:8000/

Returns
*   Trying [::1]:8000...
* connect to ::1 port 8000 failed: Connection refused
*   Trying <IP_ADDRESS>:8000...
* Connected to localhost (<IP_ADDRESS>) port 8000
> GET / HTTP/1.1
> Host: localhost:8000
> User-Agent: curl/8.4.0
> Accept: */*
>
* Empty reply from server
* Closing connection
curl: (52) Empty reply from server

Shouldn't it be (assert msg (string... instead of (assert x (string... ? Since x is a number, this will always be true.

The suggested change seems better than the existing code.

Thanks @craftybones


added the return of paths that clibs sees but are set in external var…

…iables
This fixes the install on osx. What was happening is that ctypes can see the DYLD_LIBRARY_LOAD path and then it wasn't being added onto the linker. This fixes that

This pull request was failing the test, because the Xspec extension could not be compiled.
I fixed the problem and implemented what you tried to achieve in the trunk (commit 2bf1c41) , so I'm closing this request.
@grburgess please check that it indeed works on mac.

@giacomov, this works

Great, thanks!


Masking a RUT number

Hi, could you help me to find a way to use this component or adapt it, to use it on the identification number in Chile (RUT). it has this format:
0.000.000-0 or 00.000.000-0 (the last character can be a number or the letter K

I just made a package ready to use (I'm Chilean btw)
https://github.com/LuisUrrutia/text-mask-rut
https://www.npmjs.com/package/text-mask-rut
This question should have been placed in Stackoverflow in first place, b/c the issues of Github aren't for help request, so please feel free to close this issue.


hugo: 0.136.5 -> 0.138.0

https://github.com/gohugoio/hugo/releases/tag/v0.137.0
https://github.com/gohugoio/hugo/releases/tag/v0.137.1
https://github.com/gohugoio/hugo/releases/tag/v0.138.0
I added withdeploy as to not break compatibility with previous versions, maybe putting it behind a flag would be a good idea.
For reference, from the v0.137.0 release notes:

Note that we have no longer build the deploy feature in the standard and extended archives. If you need that, download archives with withdeploy in the filename. See instalation for details. You can read https://github.com/gohugoio/hugo/issues/12994 for more on the motivation behind this, but for one, it shaves off about 40% of the binary size.

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] 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

[x] 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
[x] 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.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

hugo


feat(uat): added step unsubscribe in MqttControlSteps

Issue #, if available:
https://klika-tech.atlassian.net/browse/GGMQ-81
Unsubscribe from a topic
Description of changes:

Added unsubscribe step

Why is this change necessary:
to use in feature testing
How was this change tested:
On CI
Any additional information or context required to review the change:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

A invalid target branch in the PR. Please use uat-dev not main.


Error: Error   PA3007: APP is corrupted. Duplicate Control Unique Ids

When i pack the app source file i get the message
Error: Error   PA3007: MsApp is corrupted. Duplicate Control Unique Ids
How can i find the duplication controle ?

@gavrielsl Are you getting this just through packing and unpacking, or are you modifying the source files before packing?
If it is just through packing/unpacking, and you can send me your .msapp, I can find the duplicate control ID for you (tschneider AT microsoft DOT com). Otherwise, you'd need to search the controls for the unique ID manually, or build this project locally and run it against your source so you can set a breakpoint.
I'll look into updating our error messaging here to make it clearer in the future.


Used nuitka Version is old

The provided Nuitka Version is 1.2.7, but the current version is 1.3.8.
Best of all the current release still uses Nuitka 0.9.4.
The action should reflect this change and use the current version of nuitka.
(PR ready when needed) #11

Ah, I get it, we have failed to make releases of the action for a while, that is of course not good. I think we should do that soon.


chore(viteconfig): add me in availableRegions

Summary
Add me (Middle East) support in availableRegion,  it has announced GA release in Nov.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Warn about WorldEnvironment being ignored

WorldEnvironment is ignored in certain situations (esp. the clear color in 2D settings), and it's not clear to users why this happens; also see https://github.com/godotengine/godot/issues/6875.
This adds a warning explaining what happens.

Thanks!

Cherry picked into 3.0.3


[UI] Display a few rows of data in the tables

Is your feature request related to a problem? Please describe.
As part of the migration of the unitycatalog-ui repo to unitycatalog (main), referring the original UI issue:  Display a few rows of data in the tables #49

Describe the solution you would like

Additional context

FYI @MrPowers @vksx


Problem in supporting IE 11 in production mode

I am using react-chips in my popup, it is working good in Chrome, but not supporting in IE 11 in production mode. Please let me know whether react-chips supports IE 11.
Thanks,

Sorry for the delay. I'm not entirely sure, I haven't done much testing in IE. What are the specific issues you are running into?


HTTP 400: Message size too large

Since November 26th, our agent has been shutting down with the following error:

ERROR logdna_agent::_main: bad request, check configuration: 400 Bad Request

In another issue I found that I can expand the agent logs with RUST_LOG=info,mz_http::client=debug. Now we get:

DEBUG mz_http::client: failed request: 400 Bad Request {"status":"not ok","errors":["local:10::Broker: Message size too large"]}

How can I get the agent to run stably again?
P.S.: Can I make the agent restart automatically so that I do not lose logs? I have Restart=on-failure in the service file, but it does not seem to work (at least for this error).

@ThomasHappyHotel Can you try reducing the max request size through LOGDNA_INGEST_BUFFER_SIZE: https://github.com/logdna/logdna-agent-v2/tree/master?tab=readme-ov-file#options?
The default is 2MiB and the value is represented as bytes e.g. 2 * 1024 * 1024. Try reducing this to just 1 MiB or even further.
The error indicates an unintentional issue with our ingestion service so this should at least resolve the errors until we identify and fix the underlying issue.

@ThomasHappyHotel The agent has built in logic to loosely control the maximum size of a batch, but this doesn't work if all or most of the size is in a single line. Normally in a Kubernetes environment large lines are split up into partial lines which the agent consumes.
Can you share some information about your system and which version of the agent you are running? Do you also know if there's potentially any large lines in any of the files the agent is watching?

Additionally, can you share the agent's initial output, specifically the config output section.

@jakedipity It was hard to diagnose because the exit happened mostly in the middle of the night and old logfiles were already rotated. Luckily yesterday it happened also while I was working.
Your assumption that there is one big line in a logfile is true: five lines of one action are about 5 MiB big (I assume that most of the 5MiB are in one line).
Is it possible to increase the ingestion buffer size to a bigger value, i.e. 6 MiB, so that the agent will be able to ingest and not exit? Would there be any performance issues?

@ThomasHappyHotel Unfortunately there currently isn't a way to ingest such large chunks of data. Our ingestion service has some technical limits that limit each batch of lines to around 1 - 2 MiB. I'll open an internal ticket to see if we can better accommodate larger batch sizes in the future.
In the meantime the best option is trying to exclude the particularly long line with exclusion rules.
If it's coming from a particular file that doesn't require monitoring you can use file level exclusion rules: LOGDNA_EXCLUSION_RULES.
If the file includes logs you want then you can also use a line level exclusion rule: LOGDNA_LINE_EXCLUSION_REGEX. Off the top of my head you could do something like (?:^.{1048577}) to exclude anything with more than 1024 * 1024 characters. See here for more information about using regex with our agent.


add message for emacs-dir for test scripts

I'm not sure this is more widely needed, or the best approach, but this is to get around the issue that if one is using the test scripts, and has the tmp directory hanging around for awhile, the packages can get out of date.

A better "fix" would be to print a warning, that the packages are stored in the "/tmp/..." directory and that manual deletion is recommended after the test.

I like this idea.

I think this should mostly resolve your issue. The script is a bit intrusive in a sense that it just writes some files somewhere without telling the user about it.

Thanks, merged with slight adjustment to the message. ... is only used to indicate in progress messages in Emacs ... ;)


brew audit spurious error about “revision should not decrease”

In this bottle build job for bdw-gc (https://github.com/Homebrew/homebrew-core/runs/1595745519?check_suite_focus=true):
==> brew audit bdw-gc --online --git --skip-style
==> FAILED
bdw-gc:
  * revision should not decrease (from 1 to 0)
Error: 1 problem in 1 formula detected

There is no change in revision here, so audit should not complain. This is blocking an ARM bottle from being built.

The issue is coming from https://github.com/Homebrew/homebrew-core/pull/44735 where bdw-gc has both a revision bump commit and revision unbump commit. Since they both got merged into master, the audit is complaining that the revision decreased in https://github.com/Homebrew/homebrew-core/pull/44735/commits/c48ba172ad90255d1d5f508f8df56dfa81f1ebbf.

Well it's not actionable as an audit, is it? I don't see the point in preventing actual work being done now, because at some point in the past something happened.

This audit in particular has existed for a while and I've made a few changes lately to clean up false positives, but it keeps popping up over and over again.  I know @MikeMcQuaid did the last major refactoring to audit -- I'm not sure what his current stance on it is.
Without a significant rewrite/rescoping or disabling of this audit, a short-term solution might be to bump this back to revision 1.

As removing revisions should never happen, I also agree that bumping this to revision 1 (it should even be 2 right now ...) is what should have happened.

The bump and unbump happened within a single PR without a bottle for revision 1, so there hasn't been any negative impact. Since the current revision is 0, jumping to 2 will lead to
bdw-gc:
  * revisions should only increment by 1
Error: 1 problem in 1 formula detected

so it'd need to go to 1 first.

I agree this should be fixed so that we're not showing audit failures like this unless it's within the relevant PR.

I'm also fine with the revision being temporarily bumped to override this.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

This audit failure should never trigger unless the relevant formula revision/version/version_scheme has actually changed in the PR being tested.

Closing this as no-one has complained for a while.

This actually came up again while bottling for Monterey. It'll probably show up again for the next macOS version if not fixed before then.
I think the cause is different the times I saw, it though. AFAICT, brew is unable to parse formulae in the Git log with the old bottle blocks, so isn't able to use them as reference points for revision bumps. This causes the audit to mistakenly conclude that the revision decreased.

@carlocab I'm kinda loathe to keep this open indefinitely given that no-one touched it for a year. Thoughts?

I'm fine with keeping it closed. Just leaving notes here in case someone picks this up again at some point.


Mention aliases in the README

Thanks @colindean ! I'd like to add that for a root domain with HTTPS, one might want to implement a root redirect instead. Will also update that.

a root redirect

OOTB this module seems to have configured www.example.com, http or
https, to redirect to https://example.com. http://example.com also
redirects to that.

Added the root redirect to #10 , feel free to check the updated README 😉


Undertow request failed HttpServerExchange

ERROR [io.undertow.request] (XNIO-1 task-26) Undertow request failed HttpServerExchange{ GET /sessions/loggedin}
org.jruby.exceptions.RaiseException: (NoMethodError) undefined method `each' for "1":String
at WunderBoss::Rack::ResponseHandler.handle(/Users/deranged/Projects/jruby/lib/ruby/gems/shared/gems/torquebox-web-4.0.0.alpha1-java/lib/wunderboss_rack_response_handler.rb:35)
class RackTest
  def initialize(app)
    @app = app
  end
  def call(env)
    return [200, {"Content-Type" => "text/html"}, '1']
    @app.call(env)
  end
end

The Rack spec dictates that the body can not be a string. At a minimum, it should be an array containing the single string ['1']. TorqueBox 3 was a bit slack in following the Rack spec, but we've tightened things up in TorqueBox 4.
"The Body itself should not be an instance of String, as this will
break in Ruby 1.9."
https://github.com/rack/rack/blob/master/SPEC

oh fantastic!  I learned something new


Support change the Metashape raw image folder path

Just like the pix4d Object:
Pix4D(project_path=None, raw_img_folder=None)
In case the user changed the path of raw image folder and the project file
#95

A commit: f6b4e4f667f627ccb2a5aa025e203bac343993ac


Represent network edits

Ungap the Map, v2! Glue to the scheme sketcher, let people apply a proposed scheme, and see how it affects od2net output

CC @Robinlovelace and @stholder3.
The two use cases are editing existing roads in OSM to make them nicer, and adding totally new bridges/roads.
Doing something like "patching" an OSM file with GeoJSON input representing edits is not easy, I think. But if the only thing we're doing is feeding those edits to od2net, then it's a much easier problem potentially. The graph representation in od2net is easier to edit than OSM. So let's figure out what we want to do end-to-end, including input format of the edits, and then we could potentially start this work

More ideas from in-person conversation: the custom edge cost today could represent some edits. To do something like a 20mph zone, we could pass the edge geometry to that custom cost and then change LTS or costs accordingly


Ensure chunk sizes match when data sizes are different

This is achieved by checking the chunk sizes for each hdu in the list of hdus. Then work out the minimum chunk size for the hdus and use this.
Use the minimum to be on the conservative side.
See issue #3

Current coverage is 100% (diff: 100%)

No coverage report found for master at ddf841e.

Powered by Codecov. Last update ddf841e...fd91afb

Closes #3


Change color of button and/or label when they are selected

Adds selectedButtonColor and selectedLabelColor parameters.

Thanks @waltersanford 😸


[Bug]: Conflicting symlinks for namespace packages (e.g. PyQt6)

What happened?
After adding PyQt6 to the dependencies I see the following when trying to create a venv using this package:
  ├─▶ Conflicting symlinks found when attempting to create venv. More than one package provides the file at these paths
  ├─▶ django_pyqt6/site-packages/PyQt6/__init__.py
  ╰─▶ site-packages/PyQt6/__init__.py

Version
Development (host) and target OS/architectures: macOS aarch64 targeting macOS aarch64, also verified on linux amd64 targeting amd64
Output of bazel --version: 7.0.2
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file: HEAD (v0.7.3+)
Language(s) and/or frameworks involved: python namespace packages
How to reproduce
Check out https://github.com/dizzy57/rules_py/tree/venv-namespace
Run `bazel run //py/tests/virtual/django:manage`

Any other information?
It looks like one of the conflicting __init__.py files is provided by the python package, another is created by rules_python.
We encountered this error after upgrading to v0.7.3

Possibly duplicate of https://github.com/aspect-build/rules_py/issues/358

Thanks for the repro, this is a duplicate of #358, it's just more obvious with namespace packages. Closing this as the fix is likely the same.


Mapping to new PDK

Hi all,
I am trying to map BAG to tsmc65 nm but I failed to pass DRC and I still have some other issues.
Where you able to map the BAG to new PDK?
if yes kindly let me know and any help is really appreciated.
I followed instructions in https://bag-framework.readthedocs.io/_/downloads/en/stable/pdf/ but still something missing.

I have the same issue. Have you solved it now?


Support wildcards in exports

Feature request
Node supports wildcards in exports, e.g `"./features/.js": "./src/features/.js". It would be great if pkgroll could support this case as well.
Motivations
I want to export everything in one directory and don't want to have to list each one specifically.
Alternatives
You can write out the list manually, though it's annoying.
Additional context
https://nodejs.org/api/packages.html#subpath-patterns
Bugs are expected to be fixed by those affected by it

[X] I'm interested in working on this issue

Compensating engineering work financially will speed up resolution

[ ] I'm willing to offer financial support

Duplicate of https://github.com/privatenumber/pkgroll/issues/38


Line break within a word leads to 'non-searchability'

Hi everybody,
with regard to this old topic:
http://discuss.asciidoctor.org/Prevent-line-break-for-wrapped-text-td4514.html
I would like to point out a problem that I noticed during the rendering into a PDF document.
In my asciidoc document I import some csv tables which contain very long property names like the following:
webcontroller.outboundservice.cmis.repositoryId
The problem is that these properties are too long to be displayed within a row of the table column - the line is therefore wrapped at the end.
In the rendered PDF the table cell looks like this:
webcontroller.outboundservice.cm
is.repositoryId

If I now search for this property in the created pdf document, it will not be found, because the end of the line "cuts up" the text. So the PDF document interprets each line as a separate text.
My first thought was that it was the PDF format itself. But if I use the same table in Microsoft Word and save it as "accessible" pdf, I can find the property as "whole word".
Are there any workarounds to fix this problem in asciidoctor?
Thanks in advance.

This is a Prawn issue (the PDF generator), not an Asciidoctor PDF issue. Asciidoctor hands the text to Prawn and Prawn decides how to break it into lines. So whatever Prawn is doing that Microsoft Word is not doing has to be solved in Prawn.
You could try to create a simple PDF both ways and see if you can see what's different in the PDF source. But again, you'd need to report it to Prawn.

What you are likely referring to is https://support.office.com/en-us/article/Create-accessible-PDFs-064625E0-56EA-4E16-AD71-3AA33BB4B7ED[accessible PDFs]. Prawn doesn't support that feature, and therefore Asciidoctor PDF cannot either. When Prawn prints lines of text, it prints them as separate text objects.
Refer to upstream issue: https://github.com/prawnpdf/prawn/issues/1131.


Installing Edda for Amazon Linux Fails

The first error occurs when Ansible tries to start up mongod. Basically it fails.  Looking into the logs we see the error is:  "/usr/bin/mongod: symbol lookup error: /usr/bin/mongod: undefined symbol: _ZN7pcrecpp2RE4InitEPKcPKNS_10RE_OptionsE."
So looking that up said to use 10gen for the yum install. I modifed the tasks to include

name: Install Selected Yum Repository for MongoDB
copy: src=../files/mongodb.repo dest=/etc/yum.repos.d/mongodb.repo
when: ansible_distribution == 'Amazon'
tags: mongodb
name: Install MongoDB (yum version)
yum: pkg={{ item }} state=latest
with_items:

mongo-10gen
mongo-10gen-server
when: ansible_distribution == 'Amazon'
tags: mongodb

and the repository set to:
[mongodb]
name=MongoDB Repository
baseurl=http://downloads-distro.mongodb.org/repo/redhat/os/x86_64/
gpgcheck=0
enabled=1
Yay! After removing the old mongodb package, it ran a bit further. and stopped on this Task:
TASK: [edda | Download snapshot build of Edda from Cloudbees] *****************
failed: [ec2-54-242-11-34.compute-1.amazonaws.com] => {"dest": "/usr/local/tomcat/webapps/edda.war", "failed": true, "response": "HTTP Error 404: Not Found", "state": "absent", "status_code": 404, "url": "https://netflixoss.ci.cloudbees.com/job/edda-master/lastSuccessfulBuild/artifact/build/libs/edda-2.1-SNAPSHOT.war"}
msg: Request failed
I fixed the vars to show: https://netflixoss.ci.cloudbees.com/job/edda-master/lastSuccessfulBuild/artifact/build/libs/edda-2.2.0-SNAPSHOT.war as the new war file.
And that seems to allow it to go through to completion now.

Thanks Bob. Can you please make this a PR and I can merge it in?

Closing in favor of a PR


Improve native event handling in the toolbar area.

The issue:
Interacting (double-clicking or dragging) with areas in the Flutter app where the native macOS toolbar would typically be triggers native actions like maximizing or moving the window. While this is expected behavior on "empty" areas, it's undesirable when interacting with interactive widgets, such as buttons and draggable interfaces.
The solution:
I've developed a solution that involves creating and managing invisible native macOS UI elements (NSViews) in Swift. These elements intercept the native toolbar events, preventing them from being processed natively and instead passing them to the Flutter engine for handling within the app.
I've implemented this fix in my app project, and I'd like to share it upstream for further discussion (e.g.: better naming, code improvements, etc) and potential integration into the package.
Preview:
With debug layers

https://private-user-images.githubusercontent.com/2106934/381987939-67de09be-3ee1-4d1a-85c8-8d4a145b1257.mp4

Overlay legend:

Yellow: total usable toolbar area.
Green: "Passthrough" UI (absorbs native events and send them to Flutter)

Without debug overlays

https://private-user-images.githubusercontent.com/2106934/381988260-9058580d-dc5a-42dd-a173-1abdb9b62015.mp4

Key code points:

MacosToolbarPassthrough: A widget that watches its child and creates an invisible "passthrough" equivalent on the native side. Mouse events on this "passthrough" item do not trigger native events like expanding or dragging the window. Most layout changes in the child automatically trigger an update on the native equivalent, but you can also manually trigger an update using requestUpdate from the widget's state (MacosToolbarPassthroughState).
Most simple UI (e.g.: static size and fixed positions) may only need to use one or multiple MacosToolbarPassthrough. More complex use cases may also require the addition of a MacosToolbarPassthroughScope.
MacosToolbarPassthroughScope (optional): Flutter is optimized to avoid unnecessarily drawing UI elements, so detecting some changes in UI can be expensive or cumbersome. Even worse, sometimes the implementation may not be able to detect these changes at all (such as in some scrolling widgets or widgets that either move or change size in uncommon ways), resulting in flutter widgets being out of sync relative to their native counterpart.
Wrapping multiple MacosToolbarPassthroughunder a MacosToolbarPassthroughScope allows you to both:
1- Trigger a reevaluation on all scoped items when any of them internally requests a reevaluation.
2- Manually trigger these reevaluation events if needed (using notifyChangesOf).
When a scoped item detects a change that would normally trigger a reevaluation of their position and size, they instead notify their parent scope, which then notifies all their scoped items to reevaluate and update their positions and sizes.
I am using NSTitlebarAccessoryViewController instead of NSToolbar because the later has a padding that I could not remove and also was much more difficult to work with (e.g.: position items).

Code:
MainFlutterWindow.swift

import Cocoa
import FlutterMacOS
import window_manager

class MainFlutterWindow: NSWindow {
    private var hasToolbarDebugLayers: Bool = false
    private var toolbarPassthroughContainer: NSView?
    private var toolbarPassthroughViews: [String: PassthroughView] = [:]

  override func awakeFromNib() {
    let flutterViewController = FlutterViewController.init()
    let windowFrame = self.frame
    self.contentViewController = flutterViewController
    self.setFrame(windowFrame, display: true)

    RegisterGeneratedPlugins(registry: flutterViewController)

    setupToolbarPassthroughViewPlugin(flutterViewController: flutterViewController)

    super.awakeFromNib()
  }

    func setupToolbarPassthroughViewPlugin(flutterViewController: FlutterViewController) {

    let pluginChannel = FlutterMethodChannel(
          name: "[PLUGIN_NAMESPACE]/toolbar_passthrough",
          binaryMessenger: flutterViewController.engine.binaryMessenger)
        pluginChannel.setMethodCallHandler { (call, result) in
            switch call.method {
                case "updateView":
                  if let args = call.arguments as? [String: Any],
                     let id = args["id"] as? String,
                     let x = args["x"] as? CGFloat,
                     let y = args["y"] as? CGFloat,
                     let width = args["width"] as? CGFloat,
                     let height = args["height"] as? CGFloat {
                      self.updateToolbarPassthroughView(id: id, x: x, y: y, width: width, height: height, flutterViewController: flutterViewController)
                    result(nil)
                  } else {
                    result(FlutterError(code: "INVALID_ARGUMENTS", message: "Invalid arguments for updateToolbarPassthroughView", details: nil))
                  }
                case "removeView":
                  if let args = call.arguments as? [String: Any],
                     let id = args["id"] as? String {
                    self.removeToolbarPassthroughView(id: id)
                    result(nil)
                  } else {
                    result(FlutterError(code: "INVALID_ARGUMENTS", message: "Invalid arguments for removeToolbarPassthroughView", details: nil))
                  }
                case "initialize":
                    // Clean up necessary for flutter hot restart
                   self.toolbarPassthroughViews.removeAll()
                   self.toolbarPassthroughContainer = nil

                    #if DEBUG
                      let args = call.arguments as? [String: Any]
                      let showDebugLayers = args?["showDebugLayers"] as? Bool
                      self.hasToolbarDebugLayers = showDebugLayers ?? false
                    #endif

                    // Get the count of accessory view controllers
                    let accessoryCount = self.titlebarAccessoryViewControllers.count

                    // Iterate through the indices in reverse order to avoid index shifting
                    for index in stride(from: accessoryCount - 1, through: 0, by: -1) {
                        self.removeTitlebarAccessoryViewController(at: index)
                    }
                  result(nil)
                default:
                  result(FlutterMethodNotImplemented)
                }
        }

    }

    func updateToolbarPassthroughView(id: String, x: CGFloat, y: CGFloat, width: CGFloat, height: CGFloat, flutterViewController: FlutterViewController) {
      DispatchQueue.main.async {
          let window = self

          if self.toolbarPassthroughContainer == nil {
              // Initialize the view if it is nil
              let accessoryViewController = NSTitlebarAccessoryViewController()
              accessoryViewController.layoutAttribute = .top

              self.toolbarPassthroughContainer = NSView()
              if (self.hasToolbarDebugLayers){
                  self.toolbarPassthroughContainer!.wantsLayer = true
                  self.toolbarPassthroughContainer!.layer?.backgroundColor = NSColor.yellow.withAlphaComponent(0.2).cgColor
              }
              self.toolbarPassthroughContainer!.translatesAutoresizingMaskIntoConstraints = false

              // Assign the custom view to the accessory view controller
              accessoryViewController.view = self.toolbarPassthroughContainer!

              // Add the accessory view controller to the window
              window.addTitlebarAccessoryViewController(accessoryViewController)
          }

          if let containerView = self.toolbarPassthroughContainer {
             let windowHeight = window.frame.height

             // Convert Flutter coordinates to macOS coordinates
             let macY = windowHeight - y - height

             let flutterToggleInvertedPosition = CGRect(x: x, y: macY, width: width, height: height)
             let frame = containerView.convert(flutterToggleInvertedPosition, from: nil)

           var view: PassthroughView
           if let existingView = self.toolbarPassthroughViews[id] {
             view = existingView
             view.frame = frame
           } else {
               view = PassthroughView(frame: frame, flutterViewController:flutterViewController)
             if (self.hasToolbarDebugLayers){
                 view.wantsLayer = true
                 view.layer?.backgroundColor = NSColor.green.withAlphaComponent(0.2).cgColor

             }

             // Add the view to the containerView
             containerView.addSubview(view)
             self.toolbarPassthroughViews[id] = view
           }
         }
      }
    }

    func removeToolbarPassthroughView(id: String) {
      DispatchQueue.main.async {
        if let view = self.toolbarPassthroughViews[id] {
          view.removeFromSuperview()
          self.toolbarPassthroughViews.removeValue(forKey: id)
        }
      }
  }

  override public func order(_ place: NSWindow.OrderingMode, relativeTo otherWin: Int) {
      super.order(place, relativeTo: otherWin)
      hiddenWindowAtLaunch()
  }
}

class PassthroughView: NSView {
  var flutterViewController: FlutterViewController?

    required init(frame: CGRect, flutterViewController: FlutterViewController) {
        super.init(frame: frame)
        self.flutterViewController = flutterViewController
    }

    required init?(coder decoder: NSCoder) {
       fatalError("init(coder:) has not been implemented")
     }

  override func mouseDown(with event: NSEvent) {
    flutterViewController!.mouseDown(with: event)
  }

  override func mouseUp(with event: NSEvent) {
    flutterViewController!.mouseUp(with: event)
  }

    override var mouseDownCanMoveWindow: Bool {
        return false
    }
}

macos_toolbar_passthrough.dart

/// A collection of widgets that intercept and handle native macOS toolbar
/// events (e.g.: double-click to maximize, dragging to move window) so they can
/// be processed within a Flutter app.
///
/// The issue: interacting (double-clicking or dragging) with the area within
/// a flutter app where the native macOS toolbar would typically be triggers
/// native actions like maximizing or moving the window. This is the expected
/// behavior on "empty" areas, but undesirable when interacting with an input,
/// such as a button.
///
/// This solution involves creating and managing invisible native macOS UI
/// elements (Mainly NSViews) in Swift that intercept these events, preventing
/// them from being processed natively and instead passing them to the Flutter
/// engine for further handling.
library;

import 'dart:async';
import 'dart:collection';

import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';
import 'package:flutter/services.dart';

const String kMacosToolbarPassthroughMethodChannel =
    '[PLUGIN_NAMESPACE]/toolbar_passthrough';

const _debounceDuration = Duration(milliseconds: 10);

/// An optional "scope" for toolbar items.
///
/// When a scoped item detects a change that would normally trigger a
/// reevaluation of their position and size, they instead notify their parent
/// scope, which then notifies all their scoped items to reevaluate and update
/// their positions and sizes.
///
/// Since Flutter is optimized to avoid unnecessarily drawing UI elements,
/// detecting some changes in UI can be expensive or cumbersome. Even worse,
/// sometimes the implementation may not be able to detect these changes at all
/// (such as in some scrolling widgets or widgets that either move or change
/// size in uncommon ways), resulting in flutter widgets being out of sync
/// relative to their native counterpart.
///
/// Wrapping multiple [MacosToolbarPassthrough] under a
/// [MacosToolbarPassthroughScope] allows you to both:
/// 1- Trigger a reevaluation on all scoped items when any of them internally
/// requests a reevaluation.
/// 2- Manually trigger these reevaluation events if needed (see:
/// [notifyChangesOf]).
class MacosToolbarPassthroughScope extends StatefulWidget {
  const MacosToolbarPassthroughScope({super.key, required this.child});

  final Widget child;

  static void Function() notifyChangesOf(BuildContext context) {
    final result = maybeNotifyChangesOf(context);
    assert(result != null, 'No MacosToolbarPassthroughScope found in context');
    return result!;
  }

  static void Function()? maybeNotifyChangesOf(BuildContext context) {
    return _DescendantRegistry.maybeOf(context)?.notifyChanges;
  }

  @override
  State<MacosToolbarPassthroughScope> createState() =>
      _MacosToolbarPassthroughScopeState();
}

class _MacosToolbarPassthroughScopeState
    extends State<MacosToolbarPassthroughScope> {
  late final _DescendantRegistry _registry;

  @override
  void initState() {
    super.initState();
    _registry = _DescendantRegistry(_onReevaluationRequested);
  }

  @override
  void dispose() {
    _registry.dispose();
    super.dispose();
  }

  void _onReevaluationRequested() {
    for (final descendant in _registry.all.values) {
      descendant.requestUpdate();
    }
  }

  @override
  Widget build(BuildContext context) {
    return _InheritedDescendantRegistry(
      registry: _registry,
      child: widget.child,
    );
  }
}

class _DescendantRegistry {
  _DescendantRegistry(void Function() onReevaluationRequested)
      : _onReevaluationRequested = onReevaluationRequested;

  final void Function() _onReevaluationRequested;
  Timer? _debounceTimer;

  final Map<String, MacosToolbarPassthroughState> _descendantsById = {};

  void register(final MacosToolbarPassthroughState descendant) {
    _descendantsById.putIfAbsent(descendant._key.toString(), () => descendant);
  }

  void unregister(final String descendantKey) {
    _descendantsById.remove(descendantKey);
  }

  UnmodifiableMapView<String, MacosToolbarPassthroughState> get all =>
      UnmodifiableMapView(_descendantsById);

  void notifyChanges() {
    // Debounce change notifications
    _debounceTimer?.cancel();
    _debounceTimer = Timer(
      _debounceDuration,
      _onReevaluationRequested,
    );
  }

  void dispose() {
    _debounceTimer?.cancel();
  }

  static _DescendantRegistry? maybeOf(BuildContext context) {
    return context
        .dependOnInheritedWidgetOfExactType<_InheritedDescendantRegistry>()
        ?.registry;
  }
}

class _InheritedDescendantRegistry extends InheritedWidget {
  const _InheritedDescendantRegistry({
    required super.child,
    required this.registry,
  });

  final _DescendantRegistry registry;

  @override
  bool updateShouldNotify(covariant InheritedWidget oldWidget) => false;
}

/// A widget that intercepts and handles native macOS toolbar events (e.g.:
/// double-click to maximize, dragging to move window), forwarding them so they
/// can be processed within Flutter only.
///
/// Most simple UI (e.g.: static size and fixed positions) may only need to use
/// one or multiple [MacosToolbarPassthrough]. More complex use cases may also
/// require the addition of a [MacosToolbarPassthroughScope].
///
/// You can manually trigger the reevaluation of a [MacosToolbarPassthrough] by
/// calling [MacosToolbarPassthroughState.requestUpdate] method from its state,
/// which you may access by using a [GlobalKey] as its `key`.
class MacosToolbarPassthrough extends StatefulWidget {
  const MacosToolbarPassthrough({
    super.key,
    required this.child,
  });

  final Widget child;

  @override
  State<MacosToolbarPassthrough> createState() =>
      MacosToolbarPassthroughState();
}

class MacosToolbarPassthroughState extends State<MacosToolbarPassthrough>
    with WidgetsBindingObserver {
  /// A unique key identifying the content to be measured.
  final GlobalKey _key = GlobalKey();

  static const platform = MethodChannel(kMacosToolbarPassthroughMethodChannel);

  bool _isDisposed = false;
  _DescendantRegistry? _registry;
  Timer? _debounceTimer;
  ScrollableState? _scrollable;
  Offset? _lastPosition;
  Size? _lastSize;

  @override
  void initState() {
    super.initState();
    WidgetsBinding.instance.addObserver(this);
  }

  @override
  void didChangeDependencies() {
    super.didChangeDependencies();

    // Register this instance if scoped
    _registry = _DescendantRegistry.maybeOf(context);
    _registry?.register(this);
    _scrollable = Scrollable.maybeOf(context);
  }

  @override
  void dispose() {
    _sendRemoveMessage();
    _isDisposed = true;
    WidgetsBinding.instance.removeObserver(this);
    _registry?.unregister(_key.toString());
    _debounceTimer?.cancel();
    super.dispose();
  }

  @override
  void didChangeMetrics() => _onChange();

  void _onChange() {
    // If under a parent scope
    if (_registry case _DescendantRegistry registry) {
      // Notify scope of changes
      registry.notifyChanges();
    }
    // If standalone item
    else {
      // Debounce updates to native UI counterpart
      _debounceTimer?.cancel();
      _debounceTimer = Timer(
        _debounceDuration,
        () {
          requestUpdate();
        },
      );
    }
  }

  void requestUpdate() {
    // Immediately update position and size
    _sendUpdateMessage();
    WidgetsBinding.instance.addPostFrameCallback((_) {
      // Wait for next frame to update position and size
      _sendUpdateMessage();
    });
  }

  void _sendUpdateMessage() async {
    if (_isDisposed ||
        !mounted ||
        !context.mounted ||
        _key.currentContext?.mounted != true) {
      return;
    }

    final RenderBox? renderBox =
        _key.currentContext?.findRenderObject() as RenderBox?;

    if (renderBox == null || !renderBox.attached) {
      return;
    }

    Offset? position = renderBox.localToGlobal(Offset.zero);
    Size? size = renderBox.size;

    // If item is child of a scrollable
    if (_scrollable?.position case ScrollPosition scrollPosition) {
      // With the viewport related to the scroll area
      if (RenderAbstractViewport.maybeOf(renderBox) case final viewport?) {
        final double viewportExtent;
        final double sizeExtent;
        switch (scrollPosition.axis) {
          case Axis.horizontal:
            viewportExtent = viewport.paintBounds.width;
            sizeExtent = size.width;
            break;

          case Axis.vertical:
            viewportExtent = viewport.paintBounds.height;
            sizeExtent = size.height;
            break;
        }

        final RevealedOffset viewportOffset = viewport
            .getOffsetToReveal(renderBox, 0.0, axis: scrollPosition.axis);

        // Get viewport deltas
        final double deltaStart = viewportOffset.offset - scrollPosition.pixels;
        final double deltaEnd = deltaStart + sizeExtent;

        // Check if item is within viewport
        final bool isWithinViewport =
            (deltaStart >= 0.0 && deltaStart < viewportExtent) ||
                (deltaEnd > 0.0 && deltaEnd < viewportExtent);

        // If this item is within the scrollable viewport
        if (isWithinViewport) {
          final double startClipped = deltaStart < 0.0 ? -deltaStart : 0.0;
          final double endClipped =
              deltaEnd > viewportExtent ? deltaEnd - viewportExtent : 0.0;

          // Clip overextending content
          switch (scrollPosition.axis) {
            case Axis.horizontal:
              // Clip content is overextending horizontally
              position = position.translate(startClipped, 0.0);
              size = Size(size.width - startClipped - endClipped, size.height);
              break;

            case Axis.vertical:
              // Clip content is overextending vertically
              position = position.translate(0.0, startClipped);
              size = Size(size.width, size.height - startClipped - endClipped);
              break;
          }
        }
        // If this item is not within the scrollable viewport
        else {
          position = null;
          size = null;
        }
      }
    }

    // Update native view if was removed or changed position or size
    if (_lastPosition != position || _lastSize != size) {
      // If item is not within the scrollable viewport
      if (position == null || size == null) {
        _sendRemoveMessage();
      }
      // Update item position and size
      else {
        await platform.invokeMethod('updateView', {
          'id': _key.toString(),
          'x': position.dx,
          'y': position.dy,
          'width': size.width,
          'height': size.height,
        });
      }
      _lastPosition = position;
      _lastSize = size;
    }
  }

  void _sendRemoveMessage() async {
    await platform.invokeMethod('removeView', {
      'id': _key.toString(),
    });
  }

  @override
  Widget build(BuildContext context) {
    return LayoutBuilder(
      builder: (context, constraints) {
        // Triggers evaluation on layout changed event
        _onChange();
        return SizedBox(
          key: _key,
          child: widget.child,
        );
      },
    );
  }
}

main.dart

// ...

  const config = macos.MacosWindowUtilsConfig(
    toolbarStyle: macos.NSWindowToolbarStyle.unified,
  );
  await config.apply();

  if (kIsMacOS) {
    const platform = MethodChannel(kMacosToolbarPassthroughMethodChannel);
    await platform.invokeMethod(
      'initialize',
      kDebugMode
          ? {
              'showDebugLayers': false,
            }
          : null,
    );
  }

// ...

This builds upon improvements made in https://github.com/macosui/macos_window_utils.dart/pull/43

This looks great. Do you think it’d be possible to implement this into macos_window_utils in such a way that users wouldn’t need to update their MainFlutterWindow.swift file?
Right now, macos_window_utils is usable without touching any Swift code (unless you’re targeting older macOS versions, see #44). It’d be great if your proposal could be implemented in such a way that this continues to be the case.

I think so. I am not so familiar with macos_window_utils plugin structure (I usually prototype this way and migrate to a plugin using pigeon), but I believe we can modify MacOSWindowUtilsPlugin.swift  and add handles for these methods there (merge both initialize methods and add the equivalent of updateView and removeView, but with better naming).
So, maybe we can edit MacOSWindowUtilsPlugin.swift, adding these changes into its handle method:

Add updatePassthroughView: Or a better name, with what I've called "updateView" in the code above.
Add removePassthroughView: Or a better name, with what I've called "removeView" in the code above.
Modify existing initialize:  Maybe add a parameter to enable "passthrough views" (perhaps in place of BlockingToolbar) and adding the code from what I've called "initialize" below the existing initialization code.

Then it is just a matter of organizing the new methods/classes/variables according to the project structure.

If I understand correctly, your PassthroughViews can be added to any toolbar, so maybe it would indeed be best to add methods for updating and removing them, alongside a parameter to enable their debug colors.

Yes, they can be added to any toolbar (as far as I tested).
I would also like to share the solutions to some problems I had after upgrading to Sequoia.
The problem is that right clicking on the toolbar area is no longer passed to flutter because it now opens a native menu (i.e.: it consumes the event and does not open my menu implementation on flutter side).
To fix this issue, add the following changes to the code above:
MainFlutterWindow.swift

On method channel setup:
//... Same as before

                case "initialize":
                    // Clean up necessary for flutter hot restart
                   self.toolbarPassthroughViews.removeAll()
                   self.toolbarPassthroughContainer = nil

+                    // Disable toolbar customizations and remove native context menu (right click)
+                    if let toolbar = self.toolbar {
+                        toolbar.allowsUserCustomization = false
+                        toolbar.allowsExtensionItems = false
+                        if #available(macOS 15.0, *) {
+                            toolbar.allowsDisplayModeCustomization = false
+                        }
+                    }

                    #if DEBUG
                      let args = call.arguments as? [String: Any]
                      let showDebugLayers = args?["showDebugLayers"] as? Bool
                      self.hasToolbarDebugLayers = showDebugLayers ?? false
                    #endif

                    // Get the count of accessory view controllers
                    let accessoryCount = self.titlebarAccessoryViewControllers.count

                    // Iterate through the indices in reverse order to avoid index shifting
                    for index in stride(from: accessoryCount - 1, through: 0, by: -1) {
                        self.removeTitlebarAccessoryViewController(at: index)
                    }
                  result(nil)

    //... Same as before

On PassthroughView:
class PassthroughView: NSView {
  var flutterViewController: FlutterViewController?

    required init(frame: CGRect, flutterViewController: FlutterViewController) {
        super.init(frame: frame)
        self.flutterViewController = flutterViewController
    }

    required init?(coder decoder: NSCoder) {
       fatalError("init(coder:) has not been implemented")
     }

    override func mouseDown(with event: NSEvent) {
      flutterViewController!.mouseDown(with: event)
    }

    override func mouseUp(with event: NSEvent) {
      flutterViewController!.mouseUp(with: event)
    }

    override var mouseDownCanMoveWindow: Bool {
        return false
    }

+    override func rightMouseUp(with event: NSEvent) {
+        flutterViewController!.rightMouseUp(with: event)
+    }
+
+    override func rightMouseDown(with event: NSEvent) {
+        flutterViewController!.rightMouseDown(with: event)
+    }

}

@Andre-lbc Excuse the delay, I was a little busy lately. You’re right, right clicking on a toolbar in macOS Sequoia seems to open a context menu that allows the user to choose whether toolbar items appear as icons or text. I’d argue that is an issue in and of itself and needs to be fixed as well, so thanks for the heads up.

I’ve run into somewhat of an issue while trying to implement this. Updating a passthrough view requires the full-size content view to be enabled (which kind of makes sense, since you need to enable it to be able to place Flutter widgets on the toolbar anyway). However, in order for the Flutter widgets to be visible, one needs to make the title bar transparent, which is done with self.mainFlutterWindow!.titlebarAppearsTransparent = true in macos_window_utils. Unfortunately, the passthrough views stop working when the title bar is transparent. Am I missing something?

Sorry for the delay, I'm using the default settings for MacosWindowUtilsConfig (added below for quick reference) and not changing them after initialization. Both enableFullSizeContentView and makeTitlebarTransparent are true and the passthrough views code is still working as intended in my project.
However, If I remember correctly, I had similar issues when I initiated the passthrough code before initializing macos_window_utils. Maybe changing these properties afterwards overrides something and remove the views?
const MacosWindowUtilsConfig({
    this.toolbarStyle = NSWindowToolbarStyle.unified,
    this.enableFullSizeContentView = true,
    this.makeTitlebarTransparent = true,
    this.hideTitle = true,
    this.removeMenubarInFullScreenMode = true,
    this.autoHideToolbarAndMenuBarInFullScreenMode = true,
  });


Issue with GZip compression?

Hi, we noticed an issue when upgrading from 0.23.4 to 0.23.6. Some clients started failing and blaming the gzip compression. One example would be
io.netty.handler.codec.compression.DecompressionException: CRC value mismatch.

i can confirm this on 0.22.7, 0.22.6 works fine

Thanks for reporting. Yep, that would be the similar https://github.com/http4s/http4s/pull/5368 that targeted 0.22.

If either of you has an opportunity, would you be able to make a replication? Obviously this is something that is slipping through both the fs2 and http4s test suites 😕

@vilu @ybasket thanks to @AL333Z's fantastic work on multiple fronts, if you use http4s 0.23.6 with fs2 3.2-14-a2508ec it should fix your issues. Please give it a try and report back, when you have a chance!
@Ravenow never fear, a backport to fs2 2.x is on the way in https://github.com/typelevel/fs2/pull/2701.

@Ravenow Now available for http4s 0.22 in fs2 2.5-2-0f99472.

Where does that leave us?  Leave this open until we have fs2 releases with the fix, but no code change on our end?

Yes, the default behavior was changed in fs2 so we don't need any code changes here. Up to you when to close the issue :)

Eh, no further action on our part, and people have a (snapshot) solution toward the bottom of this.  Closing.
Great job tracking this one down.

For those afraid of hashes, this fix is now available in fs2 3.2.3:
https://github.com/typelevel/fs2/releases/tag/v3.2.3

And now (finally!) in fs2 2.5.11 as well:
https://github.com/typelevel/fs2/releases/tag/v2.5.11


Post ADLDAP sync processing

Laravel Version: 5.8
Adldap2-Laravel Version: 6.0.7
PHP Version: 7.1.33
LDAP Type: ActiveDirectory

Description: Where/when/how to implement post ADLDAP sync process
The 'cn' in the AD that I am using has inconsistent formatting.
I am using 'cn' as one of the sync_attributes, but I need to do some post sync processing to clean it up.
What is the recommended way to implement post sync processing ?

Hi @schn-webmaster, I would recommend you use an Attribute Handler to perform this required attribute processing during synchronization rather than after:
https://adldap2.github.io/Adldap2-Laravel/#/auth/setup?id=attribute-handlers
Hope this helps!


fix get environment variable

Issue #:
https://github.com/bcgov/met-public/issues/1322
Description of changes:

fixed get env variable function

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1323 (1220a1f) into main (ac4d5c8) will increase coverage by 0.01%.
The diff coverage is 95.00%.

@@            Coverage Diff             @@
##             main    #1323      +/-   ##
==========================================
+ Coverage   72.33%   72.34%   +0.01%
==========================================
  Files         304      304
  Lines        8730     8734       +4
  Branches      626      628       +2
==========================================
+ Hits         6315     6319       +4
  Misses       2313     2313
  Partials      102      102

Flag
Coverage Δ

metweb
65.88% <95.00%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

met-web/src/config.ts
96.42% <95.00%> (-3.58%)
:arrow_down:

met-web/src/utils/index.ts
39.39% <0.00%> (+3.03%)
:arrow_up:


Documentation Quickstart is out of date for 1.21.0

When running riscof testlist  and riscof run suite and env is required.
I fixed it by first running riscof arch-test
then running above comands with
--suite=riscv-arch-test --env=riscv-arch-test/riscv-test-suite/env
Which seems to be running fine. but i receive the following errors..
`
......
INFO | [--root--]: Generating database for suite: /home/user/riscof/riscv-arch-test
WARNING | [--riscof.dbgen--]: /home/user/riscof/riscv-arch-test/riscv-test-env/v/entry.S:ISA not specified.
WARNING | [--riscof.dbgen--]: /home/user/riscof/riscv-arch-test/riscv-target/OpenHW/device/cv32e40p/handler.S:ISA not specified.
WARNING | [--riscof.dbgen--]: /home/user/riscof/riscv-arch-test/riscv-target/ibex/device/rv32imc/handler.S:ISA not specified.
WARNING | [--riscof.dbgen--]: /home/user/riscof/riscv-arch-test/riscv-target/ri5cy/device/rv32imc/handler.S:ISA not specified.
INFO | [--root--]: Database File Generated: /home/user/riscof/riscof_work/database.yaml
.....
`
And when running riscof run ....
`
WARNING | [--riscof.utils--]: In file included from /home/user/riscof/riscv-arch-test/riscv-test-suite/rv32i_m/C/src/cadd-01.S:19:
/home/user/riscof/riscv-arch-test/riscv-test-suite/env/arch_test.h:14: warning: "TEST_CASE_1" redefined
#define TEST_CASE_1
: note: this is the location of the previous definition
In file included from /home/user/riscof/riscv-arch-test/riscv-test-suite/rv32i_m/C/src/caddi-01.S:19:
/home/user/riscof/riscv-arch-test/riscv-test-suite/env/arch_test.h:14: warning: "TEST_CASE_1" redefined
#define TEST_CASE_1
: note: this is the location of the previous definition
In file included from /home/user/riscof/riscv-arch-test/riscv-test-suite/rv32i_m/C/src/caddi16sp-01.S:19:
/home/user/riscof/riscv-arch-test/riscv-test-suite/env/arch_test.h:14: warning: "TEST_CASE_1" redefined
#define TEST_CASE_1
etc.
`

the suite argument should point to the riscv-test-suite/rv32i_m or riscv-test-suite/rv64i_m directory as mentioned in the doc here. So the command sequence should be :
riscof arch-test
riscor run --suite=riscv-arch-test/riscv-test-suite/rv64i_m/ --env=riscv-arch-test/riscv-test-suite/env

By default riscof parses recursively in the path pointed by --suite. It looks for any/all .S files and checks if they match the test-format spec. If not they will be skipped from the database of tests. The warning you got from dbgen are precisely those - its skipping the target specific assembly files it encountered.
The other warning you get during the run command is because all tests in the riscv-arch-test are configured to enable the same TEST_CASE_1. This macro is also separately set at compile time by riscof, hence the warning on redefinition. Once the riscv-arch-test moves to riscof, that warning should also disappear. Removing it now, will cause the current riscv-arch-test framework to fail.


Update install instructions to include clobbering and module listing …

…[Closes #633]

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azurermps-6.9.0/install-azurerm-ps.md
:white_check_mark:Succeeded
View (azurermps-6.9.0)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Coin Hack Not Working

So i was doing Blooket but a lot of the hacks weren't working. The coin hack especially bc i wanted to get it but when i did the javascript ctrl v it didn't work. Fix Plz?

its outdated
https://github.com/Minesraft2/Blooket-Cheats

Ok
On Sat, Apr 1, 2023 at 7:22 AM berrybonk @.***> wrote:

its outdated
https://github.com/Minesraft2/Blooket-Cheats
—
Reply to this email directly, view it on GitHub
https://github.com/therealgliz/blooket-hacks/issues/546#issuecomment-1492984985,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6Z7XJIHYS25ZPEOU3QVHN3W7A22LANCNFSM6AAAAAAWMQ6LCU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Crash VertexBuffer when loading glb model

Describe the bug
when i load this glb model, crash happens. but is ok with babylon.js and threejs.
Logs
At least one buffer slot was never assigned to an attribute.

Some properties of the model are not resolved，such as uv or normal

Some properties of the model are not resolved，such as uv or normal

how can i check these properties?

This model has a total of 8 skinning weights per skeleton node (i.e. two sets of weights).  Filament supports only a single set of weights per node (this conforms to the glTF minspec)
In the past we emitted a friendly error message in gltfio, I'll take a look.

This model has a total of 8 skinning weights per skeleton node (i.e. two sets of weights). Filament supports only a single set of weights per node (this conforms to the glTF minspec)
In the past we emitted a friendly error message in gltfio, I'll take a look.

thanks, it works!


fix type (plt.pairplot()->sns.pairplot())

Correction of the description in the markdown cell.

Thanks for the correction!


Podman + Sysbox Integration

Sysbox should support Podman.
Podman is a RedHat's default container-management tool. Podman is specially useful in development phases as it can simply launch containers (through a docker-like cli interface), and it can easily convert container-definition files into K8 yaml recipes, which is quite handy to quickly test new PODs within a K8 cluster. In addition, Podman supports per-container user-namespace UID mappings, which gels wells with Sysbox.
Scott McCarthy and Giuseppe Scrivano from RedHat suggested that we consider:

Using Podman to deploy system containers with Sysbox.

Enabling system containers to run Podman inside.

Are there any soon-ish plans to implement this?


Mac OS X terminal doesn't show characters such as: ö, ä, å

VSCode Version: 1.17.2 (1.17.2)
OS Version: Mac OS Sierra 10.12.6

Steps to Reproduce:
I have had VSCode for a half year now on my computer and this is the first time I noticed that I can't actually type in scandinavian characters eg. ö, ä, å (and I can't remember was I able before). Also copy-pasting them into terminal doesn't show anything sensible so probably the terminal's encoding has gone wrong. Actually I noticed this only because my Python code that I was running with the integrated terminal was failing because it couldn't read non-ascii characters.
I have no idea how and why it happened and I doubt it's because of my installed extensions or my own settings (haven't changed really that many). It's frustrating because now I have to open up a "real" terminal window for the project to get the non-ascii characters to work. I know, such inconvenience!
Also I just have to confess that I'm really disappointed at the new logo. Made me sad when I saw it. Too enterprisey.
Teemu

This is what I see:

What's in your settings.json and can you paste in the output of echo $LANG?

User settings
{
    "editor.tabSize": 2,
    "window.zoomLevel": 0,
    "search.exclude": {
        "**/node_modules": true,
        "**/bower_components": false
    },
    "extensions.ignoreRecommendations": false,
    "editor.fontFamily": "'Noto Mono', 'Droid Sans Mono', 'Courier New', monospace, 'Droid Sans Fallback'"
}

echo $LANG
fi.UTF-8

Looks like that's the issue, currently we only support a shortlist of languages based on what we provide translations for. This is an easy fix though :+1:

Fixed in https://github.com/Microsoft/vscode/commit/23962f689313cc7c8ea3bd16ef94edf849d37ad1


Disable auto update on reenable/install

Disable update-engine.service on install/reenable
Decouple sync.service and xochitl.service as this means that either sync doesn't work, or xochitl starts when it is disabled

Untested,

I can't test the toltec-base install because it's failing to fetch open-remarkable-shutdown. Even when I try to install that from a ipk file, it still fails. Not sure what is happening.

Okay, I've reinstalled toltec and this seems to have resolved it. This seems to work for me now, but someone will need to test/confirm on a rM2.

I guess sync should be unmasked on uninstall?

Wouldn't hurt I guess. Best to restore the original state on uninstall.

@Eeems Did this resolve #553?

Most likely


Disable EasyMDE inside form

I'm submitting a...

[] Bug report
[x] Feature request

Version information
Browser type and version: latest Chrome
EasyMDE version: 2.5.1
Hi, thank you for the awesome plugin and big thanks for the regular updates.
I'm here to ask you about "disabling" feature. I've used your plugin in Formik (Reactjs) and in some cases, I should disable all fields in the form and EasyMDE too.
My feature request is: Can we have "disable" option or not.
Thank you.

Any updates on this request? im trying to set the editor to preview by default for users to view, but i cant find the option to programaticalle set the editor to preview

Likewise, thanks for the great editor. Likewise, I am looking for a way to either disable the editor (textarea) or set the editor automatic to preview. Is there any updates on this request?

I am not currently working on this part of the editor, but I doubt this would be very difficult to make.
From what I get from the comments is that you'd like the editor to be programatically put into preview mode, with the toolbar disabled or hidden. Is that correct?
Pull requests are always welcome!

This weekend I will take a closer look at the source code and perhaps try to implement it.

Any updates on this request? im trying to set the editor to preview by default for users to view, but i cant find the option to programaticalle set the editor to preview

Same thing, seems like this feature hasn't been done at the moment and there is no PR addressing that.

Is there any update on this?

Hi, Is there any update on this?

Hi ! The ability to have an option to disable the textarea would be great !


Brownfield Addition: AVD Alerts Solution

AVD Alerts Solution from JCoreMS/AVDAlerts repo with updated paths and readme links in support of this repo. Includes UI, BICEP, and ARM templates with additional docs in BICEP folder.

Working to correct errors and reference CARML.

@JCoreMS  thanks for your contribution checking the PR.

Removing for now to avoid excessive notifications while working on CARML integration.


Feat/Flippers-for-collection-activity

enabling query for flippers in colllection activity
@vikiival

cc @vikiival 👀

cc @vikiival 👀

@daiagi you are missing a db migration

@daiagi you are missing a db migration
tbh I am unsure how to generate the appropriate migration

Spin indexer
just upd

apply migrations
just reset

Create new
just update-db

@vikiival check again, please. i've added migartion


CPU resources: raw vs scaled

Kubernetes is careful to define CPU in terms of an abstract compute unit.  This leaves room for scaling that compute unit later.  Adding this scaling is VERY hard to do after the fact - assumptions grow very easily about number of threads that can run, concurrency guarantees, etc.

@thockin glass houses, this is taken exactly from here ;-)
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/resources.md#resource-quantities

Woops, wrong issue

This seems much easier for a system like Kubernetes which can abstract this unit and exercise complete control over it. How would we approach this in the spec? Still just define it as abstract units and leave it up to implementations?

Yeah, maybe you're right that this is something better left to a higher
level.  How bad is it if a user submits a 4.0 KCU kube job and finds rkt
says "2400 millicores" were assigned?  I think it's not so bad actually...
On Tue, May 5, 2015 at 10:32 AM, Jonathan Boulle<EMAIL_ADDRESS>wrote:

This seems much easier for a system like Kubernetes which can abstract
this unit and exercise complete control over it. How would we approach this
in the spec? Still just define it as abstract units and leave it up to
implementations?
—
Reply to this email directly or view it on GitHub
https://github.com/appc/spec/issues/359#issuecomment-99153016.


Ensure Elasticsearch/OpenSearch domains have encryption at-rest enabled

@wrynearson Should we move this into a sprint since MCP is requesting this be completed?

Yes good idea, I added it to sprint 3.

Update: encryption-at-rest has been abled on the OpenSearch instance in MCP. PR for adding encryption at rest to the CDK template open here: https://github.com/NASA-IMPACT/nasa-apt/pull/804

cc @ChrisPhillips1024


Add chainable example

Here is an example of a chaining return that you are talking about.
https://gist.github.com/fulldecent/6d64f86869e5d9d12436
Right now it only supports async. But it is possible to also work with sync returns.
It IS possible to keep this generic! And this implementation works everywhere.

To be clear, are you still accepting contributions to this project?? If so would a PR that fixes this be in scope to be merged?


Sample app does not compile

From the app folder:
make clean && rm -rf build && make
CC app.o
/Users/.../esp32_reusable_components/app/main/./app.c:2:31: fatal error: awesome_component.h: No such file or directory

Seems that you did not set env variable EXTRA_COMPONENT_DIRS properly

Worked too late at night... working all good and as you said probably an issue with EXTRA_COMPONENT_DIRS

Glad that your problems are solved. I hope this approach is what you need.

That´s perfect, thanks a lot for your help with that.


Add validation and defaults for eventing CR

Description
Add defaulting and validation rules to the Eventing CR
Changes proposed in this pull request:

Add validation rules
Add defaulting
Add tests for both by adding integration tests

Related issue(s)

#17

/retest

/retest

/retest

/retest


NAND-of-XORs as an equality check

A way to implement equality is this, which may be a little more LUT-friendly depending on where the cell P&R is going.
~(lhs ^ rhs).andR()

I might test this later to explore other options...

Seems like I need to look into carry chains for a meta-benefit.

I'll optimize the design once I see enough progress later on.


bundle-sfx broken

bundle-sfx works fine for you? It create the bundle but when I try to load in the browser say:
Uncaught Module ..  not present.

Current jspm version do not support bundle for TypeScript. Bundle available for traceur (master branch).


lib/coap: fill documentation holes

@otaviobp please review it
I was taking a look in our CoAP API and added missing docs.
Signed-off-by: Bruno Dilly<EMAIL_ADDRESS>

+2

+3

merged, thanks


Hall effect driver

The science team needs a driver for the hall effect, research this and create a driver for it. https://www.amazon.com/gp/product/B07QS6PN3B/ref=ox_sc_act_title_1?smid=A34K5WF5Z9R33P&psc=1

This is really just creating a demo to see how it works and if it even does work.

Hall effect sensor is finalized, this is the correct sensor.

@Coreyboy1820 I made a pull request for a working demo. Let me know what the next steps are. Should I make a wrapper class for abstraction purposes? Thanks
Here is the circuit schematic used.

Finished.


unordered database

I have a problem trying to populate the database because the order is reversed
i created the model Player_name, and Player_number
In mySQL database in order

Player_name
Player_number

but in adminpanel create, the order is reversed to

Player_number
Player_name

You can change the order in two ways:

Define editProperties, listProperties, showProperties, filterProperties, e. g.: editProperties: ['Player_name', 'Player_number'] - https://docs.adminjs.co/ResourceOptions.html#editProperties
Set position attribute for specific properties in resource options:
https://docs.adminjs.co/PropertyOptions.html#position

module.exports = {
  resource: Player,
  options: {
    properties: {
      Player_name: { position: 1 },
      Player_number: { position: 2 },
    }
  }
}

Let me know if you still have any troubles and I'll reopen.


All future stream data is discarded data if TCP write hangs

Reproduction steps:

Setup a network a network limiter (in my case Apple's Network LinkConditioner)
Open the example app & start a stream (I used Facebook as server, but others appears to produce the same result)
Increase the upload bandwidth (in my case, 9mb/s to 90mb/s -- but this number shouldn't matter)
Notice the stream 'continues', but all future frames are now discarded

Analysis
I looked into this issue a bit. The issue boils down to this being a forever blocked TCP write/flush. In Java's TCP Socket, writes block indefinitely and no timeout is possible (without using NIO selectors). In this case, it seems like the connection is kept intact, but during the bandwidth change, the remote will never process one of the writes. This leaves the stream in a state where it is forever blocked while also discarding future frames.
I'll admit, I'm not sure when this same behavior might occur in the real world, but the fact that it it can occur even in a simulated one feels a bit troubling to me. So I bring up the issue.

This is working as expected. To avoid this problem you can implement adaptative bitrate for this case (this feature increase or reduce bitrate according to if you discard frames) :
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/wiki/Adaptative-video-bitrate
If you have other idea to implement in this cases we can comment and implement it.

Sorry for my very late reply to this thread.
But using adaptive bitrate here doesn't solve the issue. The TCP connection will never expire regardless of the connection quality. I can confirm this behavior using the network limiter.

Sorry for my very late reply to this thread.
But using adaptive bitrate here doesn't solve the issue. The TCP connection will never expire regardless of the connection quality. I can confirm this behavior using the network limiter.

Actually I don't have any way to check it because my router can't make a network limiter and actually I haven't a macbook. I will mark if as bug and work on it in the future.

This should be reopened, there are multiple ways to reproduce this:

Run the sample app in the emulator, start streaming, turn off the wifi on your computer, the app does not detect that there is no network.
Run the app on a device connected to a wifi, pull the nework cable from your router, the app does not detect that there is no network.


[WGSL][NFC] Switch to new pass generation tablegen definitions.

This should be the remaining one for Codegen/.


Changing grid width

Hi,
Is there a way to change the width of the grid? In the screenshot below I'd like to shorten the X axis such that the gridlines stop at data point 5. I tried to do it using CSS but couldn't get it to work.
Thanks.

Perhaps not the best approach, but I worked out how to do it using JavaScript to manipulate the value of the line’s x1 and x2 attributes.


Please edit the package name.

.TestService, .MyService
Can you please correct the package name?

thank you!
Very cool!


Resynced OWNERS file for release-2.6

Signed-off-by: dislbenn<EMAIL_ADDRESS>

/hold

/unhold
/retest

/cc @subbarao-meduri @marcolan018

/lgtm


Implement baseline test suite

Feature Request
Description
We're lacking an integration test to validate base functionality of the various exporters + options.  At the moment these tests are being run manually, but that's... less than great.
Note that it probably doesn't make sense to take up this ticket until https://github.com/datastax/adelphi/pull/104 is done (and thus the integration test framework is at least stable).
Describe the solution you'd like
The script for these runs goes as follows.  The sequence below assumes two keyspaces ks1 and ks2... embedded comments indicate expected results

adelphi export-cql
[both keyspaces should be written to stdout with anonymization + metadata]
adelphi --no-anonymize export-cql
[both keyspaces should be written to stdout without anonymization + metadata]
adelphi --output-dir=export-cql export-cql
[should have two entries in export-cql, entries should use keyspace ID rather than keyspace name]
adelphi --output-dir=export-cql --no-anonymize export-cql
[should have two entries in export-cql, entries should use keyspace name]
adelphi export-cql --no-metadata
[both keyspaces should be written to stdout with anonymization, no metadata]
adelphi --no-anonymize export-cql --no-metadata
[both keyspaces should be written to stdout without anonymization, no metadata]
adelphi --output-dir=export-cql export-cql --no-metadata
[same as equivalent run above; when writing to output directories metadata is always included]
adelphi --output-dir=export-cql --no-anonymize export-cql --no-metadata
[same as equivalent run above; when writing to output directories metadata is always included]
adelphi --keyspaces=ks1,system_views export-cql
adelphi --keyspaces=ks1,system_views --no-anonymize export-cql
adelphi --keyspaces=ks1,system_views --output-dir=export-cql export-cql
adelphi --keyspaces=ks1,system_views --output-dir=export-cql --no-anonymize export-cql
[above four runs should be equivalent to earlier runs but only include ks1 + successfully prune system_views as a system table]
adelphi export-gemini
adelphi --no-anonymize export-gemini
adelphi --output-dir=export-gemini export-gemini
adelphi --output-dir=export-gemini --no-anonymize export-gemini
[the above four runs should fail since Gemini exporter only supports a single keyspace]
adelphi --keyspaces=ks1,system_views export-gemini
adelphi --keyspaces=ks1,system_views --no-anonymize export-gemini
adelphi --keyspaces=ks1,system_views --output-dir=export-gemini export-gemini
adelphi --keyspaces=ks1,system_views --output-dir=export-gemini --no-anonymize export-gemini
[same as the equivalent runs for the CQL exporter]
adelphi export-nb
adelphi --no-anonymize export-nb
adelphi --output-dir=export-nb export-nb
adelphi --output-dir=export-nb --no-anonymize export-nb
[the above four runs should fail since nosqlbench exporter only supports a single keyspace]
adelphi --keyspaces=ks1,system_views export-nb
adelphi --keyspaces=ks1,system_views --no-anonymize export-nb
adelphi --keyspaces=ks1,system_views --output-dir=export-nb export-nb
adelphi --keyspaces=ks1,system_views --output-dir=export-nb --no-anonymize export-nb
[same as the equivalent runs for the CQL exporter]

Note that the PR for https://github.com/datastax/adelphi/issues/106 has some developments that will be relevant to this ticket

Note https://github.com/datastax/adelphi/issues/115 probably has some relevance here as well


Feature Request: CLI: add an "app" sub-command/NOUN

Today ACA has app management commands at the top-level - for example:
$ az containerapp create -n myapp --image nginx

instead of:
$ az containerapp app create -n myapp --image nginx

While there is some niceness to not having to specify the resource-type/NOUN, in the long run it's limiting because it means that if we ever have the need for an action/VERB that could apply to both the App and something global then we can't differentiate between the two. For example:
$ az containerapp init

if "init" made sense in both instances we'd be forced to choose a different VERB simply to avoid the ambiguity. But then of course, we may have ambiguity anyway because chances are the two VERBs would probably be synonyms.
There's also the advantage of being able to do:
$ az containerapp --help

add seeing the full list of resources/NOUN in one nice list w/o it also being co-located with VERBs for Apps. It's also more consistent this way to always have things in the form az containerapp NOUN VERB.

Closing this issue, please feel free to reopen if you feel strongly.


New version: evilmartians.lefthook version 1.8.1

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-10-23 01:37:20.763 [FAIL] Installer failed security check. Url: https://github.com/evilmartians/lefthook/releases/download/v1.8.1/lefthook_1.8.1_Windows_i386.exe Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 897.)

@wingetbot run


Something wrong when using whiteout

Hi,everyone.I'm new to whiteout.As the picture shows,how can I resolve this problem?Another question,when logging,I need to input the backup code or upload the PGP key file,can I skip this step?I mean is there a method that I only input the email address and password then I can login successfully?
Thanks.

do you know which imap server you are on? #394 should fix this


[metadata manager m8s] [Validator] implementation for validator

What type of PR is this?

/kind enhancement

What this PR does / why we need it:
This PR helps in validating different query params . and  gives appropriate message to the user if it is invalid.
Test Report Added?:

/kind TESTED

Test Report:

Valid Scenario

If region is invalid and type is given as AWS-S3

If SizeOfBucket is invalid

if Size Operator is invalid

Special notes for your reviewer:

/assign @PravinRanjan10


Dashboard: Send message to active session when deleting a service

Cannot reproduce the same behavior mentioned in #227 when creating or editing services, it happens only when deleting a service.

I think sending a message to the same session won't be needed as well, as the service is deleted anyway, or don't remove/reload until confirmation via the channel message is received.


Office 2019 update

update the generated code from the schema processor (backend)
add code to include new namespaces

too many conflicts, closing and opening new PR for this.


API routes for Room model

Here is the specification for a room model. For context on what the functionality will be here, we will have  a listing of the rooms available to RCOS. The small group model will have a reference to the different rooms (where each small group is located).
- Room
  - name (string)
  - location (string)
  - capacity (number)
  - wheelchair_accessible (boolean)

The role of this issue is to create the needed API routes so that we can do things like add rooms, remove rooms, etc. Here is a list of routes we should have with the associated RESTful verb:

Get ALL rooms
Get specific room
Create a room
Update a room's information
Delete a room from the database

The API for posts may be a good reference (found in server/api/post/index.js).

Resolved