Can't program central module via Mac OS

Hi! I was able to connect multiple peripherals with some help 2 days ago. I was a linux machine then, now I've switched to Mac OS and am unable to run the same code for central module which ran perfectly fine on Linux 2 days ago.
I am assuming it's related to the gcc version, but not sure
Can anyone tell why is it so? The program doesn't even reach the on_sync callback where the scanning is initiated

can you provide some more details what exactly does not work? are you not able to build, flash or it does not run after flashing?

btw, if it does not run try with newt debug and provide us backtrace (bt command). if it does not build/flash then provide appropriate log with an error.

Hi! The programs builds and loads as usual. The device is working properly for other programs such as the nrf52_adc and peripheral app.
My observation(guess) is that it never reaches the on_sync callback which calls the blecent_scan. What more should I tell you please let me know?
It was working just fine when I compiled the same in Linux 2 days ago.

I can share my code if you want to? Rather, it's in a repository in my profile. It can be found here

Any help would be appreciated. Sorry for the urgency @andrzej-kaczmarek

As requested, here is the backtrace:
(gdb) bt #0  __assert_func (file=file@entry=0x0, line=line@entry=0,      func=func@entry=0x0, e=e@entry=0x0)     at repos/apache-mynewt-core/kernel/os/src/arch/cortex_m4/os_fault.c:137 #1  0x000160a4 in ble_hs_event_start (ev=<optimized out>)     at repos/apache-mynewt-core/net/nimble/host/src/ble_hs.c:474 #2  0x000089ba in main ()     at repos/apache-mynewt-core/apps/blecent/src/main.c:372

so as you can see it stops on an assert in following function:
468 static void
469 ble_hs_event_start(struct os_event *ev)
470 {
471     int rc;
472
473     rc = ble_hs_start();
474     assert(rc == 0);
475 }

the only reason why ble_hs_start() can return an error is when ble_gatts_start() returns an error which usually occurs due to out of free memory. so the quickest solution here would be to step through ble_gatts_start() with debugger and see where it fails.
also, if the same code works fine on Linux I suspect there is difference in either Mynewt version (on Mac you clearly have 1.3.0) or target configuration (newt target config show <target>) so you should also check for differences there.

I think the reason why it fails is following fix missing in 1.3.0: https://github.com/apache/mynewt-core/pull/700 - please apply it and retry.

Hey! Thanks a lot! It works perfectly now :D
I hope this is the only fix missing in 1.3.0


Added graceful reload on SIGHUP.

This PR adds graceful reload signal handler. Closes #325.
Signed-off-by: Pavel Kirilin<EMAIL_ADDRESS>

Codecov Report
Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 73.21%. Comparing base (4ee8312) to head (11d9ca7).

Files
Patch %
Lines

taskiq/cli/worker/process_manager.py
0.00%
5 Missing :warning:

taskiq/cli/worker/run.py
0.00%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #330      +/-   ##
===========================================
- Coverage    77.88%   73.21%   -4.68%
===========================================
  Files           61       61
  Lines         1800     1803       +3
===========================================
- Hits          1402     1320      -82
- Misses         398      483      +85

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Version control window lists all global classes

Godot version:
3.2-alpha, 24e1039
OS/device including version:
Windows 10
Issue description:
When attempting to select a VCS, all global classes exposed via class_name are listed regardless:

Steps to reproduce:

Create global classes with class_name
Go to Project → Version Control → Set Up Version Control
See all classes listed in the project.

Minimal reproduction project:
vcs-global-classes.zip

I can confirm this on commit https://github.com/godotengine/godot/commit/24e1039eb6fe32115e8d1a62a84965e9be19a2ed.

I wonder what kind of VCS Select an available VCS is

Likely this Git plugin, so CC @IronicallySerious I guess.

The "Select an available VCS" refers to a GDNative object placed in the project folder that extends EditorVCSInterface. @Zylann
To use the integration you will have to extract this .zip file in your project folder.
Right now it lists all global scripts available because since the VCS integration is new, I kept things as simple as possible. I would expect the dialogue box to raise an error in the output if you selected a script that is not the Git plugin so the VCS functionality stays hidden.
I would probably fix in this line here: https://github.com/godotengine/godot/blob/24e1039eb6fe32115e8d1a62a84965e9be19a2ed/editor/plugins/version_control_editor_plugin.cpp#L384
I can get this done after Monday because of my exams, but if someone is interested they can have a look. If we are able to detect what class a GDNative plugin extends then it is a simple if statement because all VCS plugins will extend EditorVCSInterface


Commands are not Statements

https://github.com/sqwishy/vim-sqf-syntax/blob/8663c3c55c6cd903e87458c620667af56e7ff7fd/syntax/sqf.vim#L835
Those are pure SQF commands. Everything is in fact, but those provide no syntax structure.
I much prefer style of now-outdated https://github.com/KoffeinFlummi/vim-sqf/blob/master/syntax/sqf.vim, it's closer to how SQF works internally and is understood by someone who worked/works in SQF a lot.
I can PR some changes if they'd be welcome.

Some of the categorization I've done here is arbitrary. At some point I think I tried to use categories to improve diversity in highlighting. Even if they were logically inappropriate, the greater use of colour was ultimately helpful for me.
Feel free too propose a change. I might feel sad if things seem less colourful but I also might merge it anyway if I figure it'll be helpful to the three people who use this.
Alternatively, that file is generated by an ugly python script using the output of supportInfo. I have been meaning to version control it. If I do, it's easier for someone else to produce their own highlighting definitions and maintain them as new versions of Arma are released. If you think that'd be more helpful to you, let me know.

Whatever you prefer, your project. And that's why forks exist, for picky people like me. :P
Script would definitely be helpful.

I've put the script in the repo.
https://github.com/sqwishy/vim-sqf-syntax/blob/dc4055f97b2f89e64f351b551224260dbb3fe7cf/misc/gen-syntax.py
You can probably do what you want by modifying the definitions in WELL_KNOWN. Hopefully it's useful. I'm interested to see what you'd like to change.


FYI: filename encoding documented - full list of flags

Hello,
FYI, I looked at the Reolink FW and figured out the encoding of the file names in its entirety.
Of interest in particular would be the list of attributes:
https://github.com/sven337/ReolinkLinux/wiki/Figuring-out-the-file-names#attributes

@sven337 that is very instresting, thanks a lot for sharing!
I will defenitly look into this to improve the Reolink itegration.
At the moment a bit bussy with some other Reolink imporvements, but will keep this issue open untill I find some time to work on it.
Did you perhaps also look into the file names of the Reolink Home Hub?
That uses a even newer file naming standard from which I did not figure out what the flags mean....

Let me know where to find the firmware and show me the filename pattern, and I may be able to figure it out.

The firmware is on the reolink download center: https://reolink.com/download-center/?srsltid=AfmBOor3BU5F6iWv9p1mMWavhnPrtjGFN2QigYLOH4eaepdvwtnU-eMS
Device name: Reolink Home Hu
Hardware version: BASE_WENNT6NA5
I will give you a filenmae pattern as soon as possible, I don't have my Home Hub plugged in right now and am working on way too many issues at the same time at the moment...

Thanks, I have the firmware bits, and it looks like the relevant functions are indeed different.
I need to see the pattern to help with RE. Please tell me everything you know/have and what you're missing, and I should be able to RE that.

@sven337 sorry for the delay, this is the filename of a recording from the Reolink Home Hub (I replaced the UID and camera name):
"/mnt/sda/<UID>-<NAME>/Mp4Record/2024-08-27/RecM02_DST20240827_090302_090334_0_800_800_033C820000_61B6F0.mp4"
First I thought the last 6 chars would be the tags so I made a list of those tags for diffrent events:
21DCCD -<PHONE_NUMBER>01110011001101 - pet + person
182721 -<PHONE_NUMBER>10011100100001 - person
18DF13 -<PHONE_NUMBER>01111100010011 - motion + person
188FF9 -<PHONE_NUMBER>00111111111001 - pet
17DD6E -<PHONE_NUMBER>01110101101110 - pet
156701 -<PHONE_NUMBER>10011100000001 - motion
1F25E5 -<PHONE_NUMBER>10010111100101 - motion

But I could not find a logical pattern in this....

I will defenitely use the decoding you wrote, it looks way nicer.
May take a while untill I get to it though....
Lots of things I want to implement and improve.

For a Argus Track (dual lens camera) the recording on the Home Hub has the following names:
RecC02_DST20240623_163915_163926_0_380_200_033C800000_8655E.mp4
RecE02_DST20240623_163915_163925_0_780_438_033C820000_F6362.mp4
RecM02_DST20240623_163915_163924_0_F00_870_033C820000_34B93A.mp4
RecS02_DST20240623_163915_163924_0_380_200_033C800000_7EB2A.mp4

For the sub/main stream of both lenses

Here are my findings: https://github.com/sven337/ReolinkLinux/wiki/Figuring-out-the-file-names#filename-structure-for-reolink-home-hub
as far as I can tell and just like for camera, the last hex group is the filesize!
In my link you can find the flags you are looking for:
flags_mapping_v2 = {
        'resolution_index': (32,    7),
        'tv_system': (31,           1),
        'framerate': (24,           7),
        'audio_index': (22,         2),
        'ai_pd': (21,               1),  # person detection
        'ai_fd': (20,               1),  # face detection
        'ai_vd': (19,               1),  # vehicle detection
        'ai_ad' : (18 ,             1),
        'ai_other' : (16,           2),
        'encoder_type_index': (15,  1),
        'is_schedule_record' : (14, 1),
        'is_motion_record': (13,    1),
        'is_rf_record': (12,        1),
        'is_doorbell_record': (11,  1),
        'picture_layout_index': (4, 7),
        'package_delivered' : (3,   1),
        'package_takenaway': (2,    1),
        'package_event' : (1,       1),
        'upload_flag' : (0,         1),
}```

@sven337 thank you very much for figuring this all out, I wrote some initial code here:
https://github.com/starkillerOG/reolink_aio/blob/6d22f8edaa2baf6c3f8754027e292e17f5d8fe29/reolink_aio/typings.py#L403-L544
It works on "normal" Reolink cams, but on the Home Hub it does not work.
I noticed the hex_flag is always 033C800000 no matter what type of events triggered the recording.
This may be a firmware bug in the Home Hub though....  not sure.

As far as I can tell your implementation of flags isn't quite correct: the home hub and cameras use different flags.
Version 2 and 3 (I have both on my Trackmix, 3 is after the recent firmware upgrade) on cameras differ only by is_doorbell_press_record.
In fact in my table you can track all 3 known versions of flags on cameras.
The table of versions for the hub is different (it's a different namespace, in a way).
Your flag is sometimes 0x33C820000 in your own examples, which IIRC corresponds to ai_other (don't ask me what that is! it's not animal, not face, not vehicle and not person....). But I agree it is strange that they all use the same.
The resolution index being the same value despite resolution being obviously different is also a ????, but I am reasonably certain I got this right. (it's possible that there are different resolution indices for different stream types -- I haven't checked)

Note, the cameras have been updated to a new version of the encoding, version 9.
It is not the same as the home hub (!!!).
Support for the new encoding is here:
https://github.com/sven337/reolinkapipy/blob/af748158785774c556d4b799445103421bd757c3/examples/video_review_gui.py#L53
I haven't yet decoded the extra set of flags, they're always zero on my camera anyway so I do not care much. Probably same flags as the home hub (package events).

@sven337 I have updated the decoding of the recording names in the reolink_aio lib:
https://github.com/starkillerOG/reolink_aio/blob/cbcc1ab32832afc049adbdd57ee3cca89cd8a3aa/reolink_aio/typings.py#L430-L563
I think it should now work a bit better.
The most noticible improvement I have made is to reverse the binary hex value and adjust all mappings acordingly. That makes sure the first bit accross all versions is always the resolution_index and so on, newer version just append more stuff at the higher bits.
Therefore the offset does not need to be adjusted between versions anymore.
https://github.com/starkillerOG/reolink_aio/blob/cbcc1ab32832afc049adbdd57ee3cca89cd8a3aa/reolink_aio/typings.py#L465
https://github.com/starkillerOG/reolink_aio/blob/cbcc1ab32832afc049adbdd57ee3cca89cd8a3aa/reolink_aio/typings.py#L471
I am not so good in all the binary operations, so this can proably be done more ellegantly, faster and more compact, but in any case this works and should make the decoding a lot more resilient against future version changes.

Nice job, it is better to have flipped things indeed. My version is the product of the reverse engineering but I wasn't exactly focused on doing something nice either, I only wanted something that worked :)


WebSocket connection to error

Thank you very much for any help

I'm getting the same exact error


Donations verification service has stopped working

Describe the bug
It seems that there are a few donations that are missing in the UI.
User reported in Discord:
https://discord.com/channels/679428761438912522/1236022013295071313/1236022550744793098
https://gnosisscan.io/tx/0x2fd4aa0a5cb899954e2b238bde98aa69161234faf757e6a4812a4e7584e121f0
Amin said that the donation is showing in the DB, however, it is still missing in the UI
Donation was made to this project:
https://giveth.io/project/diamante-luz-center-for-regenerative-living-0
User reported in Discord and DMs:
https://discord.com/channels/679428761438912522/1236329846456713276/1236330045983952968
https://gnosisscan.io/tx/0xfa65ef0a52e2f3b96c5802dcee4783858511989b7235035e8cab4d527fa15a1a
Donation was made to this project:
https://giveth.io/project/skatehive-skateboarding-community
I will add more cases to this issue as they come up across the support channels.

this was fixed yesterday. @maryjaf pls test and close

We can close this one, I tested yesterday on production and made at least 12 donations with no issue


Animated transitions: research spike

Timebox 1d:

connection to the lifecycle events
impact on performance
older browsers support (hi, IE11) - browser APIs / external dependencies
impact on the Vaadin.Router API (what new properties / methods are needed)
how to test
plan the further work

Prototyping result in the branch: https://github.com/vaadin/vaadin-router/tree/spike/animated-transitions

Lifecycle Events

__setOutletContent needs to be changed, and probably split into two methods: a method to remove old content, and a method to insert a new one. The first of those should return a Promise, which resolves once the animation for removed view has been triggered.
We should consider using lifecycle callbacks for this, so that we could perform some async tasks before removing elements from the DOM

Impact on the API:

animate: true option added to the route config is the simplest option. This would run animations, if any.
The opening and closing attributes (names TBD) exposed on the view element
User can apply the animations to the view component using the following CSS:

@keyframes fadeOut {
  0% {
    opacity: 1;
  }

  100% {
    opacity: 0;
  }
}

:host([closing]) {
  animation: 1s fadeOut;
}


Rework API image selection tags

such that the language:<lang> tags are gone, given limited usefulness, and a
new tag set with both dist: and group: is included in order to enable, e.g.:
language: ruby
group: edge
dist: precise

:+1: LGTM :heart: :sparkles:


Make Configs Consistent

Currently we have configs with a mix of - and _. For example, we use no-weight-tying but output_layer_init_method. I don't particularly care which way we decide is the correct way, but we should be consistent across the library.

Hello! I would be more than happy to work on this issue.

Welcome @austinburnett , thanks for offering to work on this!
So for this issue--actually what's currently done in the repo is that either - or _ in an argument are accepted, and the hyphens are normalized to underscores here: https://github.com/EleutherAI/gpt-neox/blob/b608043be541602170bfcfb8ec9bf85e8a0799e0/megatron/neox_arguments/arguments.py#LL186C13-L196C56 . So we currently are consistent internally on which format is used (underscores are used for all args in NeoXArgs which matches neox_arguments.md).
Would an acceptable solution be to leave things as they are now but just document more clearly in the relevant readme that you can write args with hyphens or underscores in YML files? That's what I'd tend toward personally, if it's acceptable.

So for this issue--actually what's currently done in the repo is that either - or _ in an argument are accepted, and the hyphens are normalized to underscores here: https://github.com/EleutherAI/gpt-neox/blob/b608043be541602170bfcfb8ec9bf85e8a0799e0/megatron/neox_arguments/arguments.py#LL186C13-L196C56 . So we currently are consistent internally on which format is used (underscores are used for all args in NeoXArgs which matches neox_arguments.md).
Would an acceptable solution be to leave things as they are now but just document more clearly in the relevant readme that you can write args with hyphens or underscores in YML files? That's what I'd tend toward personally, if it's acceptable.

Yeah absolutely. Honestly, even just changing all the documentation to be consistent would probably be sufficient.

I believe this would be an acceptable solution as well. I can note in the relevant doc that the '-' args may be deprecated. For the sake of clarity, by consistency you mean modifying everything to have '_' args instead of '-'.

@austinburnett i have a weak preference for making - the encouraged separator, but otherwise yeah you got it completely.

I believe this would be an acceptable solution as well. I can note in the relevant doc that the '-' args may be deprecated. For the sake of clarity, by consistency you mean modifying everything to have '_' args instead of '-'.

I have an extremely weak preference for the other way around, but it really doesn't matter.

Alright, sounds good. I'm working on it now. I'll stick with the original plan of converting '-' to '_'. My plan is to develop a regular expression to take care of it.

I just opened up a pull request for this issue. I believe I have completed all 1 & 2. However, I'm unsure if task 3 is complete.


DiscordGo: Encountering HTTP 400 Bad Request Error for Button Components Without Emojis

Hello DiscordGo maintainers,
I've encountered an issue with the DiscordGo package (v0.27.1) related to using buttons in messages. Despite not having any emojis in the buttons, I am consistently receiving an HTTP 400 Bad Request error.
This is one example of my message
 &discordgo.MessageSend{ 		Content: content, 		Components: []discordgo.MessageComponent{ 			discordgo.ActionsRow{ 				Components: []discordgo.MessageComponent{ 					discordgo.Button{ 						Label:    "something", 						Style:    discordgo.PrimaryButton, 						CustomID: "something", 					}, 					discordgo.Button{ 						Label:    "something else", 						Style:    discordgo.SecondaryButton, 						CustomID: "something_else"", 					}, 				}, 			}, 		}, 	}
Here is an example of such error message:
HTTP 400 Bad Request, {"message": "Invalid Form Body", "code": 50035, "errors": {"components": {"0": {"components": {"1": {"emoji": {"name": {"_errors": [{"code": "BUTTON_COMPONENT_INVALID_EMOJI", "message": "Invalid emoji"}]}}}}}}}}
This error occurs even when emojis are not used in the button components. Here's a brief overview of the scenario:

Using DiscordGo to send messages with buttons.
No emojis are included in the button components.
The error appears upon message sending.

I would appreciate any insights or solutions to this problem. Could this be an issue with the library handling button components without emojis, or am I missing a step in the implementation?
Thank you for your assistance.
Best regards,
Rosa17a

This is a known problem and has been resolved in f70a01544f56a912f2528998ff449d22a708fd25. However, since it's not tagged yet, you'd have to use the @master version.


merge substrate-bn branch into master

@NikVolf could you cargo owner --add github:paritytech:core-devs?

@ordian done


fix "Manual Input" shape in flowchart.xml

Now that I've made and fixed the edits, I might as well make a PR. :)
demo

Pulled via main repo. Thanks for the fix!


dirty rectangle of text cursor not redrawn after DPI scale change

When entering the GoGi Preferences menu and editing the LogicalDPIScale from 1.0 to 1.1 by typing [backspace] (to remove the 0 from 1.0) and the typing 1 and pressing [enter] results in a change of the DPI, but leaves the black rectangle used as text cursor as a visible artefact on screen. See screenshot below:

Forcing a full refresh (by e.g. fullscreening the Preferences menu) fixes the rendering issue, so this does seem to be a dirty rectangle that needs to be redrawn but isn't. The logical state is correct (but not the state drawn to screen).
This was run on version v0.9.10 of GoGi (opening the Preferences menu from the colors example program).

This is directly changing the scaling without calling the appropriate update, probably.

fixed :)


⚠ ClamAV has degraded performance

In 2e030d4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 65 ms

Resolved: ClamAV performance has improved in 8526f30.


feat: Add format to PT MONO font

Closes #1803

I think we can merge this one without waiting for more approvals, the fix is pretty straightforward.


DF Manual Rolls: Damage rolls not working in PF2e system

Module
Manual Rolls v2.4.0
Describe the issue
When rolling damage rolls in PF2e v4.6.x (post IWR release)
To Reproduce
Steps to reproduce the behavior:

Roll an attack from a weapon or spell (works as it should)
Click on 'Damage' in spell/attack card
Damage is rolled by system dice, rather than prompting for manual input

Expected behavior
Prompt window to input manual dice results should appear before printing damage totals.

Update to Reproduction steps: Sometimes spell card damage prompts correctly; can confirm Scorching Ray single action prompts, Ray of Frost damage does not, Heal 2-action on Living does not

Unfortunately PF2 still uses this deprecated synchronous rolls. To deal with this you will need to enable Legacy mode in the module settings.

Unfortunately PF2 still uses this deprecated synchronous rolls. To deal with this you will need to enable Legacy mode in the module settings.

Friendly FYI: this isn't true and hasn't been for about a year now. Though from looking at the module's current implementation, I suspect support won't be extended unless Foundry itself switches to a similar implementation.

@stwlam based on the issues that this user (#453) has reported, PF2e is indeed still using synchronous rolls for their "critical damage rolls" and some "spell damage rolls".

@this-gavagai Doesn't a Die by its lonesome also invariably hit an _evaluateSync method?

Doesn't a Die by its lonesome also invariably hit an _evaluateSync method?
Not here in RollTerm, at least not that I'm seeing. As to why, I believe you've hit the nail on the head below.

All pf2e system rolls are async without exception. I believe the issue with the module is that it expects all dice to be represented in a Roll's top-level terms with the lone exception of PoolTerms. Core Rolls incidentally meet this expectation, but pf2e system DamageRolls contain PoolTerms that may also have constituent Rolls with dice not among their top-level terms.

I think this is right. Specifically, every time the wrapped DiceTerm.prototype._evaluateSync method is getting called, it seems the consequence of L91 here:
https://github.com/flamewave000/dragonflagon-fvtt/blob/9a307430fdb7b0d9f497f1d9d72ec941b671b237/df-manual-rolls/src/ManualRolls.ts#L91-L97
Notably, when evaluating 1d6 + 1, the property this.rollPrompt is undefined. When evaulating 1d6, however, it is defined properly. I think that might be because the check here:
https://github.com/flamewave000/dragonflagon-fvtt/blob/9a307430fdb7b0d9f497f1d9d72ec941b671b237/df-manual-rolls/src/ManualRolls.ts#L69-72
...is looking for DiceTerms and not larger groupings.

I figured out a way to fix this using a recursive method to search for DiceTerms inside the terms instead of relying on the top-level term being a DiceTerm.
However, I don't have a Linux device on hand to build the project etc. so I was testing directly on the Foundry data module.
This is what the function looks like:
static setRollPromptRecursively(obj, rollPrompt) {
          if (obj instanceof DiceTerm) {
            // If the object is a DiceTerm, set the rollPrompt
            obj.rollPrompt = rollPrompt;
          } else if (typeof obj === 'object') {
            // If the object is an object, recursively check its properties
            for (const key in obj) {
              if (obj.hasOwnProperty(key)) {
                ManualRolls.setRollPromptRecursively(obj[key], rollPrompt);
              }
            }
          }
        }

You would then replace the following code:
 for (const of this.terms) {
 	if (!(term instanceof DiceTerm)) continue;
 	(<any>term).rollPrompt = rollPrompt;
 }

by this:
for (const term of this.terms) {
            ManualRolls.setRollPromptRecursively(term, rollPrompt);
            }

This will make the module work for damage rolls in my experience, so if someone can do a pull request to fix this, feel free.


Task Queue name incorrect in history details

this is not the task queue name

@canvanooo What should we do about this? Right now, we're using the names as they're defined in the API.

Fixed in #304!


feat: add button variant to pfe-autocomplete

pfe-autocomplete
tldr;
The Red Hat Ecosystem Catalog (RHEC) wants to leverage pfe-autocomplete while keeping the same look and feel of its existing search bar design, which includes the search button to the right of the input field. Adding that variant to the existing pfe-autocomplete component.
Preview

Link(s) to demo page(s) where this element can be viewed:

Demo

What has changed and why
Link to discovery documentation (should contain all the planning and requirements for this work):

Discovery

Testing instructions

Go the demo link above and run through the following base scenarios on the textual button example:

Verify that you only see the textual button, not the icon button
Verify that the button is disabled until you start typing in the input field
Verify that clicking on an item, selects that item, and closes the drop list
Verify that that clicking on the clear icon clears the input and disables the button
Attach an event listener to pfe-autocomplete to verify that search-event is being triggered on click and capturing the search value.

document.querySelectorAll('.static')[1].addEventListener('pfe-autocomplete:search-event', (e) => console.log(e.detail.searchValue))
Browser requirements
Your component should work in all of the following environments:

[x] Latest 2 versions of Edge
[x] Internet Explorer 11 (should be useable, not pixel perfect)
[x] Latest 2 versions of Firefox (one on Mac OS, one of Windows OS)
[x] Firefox 68 (or latest version for Red Hat Enterprise Linux distribution)
[x] Latest 2 versions of Chrome (one on Mac OS, one of Windows OS)
[x] Latest 2 versions of Safari
[x] Android mobile device (such as the Galaxy S9)
[x] Apple mobile device (such as the iPhone X)
[x] Apple tablet device (such as the iPhone Pro)

Ready-for-merge Checklist
Check off items as they are completed.  Feel free to delete items if they are not applicable.

[ ] Expected files: all files in this pull request are related to one request or issue (no stragglers or scope-creep).
[x] Tests have been updated to cover these changes.
[x] Browser testing passed.
[x] Repository compiles and tests pass.
[x] Changelog updated (not needed for documentation updates).
[x] Documentation (README.md, WHY.md, etc.) updated or added.
[x] Approved by designer.

Merging
Please squash when merging and ensure your commit message uses conventional commit formatting.
Be sure to share your updates with the<EMAIL_ADDRESS>mailing list!

@kylebuch8 this is ready for ya! 👀  Two things...I thought I branched off of master, but for some reason I'm seeing all these commits related to pfe-button that I need to clean up. Also, it looks like the build is failing because of the husky version I'm using? I have to take a look at that tomorrow too. I already ran npm install to update my lock file as recommended, but it didn't work 😞

@kylebuch8 meow 🐱 have you had a chance to look into this?


Adding Temporary debug logs to vendored installer destroy code

In case we want to add some debug statements to installer destroy code for HIVE-2297

/cc @abutcher
This does two things:

Disable the "don't change clusterMetadata once set" webhook validation.

This should allow us to run this code in stage without breaking cluster service. That breakage was because CS a) vendors the old CRD, and b) is accidentally "editing" out the new platform.aws field via the ol' round trip bug. What should happen now is that CS will remove the new field, but hive will put it right back.
This change will cause us to fail unit and coverage CI because we haven't updated the unit test cases accordingly.

Add some debug messages to vendored installer code.

This will hopefully give us some breadcrumbs to track why the DNS cleanup code is not being executed.
Because this is hacked into vendored code, it will break verify.
The plan is to ignore the CI failures and just merge this. AppSRE will build an image tagged at commit X, which we will explicitly deploy to stg/int via sha.

/lgtm

CI failures are as expected. Merging...


Using certificate path with "classpath:" doesn't work, if you want to load certificates from a JAR

Not sure if it's a bug of just expected behavior. If it is, IMO should be documented.
Maybe it would be useful to use Zip File System Provider in case if user wants to load certificates from JAR.

#159 allows a single cert to be loaded from the classpath. I think that's about as far as the feature should go (it's ultimately a workaround for systems using self-signed certs but not having those certs available on developer machines).


Determine Best DB

Need to decide between MongoDB and SQLite. Use this thread to document thoughts etc. until one is decided upon.

First impressions...
MongoDB

Distributed files

Backups can be more involved, but...
Built-in "connect from anywhere" functionality

Ease-of-use for devs: Easy and intuitive
File size: 7.2 MB (for 300 records)

SQLite

Singular file

Share by passing around a single (but LARGE file)
Retrieving data from anywhere would be tricky, so..
Should be packaged with application

Ease-of-use for devs: Not so intuitive, but uses SQL language (which may be more common)
File size: 1.1 MB (for 300 records)

Notes from speaking with a CS professor...

SQL has a lot of built-in functionality (aggregate functions, statistical analysis, joins, etc.)
MongoDB requires everything to be handled client-side
MongoDB is often faster (can access and insert records faster)
SQLite requires handling a very large file...

Anyone who wants any data (even just a single record) would need access to this extremely large file
MongoDB would only return the requested records

MongoDB is more scalable

Shards/clustering allows for the database to live on multiple servers (for backups or for expanded space)
Allows fields with different data (useful for grabbing data from many sources)

Conclusions:

If our database uses standard aggregations or statistical analyses, then SQL would handle that for us
If our data has too disparate data (making it difficult to unify data), then Mongo has a major advantage
If we have a large data set, then Mongo has another major advantage
If we have multiple tables that need to have their tables joined, SQL does this natively but MongoDB would require us to do this by hand (though this may not be too hard if we set it up right)


parallel programs now emitting a HDF5 error message about H5FDunregister()

If I look at the output of nc_test4/run_par_tests.sh I see a bunch of HDF5 error messages (though the tests succeed):
157: Testing MPI parallel I/O with various other mode flags...
157:
157: *** Testing illegal mode combinations
157: *** Testing create + MPIO + fletcher32
157: *** Testing create + MPIO + deflation
157: ok.
157: *** Tests successful!
157: HDF5-DIAG: Error detected in HDF5 (1.14.3) thread 0:
157:   #000: H5FD.c line 373 in H5FDunregister(): not a file driver
157:     major: Invalid arguments to routine
157:     minor: Inappropriate type
157:
157: Testing MPI parallel I/O without netCDF...
157:
157: *** Testing basic MPI file I/O.
157: *** testing file create with parallel I/O with MPI...ok.
157: *** Tests successful!
157:
157: Testing very simple parallel I/O with 4 processors...
157:
157: *** tst_parallel testing very basic parallel access.
157: *** tst_parallel testing whether we can create file for parallel access and write to it...ok.
157: HDF5-DIAG: Error detected in HDF5 (1.14.3) thread 0:
157: HDF5-DIAG: Error detected in HDF5 (1.14.3)   #000: H5FD.c line [37](https://github.com/edwardhartnett/netcdf-c/actions/runs/10632258936/job/29474869480?pr=8#step:12:38)3 in H5FDunregister(): not a file driver
157:     major: Invalid arguments to routine
157:     minor: Inappropriate type
157: HDF5-DIAG: Error detected in HDF5 (1.14.3) thread 0:
157:   #000: H5FD.c line 373 in H5FDunregister(): not a file driver
157:     major: Invalid arguments to routine
157:     minor: Inappropriate type
157: thread 0:
157:   #000: H5FD.c line 373 in H5FDunregister(): not a file driver
157:     major: Invalid arguments to routine
157:     minor: Inappropriate type
157: *** Tests successful!
157: HDF5-DIAG: Error detected in HDF5 (1.14.3) thread 0:
157:   #000: H5FD.c line 373 in H5FDunregister(): not a file driver
157:     major: Invalid arguments to routine
157:     minor: Inappropriate type

Obviously we don't want this. I am investigating now. @DennisHeimbigner did I see you mention this problem in another issue? Do you have any idea what is happening?

OK, this must be a HDF5 thing, because it happens in 1.14.x but not in 1.12.2. I am continuing to investigate...

I'm still seeing failures, not just the messages-but-passing situation being reported more broadly.  Can you drop your libhdf5.settings file (or email it to me) so I can try to narrow down what's going on in the first place, on my end?

Scratch that; by installing the hdf5 package from the system package management system, I'm seeing behavior consistent with what's been otherwise reported.  Curious that the hand-built version is returning a hard error instead of reporting success.  But now at least I am seeing consistent behavior.

The libhdf5 deployed via package management systems is compiled with LDFLAGS=-Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro.  Disabling the read-only relocations changes the behavior such that we see hard failures instead of HDF5-DIAG messages but tests passing. I don't know if that's useful information to figure out what's going on, but there it is.  Continuing to try to sort this out on my end as well; on Ubuntu 22.04, compiling without the LDFLAGS defined above, I see no failures at all.  On Ubuntu 24.04, I see the crashes; if I add the read-only relocations linker option, I start seeing the warnings.


The /move command doesn't properly reassign rooms

If you /move entryway from lounge, you can't hear what other people are saying/say anything and have other people hear it. It's weird! Refreshing the page fixes it (!??).
So...yeah, chew on that.

This seems to only happen on /move. Worth confirming it vs sidebar vs room description links.

The sendChatMessage function didn't have signalRGroupActions defined as an output. Hopefully adding that fixes this.


Vanilla Meta's are both broken for both Vanilla and Modded Items in 1.10.2

So @bloodmc 👍 I guess I will be the first to complain about this haha. I even stripped down to nothing but spongeforge/forge/GP/LP.
So here it is:
/cf block-place minecraft:wool.5 minecraft:dirt true
This will not work and bring up too many argument errors.
Pretty much when you set the target if the source has a meta it will screw it up. Like the .5 acts as the target or at least during the cmd firing of it.

@Rasgnarok has helped me like crazy with the issue via Discord and has recommend I post a bug report here. There is really no depth to the issue. Pretty much if you create a meta source you can't have a target. In fact you will see this when auto completing after a meta:

Versions:
forge-1.10.2-<IP_ADDRESS>7-universal.jar
spongeforge-1.10.2-2477-5.2.0-BETA-2731.jar
griefprevention-1.10.2-<IP_ADDRESS>2.jar
LuckPerms-Sponge-4.0.16.jar

To be clear, /cf block-place minecraft:wool minecraft:dirt true works just fine for me. Using latest GP on 1.12.2 Spongeforge, I can reproduce the issue here.
The following cause the "Too many arguments" error:
/cf block-place minecraft:wool.5 minecraft:dirt true
/cf block-place minecraft:dirt minecraft:wool.5 true
/cf block-place minecraft:wool.5 minecraft:wool.5 true


write dataset to disk without knowing its size ahead of time?

Is there a way to write an HDF5 dataset without knowing its size ahead of time? I'd to write a dataset to disk, in chunks, as I'm generating it, but I won't know how big the dataset is until I'm done.
Thanks!

Oh, I see...there's discussion of "extendible dimensions" in the "midlevel routines" section of the documentation. Works really well!


libxlsxwriter: 1.1.8 -> 1.1.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/jmcnamara/libxlsxwriter/releases.
meta.description for libxlsxwriter is: C library for creating Excel XLSX files
meta.homepage for libxlsxwriter is: https://libxlsxwriter.github.io/
meta.changelog for libxlsxwriter is: https://github.com/jmcnamara/libxlsxwriter/blob/refs/tags/v1.1.9/Changes.txt
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.9 with grep in /nix/store/x7fnri8hrvwmrzdg5b41lf5kly3nngxl-libxlsxwriter-1.1.9
found 1.1.9 in filename of file in /nix/store/x7fnri8hrvwmrzdg5b41lf5kly3nngxl-libxlsxwriter-1.1.9

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

libxlsxwriter
spatialite_gui

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x7fnri8hrvwmrzdg5b41lf5kly3nngxl-libxlsxwriter-1.1.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libxlsxwriter https://github.com/r-ryantm/nixpkgs/archive/5dc2180c8da6ed09bff66583033f9693de07be6f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5dc2180c8da6ed09bff66583033f9693de07be6f#libxlsxwriter

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x7fnri8hrvwmrzdg5b41lf5kly3nngxl-libxlsxwriter-1.1.9
ls -la /nix/store/x7fnri8hrvwmrzdg5b41lf5kly3nngxl-libxlsxwriter-1.1.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 2 packages built:

libxlsxwriter
spatialite_gui

Maintainer pings
cc @dotlambda for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

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

aarch64-darwin

:white_check_mark: 2 packages built:

libxlsxwriter
spatialite_gui


Upload CSCI 49377 Deep Learning Syllabus

also added friend as a contributor! Thanks Josh for your help :D

BTW two fun facts:

That  "Merge branch 'master' into deep-learning" commit from me happened because there were some new changes to the README file since you made your pull request, and those changes were to the same section that you edited. So GitHub blocked me from merging your pull request until I resolved that conflict, basically by seeing the two versions of the README side by side and editing it to keep both changes.

If you look at the commit history of the master branch you'll notice that my two messy commits ("Merge branch..." and "Fix whitespace...") aren't there, it's as if your pull request changes just got squished into one commit. That's exactly what happened, instead of clicking "merge", I clicked "squash and merge". There's a holy war about this... so it's up to your judgement.


duplo-1.6.19 fails test suite

Citing from http://hydra.cryp.to/build/527320/nixlog/1/raw:
running tests
Running 1 test suites...
Test suite tests: RUNNING...
Tests
  Component support
    slash is transformed into dash: FAIL (0.01s)
      *** Gave up! Passed only 86 tests.
    extracts component ID:          OK

1 out of 2 tests failed (0.01s)
Test suite tests: FAIL

@peti That's strange. Though the most recent version at v1.7.5 should be working. By the way, did you get duplo to run on hydra? I've been looking into using Nix for management but haven't quite found an intuitive way to use it. Do you happen to have any insight on that? Thanks.

I believe this issue occurs in a test that has a ==>-style precondition, and the random generator just happened to generate lots of samples that didn't fulfill that condition, so at some point it gave up to avoid running "forever". IMHO, the only way to avoid that corner case is to (a) use appropriately weak pre-conditions or, if that isn't possible, (b) write a forAll-style generator that constructs appropriate samples alll the time.
About you question: I'm not actually using duplo myself, I'm afraid, I just maintain the Haskell packages for Nix and thus came across the build error in our CI, so I can't say much about your question. Sorry!

Ah. Thanks for letting me know then! So I ran the tests again at v1.6.19, and I ran it again with 1 million test cases. It has run fine on my machine every time. Not sure what has happened.
Actually, I'm curious of why Nix would pick duplo up as I haven't explicitly pushed it that way. This may be too much to ask, but is there a way to remove it from the registry?

Nixpkgs distribute every package that's available on Hackage.

Oh. I see. Sorry for sounding very ignorant when it comes to Nix as I haven't had too much experience with it. It seems that I couldn't find that particular job on nixos' hydra here: http://hydra.nixos.org/job/nixpkgs/haskell-updates/haskellngPackages.duplo.x86_64-linux and the version seems to run fine in most of the jobs listed there. Am I looking at the right place?

The build logs on hydra.nixos.org don't show the error because I disabled the test suite: https://github.com/NixOS/nixpkgs/commit/707f75ddabb6fb69ccc7381c3a39325f9a47670f. The build log I linked to is from hydra.cryp.to, which is my own server. I use that to test the state of the Haskell package set before pushing a new version to the official repository.

Ah got it. I'd love to make this work, but I don't even know where to begin. The tests are running fine at that version as well as the current version. The preconditions are actually necessary because it would otherwise be an improper Component.io name. If it is not too much to ask, is it possible for you to run the most recent version at 1.8.0 on hydra?

I don't believe that it makes any difference where those tests run. Whether they fail or not is simply a matter of probabilities. For every possible sample that this test might be run with, there exists a probability that this particular sample is generated by QuickCheck. The sample space is partitioned into two sets: those elements that satisfy your pre-condition and those that don't. This means that we can determine a probability for QuickCheck to generate a sample that leaves the test inconclusive (because it doesn't satisfy the pre-condition), and consequently there is a probability that such an inconclusive sample is picked, say, 100 times in a row. If that happens, then QuickCheck will abort the test and report a failure (which is what happened in the build log we saw).
The test didn't fail because QuickCheck managed to prove it wrong -- it failed because QuickCheck didn't manage to generate enough valid samples to run the test at all. Clearly, the test will succeed fine in, say, 99 out of 100 times it's run, but my guess is that there will be intermittent failures because of that issue. Now, intermittent failures is the one thing we don't want on our CI environment, because these kind of false positives cause significant effort to the Nixpkgs maintainers. Every time that test fails, there's going to be an e-mail sent to someone, that person has to read the logs, evaluate the situation, write a bug report, etc. That is a lot of work.
If you are confident that you've understood the reason for that test failure and if you are certain that those issues have been remedied, then I'll be happy to re-enable the test suite in Nixpkgs. But I rather not enable the test suite in our distribution's central builds as a kind of debugging attempt, just so that we can check whether it fails again.

Hey @peti , I'm really sorry for having gone missing. I'll actually stop pushing to Hackage. Since Hackage doesn't allow packages to be removed, can you somehow put a tag to prevent fetching duplo for tests? Thank you! And sorry for the inconvenience.

http://hackage.haskell.org/package/duplo/maintainYou may want to mark your package as deprecated  on Hackage:

You may want to mark your package as deprecated on Hackage: http://hackage.haskell.org/package/duplo/maintain.

Done. Thank you for the suggestion. I wasn't aware of that. Closing this issue now.


Add linuxmusl-arm64 binaries

Could you please add linuxmusl-arm64 binary generation?
Currently only linuxmusl-x64 binaries are being generated and we need musl arm64 binaries for node-alpine.
Seems to me the current build script and docker images can handle it already, just need an extra build target.
It will be a great Christmas present - now that the pubs are closed :)

PR welcome if you're able.

+1 to this, currently trying to build a docker image that depends on libvips but it won't compile due to the binaries not being available. Won't compile either.

almost succeeded with the build for muse @lovell ! Fixed a very nasty issue with harfbuzz https://github.com/harfbuzz/harfbuzz/issues/2771
Just one final road block of some dependency mixture:
   Compiling glib v0.9.3
   Compiling librsvg_c_api v0.0.1 (/deps/svg/librsvg)
    Finished release [optimized] target(s) in 1m 10s
ar: `u' modifier ignored since `D' is the default (see `U')
  CCLD     librsvg-2.la
libtool:   error: object name conflicts in archive: .libs/librsvg-2.lax/librsvg_c_api.a//deps/svg/./.libs/librsvg_c_api.a
make[3]: *** [Makefile:998: librsvg-2.la] Error 1
make[3]: Leaving directory '/deps/svg'
make[2]: *** [Makefile:1277: install-recursive] Error 1
make[2]: Leaving directory '/deps/svg'
make[1]: *** [Makefile:1584: install] Error 2
make[1]: Leaving directory '/deps/svg'

any idea what that might be?

all solved - made it optional as it seems it was included by the dependencies.
here is the PR https://github.com/lovell/sharp-libvips/pull/73

PR #90 added this - I'm going to re-open this issue until we ship a release that uses it.

The new linuxmusl-arm64v8 libvips binaries are now tested as part of sharp's CI process, which means prebuilt linuxmusl-arm64 sharp binaries will also be provided from the next release - see https://travis-ci.org/github/lovell/sharp/builds/761832277
Thanks all for your help with this.


re-add the ability to turn on bot management

Current Terraform version
0.14.7
Description
missing the ability in the provider to enable "bot management" - "javascript detections"
Use cases
unable to enable the feature via the cloudflare provider
Potential Terraform configuration
none exist
References
No response

duplicate of #693


Add latest version to bower

The latest version in bower is 0.2.8 - could you add the latest (0.3.1)?

Hi @khaines
Hope I find you well.
Seems that I faced with one issue. Unfortunately, I can't resolve it myself.
I need to update bower package. However bower package relates with your repository, so I don't have any abilities for pushing new changes to bower.
Could you please pull all my changes to update package.
Thanks in advance.
P.S. I've duplicated my message here.

Hi @rosieks
I suggest to wait some time. If I do not get feedback from @khaines I will register a new bower package.

Thanks @VladimirRybalko,
Then I will wait

I will try to take care of this tonight as well as get that bower package
changed to look at the right location :)
Cheers,
ken
On Mon, Jun 19, 2017 at 12:35 AM, Sławomir Rosiek<EMAIL_ADDRESS>wrote:

Thanks @VladimirRybalko https://github.com/vladimirrybalko,
Then I will wait
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/VladimirRybalko/angular-applicationinsights/issues/61#issuecomment-309361839,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABF1HI80HuL-8LNWvel36MCfNjZvSVA0ks5sFiTbgaJpZM4NnXwk
.

@khaines any news about this issue?

There isn't a way to transfer it unfortunately, so I had to deregister the package. Please feel free to register it again

Correction it did get registered to the new location :), so folks can once again get the latest updates via bower

@khaines it's great! Thanks you.
So bower package is still accessible via the old name: "bower install angular-applicationinsights", isn't it?

yes it is...same name
On Thu, Sep 14, 2017 at 12:28 AM, Vladimir Rybalko<EMAIL_ADDRESS>
wrote:

@khaines https://github.com/khaines it's great! Thanks you.
So bower package is still accessible via the old name: "bower install
angular-applicationinsights", isn't it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/VladimirRybalko/angular-applicationinsights/issues/61#issuecomment-329397859,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABF1HK95DP31ed56jL3VxJml5HZ8UaWCks5siNWwgaJpZM4NnXwk
.


Update Oura and other dependencies, improve configs

The update includes:

new oura and pallas versions
new configs for preview / preprod switch
other dependency updates

switched to git rev for oura since there's no release on crates.io for 1.8.3


Update Readme

Signed-off-by: Nico Schieder<EMAIL_ADDRESS>

@bentito This should make it easier to get started and try out PKO. :)
We'll improve on these docs when we are closer to stable (Somewhere around end of next month :crossed_fingers: )

just the above thing @thetechnick , rest all looks great!


Correct orderBy docs

Looking at the docs for orderBy:
orderBy: will reorder a column asc or desc
@Param integer columnNumber - column number starting on zero
@Param smallint sortType - Zero will toggle current option, one for desc, two for asc |
$('#my').jexcel('orderBy', 2);

but when I use it that does not work as expected. And looking at the code for version 2.0.2 I see:
            // No order specified then toggle order
            if (! (order == '0' || order == '1')) {
                var d = $(c).find('.arrow-down');
                if ($(d).length > 0) {
                    order = 1;
                } else {
                    order = 0;
                }
            }

and
                    if (! o) {
                        return (valueA > valueB) ? 1 : (valueA < valueB) ? -1 : 0;
                    } else {
                        return (valueA > valueB) ? -1 : (valueA < valueB) ? 1 : 0;
                    }

So this tells me it actually works like this (and the docs should reflect that):
@Param smallint sortType - One will order DESC, zero will order ASC, anything else will toggle the current order
I tested and that is how the functionality actually is.
This is a very small change to do (I'm not sure you're using anything to generate docs so I wasn't able to find the source for the docs, otherwise I would've opened a PR with it directly) and will help people.

Updated! Thank you for that.


[Do not merge] Draft for improving relative format

When we modify conversion tool code, how to match length of iLib(full, long, medium, short) with CLDR(full, short, narrow)?
In addition, there are some cases that full is same with narrow or short is longer than full in CLDR.
"week": {
            "displayName": "vika",
            "relative-type--1": "í síðustu viku",
            "relative-type-0": "í þessari viku",
            "relative-type-1": "í næstu viku",
            "relativeTime-type-future": {
              "relativeTimePattern-count-one": "eftir {0} viku",
              "relativeTimePattern-count-other": "eftir {0} vikur"
            },
            "relativeTime-type-past": {
              "relativeTimePattern-count-one": "fyrir {0} viku",
              "relativeTimePattern-count-other": "fyrir {0} vikum"
            },
            "relativePeriod": "the week of {0}"
          },
          "week-short": {
            "displayName": "vika",
            "relative-type--1": "í síðustu viku",
            "relative-type-0": "í þessari viku",
            "relative-type-1": "í næstu viku",
            "relativeTime-type-future": {
              "relativeTimePattern-count-one": "eftir {0} vikur",
              "relativeTimePattern-count-other": "eftir {0} vikur"
            },
            "relativeTime-type-past": {
              "relativeTimePattern-count-one": "fyrir {0} viku",
              "relativeTimePattern-count-other": "fyrir {0} vikum"
            },
            "relativePeriod": "the week of {0}"
          },
          "week-narrow": {
            "displayName": "v.",
            "relative-type--1": "í síðustu viku",
            "relative-type-0": "í þessari viku",
            "relative-type-1": "í næstu viku",
            "relativeTime-type-future": {
              "relativeTimePattern-count-one": "+{0} viku",
              "relativeTimePattern-count-other": "+{0} vikur"
            },
            "relativeTime-type-past": {
              "relativeTimePattern-count-one": "-{0} viku",
              "relativeTimePattern-count-other": "-{0} vikur"
            },
            "relativePeriod": "the week of {0}"
          },

https://github.com/iLib-js/iLib/pull/91/commits


Create a terra-kaiju-plugin

This pull request is dependent on this PR getting pulled in and released.
https://github.com/cerner/kaiju-plugin-utils/pull/1
In this PR there is the initial project setup. This still requires the readme to be updated, but it's a good first step and I want to make sure the travis build is passing.
This is the default kaiju plugin for Terra UI. It offers code generation and preview generation using the utils provided by the kaiju plugin utils module. It uses webpack to generate the preview and a virtual file system to provide both the code and preivew files.

The tests only cover the public api right not and extensively test code generation yet.


Add the ability to scale down images during decode (IDCT scaling)

When loading a large image to generate a small thumbnail, jpeg-decoder currently requires allocating a large buffer and decoding the full image. It's possible to use a smaller IDCT to directly decode a JPEG image at a fraction of the full size, saving decode time and memory. This adds IDCT implementations to handle 1/8, 1/4, and 1/2 size decoding.
The interface is a new Decoder constructor that accepts a requested image size. The implementation rounds this up to the nearest scale for which an IDCT implementation exists. This seems nicer than libjpeg's scaling API, which represents the size as a fraction and requires the user to know which scale factors are available.

👍  on this, this is a great feature to have !
Can someone review this ? @fintelia maybe ?

Failing tests are due to the use of the use crate:: syntax not available in 1.28, but all PRs seem to be failing on 1.28 because of dependencies updating to the 2018 edition. I've opened https://github.com/image-rs/jpeg-decoder/pull/118 to increase the minimum Rust version to 1.34.

I like the idea of exposing this functionality.
Would it be possible to control the scale factor via a separate modifier function on Decoder rather than making a new constructor? That way the user would be able to see the metadata of the image before deciding whether to try rescaling, and would also be compatible with adding other similar sorts of functionality without an exponential blowup in the number of constructors required.
I'm also not completely sold on taking minimum output dimensions as a argument. If the only possible downscale factors are 2, 4 and 8, why can't we just have the user pass one of those directly? Another point is that I'd expect users would often either want to decode to exactly the target size or to something substantially larger so that they can get a nicer downsampled result?

Would it be possible to control the scale factor via a separate modifier function on Decoder rather than making a new constructor?

Sure, I'll try that. It will take some refactoring of parser.rs because right now it computes values while parsing the headers that would need to be recomputed after changing the scale factor.

If the only possible downscale factors are 2, 4 and 8, why can't we just have the user pass one of those directly?

It's possible to add other scale factors N/8 by adding a NxN IDCT. libjpeg supports all values of N between 1 and 16. It accepts a fraction N/M, but rounds to the next supported scale factor. Do you think that interface is preferable? Since the goal is usually a particular size thumbnail rather than a fraction of the original size, I imagine most users of that interface would implement the same math I added here to compute that scale factor, except they'd either have to hard-code the supported scale factors, or we'd have to add another API to list them. If a library user would like to perform more of the scaling with an external resampling algorithm, they can always double the requested size or similar.

I also think the interface that exposes Dimensions will both be easier to use and less likely to require a breaking change in the future.

It's possible to add other scale factors N/8 by adding a NxN IDCT. libjpeg supports all values of N between 1 and 16.

This is the piece I was missing, your design is cleaner if a bunch more scale factors could be added.
One more question I have is the "rounding mode". The current strategy is to always round up to a large image size when picking between two scale factors. Other options would be round towards closest and round towards the original size (so decreasing the size rounds up, but increasing image size rounds down). The current choice seems reasonable to me, but I want to double check there isn't a reason we might later want to prefer a different strategy

I chose to round up for the use case you mentioned previously: you want the IDCT to scale to larger than the desired size, then follow it with a resample to the final size.
If we were to later add a N>8 IDCT for upscaling, I think the desired behavior would be to round towards the original image size. That is, round up when downscaling, and round down when upscaling. Since this does not add upscaling support, the difference would only be how it is documented. (You could see the "or the full size of the image if the requested size is larger" as the degenerate case of this. Since there is no N>8 IDCT, a larger size always rounds down to 8/8 scaling).

Updated to make the API be decoder.scale(requested_width, requested_height) instead of Decoder::scaled(requested_width, requested_height), with clearer documentation on scaling factor selection.

@fintelia Is there anything else you'd like changed before merging? We're using this in production and have run about 100k photos through it so far.


python3Packages.adafruit-platformdetect: 3.19.4 -> 3.19.5

Motivation for this change
https://github.com/adafruit/Adafruit_Python_PlatformDetect/releases/tag/3.19.5
Things done

Built on platform(s)

[x] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

2 packages built:

python310Packages.adafruit-platformdetect
python39Packages.adafruit-platformdetect


Doesn't work on ARM achitecture

trying to run coolify on one of the free ARM compute VM provided by Oracle Cloud. here's what I got
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error
standard_init_linux.go:228: exec user process caused: exec format error

Got the same trying to run other images not targeting ARM architecture.

Yeah, it looks like bitnami/redis does not support ARM. I will try to come up with a fix.

I find a quick fix. I'm releasing the new version soon (~20 mins)

cool!

You probably need to reinstall Coolify with wget -q https://get.coollabs.io/coolify/install.sh -O install.sh; sudo bash ./install.sh -f

I'll try it again and let you know.

docker logs -f coolify-redis
1:C 14 Apr 2022 22:19:09.896 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 14 Apr 2022 22:19:09.896 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 14 Apr 2022 22:19:09.896 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 14 Apr 2022 22:19:09.897 * monotonic clock: POSIX clock_gettime
1:M 14 Apr 2022 22:19:09.898 * Running mode=standalone, port=6379.
1:M 14 Apr 2022 22:19:09.898 # Server initialized
1:M 14 Apr 2022 22:19:09.898 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:M 14 Apr 2022 22:19:09.905 * Ready to accept connections
1:M 14 Apr 2022 22:24:10.012 * 100 changes in 300 seconds. Saving...
1:M 14 Apr 2022 22:24:10.012 * Background saving started by pid 15
15:C 14 Apr 2022 22:24:10.020 * DB saved on disk
15:C 14 Apr 2022 22:24:10.020 * RDB: 0 MB of memory used by copy-on-write
1:M 14 Apr 2022 22:24:10.114 * Background saving terminated with success

docker logs -f coolify

><EMAIL_ADDRESS>start /app
> npx prisma migrate deploy && npx prisma generate && npx prisma db seed && node build/index.js

Prisma schema loaded from prisma/schema.prisma
Datasource "db": SQLite database "prod.db" at "file:../db/prod.db"

16 migrations found in prisma/migrations

No pending migrations to apply.
npm notice
npm notice New minor version of npm available! 8.5.0 -> 8.7.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.7.0>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice
Prisma schema loaded from prisma/schema.prisma
Warning: Your current platform `linux-arm64-openssl-1.1.x` is not included in your generator's `binaryTargets` configuration ["linux-musl"].
To fix it, use this generator config in your schema.prisma:
generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "linux-musl"]
}
Note, that by providing `native`, Prisma Client automatically resolves `linux-arm64-openssl-1.1.x`.
Read more about deploying Prisma Client: https://github.com/prisma/prisma/blob/main/docs/core/generators/prisma-client-js.md

✔ Generated Prisma Client (3.11.1 | binary) to ./node_modules/.pnpm/@prisma+client@3.11.1_prisma@3.11.1/node_modules/@prisma/client in 595ms
You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client

import { PrismaClient } from '@prisma/client'
const prisma = new PrismaClient()
┌─────────────────────────────────────────────────────────┐
│  Update available 3.11.1 -> 3.12.0                      │
│  Run the following to update                            │
│    npm i --save-dev prisma@latest                       │
│    npm i @prisma/client@latest                          │
└─────────────────────────────────────────────────────────┘
Running seed command `node prisma/seed.cjs` ...

🌱  The seed command has been executed.
Sentry Logger [log]: Integration installed: InboundFilters
Sentry Logger [log]: Integration installed: FunctionToString
Sentry Logger [log]: Integration installed: ContextLines
Sentry Logger [log]: Integration installed: Console
Sentry Logger [log]: Integration installed: Http
Sentry Logger [log]: Integration installed: OnUncaughtException
Sentry Logger [log]: Integration installed: OnUnhandledRejection
Sentry Logger [log]: Integration installed: LinkedErrors
Listening on <IP_ADDRESS>:3000

still not working.

The prisma thing is a warning. Other than that, it looks okay. Is it not reachable in your browser?

keeps loading and loading. but not displaying anything.

just tried coolify on a new Vultr VM and it works fine. I guess it's the ARM thing that's the issue. Hopefully it's not the Oracle free VM that are the culprits.

I even tried one their Intel one and it doesn't work. Maybe that's something from their side.

Quick update: AMD and Intel work from Oracle. I had to open the port 3000 to talk to the server. I will try again on ARM and update this thread.

@jgb-solutions
Did you get the ARM servers to work ?
I have a similar issue where the XX.XX.XX.XX:3000 page just hangs.
Opening port 3000/tcp and 3000/udp did not help.
Did you do any iptables changes within the VM ?

Hey @dickermoshe yes I got it to work but pulling the latest version at the time. Though it doesn't work as expected. I think last month or so I tried it again on an ARM machine. Everything seemed to work, I could deploy an Elixir app with Docker. But no Node apps wanted to run. They didn't use Docker. Just plain Next.js apps. Other than that No DB or analytics did work. They start then stop by themselves in a few seconds. I didn't bother opening another issue since Coolify is not something I'm planning to use in production (Not in the near future anyway) but just to play around on free Oracle servers.


EPA Breakdown Issues

EPA Breakdown has a few issues:
Certain points will be under 0. I do understand that this team probably has cost the team points but cycles and links are affected by this and can be negative.

It might seem counterintuitive at first, but cycle and link EPAs can be negative. For example, if a team claims responsibility for a task in auto but fails to deliver, they might reduce the number of auto game pieces scored. If a team is scoring pieces low and takes up space near the grid, this might reduce the alliance's middle and top game pieces scored.
While most of the negative results are due to noise and random chance, I don't want to hide this and obscure some second order effects.


Update the icon of twitter

In the footer section the twitter logo is bird, by the update of the logo add the X  in the twitter logo.

I would like to work on this issue. Could you please assign me this task


enforce database env prefix

Purpose
To prevent having the same prefix between different environments, we have created a mapping where all environment are defined with a corresponding prefix.
Proposal
Create a mapping between and their prefixes and use them to generate database credentials.
Also added in this PR mongodb admin password generation.

You can postpone this improvement, but don't forget to declare an issue for that.


Add Sveltkit boilerplate

Once it can npm install.

Bun should probably not be listed as that could be misleading, it's only (optionally) used as the package manager, no Bun functionality is usable in the code due to the node part of NW.js.


[Frontend] - Client ID input field error validation issues

Describe the bug
Wrong behavior for some edge cases at the field validation from the Client ID field of the Grant User Permission page. Might need refactoring at the regex expression.
Screenshots
1.
Private Zenhub Image

Private Zenhub Image

Private Zenhub Image

Private Zenhub Image

we can rethink and discuss within the team, to see if we still want to allow user enter multiple forest client at once, or they can enter one by one.


the Context_proxy class should not be exposed to plugins

The Context_proxy class should be an implementation of an interface that plugins should never have to downcast to.

mentioned in commit a038051c22da03683c960ea148b1872cb0e8520a

mentioned in commit 1d05112b0ba35d3f98b50b7733d58cc2d864b2fa

mentioned in commit d942079dd73c6ce1806ca82676013d65d177ffa4

mentioned in commit 35e28800b738b9cfc8c403c6cefb6abb3d3fb361

mentioned in commit 29b2f7e6e957f77a67ee0b3fe9987bc60b9e8d8e


Create a tracing span inside operation handlers.

Create a new span when the operation is executed.

https://github.com/awslabs/smithy-rs/pull/1314


breakfix: Azure OAuth2 config not working

Describe the issue
I’ve followed the documentation for setting up an Azure OAuth2 IdP.
When I run my pipeline to validate the Caddyfile, I get the following error:
Error: loading http app module: provision http: server srv0: setting up route handlers: route 0: loading handler modules: position 0: loading module 'subroute': provision http.handlers.subroute: setting up subroutes: route 1: loading handler modules: position 0: loading module 'subroute': provision http.handlers.subroute: setting up subroutes: route 1: loading handler modules: position 1: loading module 'authentication': provision http.handlers.authentication: loading authentication providers: module name 'authorizer': provision http.authentication.providers.authorizer: loading security app module: provision security: server initialization failed: failed configuring identity provider: failed to fetch metadata for OAuth 2.0 authorization server: metadata authorization_endpoint field not found for provider azure
Configuration
Paste full Caddyfile below:
Removed
Version Information
Provide output of caddy list-modules -versions | grep git below:

Error: unknown shorthand flag: 'v' in -versions

Expected behavior
I expect the configuration to work!
Additional context
Add any other context about the problem here.

what is meaning of blank nvironment variables？ I try The Microsoft oauth2.0 recently， i Compare The part Which is Microsoft of the documentation. the blank nvironment variables is meaing that we not set the metadata  authorization_endpoint ?

what is meaning of blank nvironment variables？

@abirvepete , it is likely the environment variables were not set.


Update debugging.mdx

🚀 Deployed on https://66f1881b1b621d39e0a7c965--cozy-fox-0defec.netlify.app


Resolve linter failure on PRs from external repos

Description
As discussed in #286, we discovered that in a number of PRs where the base repo is external, the linter fails.
This seems to be a bug of the super-linter, but fixing it is beyond our capacity. We noticed that the problem is related to VALIDATE_ALL_CODEBASE = false, in which case the super-linter will switch branches and find files that have been changed, and the super-linter will only perform linting on those files. The failure happens during the branch switch.
This PR, therefore, changes VALIDATE_ALL_CODEBASE to true. We expect that this change can get rid of such failures.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[x] Re-reviewed Files changed in the Github PR explorer

N/A:

[ ] Wrote unit tests
[ ] Updated relevant documentation in the code
[ ] Added a relevant changelog entry to the Pending section in CHANGELOG.md

Lets hope this fixes it 🙏


Topic recognition - s4753820 ViT ADNI Brain Data Classification

Hi,
This pull request integrates a solution for Alzheimer's Disease detection using Vision Transformers (ViT), applying it to the ADNI dataset. The goal was to classify MRI brain scans into two categories: Alzheimer's Disease (AD) and Healthy (No Alzheimer's). The implementation leverages PyTorch and a Vision Transformer architecture, combined with aggressive data augmentation and a comprehensive training, validation, and testing pipeline. While we aimed for a target test accuracy of 80%, our final model reached a test accuracy of 67.93% which unfortunately means our model architecture/hyperparameters likely weren't tuned enough.
Contents / Files Added:

dataset.py: Contains the functions for dataset loading, augmentation, and splitting the dataset into training, validation, and test sets.

modules.py: Defines the Vision Transformer model architecture, including patch embedding, transformer layers, and classification heads.

train.py: Implements the full training loop, including validation steps, learning rate scheduling, checkpoint saving, and loss/accuracy plotting.

predict.py: Demonstrates the usage of the trained model for prediction. It prints classification results and provides visualizations such as confusion matrices and image grids with predicted labels.

Documentation:
README.md: A more detailed explanation of the project, including problem description, algorithm explanation, architecture overview, preprocessing steps, example usage, and experiment results.
Let me know if any changes are required or feedback needs to be incorporated!
Sincerely,
Yuvraj Fowdar
s4753820

This is an initial inspection
1) Recognition Problem:
a) Algorithm solves the respective pattern recognition problem appropriately: (+3)
b) Algorithm implemented in PyTorch demonstrated and functions as intended to solve the respective problem: (+3)
c) Good design implemented in PyTorch that solves the problem: (+1)
d) Commenting: (+1)
e) Algorithm is normal or above difficulty while implemented in PyTorch while solving the respective problem: Hard level (+5)
f) Algorithm is hard difficulty while implemented in PyTorch while solving the respective problem: Hard level (+5)
(Total: 18/20)
2) Commit Log:
a) Meaningful commit messages with evidence of individual work and originality: (+2)
b) Progressive commits and logical log structure providing evidence of individual work and originality: (+3)
(Total: 5/5)
3) Documentation:
Requirement:
Tittle: Done
Description of the algorithm: Done
Problem that it solves: Done
How it works in a paragraph (example any pre-processing): Done
Figure/visualisation (any input, output & results): Done
Dependencies: Done
Marking:
a) Description and explanation of the working principles of the algorithm implemented and the problem it solves: (+5)
b) Description of usage and comments throughout scripts: (+3)
c) Proper formatting using GitHub markdown: (+2)
(Total: 10/10)
4) Pull Request
a) Creating a pull-request into correct branch with a working and demonstrable version of the algorithm: (+2)
b) Incorporating feedback into the pull request: (+2)
c) Description of and comments within the pull request: (+1)
(Total: 5/5)
Feedback:

Good attempt.
I think one of the major issue lies in data pre-processing, where test and validation sets were used after data augmentation.
In CV tasks, the training dataset can be modified (augmented) for various reasons but test/valid should be left untouched

Any Changes Needed: No

Observational Feedback
Pull Request:
Correctly created the Pull request from Topic Recognition Branch .
The pull request includes a clear description about the file structure .
File Organizing: Well-organized files.
Commit Log:
Commit messages are progressive for the Recognition Problem solved using 4 files .
Commits are regularly made.
Documentation:
Code comments and docstrings are included.
Proper GitHub markdown formatting is used, with organized headings, lists, and code blocks.
Should  add about Conclusion and future improvements in the ReadMe.

Marking

Good/OK/Fair Practice (Design/Commenting, TF/Torch Usage)
Good design and implementation.
Spacing and comments.
Header blocks.
Recognition Problem
OK solution to problem. -2
Driver Script present.
File structure present.
Good Usage & Demo & Visualisation & Data usage.
Module present.
Commenting present.
No Data leakage found.
Difficulty : Hard. ViT (Hard Difficulty)
Commit Log
Good Meaningful commit messages.
Good Progressive commits.
Documentation
Readme :Good.
Model/technical explanation :Good.
Description and Comments :Good.
Markdown used and PDF submitted. PDF checked.
Pull Request
Successful Pull Request (Working Algorithm Delivered on Time in Correct Branch). On time submission.
No Feedback required.
Request Description is good.
TOTAL-2

Marked as per the due date and changes after which aren't necessarily allowed to contribute to grade for fairness.
Subject to approval from Shakes


(maint) Remove redundant test cases

Previously the transport shared examples attempted to test various scenarios
however the ruby strings used contain duplicates:
''single single'' is just the same as "'double single'" from a ruby point of
view except the first word has changed.  The same goes for single double,
single "double" single and single 'single' single.
This commit removes the redundant tests and their expectations.

CLA signed by all contributors.


Windows 10 system dark theme

Would it be possible to change app controls colour to black/grey shades depending on Windows set to light/dark mode? The current system setting can be retrieved from the registry at
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize
where the AppsUseLightTheme and SystemUsesLightTheme values are the ones to look for.
(Also notice that older versions of Windows 10 used only one of these options when dark mode was first introduced and the ability to change theme for apps and system independently was added later on, so this might cause some compatibility issues if not handled.)
I know that controls colours can be changed in Winforms, but I don´t know if it goes for all of them (Some people say Combobox cannot be styled). This is a minor feature anyway, but it would be pretty neat, I think.

Update <IP_ADDRESS> ;)


Add support to expose API methods using multiple URLs (iso6)

Description
This is the same PR as #6191 but applied on the iso6 branch due to a merge conflict.
Add support to expose API methods using multiple URLs. If the path property of the typedmethod annotation has type list, the inmanta client will always use the first path to perform its API calls.
closes  inmanta/inmanta-lsm#1274
Self Check:

[x] Attached issue to pull request
[x] Changelog entry
[x] Type annotations are present
[x] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
[x] Sufficient test cases (reproduces the bug/tests the requested feature)
[x] Correct, in line with design
[x] End user documentation is included or an issue is created for end-user documentation
[ ] ~~If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso6 in fe13b82c37942420b5622c8476c64bd8cad9e121


Preventing ClientSessionManager from calling onClinetShutdown multiple times

Saw this as a good easy bug to fix to get introduced to runelite. Is this a good solution?
#11354

sessionId can also be null if a ping fails, so maybe that should also be fixed (as it would also throw without this bug). Maybe the correct way to fix this is to prevent the shutdown from happening twice?

So abort shutdown if the session ID is already null?

The root of this problem is shutdownClient is being called >1 times I think. Not sure the best way to make it not do that. Completely unrelated to that, is L125 can set sessionId = null which means that it can be null in onClientShutdown, so I would just null check it there.

Simple isShuttingDown variable in ClientUI would suffice imo

Simple isShuttingDown variable in ClientUI would suffice imo

That's what I was originally thinking too, but I felt like adding a new variable just for this added clutter. Especially when checking if sessionId is null does the same thing and prevents any other scenario where we'd call delete with a null session ID.


Update README.md

OA Technical Update 30/06/23 11:40AM

I have read the CLA Document and I hereby sign the CLA


[BUG] aws(elastickbeanstalk) and library

When i'm up code on localmachine @model_observer work, but if I'm deploy it on aws (elastickbeanstalk) @action work, but @model_observer don't work.I asked amazon support what the problem might be, we checked the server settings/code settings for the deployment and they indicated that most likely the problem is in the library.
I can subscribe/unsubscribe, but changes on model i can't get
class MethodConsumer(AsyncAPIConsumer)

Sorry I somehow missed this message in my inbox.
Do yo know what channel layer you are using?


No package matching 'containerd.io' is available

I'm following along http://www.pidramble.com/wiki but when I come to "Provision the Raspberry Pis" I get an error in the playbook.
TASK [geerlingguy.containerd : Ensure containerd is installed.] ********************************************
fatal: [kube3]: FAILED! => changed=false
msg: No package matching 'containerd.io' is available
fatal: [kube1]: FAILED! => changed=false
msg: No package matching 'containerd.io' is available
fatal: [kube2]: FAILED! => changed=false
msg: No package matching 'containerd.io' is available
I looked around a bit and can't figure out what to do next.
Any ideas will be appreciated.

Figured it out.I needed the 64-bit OS image.
I found it at https://downloads.raspberrypi.org/raspios_lite_arm64/images/
and containerd installs now.
On to new errors to resolve.


[UPD] - Mapped functions to public schema - FIX #68

Fix for series 3.*

Coverage remained the same at 82.867% when pulling 9eacbaccdb6bcad3a28f6640e56af6be54a61c77 on 4CME:master into a56145880f17140c0ab8ce6fbbb8ac40b322e184 on njbarrett:master.

Coverage remained the same at 82.867% when pulling 9eacbaccdb6bcad3a28f6640e56af6be54a61c77 on 4CME:master into a56145880f17140c0ab8ce6fbbb8ac40b322e184 on njbarrett:master.

Coverage remained the same at 82.867% when pulling 9eacbaccdb6bcad3a28f6640e56af6be54a61c77 on 4CME:master into a56145880f17140c0ab8ce6fbbb8ac40b322e184 on njbarrett:master.

Failures are not being caused by merged code, but by previous existent code.

Thanks for this as well.


add endpoint for creating subimage

This creates the endpoint needed for the first steps for #74
Please note this PR also updates tox configuration for linting and black

Pytest added. @annehaley


Add more info to install curl in mTLS page

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
Assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

you should avoid force merge, it'd be nice to fix the 404 instead, even if it's not in your pr


chore: remove unnecessary dependencies from templates

Not sure why jsdoc and uglify-js were listed as dependencies in the templates, but shouldn't be needed as explicit dependencies.

These are also in samples, which can be looked at when those are next updated.


Java 2.1: Byte Code

Description 📜
Created a documentation for Java Bytecode.
Fixes #1196

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Java_Domain

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@AkMo3 @garvitraj I have made the Pull request, please review it.

@nandini7637 Please start the review

I have reviewed it, @AbhinandanAdhikari  please correct the spelling of 'environment', else everything looks good, well done and I think we can merge it after the corrections.

I have reviewed it, @AbhinandanAdhikari please correct the spelling of 'environment', else everything looks good, well done and I think we can merge it after the corrections.

@nandini7637 Ma'am, I've corrected the spelling.


Debugging Issue

Start backend using Debugging
Set break point at the beginning of endpoint code

[x] Start in frontend with split screen loading source for an API fetch using GET.

[x] Set break point on fetch, inside .then, inside .fetch
[x] Run frontend, screen capture break at fetch while examining Body
(fetch function)

(.then)

[x] Press step over on backend until you have obtained data from database, screen capture HashMap or other data Object

[x] Return to frontend debug session

[x] Step in until you see data, screen capture capturing break point and Data.

Peer Review: Anthony Bazhenov
Debugging
Grade: 1.9/2
Good in depth guide to debugging that shows a deep understanding of the process and its purpose. Followed almost all the same instructions as on the debugging canvas page but is missing a few screenshots for some of the steps. Shows process of adding breakpoints in login and clearly shows it stoping in the frontend and shows screenshots of breakpoints in the backend and stepping over until he received the data in the backend. He then shows him returning to the frontend session where he steps over again until the data appears showing screenshots of the process. Overall Tay had a super in depth guide with screenshots showing the process of debugging in a organized and complete way. The only reason I lowered the grade slightly to a 1.9 is because he didn't have all the same bullet points as in the original canvas assignment, but he still gets across the same ideas and shows the whole process.


Update version of embedded spectral

The version of the embedded spectral is 6.2.1.
The latest version of spectral is 6.6.0.
Unfortunately, the older version contains backward compatibility issues, most significantly around how aliases are defined. (see https://github.com/stoplightio/spectral/pull/2085 and https://github.com/stoplightio/spectral/pull/2033)
The latest spectral URL style guide makes use of aliases; without the latest version of spectral, this style guide cannot be used as is.

Hi, thanks for the report and sorry for the delayed response.
We wanted to make the setup of the plugin as easy as possible by bundling the CLI with it. But we also noticed the downsides of this approach and decided to no longer bundle it with our latest version 2.0.0.
From now on the spectral cli installed on your system will be used for linting. This should fix most of the problems the plugin hat till now.
Please feel free to upgrade and try it out with the latest version of the spectral CLI.


Is it possible to use only sceneKit (or somehow desrease lib size)?

I don't need the part with AR, I only need a scene API.
I ask this because compiled library size is 22MB if I understand everything right and this is just way too much.
For example, jpct-ae size only 3mb.

We are working in decreasing the lib size now for our next update (targeting early next week). Will update this thread once the new version is live, along with new lib size.

Hi @Svoka,
With our ViroCore 1.1 update, we have reduced the size of the ViroCore library to 4.2 MB!
Check out the release and upgrade instructions here: https://virocore.viromedia.com/docs/releases
Sorry for any inconvenience! Feel free to reach out to us if you have any other issues!
Andy

@achuvm wow! Definitely wanna check it right now :)


Be consistent about "duration" method parameters

The AttemptTimeLimiters and WaitStrategies classes have methods that take a (long, TimeUnit) pair, whereas StopStrategies#stopAfterDelay accepts only a long. Not a big deal, but slightly unfortunate from an API point of view.
How about aligning StopStrategies with the other two classes by introducing StopStrategies#stopAfterDelay(long, TimeUnit) and deprecating StopStrategies#stopAfterDelay(long)?
(I understand the some of the strategy interfaces also take only a long, but most users will not implement those themselves, and in any case those types are in some sense more "low level".)

I like consistency, too. That's a good catch. Feel free to open a PR for it, and I'll get it into the next release.

Cool. I opened PR #39.

Your duration method parameter consistency fix should be good to go now in 2.0.0. Thanks again for your contributions.


"Cotu Mihalea" is listed in the drop-down menu

Description:
"Cotu Mihalea" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Cotu Mihalea" in the search bar.

Expected results
The location is listed in the drop-down menu as "Cotu Mihalea, Brăila (Siliștea)".


Cannot find Creator of Graph for "Created By" Condition

I have Discourse Graph installed in two graphs.
In both I have a multiple queries finding nodes referencing multiple titles and created by.
And in both graphs, the creator of the graphs name doesn't show up.
Multiple other username show up .
The name of the creator of the graph shows up when I hover over nodes he creates / edits.
His name also shows up in the selection of of Author and Last Edited By.
I tried manually typing in his name, but it still doesn't show up.
I also tried disabling Discourse Graph and enabling Query Builder via Roam Depot, but no luck.
Any idea what might be causing this or how I might debug it?

What does the datalog query say? On the bottom left, it should output the equivalent datalog query that you could enter in the console and start manipulating the query to see what the bug could be

Ah, one thing I didn't try was fully typing in his username and trying to run the query.
I just assumed because it wasn't in the autocomplete that it wouldn't work.  My mistake.
If I manually type in the username and run the query, it returns the expected results. 👍

What comes up on the autocomplete?

It is just blank from the UI while looking for the user (creator of the graph).
I believe it has something to do with the fact that the creator of the graph was "anonymous" for some time then changed his name to "Matt" just recently.
I tested this by creating some queries to show blocks that were created when he was "anonymous" vs when he was "Matt".  Query Builder gives an error trying to show the selection of created by when he was "anonymous".  But no error is given when querying blocks created after the change to "Matt" was made.
Blocks from templates were created in 2022 by "Matt"
Blocks from page zettels were created in 2020 by "anonymous"
Removing the selections removes the error and allows the query to run.
Third query shows "Matt" not displaying in the created by UI.
https://user-images.githubusercontent.com/3792666/199075090-dbdbd93d-5f9d-41b7-8f05-1a8cee137923.mp4
Below is showing the error from Chrome Console.
https://user-images.githubusercontent.com/3792666/199075278-1620a5fb-d263-4ee0-9b98-1181b9ddf93e.mp4

Ok was able to confirm these issues in the code but can't reproduce on my end - just pushed a fix for review on Roam Depot.
While it's being reviewed, we could verify the fixes from downloading the zip and loading it in developer mode from here: https://roamjs.com/extensions/query-builder

Fixed!
https://user-images.githubusercontent.com/3792666/199573564-a322fad4-772a-4315-b994-ab91186dade1.mp4


The number of pretraining steps

Hi Gengmo,
Thanks for your nice work ! I have a question about the number of pre-training epochs. From the Appendix in the paper, the number of max training steps for pretraining is 1M with batch size 128 (about 7 epochs).
Is such a small number of pretraining epochs due to early stopping?
Have you ever tried what happens if you train for more epochs?

Got it. This is not due to early stopping. We have tried a larger number of training steps. However, the performance is not significantly improved.

That helps me a lot. No more questions.
Thanks for your prompt reply!


Default to fine-grained brightness changes, as if Shift+Option+Brightness were held

Before opening the issue, have you...?

[X] Searched for existing issues

Is your feature request related to a problem? Please describe
Each default step in brightness can be too much of a change in either direction. Default to fine-grained control. MacOS provides this natively if you hold Shift+Option while changing the brightness.
Describe the solution you'd like
Default to fine-grained brightness changes on button press
Describe alternatives you've considered
Fine-grained changes manually
Anything else?
No response

Found it 4 seconds after creating this feature request. For future people stumbling upon this via a search or Google, the solution is in the Keyboard tab. Enable OSD scale


Release/v0.4.2

Update to Kotlin v1.4

Codecov Report

Merging #60 into master will decrease coverage by 0.68%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #60      +/-   ##
============================================
- Coverage     96.45%   95.77%   -0.69%
  Complexity       93       93
============================================
  Files            26       26
  Lines           734      734
  Branches         11       16       +5
============================================
- Hits            708      703       -5
  Misses           19       19
- Partials          7       12       +5

Impacted Files
Coverage Δ
Complexity Δ

...tlin/dev/gumil/kaskade/coroutines/StateFlowTest.kt
93.90% <0.00%> (-4.88%)
7.00% <0.00%> (ø%)

...commonTest/kotlin/dev/gumil/kaskade/KaskadeTest.kt
95.83% <0.00%> (-1.05%)
15.00% <0.00%> (ø%)

Continue to review full report at Codecov.

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