Quoting the collector parameter ignored-mount-points produces unwanted results

What happened?
Setting the filesystem collector parameter ignored-mount-points puts the value in quotes to the service file,
which is fed verbatimly into regexp parser and makes the expression "useless".
Is there some way to work around this obstacle?
(detailed description below)
Did you expect to see some different?
As per these two node exporter issues quoting the regexp in service file is a wrong thing to do:
https://github.com/prometheus/node_exporter/issues/911#issuecomment-429712534
https://github.com/prometheus/node_exporter/issues/1000#issuecomment-583202422
How to reproduce it (as minimally and precisely as possible):
Use the example from the defaults/main.yml file:
node_exporter_enabled_collectors:
- filesystem:
    ignored-mount-points: "^/(sys|proc|dev)($|/)"

Produces the .service file with execstart line:
ExecStart=/usr/local/bin/node_exporter \
--collector.textfile \
    --collector.textfile.directory=/opt/prometheus_data \
--collector.filesystem \
    --collector.filesystem.ignored-mount-points='^/(sys|proc|dev)($|/)' \
    --web.listen-address=<IP_ADDRESS>:9100

Result:
# curl -s localhost:9100/metrics|grep 'mountpoint="/sys'
node_filesystem_avail_bytes{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 9.0760503296e+10
node_filesystem_device_error{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 0
node_filesystem_files{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 2.2158326e+07
node_filesystem_files_free{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 2.215831e+07
node_filesystem_free_bytes{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 9.0760503296e+10
node_filesystem_readonly{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 1
node_filesystem_size_bytes{device="tmpfs",fstype="tmpfs",mountpoint="/sys/fs/cgroup"} 9.0760503296e+10

If the quotes are manually removed from the switch line:
--collector.filesystem.ignored-mount-points=^/(sys|proc|dev)($|/) \

then the result is as expected (mountpoint is ignored):
# systemctl daemon-reload
# systemctl restart node_exporter.service
# curl -s localhost:9100/metrics|grep 'mountpoint="/sys'
#

Role version:
version: 0.21.5

Ansible version information:

ansible --version
ansible 2.8.2
  config file = /root/src/clip-hpc/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /root/src/clip-hpc-venv/lib/python3.6/site-packages/ansible
  executable location = /root/src/clip-hpc-venv/bin/ansible
  python version = 3.6.8 (default, Dec  5 2019, 15:45:45) [GCC 8.3.1 20191121 (Red Hat 8.3.1-5)]

Seems like a fix would be to always quote with double quotes and not single ones. Unquoted regex can also lead to unexpected issues as mentioned in https://github.com/cloudalchemy/ansible-node-exporter/pull/144

This role has been deprecated in favor of a the prometheus-community/ansible collection.


[DOC] Discuss tuning spark.task.resource.gpu.amount in tuning guide

The tuning guide does not mention how to tune the spark.task.resource.gpu.amount setting when Spark is scheduling GPUs.  If this is left at the default of 1 then only 1 task per executor will run, likely wasting CPU cores and leading to suboptimal performance for parts of the query that are not GPU-bound.  For example, setting spark.rapids.sql.concurrentGpuTasks to 2 makes no sense if spark.task.resource.gpu.amount is 1, as only 1 task will ever run concurrently in the executor due to the GPU resource limit.

When updating the tuning guide as part of this PR, we should also update existing documentation with examples using spark.task.resource.gpu.amount=1, either explicitly or via the default, to mention that this is probably a suboptimal setup and point to the relevant section of the tuning guide.

note we have some info here about this, but we should tie everything together: https://nvidia.github.io/spark-rapids/Getting-Started/#spark-gpu-scheduling-overview


Fibonacci algorithm

An algorithm to find the nth number in the fibonacci’s sequence

Thanks for the PR!


Cursor Position not calculating as expected when using comptext widget

Hello,
I I have found a bug with the cursor position that I am unable to fix. When housing an <$edit-comptext> widget inside of any HTML table, the popup element to select the desired option is rendering in the corner of the tiddler. This can be replicated with the below code:
<$list filter="[{!!title}addprefix[test]]">

<$edit-comptext field="leader" placeholder="Leader of this org" />

</$list>

Unclear as to what the solution here would be. Thanks for the good work, this plugin is still one of my favorites :)

Hello. Ok.....
Hmm, first I am not very fluent with the TW widgets by themselves (the <$things...>). So, I have copied your twtext inside a TW (version 5.1.11) and indeed, I get a tiddler with an input field where the popup behave "strangely".
But, when I look at the DOM, in a "regular" Tiddler, in edit mode, the editor is a
<textarea class="tc-edit-texteditor" style="height: 100px;">text</textarea>
whereas in using your example, the input element of the tiddler is a
<input type="text">
So I do not know what is exactly behind the <$edit-comptext ... /> tw_widget, but it does not behave as a "classical tiddler editor". Besides, INPUT element is very different from TEXTAREA (one line max vs multilines)...
To be sure that I did things right, here is a snapshot of a tiddler Bug2 with the code you gave me. Is this correct ?

The module to compute the caret position (that I did not write) works like this : it create a dummy textarea, set it to the same style than the original textarea (of the editor), paste the current text in it and, from the size of this dummu one-line textarea, deduce the actuai position of the carret in the original textarea.
With an input elements, I do not know what happens...

Hey, thanks for checking this. Let me show what this looks like in preview mode with screenshots. I am somewhat ignorant of how the widgets work specifically, but as I understand the plugin generates the ability to use $edit-comptext as opposed to $edit-text which is the normal mode of editing.
the issue only occurs when the widget is wrapped in an HTML attribute, like a table. See the below.
In this image, you can see the HTML table (top) editing the field is causing the placement of the input box to appear in the top left corner.

Without the HTML attribute wrapping, the cursor position calculates as expected:

I may have a friend who is more JS literate than I check to see if he can sus why the element is calculating incorrectly as well. Here's the code snippet:
<$list filter="[{!!title}addprefix[test]]">

<$edit-comptext field="field-1" placeholder="field 1" />

</$list>
<$list filter="[{!!title}addprefix[test]]">
<$edit-comptext field="field-2" placeholder="field 2" />
</$list>

@RK-Shaw Try giving your table position:relative (via class + CSS or inline style)

@saqimtiaz : thanks for the tip. Works great
If I use the following code, it works
<$list filter="[{!!title}addprefix[test]]">

<$edit-comptext field="field-1" placeholder="field 1" />

</$list>
<$list filter="[{!!title}addprefix[test]]">
<$edit-comptext field="field-2" placeholder="field 2" />
</$list>

If I understand properly, the reason for this is that the popup element has position:absolute and so needs an "anchor" to position itself. And adding the position:relative to the table element makes it a proper anchor. Nice.
(I have so much to learn....)

awesome! that works as stated, time to go about applying that element to my various table classes in my stylesheet!
Cheers,
-RKS


ci: use pnpm

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Can't replace a static method without compromising strict standards or doing runkit_import()

Hi all,
It would be great if runkit could replace a static methods the same way it replaces the non-static ones.
Right now replacing a static method with runkit_function_redefine() makes it non-static, so calling it later as a static generates a Strict Standards warning.
The only way I found to replace a static method (and keep it a static) is to do runkit_import() with RUNKIT_IMPORT_OVERRIDE flag to replace the original method.
Also, the behaviour of runkit_function_redefine() with static methods is not documented - I think it should!

This ticket can be closed, as the PHP manual has already been improved in this regard.

Thanks, @cmb69. I forgot about that :)


feat(wasi-threads): improve thread id allocator to reuse identifiers

At the moment, when created, a thread receives an incremental number as an identifier.
This PR allows reusing thread ids once they are released. That is done by using a stack data structure to keep track of the used ids.
When a thread is created, it takes an available identifier from the stack. When the thread exits, it returns the id to the stack of available identifiers.

I'm doing some additional refactoring to have both pos and size as unsigned so that comparisons are safe. I just need to get pos to point to the first empty position in the stack rather than at the top element.


npm start not working

npm start not working and getting following errors:

<EMAIL_ADDRESS>prestart C:\quickstart\quickstart-master
npm run build
<EMAIL_ADDRESS>build C:\quickstart\quickstart-master
tsc -p src/
<EMAIL_ADDRESS>start C:\quickstart\quickstart-master
concurrently "npm run build:watch" "npm run serve"
Error occured when executing command: npm run serve
Error: spawn cmd.exe ENOENT
at exports._errnoException (util.js:1018:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:367:16)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:393:7)
at startup (bootstrap_node.js:150:9)
at bootstrap_node.js:508:3
Error occured when executing command: npm run serve
Error: spawn cmd.exe ENOENT
at exports._errnoException (util.js:1018:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:367:16)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:393:7)
at startup (bootstrap_node.js:150:9)
at bootstrap_node.js:508:3
[1] npm run serve exited with code -4058

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'concurrently "npm
run build:watch" "npm run serve"'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the angular-quickstart pa
ckage,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     concurrently "npm run build:watch" "npm run serve"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular-quickstart
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular-quickstart
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\quickstart\quickstart-master\npm-debug.log
solutions will be appreciated.

issue has been moved to #16237


Fix Byte Order Mark (BOM) handling in markdown display and editor.

Gitea version (or commit ref): <= 1.8.0
Operating system: All.
Database (use [x]): All.
Can you reproduce the bug at https://try.gitea.io:

[X] Yes (provide example URL) - https://try.gitea.io/emonk/Markdown-BOM-Test
[ ] No
[ ] Not relevant

Description
When the README.md file contains a Unicode Byte Order Mark the file the first line of the file is
formatted incorrectly.  This happens for all BOMs that I have tested - UTF8, Unicode and Unicode
Big Endian.  The text of the file loads correctly in all cases, the only problem is with the BOM
being treated as file content and incorrectly displayed in both the rendered view and the editor.
This is a particular problem for developers using Visual Studio and other environments which
insert a BOM by default, and can be difficult to change without add-ons to the environment.
The various Unicode Byte Order Markers are metadata and should not be treated as file content.  At a minimum the markdown renderer should detect and discard BOMs in the content.  The markdown editor should likewise detect and remove BOMs during load and either replace them during save or save without markers.
I don't understand Go so I won't be submitting a pull request.  From 10 minutes casting about in the code it looks like ToUTF8WithErr and ToUTF8WithFallback might be a place to
start.  It looks like those are the main methods used to massage text file content into UTF8 for
both render and edit.
Screenshots
Screenshots taken from try.gitea.io site mentioned above.

Bad first line formatting, treats BOM as unknown non-printable character:

Editor showing BOM as unknown/bad character:

Would be interested in how GitHub solves this (or not). Generally, I think all BOMs should be abolished, but I guess the broken software might behave differently (cough Excel), so there might be some value in preserving the BOM if present (but never rendering it).

It's probably through some use of the chardet or similar.
It's probably reasonable to pass the stuff through this - but the trouble with the chardet library is that it's not nearly perfect.

BOM should be easily detectable via regex \uFEFF, no need for a library.

Ah but I bet that the next problem will be cp1252 related

Please do not use regexp for this, just check first two bytes

BOM is actually three bytes in UTF-8 and two bytes in UTF-16. Still think it's best to regex-test the unicode string instead like ^\uFEFF.

It does not matter it still be faster than doing regexp and converting byte array to string

OK so we are passing this content through a chardet.
OK so we need to adjust our "decoder" for utf-8 to simply remove the BOM if present.

I think the most elegant solution would be:

Strip BOM from rendered markdown and web editor.
When user saves a file in the web editor check if the previous file had a BOM and preserve it.

As I said, BOM preserval is important when dealing with certain Microsoft products which use the BOM as indicator wether a file is UTF-8 or ASCII, like Excel does.

@silverwind - OK I've got removal of the BOM on decoding sorted out. In terms of keeping the previous encoding that's a bit more difficult - we don't currently do that at all - all data created on the editor is assumed to be UTF-8 AFAIU (I certainly didn't write any encoding gadgets - doing it properly is a horrible experience.)

We're making the assumption that everything is UTF-8 so adding it back when committing from the UI shouldn't be too hard. Read the old file, check if its first three bytes match (maybe create a shared hasBOM function to use in the template renderer as well) and if they do, add them to the saved content.
Thought I won't block on this, stripping BOM is already an improvement.

OK done.

The attached pr will attempt to reencode to the detected charset and upon failure will default to utf8 with or without BOM as per original charset.

Thanks, will likely test this tomorrow.


Reimplement 4+ ping restrictions/Implement better raid mitigations

In the wake of recent raids on the r/jailbreak server, I propose for the 4+ ping limit per message be reimplemented, or for better raid mitigations (instant lockdown of the server via a command, raid protection mode that locks whitenames out of the server or requires additional verification to write) to be implemented. I'm not an expert python developer, but I'd be willing to look into it if no other contributors have time for this.

Good suggestions. I'll work on this.

If you want another idea maybe check this bot out and it's antiraid system: https://github.com/zekroTJA/shinpuru#antiraid
it works with a nice system which allows only a few users to join and interact per a specific interval


Remove travis and appveyor CI config

Please confirm that this PR has done the following:

[x] Description in RELEASE_NOTES.md Added

Description of PR
This PR:

[x] Removes the configuration files for travis and appveyor.
[x] Badges on the docs pages have been updated (see latest on RTD).
[x] integration with travis and appveyor has been deactivated.

Could not review pull request. It may be too large, or contain no reviewable changes.

@gidden, can you check whether there are any other files or settings that can be removed as part of the migration to GitHub Actions and codecov? thanks!

@znicholls - this would remove files required for the make commands (namely environment files). we were using make test etc on our various CIs, but now this is not needed for github actions.
I think we have three options:

remove also the Makefile on which this depends
keep the environment files
use make in the github actions

I would prefer 1 or 3, as otherwise things will get out of sync. Other preferences?

Having done this a few times now (see eg github.com/openscm/scmdata or github.com/openscm/openscm-twolayermodel), I’d go for 1. The ultimate source of truth is the CI. The Makefile is a pure convenience but I don’t think you or @danielhuppmann use it so there’s no point keeping it. If I get back into serious development I’ll add it back in but there’s no point having it unless it’s useful.

thanks @gidden & @znicholls for the input!

just realized that I'm actually using make publish-on-pypi for every release...

re-added the environment files needed by make

thanks @znicholls for the assist!


undefined is not an object (evaluating 'InAppUtils.loadProducts')

I'm stuck on this for a few days, I've seen the previous issue when they fixed it by reinstalling the app in the simulator but it didn't work for me. Any idea howI could fix it? I've also followed the guide from react native on making sure libraries are linked...

@hugoh1995 How did you resolve this?

i'm in this trouble too! and i dont know how to resolve it.i need help!!!!

in same problem !!

same problem on device and simulator...

I also encountered this issue.
react-native install react-native-in-app-utils didn't linked the InAppUtils library.
Had to link manually
Now it works fine!

You may have to cd into ios and run pod install

React native InappUtils works on android app ?
i Have same error on android project


TypeError: dayjs is not a function

<EMAIL_ADDRESS>

Maybe related to https://github.com/vuepress/vuepress-plugin-blog/pull/93 ?

Maybe related to https://github.com/vuepress/vuepress-plugin-blog/pull/93 ?

Maybe related to vuepress/vuepress-plugin-blog#93 ?

yes, thanks! yesterday, I have to use<EMAIL_ADDRESS>

Maybe related to vuepress/vuepress-plugin-blog#93 ?

yes, thanks! yesterday, I have to use<EMAIL_ADDRESS>

I have the same problem

I have the same problem

FYI, root cause might be
webpack/webpack#4742
iamkun/dayjs#480
iamkun/dayjs#492

FYI, root cause might be
webpack/webpack#4742
iamkun/dayjs#480
iamkun/dayjs#492


Premiere pro crack 2024 Download

Premiere pro crack 2024 Download
Adobe Premiere Pro 2024: The Ultimate Video Editing Powerhouse
If you're serious about video editing, Adobe Premiere Pro 2024 is a game-changer. Packed with cutting-edge features and enhanced performance, it’s the go-to tool for professionals and enthusiasts alike. The new updates focus on streamlining workflows, speeding up processes, and improving collaboration. Whether you're working on complex multi-camera edits, color grading, or audio mixing, Premiere Pro has you covered with its powerful tools and seamless integration with Adobe Creative Cloud.
This version introduces AI-powered features like Auto Reframe, which intelligently adjusts your footage for different aspect ratios, and improved motion graphics templates for faster customization. The updated interface feels even more intuitive, allowing you to focus on your craft without getting bogged down by complicated menus.
Plus, with cross-platform compatibility and cloud syncing, you can work on your projects from anywhere, anytime. Whether you’re editing a YouTube vlog or a feature-length film, Adobe Premiere Pro 2024 offers everything you need to bring your vision to life with professional-grade precision.
Ready to level up your editing game? Premiere Pro 2024 is here to help you do just that.
 Packed with new features, performance upgrades, and industry-leading tools, it's a must-have for both professionals and creators who want to take their videos to the next level. Here are some of the biggest benefits of using Premiere Pro 2024:

AI-Powered Enhancements
One of the standout features in Premiere Pro 2024 is its AI-powered tools, which take your editing efficiency to new heights. Auto Reframe intelligently detects the action in your video and automatically adjusts it to fit different aspect ratios, making it perfect for editing content for social media, YouTube, or cinematic formats without the hassle.

Improved Performance
Premiere Pro 2024 delivers faster rendering, smoother playback, and quicker exports. Thanks to optimizations like hardware acceleration and M1/M2 chip support, editing 4K, 8K, and high-frame-rate footage is smoother than ever. If you’re working on high-resolution content or large projects, this performance boost will save you a ton of time.

Better Collaboration with Adobe Team Projects
With Adobe’s Team Projects feature, collaboration has never been easier. Premiere Pro 2024 allows you to work on projects in real-time with teammates across different locations. Cloud-based sharing and syncing ensure everyone is on the same page, making it ideal for large-scale productions or remote teams.

Seamless Integration with Creative Cloud
If you already use other Adobe tools, Premiere Pro integrates beautifully with the entire Creative Cloud suite. You can quickly jump between After Effects, Photoshop, Illustrator, and Audition to bring your vision to life. This workflow synergy saves time and lets you focus more on your creativity than on technical details.

Advanced Color Grading Tools
Colorists and videographers will love the advanced color grading tools in Premiere Pro 2024. The Lumetri Color Panel has been enhanced for even more precise color control, making it easier to create that perfect cinematic look. Plus, HDR support means you can now edit and export in stunning high dynamic range for a richer viewing experience.

Customizable and Intuitive Interface
Premiere Pro’s interface is completely customizable to fit your workflow. You can adjust the layout, panels, and tools to create a workspace that works for you. Whether you’re a beginner or a seasoned pro, the intuitive design helps you focus on the creative process rather than getting lost in menus and options.

Expanded Motion Graphics Templates
Working with motion graphics has never been easier. Premiere Pro 2024 introduces an expanded library of motion graphics templates, letting you quickly drag and drop pre-built animations into your project. You can also customize them directly within the app without having to dive into After Effects—perfect for those who want pro-level results without the steep learning curve.

Advanced Audio Editing
With Premiere Pro 2024, you get more control over your sound. The new audio editing tools allow for better noise reduction, clearer dialogue, and more precise audio mixing. Plus, integration with Adobe Audition means you can take your sound design to the next level if needed.

Pro-Level Output and Export Options
Whether you're exporting for social media, broadcast, or film, Premiere Pro offers a wide range of export presets and custom settings. The new codec support ensures you can output in the highest quality for any platform, and direct export to cloud services makes sharing your final project easier than ever.


[UI Bug] Blue outline left on comment's delete button after cancel deleting a comment

Issue
When the user clicks on the "Delete" button at the bottom of a comment they created and the confirm modal window popped up - if they click to cancel the deleting request, the modal window will disappear but left BLUE outline on the comment's "Delete" button.
Desktop: will show blue outline text box for Delete button for a while, then it will disappear by itself.
Mobile Web: will show blue outline text box for Delete button until the user click on anywhere else
Steps to reproduce

Access any post as a logged-in user, write a new comment
Click on "Delete" button at the bottom of the comment
Modal window pops up and ask for delete confirmation, click "Cancel" button
Observe the result that happens to the comment's "Delete" button.

Expected behavior
No blue outline left after click to cancel comment deleting

Also, when the outline appears, it shouldn't be that blue but our main color.

I looked into this issue and will push proposed change to branch feature/1473 when I get access.  Thanks.

tested on staging for both desktop and IOS


bpftrace-compiler: add run-via-edgeview

In more RL like scenarios, it is neither possible to reach EVE via ssh nor via direct network access. For these cases edgeview was developed.
This new feature leverages edgeview to run bpftrace scripts in more tough environments.

@christoph-zededa, please ping me when you think all comments are addressed.

@christoph-zededa, please ping me when you think all comments are addressed.

I think I addressed everything, @OhmSpectator ping.

@christoph-zededa, do you think merging now is okay without waiting for all the test runs? I don't see this PR should affect any functionality checked by these tests...

@christoph-zededa, do you think merging now is okay without waiting for all the test runs? I don't see this PR should affect any functionality checked by these tests...

I am okay with it, but we're also not in such a hurry not being able to wait for it ...

I am okay with it, but we're also not in such a hurry not being able to wait for it ...

Just not to waste the runners' time.


Add checks for BoundedEnum

Sorry for the unimaginative law names, I hope someone else can come up with nicer ones.

I guess this will fail until purescript-enums is tagged.

Also need to add the dependency I think!

Doh! I had a bower link... >= 2.0.1?

Thanks!

Just curious, why do you use sudo: required in the travis setup? Don't you prefer the container-based environment?

Should I make a release now, or are there any other checks you're working on at the moment?

Just curious, why do you use sudo: required in the travis setup? Don't you prefer the container-based environment?

The trusty image requires it, and that's pretty much essential for PureScript projects, for some reason they build awfully without it - take 10-100x longer and sometimes stall forever.

I think trusty is container based too.

Looks like thy have a beta: https://docs.travis-ci.com/user/trusty-ci-environment/

I think I can write Enum tomorrow, let's wait a bit.

Okidoke, thanks! We can try the trusty beta thing in that PR too perhaps :)

I'll open a separate request for the trusty beta, but build times are roughly the same and boot time is almost instantaneous. Things aren't as nice when trying to build the purescript compiler itself, I get failures due to lack of disk space and also the build seems slower.


Remove az-binary check

I assert that az-binary check is a bit too excessive since it's not always required to have az binary installed when you are installing Cilium on AKS.
Instead of forcing users to specify --disable-check=az-binary flag, let's just fail if az binary is needed but not found. This behavior is consistent with how we handle gcloud binary.

What does the output look like when the binary is missing?

❌ Unable to execute "az account show --output json --only-show-errors":

@michi-covalent does the output below that indicate that the binary is missing? I think some messaging along those lines is useful.

yes it does, sorry i didn't paste the whole output:
❌ Unable to execute "az account show --output json --only-show-errors":
↩ Rolling back installation...

Error: Unable to install Cilium: unable to execute "az account show --output json --only-show-errors": exec: "az": executable file not found in $PATH

makes sense to me


Remove comment

a) Not very informative
b) # is not a comment introducer in zsh so this caused me some confusion when I cut'n'pasted...

a) Not very informative
b) # is not a comment introducer in zsh so this caused me some confusion when I cut'n'pasted...

I thought that was quite an informative comment. And this is not a zsh script.

a) Not very informative
b) # is not a comment introducer in zsh so this caused me some confusion when I cut'n'pasted...

I thought that was quite an informative comment. And this is not a zsh script.

Although I agree, for copying and pasting it can be troublesome. Why not have the tutorial user invoke a rule in the top Makefile to just build the core?

Although I agree, for copying and pasting it can be troublesome. Why not have the tutorial user invoke a rule in the top Makefile to just build the core?

My reasoning for submodule initialization as a separate line was this:

The third_party makefile used to update/initialize submodules, but doesn't any more as of #691 -- I was surprised to notice this change when testing. However, I think it makes sense not to automatically update/initialize submodules, because that setup made it a huge pain to update the submodules (make would reset the update -- that's why we have the now-redundant no-update target). Regardless of what the best answer is here, I think it's evident enough that the behavior of that Makefile changes frequently, so I'd rather not make the tutorial assume anything about its behavior. If I don't assume the makefile will initialize the submodules, then the user has to. One option would be to have make submodule-init which just initializes the submodules, but I think that's no more readable than git submodule.
I could have instead suggested people clone with the --recursive option, which initializes the submodules as part of the clone, but then some people might have cloned already and not know how to recover, and/or not notice the --recursive.

Closing this in favour of #778 which adds a top level command and replaces the command referenced here with the new one in the linked PR


Merge 6 -> 7

➡ Forward port
Port ign-gazebo6 to gz-sim7
Branch comparison: https://github.com/gazebosim/gz-sim/compare/gz-sim7...ign-gazebo6
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

Can we wait until https://github.com/gazebosim/gz-sim/pull/2398#discussion_r1643390612 is resolved to merge this?

yes this can wait

@Mergifyio update

Can we wait until #2398 (comment) is resolved to merge this?
https://github.com/gazebosim/gz-sim/pull/2451 is merged, so we can move forward with this. Can you update the PR?

updated


Cleanup and update from two site branch, add ability to do rotation of entire PEPS

OK I'm going to merge this because it has all our two site stuff and a bunch of other things


core_ibex dv build system refactor

[
This is a big PR (33 files changed, 2477 insertions(+), 1886 deletions(-)), so
no rush to review, and feedback very much welcome.
It would be helpful to just checkout and see how building works for you locally!
]
As well as completely removing the existing non-cosim flow, this commit
significantly refactors the build system to be less reliant on the makefile.
This is a continuation of previous refactoring such as this PR.
While we still use the Makefile, it is relegated to only providing scheduling
and dependency calculations between the different build steps.
This is possible by moving all of the build metadata into a file on-disk, which
is populated at the start of a new regression, then read and written to by the
different scripts executing the build. Each build step only needs to be passed
the location of this metadata at the top-level, and it can then import all
the information it requires to calculate and perform the next build stage.
As every stage has all of the information of previous stages available to it,
it makes it very much more convenient to access useful data.
This metadata object is stored as a serialized binary .pickle file, but is also
exported as a human-readable yaml version for viewing.This should also
aid integration into different build systems, as the dependency on Make is
much weaker.
The file metadata.py and test_run_result.py contain the definitions for
these metadata objects. metadata.py defines an object for the whole
regression, while test_run_result.py defines objects for each individual test
performed.
The file riscvdv_interface.py has been created to better isolate the interface
with that project.
The file setup_imports.py has been created to centralize the importing of
python modules from other projects (riscvdv/ot_lowrisc_ip etc.).
Existing python code has been tidied to better conform to PEP8 standard
formatting, and to be more pythonic in general such as using pathlib.Path.
N.B.
Some new python dependencies are added, so if running locally you will
to update your python package set by running...
pip3 install -r python-requirements.txt

CI runs this command automatically so no change is needed for that.

While running the following command:
make -j7 --keep-going IBEX_CONFIG=opentitan ITERATIONS=1 WAVES=0 COV=0

I encountered the following error:
riscv32-unknown-elf-gcc: error: ibex/dv/uvm/core_ibex/out/run/riscv_csr_test.2825/test.S: No such file or directory
riscv32-unknown-elf-gcc: fatal error: no input files
compilation terminated.
make: *** [Makefile:284: out/run/riscv_csr_test.2825/test.bin] Error 1

I tried running this on my own system and here are a couple of comments.
We'll need to add the following Python 3 libraries as dependencies:

pathlib3x
typeguard
portalocker
typing_utils

I'm getting the following warning when running just $ make: WARNING:ibex_cmd:Rejecting test riscv_bitmanip_full_test, 'rtl_params' specified not compatible with ibex_config
The trr.yaml files and metadata directory seem to be generating successfully.

Thank you for looking at this @marnovandermaas .
I've updated the original PR comment to mention the necessary python packages. They are added to the python-requirements.txt file as part of the PR but you have to update your local environment manually, so I left a comment with the command you need to run.
The "Rejecting test riscv_bitmanip_full_test" is just a more-verbose warning that tests are being excluded due to mismatching IBEX_CONFIG against the testlist. Not sure if this is an improvement, but I thought maybe being more-explicit would be useful.

While running the following command:
make -j7 --keep-going IBEX_CONFIG=opentitan ITERATIONS=1 WAVES=0 COV=0

I encountered the following error:
riscv32-unknown-elf-gcc: error: ibex/dv/uvm/core_ibex/out/run/riscv_csr_test.2825/test.S: No such file or directory
riscv32-unknown-elf-gcc: fatal error: no input files
compilation terminated.
make: *** [Makefile:284: out/run/riscv_csr_test.2825/test.bin] Error 1

Hmm interesting, I've not seen that error. Will investigate further.
Thanks again for starting to review this very-large changeset!

Pushed a new commit 409e2dc which has some misc fixes, plus some improvements to regr.log, such as placing the summary percentage at the top of the file, and adding some lines of context around the log-line indicating the test failure. This should make the logfile more useful at a glance.

One other thing I was thinking was automatically generating a test.dump file. I always end up running the following command when I'm debugging a test:
riscv32-unknown-elf-objdump -D test.o > test.dump

Would we be able to add this quality of life improvement to this build system overhaul?

One other thing I was thinking was automatically generating a test.dump file. I always end up running the following command when I'm debugging a test:
riscv32-unknown-elf-objdump -D test.o > test.dump

Would we be able to add this quality of life improvement to this build system overhaul?

I actually already had these locally, even had makefile targets for them in the PR but I didn't include the scripts.
Pushed another commit, now you should be able to run make dump prettify to call the scripts and generate both a test.dump and a trace_pretty.log, which is a column-aligned version of the ibex trace.

Rebased

Rebased

The previous rebase was bad (I missed part of the new test_done mechanism) so force-pushed again to fix it.

Also some documentation going over the flow internals would be great, though not an immediate priority. Please create an issue to track the need for it (let's make it a V3 issue for now).

Also some documentation going over the flow internals would be great, though not an immediate priority. Please create an issue to track the need for it (let's make it a V3 issue for now).

Noted in #1778. Thanks for the review :)


[rayci] add dependency tracking in stepNodeSet

for tracking which nodes to include or reject.

ping.
if this gets no review tomorrow morning, I will just force merge this


Hash tag sort

Issue

Whenever click the hashtag, the tagged post should be listed.

Memo

Do I have to use another vue page? or ReadPage.vue is enough ?


nifi-1214b Mock Framework should allow order-independent assumptions …

nifi-1214b Mock Framework should allow order-independent assumptions on FlowFiles. This replaces previous nifi-1214

Hey @ToivoAdams, looks like this has merge conflicts. Could you address them?

I hope conflicts are now resolved.

Hey @ToivoAdams, you didn't properly rebase. If you double check this PR, you brought in 250+ commits that change 2,163 different files. What you should have done is rebase your commits on top of the latest master and then force pushed to your branch.
Currently I think the best way forward is to create a new branch off of the latest master, where you a new commit with your changes on top of it and create a new PR.


Beginner Course - Debugging

Dear all,
I wanted to follow up on a brief conversation I had with @roiser regarding debugging tools. First of all, I think it's great that it's part of your beginner track because I often see this topic being ignored while, in fact, it's one of the most important topics there is. I reached out to @roiser to "advertise" the graphical debuggers. It seems like over time people fell back to using gdb / lldb via the terminal, but there are arguably many advantages to using GUIs for debugging. E.g., CodeLLDB is a free extension for VSCode integrating debugging of CPP code in the IDE. There are many alternatives (see for instance ATPESC2022, Track 6) but some of them are not free.
Point of this issue is that I think it would be very helpful to make people aware of these tools such that they at least know they exist and can follow up if they wanted to. So I think it would be good to consider allocating 1-2 slides to expose participants to these tools. :)
Tobias

Hi, thank you for your suggestion!

It seems like over time people fell back to using gdb / lldb via the terminal, but there are arguably many advantages to using GUIs for debugging.

In my experience this depends a lot on your organisation's culture. For many software engineers or folks in the industry using a graphical IDE is a no-brainer. Others just start out with the bare and established command line tools and manage to pass the long learning curve to also reach stunning productivity. It is ultimately a mix of culture, education, work environment and personal preference.

[...] but some of them are not free.

Which is often a big driver for choosing a specific solution. A few hundret bucks sounds expensive, especially when you are a student or in your early career. However, when you start to think about the value of your own time, a good development environment can already amortize its cost at the first bug that took you only half the time to find :)
CERN has licenses for some products, like MS Visual Studio which offers a great experience on Windows. Your question now motivated me to inquire at the license service whether CERN could get licenses for CLion, which I have been using for 2 years now on Linux and also offers a great experience.

Point of this issue is that I think it would be very helpful to make people aware of these tools such that they at least know they exist and can follow up if they wanted to. So I think it would be good to consider allocating 1-2 slides to expose participants to these tools. :)

Very much agreed! But I am only one voice on this course and people may have different opinions. It would help if you could suggest some concreate products, maybe even with a few key points that makes the product great. Like you suggested CodeLLDB, which I have not heard before. I know VS Code has a debugger, but I have never used it (I use CLion) so i don't know whether CodeLLDB provides a benefit over the built-in debugger. Maybe someone will then try said product and if they are convinced as well, we could put it on a slide.

Your question now motivated me to inquire at the license service whether CERN could get licenses for CLion

So, the CERN license service informed me that we have a pooled license for JetBrains products at a reduced price. But you cannot use it for free, your group would need to contribute to the license costs. The license service can inform you about all the details in case you are interested.

Very good, is there already a pointer to it in our slides? If not shall we provide one?

I can add a slide when preparing for the next HEP C++ coures. I am busy the next two weeks.
@TobiasDuswald please add some more concrete tools you would like to see on the slides. I can then include them when I make the slide.

Runaway comment: I'm a big fan of https://github.com/cyrus-and/gdb-dashboard to give gdb a boost. The one big thing gdb-dashboard doesn't provide is that it won't move your editor's cursor to the line currently being debugged (it will display it nicely and with syntax highlighting, but it can't do anything for your editor).

Hi, I recently picked an alternative - https://github.com/hugsy/gef. The main reason I prefer it to Cyrus's dashboard: after moving to another line (i.e. next), the Cyrus' dashboard flushes the screen and I cannot see the previous state ... whereas Gef would give the result below the previous. On top of that Gef comes with a slightly more fancy coloring scheme - different color for Modified register | Code | Heap | Stack | String. Lastly, it is said to be "easily extensible", allowing to create own commands - https://hugsy.github.io/gef/api/ (I have not tried them yet though).
Problem with cursor is still there.


CLI should use consistent system-dependent path separators

Expected Behavior
Consistent/expected path separators are used. Standard for Java tools is to use : on *nix and ; on Windows for path separation, and , or   (a space) for separation of Ant-style filters.
Current Behavior
Bit of a mixed bag.

--input, --plugin, --config & --config-resource accept both , and ; as path separators regardless of platform.
--report is an odd one, since it requires using : as an internal separator between components of the input command (e.g. -r txt:reports/detekt.txt). This caused issues on Windows (now worked around).
--filters separates on , and ; but is a bit different in scope since the value is typically quoted.

Context
Several issues in the past with Windows related to handling of path separation. Consistency with other tools.
Proposal is:

--input, --plugin, --config & --config-resource allow path separation using only : on *nix and ; on Windows
--report is deprecated in its current form. Introduce --report-txt, --report-xml and --report-html which each accept a single path to the desired output file. No parsing of input is required except to convert to a file path.
--filters accepts either "<filter-1> <filter-2>" (quoted, space-separated), "<filter-1>,<filter-2>" (quoted, comma-separated), <filter-1> <filter-2> (unquoted, space-separated), <filter-1>,<filter-2> (unquoted, comma-separated).

Of course, these conventions will have to be enforced as rules going forward as new parameters are introduced.
Your Environment

Version used: RC9.2
Operating System and version: Windows
Link to your project: N/A

Hm, platform specific separators could be confusing if you use both windows and *nix?
Configuring CI will need the right separators hmm.

You need to use / path separator on nix and \ on Windows, so paths are already written differently on the CLI on the two platforms.

How about we agree on something that works for everyone? I don't like the idea of checking of which OS you use and depending on that configure the CLI parameters.
Also this probably means another breaking change :(

something that works for everyone

That's the problem... there won't be a single separator that works for everyone (just like the path separator is different on *nix and Windows, so the CLI parameters will always be different on the two platforms anyway).
But, as long as a : character isn't used, it probably doesn't matter. @arturbosch do you want to make a call and either recommend a PR or close the issue as wontfix?

Hm if I read the conversation again, I think we should change the separator and introduce a breaking change her :(.
What about we just leave ; as a separator on windows and unix?
So:
--input, --plugin, --config & --config-resource will use just ;
--filters could be either also separated by ; or if jcommander allows us to use --filters <first> <second> ...
For --report an semicolon could look weird -r txt;reports/report.txt, -r txt=reports/report.txt could be an option to remove the workaround. Or if jcommander supports arity (seems it does) we could use -r txt reports/report.txt.
Hardcoding reports to cli parameters is not an option.

That's all doable. JCommander supports variable arity which allows --filters <first> <second> ... and fixed arity for --report txt reports/report.txt which I think looks nice.
As for leaving just ; as the separator (and removing ,), that would probably be fine.
But perhaps this change should be deferred to a detekt 2.0 release, rather than another breaking change before 1.0?

Having a hard time imaging the changes here. Can you give a concrete example of the current configuration and how you want to change it?

Since this issue became quite stale, what are we going to do about?

Since this issue became quite stale, what are we going to do about?

I propose that for detekt 2.0 the path separators are updated so they're system-dependent for any CLI options that accept multiple paths. That's the convention used for both javac and kotlinc.
I don't have as strong an opinion on the other options since I use detekt from Gradle so I don't have to worry about any issues with those.

I propose that for detekt 2.0 the path separators are updated so they're system-dependent for any CLI options that accept multiple paths. That's the convention used for both javac and kotlinc.
I don't have as strong an opinion on the other options since I use detekt from Gradle so I don't have to worry about any issues with those.

This issue is stale because it has been open 90 days with no activity. Please comment or this will be closed in 7 days.

What's the conclusion here? Are we using fixed ; for both Nix and Windows as per the comment https://github.com/detekt/detekt/issues/1253#issuecomment-445077707? Or doing smth else?

I agree fully with https://github.com/detekt/detekt/issues/1253#issuecomment-445077707 so I think that we can go with ;.

@3flex I tried to fix it but following TC will fail now
executeDetekt(
                    "--input",
                    path.toString(),
                    "-Xcontext-receivers",
                    "-opt-in=org.jetbrains.kotlin.compiler.plugin.ExperimentalCompilerApi",
                )

As now "-Xcontext-receivers", is being considered a param for --input(and hence failing as there is no file with the name "-Xcontext-receivers"). For these cases, we have to update the documentation to put Gradle related param after the gradle command ./gradle


Update team and project documentation to reflect changing team membership

@FanguiGuo's signature was added in commit a6fed68f2004a042451d4fa46bc6581a134d2179


Private recordings

+1, really waiting for this feature!
It would definitely expand your target market in the form of companies sharing top-secret terminal playbacks among their staff.
I would pay for this feature as well.

:+1: :+1: :+1:
I would PAY FOR THIS FEATURE.

I'm with @fusiondog on this one. I'd just run a local copy as mentioned in the FAQ.
https://asciinema.org/docs/faq

Good news! Private asciicasts just landed for everyone: http://blog.asciinema.org/post/private/

That's wonderful news! I am very thankful for this feature.
It appears that you did not introduce any paid model for this. I recommend you also think of a way to monetize asciinema's usage in the future to raise funds for further development. It's a cool project!

@hardipe Enjoy! No, no paid model this time. Maybe some day, we'll see. As for private asciicasts I realized that this is a really essential thing, and everyone who wants to try asciinema shouldn't be forced to auto-publish their first recordings.


Add .gitignore for FreePascal (http://www.freepascal.org) and Lazarus…

Reasons for making this change:
Currently missing.
Links to documentation supporting these rule changes:
http://wiki.freepascal.org/file_types
Link to application or project’s homepage:
http://www.freepascal.org
http://www.lazarus-ide.org

@davegorst - Does this template solve what you're looking for? https://github.com/dvcs/gitignore/blob/37adf08cf5e2cbd75077c2d4eef00082b5a5a554/templates/Lazarus.gitignore
You can access it at: https://www.gitignore.io

It certainly looks like it. I hadn't seen this fork - it might be an
idea to feed all this back into the source wiki.
Thanks,
Dave.
------ Original Message ------
From: "Joe Blau"<EMAIL_ADDRESS>To: "github/gitignore"<EMAIL_ADDRESS>Cc: "davegorst"<EMAIL_ADDRESS>"Mention"
<EMAIL_ADDRESS>Sent: 12/12/2017 12:41:10
Subject: Re: [github/gitignore] Add .gitignore for FreePascal
(http://www.freepascal.org) and Lazarus… (#2545)

@davegorst https://github.com/davegorst - Does this template solve
what you're looking for?
https://github.com/dvcs/gitignore/blob/37adf08cf5e2cbd75077c2d4eef00082b5a5a554/templates/Lazarus.gitignore
You can access it at: https://www.gitignore.io
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/github/gitignore/pull/2545#issuecomment-351039811,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIYVWztWZim6UNVrA30wwOuKsyNgmNowks5s_nRlgaJpZM4Q6vrV.

You can definitely add it to the source wiki.

I'm going to close this out because there is a Global/Lazarus.gitignore that already defines all these rules.


Migrate SharedPreferences to DataStore

Describe the feature request.
Following this pull request. We will migrate all the functionality of unencrypted shared preferences to datastore.
Additional context
Acceptance criteria
A check list of all things to verify once the implementation by the engineer is complete
Area path
A list of ordered steps in the app on usage of the feature to support anyone testing it e.g. Code reviewer, QA e.g.

Login to the app
Open Navigation bar
Click on Children register
Click on Child profile
Click on Edit profile from menu

Implementation plan (For Engineers)
Create serializable wrapper data classes for relevant SDK classes
Replace shared preferences functionality
Update view models with StateFlow when needed
Write new tests
Remove unused tests
Update documentation

@f-odhiambo @ndegwamartin The most significant items left are

Creating a Serializable wrapper for LocationHierarchies to allow storage
There's a single read I need to port that seems to use REMOTE_SYNC_RESOURCES
Updating tests that need proto datastore
writing any new tests and docs


Update return type of getRelationshipToSum method

Changed the return type of getRelationshipToSum function in CanAggregateRelatedModels class. Previously, the function could only return string or null, Now it can return string, array, or null. This change gives the option to set additional query constraints on the sum query.

[ ] Changes have been thoroughly tested to not break existing functionality.
[ ] New functionality has been documented or existing documentation has been updated to reflect changes.
[ ] Visual changes are explained in the PR description using a screenshot/recording of before and after.

Please test your PRs as this doesn't work, $this->relationshipToSum is never set to an array in the first place.
I think we should change the syntax, instead of allowing an array we should add a third param to sum() as a Closure to scope the relationship by.


DRATs cannot run against a credhub-enabled environment

It looks like DRATs expects to pull the CF admin password from the deployment manifest. This doesn't work in credhub-enabled envs as the manifest only contains references to the password (((cf_admin_password))).
We are currently using a fork of DRATs that takes in CF_ADMIN_PASSWORD as an env variable instead. This will break the DRATs flow of backing up from one env and restoring to another unless they both have the same admin password.

@ljfranklin thanks for letting us know, we were aware of this issue, the fix is in flight in https://www.pivotaltracker.com/story/show/151244808, we have chosen a similar approach of taking in the cf creds from the ENV

done with https://www.pivotaltracker.com/n/projects/1662777/stories/151244808


esm.sh externals no longer working

Unfortunately it seems the esm.sh provider is no longer supporting externalization of dependencies, so it's become more difficult to support for us.
For now I've just reverted the test case in https://github.com/jspm/generator/commit/a4808ffd2be1ec102dee6a58979549110cc64fc6.
@ije is there a way that we can still support externals on esm.sh for JSPM CLI support?

there is a bug that makes lit (just lit) ignoring the ?external query in v117 builds, this will be fixed at next deploy.

Thanks for the update here @ije! Glad to hear we can re-enable the test soon.

@guybedford just deployed the fixes, can you please try again thanks 🙏

@ije that seems to be working to me. Although the online generator seems to be failing due to access-control-allow-origin unfortunately:
https://generator.jspm.io/#U2xhYGBkDM0rySzJSU1hyMkscTDSM9Az0C1K1jMEAI4dhrMdAA

Hmm, actually it seems like the test is still not passing. We're currently using the * import form. Perhaps we should be using external queries explicitly?
We're accessing this URL for Lit<EMAIL_ADDRESS>resolved via<EMAIL_ADDRESS>

after purging (cdn) cache, it works for me now, but i found some other 404 errors,
eg:
GET<EMAIL_ADDRESS>404

this correct path is:
<EMAIL_ADDRESS>

@ije thanks, I can confirm that allows us to reenable the tests here too. For the unnecessary package.json checks, this is a fallback behaviour in JSPM when it doesn't recognize the pathing system in use by the provider. It usually works eg in Node.js, but breaks down in the browser due to 404 pages often not including access-control-allow-origin, as seems to be the case for esm.sh here.
I've got a possible fix in https://github.com/jspm/generator/pull/302 to better support working out the package root, although need more time to test it properly.

Closing as resolved, thanks again for the help!


can you add the new view like QQ's drawer

the MMDrawerController is very great , but can you add the new view like QQ's drawer?

###like this -->left view

###like this -->right view

##gif

@JuniorXiao  https://github.com/romaonthego/RESideMenu


Update KEB dependencies

Description
Changes proposed in this pull request:

update dependencies without introducing breaking changes.

Related issue(s)

/retest

/retest


[tests]: Clear unused records from the zone map

Is this a BUG REPORT or FEATURE REQUEST?:
feature
What happened:
Currently, we have lots of unnecessary records in our zone map for E2E tests.
We should point all the URIs used inside the tests records to example.com since we right now none of the URIs follow a standard.
What you expected to happen:
Have a standard for all the URIs used inside the zone map and remove the unnecessary records.
Anything else we need to know?:
We should discuss this change before starting #291.
Should we still keep a minimal set of e2e tests inside our code or not? If we decide to keep a few of them then we have to still keep the mock DNS server too.
Also if we decide to move to only having external e2e tests, does it make sense to clear the records right now? I think since it takes much longer time to implement the external tests, it would worth it to clear the current records.

I agree on cleaning up our tests especially our use of URIs.
I would still keep a set of unit like tests with a mock dns server as it's easier to test. On the specifics I'll respond over at #291.
On the standardization how about the following for request records:
..example.com/
Which get redirected to something like:
..example.com
Example:
website-fallback.git.git.example.com
git-pull-success.git.git.example.com
git-push-success.git.git.example.com
wildcard-fallback.git.path.example.com
path-fallback.git.path.example.com
git-pull.git.path.example.com
git-push.git.path.example.com

A rough idea. Happy to hear your ideas.


Community website screenshot

#ISSUE-NO
#234
What does this PR do?
This PR adds a screenshot of the homepage of Community Website

@WebShivam , please give some meaningful name to the screenshot file, so that it is easily distinguishable when we add other images to the directory.
Thanks

The new file is not visible. Did you rename the file or delete it ?

The new file is not visible. Did you rename the file or delete it ?

I renamed it and its new name is community-website-screenshot


typo: Double word "or"

@nschonni : Thanks for your contribution! The author, @rayne-wiselman, has been notified to review your proposed change.


Updates for docsite inclusion (WIP)

Site Generator updates to pull in this branch:  https://github.com/uport-project/uport-project.github.io/pull/20/files
The current structure looks like this when deployed with these changes:

I am still working on the content & information hierarchy, so things till change slightly from this screen shot, but I hope this helps add context to some of the changes.  Generally the changes were to try and include the information needed in the docs-site in a way that could be somewhat standardized.
The docs-repo contains some general guidelines for my approach here.  The following suggestions will help answer questions as to why I moved some content around, the rest of the guidelines are here:  https://github.com/uport-project/docs/blob/develop/README.md#repository-guidelines
- Put detailed content, like implementation details in the /docs folder.
- Docs folders can have: guides, tutorials, sdk/api reference documentation.

I will change the suggestions above to also include basic install/getting started quick copy in the readme.
The generated documention needs a little work too, which requires some edits to the pre-generated code.
Generated documentation (showing under reference):

This is the issue with the generated doc though... note the SimpleSigner => bit above....
hopefully we can change this so the reference to simpleSigner is not so redundant... the links are a little weird.

The link in the nav ends up looking like:  http://localhost:8000/did-jwt/reference/index#simple-signer-hex-private-key-%E2%87%92

Update...  This is how things sit now.  I will need some input on the nav headings.


Fix build issue with SWIG 3.0

This change fixes a problem that occurs when trying to build the example with SWIG 3.0 (as packaged as swig3.0 in Ubuntu 14.04): the generated wrapper code is missing a header #include. By
extending the .swig file with an explicit dependency, this problem is fixed.
However, there is still a problem:
malte@eucleia:~/tmp/simplelib(git)$ make cleanall
malte@eucleia:~/tmp/simplelib(git)$ make
clang++ -Wall -I ./inc -fpic -c src/simpleclass.cpp -o obj/simpleclass.o
swig -go -c++ -debug-classes -intgosize 64 -soname libSimpleLib.so simplelib.swig
Classes
------------
std::initializer_list
std::vector
std::vector<(bool)>
std::vector<(char)>
SimpleClass
std::vector<(std::string)>
clang++ -Wall -I ./inc -fpic -c simplelib_wrap.cxx -o obj/simplelib_wrap.o
clang++ -Wall -shared -o lib/libSimpleLib.so obj/simpleclass.o obj/simplelib_wrap.o
malte@eucleia:~/tmp/simplelib(git)$ make build
Building bindings...
/usr/lib/go/bin/go tool 6c -I /usr/lib/go/pkg/linux_amd64/ -D _64BIT simplelib_gc.c
simplelib_gc.c:33 struct must have tag
simplelib_gc.c:49 struct must have tag
simplelib_gc.c:65 struct must have tag
simplelib_gc.c:81 struct must have tag
simplelib_gc.c:97 struct must have tag
simplelib_gc.c:113 struct must have tag
simplelib_gc.c:129 struct must have tag
simplelib_gc.c:145 struct must have tag
simplelib_gc.c:161 struct must have tag
simplelib_gc.c:177 struct must have tag
simplelib_gc.c:193 struct must have tag
too many errors
make: *** [build] Error 1

Googling around for this error hasn't thrown up anything useful. Any ideas what's going on?

I tried the same code again with Go 1.5 and swig 3.0.7 and it worked.

I tried the same code again with Go 1.5 and swig 3.0.7 and it worked.

Thanks, I merged another PR to update the project for latest version of SWIG.


Translations sometimes not sent

Hey,
I'm currently encountering an issue wherein transcription operates as expected, but translations are inconsistently returned from the SDK (or API??). Restarting the session a few times occasionally resolves the problem, although not consistently. Unfortunately, I haven't been able to identify a clear pattern in this behavior.
In more detail, I am receiving regular AddTranscript messages, but no AddTranslation ones. My audio sources are German online radio senders, which I feed into speechmatics with fetch (see the code snippet below).
My code:
let isRunning = false;
let url = "https://dispatcher.rndfnk.com/br/br24/live/mp3/mid"; // alternative, same issue https://st01.sslstream.dlf.de/dlf/01/high/aac/stream.aac?aggregator=web
let lang_origin = "de";
let lang_target = "en";

const session = new RealtimeSession({
  realtimeUrl: "wss://eu2.rt.speechmatics.com/v2",
  apiKey: process.env.apiKey,
});

session.start({
  transcription_config: {
    language: lang_origin,
    operating_point: "enhanced",
    enable_partials: false,
    max_delay: 5,
    max_delay_mode: "flexible",
  },
  translation_config: {
    target_languages: [lang_target],
  },
  audio_format: { type: "file" },
});

session.addListener("RecognitionStarted", (data) => {
  console.log("RecognitionStarted", data);

  //prepare file stream
  isRunning = true;

  fetch(url)
    .then(
      (res) => {
        const reader = res.body.getReader();

        const pump = () => {
          return reader.read().then(({ done, value }) => {
            if (!isRunning || !session.isConnected) {
              return;
            }

            if (done) {
              session.sendAudio();
              return;
            }

            session.sendAudio(value);
            return pump();
          });
        };

        return pump();
      },
      (err) => {
        console.log(err);
      }
    )
    .finally(() => {
      session.stop();
    });
});

session.addListener("AddTranscript", (message) => {
  console.log("AddTranscript", message);
});

session.addListener("AddTranslation", (message) => {
  console.log("AddTranslation", message);
});

I'd very much appreciate to get some input.
Thanks in Advance!
Alex Daichendt

Hi @adaichendt-tv1 . Thanks for raising this. This was caused by an internal incident in which the translation services were scaled down in our EU SaaS cluster. However, our Site Reliability team have said that the service should be back up now. I hope this helps.

Hi, thanks for the quick response! It indeed seems to be working as expected again. Is there by any chance a status page that I can check in case we encounter the same issue again?

@adaichendt-tv1 - Speechmatics status page: https://status.speechmatics.com/

Thank you! I received no more complaints now.


We will make sure Twitter works. Then svelte templates need to be built for github, hackernews and readability - I can work on it but we need to organize code for separating the templates for the sources.

We will make sure Twitter works. Then svelte templates need to be built for github, hackernews and readability - I can work on it but we need to organize code for separating the templates for the sources.

When it gets merged, we need to really test it manually. Loads of things might have been broken up. PDF as well as EPUB.
This project is getting too big now 😅

Well good luck to us then!


Getting import error using django-rest-framework-social-oauth2

I have followed all the instructions mentioned in the documentation for setup but I am getting import error. Below is the stacktrace:
Traceback (most recent call last):
File "/home/vaio/git_kiti/kiti/manage.py", line 10, in <module>
execute_from_command_line(sys.argv)
File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 338, in execute_from_command_line
utility.execute()
File "/usr/local/lib/python2.7/dist-packages/django/core/management/__init__.py", line 312, in execute
django.setup()
File "/usr/local/lib/python2.7/dist-packages/django/__init__.py", line 18, in setup
apps.populate(settings.INSTALLED_APPS)
File "/usr/local/lib/python2.7/dist-packages/django/apps/registry.py", line 108, in populate
app_config.import_models(all_models)
File "/usr/local/lib/python2.7/dist-packages/django/apps/config.py", line 198, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
File "/usr/local/lib/python2.7/dist-packages/social/apps/django_app/default/models.py", line 8, in <module>
from social.utils import setting_name
File "/usr/local/lib/python2.7/dist-packages/social/utils.py", line 13, in <module>
from requests.packages.urllib3.poolmanager import PoolManager
ImportError: No module named packages.urllib3.poolmanager

This is coming from python-social-auth.
Probably a version conflict with the requests package. See [this commit] (https://github.com/omab/python-social-auth/pull/626/commits/80ceb11e761c8a154b00e488e26412cacac1d1f9).
Check the version of your requests package.

It was 2.2 but now I have upgrade it to 2.9.1. Still facing the issue.

We'll have to wait for them to fix it.
I can't really help you more than that.
Try commenting or +1 this issue
What I usually do when something isn't going to be fixed soon is forking the project, fixing it and then adding my fork in my requirements.txt (just before the other packages using it).
-e git+https://github.com/puneetagg/python-social-auth.git#egg=python-social-auth #needed for drfso2 while issue 617 isn't fixed
django-rest-framework-social-oauth2==1.0.4

Thanks for suggesting the way in such situations.

Its resolved. Python used for running application was of the system and I now changed it to that of my virtual env. May be that's why requests module was being picked from the system instead of virtaulenv.
Thanks!


python311Packages.zha-quirks: 0.0.99 -> 0.0.100

Diff: https://github.com/zigpy/zha-device-handlers/compare/refs/tags/0.0.99...0.0.100
Changelog: https://github.com/zigpy/zha-device-handlers/releases/tag/0.0.100
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 235278 run on x86_64-linux 1

8 packages built:

home-assistant-component-tests.hassio
home-assistant-component-tests.homeassistant_hardware
home-assistant-component-tests.homeassistant_sky_connect
home-assistant-component-tests.homeassistant_yellow
home-assistant-component-tests.otbr
home-assistant-component-tests.zha
python310Packages.zha-quirks
python311Packages.zha-quirks


Allow one account key for all registrations.

Recently we ran into the rate limit for registrations per IP address.

https://letsencrypt.org/docs/rate-limits/

Alternatively, it shall be possible to configure a single account key for all issuances.

https://letsencrypt.org/docs/integration-guide/

How would such a setting require changes to the current companion?

I've already got this feature covered, I'll try to merge it in dev this week end.

A first version of the feature has been commited to dev : 4334d1593e841c8a16b013e565980351d1d25d57.
It's closely inspired by the way certbot handle account keys. You can check the doc and try it now by pulling and using jrcs/letsencrypt-nginx-proxy-companion:dev.
Note: if you use the dev version with an existing certificates volume/dir, on the next certificate(s) renewal it will replace corresponding account keys with a symlink to
/etc/nginx/certs/accounts/acme-v01.api.letsencrypt.org/directory/default.json
This new file will be copied from the account key of the first renewed certificate.
This will in turn cause a re-validation of all the other domains to the new common ACME account when their certificates are due for renewal. So be sure that your nginx-proxy stack is working properly and that you have no issues wit LE domain validation before using jrcs/letsencrypt-nginx-proxy-companion:dev, and backup you certificates volume.
You can also disable the feature entirely by setting the REUSE_ACCOUNT_KEYS to false on the letsencrypt container. This will make the container behave as it does currently in master (create a new ACME account for almost every new domain).
The automatic switch to a common ACME account key on renewal has been tested with success on two separate hosts running different services.
I pondered about having the whole feature be opt-in or opt-out, IMHO the current behaviour is generating enough issues on its own for this to be opt-out.

LGTM

Merged in master as of #298


'invalid WAV file (expected 'data' at byte 36)'

Firstly, thanks for making this library. I'm finding it very useful for a project I'm working on.
I'm having issues reading a couple of wav files, and am getting the error 'invalid WAV file (expected 'data' at byte 36)' when running the following line:
(int sampleRate, double[] audio) = WavFile.ReadMono(audioFile_path);
The audioFile_path is a valid path to a wav file, which worked fine before the repo was recently updated to use this custom wave file reader. The wav files I encountered this error with were from "The Ryerson Audio-Visual Database of Emotional Speech and Song" which you can find here: https://zenodo.org/record/1188976
I get the same error for any of the wav files of this database I've tried. For other datasets I'm using, I don't get this error. Is there something I'm doing incorrect or is this something you could possibly fix?
Regards,
Kevin

Hey Kevin,
Sorry to hear the new WAV reader isn't reading these files like it used to! On one hand I tried to get the new WAV file reader to be able to read sample rate out of the header and support 2-channel WAV files, but on the other hand this requires the header to be properly parsed and I suspect the WAV file you're reading doesn't strictly adhere to the format described in http://soundfile.sapp.org/doc/WaveFormat/ which I used to base the new WAV reader on.
I'll take a closer look at these WAV files and put the old function back in and/or modify the current function to ensure it can read these. The specific download link for the WAV files you referenced is https://zenodo.org/record/1188976/files/Audio_Song_Actors_01-24.zip
Note that the WAV reading method in Spectrogram 1.0 is here:
https://github.com/swharden/Spectrogram/blob/1.0.0/src/Spectrogram/Tools.cs
in a pinch you can add this function to your project (modifying it as needed to output double[] instead of float[])
I'll get this on NuGet later today. Thanks again for reporting it!

Thanks Scott! I appreciate the speedy reply. I'll use Spectrogram 1.0 until the fix. Thanks!

It looks like this error is caused because the Microsoft WAV file spec says that the 4 bytes at position 36 should be data but Apple WAV files use FLLR ("filler").

It seems this topic is addressed at length here.
For a simple fix I'll just remove the assert and allow these 4 bytes to be any characters, this should fix the problem.

Plot thickens...

After FLLR is a UInt32 that decodes to 4044, then the byte position is at 44.
4044 bytes later (at position 4088) are the letters data I was looking for.
The UInt32 following data decodes to 429230 (the number of samples in the file).
Then the actual audio data starts.
 Weird!

Just released Spectrogram 1.2.1 with an improved WAV file reader. I'm pretty sure this will do the trick! Let me know if you hit any snags 👍


cli: macOS unable to run anchor build --verifiable

It's been reported that mac users may get the following error
Error: Bad CPU type in executable (os error 86)

The user can successfully run anchor build, so it's expected this is a docker specific issue.

The user re-installed docker and everything now works. Classifying as user error. Closing.


Fix docs styles

[x] Fix linting errors
[x] Label has been added

Change information

@unix
Thank you for your advice. I've improved


Question :

Hello Sir,
Did you publish any research paper on this project. If yes, please drop a link to access that paper. It will be helpful in order to understand the project. Or any material which is related to this project which can help in understanding the project better.

No, I didn't publish any paper. It was just a fun project which I made in my free time. It's an open source project.


Please add a search bar to find the suitable emojis

The package is awesome. It will be better if it has a search bar just like in G-board keyboards.

I agree and I'm planing to integrate it already for a while but having trouble to find time. But don't worry, it's on my mind and maybe someone else has more time and is willing to create a nice PR for it :)


Fix typo within readme

Additionally, should the section header above this fix be Rebuild one package (one instead of on)?
:memo: Documentation

Fix typo in root readme

Thanks for the fix @hamlim 🙌
I made the one fix also 👍


big cpu use

I'm on version 1.10.1 facing the same issue.

I have the same issue on AMD laptop. I could provide more info if you need.
same HP Laptop

Thank you for reaching out! If this is still an issue for you, please contact us at support.getoutline.org and include the GitHub issue number so that we can better support your needs.
If you haven’t already, check out the Outline Support Site at support.getoutline.org for access to help articles and more.


new german translations

added the new german translations. While I was at it I adjusted some old ones.

Thanks very much for the new translations and also for the fixes! 🙌


Exponentiation on the web interface

Exponentiation does not seem to work in the web interface (Firefox).
As the web interface immediately converts the input into special symbols it is not possible to do inputs such as 2**3 as these get immediately turned into 2⋅⋅3, which then results in Unexpected token: 'Star'
Also I am not able to input ^2 for some reason as the circumflex gets immediately deleted.
The console version works fine.

Not sure why the circumflex would be deleted. I can't reproduce that on my machine. However, I now made sure a⋅⋅b gets parsed as a^b in the latest commit.

Thanks!
I think its because I'm on a german quertz keyboard and entering a circumflex would start to create a compose key input. Like the sequence ^ a results in â. If i actually want to type a circumflex, I would have to type ^ ^. The first circumflex to enter composing mode, and the second one to confirm the compose as "yes i would like a circumflex". The same thing is with keys like ` and ´
In the oninput event this behaviour seems to be handled with specifying the composed and isComposed properties in the event.
In total there are 4 oninput events that are triggered:
First: ^

{"isComposing":true,"composed":true,"inputType":"insertCompositionText","data":"^"}

Second: ^

{"isComposing":true,"composed":true,"inputType":"insertCompositionText","data":""}
{"isComposing":false,"composed":true,"inputType":"insertCompositionText","data":""}
{"isComposing":false,"composed":true,"inputType":"insertText","data":"^"}

Note that the circumflex immediately disappears after typing the first one - without any further interaction... So my guess would be that the whole composition cycle gets somehow cancelled and therefore deletes the "fake" circumflex that indicates that i am in the composing mode...
Here is some more info on that bizz.

I managed to reproduce these shenanigans:
<html>

<head>
  <script>
    function inp(e) {
      let b = document.getElementById("blub");

      e.target.selectionStart = e.target.selectionStart;
      e.target.selectionEnd = e.target.selectionStart;
    }
  </script>
</head>

<textarea id="blub" oninput="inp(event)"></textarea>

</html>

So i guess the problem is that when I enter the composing mode by entering the first circumflex, the selection of the textfield is immediately updated, which is interpreted by the browser as "the cursor moved so we need to cancel the composing"
If i wrap the changing of the selection in an if, then it works.
<html>

<head>
  <script>
    function inp(e) {
      let b = document.getElementById("blub");

      if (e.inputType !== "insertCompositionText") {
        e.target.selectionStart = e.target.selectionStart;
        e.target.selectionEnd = e.target.selectionStart;
      }
    }
  </script>
</head>

<textarea id="blub" oninput="inp(event)"></textarea>

</html>

Maybe inserting a similar if here solves the issue....
https://github.com/PaddiM8/kalker/blob/e50d398195bf2d575c4066050faf1553ffeb3937/web/src/KalkCalculator.svelte#L221-L235
But I am not at all aware of any side effects this may have, and I know nearly nothing about this whole key composing stuff myself, so take all of this with a grain of salt, should you or someone else decide to look into this rabbithole.

This would be a very quick fix for it, that seems to work reasonably well: https://github.com/MonaMayrhofer/kalker/commit/77bd037f26394ab9abb7e8d397bca096fd84afd3. Normally the circumflex would be somehow highlighted as being "fake", (normally underlined), but that would not be as straight forward to implement.
Well that's it for me for now, I don't know how many users are actually affected by this (i personally thought this was standard behavior but as you cannot reproduce it, it does not seem to be as standard).

@MonaMayrhofer That looks like a reasonable fix, neat. Feel free to make a pull request!


MMap without entrypoint

When manual mapping a DLL into a process, how do I map it in such a way so the entry point is not called? Apologies if I'm missing a flag/setting

Did it myself, no need for this


Documentation Request: How to update smart contract and frontend code

Is your documentation request related to a problem? Please describe.
Currently, it's unclear how to update smart contracts and frontend code

We are investing how to improve the developer workflow around updating smart contracts and frontend code.
After you create a project using BOAT, these are the folders and files you are interested in when updating a smart contract:
Using BuyMeACoffee smart contract as an example below
<project-name>
├── contracts
│   ├── src
│   │   └── BuyMeACoffee.sol          ← smart contract code
│   └──out/BuyMeACoffee.sol
│       └── BuyMeACoffee.json         ← output from "forge build" which contains the updated ABI
│
└── web/app/buy-me-coffee
    └── _contracts
        ├── BuyMeACoffeeABI.ts             ← copy of ABI from contracts/out/BuyMeACoffee.json
        └── useBuyMeACoffeeContract.ts     ← deploy address

Importing updated ABI to frontend code
After updating your smart contract code, run forget build in the contracts folder. This will create a json in the contracts/out directory.
The output json contains additional information. We only need the abi property from that json object. Let's use jq to extract just the abi property
# from the "contract" folder

jq .abi out/BuyMeACoffee/BuyMeACoffee.json

Take the output of jq and update web/app/buy-me-coffee/_contracts/BuyMeACoffeeABI.ts
Done with first step!
Deploying your smart contract and updating frontend code
Make sure you got all the environment variables squared away in contracts/.env and get some base sepolia eth from a faucet!
To deploy your smart contract,
# from the "contract" folder

source .env && forge script script/LocalContract.s.sol:LocalContractScript  --broadcast --rpc-url https://sepolia.base.org

In the long output, find the value for Contract Address.
Copy that value and update web/app/buy-me-coffee/_contracts/useBuyMeACoffeeContract.ts with the new address.
Outro
This is one of the more error prone steps. Take it step by step.
If you are new smart contract deployment, just try deploying the existing BuyMeACoffee contract and replace the contract address. After, try updating BuyMeACoffee.sol and get the new ABI in your frontend code.
We are thinking of ways to make this step easier in the future! Happy hacking!


RSS/Atom support for data-driven content

Being able to use RSS and Atom feeds for data sources (i.e., a getFeed function) could be extremely useful, especially when combined with a cron job to trigger a build/deploy.
It looks like there are a few go libraries which could handle this:

https://github.com/mmcdole/gofeed
https://github.com/SlyMarbo/rss
https://github.com/ungerik/go-rss

would be extremely useful

For what?
Hugo is and will be a static generator, I think. There is another issue about somehow generating pages "on the fly" (and I assume also not writing to disk) based on data files etc., but that will go into the normal Hugo "pipeline", which would end up in whatever output format you want (including RSS if you want).

I can think of lots of use cases off the top of my head. Building a news aggregator is pretty obvious. Or adding a "News" section to a site which pulls in articles off of Medium or from a Wordpress install. Or adding a bit of content to a sidebar instead of just a static link. Or list videos from your YouTube channel, or pictures from Instagram, etc. Maybe a company would want a "Careers" page which pulls their entries from Monster.com. Or pulling in the titles of recently active topics from a community forum.
And that's just the general purpose stuff. A lot of the uses will very be specific to the topic at hand. If you're making a page for a programming language, maybe you want to display the latest packages published to NPM/Crates/CPAN/PEAR/etc., or StackOverflow posts. Maybe a site for a musician would want to pull in a list of upcoming concerts from StubHub/TicketMaster/etc, or songs from SoundCloud. The more interesting use cases are almost always the stuff you don't anticipate.
Sure, this is stuff you could do manually by adding stuff to content/, but that requires specialized knowledge. Why force people to learn how a specific Hugo site works when adding content could be as easy as just adding a video to YouTube, a picture to Instagram, a blog entry to Medium, etc.? Besides, if you only have to add content in one place you don't have to worry about keeping it in sync.
I'm not sure why being a static generator would be a restriction. Just run it however often you want to check for new content. As an example, Planet Planet is a static generator. You just set up a cron job to automatically kick off a build… Travis CI makes it pretty easy without having to do anything locally, as long as daily is often enough, or if you prefer Netlify you can just GET a url from a cron job to kick off a build.

I'm not sure why being a static generator would be a restriction.

No, but it sets a scope for "what Hugo is". There is a saying about "doing one thing well..."

No, but it sets a scope for "what Hugo is". There is a saying about "doing one thing well..."

But this doesn't really alter the scope of Hugo. It's still a static site generator. All I'm suggesting is to add a getFeed function alongside the existing getJSON and getCSV functions.

getJSON and getCSV is already pushing it, and they fall into a more general domain than the getFeed thing. I don't want to maintain more getRemote something.

I don't think maintenance would be much of an issue; the infrastructure for retrieving remote content is obviously already there (for getJSON/getCSV), and any bugs in the feed parsing belong in a library you don't maintain, so they wouldn't be your responsibility. It seems like this should only add a few lines of code to Hugo, since the hard parts are either already part of Hugo or in the feed library.
I can understand not wanting to pull in another library and bloat the executable, but IMHO the benefits from this vastly outweigh the costs there.
Since Hugo is your project obviously the final decision is yours, but I would suggest that you ask the community (on discourse, I guess) for opinions before closing this. If people are against it, or generally don't care, it's probably safe to close it, but I have a feeling a lot of people would be extremely interested in this.


--no-validate-html and --skip-coverage together break test

Describe the issue
     Datatracker 11.0.0-dev test suite, 03 October 2023 01:14:35 PDT:
     Python 3.9.16 (main, Apr 12 2023, 12:03:39)  [GCC 10.2.1 20210110].
     Django 4.2.5, settings 'settings_test'
     Changing TEMPLATES[0]['OPTIONS']['string_if_invalid'] to '' during testing
     Changing INTERNAL_IPS to '[]' during testing.
     Running an SMTP test server on <IP_ADDRESS>:2026 to catch outgoing email.
     Loading factory-boy random state from .factoryboy_random_state
     Not validating any generated HTML; please do so at least once before committing changes
Traceback (most recent call last):
  File "/workspace/ietf/manage.py", line 15, in <module>
    execute_from_command_line(sys.argv)
  File "/home/dev/.local/lib/python3.9/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
  File "/home/dev/.local/lib/python3.9/site-packages/django/core/management/__init__.py", line 436, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/dev/.local/lib/python3.9/site-packages/django/core/management/commands/test.py", line 24, in run_from_argv
    super().run_from_argv(argv)
  File "/home/dev/.local/lib/python3.9/site-packages/django/core/management/base.py", line 412, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/dev/.local/lib/python3.9/site-packages/django/core/management/base.py", line 458, in execute
    output = self.handle(*args, **options)
  File "/home/dev/.local/lib/python3.9/site-packages/django/core/management/commands/test.py", line 68, in handle
    failures = test_runner.run_tests(test_labels)
  File "/workspace/ietf/utils/test_runner.py", line 1145, in run_tests
    failures = super(IetfTestRunner, self).run_tests(test_labels, extra_tests=extra_tests, **kwargs)
  File "/home/dev/.local/lib/python3.9/site-packages/django/test/runner.py", line 1048, in run_tests
    suite = self.build_suite(test_labels, extra_tests)
  File "/workspace/ietf/utils/test_runner.py", line 1083, in build_suite
    return super().build_suite(test_labels, extra_tests, **kwargs)
  File "/home/dev/.local/lib/python3.9/site-packages/django/test/runner.py", line 899, in build_suite
    all_tests.extend(iter_test_cases(tests))
  File "/home/dev/.local/lib/python3.9/site-packages/django/test/utils.py", line 260, in iter_test_cases
    for test in tests:
TypeError: 'NoneType' object is not iterable

Removing either --no-validate-html or --skip-coverage makes the test run start.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

We could look at this at the codesprint?


Implement AI component

fixes #635

Created a new PR with the same content but the conflicts resolved https://github.com/okfn/opendataeditor/pull/650


Support no-value cookies?

Apparently document.cookie supports cookies with no value via document.cookie = "foo". This is distinct on the wire (i.e. in the resulting HTTP headers) from cookies with value empty string (document.cookie = "foo=").
Is support for this needed, so that this API encompasses the entire cookie data model, or can we be stricter?
Related: https://github.com/whatwg/html/issues/804

One option (though it complicates the API slightly) would be to default to stricter https://tools.ietf.org/html/rfc6265#section-4.1 rules by default, but have a flag to permit relaxation to https://tools.ietf.org/html/rfc6265#section-5.2 rules when absolutely necessary for interoperability, e.g. ... {[' permissive ']: true} - similarly the read APIs could have an option to relax parsing ... {[' permissive ']: true}

Another alternative to all this would be a radically simpler API - navigator.getCookies().then(jar => {...} ) which is merely an async read of document.cookie, and nagicator.setCookie(string).then(() => {...}) which is merely an async write of document.cookie
@cramforce what do you think? how much hand-holding, parsing assistance, etc. is actually useful?

(that's more or less the original proposal by @slightlyoff  from https://github.com/slightlyoff/ServiceWorker/issues/707#issue-86384003 )

Forked that radically simpler API discussion to https://github.com/bsittler/async-cookies-api/issues/8

See also this discussion of nameless and/or valueless cookies:
https://www.ietf.org/mail-archive/web/http-state/current/msg00320.html
The cookie RFC says valueless set-cookie attempts are ignored, but in fact browsers do not seem to ignore them.

@abarth - do you have any idea whether valueless cookies are used in the real world?

@bsittler If they exist in the wild, they're exceedingly rare.  They certainly have cropped up at least once in the past.  If you're defining a new API for cookies, I wouldn't worry about them.  It's debatable whether folks implementing existing APIs (i.e., document.cookie and Set-Cookie) ought to worry about them.

The new explainer outlines a more restrictive API which disallows both reading and writing no-value cookies. Some of the other inconsistencies mentioned here are implicitly addressed by that outline (character set: always UTF-8 for reading and writing/USVString from script perspective, max-age: not present in the proposed API for writing cookies, multiple occurrence of the same attribute: not possible in the proposed API for writing cookies) but the rest still need to be addressed.

Fixed explainer link

Please stop spamming my inbox with notifications that you edited a post :(. We can all just see the new post...

Will do, didn't realize!
On Jul 27, 2016 10:39, "Domenic Denicola"<EMAIL_ADDRESS>wrote:

Please stop spamming my inbox with notifications that you edited a post
:(. We can all just see the new post...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bsittler/async-cookies-api/issues/1#issuecomment-235661902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAD3R8Yq9S6wCtz36W4tHP4DpmluD9b2ks5qZ5e2gaJpZM4Hpuvz
.

Further reading of the cookie compatibility results from https://inikulin.github.io/cookie-compat/ make it fairly obvious that there is de-facto standard behavior for Set-Cookie with no '=' across all browsers tested except Safari. Specifically, it is treated identically to the same Set-Cookie prefixed with '=', and updates the cookie with the empty-string name. I will go ahead and follow the majority behavior here in the polyfill and assume the spec will probably be changed to match that.


$Call doesn’t work with unions of instance methods

One surely expects that f() is assignable to $Call<typeof f>, but in
fact this is not always the case:
// @flow
class Foo { type(): "FOO" { return "FOO"; } }
class Bar { type(): "BAR" { return "BAR"; } }
declare var x: Foo | Bar;
const xType1: "FOO" | "BAR" = x.type();
const xType2: $Call<typeof x.type> = x.type();

This is true in spite of the fact that Flow can assign precise types to
x.type; the following declarations have no error:
class Foo { type(): "FOO" { return "FOO"; } }
class Bar { type(): "BAR" { return "BAR"; } }
declare var x: Foo | Bar;
const xType1: () => ("FOO" | "BAR") = x.type;
const xType2: (() => "FOO") | (() => "BAR") = x.type;

It seems to be fixed now


how can I prevent form submit on ENTER especially when add-from-autocomplete-only="true" ?

Here's the plunker http://plnkr.co/edit/QlQz7b91Gau9hwD35Obc?p=preview - you can easily type anything in (ie. test12345) cancel autocomplete list and hit Enter - the form will get submitted - how to prevent that? I want to keep default behaviour of the form, so it can be submitted once you hit ENTER on other controls, just not inside tagsInput (in this case with add-from-autocomplete-only="true").

+1


Add links to good gazetteers to help for Transcribers

https://www.genuki.org.uk/gazetteer
https://www.visionofbritain.org.uk/expertsearch
gazetteer.org.uk

May I fly a kite?
We now have a Gazetteer of our own with Latitude and longitude. In transcription etc we can use a Locate button to open Google maps and see the place. In Validation we make sure that the POB is valid and in our database (unless we cant).
If this locate facility was added to the person in a household in the search results when Birth Places are displayed to the researcher, then the researcher could see the Place on Google Maps.
Geoff

Is there any further need for this?

I don't see a need for the original story - but there doesn't seem to be a story covering Geoff's suggestion, so I'll make one.

The original story is no longer required.
We have created a Gazetteer which will become very comprehensive, and not restricted to the UK, over time. The Handbooks recommend three other Gazetteers, two of which were used as sources for our original version.
There is no longer a need for other links from FreeCEN. Our Gazetteer is gaining in popularity and credibility and we should back it.
Geoff

Thanks, Geoff - It is closed, and I have made the story for your suggestion that we link from the place shown to the researcher to google maps - something like this already exists in FreeREG  - I will comment more on that story.


track issue with menu max or maya

not sure if it's max or maya. but if we parent a new menu entry to an existing menu on startup. the whole menu is removed.

pyblish can correctly add to maya menu, so it's likely max https://github.com/pyblish/pyblish-maya
also adds to maya menu https://github.com/hannesdelbeke/maya-plugin-template

believe it's maya after all

you can't add to existing menus. e.g. the Windows menu, named mainWindowsMenu or it will be empty if plugin loads on startup.

hack from pyblish https://github.com/pyblish/pyblish-maya/blob/893dee39aef34aa7daa7c3e5593247abb8282731/pyblish_maya/lib.py#L147C6-L147C6

relates to extending menus https://github.com/hannesdelbeke/unimenu/issues/35


Remove unnecessary null check

This PR didn't automatically add anyone as reviewers. I have a feeling this PR is @blowdart's territory!

Why do you think it's unnecessary? :) Or what actual harm does it do here?

There's absolutely no harm here. I just thought since logger is being set in constructor, the null check could be dropped for a tiny perf improve.

There's absolutely no harm here. I just thought since logger is being set in constructor, the null check could be dropped for a tiny perf improve.

It improves the clarity of the code. Which I'm told is important when it's security related - the extra null check is misleading,


[BUG] pivpn script does not return proper exit code

In raising this issue, I confirm the following:

[x] I have read and understood the contributors guide.
[x] The issue I am reporting can be replicated.
[x] The issue I am reporting is directly related to the pivpn installer script.
[x] The issue I am reporting isn't a duplicate (see FAQs, closed issues, and open issues).

Describe the bug
When there is an error which should cause the pivpn script to produce a non-zero exit code, 0 is returned instead.
When running the following command: pivpn revoke --yes michael123
The following output is produced: You passed an invalid cert name: 'michael123'!
Then, when running echo $? the output is 0
To Reproduce
Steps to reproduce the behavior:

Run pivpn revoke --yes michael123
Then Run echo $?
The contents of $? should be 1 not 0

Expected behavior
The exit code from the script in this context should be 1
Desktop (please complete the following information):

VPN Protocol: Open VPN
OS: Raspbian buster
Version [e.g. 22]

Additional context
I searched for the error message and found it in pivpn/scripts/openvpn/removeOVPN.sh.  Lines 120-121.  There is clearly an exit 1 statement, but the pivpn script is not passing along the exit code.
In the file pivpn/scripts/openvpn/pivpn.sh the function that loads removeOVPN.sh is on line 45.  On line 46 the exit code is hard coded to exit 0 instead of exiting with the exit code of the called script.  Perhaps all those exits in the main script that follow a sub-script should be exit $? to pass along the exit codes.

See PR #1232

See PR #1232

Merged to master 7fdbe44df5319b7c99a4481c754acd8c0c6c98fa closing.

Merged to master 7fdbe44df5319b7c99a4481c754acd8c0c6c98fa closing.


Wrong link in case description

On page 7 of the case description, the link to the github repository is pointing to the offline case, and not to this repository.

Thanks, fixed with  5795cd4