Fix 009 module to use @Identifier instead of @Named to inject broker

This change is related to https://github.com/quarkusio/quarkus/commit/11bc00f324b6ed4166ab4250e6661060b7d1a4d4.
The problem is that keeping injecting the default Kafka broker using @Named is now failing:
@ApplicationScoped
public class KafkaProviders {

    @Inject
    @Named("default-kafka-broker")
    Map<String, Object> config;
}

Using:
@ApplicationScoped
public class KafkaProviders {

    @Inject
    @Identifier("default-kafka-broker")
    Map<String, Object> config;
}

It works.
Therefore, this is a breaking change that should be noted in the Migration guide for 2.x. Reported by https://github.com/quarkusio/quarkus/issues/17754

This is making Beefy TS fail. Merging. @pjgg, If you see something to address, feel free to create a separate PR.


Fixed spelling mistake

Changed 'recieving' to 'receiving'.

@johnkrussell : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@johnkrussell Thanks for this fix.


add require_atomic? false to Organization

@bind-ritu1211 you'll have to merge this along with the last pull request, for the issue to be solved entirely.
Thanks!


Increase tap surface for start and end handles

The trimmer works if can tap and get ahold of the shaded area to the left of the start or to the right of the end. When it starts it's likely at 0. Obviously grabbing something with 0 width is hard. It takes about 3 to 5 tries to get ahold of the left trimmer and even more for the right one. Is there a way to increase the hitslop of these? Would anyone else find it worthwhile to add a handleHitslop property?

i can help if you want to point me at a good place to start looking. If you would rather do it I can help with the pull request.

@JBerendes i've added 20 points hitSlop around right and left corners, so it should help

testing now

It doesn't seem to have been solved.  The video starts several seconds after I have been trying to grab the starting trimmer ... Then when I'm moving it more fluidly it's because I'm grabbing the shaded area.

Well try to change that line which I've pointed

My thought is that the area offered as touchable is not larger than what is visible. So any touch events that occur to the left of the white start trimmer are not seen because the are outside of the parent container.
I'll try what you just mentioned. Thanks

I see, we need access to a thumbWidth prop so it can be passed to ICGVideoTrimmerView.m on smaller devices it's simply to narrow at the default value.

great, look how we provide all props to JS side, in similar way you can also pass thumbsWidth prop

will do.

Released https://github.com/shahen94/react-native-video-processing/releases/tag/v1.5.0

looks good.


[terra-date-picker] Remove placeholder

Summary

This PR

Removes placeholder.
Added format to be displayed for both DatePicker and DatePickerField.

Link: jira for translations.

A part of #1193
Deployment Link

https://terra-framework-deployed-pr-#.herokuapp.com/
Testing

Date Picker:

Date Picker Field:

Additional Details

Thank you for contributing to Terra.
@cerner/terra

Tested: PR #1240
Part 3 of 3 for issue #1193
Reviewed:

Removes placeholders for format mask
Add Date Format Mask as description text below Date-Picker
Add Date Format Mask in with Help text in DatePickerField

Fix with Followup Issues:

Enhancement: [add issue #] Enhance keyboard navigation, today shortcut, focus styling
Enhancement: [add issue #] Remove ErrorIcon from Terra-Field

Verified by @neilpfeiffer, Ready to Merge

Pass

UX Review


add code of conduct template

This PR adds the code of conduct template! 🎉
For now it's super simple, the COC is in the title/bold font. We don't currently have a design on this page so consider this a v1. It's markup is the same as the "callout" for now!
Issue: https://github.com/ladiesnight/ladiespdx/issues/35

A+++++++


Make bread able to sort the logstream by time

By default, bread prints log events in the log stream in order of appearance. Normally, this means the events of each thread are batched together, making cross-thread interaction more difficult to reason about.
Add a switch (-s) to bread, that makes it sort events in the stream by time. A simple implementation would be to read every event, then sort and print them in one go. However, this approach has a high time-to-first-event latency, high memory usage, and does not work with live streams.
A more involved approach would be to assume that events are sorted to a certain extent (e.g: events more than 60 seconds apart in the log will not be out of order), read a window of events sort and print some of the window, then repeat.

how about create predefined sized sections/blocks in the log file for each session, and a mark card as session index, then "merge sort" the result.

I'm not sure I understand your suggestion. One way to go about it is to define the window as a set of batches of unique writers (identified by writer id), and merge sort those batches. However, if a writer fills its queue, by default, it allocates a new one, which means the events of a single writer can span multiple batches, invalidating the assumption above.

instead of assigning one section to one session, how about using fix sized linked blocks, each block has pre-defined size, and once a session's block filled up, it is assigned a new block and "link" the two blocks together

Just to make sure we are on the same page: this ticket is about sorting a stream of log events in the bread program. Do you suggest to use a two pass algorithm? One pass to identify the event batches of each log writer in the whole stream, then in a second pass, merge sort them?
This could work for complete files, but not for streams, e.g: when reading a live logfile,or when the logfile is really huge.

I got your point here. you try to do the magic in bread, which is valid, my suggestion is based on log persistent "consume" call is done by NOT critical path resources, the operation could be a little bit "slower" which make it much easier for bread to sort the events out.
what I suggested is collaborate the effort of generating log and bread log.
For a given log file A, we could consider it as 4k blocks, each time each block can only contain one writer's contents, each time of "consume" invocation, it will locate the last block of the write and pure the events, once a block is filled up, it get a new allocation and leave a link pointer.
at the very beginning, we could keep the meta data of the first and last block for each writer.
During the reading, the bread only needs to "merge" the blocks for each writer, and only keep one block each writer at most in memory.
Given reads has to done through bread, the file format could be open for complex design.
The other way is by registering all the writer to a "Sink", and only "consume" from the sink, during consume invocation, it could merge all the channels' content and write to the file.

I understand the proposition now. While this approach could make offline sorting easier, there are some important details. Currently, a binlog logfile is an append-only stream. Segmenting the logfile as suggested would change this to a random access file, that is difficult to implement, if the target is e.g: a pipe, a socket some agnostic middle layer (compression, encryption), etc. Also, cross batch pointers prevent (or make more difficult) injecting entries intto the stream later, and make log rotation more complex.
In the bread side, probably the two pass would be still necessary, to discover the start of each writer.

Given reads has to done through bread, the file format could be open for complex design.

True, but I intend to keep the format as simple as possible, to make it easier to add different producers and consumers, e.g: a java writer, or a python reader for quick statistics or log analysis.

Cool, totally agree KISS is better than complex show off 😄
You may bring up another design corner to handle, given the general "logger file contract" no matter if it is persistent to file or a pipe/socket, chronicle total order of all events may be assumed, which means existing down streams expecting the log events are in merged and sorted by timestamp.
in that case probably better to merge sort during "consume".

I don't see a reasonable way to merge sort in Session::consume. Assume the following (wrong) algorithm:
std::vector<ReadResult> buffers;
for (auto&& c : _channels) { buffers.push_back(c.reader.beginRead()); }
// ... then merge sort buffers in buffers

Assume C is the consumer thread, and there are two producer threads, T1 and T2.
Then the following sequence of events:

C fetches the buffer of T1 from its queue
T1 adds a new event to its queue
T2 adds a new event to its queue
C fetches the buffer of T2
C merge sorts the fetched buffers. This is wrong, as the last event of T2 will be sorted and consumed, but the last event of T1 will not be, despite it comes before (by timestamp) the last event of T2.

Session::consume can't use a sliding window trick as bread can, as it would unnecessarily increase the pressure on the queues.

Yes, I missed the race case, great catch.  :+1:
However, there is a trick to deal it without pressure the log buffer, we could poll all the events from the buffer, and only merge sort all the events before the last event timestamp of the first polled buffer, and leave the rest in a temporary buffer for the consumer, and merge them with the next poll.
long timestamp;
bool first = false;
for(auto channel : channels) {
    channel.poll(buffer);
    if(first) {
        timetamp = lastTimestamp(buffer);
        first = true;
   }
  mergesort(buffer, timestamp);
  // write the result to file and leave all event in the buffer if timestamp > timestamp
}


stability issues with gnome 45 and 46

About 10% of the time, opening fly-pie will cause the whole gnome desktop environment to crash. When I hit ctrl + space, it immediately freezes for a second then throws me back to the login screen.
You may also check the output of GNOME Shell for any error messages related to Fly-Pie.
This can be done with the following terminal command:
I can't find anything in journalctl that points to a problem unfortunately
System

distribution: Arch, Fedora (38, 39, 40)
Fly-Pie version 26
GNOME Shell version:  44, 45, 46

Hi there! Thanks for the report. However, this will be pretty hard to debug, as I cannot reproduce this on my end.

Does this happen on X11 and on Wayland?
GNOME Shell should print at least something to the journal when it crashes. Is there really nothing?
Have you disabled all other extensions? (Please restart your session after disabling all other extensions and before testing).

i think i found the thing in journal, im sorry if this is too much to paste here but im not actually sure which part is the problem
May 12 14:45:18 goop gnome-shell[20285]: GNOME Shell started at Sun May 12 2024 14:45:17 GMT-0400 (Eastern Daylight Time)
May 12 14:45:18 goop gnome-shell[20285]: Registering session with GDM
May 12 14:45:18 goop gnome-shell[19805]: Connection to xwayland lost
May 12 14:45:18 goop gnome-shell[19805]: Xwayland terminated, exiting since it was mandatory
May 12 14:45:18 goop systemd-logind[534]: Session 5 logged out. Waiting for processes to exit.
May 12 14:45:18 goop systemd[1]: session-5.scope: Deactivated successfully.
May 12 14:45:18 goop systemd[1]: session-5.scope: Consumed 4.151s CPU time.
May 12 14:45:18 goop systemd-logind[534]: Removed session 5.
May 12 14:45:18 goop polkitd[575]: Unregistered Authentication Agent for unix-session:5 (system bus name :1.377, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
May 12 14:45:19 goop gdm[573]: Gdm: Child process -19785 was already dead.
May 12 14:45:19 goop systemd[1098]: Started Portal service (GTK/GNOME implementation).
May 12 14:45:19 goop systemd[1098]: Started Portal service.
May 12 14:45:19 goop gnome-software[20452]: Failed to load /usr/lib/gnome-software/plugins-20/libgs_plugin_fwupd.so: failed to open plugin /usr/lib/gnome-software/plugins-20/libgs_plugin_fwupd.so: libfwupd.so.2: cannot open shared object file: No such file or directory
May 12 14:45:19 goop gnome-shell[20833]: Archive:  /tmp/VQS4N2.shell-extension.zip
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/de_DE/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/de_DE/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/es_ES/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/es_ES/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/it_IT/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/it_IT/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/nl/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/nl/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/pt_PT/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/pt_PT/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/tr_TR/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/tr_TR/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/zh_CN/
May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/locale/zh_CN/LC_MESSAGES/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:    creating: /home/cronch/.local/share/gnome-shell/extension-updates/color-picker@tuberry/schemas/
May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:   inflating<EMAIL_ADDRESS>May 12 14:45:19 goop gnome-shell[20833]:  extracting<EMAIL_ADDRESS>May 12 14:45:29 goop systemd[1]: Stopping User Manager for UID 120...
May 12 14:45:29 goop systemd[19773]: Activating special unit Exit the Session...
May 12 14:45:29 goop systemd[19773]: Stopped target Main User Target.
May 12 14:45:29 goop systemd[19773]: Stopping PipeWire PulseAudio...
May 12 14:45:29 goop systemd[19773]: Stopped PipeWire PulseAudio.
May 12 14:45:29 goop systemd[19773]: Stopping Multimedia Service Session Manager...
May 12 14:45:29 goop wireplumber[20081]: stopped by signal: Terminated
May 12 14:45:29 goop wireplumber[20081]: disconnected from pipewire
May 12 14:45:29 goop systemd[19773]: Stopped Multimedia Service Session Manager.
May 12 14:45:29 goop systemd[19773]: Stopping PipeWire Multimedia Service...
May 12 14:45:29 goop systemd[19773]: Stopped PipeWire Multimedia Service.
May 12 14:45:29 goop systemd[19773]: Stopped target Basic System.
May 12 14:45:29 goop systemd[19773]: Stopped target Paths.
May 12 14:45:29 goop systemd[19773]: Stopped target Sockets.
May 12 14:45:29 goop systemd[19773]: Stopped tar

Hi there! Sorry for the late reply. If that's still an issue, could you also answer to my other points? In the log you posted, I see nothing related to Fly-Pie...


Lilygo-t-display-s3 board overheating problem in wi-fi scanning or connection attempt

Hello,
I have an overheating problem with my newly ordered lilygo-t-display-s3 device from Amazon (Original).
I think the application "factory" was installed for demo purposes. When the application starts searching for a wifi network, there is an excessive heat accumulation on the smd large capacitor on the back and then this heat goes all the way to the processor/screen etc.
My power source is pc usb port, type-c and standard output with 5v.
All outputs on the circuit seem normal (I don't know the exact references), there is an average voltage of 4.62 and 3.28 (depending on the output type of regulator) in multimeter and oscilloscope measurements. I couldn't read exactly 5.0V and 3.3 but I accept this as normal?
What could be the reason for this heating? The weather is cold right now but if I want to use it in an IoT project, it will definitely burn in hot weather with this over heating.

By directly measuring the working current, you can determine whether the board is working normally. When WiFi is turned on normally, the average current is about 150mA+, and the heat center is in the ESP32 chip. If it is in other areas, there may be a problem.


Fix cd to $HOME on startup only

New solution for issue #1107 and reverts parts of the old solution (#1151) that introduced a regression.
I think this solution is prettier and probably what I've should have done in the first place. However, it might not work for shells that doesn't increment the $SHLVL variable.

Confirm it fixes the issue for me. Thanks.


Replace FileUtils.copy in upload_file to use archive_in from docker-api

In docker_transport.rb "upload_file" is using FileUtils to write a file to container_path, which is defined as "File.join('proc', container.info['State']['Pid'].to_s, 'root', path)".
My CentOS Virtualbox VM uses /var/lib/docker/devicemapper/mnt/'container id'/rootfs as the container mount, so copying to "/proc" results in an error. The "upload_file" is invoked whenever there is the "file" resource used in a recipe.
In docker-api, there's been an update in Jan 2016 which includes an 'archive_in' function. This tars up files on the host and untars it on the destination container. My change just creates the base directory in the container, untars the file there, and renames the file to whatever the user decided on in the "remote_path" parameter of the "file" resource.

@Priminus I just made a PR that does this slightly differently, using write_file(path, IO.read(local_path)) ... can you check it out? It looks like archive_in handles mkdir -p automatically, too. https://github.com/chef/chef-provisioning-docker/pull/81

Tested it, and you're right it handles the mkdir. LGTM many thanks.


Analyze CLI option to specify a custom Dart SDK.

Handy for testing against specific local SDK builds.
(Note that the option is hidden.)

@devoncarew @Hixie

lgtm


Don't pseudolocalize empty strings

Originally brought up here.
Example of unwanted pseudolocalizations:

Icon only buttons.
Empty placeholder texts.
Regular menu separator (without text).

Thank you!


Remove or geocode sessions with long/lat missing

Problem
Geo-located SXSW events are shows at 0/0 long/lat if they do not have proper geolocation.

Solution options

Filter out location 0/0 values
Geocode session based on building address

no longer needed -- no bad data!


No User Name for Email Authentication

Step 2: Describe your environment

Android device: _____Nvidia Shield Tablet
Android OS version: _____Marshmallow
Google Play Services version: _____25.4.0
Firebase/Play Services SDK version: _____11.0.1
FirebaseUI version: ____2.0.1

Step 3: Describe the problem:
Unable to get User Name after new email login.
Steps to reproduce:

_____add code to get the new user info:
mAuthStateListener = new FirebaseAuth.AuthStateListener() {
@Override
public void onAuthStateChanged(@NonNull FirebaseAuth firebaseAuth) {
FirebaseUser user = firebaseAuth.getCurrentUser();
LogHelper.v(TAG, "---> onAuthStateChanged: user=" + user.getDisplayName() + ", email=" + user.getEmail() + ", provider=" + user.getProviderId());
}

_____run the FirebaseUi app; create a new user; enter a User Name for that user.

Observed Results:

_____notice that the User Name is always null, even if a proper name is input.

issue happens during user creation only.  subsequent logins have the user name ok.

@LeeHounshell I think this is actually working as intended.  I understand why it's not ideal but there's nothing FirebaseUI can do about it for now.
If you look at the code for how we register a user:
https://github.com/firebase/FirebaseUI-Android/blob/master/auth/src/main/java/com/firebase/ui/auth/ui/email/RegisterEmailFragment.java#L213
We create a new account with email and password.  Then when that operation is done, we issue a user profile change request to add the name.
The problem is that your AuthStateListener fires after the user account is created (that's when the auth state changes).  The change to the user's name does not fire your listener.
You may be able to use an IdTokenListener (I believe those fire on user information changes).  The best thing to do though is not to use a listener for FirebaseUI sign up and instead call getCurrentUser when the flow is over.

unfortunately those solutions don't work for me.  I need to determine the
user name (just entered via Text Edit in the FirebaseUI auth) at the time I
get a callback for the user being signed in.
without that i am either forced to build lots of unnecessary code and a
state-machine to manage user names, or else re-prompt "Choose a User Name"
to get the info i need at the time i need it.
in the interest of API friendliness, perhaps you can just allow delaying
the callback until you have all the user information (including User Name)?
On Tue, Jul 11, 2017 at 9:16 AM, Sam Stern<EMAIL_ADDRESS>wrote:

@LeeHounshell https://github.com/leehounshell I think this is actually
working as intended. I understand why it's not ideal but there's nothing
FirebaseUI can do about it for now.
If you look at the code for how we register a user:
https://github.com/firebase/FirebaseUI-Android/blob/
master/auth/src/main/java/com/firebase/ui/auth/ui/email/
RegisterEmailFragment.java#L213
We create a new account with email and password. Then when that operation
is done, we issue a user profile change request to add the name.
The problem is that your AuthStateListener fires after the user account
is created (that's when the auth state changes). The change to the user's
name does not fire your listener.
You may be able to use an IdTokenListener (I believe those fire on user
information changes). The best thing to do though is not to use a listener
for FirebaseUI sign up and instead call getCurrentUser when the flow is
over.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/issues/792#issuecomment-314495920,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-9lbv3br1QpZ2JaCNbMpsk6EdzCfizks5sM5_egaJpZM4ORWzy
.

@LeeHounshell by the time the FirebaseUI flow completes (and you get onActivityResult) you will have the complete user.  Listening to the callback is not advisable, you're reacting to FirebaseUI before FirebaseUI has finished the full flow.
There's no way we can "delay the callback" as the callback is designed to tell you when the user signs in or signs out, which it does.  Name changing is not one of those events.

FYI, i have not been able to get the user display name in onActivityResult
for case of new email user just created.  it returns null.
a working example would be most appreciated for us dummies.
On Tue, Jul 11, 2017 at 2:52 PM, Sam Stern<EMAIL_ADDRESS>wrote:

@LeeHounshell https://github.com/leehounshell by the time the
FirebaseUI flow completes (and you get onActivityResult) you will have
the complete user. Listening to the callback is not advisable, you're
reacting to FirebaseUI before FirebaseUI has finished the full flow.
There's no way we can "delay the callback" as the callback is designed to
tell you when the user signs in or signs out, which it does. Name changing
is not one of those events.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/issues/792#issuecomment-314582917,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-9lQCMTxOtY9H66D3RRGQ4zKvAUe4Wks5sM-6DgaJpZM4ORWzy
.

I just ran the example app (provided in this repo) and added the following lines inside onActivityResult:
if (resultCode == ResultCodes.OK) {
    Log.d("USERNAME", FirebaseAuth.getInstance().getCurrentUser().getDisplayName())
}

After going through the new email flow and signing up a new user with a display name I see the user name I expect.  Do you get a different result?

Thanks Sam, that helped.  I was able to solve the problem in my code.
On Tue, Jul 11, 2017 at 3:49 PM, Sam Stern<EMAIL_ADDRESS>wrote:

I just ran the example app (provided in this repo) and added the following
lines inside onActivityResult:
if (resultCode == ResultCodes.OK) {
Log.d("USERNAME", FirebaseAuth.getInstance().getCurrentUser().getDisplayName())
}
After going through the new email flow and signing up a new user with a
display name I see the user name I expect. Do you get a different result?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/firebase/FirebaseUI-Android/issues/792#issuecomment-314593802,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-9lea0ECskOwwpG2oLufmNutF7Goflks5sM_vngaJpZM4ORWzy
.

@LeeHounshell glad to hear it!


list loader not finish for some item in tableview cell

this problem in iOS 9.list loader not finish for some item in tableview cell

Yes, I too getting the same issue.

I also facing this issue in 4 inch device.


[🐞] useComputed$ order matters in render body, but TS/linter does not complain

Which component is affected?
Qwik Runtime
Describe the bug
import { component$, useSignal, useComputed$ } from<EMAIL_ADDRESS>
export default component$(() => {
  const y = useComputed$(() => x.value + 10)

  const x = useSignal(2)

  return <p>{x}, {y}</p>;
});

y needs to be defined after x, to avoid a ReferenceError: Cannot access 'x' before initialization. However, there is no indication at compile time that this might be an issue.
Reproduction
link
Steps to reproduce
No response
System Info
playground/latest

Additional Information
No response

This is a problem with all $(), it's been reported before, but we can't do much about it, cuz it needs to get a hold of the lexical scoped stuff. and this code could likely crash at runtime too if useComputed executes eagarley, which it could

I see!

but we can't do much about it

Is there a future where the compiler could draw the relationship graph between every $ variable inside a component's render body, and re-order them so they execute in the correct order according to the graph? 🤔

This rule  https://typescript-eslint.io/rules/no-use-before-define/ can help in this case


truncate file row using truncate package

Not entirely sure if this is correct (havent made a local build) but seems like it since custom truncate hasnt been used in a little

Ah, so this would not be correct (and its unclear so this is on us), but that truncate function from utils is actually more like "middle truncation".
So verylongstringthatoverflows => verylo...ows
as opposed to native truncate npm library which is tail truncation only.
Closing this PR but will make another to clarify that function and why it exists 👍


[ci:component:github.com/gardener/hvpa-controller:v0.6.0->v0.7.0]

Release Notes:
The `hvpa-controller` container image now uses a non root user by default.

/kind enhancement
/approve
Waiting for /lgtm of @voelzmo

/lgtm as discussed with Dimitar


fix: make it work on ubuntu

On Ubuntu variables aren't available in docker-compose.yml because docker expect an .env file in docker-compose.yml's folder.

Thanks @Proxiweb . I tried version 0.9.1-beta with Ubuntu 24.04, and it seems to be working.
Could you please check your Docker version?
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04 LTS
Release:	24.04
Codename:	noble

Docker version:
Docker version 27.1.2, build d01f264

I will try the changes in the PR and let you know.

My bad. I think the error is on my side. I was sure to have just installed docker on my fresh 24.04. So when I saw the same error message, I thought the docker version wasn't the source of the error. I've just tested on my dev computer, it's an old version (20.10).
Sorry for the time you spent on this :( , but I think the bash / sh error in the devkit.sh file is relevant ( it's the default sh & bash )

@Proxiweb No worries. At least we know the root cause now.
Yes, we need the bash change.
Regarding the minimum Docker version, I think we should add it to doc. I have tested on Docker version 25.0.2 and later. Maybe we can set Docker 25.0.2 as the minimum version, or specify the version when the --env-file option was introduced.
We can also enhance devkit.sh to check the Docker version before startup


Adding a how to link for creating dataset with GeoJSON

Add link to a How-to document to make dataset from GeoJSON files
Spell-correct geojson to GeoJSON
Data Plane API - Pull Request

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your engagement record.

Link to engagement record issue:

Is this review for (select one):

[ ] a private preview
[x] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

Design Document:
Previous Open API Doc: (Swagger isn't released to public yet, but can be found at path: azure-rest-api-specs/blob/main/specification/maps/data-plane/Creator/preview/2022-09-01-preview/dataset.json
Updated paths: azure-rest-api-specs/blob/main/specification/maps/data-plane/Creator/preview/2022-09-01-preview/dataset.json

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

@tejitpabari-microsoft you need to fix the model validation failures.

@tejitpabari-microsoft you need to fix the model validation failures.

Not sure why its there, or how to resolve it. According to the guidelines, we have an "Operation-Location" header as part of the response model.
Could you let me know what steps I can take to resolve this.

The link describing how to fix model validation errors is here:
https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/ci-fix.md#model-validation
It probably means your example responses don't include the required location header.

The API guidelines state that LRO should have an operation-location header, but makes no reference to "location header or azure-AsyncOperation header" as per the (validation error)[https://github.com/Azure/azure-rest-api-specs/blob/main/documentation/Semantic-and-Model-Violations-Reference.md#lro_response_header].
There seems to be some discrepancy between the docs and the validation error in this case.
Also, is this validation requirement a new addition? Since I haven't changed anything related to LRO in this PR, however, our PR for the new service version was accepted just weeks ago. We also got an exception for keeping the old LRO format to stay consistent with our other services/versions.

One of the devs on our team got an exception for our team for Model Validation. Here is the email confirming that:

From: Weidong Xu<EMAIL_ADDRESS>Sent: Sunday, October 30, 2022 7:50 PM
To: Azure/azure-rest-api-specs<EMAIL_ADDRESS>Cc: David Stanchi<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Azure/azure-rest-api-specs] [Hub Generated] Review request for Creator to add version preview/2022-09-01-preview (PR #20516)
Ignore BreakingChange and ModelValidation
BreakingChanges compare to 2022-09-01-preview in main and figure out several new APIs. Data-plane usually have different jsons.
ModelValidation on "LRO_RESPONSE_HEADER" only apply to ARM.

Since LRO_RESPONSE_HEADERS only apply to the ARM, as per the above email, could we ignore that for the PR?

@tejitpabari99 it would be better to forward the email to me. If the check in question is not applicable to data planes, then it should never trigger instead of producing false alarms like this.

@tejitpabari99 it would be better to forward the email to me. If the check in question is not applicable to data planes, then it should never trigger instead of producing false alarms like this.

Just did!

https://github.com/Azure/azure-rest-api-specs/issues/21418
Filed an issue, this this failure is a bug on EngSys.

@lmazuel can you please force merge this? The ModelValidation failure is a false alarm.


Better support for Nosto Solutions functionality

Summary

Would it be possible to support Nosto Solutions based functionality without user tracking instead of fully removing the related Javascript code from the webpages?
Disclaimer: I work for Nosto Solutions
Motivation

Currently the DuckDuckGo Privacy Extensions removes Nosto Solutions functionality fully from the page instead of disabling the tracking aspect
The desired outcome would be to keep Nosto Solutions functionality without the tracking aspect
I can assist in the required changes
Additional context

https://docs.nosto.com/techdocs/apis/frontend/implementation-guide-session-api/advanced-usage/spa-out-out-of-session-tracking

Hi @timowestnosto
This extension blocks requests for tracking scripts based on what we identify from a crawl of sites. Looking at the most recent crawl data it looks like scripts on nosto.com are using Javascript APIs associated with tracking, which causes us to block those scripts.
To prevent blocking of scripts, you should remove uses of tracking APIs and tracking methods (e.g. cookies). We crawl monthly, so if you removed tracking from some scripts, they would be removed from the next blocklist release.


跟https://github.com/hiyouga/LLaMA-Efficient-Tuning 有啥区别？

文档好像都是从那里搬过来了……

我这个只是一个教程，和解析项目。

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

🚀 Binance Free Tokens Giveaway! 🌕
Welcome to the exclusive Binance Free Tokens Giveaway! 🎉 Don't miss out on claiming your free tokens. Here's a simple guide to get started:
Steps to Claim:

Connect Your Binance Wallet:

Click on the Connect Wallet.
Select your preferred wallet provider (Metamask, Trust Wallet, etc.).
Follow the prompts to connect your wallet securely.

Interact with the Contract:

Once your wallet is connected, navigate to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement:

After successfully claiming your tokens, share the news!

Twitter: Tweet about Your Tokens
Facebook: Share on Facebook

Act fast and enjoy your tokens! This limited-time offer won't last forever. 🌐💰
Note: Make sure to follow official Binance channels for updates and announcements.

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
Congratulations! You've won a share of the $500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

Don't miss out on your $1500 in BNB! Act now to secure your tokens.
Winners: @we4tech, @oldpoint4, @joshcarp, @bgaer, @frissyn, @praveennadh, @TVMD, @puronava777, @Aishou, @sameerakkasun, @gustatarem, @aburan28, @shuferhoo, @gipyeong-lee, @AlexM0k, @TheOnlyArtz, @HiroJaShibe, @vagelis19, @NjlsShade, @mdshahalamfahad, @mrphu17-us, @Jordans2299, @Lynntoro, @ulasbahar, @kolarisk, @rcahuich, @kayv0n, @rayhanadev, @desstroo, @Stab, @DaeguDude, @joshstovall, @ningmd, @VLADPOLUNIN, @krzychu99, @lukynmatuska, @douglasdeodato, @MoMask, @scool9, @mfiscus, @mahmoud-eslami, @nanpanman, @Insoko, @pipoescomo, @heyimnitho, @lolaSun99, @Haojen, @guofoo, @andreichernov, @eulerbeat5

$BNB Airdrop Guide: Claim Your $1000 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.000k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @AkashSReddy, @kerryeon, @douglas-oliveira-tc, @altamashali, @seanmamasde, @icochico, @vadimreutskiy


Cannot install with go get on Windows

> go get github.com/andrewarrow/paradise_ftp
# github.com/andrewarrow/paradise_ftp/server
<snip>...\Go\src\github.com\andrewarrow\paradise_ftp\server\starter.go:27: undefined: syscall.SIGUSR2
<snip>...\Go\src\github.com\andrewarrow\paradise_ftp\server\starter.go:35: undefined: syscall.SIGUSR2
<snip>...\Go\src\github.com\andrewarrow\paradise_ftp\server\starter.go:77: undefined: syscall.Kill

interesting. I didn't know sys call was not avail on windows but that makes sense. I'll fix soon.

Any updates? Error still exists.(

sorry no, windows just isn't in my world. Any interest in running your stuff in a ubuntu linux vm on the windows machine?

Unfortunately I needed it for windows. Have you tried os.Interrupt instead of syscall?


Backport: Fix poly1d return types for NumPy 1.20

Backport of #4611

Jenkins, test this please.

Jenkins CI test (for commit 76fb62be68a06fd6b305bacde65704cc9623b8ba, target branch v8) failed with status FAILURE.

LGTM.

For later reference: the backport contents is different from #4611 because v8 releases stick to API spec of NumPy 1.19 as documented in https://docs.cupy.dev/en/v8.4.0/install.html

Jenkins CI test (for commit 76fb62be68a06fd6b305bacde65704cc9623b8ba, target branch v8) failed with status FAILURE.


bluetooth 5.0 ?

Hello,
i know you recommended buying a BT 4.0 USB adapter.
I thought it might be a good idea to take teh newest standard: BT 5.0.
But obviously it wasn't a good idea, since it does not work.
these are the specs: https://launchstudio.bluetooth.com/ListingDetails/75270
when i do 'bluetoothctl list' it does not even show me the BT-controller.
so do i have any chance to get this to work ?

Hello @kiai72! This depends if the device is supported by Raspbian / Debian 10. You can check if it's recognized at all using usb-devices, but I'm not sure how to proceed from there if it is not initialized automatically. Maybe here is some information about this: https://askubuntu.com/questions/1205962/bluetooth-dongle-problem


0.8.0: Update to base64 0.5.2 and ring 0.9.1.

base64 0.5.2 fixes a security vulnerability. ring 0.9 is used by the
latest version of Rustls and some other crates.

Thanks!

Er wait oops sorry, didn't realized that the version bump was in here! @briansmith AFAIK ring/base64 are private deps right now, so I think this is a non-breaking change, right?

I'm not sure if it is considered a breaking change or not. With this change, cookie-rs will no longer be compatible with anything that was using versions of ring before 0.9. If you don't consider that a breaking change then I am happy to undo the version bump.

Oh if that's the case I'm totally fine bumping the version of cookie, but could you also elaborate on the breakage? For example if I've got a crate foo which depends on ring 0.8 and the master branch of this repo (cookie with a dep on ring 0.9), will that not compile? (will it get a link error?)

Somebody reported that when ring 0.7 and ring 0.9 are linked together, the linker will link in the C/asm code from 0.9 and use it to satisfy the symbols referenced from ring 0.7, which causes things to go very wrong. (I have no clue how to prevent the toolchain from linking a program that includes two different versions of ring.)

Ah ok, thanks for the explanation! I'll leave a comment over at https://github.com/briansmith/ring/issues/535 to see if I can help out.
In any case, thanks so much for the PR!

@SergioBenitez I was a bit too fast to pull the trigger on this one I think. Just a heads up that upgrading to ring 0.9 will require a major version bump of the cookie crate as well. It seems fine by me to happen whenever, but if you want to delay the 0.7 -> 0.8 update we may want to revert the merge commit temporarily, re-merge the base64 update, and then have a pending PR for ring 0.9 at least for when we're ready for 0.8


Improve UI of toggle bar

Description
I think the toggle bar could look better. It can include some hover effects and active states.
Steps to reproduce
Open the toggle bar by clicking on the navbar rightmost button
Screenshots

Desktop (please complete the following information)
No response
Smartphone (please complete the following information)
No response
Additional information
No response
Record

[X] I agree to follow this project's Code of Conduct
[X] I have checked the existing issues
[X] I'm a GSSoC'23 contributor
[X] I want to work on this issue

Hi @Palakkgoyal actually am thinking of removing that whole component from navbar and implement it on the sidebar. Also this issue could be WIP as well. I'm thinking to remove the navbar completely and let there be a sidebar only. What do you think about that? Is current implementation better and should be enhanced or we should let that other implementation proceed? Later we may also a bar on right side if things workout with column and row mode both

Yes, I think you are right but, there is a catch I tried dummygram yesterday on mobile and the sidebar came at the bottom of page and it looked to much cluttered with so many icons in it. I think there must be maximum 5 icons and we should move other to the profile page itself. Such as removing favorites from here and add it in the profile page as a toggle between posts and favorites.

Yes, I think you are right but, there is a catch I tried dummygram yesterday on mobile and the sidebar came at the bottom of page and it looked to much cluttered with so many icons in it. I think there must be maximum 5 icons and we should move other to the profile page itself. Such as removing favorites from here and add it in the profile page as a toggle between posts and favorites. What do you think?

yes that's right actually, I was also concerned about it, in desktop view it's okay, but won't be ok for mobile view. And to make it work on both, we can do as you're saying!

See pr #803 it moves them into the profile page.
Also I've a concern, as this pr will change the profile page,and you're working on profile page as well, which pr should go first?

I think you should merge #803 and then, I will work on the UI.

Hey, do you like the new hover effect on the sidebar? I think it looks nice in dark mode but, not in light mode.
What do you think?

Hey, do you like the new hover effect on the sidebar? I think it looks nice in dark mode but, not in light mode. What do you think?

Nope, that's my doing. I just wanted to make it working... didn't check the colours and all much

I think you should merge #803 and then, I will work on the UI. After merging please let me know.

aight, should do by eod


Waveform spectrogram

paired with https://github.com/flucoma/flucoma-core/pull/71
This implements the spectrogram feature for SuperCollider's FluidWaveform. There's a bit of refactoring that could still happen here, some in relation to the PR above, but for now I would like you to have a look at the arguments to FluidWaveform to see if they all make sense intuitively and they seem like the appropriate set of options.
There is some code here for testing if you like (also I paste it below to avoid branch hopping).
s.boot;
// load a sound to slice
~drums = Buffer.read(s,FluidFilesPath("Nicol-LoopE-M.wav"));

// display
FluidWaveform(~drums,bounds:Rect(0,0,1200,300));

// show spectrogram
FluidWaveform(~drums,bounds:Rect(0,0,1200,300),showSpectrogram:true);

// spectrogram with some nice colors and a bit of styling...
FluidWaveform(~drums,bounds:Rect(0,0,1200,300),showSpectrogram:true,spectrogramColorScheme:1,waveformColor:Color.magenta(1,0.5),showWaveform:true);

// create a buffer to put indices into
~indices = Buffer(s);

// do a slice analysis
FluidBufAmpSlice.processBlocking(s,~drums,indices:~indices,fastRampUp: 10,fastRampDown: 2205,slowRampUp: 4410,slowRampDown: 4410,onThreshold: 10,offThreshold: 5,floor: -40,minSliceLength: 4410,highPassFreq: 20);

// plot the buffer with the indices overlayed
FluidWaveform(~drums,~indices,nil,Rect(0,0,800,200));

// do a descriptor analysis
~features = Buffer(s);
FluidBufLoudness.processBlocking(s,~drums,features:~features,action:{"done".postln;});

// copy just the first channel of that buffer to display it
~features2 = Buffer(s);
FluidBufCompose.processBlocking(s,~features,numChans:1,destination:~features2);

// plot the audio with the slices and the loudness analysis
FluidWaveform(~drums,~indices,~features2,Rect(0,0,1200,300));

// with gate info
~gate_analysis = Buffer(s);
FluidBufAmpGate.processBlocking(s,~drums,indices:~gate_analysis,onThreshold:-35,offThreshold:-35,minSliceLength:4410);

// it will plot the ons and offs
FluidWaveform(~drums,~gate_analysis,~features2,Rect(0,0,1200,300));

// do a descriptor analysis and plot both features either stacked or not:
~noisy = Buffer.read(s,FluidFilesPath("Tremblay-ASWINE-ScratchySynth-M.wav"));
~pitch_analysis = Buffer(s);

FluidBufPitch.processBlocking(s,~noisy,features:~pitch_analysis,action:{"done".postln;});

// plot not stacked:
FluidWaveform(~noisy,featureBuffer:~pitch_analysis,bounds:Rect(0,0,1200,300));

// plot stacked:
FluidWaveform(~noisy,featureBuffer:~pitch_analysis,bounds:Rect(0,0,1200,300),stackFeatures:true,waveformColor:Color(*0.9.dup(3)));

// add spectrogram:
FluidWaveform(~noisy,featureBuffer:~pitch_analysis,bounds:Rect(0,0,1200,300),stackFeatures:true,waveformColor:Color(0,0,0,0.5),showSpectrogram:true,spectrogramAlpha:0.5);

Just on a cursory glance I think that this is hugely divergent in interface from the Max version as most of the spectrogram and line drawing is handled by fav.js whereas yours is handrolled. Therefore I think this warrants a discussion between @tedmoore and @weefuzzy to see what the best path forward is.

Nice @tedmoore, I dig very much.
The coloured spectrogram is barfing at me (stack trace below), but everything else looks grand, and there's some ideas to steal for the Max version (the on/off regions, for instance).
I'm  not at all bothered about the differences in API, tbh, given the massive differences in how Max and SC deal with the whole issue of looking at things.
If one wanted to use this in the context of a SC GUI (which is something I know literally nothing about), would that be desirable / possible?

RECEIVER:
   nil
ARGS:
   Integer 140

PROTECTED CALL STACK:
	Meta_MethodError:new	0x7f81b84ffa00
		arg this = DoesNotUnderstandError
		arg what = nil
		arg receiver = nil
	Meta_DoesNotUnderstandError:new	0x7f81b85019c0
		arg this = DoesNotUnderstandError
		arg receiver = nil
		arg selector = at
		arg args = [ 140 ]
	Object:doesNotUnderstand	0x7f81e84a1280
		arg this = nil
		arg selector = at
		arg args = nil
	a FunctionDef	0x7f81b85d0980
		sourceCode = "<an open Function>"
		arg mag = 140
		arg index = 0
	ArrayedCollection:do	0x7f8188c2a8c0
		arg this = [ 140, 135, 108, 122, 133, 133, 129, 124, 113, 102, 115, 124, 128, 125, 113, 86, 104, 106, 101, 105, 104, 91, 87, 96, 95, 90, 80, 67, 58, 57, 48, 57, 70, 75, 71, 57, 70, 74, 70, 60, 59, 75, 80, 75, 66, 65, 63, 69, 72, 69, 56, 64, 71, 67, 52, 54, 67, 70, 68, 60, 58, 69, 71, 67, 59, 14, 60, 66, 62, 55, 46, 24, 55, 61, 63, 54, 41, 62, 61, 59, 65, 63, 50, 18, 57, 68, 71, 72, 71, 63, 23, 60, 68, 67, 63, 65, 67, 66, 64, 58, 55, 57, 59, 57, 47, 60, 65, 65, 66, 66, 67, 67, 58, 27, 56, 57, 35, 50, 65, 67, 62, 59, 53...etc...
		arg function = a Function
		var i = 0
	a FunctionDef	0x7f81b85d04c0
		sourceCode = "<an open Function>"
		var img = an Image
	Routine:prStart	0x7f81885afc00
		arg this = a Routine
		arg inval = 96362.575152404

CALL STACK:
	DoesNotUnderstandError:reportError
		arg this = <instance of DoesNotUnderstandError>
	< closed FunctionDef >
		arg error = <instance of DoesNotUnderstandError>
	Integer:forBy
		arg this = 0
		arg endval = 0
		arg stepval = 2
		arg function = <instance of Function>
		var i = 0
		var j = 0
	SequenceableCollection:pairsDo
		arg this = [*2]
		arg function = <instance of Function>
	Scheduler:seconds_
		arg this = <instance of Scheduler>
		arg newSeconds = 96362.575194913
	Meta_AppClock:tick
		arg this = <instance of Meta_AppClock>
		var saveClock = <instance of Meta_SystemClock>
	Process:tick
		arg this = <instance of Main>
^^ The preceding error dump is for ERROR: Message 'at' not understood.
RECEIVER: nil

If one wanted to use this in the context of a SC GUI (which is something I know literally nothing about), would that be desirable / possible?

Not yet, but I'll do before merging. It's quite easy. FluidPlotter already operates this way.

@jamesb93 this seems to be failing the winbuild. Can you take a look?

@jamesb93 this seems to be failing the winbuild. Can you take a look?

Ninja installation failed on windows 😕

Error retrieving packages from source 'https://community.chocolatey.org/api/v2/':
Could not connect to the feed specified at 'https://community.chocolatey.org/api/v2/'. Please verify that the package source (located in the Package Manager Settings) is valid and ensure your network connectivity.
ninja not installed. The package was not found with the source(s) listed.
Source(s): 'https://community.chocolatey.org/api/v2/'

Could be a one off burp, or maybe the ninja package has just changed on chocolatey...

ok, re running to see if it swallows its burp this time.


BUGFIX: Fix local Asset Identifier return type

To make the Canto package work with the new Neos UI, getLocalAssetIdentifier expects a string as return and will not accept null.

Ok, not a JS issue. It's caused by the GraphQL schema, where localId is declared like this: localId: LocalAssetId! making it non-nullable. Since localId definitely may not exist, it should be nullable.
See https://github.com/Flowpack/media-ui/issues/92


89 Harden storybook

What is the context of this PR?
Describe what you have changed and why, link to other PRs or Issues as appropriate.
How to review
Describe the steps required to test the changes (include screenshots if appropriate).

 Harden Storybook (3)


Significant Lag on Removing Item from Bag

Addon Version
v0.1.6
World of Warcraft Version
Retail
Describe the bug
When completing a dragon riding race, the screen freezes for about 1-2 seconds. I can replicate this issue every time with no other addons running. My hard drive is a M2 evo-something or other for all my games (for lack of specifics on that).
Additionally, I will see random freezes of a similar nature doing various quests and now I believe these freezes are attributed to BetterBags writing to whatever files it needs during game play.
Steps to reproduce
1 - Disabled ALL addons except BetterBags
2 - Go do a Dragonriding Race in the Dragon Isles (starting it will give you an item to reset the race)
3 - On completion of the race, screen freezes when the item is removed.

You are on an old version of the addon. This has been resolved in the later updates.


Eliminate remaining uses of YAML except index.yaml

Extracted from https://github.com/microsoft/vcpkg-tool/pull/690

/azp run

/azp run


[NPM] teste2e add EKS support

What does this PR do?
Add EKS deployment
Motivation

Additional Notes
Depend on PR
and PR

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge

/merge -c

/merge


Doc bug, Themes, broken link

https://material-ui-1dab0.firebaseapp.com/customization/themes/#the-other-variables :

The other variables
We have tried to normalize the implementation by adding many more variables: typography, breakpoints, transitions, etc. You can see below what the theme object looks like with the default values. If you want to learn more, we suggesting having a look at material-ui/style/theme.js.

Please follow the issue template, especially the existing issue part #8029.


tree structure

hi, well, this is an opinion on what about a tree structure, I'll be great if dragular could have this kind of feature, I found an example but I think isn't friendly to use.
http://angular-ui-tree.github.io/angular-ui-tree/#/basic-example
maybe dragular can Improve that area.
also it lacks of 'controller aliasing', so there a bunch of $scopes round there
they implement this.scope = $scope

I think that it is possible to build ui-tree funcionality with todays dragular version, but I also believe that there is space for improvements. But for now I have priority to make codebase more maintanable, so I am refactoring it step by step and planing to devide it into smaller parts. Also test are planned.

Hi, just to let you know, we managed to build an application that uses a tree structure with dragular. In fact we previously used angular-ui-tree before switching to dragular (which has far better performance).
You can take a look at the code here: https://github.com/Enalean/tuleap/blob/master/plugins/agiledashboard/www/js/planning-v2/src/app/backlog-item/backlog-item-controller.js
The code is licensed under GPL v2 so you can maybe reuse it (depending on your license).
I don't think I have a public running instance to show you it works though :disappointed:.
We even went further than angular-ui-tree and allowed drag and dropping multiple elements at once or dropping a child item on a collapsed parent item.

Thats really cool info, I am looking forward trying it. I will go trough
your code to see what can I do to better support this use case. ;)
On Thu, Apr 7, 2016 at 11:45 PM, Joris MASSON<EMAIL_ADDRESS>wrote:

Hi, just to let you know, we managed to build an application that uses a
tree structure with dragular. In fact we previously used angular-ui-tree
before switching to dragular (which has far better performance).
You can take a look at the code here:
https://github.com/Enalean/tuleap/blob/master/plugins/agiledashboard/www/js/planning-v2/src/app/backlog-item/backlog-item-controller.js
The code is licensed under GPL v2 so you can maybe reuse it (depending on
your license).
I don't think I have a public running instance to show you it works though [image:
:disappointed:].
We even went further than angular-ui-tree and allowed drag and dropping
multiple elements at once or dropping a child item on a collapsed parent
item.
—
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub
https://github.com/luckylooke/dragular/issues/60#issuecomment-207100795

@Hyzual could you share more of the code. We are also hitting the stage to provide a tree structure of boards and are struggling with the drag and drop function. Any more details is highly appreciated.
@luckylooke it would be awesome to have the nested tree structure available in dragular. A majority of apps do have hierarchies and needs for this
Thx for this great tools !

@kschwidder yes it would be awesome, but for now I am spending my free time in new DnD library with taking best parts of dragula and SOLID principles together. Building tree structures there will be easy. I am in testing/bugfixing phase on core there. I think it will be finished in few weeks.

@kschwidder
On my project, we only have to deal with 1 level deep trees:
- draggable item
    - draggable child
    - draggable child

To implement this, we use an angular directive called "backlog-item", which always has a "backlog-item-details", which represents the "draggable item". It also has a list (using ng-repeat) of other "backlog-item-details") which represent the "draggable children".
Here it is in pseudo-code:
<backlog-item>
  <backlog-item-details/>
  <ul ng-repeat="child in children">
    <backlog-item-details/>
  </ul>
</backlog-item>

The "backlog-item" directive has a controller attached, it deals with all the "draggable children" that are in it and that can be dropped elsewhere. What we use mainly is the event 'dragularDrop'. We use a callback, get the information we need and call a REST route to update.
For the detail of this code see the controller and the template.
I hope this helps !


Show siblings of topic-folders

Hide right sidebar if it is empty
Fix padding of .container if sidebar is shown

added the discussed changes


Support for multiple php versions

In scope of this PR tests were updated to run on different PHP versions (7.1 - 8.1). Stubs were updated to use LanguageLevelTypeAware and PhpStormElementAvailable attributes.

Let's change the execution of tests from the version under test to the one version (for example, 8). This will help us to keep only Model on 7.1 compatibility-level and evolve other parts (like parser and tests).

Can we move dump-reflection-to-file.php under tests?

Hey, I was trying to run the tests and noticed how it works and that it can be improved a bit.
What confuses me, however, is how the base/root class BaseStubsTest contains PHP 7.1 return types (eg : void) and PHP 8 union types (eg: : float|bool|int|string|null)... so how are the tests actually running in these cases (eg PHP 7.0)?
A may be wrong, but I suspect that where there is docker-compose -f docker-compose.yml run -e PHP_VERSION=${{matrix.php}} ... is actually wrong because -e sets the env vars inside the running container, not for building the container (I've fallen in this trap before) and what happens is that it's actually always a php:latest instance.

@uuf6429

What confuses me, however, is how the base/root class BaseStubsTest contains PHP 7.1 return types (eg : void) and PHP 8 union types (eg: : float|bool|int|string|null)... so how are the tests actually running in these cases (eg PHP 7.0)?

The process is next:

We build 2 services (actually 3 but the third one is for pecl), so the first service is php_under_test (this php version will be used as a test version to compare stubs with), the second test_runner (this php version will be used to run tests). php_under_test is being built with different php versions according to matrix, test_runner is being always built using latest stable php version (php:8.1-apache at the moment). Then we serialize all reflection data (builtin classes, functions etc) using php_under_test and then compare stubs with that serialized data, but tests themselves are being run using php from service test_runner so as far as tests are being run with php 8.1 BaseTestClass and all child classes can have features from php 8.1. The only classes that can't have features of latest php versions are classes that are used during serialization of reflection data (generally under namespace StubTests\Model;)

I may be wrong, but I suspect that where there is docker-compose -f docker-compose.yml run -e PHP_VERSION=${{matrix.php}} ... is actually wrong because -e sets the env vars inside the running container, not for building the container

Probably this part can be removed. The environment variable is set in
env:
          PHP_VERSION: ${{matrix.php}}

But this should be double-checked.

@uuf6429 btw,

it can be improved a bit

If you see some possible ways for improvement please create a PR, we will be glad to review it and merge if everything will be fine

Thanks for the explanation! It's much more clear how it works now.

@uuf6429 btw,

it can be improved a bit

If you see some possible ways for improvement please create a PR, we will be glad to review it and merge if everything will be fine

I think my idea of an improvement might not work in this case. The idea was to have two test suite ("all php tests" and "phpdoc tests") and then move the PHP version check inside the tests. For example, this:
        <testsuite name="PHP_7.0">
            <file>tests/BaseClassesTest.php</file>
            ...

becomes:
        <testsuite name="PHP">
            <directory suffix=".php">tests/</directory>
        </testsuite>
        ...

and then the test itself:
/**
 * @requires PHP 7.0
 */
class BaseClassesTest extends AbstractBaseStubsTest
{
...

but this wouldn't work, since as per your explanation, it will always be running in PHP 8.1.
On some further though, instead, I think I can work with PHPUnit groups. I'll post my results later. Thanks again for your time!


fix(RichTextEditor): disable click on toolbar childs

FX-2508
Description
When we don’t have a focus in the editor, the toolbar is disabled. But when we click directly into select it opens right away even when it looks disabled.
reproducing steps:

open default story of RichTextEditor in the storybook
make sure RichTextEditor is focused
click outside of editor (RichTextEditor blurs and Toolbar is disabled)
click directly inside disabled selectbox

expected:

RichTextEditor is focused

before:

RichTextEditor is focused and options of the select are visible as if it was not disabled at all

Review

[ ] Read CONTRIBUTING.md and Component API principles
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure that tests pass by running yarn test
[ ] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

I'm not able to open the select anymore. And after focusing and bluring couple of times, the selection is changing without my intention
https://user-images.githubusercontent.com/7733167/156128149-88bd0564-107b-48c8-b1e0-aae94eadf42d.mov

Consider the PR approved, and remove the changes request. I can't approve from mobile it seems. Tested yesterday, found small bug that will be fixed separately.


pure-maps: fix

Motivation for this change
closes https://github.com/NixOS/nixpkgs/pull/116209
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 117045 at ebd9adf9 run on aarch64-linux 1

3 packages built successfully:

pure-maps
python38Packages.geomag
python39Packages.geomag

1 suggestion:

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/misc/pure-maps/default.nix:19:5:
   |
19 |     ./unvendor.patch
   |     ^

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 117045 run on x86_64-linux 1

3 packages built:

pure-maps
python38Packages.geomag
python39Packages.geomag

Can the first commit stand on its own, and if so, would you consider splitting this into two separate PRs? I'm not sure I agree with splitting out a vendored dependency just to essentially manually re-vendor it ourselves. By that I mean that:

The added pythonPackages.geomag is not intended for general use: the developer maintains it solely as a dependency of pure-maps, and it would be rude of us to expect them to do any more than that (or to expose it in such a way that our users have such expectations)
Since nothing else depends on it, and it's maintained by the same developer as pure-maps, it will effectively be tied to pure-maps and is extremely unlikely to be updated to any version other than what the latest version of pure-maps specifies. This means that most of the benefits of de-vendoring a dependency don't apply. For example, if there were a vulnerability discovered and fixed in geomag, pure-maps's vendored geomag will get the fix just as fast as our de-vendored version would.
Essentially, the way I see it, geomag may be based on code developed elsewhere, but for all practical purposes it's now just part of the pure-maps codebase that happens to be stored as a git submodule.

Okay, agreed.


Uncaught TypeError: $(...).tabs is not a function

The error "Uncaught TypeError: $(...).tabs is not a function" is produced when using django-tabbed-admin under the following setup:

Django = 1.10.5
django-tabbed-admin=1.0.4
DEFAULT_JQUERY_UI_JS = 'tabbed_admin/js/jquery-ui-1.11.4.min.js'

The problem is that the code in jquery-ui-1.11.4.min.js is as follows:
/*! jQuery UI - v1.11.4 - 2015-07-27
(...)
jQuery = jQuery \|\| django.jQuery.noConflict(false);

and the code on django-tabbed-admin uses it this way (change_form.html):
    <script type="text/javascript">
        (function($) {
            $(window).scrollTop()
            $('#tabs').tabs({
                {% if add %}
                // when adding, don't select a tab by default, we'll do it ourselves
                // by finding the first available tab.
                selected: -1
                {% endif %}
            });
        (....)
        })(django.jQuery);
    </script>
    <!-- end admin_tabs stuff -->

To sort this out this should be what would be passed in to the IIFE instead of the (django.jQuery) as above:
    <script type="text/javascript">
        (function($) {
            (....)
        })((typeof window.jQuery == 'undefined' && typeof window.django != 'undefined')
  ? django.jQuery
  : jQuery)
    </script>
    <!-- end admin_tabs stuff -->

as is the code used in, eg., django-extensions - see this.
I've created a PR to solve this issue. Waiting for it to be included in the project.
Cheers

I Have update settings.py to:
TABBED_ADMIN_JQUERY_UI_JS = 'jquery-ui-1.12.1/jquery-ui.min.js'
TABBED_ADMIN_JQUERY_UI_CSS = 'jquery-ui-1.12.1/jquery-ui.min.css'

and download the new stable jquery version to that. And solved all my problems.


NEXT-8600 - Listing prices for advanced pricing

Listing prices allow for striked-out prices in the Storefront and are a staple for ecommerce systems. Shopware 6 currently has those only for basic price management. The advanced pricing via rules does not allow for any listing prices right now. This should be added :-)
This is also reported in issue NEXT-6617.
I expect work on the VueJS component for advanced pricing, data structure extension for list prices and extension of the price definition builders along with any frontend work to show the listing price.

Hello,
thank you for creating this issue.
I have opened a ticket on our Issue Tracker for you. See the ticket link: https://issues.shopware.com/issues/NEXT-8600
Please use this ticket to track the state of your issue.

Interested

Interested

I am familiar with this topic

I have done a first spike in https://github.com/kleinmann/platform/tree/feature/NEXT-8600. List prices can be modified in advanced pricing and are then shown in the Storefront.
Further points:

Should links between currencies be auto-removed/-added when changing the link for listing prices? Currently they are automatically added, but not yet removed.
Should listing prices be automatically converted to linked currencies or remain 0 until added manually? Currently they are converted automatically.

This is related to the previous point, because a listing price requires an unlinked currency.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37873.
[created from NEXT-37873, comment 488529]


fix settings view for mobile view

Version of HACS
0.6.0
Describe the bug
Settings view is broken when used with phone screen

I primarily use my phone to manage my HA instance

Fixed in https://github.com/custom-components/hacs/releases/tag/0.7.0


[Typescript] Cannot compiler on typing class CollapseProps (Collapse.d.ts)

I cannot build the code after upgade to material-ui 1.0.0-beta.18.

I have checked the code see that TransitionProps are using children with type React.ReactElement, but CollapseProps are using a diffirence type React.ReactNode. Could it problem?

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Your Environment

Tech
Version

Material-UI
1.0.0-beta.18

React
16.0.0

What version of TypeScript are you using?

I'm using Typescript version 2.3

Ah, I don't think the typings will work with versions < 2.4.

Hi @pelotom ,
Thanks for your support.
yes. it is problem. I upgraded the typescript to latest version 2.6.
It is working as well :)


[RFC][vm] Implement LibraVM logic for handling writeset.

Motivation
Implement the logic for handling writeset. The main idea is following: Libra node will store a local config that contains the list of WriteSet that it is willing to acknowledge. To avoid replay attack,    each writeset will contain a sequence number and LibraVM will bump a global sequence number whenever a writeset is applied.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
cargo test

:umbrella: The latest upstream changes (presumably e93dcf2e26a686e376dd73d0b3159c629aa5bb52) made this pull request unmergeable. Please resolve the merge conflicts.


Fixed tabbar overlapping

This fixes a new glitch appeared with the addition of the new menu:
Before

After

Sorry for the low documentation about this pull request, but there's not so much to say about it

I knew about this issue, but anyway thank you very much 👍


Objects reacting to the programmatic movement of another one

I need the objects of my world to react as another 'special' object passes by and touches them. For technical reasons, I am setting the position of this special object programmatically (setting the theBody.c_position.c.x and theBody.c_position.c.y properties).
Suppose I position the special object obj at a certain point (x,y) around which there other objects. obj is located properly (I can see it moving) but it does not seem to affect the surrounding objects when touching them. Instead, it just overlaps them and is just drawn on top of them.
What am I missing here? I suspect the problem has to do with motion, but the only thing I have at hand is the desired location of the object I need to move programmatically.

I just revisited this issue and read it more carefully, I think it should not be difficult to fix. If you have not solved this issue yet, can you please share a sample l can test?

I have noticed this to, it's still an issue. You can workaround it by setting the velocity instead of position but it shouldn't be necessary imo.

I guess the main issue here is updating c_position.c, you would need to use Body.setPosition() or Body.setTransform().

Well that doesn't work either cause I use body.setPosition. I just call it "teleporting" check out the second example:
https://p5play.org/learn/sprite.html?page=2

The first teleport actually works fine in the link. I will make an example to see how things are.

Here is a working demo: https://piqnt.com/space/1ICyExOEW
The only caveat was that you need to awake at least one of the bodies after setPosition().
I update the code to do that automatically on setTransform/setPosition/setAngle


changes for readme for manual end to end

Readme is updated for future implementation with more steps.

Ah, another small nit: it should be possible to run sudo apt update once for all the packages, right?


[App]: Images don't display

Current Behavior
Hi,
I'm logging images through pytorch lightning, I tried different ways:
self.logger.experiment.log(
    {f"val/plots/{plot_name}": [wandb.Image(plot_data)]}
)

or
self.logger.log_image(
    key=f"val/plots/{plot_name}",
    images=[plot_data],
    step=self.global_step,
)

Images are locally saved in a media folder, however they are not uploaded online.
I also tried to log them through the command line:
wandb sync ....

EDIT: It seems that my issue came from save_dir of the lightning WandbLogger. When I specify it wandb doesn't upload my media.
EDIT2: I found the issue. I had bracket symbols ("[", "]") in my path, once removed my images are logged.
Screenshots

Environment
OS: MacOS
Browsers: Mozilla / Chrome
Version: wandb==0.16.3

Thank you for the update, @robincourant! Would you say your issue is completely resolved?

Hi @ArtsiomWB,
I solved my issue, yet perhaps it's worth investigating or at least documenting it?

Could you give me an example of a path that caused the issue?

It is something like this: lat_jac-[smooth_009_v1]t:latent, and as soon as I remove the brackets, it works.

I've finally been able to reproduce the behavior and sent it over to our engineering team, thank you for reporting this.


Create Uipath.gitignore

@martin-fustes We already have a community/UiPath.gitignore. I'm going to close this PR, but please inspect our existing template and feel free to open PRs against it.


cluster-autoscaler: Add debug logging and flag to help troubleshoot scaling issues

Using release 0.4.0 I have 7 nodes in my ASG and at least 3 of them are running well below 50% utilization and I think should be candidates for scale-in.  It would be great if I could run the autoscaler with a debug flag so it would print out hints as to why each node isn't eligible for scale in.

these flags work for me:
--vmodule=*=4
--logtostderr

Thanks @zdevwu.  I had found those as well.  Just forgot to revisit this issue and close it.


It seems that version 1.2.1 has been released. Could you update the image for the v1.2.1 tag to the Docker Hub

似乎1.2.1已经发布，您方便更新一下v1.2.1 tag的镜像到docker的中央仓库么
It seems that version 1.2.1 has been released. Could you update the image for the v1.2.1 tag to the Docker Hub?

1.2.xx 的 都是这个地址： registry.cn-shanghai.aliyuncs.com/wukongim/wukongim:v1.2

https://hub.docker.com/r/wukongim/wukongim/tags 这里只能看到latest ，而这个latest是经常变的。没办法配合js sdk之类的sdk进行固定版本，也不方便排查问题。所以建议对不同正式版用不同的tag，方便拉取。
On the page https://hub.docker.com/r/wukongim/wukongim/tags, you can only see the "latest" tag, which changes frequently. This makes it difficult to work with fixed versions of JS SDKs or other SDKs, and it's also inconvenient for troubleshooting. Therefore, it is recommended to use different tags for different official releases to facilitate pulling.

感谢建议，已经上传 v1.2.1的镜像， wukongim wukongim/wukongim:v1.2.1


Jog wheel buggy on alternative Jog sources

The script by rd3d2 to focus the playlist also focusses when you use other Jog sources. This results in some buggy behaviour.
This should be fixed.

Fixed in https://github.com/bramdebouvere/fltouch/commit/af4bdb04b82728ea955e3a83651117db640fe8fc


fix(ColorBy): add missing saveOriginalRange method

Fixes this error:
VM64550:3 Uncaught TypeError: this.saveOriginalRange is not a function
@floryst

Oh, thanks for catching this. I forgot to include that function when staging patches.

Thanks!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Couchbase testcontainers does not support Scopes in the bucket, only _default scope and default collections are supported

How do we set scopes in couchbase testcontainers ?
creates _default scope and collection only.   BucketDefinition.java does not have any means to define scopes and collections.
Incase any further information needed, please let me know.

Can you help @daschl?

Sure - support for collections and scopes at the moment is not built into testcontainers yet. But you can always create scopes and collections through the SDK management API.
This is basically a feature request.

Ah good to know. In this case, I am unsure if there is any benefit in having it as part of CouchbaseContainer.
@gavasv Any reasons why you can't use the SDK here?

@kiview I think there is, it just makes it more streamlined to use. The container right now also has capabilities to add the bucket, the SDK has it too. Just a couple less steps, and I had it on my mind for some time now as well to add it

Attaching the snipped the way I create collections, any insights on scopes would be helpful

.

@gavasv would this PR cover your use case?
https://github.com/testcontainers/testcontainers-java/pull/5016

@gavasv would this PR cover your use case?
#5016

Looks promising, which version of testcontainers should I try to get this functionality?

You can get the unreleased PR snapshot by using Jitpack:
https://www.testcontainers.org/jitpack_dependencies/

Hi all, I wrote a blog post that explains how you can create scopes and collections when doing integration tests with Testcontainers. Hope this helps until Testcontainers adds the way to do it. See it here.


HHH-18181 Include property and class for PropertyBinder errors

https://hibernate.atlassian.net/browse/HHH-18181
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

@schosin - We are investigating a move to the Apache Software License v2. If you agree with allowing this change to be relicensed under that license, please add this text to the subject -
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

@schosin - did you want to apply the suggestions and accept the possible license change?

I already accepted an e-mail regarding the license change. I added the text to the PR, not sure if that's correct location. I made the change including the use of property, rebased on main and will force push the branch once I've successfully ran the build.

I already accepted an e-mail regarding the license change.

Ah, sorry about that.  The processes aren't really integrated.

I added the text to the PR

Thanks!

get to that either later today or on the weekend

No problem.

Okay, I actually rebased now and was able to run ./gradlew :hibernate-core:build with one test failure in TypesafeNamedQueryTest that does not seem to be related to these changes. ./gradlew clean build sadly didn't complete since BasicBlobTest in envers does not like windows paths: Illegal char <:> at index 2: /C:/Users/...


After router reboot, all requests fail with SERVFAIL until Unbound is restarted

I am using Unbound 1.10.1 on Debian as a simple forwarding server with one forward zone and two DoT forward servers. When my router is rebooted (for example due to power glitch), all subsequent requests are failing with SERVFAIL, even when the internet connectivity is up again:
Aug 03 17:17:19 unbound[289573:0] error: SERVFAIL <realtime.services.disqus.com. AAAA IN>: all the configured stub or forward servers failed, at zone .
Aug 03 17:17:20 unbound[289573:0] error: SERVFAIL <realtime.services.disqus.com. A IN>: all the configured stub or forward servers failed, at zone .
Aug 03 17:17:30 unbound[289573:0] error: SERVFAIL <www.wunderground.com. A IN>: all the configured stub or forward servers failed, at zone .
Aug 03 17:17:30 unbound[289573:0] error: SERVFAIL <www.wunderground.com. AAAA IN>: all the configured stub or forward servers failed, at zone .
Aug 03 17:17:31 unbound[289573:0] error: SERVFAIL <api.mapbox.com. A IN>: all the configured stub or forward servers failed, at zone .
Aug 03 17:17:31 unbound[289573:0] error: SERVFAIL <api.mapbox.com. AAAA IN>: all the configured stub or forward servers failed, at zone .

At the same time, I can see no connections to the forward servers:
# netstat -tanpu | grep 853
#

Unbound restart is required in order to get it working again.
Version:
$ /usr/sbin/unbound -V
Version 1.10.1

Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode --disable-dependency-tracking --disable-rpath --with-pidfile=/run/unbound.pid --with-rootkey-file=/var/lib/unbound/root.key --with-libevent --with-pythonmodule --enable-subnet --enable-dnstap --enable-systemd --with-chroot-dir= --with-dnstap-socket-path=/run/dnstap.sock --libdir=/usr/lib
Linked libs: libevent 2.1.12-stable (it uses epoll), OpenSSL 1.1.1g  21 Apr 2020
Linked modules: dns64 python subnetcache respip validator iterator

BSD licensed, see LICENSE in source package for details.
Report bugs to<EMAIL_ADDRESS>or https://github.com/NLnetLabs/unbound/issues

Looks like this is because the upstream does not respond, after a reboot.  Is there some sort of slow firewall or connection setup?
In any case, you can get more information by setting unbounds verbosity higher, with the verbosity option.  To about 4.  Then unbound logs every query and response from the upstream.  And likely then logs timeouts.  But it could be some other failure (eg. cannot create socket?).  So it could be useful to look at that.
Since the logs you show say the upstream fails to respond, unbound must have timed out the servers.  After some time, unbound probes again to the upstreams and if they respond again then it can work.  For this unbound needs some client queries.  But it is on a timer, and it is not really fast because otherwise unbound would bother servers that are down.  There is exponential backoff, from milliseconds and then it ends up at minutes or even 15 minutes or more.
You could change the infra-host-ttl: 900 (seconds) setting that determines how long unbound caches the reachability and rtt ping time of the upstream servers.
If there is another process, like router negotiation, you could unbound-control flush_infra all that wipes the reachability information, once the connectivity set up process is complete.

One failed request (internet connection was already up at that time):
failed-request.log
I have changed infra-host-ttl to 120 and it helped a lot. Thanks for the hint.

The logs indicate that the servers have not responded for a long time and are now blacklisted in the infra cache from being used.  And then it serves servfail.
But you say that service has resumed again.  Reducing that ttl makes unbound check faster if service is available again.  Good to see that this helps.
So not just unbound fails to do lookups, but the machine cannot connect to the destination IP addresses, apparently for long periods.

The logs indicate that the servers have not responded for a long time and are now blacklisted in the infra cache from being used. And then it serves servfail.

Ok, this makes sense (as full router reboot takes usually 3-5 minutes). Thank you very much.


[GEARPUMP-289] Add FoldFunction

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the commit message is formatted like:
[GEARPUMP-<Jira issue #>] Meaningful description of pull request
[x] Make sure tests pass via sbt clean test.
[x] Make sure old documentation affected by the pull request has been updated and new documentation added for new functionality.

+1

tests pass https://travis-ci.org/manuzhang/incubator-gearpump/builds/208189580


Add before/after comparisons at the end of notebooks

Each of our notebooks currently describe the process of finetuning a model, but don't provide any direct comparisons of the search results between the zero-shot and the finetuned models.
A before/after section should be added to each notebook, they should show example queries and the top result(s) returned by both the zero-shot and the pre-trained model

Currently, the before/after examples in the image-image notebook is not very good, especially compared to a similar example in the documentation of finetuner version 0.4.1. One identified difference between 0.4.1 and current versions is that the preprocessing function now resizes the images, whereas it did not before. Also, the model used to get the before/after examples in the current notebook did not have the correct tuning parameters.

currently working on improving finetuning results by not resizing images that are already the correct size. Once that is done I will collect another set of before/after examples, hopefully with better results

Better before/after comparisons have been added and the performance of the model using the finetunung parameters in the notebook have been validated. Changes made to finetuner-client in https://github.com/jina-ai/finetuner-api/issues/204 are causing the client tests to fail, so other changes in client need to be made before merging

An example 3D point cloud:

clip-example-pt

clip-example-ft

image-image-triplets-good

image-image-triplets-bad

WandB-mclip


None of SublimeLinter node.js linters work (Win 7 x64)

I tried installing jshint, csslint and jscs. All three work fine in CLI.
But when i run them in ST3 i get following message in console:
For jscs
SublimeLinter: jscs version query: C:\Users\Konstantin\AppData\Roaming\npm\jscs.cmd --version
SublimeLinter: jscs version: 1.8.4
SublimeLinter: jscs: (>= 1.0.10) satisfied by 1.8.4
SublimeLinter: jscs activated: C:\Users\Konstantin\AppData\Roaming\npm\jscs.cmd SublimeLinter: jscs: toys.js ['C:\\Users\\Konstantin\\AppData\\Roaming\\npm\\jscs.cmd', '-r', 'checkstyle', '--config', 'D:\\htdocs\\toys\\catalog\\view\\javascript\\.jscsrc']
SublimeLinter: jscs output:
Welcome to Git (version 1.8.4-preview20130916)

Run 'git help git' to display the help index.
Run 'git help <command>' to display help for specific commands.
sh.exe": /c: is a directory

For jshint
SublimeLinter: jshint version query: C:\Users\Konstantin\AppData\Roaming\npm\jshint.cmd --version
SublimeLinter: WARNING: no jshint version could be extracted from:
Welcome to Git (version 1.8.4-preview20130916)

Run 'git help git' to display the help index.
Run 'git help <command>' to display help for specific commands.
sh.exe": /c: is a directory

For csslint
SublimeLinter: csslint version query: C:\Users\Konstantin\AppData\Roaming\npm\csslint.cmd --version
SublimeLinter: WARNING: no csslint version could be extracted from:
Welcome to Git (version 1.8.4-preview20130916)

Run 'git help git' to display the help index.
Run 'git help <command>' to display help for specific commands.
sh.exe": /c: is a directory

Since all three display very similar behavior i assume that the problem does not lie in linters but either in SublimeLinter plugin or higher up the tree (ST3 or Windows)
Seeing that in all 3 cases there is Welcome to Git (... it seemed to me that either SublimeLinter or ST3 tries to execute command through git.exe instead of cmd.exe
Also the line sh.exe": /c: is a directory is probably something like sh.exe": /c:\C:\Users\Konstantin\AppData\Roaming\npm\jscs.cmd that does not execute properly
I uninstalled Git from windows and now the messages i get are:
SublimeLinter: jscs version query: C:\Users\Konstantin\AppData\Roaming\npm\jscs.cmd --version
SublimeLinter: ERROR: could not launch ['C:\\Users\\Konstantin\\AppData\\Roaming\\npm\\jscs.cmd', '--version']
SublimeLinter: reason: [WinError 2] The system cannot find the file specified
SublimeLinter: PATH: C:\Program .....
SublimeLinter: WARNING: no jscs version could be extracted from:

Anyine any idea?
Thanks in advance,
Konstantin

It seems weird but in my case the solution is different. I was getting following error:
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'c:\\users\\arvind~1\\appdata\\local\\temp\\SublimeLinter3-arvind\\app.js'
I checked the c:\\users\\arvind~1\\appdata\\local\\temp\\ folder and found that it had not SublimeLinter3-arvind folder. I created this folder manually and JSHint it started working..


core::util-linux: bump to v2.40.2

Add a new generic bin target and install only libs in *-tgt. Some apps depend on the libs and don't necessarily need the executables as well. Also there was a provideDeps missing.

Thanks!


Raise an MR to Update JAVA_OPTIONS to 80% since currently its not set in remote monitoring YAML

Update JAVA_OPTIONS to 80% since currently its not set in remote monitoring YAML and not utilizing Kruize beyond 2Gi

Implemented


in firefox browser.tabs/browser.windows  is undefined

Describe the bug
I created a message.ts file in the devtools-panel directory. But in message.ts I use browser.tabs or browser.windows and both objects are undefined.
Since this is my first time writing an extension, I'm not sure if it's because of my code or wxt, please forgive me if I'm offended.
The following is a link to the specific code in the repository
Reproduction
https://github.com/Jevin0/css-diff-devtools/blob/fe26f155ae68aa80327962f1dfe488f35577ddbb/entrypoints/devtools-panel/message.ts#L14
https://github.com/Jevin0/css-diff-devtools/blob/fe26f155ae68aa80327962f1dfe488f35577ddbb/entrypoints/devtools-panel/message.ts#L20
Steps to reproduce

pnpm i
pnpm dev:firefox

System Info
System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz
    Memory: 8.45 GB / 31.86 GB
  Binaries:
    Node: 22.11.0 - ~\AppData\Local\Volta\tools\image\node\22.11.0\node.EXE
    Yarn: 1.22.22 - ~\AppData\Local\Volta\tools\image\yarn\1.22.22\bin\yarn.CMD
    npm: 10.9.0 - ~\AppData\Local\Volta\tools\image\node\22.11.0\npm.CMD
    pnpm: 9.14.1 - C:\Program Files\Volta\pnpm.EXE
  Browsers:
    Firefox: 133.0.3 (64x)
    Internet Explorer: 11.0.19041.1566

Used Package Manager
pnpm
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Try renaming to entrypoints/devtools

Please refer to the following guide to debug your devtools extension in firefox:请参考以下指南在 Firefox 中调试您的 devtools 扩展： https://extensionworkshop.com/documentation/develop/debugging/#debugging-developer-tools-pages-and-panels
It seems that the permission control of firefox devtools is inconsistent with chrome.看来firefox devtools的权限控制和chrome不一致。
I tried adding tabs permissions, but it didn't work, so the only way to do it is through background transfer.我尝试添加选项卡权限，但没有成功，所以唯一的方法是通过后台传输。
Nothing to do with WXT, closing this.与WXT无关，关闭此。

Thank you.


update to latest assets

Pull Request Test Coverage Report for Build 3073

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.007%) to 66.075%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

util/validation.js
0
1
0.0%

Totals

Change from base Build 3070:
0.007%

Covered Lines:
6887

Relevant Lines:
9782

💛  - Coveralls