Handling ttys not accepting sequences e.g when suspended by Flow Control

Currently whenever a terminal is in suspended mode (and maybe for some other reasons) and pywal tries to send the color sequences to it the save_file here:
https://github.com/eylles/pywal16/blob/095b169fa8ddbcc0466ee44bbf93e5556194b13f/pywal/sequences.py#L92
it will get stuck trying to write indefinitelly, blocking the writing to the remaining ttys and program itself
I tried this PR Add --active-only flag to only run pywal on active ttys from dylanaraps repo. But unfortunately it didn't work for Kitty, which doesn't show up in who output for some reason and also doesn't handle the aforementioned suspend mode.
So I am wondering if there is a way to reliably detect whether a tty cannot receive input so it is skipped. Konsole links to this wiki page about Software Flow Control, could it be that there is a way to detect in which state a tty is? Or will it be okay putting a timeout to the write operation to abort when it gets stuck?

huh interesting, after checking some stuff it seems the issue may be on how the who(1) program determines the active terminals, a sure fire way to check if a terminal or any process for that matter is active is with ps -o state= -p <pid> which will return the state code with a single char (on the manpage for ps just check the 'state codes' section)
however neither who nor checking the /dev/pts/ dir like pywal does can yield the pid of the terminals to feed ps.
thankfully ps has the -t option to specify a ttylist, then a command constructed like this ps -o uid,pid,state,tty -t <ttylist> where the ttylist is the list of pseudo terminals separated by a comma (for example pts/1,pts/2,pts/3,pts/4,pts/5) will produce output as follows:
  UID   PID S TT
 1000  3651 S pts/1
 1000  4195 S pts/1
 1000  4321 S pts/2
 1000  4518 S pts/3
 1000  4751 S pts/3
 1000  4753 S pts/4
 1000 32551 S pts/5

the only important fields there are the tty and the status columns, so i would remove the uid and pid params from the ps command and we would get:
S TT
S pts/1
S pts/1
S pts/2
S pts/3
S pts/3
S pts/4
S pts/5

with that we would be able to parse the output, if the 'S' column is a T we skip sending sequences to that terminal, however i'm not so sure what would be the best way to deal with duplicate entries and then there are the issues that this most likely won't work for mac nor openbsd which use a different scheme for their pseudo terminals.
i will try to have a branch ready to test this week

Hmm, the state is not changing for me when I enable suspend mode, it returns exactly the same and man page mentions job control and not flow control, very similar name it made me think it was the same thing at first.
So it sounds for me that the later requires a completely different check if it even exists?
Also, interestingly enough, job control to the shell or the parent (Konsole here) doesn't stop tty receiving input:

I've had it happen at random times but never tried to debug it and I don't make use of flow control myself, which is the only way i can manually reproduce this. So is either some software I use suspending a terminal (probably vscode) or a completely different issue perhaps?
For now I will wait for the issue to happen again and try to debug it.

There seemed to be some reports of this also happening in the old pywal repo. https://github.com/dylanaraps/pywal/issues/40#issuecomment-314990634
I did come across this issue myself with WebStorm and I know I worked around it somehow, but I don't remember how. I come across this daily, so I might be able to debug it or try things for y'all.

Hi, I think I found a way to handle this, by using fcntl to set os.O_NONBLOCK flag before trying to write to the file. This way it fails immediately and we can simply log the error?

That sounds like a reasonable approach, maybe @eylles can weight in on if this is acceptable or not?

checking the pr

it works so far so closing this for now.


Superfox

you should also create Superfox which is Firefox for windows 7/8 devices

I imagine with this, the vista extended kernel and this hypothetical Firefox fork would be spreading him quite thin no?

Firefox 115 ESR and special methods to get Firefox 118+ working on Windows 8.1 have negated the need for this fork, until early next year.
Then it will be done.
The Vista extended kernel's scope has been greatly reduced. The situation with One-Core-API and Chromium 11x reveals why Supermium exists; they are having to use a myriad flags and go without certain features to run other Chromium browsers. So I abandoned all efforts of running future Chromium browsers after 111 and make Supermium instead.
However, there will be more Vista extended kernel releases in the future but focusing on kernel mode components such as modified or new drivers.

Then it will be done.

Thank you! We need orange fox in Win7.

I confirm that you can run Firefox 121.0 on Win 8.1.
All you need is to unpack latest (not ESR) FF setup.exe from https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
and edit Optional header of firefox.exe with CFF Explorer (or similar tool).

p.s. Maybe it can run on Win 7, too. But I guess it needs additional DLLs (api-ms-....).

Would that be the same ones currently included with ESR 115.x.x, or would additional ones besides those be needed as well?

p.s. Maybe it can run on Win 7, too.

I tested FF 121 in Windows 7 x64 ESU fully up-to-date environment. And it is no go.
At first program begs for API-MS-WIN-SHCORE-SCALING-L1-1-1.dll.
After putting lib into FF and system32 folders software drops: could not load xpcom error.

Sorry for be too optimistic. FF 121 still can NOT run on Win 7 with many added API-MS- libs nor VxKex.

Sorry for be too optimistic.

https://www.reddit.com/r/windows7/comments/18v3o8j/i_present_you_a_christmas_gift_firefox_121/

https://www.reddit.com/r/windows7/comments/18v3o8j/i_present_you_a_christmas_gift_firefox_121/
This VyvFox is serious project and it really works on Win 7! Thanks for sharing this New Year's gift, @spacedrone404 !

Thanks for sharing this New Year's gift
doing my part, enjoy

Backport of Vyvfox to Firefox, works on Win 7 x64
https://github.com/adeii/supermium-portable/releases/tag/v121

@adeii thanks for the build.
I tested it out with Facebook which is a resources hungry site and the performance is as good as Supermium but then I tried to open a youtube link and it doesn't work. LOL @K4sum1

@adeii thanks for the build. I tested it out with Facebook which is a resources hungry site and the performance is as good as Supermium but then I tried to open a youtube link and it doesn't work. LOL @K4sum1

I have no idea if taking libs breaks anything. I use a custom compile of Vyvfox daily, specifically just for YouTube, and have 0 issues.

Backport of Vyvfox to Firefox, works on Win 7 x64 https://github.com/adeii/supermium-portable/releases/tag/v121

odd things of github... :cop:
this post has not been edited however it takes me to Supermium portable download links which didn't exist last month.
I also realized vyvfox is now r3dfox....

this post has not been edited however it takes me to Supermium portable download links which didn't exist last month.

It's possible to remove a git tag based github release and recreated it with the same name.

this post has not been edited however it takes me to Supermium portable download links which didn't exist last month.

Sorry for old tag. Correct link is https://github.com/adeii/supermium-portable/releases/tag/F121

On the topic of Firefox backported, 122 is a thing.
https://github.com/Eclipse-Community/r3dfox/releases/tag/122.0.1-beta

Sorry for old tag.

it's not your fault dude. I had already downloaded this fork 2 weeks ago
this kind of things blows my mind because github superseded the previous link without notifying it

On the topic of Firefox backported, 122 is a thing.
Does not work on XP or Vista stock.

it's a shame if we'll get stuck on Mypal 68 forever :cry:

On the topic of Firefox backported, 122 is a thing.
Does not work on XP or Vista stock.

it's a shame if we'll get stuck on Mypal 68 forever 😢

I'm not a good programmer, there is no chance I get it working on XP or Vista stock. If fedor2 or someone else were to help and backport it to those versions, I would welcome it. If this does happen though, I'm not going the cheap closed source progwrp route.

I'm not a good programmer, there is no chance I get it working on XP

No problem https://github.com/win32ss/supermium/issues/207#issuecomment-1916105316

If Feodor2 or someone else were to help and backport it to those versions, I would welcome it.

No chance.  https://github.com/Feodor2/Mypal68/issues/222#issuecomment-1625445014

I'm not a good programmer, there is no chance I get it working on XP or Vista stock.
Although Windows XP support is surely nice, i think that availability of SuperFox for Windows 7 is a more critical thing.

@spacedrone404 Kinda aged poorly, I had enough will to do it.
https://github.com/Eclipse-Community/r3dfox/releases/tag/v126.0.2v
Also why wait for Superfox when r3dfox exists?

Also why wait for Superfox when r3dfox exists?
Currently i'm on 115 ESR and will switch to RedFox around October 2024, after all things settle down.
I like ESR stability. And yeah, variety is always a good thing.


Create setenv.sh

Issue

Link:
Summary:

How

Screenshots

References

Checklist

[ ] Tests added
[ ] Cleaned up commit history (rebase!)
[ ] Documentation added
[ ] Thought about variable and method names

@shawaj We need to source it in the start-gateway-config.sh and add it to the dockerfile too

@shawaj This one for the dockerfile:
COPY setenv.sh /opt/nebra/setenv.sh

@shawaj This one for the dockerfile: COPY setenv.sh /opt/nebra/setenv.sh

It's already in there

https://github.com/NebraLtd/hm-config/blob/13f1eb5b1887df09db3111dc9c258c6f56280c69/Dockerfile#L68


can't get newast tests to run

$ rake test
NameError: uninitialized constant Mirah::Scoper
  const_missing at org/jruby/RubyModule.java:2569
  const_missing at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking/gems/rake-<IP_ADDRESS>/lib/rake/ext/module.rb:36
   MockCompiler at /Users/nick/hacking/newast_mirah/test/test_compilation.rb:26
        TestAst at /Users/nick/hacking/newast_mirah/test/test_compilation.rb:24
         (root) at /Users/nick/hacking/newast_mirah/test/test_compilation.rb:21
        require at org/jruby/RubyKernel.java:1038
       __file__ at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:15
         select at org/jruby/RubyArray.java:2400
         (root) at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:4
rake aborted!
Command failed with status (1): [/Users/nick/.rvm/rubies/jruby-1.6.4/bin/jr...]

Tasks: TOP => test
(See full trace by running task with --trace)

@ribrdb thoughts? I grepped through lib/ and test/ and couldn't see any mention of Mirah::Scoper

The newast branch is still pretty broken. The only tests I've got running
are test_jvm_compiler and test_typer. I run them individually:
$ jruby test/test_jvm_compiler.rb
A lot of stuff has been rewritten in Mirah, including the scoper class so
any references to the old one need to be fixed. I think test_compilation is
completely obsolete now though. The compiler now just uses the AST visitor
api.

I was thinking about trying to merge master into newast, but I wanted to make sure I didn't break anything that wasn't already broken.

Ok, the tests should all run now on the newast branch.
On Mon, Oct 24, 2011 at 8:00 PM, Nick Howard <
<EMAIL_ADDRESS>
I was thinking about trying to merge master into newast, but I wanted to
make sure I didn't break anything that wasn't already broken.
--
Reply to this email directly or view it on GitHub:
https://github.com/mirah/mirah/issues/154#issuecomment-2512409

now I get
TypeError: Node is not a class
       AST at /Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:40
    (root) at /Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:18
   require at org/jruby/RubyKernel.java:1038
    (root) at /Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:21
   require at org/jruby/RubyKernel.java:1038
    (root) at /Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/compiler/java_source.rb:20
   require at org/jruby/RubyKernel.java:1038
  __file__ at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:15
    select at org/jruby/RubyArray.java:2400
    (root) at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:4
rake aborted!
Command failed with status (1): [/Users/nick/.rvm/rubies/jruby-1.6.4/bin/jr...]

any suggestions?
I can get ruby test/test_jvm_compiler.rb to run, but only two assertions pass. I see a lot of
Mirah::InternalCompilerError: undefined method `to_widen' for #<BiteScript::FileBuilder:0x70a80cf0>

and
NoMethodError: undefined method `parent' for #<Java::OrgMirahTyper::Typer:0x7c4a8355>
    /Users/nick/hacking/newast_mirah/lib/mirah/jvm/types/integers.rb:133:in `add_intrinsics'

the "Node is not a class" error should be fixed by my latest push.
You need to checkout the latest bitescript to fix the "to_widen" issue.
On Tue, Oct 25, 2011 at 6:48 PM, Nick Howard <
<EMAIL_ADDRESS>
now I get
TypeError: Node is not a class
      AST at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:40
   (root) at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:18
  require at org/jruby/RubyKernel.java:1038
   (root) at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:21
  require at org/jruby/RubyKernel.java:1038
   (root) at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/compiler/java_source.rb:20
   require at org/jruby/RubyKernel.java:1038
 __file__ at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking
/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:15
   select at org/jruby/RubyArray.java:2400
   (root) at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking
/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:4
rake aborted!
Command failed with status (1):
[/Users/nick/.rvm/rubies/jruby-1.6.4/bin/jr...]

any suggestions?
I can get ruby test/test_jvm_compiler.rb to run, but only two assertions
pass. I see a lot of
Mirah::InternalCompilerError: undefined method `to_widen' for
#<BiteScript::FileBuilder:0x70a80cf0>

and
NoMethodError: undefined method `parent' for
#<Java::OrgMirahTyper::Typer:0x7c4a8355>
   /Users/nick/hacking/newast_mirah/lib/mirah/jvm/types/integers.rb:133:in
`add_intrinsics'

--
Reply to this email directly or view it on GitHub:
https://github.com/mirah/mirah/issues/154#issuecomment-2525590

Oops, I missed part of the commit.  Try again now ( you still need the
latest bitescript ).
On Wed, Oct 26, 2011 at 9:01 AM, Rib Rdb<EMAIL_ADDRESS>wrote:

the "Node is not a class" error should be fixed by my latest push.
You need to checkout the latest bitescript to fix the "to_widen" issue.
On Tue, Oct 25, 2011 at 6:48 PM, Nick Howard <
<EMAIL_ADDRESS>
now I get
TypeError: Node is not a class
      AST at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:40
   (root) at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:18
  require at org/jruby/RubyKernel.java:1038
   (root) at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/source_generator/precompile.rb:21
  require at org/jruby/RubyKernel.java:1038
   (root) at
/Users/nick/hacking/newast_mirah/test/../lib/mirah/jvm/compiler/java_source.rb:20
   require at org/jruby/RubyKernel.java:1038
 __file__ at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking
/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:15
   select at org/jruby/RubyArray.java:2400
   (root) at /Users/nick/.rvm/gems/jruby-1.6.4@mirah_hacking
/gems/rake-<IP_ADDRESS>/lib/rake/rake_test_loader.rb:4
rake aborted!
Command failed with status (1):
[/Users/nick/.rvm/rubies/jruby-1.6.4/bin/jr...]

any suggestions?
I can get ruby test/test_jvm_compiler.rb to run, but only two assertions
pass. I see a lot of
Mirah::InternalCompilerError: undefined method `to_widen' for
#<BiteScript::FileBuilder:0x70a80cf0>

and
NoMethodError: undefined method `parent' for
#<Java::OrgMirahTyper::Typer:0x7c4a8355>
   /Users/nick/hacking/newast_mirah/lib/mirah/jvm/types/integers.rb:133:in
`add_intrinsics'

--
Reply to this email directly or view it on GitHub:
https://github.com/mirah/mirah/issues/154#issuecomment-2525590

I have latest bitescript from headius/bitescript and I'm still getting the to_widen errors, but the node errors are gone. Instead I'm getting
NoMethodError: undefined method `type_factory=' for Mirah::AST:Module
    /Users/nick/hacking/newast_mirah/test/test_javac_compiler.rb:66:in `compile'

Trying again, grepping through bitescript, to_widen is not defined in the latest bitescript. Might you have a local copy with it added?

Yep I found a couple commits I never pushed. Want to try again?

I merged master into newast. Tests run. There's still quite a lot of broken things though.


cat in the picture is NOT el gato

it looks like floppa!! how could you do this FBXImportGeneric!!! 😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡😡

I cannot believe this

fr

solved


genpolicy: add support for cc-local-csi

Merge Checklist

[x] Followed patch format from upstream recommendation: https://github.com/kata-containers/community/blob/main/CONTRIBUTING.md#patch-format

[x] Included a single commit in a given PR - at least unless there are related commits and each makes sense as a change on its own.

[x] Aware about the PR to be merged using "create a merge commit" rather than "squash and merge" (or similar)
[x] genPolicy only: Ensured the tool still builds on Windows
[x] genPolicy only: Updated sample YAMLs' policy annotations, if applicable
[x] The upstream-missing label (or upstream-not-needed) has been set on the PR.

Summary

Adds support for cc-local-csi to genpolicy, reusing most of the code from my previous PR.
Test Methodology

Manual testing, ensuring we're not regressing on cc-managed-csi/managed-csi/emptyDir, using the YAML below:

YAML test file

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-managed-cc-csi
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 50Gi
  storageClassName: cc-managed-premium-csi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: pvc-managed-csi
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 50Gi
  storageClassName: managed-csi
---
kind: Pod
apiVersion: v1
metadata:
  name: managed-local
spec:
  runtimeClassName: kata-cc
  containers:
    - image: "busybox:latest"
      name: busybox
      command:
        - sleep
        - "infinity"
      volumeMounts:
        - name: cc-managed-csi-vol
          mountPath: /mnt/persistent-ok
        - name: managed-csi-vol
          mountPath: /mnt/persistent-broken
        - name: cc-local
          mountPath: /mnt/scratch-ok
        - name: emptydir
          mountPath: /mnt/scratch-broken
  volumes:
    - name: cc-managed-csi-vol
      persistentVolumeClaim:
        claimName: pvc-managed-cc-csi
    - name: managed-csi-vol
      persistentVolumeClaim:
        claimName: pvc-managed-csi
    - name: cc-local
      ephemeral:
        volumeClaimTemplate:
          spec:
            accessModes:
              - ReadWriteOnce
            storageClassName: cc-local-csi
            resources:
              requests:
                storage: 1Gi
    - name: emptydir
      emptyDir: {}

I just verified Windows build. I would ask for one geen pipeline test run before merging. I forgot to ask last PR. I can help debug failures, if any


Add edn/clojure syntax highlight to scripting documentation code blocks

There are plugins to add syntax coloring. It just that the documentation of such plugins is very hard to understand: they expect you to know how mkdocs works internally and provide no easy step to integrate it.
Originally posted by @Kryptos-FR in https://github.com/fragcolor-xyz/chainblocks/pull/75#discussion_r661112230

@Kryptos-FR this probably should be high priority. But let's wait until PR merged and docs deployed.


Try another AppVeyor hack.

Trying an alternative hack to get conda to work on AppVeyor.
xref: #28 https://github.com/conda/conda/issues/6527
cc: @isuruf @bgruening

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Added styles for "replied to" fields

Thank you! 😄 Sorry for the late response, have been busy recently. Will look at this now.

@csatacsirke do you still want to fix this? If not, I can do it ☺

Ah, sorry again, just life came up, and i can't find time to finish it :( Please do it :)

Okay will do! 😄


Alignment of buttons on Home page

The buttons on the home page are misaligned and also a "Home" buttons is displayed twice. This affect the overall visual appeal and usability of the interface.
I would like to contribute to solve this issue. So, please assign it to me.

I have solved this issue @vishanurag . Please tag me under gssoc'24 and hacktoberfest.

Closed via #1027


Require mutable reference for send_back method call

This PR is separated from #365 to buy time to make backward incompatible changes.

Important! This PR prevents of creating and calling callbacks in view methods.

bors r+


Add more locking to storage drivers

fixes #31017
Most drivers currently seem to rely on the lock in the refCounter but this is not enough for a safe api. A simple case that is not working is 2 parallel Get() calls. First one will start the actual mount(slow process) while the second gets a cache hit from the refcounter. After the second one returns data is read from that path but it has not even finished mounting yet.
@cpuguy83 @dmcgowan
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>

LGTM

Is this issue fixed? Which build or docker version can I try?

@JackyChen255 master build from https://master.dockerproject.org/

Which official release will include this fix? 17.03.0-ce (2017-03-01)?

@tonistiigi Which official release will include this fix? 17.03.0-ce (2017-03-01)? Thanks

@JackyChen255 This was not picked for 17.03.x branch.

@JackyChen255 thanks to our new release schedule, you won't have to wait too long, this will in included in the next release, 17.04 (to be released in April)


feat: support 'goog:loggingPrefs' value when creating a session

Problem: Able to receive performance log types and get performance logs when using Mobile JSON Wire protocol but unable to do the same when using W3C.
Reason: The logging preferences are set using "goog:LoggingPrefs" in Selenium capability. "[enablePerformanceLogging](https://github.com/appium/appium-android-driver/blob/92b51340cd976a73cb60530d6cdd6d43414b939a/lib/commands/context/helpers.js#L208)" is deprecated and Selenium 4 does not allow passing it. However, the Appium Android driver did not account for it and set it correctly to pass it to the Appium Chromedriver. Thus, the ChromeDriver would not receive it and then create a default session with the default logging preferences i.e. {browser: ALL}.
Logs (when trying to use the Appium server):
Capabilities sent:
22024-08-28 14:12:36:753 - [HTTP] {"capabilities":{"firstMatch":[{"goog:chromeOptions":{"args":["--proxy-bypass-list=<-loopback>","test-type","--proxy-server=http://[REDACTED]","--disable-features=Translate"]},"newCommandTimeout":0,"goog:loggingPrefs":{"performance":"ALL"},"appium:skipServerInstallation":"true","platformName":"Android","deviceName":"android","browserName":"chrome"}]}}
Capabilities when creating a ChromeDriver session capabilities:
2024-08-28 14:12:40:644 - [AndroidDriver] Merging 'goog:chromeOptions' into 'chromeOptions'. This may cause unexpected behavior
2024-08-28 14:12:40:644 - [debug] [AndroidDriver] Before starting chromedriver, androidPackage is 'com.android.chrome'
2024-08-28 14:12:40:645 - [debug] [Chromedriver] Changed state to 'starting'
2024-08-28 14:12:40:645 - [Chromedriver] Set chromedriver binary as: /usr/local/.browserstack/deps/chromedriver/v123.0.6312.86/chromedriver
2024-08-28 14:12:40:645 - [debug] [Chromedriver] Killing any old chromedrivers, running: pkill -15 -f "/usr/local/.browserstack/deps/chromedriver/v123.0.6312.86/chromedriver.*--port=18086"
2024-08-28 14:12:40:663 - [Chromedriver] No old chromedrivers seem to exist
2024-08-28 14:12:40:663 - [debug] [Chromedriver] Cleaning any old adb forwarded port socket connections
2024-08-28 14:12:40:664 - [debug] [ADB] List forwarding ports
2024-08-28 14:12:40:664 - [debug] [ADB] Running '/usr/local/.browserstack/android-sdk/platform-tools/adb -P 5037 -s R5CT21L7E6E forward --list'
2024-08-28 14:12:40:671 - [Chromedriver] Spawning chromedriver with: /usr/local/.browserstack/deps/chromedriver/v123.0.6312.86/chromedriver --url-base=wd/hub --port=18086 --adb-port=5037 --verbose
2024-08-28 14:12:40:681 - [debug] [Chromedriver] Chromedriver version: '123.0.6312.86'
2024-08-28 14:12:40:682 - [debug] [WD Proxy] Matched '/status' to command name 'getStatus'
2024-08-28 14:12:40:682 - [debug] [WD Proxy] Proxying [GET /status] to [GET http://<IP_ADDRESS>:18086/wd/hub/status] with no body
2024-08-28 14:12:40:684 - [debug] [WD Proxy] Got response with status 200: {"value":{"build":{"version":"123.0.6312.86 (9b72c47a053648d405376c5cf07999ed626728da-refs/branch-heads/6312@{#698})"},"message":"ChromeDriver ready for new sessions.","os":{"arch":"x86_64","name":"Linux","version":"5.16.12-200.fc35.x86_64"},"ready":true}}
2024-08-28 14:12:40:684 - [Chromedriver] Starting W3C Chromedriver session with capabilities: {
2024-08-28 14:12:40:684 - [Chromedriver]   "capabilities": {
2024-08-28 14:12:40:684 - [Chromedriver]     "alwaysMatch": {
2024-08-28 14:12:40:684 - [Chromedriver]       "goog:chromeOptions": {
2024-08-28 14:12:40:684 - [Chromedriver]         "androidPackage": "com.android.chrome",
2024-08-28 14:12:40:684 - [Chromedriver]         "args": [
2024-08-28 14:12:40:684 - [Chromedriver]           "--proxy-bypass-list=<-loopback>",
2024-08-28 14:12:40:684 - [Chromedriver]           "test-type",
2024-08-28 14:12:40:684 - [Chromedriver]           "--proxy-server=http://[REDACTED]",
2024-08-28 14:12:40:684 - [Chromedriver]           "--disable-features=Translate"
2024-08-28 14:12:40:685 - [Chromedriver]         ],
2024-08-28 14:12:40:685 - [Chromedriver]         "androidDeviceSerial": "R5CT21L7E6E"
2024-08-28 14:12:40:685 - [Chromedriver]       },
2024-08-28 14:12:40:685 - [Chromedriver]       "goog:loggingPrefs": {
2024-08-28 14:12:40:685 - [Chromedriver]         "browser": "ALL"
2024-08-28 14:12:40:685 - [Chromedriver]       }
2024-08-28 14:12:40:685 - [Chromedriver]     }
2024-08-28 14:12:40:685 - [Chromedriver]   }
2024-08-28 14:12:40:685 - [Chromedriver] }

Note that the capabilities sent while creating a ChromeDriver session do not contain the logging preferences: "performance": "ALL” but only the default value "browser": "ALL". This change fixes it in the Android appium driver.

Hi @pujagani, congrats, the Appium project wants to compensate you for this (and perhaps other) contribution(s) this month! Please reply to this comment mentioning me and sharing your OpenCollective account name, so that we can initiate payment! Or let me know if you decline to receive compensation via OpenCollective. Thank you!

Thank you so much @jlipps! OpenCollective details :  https://opencollective.com/pujagani


[Proposal] Set domain, tags etc. via the context

Having all fields for the error builder settable via context.Context would make it easy to make sure that any error further down in the chain has e.g., the domain set.
Motivation
For us the use case is that we have different areas of the code where it would be nice to always be able to ensure all errors have a domain or tags set.
Rather than enforcing everyone to remember to add In -- which sometimes might even be possible to figure out as you don't know what the call-chain is -- you set the In via the context and then as long as you do WithContext it will get set automatically.
Interface
In terms of interface I'm not sure what would be the best to avoid confusion. I can think of a few different ways

Prefixing with With.
Prefixing with WithContext.
Prefixing with Context.
Setting a default OopsErrorBuilder in the context.

(1) would have functions like WithIn. It has the advantage of being similar to other APIs when using context but doesn't play very nicely with the already existing function With (WithWith?).
(2) would have functions like WithContextIn. It is similar to the above but still sounds weird (WithContextWith?) and is maybe unnecessarily verbose without much clarity.
(3) would have functions like ContextIn or ContextTags which while not fully in line with what you would expect in therms of API doesn't collide with other names used and is also fairly clear what it would do.
(4) would need only two functions WithBuilder which sets a default builder in the context that can then be retrieved with FromContext(ctx).
Example
As an example of how it could look.
First of all, you add what you want to the context, using:
ctx := oops.WithBuilder(ctx, oops.In("domain"))

Then somewhere further down the call chain you then do
return oops.FromContext(ctx).Wrap(err)

Hi @mbark
Thanks for this great suggestion and your different API proposals.
For comparison, here is the list of helpers in OTEL:

ContextWithSpan
ContextWithSpanContext
ContextWithRemoteSpanContext
SpanFromContext
SpanContextFromContext

I'm accepting the PR.

As an extension to your PR, what do you think about merging multiple OopsErrorBuilder ?
Example:
ctx := context.Background()

ctx = oops.WithBuilder(ctx, oops.In("domain"))
// ...
ctx = oops.WithBuilder(ctx, oops.Tag("tag"))

err := oops.FromContext(ctx).Errorf("error")

err.(OopsError).Tags()       // []string{"tag"}
err.(OopsError).Domain()     // "domain"


ES6 constructor returns class instead of object while switching F12 on or off

https://github.com/Microsoft/ChakraCore/issues/1496#issuecomment-276930383
Repro here: https://gist.github.com/michabaur/2a627a3e7a5703dbd682b6ef3274e5dc
Also repros without 'require.min.js'.
No repro if class is defined/declared in the same scriptContext.

https://github.com/Microsoft/ChakraCore/pull/2504


Style changes for Essential search area

Description of PR
Changed styling for search area in Essentials page to match the design language of the site
Type of PR

[x] Bugfix
[x] Refinement

Checklist

[x] Compiles and passes lint tests
[x] Properly formatted
[x] Tested on desktop
[x] Tested on phone

Screenshots

Added Max width to search area so it won't stretch all the way to edges, Fixes #1141   hidden search results by NavBar.

Adjusted search button to match even layout
BEFORE

AFTER

Adjusted ListItems and CollapseItem Styles for Guive seamless even look
BEFORE

AFTER

Fixes #1146 #1140

@nikita-11 Can you have a look at this?

Patched by #1383. Thanks anyway :)


Allow unbounded quoted sequences \Q...

PCRE and ICU both support quoted sequences that don't have a terminating \E. Update the parsing to allow this.

@swift-ci please test

Ah actually it's probably better to continue reject \Q\E as [\Q\E] should definitely be illegal

@swift-ci please test

@swift-ci please test


Sailsjs 1.0 breaks if cache option i sadded to webpack config

Webpack config option to add
cache: {
type: 'filesystem',
maxMemoryGenerations: 10
}
Message I get from sails after running sails lift:
error:
error:
-------------------------------------------
The sails.config.cache setting is no longer available in Sails 1.0.
Please use sails.config.http.cache instead.
-------------------------------------------
BUT I MODIFIED WEBPACK CACHE!!!!

Hi @rantiev, the sails.config.cache option was previously used to configure the cache in previous versions of Sails and is now deprecated.
We recommend that you nest your cache configuration under sails.config.custom configuration. e.g., sails.config.custom.cache


chore: bump version to 1.1.0

Issue #, if available:
Description of changes: Update version to 1.1.0 to update SAR latest version.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Ensure GAMS can run all the benchmarks

#181 would need to be finished first

Also there are Element is redifined errors which are caused by multiple descriptions for the same processes / commodities.

What is the reasoning for including in times_prc_sets only "DMD", "CHP", "ELE", "HPL", "IRE", "NST", "PRE", "STG", "STK", "STS"?  Why not include other types as well, e.g. DISTR, MISC, PRV, PRW, REF, XTRACT, RENEW?  Some of these even have special meaning in the TIMES code, and therefore models would not work correctly if you exclude them.

Thanks, @Antti-L. No particular reason, except for the other types not present in any of the benchmark and the ease with which the list can be expanded. I can include all of the already. I.e. all members of SET PRC_GRP in maplists.def?


Cannot synchronize data using materialized views

Bug Report
Briefly describe the bug
When I insert data
Transaction is not in running status, but in Finished: while write prefix to view kafka_view.test_play_game_to_test_play_game
The result you expected
Can be used normally
How to Reproduce
target table
CREATE TABLE log.test_play_game
(
    `ck_date` Date,
    `kind` String,
    `task_id` Nullable(String),
    `num` Nullable(Int64)
)
ENGINE = CnchMergeTree
PARTITION BY ck_date
ORDER BY (ck_date, kind)
TTL ck_date + toIntervalMonth(1)
SETTINGS storage_policy = 'cnch_default_s3'

source table
CREATE TABLE log.test_play_game_source
(
    `ck_date` Date,
    `kind` String,
    `task_id` Nullable(String),
    `num` Nullable(Int64)
)
ENGINE = CnchMergeTree
PARTITION BY ck_date
ORDER BY (ck_date, kind)
TTL ck_date + toIntervalMonth(1)
SETTINGS storage_policy = 'cnch_default_s3'

materialized view
CREATE MATERIALIZED VIEW kafka_view.test_play_game_to_test_play_game TO log.test_play_game
(
    `ck_date` Date,
    `kind` String,
    `task_id` Nullable(String),
    `num` Nullable(Int64)
) AS
SELECT *
FROM log.test_play_game_source

insert data
insert into log.test_play_game_source
values ('2023-08-31', 'play_game', '1234567', 10);

Version
<IP_ADDRESS>

Materialized view support will be production ready in the next replease 0.2.0

Could you try the new version and update?

@kevinthfang It has been tested and can be used normally. Thank you very much.


Armor Effects Overlay

Can we get an overlay that shows what stats/perks equipped items are giving us?  IE Void , Barrowers ,diary gear and 99 capes .

Duplicate


.waves-effect doesn't work with sass

I'm trying to create an angular2 application with materializecss, but the .waves-effect does not work when extended using sass.
Here is my angular.cli.json:
{
  "$schema"<EMAIL_ADDRESS>  "project": {
    "name": "todolist-front"
  },
  "apps": [
    {
      "root": "src",
      "outDir": "dist",
      "assets": [
        "assets",
        "favicon.ico"
      ],
      "index": "index.html",
      "main": "main.ts",
      "polyfills": "polyfills.ts",
      "test": "test.ts",
      "tsconfig": "tsconfig.app.json",
      "testTsconfig": "tsconfig.spec.json",
      "prefix": "app",
      "styles": [
        "styles.css"
      ],
      "scripts": [
        "../node_modules/jquery/dist/jquery.js",
        "../node_modules/hammerjs/hammer.js",
        "../node_modules/materialize-css/dist/js/materialize.js"
      ],
      "environmentSource": "environments/environment.ts",
      "environments": {
        "dev": "environments/environment.ts",
        "prod": "environments/environment.prod.ts"
      }
    }
  ],
  "e2e": {
    "protractor": {
      "config": "./protractor.conf.js"
    }
  },
  "lint": [
    {
      "project": "src/tsconfig.app.json"
    },
    {
      "project": "src/tsconfig.spec.json"
    },
    {
      "project": "e2e/tsconfig.e2e.json"
    }
  ],
  "test": {
    "karma": {
      "config": "./karma.conf.js"
    }
  },
  "defaults": {
    "styleExt": "css",
    "component": {}
  }
}

Here is my styles.scss:
$roboto-font-path: "../node_modules/materialize-css/dist/fonts/roboto/";
@import "../node_modules/materialize-css/sass/materialize";

button {
  @extend .waves-effect, .btn; // .waves-effect is extended as seen
}

Here is my component html:
  <button class="waves-effect">Waves effect works here</button>
  <button>Waves effect doesnt work here</button>

As seen, the waves effect works with the first button but not the second, even though .waves-effect is extended in styles.scss. To be clear, extending other classes such as .btn work perfectly fine. Please help me in solving this.
Thanks

It works with SCSS, is that an option for you?


Disable map button if no location data available

If no location data for the current incident is available, the "open map" buttons should be clearly deactivated. Currently there is only a popup shown on click of the button.

fixed in version 1.1.3


Integrating scroll-snap-api for current slide and revamp the setup

Hi,
Like i mentioned in the draggable issue, maybe the scroll-snap-api can help to get a more accurate result on your current slide.
I wrote a proof a concept below, which also works with scroll-snap-align: start; And vertical scrolls could be easily added.
There's no debouncer in the scroll, and it isn't clean code but here's an idea for a revamp
 // init slider
  Slider.init({
    slider: ".snap-slider",
    item: ".snap-slide",
    active:".active",
    // can be false or ignored
    paginate: ".snap-paginate",
    mousedrag:true,
    autoplay:false,
  });

This means that multiple sliders can be activated at once, no plugins (that extra 4kb is worth it for a faster setup)
You could add a default css file with default classnames as well, but you can also use your own classnames
an active class would be very helpfull, assigned to the slides and buttons (not yet in this example)
slider should be re-iniated on resizing the window since the coordinates of the scroll-snap-api needs to be calculated again

there is also an next and prev within the scroll-snap-api
import { scrollSnapToNext } from 'scroll-snap-api';
scrollSnapToNext( scrollingElement, 'right' ); // 'left', 'right', 'up', 'down'

structure

Slide 1

Slide 2


Error on new page creation -  tinyMCE related

Sorry, me again 🙄.
On another instance, I get an error when trying to create a new page:
Impossible to create the root directory "/var/www/html/public/assets/_tinymce". The "Symfony\Component\Cache\Simple\AbstractCache" class is deprecated since Symfony 4.3, use "Symfony\Component\Cache\Adapter\AbstractAdapter" and type-hint for "Symfony\Contracts\Cache\CacheInterface" instead.

I tried creating the folder manually , it doesn't make any difference. I wonder if it tries to write to filesystem and not to S3 for some reason?
Thanks

Sorry, it seems
RUN mkdir -p /var/www/html/public/assets/_tinymce && chown -R www-data:root /var/www/html/public

in my Dockerfile fixes it...


Commenting not working; "commentstring empty"

Hi, I'm facing some obstacles in my quest for templ support in nvim. It all seems to be working - except for commenting:

Browsing through the issues here, it seems that commenting is working for others, which is why i'm posting here.

checkhealth: - templ               ✓ . . . ✓
LspInfo: Both templ and html loaded.

I have tried creating .config/nvim/after/ftplugin/templ.lua with vim.bo.commentstring = "// %s". That would allow me to comment, but as soon as i save the file and auto-format does its thing, sections with comments break the file.
My setup is:

LazyVim starter from https://www.lazyvim.org/installation
One custom plugin file https://github.com/eschmar/dotfiles/blob/master/nvim/froid.lua

Trying a fresh lazyvim install with just enabling go+templ yielded the same result.. Is this working for others? Any advice would be highly appreciated! Sorry if I'm writing in the wrong place, I'm fairly new to more custom nvim configurations. Thanks!

Sorry for the ambiguity and thanks for your response! With commenting I mean toggling a selection of code or a code line to be commented or un-commented (with gc). From the notes of mini.comment:

To use tree-sitter aware commenting, global value of 'commentstring' should be '' (empty string). This is the default value in Neovim>=0.9, so make sure to not set it manually.

I inferred from this excerpt that tree-sitter would provide instructions on how to comment. But now after your comment and reading into the source, that's not the case (it's from the file type).. I'll post a solution here if i can find one to at least provide some value to the issue, otherwise this can be closed. Thanks again!

Yeah skimming through the source code of mini.comment I don't quite get what tree-sitter should provide for it to work.


fix: resolve serialization errors in .NET examples

This ended up being a slightly bigger commit than I anticipated. But, I essentially did two things:

Annotate all *Result types in Mondocks.Net/Types.fs with [<BsonIgnoreExtraElements>]; otherwise, the .NET MongoDB Driver freaks out that the schema doesn't match exactly.

Avoid serializing each Index object in the IndexBuilder. When I first ran the example in samples/Indexes, it failed with this exception:

Unhandled exception. MongoDB.Driver.MongoCommandException: Command createIndexes failed: BSON field 'createIndexes.indexes.0' is the wrong type 'string', expected type 'object'.

So we DON'T need the serialization step in the IndexBuilder anymore (though I kept the interface the same).
Finally, I added a Nix flake with a very simple devShell because that's just what I'm used to developing with.

Closes #36.

Feel free to ignore/delete the Nix flake if you're not interested 😅. I'm not building anything, just providing a very simple devShell that brings dotnet6.0 into the $PATH. (But, if you have any questions, feel free to ping me!)


Func unwrap_partitions doesn't work for 'python' engine

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): all
Modin version (modin.__version__): 0.9.1+01ba1f40c032e92f16dd6f276e238baf5473bda7
Python version: 3.8.5
Code we can use to reproduce:

import os
os.environ["MODIN_ENGINE"] = "python"
import modin.pandas as pd
from modin.distributed.dataframe.pandas import unwrap_partitions

df = pd.DataFrame([0])
parts = unwrap_partitions(df, axis=0, get_ip=True)
print(parts)

Describe the problem

Possible, support of unwrapping partitions is implemented for Ray/Dask engines only.
Source code / logs

@YarShev please, take a look

@prutskov , that is not a bug. The feature is mainly intended for cluster users to help them minimize data movement by using partition IPs. That doesn't make sense for python engine. Reclassifying the issue as a question.

@YarShev, In this case need to show user-friendly exception, instead of:
parts = unwrap_partitions(df, axis=0, get_ip=True)
  File "/localdisk/aprutsko/modin/modin/distributed/dataframe/pandas/partitions.py", line 84, in unwrap_partitions
    return [
  File "/localdisk/aprutsko/modin/modin/distributed/dataframe/pandas/partitions.py", line 85, in <listcomp>
    part.force_materialization(get_ip=get_ip).unwrap(
  File "/localdisk/aprutsko/modin/modin/engines/base/frame/axis_partition.py", line 115, in force_materialization
    return type(self)(materialized, get_ip=get_ip)
TypeError: __init__() got an unexpected keyword argument 'get_ip'

The user will be confused by this error.

@prutskov , yes, sure. We throw the exception but it is for axis is None only, unfortunately. We need to add the exception for axis=0 and axis=1 as well. I will open a conforming issue for that. If you do not have something else, feel free to close the issue.

Adding the feature regarding getting partition and conforming node IP address for python engine will require additional efforts and significant refactoring of the code. I do not see that is necessary. We could support getting python partition without node IP address for debug purposes if we really want it.

I don't think we plan to fix something here. You can close the issue.


Fixed shadow issue when using Autolayout

This fixes the issue described in #47

Thanks for contributing this PR. I've made this update with a small change to work with Swift 3.


Feature request: ignore-file option for no-import-side-effect

Similarly to the current option that takes a regex to match modules that should be allowed to be imported with side effects, it'd be nice if there were an option that would let me do the same thing except for files in my project.
Specifically, I have a main.ts that imports a decent number of external modules for their side effects by design, and it'd be more convenient to configure "no-import-side-effect": [true, {"ignore-file": "main\\.ts"}] than "no-import-side-effect": [true, {"ignore-module": "(angular|angular-material|jquery|zone\\.js|etc.)"]. This would also solve the problem that I don't necessarily want any other files performing side-effect imports of, say, zone.js just because main.ts does it.

I'm fairly opposed to adding file names or globs to rule config options. tslint.json should define how to lint, not what to lint. I suggest using comment flags for your use case. Related: https://github.com/palantir/tslint/issues/629#issuecomment-261291205

Cool, makes sense. In that case, is the ignore-module option most likely going to be deprecated at some point?


Title anchor

Add title-link before each title

SWG-76

This is already supported with the new style guide in version 3.0.0.


Minify images

closes #8

I couldn't run generate minified png images though because my computer hangs when I run gulp svg2png (a lot of phantomjs instances start running in background and eat all RAM and swap).

Nice, I am planning to cherry-pick your commit. So would not merge directly. Thanks!!


Save config to file after change

Hey,
Let me point out first that I really enjoy managing my project with sacred!
One small thing I am not sure about whether this is possible currently.
Small example:

I save my configuration using a function decorated with @experiment.config:   a = 0

I change some of the variables using @experiment.capture:   a=1
However after (2.) the values in the config.json are not updated (a is still 0). Is there a way to do this?

I managed to do this now in the following way
def update_config_json(keys, values, sacred_output_path, sacred_id):

    def nested_set(dic, keys, value):
        for key in keys[:-1]:
            dic = dic.setdefault(key, {})
        dic[keys[-1]] = value

    sacred_run_file = os.path.join(sacred_output_path, sacred_id, "config.json")
    if os.path.exists(sacred_run_file):
        with open(sacred_run_file) as config_file:
            config = json.load(config_file)

        for key, value in zip(keys, values):
            nested_set(config, key, value)

        with open(sacred_run_file, "w", encoding='utf-8') as config_file:
            json.dump(config, config_file, ensure_ascii=False, indent=4)

However I would like to know if there is a built-in way of doing this in sacred.

What exactly are you trying to achieve? Sacred first builds up the config from the command line args and config scopes (e.g., @experiment.config), then passes it to the observers that save it and after that, the experiment is executed with the constructed configuration (which is passed to captured functions @experiment.capture) which is fixed for this specific run. The captured functions are meant to use the configuration but not to modify it, because this cannot be recorded properly. There should be no need to update the configuration after it is constructed from the config scopes and sacred actually raises an error if it detects that you tried to modify the configuration.
So if you want to update the configuration somewhere in a captured function after it was constructed, sacred does not support this and there is probably a different way to achieve the same thing just by using config scopes. There is no way to change the configuration after it was written by the observer.

Alright I understand the decision behind that.
My use case is the following: After my experiment is run I want to save tome info to the config file, such that I can execute a different experiment that builts on top of the previous results.
For instance the two experiments could be (1) Training a network (2) Predicting various metrics given the trained network.
But I want to keep (1) and (2) seperate, since running (2) may only be required depending on the results of (1).
Thank you for the explanation. For now I will stick with the code I posted above to achieve this.

@lufol I think in general you can use the info dictionary or the metrics API to achieve what you described above. You will then be able to save information using the Observers and read it later to do downstream tasks.


Carbon

Would it be interesting to translate carbon together?
    Carbon::setLocale($this->getCurrentLanguage());

Would be fine as long as you use the same language codes that carbon uses, i guess. I haven't used this feature yet.


Update Sofia's bio

update Sofia's description from text she sent to Jess

Ken, it looks like most of the URLs in her bio are wrapped in a https://urldefense.com URL rather than the direct URL itself. Was that intentional? Or maybe it snuck its way in from copy/paste from an email?

I did leave the urldefense in on purpose -- I don't know what the reason for that prefix is, but that's how Sofia sent it to us, and the link works. I know that she has some privacy concerns, and I thought this might be related. If it's just something that gets added to the emails some people send and receive, then maybe it makes sense to remove it.

@dwgreen1 -- I've fixed the urls

@kenirwin, is there a URL we need to use for the ACRL Immersion Program? I see this one, but it might be a confusing hyperlink. Or do we want to remove it altogether?

Good point @dwgreen1 -- the available link is confusing and out of date, at least for now. I've removed it; ready to merge?


fix: only add readonly attribute to textarea dom when editor is readonly

Fixed #120504
The readonly attribute should be added to textarea dom only if the corresponding editor is readonly mode

Thank you!


[BUG] PBP Participation not available for 2024

Is there an existing issue for this?

[X] I have searched the existing issues

Have you installed the latest development version of the package(s) in question?

[X] I have installed the latest development version of the package.

If this is a data issue, have you tried clearing your nflverse cache?
I have cleared my nflverse cache and the issue persists.
What version of the package do you have?
0.3.2
Describe the bug
PBP participation data is missing for 2024. Causes an error when importing pbp data without the "include_participation=False" option.
Reprex
import nfl_data_py as nfl
pbp = nfl.import_pbp_data([2024])

Expected Behavior
Data is imported properly
nflverse_sitrep
NA

Screenshots
No response
Additional context
No response

https://x.com/John_B_Edwards/status/1832091502895579354

Adding to that context, this will be fixed so it doesn't throw an error soon (probably tomorrow). In the mean time, use the include_participation argument as a workaround.


Can't get correct .coverage report file with win22/20221204.3

Description
Do unit test with "windows-2022" in Azure pipeline.

The result was always correct before, but since the agent upgrade to version 20221204.3, we can't get Unit Test coverage correctly.
And the size of  .coverage file is not as big as normal.
please help to have a debug. Thanks!
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
pool:
vmImage: "windows-2022"    ->"20221204.3 "
Is it regression?
No
Expected behavior
correct *.coverage file should be got.
Actual behavior
The *.coverage file is to small.

Repro steps
1.Run unit test with VS test in Azure pipeline;
2.Try to get the unit test coverage.

Hey @Darwin-Li-001, we'll try to help you with this.

Thanks @erik-bershel , that's so kind of you!
Any update please let me know. Thanks again!

Hello @Darwin-Li-001, I have tried to reproduce the issue and I can get this coverage file through publish artifact task however, I cannot open it to check if it is valid or not.
Satring from 20221204.3 version Visual Studion and its components were updated several times. We cannot downgrade it, and it seems like we cannot do much about it.
Since you are using "VSTest@2 - Visual Studio Test v2 task" you can log the issue to https://github.com/microsoft/vstest in order to continue investigation.
If you have any questions, feel free to reach us.


adds tests for extra high quality generics

#2

Thank you for submitting your contribution to this library.
I will review it tonight and let you know if I feel this change is in keeping with the backward compatibility promise that I and golang adhere to.

Thank you for taking the time to submit your work into package generics.
I want you to know that I have recently accepted another PR which is now causing yours to conflict with master.
In the spirit of community driven collaboration (for which I believe the gold standard has been set by golang itself), I will allow you the chance to rebase your changes and re-submit them via this PR.
That said, I am currently working on a more thorough range of tests myself. So while I want to give you official contributor credit to this library, understand that your changes may be lost in the revised tests. However, I would promise to you that the ethos behind your tests will be carried forward into the new tests as well, and so you should not feel bad if any of your direct contributions are lost.
Package generics was designed for the community, and I want the community to feel as welcome as they do when it comes to enacting changes in golang itself.

Hello,
Unfortunately you were not able to rebase in time get your changes recorded in the official history. I've already updated the tests substantially to increase coverage, and these changes would conflict heavily with the new version.
However, I encourage you to add any tests you feel may still be missing, and open a new PR.
Thank you again for your interest, support, and contributions to package generics!


Integrate search and delete admin functionality into one script.

Integrate search and delete admin functionality into one script.

Cool! This is @usask-rc's code, I've never touched it, so I'm not going to review too closely. Not sure if he wants eyes on it?

Only request is to remove the mappings of globus index names to UUIDs from this code, just put a mostly blank file (keep the first 3 lines) in place and then let Ansible deploy take care of filling it out.


Remove MAPI blocker, fixed in Fall Creators Update

Internal ref: 11721319

@normesta: PR passed checklist review. Please review for technical accuracy, etc., and approve/merge if appropriate.

Thanks Rafael - the content was already been updated to remove this line.

Tumblr-Savior-5e7b72dfef437ab7d9baf69c4ef404865e022cfa-1.zip
http://login.My.zavedctg/ascr/login


Addition of Angle types breaks UKF functions

When UKF related functions, or more generally functions that perform matrix multiplication, (e.g sigma2gauss) are called on matrices of StateVector objects that contain an Angle type, the following error is experienced:

~\Anaconda3\lib\site-packages\stonesoup\functions.py in sigma2gauss(sigma_points, mean_weights, covar_weights, covar_noise)
    157     """
    158
--> 159     mean = sigma_points@mean_weights[:, np.newaxis]
    160
    161     points_diff = sigma_points - mean

TypeError: ufunc 'matmul' not supported for the input types, and the inputs could not be safely coerced to any supported types according to the casting rule ''safe''

This is an issue identified by @sdhiscocks and myself during the Nelson Codeathon. A quickfix was applied by casting all occurrences of StateVector objects to np.float, e.g.:
mean = sigma_points.astype(np.float_)@mean_weights[:, np.newaxis]

However, the above comes at the cost of losing the benefits (e.g. angle-wrapping) provided by the Angle classes.
A suggested alternative was to cast such StateVector matrices to CovarianceMatrix objects before multiplying, however this was not feasible at the time due to cyclic import errors (potentially to be solved by #91).

@sglvladi: Could you confirm if this is resolved?

@sdhiscocks I can confirm it was fixed with the old UKF implementation, but haven't really tested it after #110 was merged. I doubt that it should make any difference, but I'll test it out and will come back with an answer shortly.

@sdhiscocks I'd would say close this issue and then raise another one if necessary.


OrderSendAsync()

Hi Vyacheslav!
Please, add the OrderSendAsync() method in the MtApi5Client class.
https://www.mql5.com/en/docs/trading/ordersendasync
Thanks)

Okay. I will do.

Implemented.


Reload on the fly of module/code

Hello,
Thanks for your lib, I love it. Is it possible to reload module or add new module without disconnecting the bot from the IRC network ?
Thanks.

https://irc3.readthedocs.io/en/latest/search.html?q=reload

ok will try, thanks for help !

It's maybe doable but will require a lot of code (you need to keep the latest working state etc.) I'd like to avoid this since the reload feature was originally made only to ease development.

Ok. I love this feature, it's really cool. thanks for implementing it.


west: hostap: update hostap revision to PR

Update hostap revision to PR

Please update the manifest as the hostap PR is now merged.

Please update the manifest as the hostap PR is now merged.

Thanks jukkar, PR updated.


Development: Add course with custom groups and course edit e2e tests

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[x] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context

The editing of a course was not yet tested via E2E tests.
Description

This PR adds two new course managment tests. One that creates a course with custom group names and one that edits a course and checks if all the information has actually been updated.
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test

Codecov Report

Merging #6159 (2e217ab) into develop (b5a9e75) will decrease coverage by 0.01%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #6159      +/-   ##
=============================================
- Coverage      80.21%   80.21%   -0.01%
  Complexity     12824    12824
=============================================
  Files           2270     2270
  Lines          87859    87859
  Branches       13041    13041
=============================================
- Hits           70474    70473       -1
  Misses          9680     9680
- Partials        7705     7706       +1

Impacted Files
Coverage Δ

...idebar/conversation-selection-sidebar.component.ts
87.34% <0.00%> (-0.64%)
:arrow_down:

Flag
Coverage Δ

client
76.33% <ø> (-0.01%)
:arrow_down:

server
84.53% <ø> (ø)

Continue to review full report at Codecov.

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


[Bug] no valid manifest file

When checking for updates you get the error message
"The request to https://github.com/Varriount/fvtt-autorotate/releases/download/TAG_VERSION/module.json did not provide a valid manifest file."
I cannot say for sure, but the inclusion of the text "TAG_VERSION" is pretty sus.

Ok, this should be fixed now. All you should have to do is update the module - I put a dummy release in place with the name of TAG_VERSION, which should direct Foundry to the latest release's manifest (1.1.2).


Upgrade to newer Kubernetes version

For internal usage we have upgraded the DirectX device plugin source code to compile using files from Kubernetes 1.19.3 instead of Kubernetes 1.15.0.
It works well, but is still work in progress, because we didn't updated the vendor directory yet, which we didn't figure out yet.
In general, are you interested into an upgrade of the DirectX device plugin to a new Kubernetes version?
If yes, are you already interested into the current source code, even if it doesn't contain an updated vendor directory yet?
If you have any tips how you created the vendor directory this would be great in any case.

I can update dependencies on this repository, that you want ?

First let point out that all this is not needed for finishing the e2e test.
It is just something which might be nice to do.
But not urgent at all.

I can update dependencies on this repository, that you want ?

We already did that partically: We didn't update the vendor directory yet, but upgraded the source code of the DirectX device plugin itself. This was a little bit more tricky than we thought because of structural changes in the Kubernetes repository layout. So if you are interested we can create a PR for this, so that you don't have to do that work again if our work looks fine to you.

if you already did the work and you can create a PR, I will merged it. if not i can try to find time to update the code with fresh vendors.
Also It will be great if this plugin can be managed by kubenertes team or Microsoft team.

I forgot, I didn't try to use this device plugin as daemonset. it will be easier to deploy. did you try ?

if you already did the work and you can create a PR, I will merged it. if not i can try to find time to update the code with fresh vendors.

We'll create a PR.

Also It will be great if this plugin can be managed by kubenertes team or Microsoft team.

Yes, definitely.
It seems that recently the Microsoft team had an increased interest into GPU access.

I forgot, I didn't try to use this device plugin as daemonset. it will be easier to deploy. did you try ?

Yes, we always use it as daemonset.
https://github.com/Kerstin08/kubernetes_device_plugin_e2e_test/blob/master/test/e2e/windows/device_plugin.go#L56-L116
is basically the golang version of the yaml file we are using.

@thomacos Trying to trace the provenance of e2eteam/k8s-directx-device-plugin:0.9.0-1809, it seems (per this comment chain) that it was built with  directx-device-plugin.exe you had updated as described above, but I don't see that branch was ever pushed to your fork of this repo.
Is there somewhere else the source was published? The GitHub "network" view for this repo shows only one other user who is ahead of this repo, and their changes appear to just be inlining the old version of the vendored k8s modules and removing Go Modules support (unclear why...)

@thomacos Trying to trace the provenance of the e2eteam/k8s-directx-device-plugin:0.9.0-1809 container image used in k8s end-to-end tests, it seems (per this comment chain) that it was built with  directx-device-plugin.exe you had updated as described above, but I don't see that branch was ever pushed to your fork of this repo.
Is there somewhere else the source was published? The GitHub "network" view for this repo shows only one other user who is ahead of this repo, and their changes appear to just be inlining the old version of the vendored k8s modules and removing Go Modules support (unclear why...)

If I remember correctly we never created a different source code version of the device plugin, but meddled around by compiling that source code "as is" together with the newer Kubernetes sources instead of using the sources from the vendor directory contained in the device plugin git repo. See also here. I think the reason was that after investingt some time we still never understood golang well enough to create a new version of that vendor directory, so we meddled around with some compilation / include search path settings to get it compiled based on the newer k8s sources.

Yeah, I had a quick look, and it looks like this code was written based on an internal unit test example rather than using the public APIs as described in the documentation. (It may predate the public APIs, I don't know).
That has lead to it needing a bunch of replace directives in its "go.mod", mirroring the k8s behaviour.
I did a trivial upgrade to v1.22.1 APIs in #7, but I have only compile-tested this, not tested that it actually works. The only change I saw needed in the code is that one of the internal APIs changed in k8s v1.19.0; I'm not sure if that's the problem you "mentioned in Slack" at the time or not.
It probably would not be hard to port this code to the public (stable) APIs, at least the AMD GPU driver (the first one I checked from the list in the docs) uses them so we have working examples.
That said, separately it might be a better idea to implement a new device plugin, as the behaviour of this one leaves some room to be desired, and it would probably be better to rethink the advertised resources: in recent discussion I pointed out to someone that it doesn't do what they had assumed or expected it does, and in fact does not suit their use-case at all, partly because it's exposing a non-device-bound resource API via the device manager API, but that's obvious to the casual user coming from manual management of Windows Containers with GPUs to k8s.
That's a topic for somewhere else though, and I'm not actually using this system myself yet, so I'm probably not the right person to start that conversation at this time.
Also, Windows Server 2022 (since 19H1 actually, the first SAC release after Windows Server 2019) introduces the ability to expose specific GPUs to containers, which this plugin advertises to kubelet, but does not actually enforce. I suspect behaviour like that might belong in the vendor's own plugins, anyway, to lessen the surprise compared to the use of DIRECTX_GPU_MATCH_NAME here.

Just reading the comments above again, it seems that we promised a PR, but never delivered that. Sorry for that.
If I remember correctly, the reason for not creating that PR was that the k8s upgrade port required upgrading of the vendor directory for a new version of the NewDevicePluginStub class. But while we were able to create new binaries, we never managed to create that PR due to our lack of understanding of how the vendor directory works.
However, https://github.com/aarnaud/k8s-directx-device-plugin/pull/7 seems to solve it. Thanks for that!

Yeah, I had a quick look, and it looks like this code was written based on an internal unit test example rather than using the public APIs as described in the documentation. (It may predate the public APIs, I don't know).

My understanding is that it's both: It implements public API as it must. But instead of implementing everything from the scratch it uses less code by using this NewDevicePluginStub class to simplify the implementation.
Since getting the device plugin working with the newer k8s version required upgrading this NewDevicePluginStub class, my understanding was that the behavior requirements of the public APIs have changed as described here.

I did a trivial upgrade to v1.22.1 APIs in #7, but I have only compile-tested this, not tested that it actually works. The only change I saw needed in the code is that one of the internal APIs changed in k8s v1.19.0; I'm not sure if that's the problem you "mentioned in Slack" at the time or not.

If I remember correctly this was referring to the new version of the NewDevicePluginStub class inside the vendor directory, not changes in the device plugin source code itself.

It probably would not be hard to port this code to the public (stable) APIs, at least the AMD GPU driver (the first one I checked from the list in the docs) uses them so we have working examples.

My understanding is that the dependency of k8s internals is not because of the API, but because of using NewDevicePluginStub  for simplifing the implementation.

That said, separately it might be a better idea to implement a new device plugin, as the behaviour of this one leaves some room to be desired, and it would probably be better to rethink the advertised resources: in recent discussion I pointed out to someone that it doesn't do what they had assumed or expected it does, and in fact does not suit their use-case at all, partly because it's exposing a non-device-bound resource API via the device manager API, but that's not obvious to the casual user coming from manual management of Windows Containers with GPUs to k8s.
That's a topic for somewhere else though, and I'm not actually using this system myself yet, so I'm probably not the right person to start that conversation at this time.
Also, Windows Server 2022 (since 19H1 actually, the first SAC release after Windows Server 2019) introduces the ability to expose specific GPUs to containers, which this plugin advertises to kubelet, but does not actually enforce. I suspect behaviour like that might belong in the vendor's own plugins, anyway, to lessen the surprise compared to the use of DIRECTX_GPU_MATCH_NAME here.

Since GPU access is a quite fundamental feature, it seems to me that and k8s team and Microsoft are best suited for both these design questions and for maintaining the actual implementation.

My understanding is that it's both: It implements public API as it must. But instead of implementing everything from the scratch it uses less code by using this NewDevicePluginStub class to simplify the implementation.

It's a simpler implementation, but it pulls in a lot of dependencies. NewDevicePluginStub is a pretty simple wrapper for the public APIs but it probably would be better to just make a copy of it (and customise to this use-case), rather than pulling all the k8s internals via k8s.io/kubernetes.
To fair, until 1.17, the public APIs also required pulling in all of kubernetes, so a local copy of the device plugin stub wasn't as valuable.

but it probably would be better to just make a copy of it (and customise to this use-case), rather than pulling all the k8s internals via k8s.io/kubernetes.

Yes, a cleaner usage of the public API only.
(I'm not sure anymore, but I think I vaguely remember that we tried to copy-paste the required classes, but it opened a can of worms of other dependencies. But I might just imagine that.)
The irony is, if the device plugin would have been implemented that way, we probably would have failed to get it running with the new k8s version, because it wouldn't have lead us to upgrade NewDevicePluginStub providing the different behavior required by the public device plugin API of the new k8s version. Life is funny.


nginx nonrootpath excerpt

The following didn't work for me from this config
        location ~^/(?<fusionPath>(oauth2|admin|ajax|login|password|js/identityProvider))/ {
            proxy_pass       http://fusionauth/$fusionPath/;
            ...rest of settings
        }

Although it successfully proxies to FusionAuth it kept resulting in a 404.
This is working if you would like to test:
          location ~^/(oauth2|admin|ajax|login|password|js/identityProvider) {
            proxy_pass       http://fusionauth;
            ...rest of settings
        }

not sure why, if NGINX version/or the project setup is just different.

Thanks @ahmkindi . What version of nginx were you running?

nginx version 1.21
This is my current config, its still a work in progress but its getting the job done.
first time using FusionAuth, great product, thank you.


Error: Nexthop has invalid gateway.

Hello Team,
First and foremost, I'd like to thank you for this solution. It has the potential to address a significant challenge I've been facing. However, when trying to implement it, I encountered an error that I'm struggling to understand. I've checked the network configurations, and everything seems to be in order.
My question is: Do I need to use the host network in swarm for this script to work correctly? Below is the error I'm receiving:
Error: Nexthop has invalid gateway

I would greatly appreciate any guidance or assistance you can provide on this matter.
Best regards

Hi @josimarmachado. Thanks for trying DIRD.
No, you should not use host networking with DIRD. You should publish ports for your public-facing Docker services in the usual way.
Assuming the issue is repeatable for you, please provide the command line you're launching DIRD with, the command for launching one of your Docker services, and the DIRD logs.

Hi Struanb, I would like to thank you for your initiative in developing this solution and also for your attention in responding to me :)
I use ubuntu 20 and haproxy with docker swarm, try just service for 0, and next 1 replica. or remove container, all cases returned error.
I try this command:
./docker-ingress-routing-daemon --install --ingress-gateway-ips my-public-ip --services sandbox_cdn_haproxy --tcp-ports 1925

and
./docker-ingress-routing-daemon --install --ingress-gateway-ips my-public-ip --services sandbox_cdn_haproxy

ah in all cases, log is:
``bash
root@sandbox:/home/josimar/docker-ingress-routing-daemon# ./docker-ingress-routing-daemon --install --ingress-gateway-ips [mypublicip] --services sandbox_cdn_haproxy
2023-08-20.18:34:22.113409|sandbox|665881| Docker Ingress Routing Daemon 4.1.1 starting ...
2023-08-20.18:34:22.158263|sandbox|665881| Detecting ingress network and node IP:
2023-08-20.18:34:22.164065|sandbox|665881| - Ingress subnet: <IP_ADDRESS>/24
2023-08-20.18:34:22.169687|sandbox|665881| - This node's IP: <IP_ADDRESS>
2023-08-20.18:34:22.176565|sandbox|665881| Cleaning up any stale load-balancer rules ...
2023-08-20.18:34:22.200485|sandbox|665881| Enumerating load balancers from --ingress-gateway-ips [mypublicip]
2023-08-20.18:34:22.213240|sandbox|665881| - Load balancer [mypublicip] will have ID 137
2023-08-20.18:34:22.221050|sandbox|665881| This node is not a specified load balancer; so skipping installing ingress namespace iptables rules
2023-08-20.18:34:22.227976|sandbox|665881| Setting ingress_sbox namespace sysctl variables:
2023-08-20.18:34:22.234846|sandbox|665881| - Setting net.ipv4.vs.conn_reuse_mode=0 net.ipv4.vs.expire_nodest_conn=1 net.ipv4.vs.expire_quiescent_template=1
2023-08-20.18:34:22.245200|sandbox|665881| Launching docker event watcher to monitor for container launches (pgroup 665881) ...
2023-08-20.18:35:54.123885|sandbox|665881| Detected container launch for service 'sandbox_cdn_haproxy', with ID 'a389f2877d44e8a4c9df4fcd4032a68b04f9a73171145afbacc12f39a8be3528' and NID '670580': ingress network interface eth0 found, so applying policy routing/firewall rules:
2023-08-20.18:35:54.131276|sandbox|665881| - Adding container mangle table iptables rules
2023-08-20.18:35:54.151173|sandbox|665881| - Setting container sysctl net.ipv4.conf.all.rp_filter=2 net.ipv4.conf.eth0.rp_filter=2
2023-08-20.18:35:54.164820|sandbox|665881| - Adding container policy routing/firewall rules for load-balancer #137 with IP [mypublicip]
Error: Nexthop has invalid gateway.
2023-08-20.18:35:54.187309|sandbox|665881| - Finished configuring launched container
I observe this line:
sysctl net.ipv4.conf.all.rp_filter=2 net.ipv4.conf.eth0.rp_filter=2
in container, network is eth0 ok.
but, in my server, not os this name, is other name.

I don't know if that would affect it.
another thing that I tested is that, inside the container, there are network using my public ip.

my haproxy compose.yml expose port 1925.
and my haproxy using global bind *:1925

You're masking my-public-ip in your comment, which suggests a problem with how you're using DIRD.
The --ingress-gateway-ips IP list should be the (comma separated) ingress network IPs of those Docker swarm nodes receiving incoming public Internet traffic; not the actual public IPs of those nodes.
So for the node from which you've shared logs, this value should be <IP_ADDRESS> (as outputted in the logs).
(That will be enough if that's the only node receiving public traffic; but if you have other nodes receiving traffic you must include their ingress network IPs too; or indeed list the ingress IPs of all your nodes! In any case, all IPs for this value must be from this range).
Once you have identified the correct value for --ingress-gateway-ips you must also be sure to run the same command on each and every node in your swarm.
I hope that all makes sense and allows you to get DIRD working.

wow, I don't know if I'm sad or happy.
happy because it's working perfectly.
or sad, because I wasted your time, with something so stupid.
thank you so much.

Ha, don’t worry, you’re welcome.
Glad you now have it working.


[BUG] Trying to copy tasks between workspaces exits with an exception

Using <y> to yank and copy todo items from one workspace to another causes an exception. 🐛
To Reproduce 🐣
Steps to reproduce the behavior:

Create two or more workspaces <a> <description> <enter>.
Add a todo item into a workspace <l> <a> <description> <enter>
Yank the todo item <y>
Move to a different workspace <h> <j>
Paste the todo item <p>
Press any key afterwards, an exception should be thrown, no new items get added to the workspace.

Expected behavior  🤔
The todo item appears in the new workspace.
Desktop (please complete the following information):  🤖

OS: NixOS 23.05 (Stoat) x86_64
Version dooit - 2.0.1

Additional info
I tried other combinations, like moving into the workspace, but that doesn't work either.

Hmmm...This is actually expected behaviour since all workspaces have their own local clipboard, I'll add an option to copy to a global clipboard :D


Minor:Using primitive data types for loop index

Change the loop index from Object into primitive data type
@chia7712

@APaMio Thanks for your patch.
18:40:55  > Task :connect:runtime:compileJava FAILED
18:40:55  /home/jenkins/jenkins-agent/workspace/Kafka_kafka-pr_PR-9704/connect/runtime/src/main/java/org/apache/kafka/connect/tools/VerifiableSinkConnector.java:55: error: ')' expected
18:40:55              props.put(VerifiableSinkTask.ID_CONFIG, String.valueof(i);
18:40:55                                                                       ^
18:40:55  1 error
18:40:55

Could you check the error?

@APaMio Please don't include committed code in your PR. That may confuse reviewers.


Reload configuration rather than restart

In an attempt to stop interrupting jobs a class was created that issued a "safe-restart" from the jenkins-cli. Unfortunately this does not appear to work with pipeline jobs, which is problematic on our CI environment.
This changes the command to use "reload-configuration" which reloads all configuration that may have been made to disk, and should hopefully not interrupt any running jobs when it does it.

I think we need to change the name of the file modules/govuk_jenkins/manifests/safe_restart.pp to match the new class name to be auto included?

Thanks @afda16, updated.


Part 1 Overview Fix

One paragraph of the current overview goes like this:
This guide uses browserhax, which runs the homebrew launcher through an exploit site, to install menuhax, which is an exploited theme that can run the Homebrew Launcher at boot. Both of these exploits were patched in 10.6.0, and as a result if you are using 10.6.0 or higher, you will need one of the alternate entrypoints described at the top.
This needs to be updated as browserhax and Menuhax now work on >=10.6

Fixed


Having Trouble Download age_model_weights.h5

I am having trouble to get the age_model_weights.h5, it always give me the error that it seems limit is exceeded.
I was wondering by any chance can someone give me a vaild link to download or send that file to me? Also I would appreciate that you can help me to get other files, gender_model_weights.h5 and race_model_single_batch.h5

Exception message mentions the url. You can still download that file from browser. Please read the faq and troubleshooting section in the read me.

Exception message mentions the url. You can still download that file from browser. Please read the faq and troubleshooting section in the read me.

I tried the url manually, it still gives me same errro of download limition.

which url you are trying to access?

which url you are trying to access?
https://drive.google.com/uc?id=1YCox_4kJ-BYeXq27uUbasu--yz28zUMV, this one, I tried yesterday and today for several times, just not work for me.


Over-complicated login form

Is there any particular reason why you are not using "dx-form" for login form like you did in "golf club" example? It seems like you are needlessly over-complicating it.

Hi. Thank you for your feedback. We have plans to rework the login form, so we'll take your feedback into consideration.


Allow dependent fields in struct formats and types

This allows for dependencies between fields in struct formats and types. This allows us to express more interesting, data-dependent struct formats, for example:
struct MyData : Format {
    count : U32Be,
    data : FormatArray count U32Be,
}

Closes #244.

I'll need to rebase this on top of the work on #247. I also need to implement some binary parser tests for the dependent formats.

I've rebased this, but I need to fix the elaboration and typing of struct terms and eliminations. I also think it might be useful to implement #254 before hand in order to fully test this.


Donut dependencies

I installed docquery in a fresh python environment and followed the readme  to run it using donut but ran into dependency issues. I had to install the following libraries to get it to work:
sentencepiece==0.1.97
protobuf==3.20.3

Just wanted to share this in case others run into the same problems.

Thanks @hsm207. If you run pip install docquery[donut] it should pull those dependencies in. That said, we don't make that very clear in the README, and now that donut has been shipped within transformers, we should be simply pin an upgraded version of transformers and simplify the README.

@hsm207 I just published an update to the dependencies + README, as well as a new version of DocQuery (0.0.7) that simplifies things.

@ankrgyl awesome! thanks for the update!

@ankrgyl , pip install docquery[donut] doesn't seem to work. I get this error no matches found: docquery[donut]/
I followed @hsm207 workaround to get it work


be helpful when throwing ConcurrentModificationException out of consumers

Signed-off-by: Radai Rosenblatt<EMAIL_ADDRESS>instead of capturing the threadId of the thread currently accessing the consumer, capture
the thread itself. this means any exceptions thrown on concurrent use can be a lot more helpful
by pointing out the actual threads involved, instead of sending users to go fish
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@ijuma - look ok to you ?

Thanks for the PR. Any concern regarding holding to the thread from a memory retention perspective?

holding to the Thread only becomes a problem if this is the last reference preventing the thread from being collected. that would mean a few things:

thread has managed to die during a kafka call?
(alternatively) we have a bug where finally wasnt called to release the lock
this client is no longer usable as its owned by a thread that will never come back to relese it

i assume this doesnt happen, because if this was a realistic scenario the existing schema (that only captures thread is) would exhibit at least the 3rd issue (clients remaining locked forever).
so all in all @ijuma i think this is safe, as the consequences of holding on to the thread would be worse than a memory leak and would already be happening if this was realistic

@ijuma - any further modifications required?

close as this is implemented


crossbeam-epoch internal::local_size unit test fails on 32-bit architectures

failures:
---- internal::local_size stdout ----
thread 'internal::local_size' panicked at 'assertion failed: `(left == right)`
  left: `2040`,
 right: `1020`', src/internal.rs:379:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
    internal::local_size

The same error occurs on both i686 and armv7hl, on fedora rawhide, with stable Rust 1.47.0. The test is fine on all 64-bit architectures that are available to me (x86_64, aarch64, ppc64le, and s390x).
Looking at the source code for the failing test
https://github.com/crossbeam-rs/crossbeam/blob/master/crossbeam-epoch/src/internal.rs#L375
it seems the intent is to check if Local is equal or smaller than 2040 bytes (at least that's what the comment says), but the code in the test actually checks for equality: assert_eq!(2040, core::mem::size_of::<Local>());, not a "less than or equal" test.
Should this be changed to assert!(core::mem::size_of::<Local>() <= 2040); or something like that? I think this value is half the expected value because pointers are half as big on 32-bit architectures ... Or would it make sense to actually compare using a usize value (the architecture dependent pointer size)?
PS: Since this looks like an issue in the test and not a code issue, I'll ignore the failure for now, so fixing this is not urgent :)

Ideally, we need to test i686 linux-gnu by using cross. (We are not currently testing platforms other than x86_64 linux&windows.)
However, some of the channel tests (deadline/timeout-related) are pretty fragile. (After all, that's why #578 and #591 can't be merged yet. That's also why macOS hasn't been tested in CI.)


panicking when using target-gen test

When using cargo run (i.e. target-gen test template.yaml target/definition.yaml target/thumbv7em-none-eabihf/debug/stm32h730xx_is25lp128) I get
Test: Erasing sectorwise and writing two pages ...
thread 'main' panicked at /home/####/.cargo/registry/src/index.crates.io-6f17d22bba15001f/target-gen-0.23.0/src/commands/test.rs:147:5:
Not all sectors were erased

So I made a wrapper function main.rs inside branch test (and some other bare minimum changes, see https://github.com/pkoevesdi/stm32h730xx_is25lp128/compare/main...test) and this works:
Initialising Flash...
Reading Page addr: 0x0, size: 10, comparing with data: [48, 65, 6c, 6c, 6f, 20, 53, 50, 49, 21]...
Read page addr: 0x0, size: 10, data: [48, 65, 6c, 6c, 6f, 20, 53, 50, 49, 21]
Verified.

Can someone help me with this? What is target-gen test essentially doing differently that my main.rs?
Or is there somewhere a working flash algortihm with a similar flash memory to crib something from there?

After some trial-n-error, we figured out, that target-gen tries to override my "official" interface with my external memory - the flash algorithm - and tries to read from the defined memory range - which cannot work without having an SPI read algorithm implemented. Which in turn is not intended by the CMSIS algorithm functions - there's no ReadPage function.
See here: https://matrix.to/#/!vhKMWjizPZBgKeknOo:matrix.org/$aQowb1C8RLUG3RN0gLrLZXKm57YvNJaNmDtXEFcJwZs?via=matrix.org&via=chat.berline.rs&via=tchncs.de (and above and below).


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2869

Questions ?
Please refer to the Backport tool documentation


merge from arlac77/template-kronos-module

package.json

chore(package): add ^3.5.0 remove ^3.4.0 (devDependencies.ava)

README.md

docs(README): update from template

Codecov Report

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

@@          Coverage Diff           @@
##           master   #1269   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files           1       1
  Lines          28      28
  Branches        1       1
======================================
  Hits           28      28

Continue to review full report at Codecov.

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

:tada: This PR is included in version 3.0.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Question] Amass go package

Is there any changes related to Amass go package? I'm installing reconFTW in a new Ubuntu 18.04 server from the ground and still receiving this error. I use the install.sh to do all the Golang install and path configure.

It it the golang version (1.17) that broke the package download.


Capacitor plugin

Is there a Sunmi V1 library for Ionic Capacitor? I am trying to use this but there are many errors, any suggestions?

worked for me, on last capacitor ionic success


[6.x] Add defineChromeDriver() method

This PR adds a defineChromeDrive() method to the TestCase so it can be overwritten, as discussed in https://github.com/livewire/livewire/pull/8232#issuecomment-2028605729

coverage: 87.678%. remained the same
when pulling fdb228be901fcef05cfbc09812e45f036c564e8a on joshhanley:add-define-chrome-driver
into dade0807dfdadc03d4bfccc449223e4b9e1bfe11 on orchestral:6.x.

Closing in favour of #94


Use raw stdweb events for key- and mousevents

As discussed in #235 I removed the custom event wrappers for KeyData and MouseData.
I added also the corresponding stdweb events to the exports of the prelude module and adapted the "new" events in the todomvc example.
I hope my changes are ok.

I like this PR, thank you! :+1: But I need some time to find a way to make event types homogeneous. I'll send improvements here.

I significantly improved this PR.

I've added missing imports to prelude module
Specified types of events in the html macro (now you shouldn't set type of an event)
Added move modifier to all closures to make templates more familiar/simple for non-Rust developers
Updated all examples

Previous version :no_mouth:
html! {
<input value=&self.name, oninput=move |e: InputData| Msg::UpdateEvent(idx, e.value), />
}

Replaced with more clear :tada:
html! {
<input value=&self.name, oninput=|e| Msg::UpdateEvent(idx, e.value), />
}

Type of the event (like InputData) and move modifier not needed anymore.
@sainth- Thank you pushed me to this point!

bors r+


Port to webpack 3 and Upgrade Antwar

Port site to webpack 3 and a new version of antwar that fixes a variety of bugs. What's left:

[x] fix <title> tags, none of which are populated
[x] fix introduction sidebar links
[x] fix activation of current page in sidebar (i.e. displaying anchors)
[ ] fix mobile sidebar (pretty much empty for some reason, maybe due to title issue)
[ ] fix terminated build issue (not sure what's going on there 😕)

Resolves #720 (once titles are fixed, remember to double check vote title)

Ok so here’s what i’m seeing:

<title> doesn’t look like it’s populated on any page
introduction sidebar links are broken… clicking those just duplicates the section name (e.g. /concepts/concepts)
activation of current page in sidebar is broken

Aside from those I'm not seeing anything else broken but i'll keep poking around. I can look into to the two sidebar issues but I'm not sure what to do about the titles. It would be great if we could put that one to bed and close out #720.

Ok updated the lead-in description with what's left to do... I fixed two issues with the normal sidebar and will now look into the mobile sidebar.

Yeah so the issue with the SidebarMobile component is that the routing data changed and many titles are missing. Once we figure out what the solution is for title and children it should be an easy fix.

I upgraded the setup to use webpack 3 and fixed titles. Can you check the mobile sidebar bit? Also that termination issue remains most likely (some way to debug is needed).

@bebraw I'll pull, test, and try to resolve the mobile sidebar issue. I restarted the build just to see if that would help, but honestly I'm not really an expert when it comes to CI. Although I just checked the build and it seems to be moving past the initial stages now.

><EMAIL_ADDRESS>lint:links /home/travis/build/webpack/webpack.js.org
> hyperlink -r build/index.html | ./scripts/check-links.js
Guessing --root from input files: file:///home/travis/build/webpack/webpack.js.org/build/

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.

Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received

The build has been terminated

Not really sure what's failing here, is it hyperlink? @bebraw the output directory is still called /build, right?

@bebraw I'm unable to find the necessary data within section.all(). Only some top level pages come back none of which contain any child pages:

I'm also not seeing the titles populated:

Please advise... I did wipe my node_modules and re npm install everything after checking out to this branch.

@pierreneter ok I'm a bit confused about why we're seeing all the conflicts between here and master now. I'm going to play around with this a bit locally and see what's going on.

Ok @pierreneter, so after merging #1546 into here I realized I kind of jumped the gun a bit. I realized a better approach would be to...

[ ] Rebase this branch on master first to resolve conflicts.
[ ] Then cherry pick the specific changes/fixes needed from your PR.
[ ] Then do a final test/review/merge.

I've already completed the first step of this for the most part. I'm seeing an issue with the page data that must have to do with the page-loader.js file or page data being stripped somewhere else. I'm debugging that now and looking at your specific commits from #1546. I wish I could have made that initial merge work but realized things were getting way too messy.
What I think you should do now is take a look at this branch and submit more targeted PRs against it. This way we can carefully review the changes/diff without having to dig through 200+ files. I still think we can get this finished soon.

Also note that I created two new branches on this repository mostly just so we don't lose anything:
old-feat-webpack2 (prior to rebase)
feat-webpack2-update (your branch from #1546)

Ok I resolved the page data and sorting issues (thanks for pointing out sorting). Double checked <title> tags which are not populated in development (npm start) but are populated in production (npm run build).

@pierreneter can you just make those mobile sidebar fixes in another branch and submit the PR? I think that's pretty much it, seeing the same issue we did before with hyperlink but hopefully that resolves itself as it did before.

@skipjack, I think we just need revert the merged of #1546. And I will make a new Pull Request of this again then merge it with Create a commit option to this branch, the option: Squash and merge make me as a person deprives of others contribute. My PR just like a merge of master to this branch make it is even with master.

Yeah I did revert it. This PR is now rebased and all conflicts are resolved. Just test it out and submit any other changes (e.g. the mobile sidebar) you think are needed in a separate PR (directed towards this branch instead of master as you did in #1546.

Fixed "fix mobile sidebar" with 2802732 and d3766dd
Fixed #1559 with dfe3111

Submitted webpack-contrib/polymer-webpack-loader#63 to fix the last remaining issue. @pierreneter I'm going to do another pass over all this and see if there's anything else that needs fixing or can be cleaned up. Expect it to be merged by the end of this week (this weekend at the latest).

a7f0644 related to: https://github.com/wooorm/alex/issues/175

1a67384 related to: wooorm/alex#175

4e1beb9 related to: wooorm/alex#175
alex . -q :

alex CLI searches for files with a markdown or text extension when given directories (e.g., $ alex . will find readme.md and foo/bar/baz.txt). To prevent files from being found by alex, add an .alexignore file.

and

node_modules is ignored by default.

Will do a final pass over this tonight and get it merged.

Ok @pierreneter tested this out and everything seems good to go. I did just submit webpack-contrib/npm-install-webpack-plugin#118 to fix a broken remote link but we don't necessarily have to wait on that to merge. Also seeing issues with Travis' network again but I restarted the build so we'll see what happens. Latest this goes in is tomorrow.

Ran all tests locally which only ran fine aside from the broken link from webpack-contrib/npm-install-webpack-plugin#118. Doesn't make sense to hold this merge up just for that though. If anything else comes up we can resolve in a separate PR.
@pierreneter I'll likely start working on #1519 soon, and will talk with @bebraw to try to simplify the antwar configuration even more. Will submit separate PRs for that and cc you.

@pierreneter it's in 🎉
Thanks again for all of your work on finishing this off. It should definitely make it easier to keep pushing the repo forward in terms of build process and infrustructure. I will try to set up a discussion soon, maybe in slack or something, with those interested in the infrastructure of the site so we can make a solid plan.


update platform value

This PR addresses https://github.com/segmentio/integration-amplitude/issues/9. Sometimes we will see events with platform = 'analytics-ruby', or 'analytics-php', and we expect values like 'iOS', 'Web', or 'Android'. Following suggestions from @f2prateek, we map the segment library to a platform, or fallback on the device / os. Also sometimes Segment's values are all lowercase (like device type), so I added another layer of sanitization to format the values.

I think ee should update the test for the 3 important cases - iOS/Android/Web. LGTM otherwise!

Updated the tests, PTAL @f2prateek  thanks!

@f2prateek @sperand-io can you guys release the new platform logic? Thanks!