Copying files from Win10 to Kubuntu20.04  and back

Copy   ctrl+c  win10,     ctrl+v  kubuntu  works well for text.
Copy files win10 to linux   only 1 time, then you need to reconnect xrdp.
Please help.

Hi @nikimagic
Can you give us more information please.

Which version of Kubuntu are you running?
What version of xrdp (output of xrdp -v)?
How are you copying the files exactly? Is it control-c in win 10, then control-v in Kubuntu as it is for the text?

At the moment there's a bug which prevents files being copied from the thinclient_drives directory to the Linux side - see #1563. You can't do it this way.

Hi @nikimagic
Can you give us more information please.

Which version of Kubuntu are you running?
What version of xrdp (output of xrdp -v)?
How are you copying the files exactly? Is it control-c in win 10, then control-v in Kubuntu as it is for the text?

At the moment there's a bug which prevents files being copied from the thinclient_drives directory to the Linux side - see #1563. You can't do it this way.

Kubuntu 20.04  full update
xrdp 0.9.12
CTRL+C   win10   to  CTRL+V  Kubuntu
Text  good  copy
Files  only one copy.

Kubuntu 20.04  full update
xrdp 0.9.12
CTRL+C   win10   to  CTRL+V  Kubuntu
Text  good  copy
Files  only one copy.

how do i install the new version of xrdp v0.9.15 ???

how do i install the new version of xrdp v0.9.15 ???

@nikmagic - I've tried reproducing this with a very simple test as follows:-

Kubuntu 20.04 VM running XRDP v0.9.12

Win 10 VM

Two files temp1.txt and temp2.txt in Documents on Win 10 machine, contents as follows:-

temp1.txt

This is document 1

temp2.txt

This is document 2

Connect to Kubuntu machine using the file kubuntu-20.rdp. You will need to change the line full address:s:kubuntu-20 to use this in your setup. Change kubuntu-20 to the name of your target host.

Run Dolphin on Kubuntu and browse to home folder

Win 10 Explorer select temp1.txt, CTRL-C

Kubuntu Dolphin CTRL-V

Win 10 Explorer select temp2.txt, CTRL-C

Kubuntu Dolphin CTRL-V

That all seems to work OK. So there must be some difference between what I have and what you have. It could be RDP settings, filenames or file contents. Could you have a look at what I've done above and see what the differences are with your setup?
Regarding your second question, once Debian/Ubuntu is released with a version of XRDP it will stay the same except for security updates and important bug-fixes. So the 20.04 LTS versions of ?Ubuntu will only carry xrdp 0.9.12.
If you want to try 0.9.15 you'd have to build it yourself. There are instructions on the wiki if you're interested in trying this.
Finally, if you're running Kubuntu you might find the conversation at #1773 of some interest.
Let us know how you get on.

@nikmagic - I've tried reproducing this with a very simple test as follows:-

Kubuntu 20.04 VM running XRDP v0.9.12

Win 10 VM

Two files temp1.txt and temp2.txt in Documents on Win 10 machine, contents as follows:-

temp1.txt

This is document 1

temp2.txt

This is document 2

Connect to Kubuntu machine using the file kubuntu-20.rdp. You will need to change the line full address:s:kubuntu-20 to use this in your setup. Change kubuntu-20 to the name of your target host.

Run Dolphin on Kubuntu and browse to home folder

Win 10 Explorer select temp1.txt, CTRL-C

Kubuntu Dolphin CTRL-V

Win 10 Explorer select temp2.txt, CTRL-C

Kubuntu Dolphin CTRL-V

That all seems to work OK. So there must be some difference between what I have and what you have. It could be RDP settings, filenames or file contents. Could you have a look at what I've done above and see what the differences are with your setup?
Regarding your second question, once Debian/Ubuntu is released with a version of XRDP it will stay the same except for security updates and important bug-fixes. So the 20.04 LTS versions of ?Ubuntu will only carry xrdp 0.9.12.
If you want to try 0.9.15 you'd have to build it yourself. There are instructions on the wiki if you're interested in trying this.
Finally, if you're running Kubuntu you might find the conversation at #1773 of some interest.
Let us know how you get on.

The first server copies everything well.
Second server does not copy
I don’t know yet where to look, what is the difference. I think
Both servers kubunta 20.04 full update

The first server copies everything well.
Second server does not copy
I don’t know yet where to look, what is the difference. I think
Both servers kubunta 20.04 full update

It does sound rather difficult to debug.
I think you're right in that finding the difference between the two is a good place to start.
Possible areas I can think of are as follows. I expect you've tried a lot of these already:-

Contents of /etc/xrdp/sesman.ini
Login configurations. Using the same back-end (Xorg/Xvnc) on both servers.
Windows client configurations. Try swapping the Windows clients between servers.
Linux user configurations. Create new empty Linux accounts on both servers and try with those.

Has the first copy definitely finished before the second one is started? If it's a big file and a slow network it might be taking longer than expected. Disconnecting and reconnecting would stop the copy operation in progress.

It does sound rather difficult to debug.
I think you're right in that finding the difference between the two is a good place to start.
Possible areas I can think of are as follows. I expect you've tried a lot of these already:-

Contents of /etc/xrdp/sesman.ini
Login configurations. Using the same back-end (Xorg/Xvnc) on both servers.
Windows client configurations. Try swapping the Windows clients between servers.
Linux user configurations. Create new empty Linux accounts on both servers and try with those.

Has the first copy definitely finished before the second one is started? If it's a big file and a slow network it might be taking longer than expected. Disconnecting and reconnecting would stop the copy operation in progress.

Hi Matt
It turned out to be a working version on both servers.
1.sudo apt install xrdp
2. Edit /etc/xrdp/startwm.sh
3. Edit /etc/xrdp/xrdp_keyboard.ini
4. Copy /etc/polkit-1/localauthority/50-local.d/xrdp-kde.pkla (kubuntu gui reset)
5 Create new user
6 Delete old users
Copy files CTRL + C and CTRL + V ideally win 10 to kubuntu and back
Kubuntu2004_ru_kb_xrdp.zip

Hi Matt
It turned out to be a working version on both servers.
1.sudo apt install xrdp
2. Edit /etc/xrdp/startwm.sh
3. Edit /etc/xrdp/xrdp_keyboard.ini
4. Copy /etc/polkit-1/localauthority/50-local.d/xrdp-kde.pkla (kubuntu gui reset)
5 Create new user
6 Delete old users
Copy files CTRL + C and CTRL + V ideally win 10 to kubuntu and back
Kubuntu2004_ru_kb_xrdp.zip

If I understand you correctly it's working now. Is that right?
If so, we can close this one. If we get any more relevant information about exactly why it was behaving the way it was we can re-open it. Let me know.

Works, but I would like to test some more.
Let's wait a week.

large files 5 GB, copied to Linux, about 1 GB in size.
How to copy files 10 GB?
Copy-paste! Linux-> Windows.

@nikimagic - I don't understand what you're asking above. Can you be clearer please?

Closing - no more input.


Refactor AppBar to Header, move Exports to Header

The Issue

Having Download, Screenshot, and Add Custom as text within buttons makes resizing the Calendar pretty unwieldy.
Additionally, Export feels like it makes more sense being housed in the App Bar alongside Import and Load (but I do understand the reason for why it was housed within the Calendar).
 I probably should've opened a issue first, but I got carried away with just seeing what it might look like and ended up just building out the whole thing
Summary

Move download and screenshot into Export in the App Bar
Change Add Custom button to just an Icon Button

Test Plan

Screenshot and download still work
Changes are all UI/UX based, so it comes down to what makes sense for users

Issues
Closes #

Thoughts and Misc

Tweaked the padding on mobile of the Menu Icon to let it breathe a little more

Pretty unrelated, but the App Bar does get pretty cramped at smaller tablet sizes, but the Logo resizes to allow it to fit (*up until the mobile breakpoint).

The one reservation I have about this change is mainly that the "Custom" part of "Add Custom Events" isn't particularly well conveyed by just a simple Add icon. Some solutions might be to make the Add icon a variant that's a little more pronounced (such as a Plus in a Circle, etc), hinting to the user that it's not simply a basic Add Button.

Cool, I can help with this PR. The entire AppBar was supposed to be refactored from scratch, but I never got around to pushing my changes into the main branch. Just request a review whenever you're ready and I'll take a look.
The AppBar should be renamed to Header. Here's a reference of how it should actually be built.
My refactor also addresses a UI issue on the live website where hovering over a button in the mobile menu causes a double outline (this is because it currently nests a button inside of a component that was already styled to be a button).

UI/UX comment: I agree that the add custom event just being a plus sign is kinda confusing, and I think the strat might be to move it to the class search tab in the right pane instead of where it is right now, and bring back the full "Add Custom" text to make it obvious. But I don't want to scope creep this PR any further than it already is with the refactor and everything, so lmk what you think and I can create an issue for it.

Also, respectfully, can we aim to keep PR's more limited in scope in the future? Like, moving the exports to the app bar should be a completely separate concern from a total refactor of the entire component, so we can merge in the feature change super quick then spend more time worrying about the refactor without it blocking the UI/UX change.

Also, respectfully, can we aim to keep PR's more limited in scope in the future?

Sorry, the header's been bothering me for a while and I finally got the chance to scratch that itch 😅
Idk if the devops PR can be easily split up either, since all the tooling is just kind of interconnected; there are definitely files that can be pruned from the diff, but I just want to include them so I don't have to go back :^) .
I'll work on splitting up the tRPC and auth PR though

Also, respectfully, can we aim to keep PR's more limited in scope in the future?

Sorry, the header's been bothering me for a while and I finally got the chance to scratch that itch 😅
Idk if the devops PR can be easily split up either, since all the tooling is just kind of interconnected; there are definitely files that can be pruned from the diff, but I just want to include them so I don't have to go back :^) .
I'll work on splitting up the tRPC and auth PR though

Yeah I'm not saying don't refactor stuff, I'm just saying that you should try to keep your PR's as small as possible to make them easier to review, and try to refrain from tacking on changes that increase the scope of existing PR's.

UI/UX comment: I agree that the add custom event just being a plus sign is kinda confusing, and I think the strat might be to move it to the class search tab in the right pane instead of where it is right now, and bring back the full "Add Custom" text to make it obvious. But I don't want to scope creep this PR any further than it already is with the refactor and everything, so lmk what you think and I can create an issue for it.

I think moving the Custom Event button to the Search tab would cause too large of a UI/UX disconnect, so I've opted instead to revert it's design back to its previous Button form.

Previous upgrades to the toolbar now allows the components to wrap, making it look pretty nice on mobile screens as well:

Oh, yeah I added flexbox to the toolbar during the refactor. :nerd:

I know we're a tad far along into this PR, but I'm pretty strongly in favor of some sort of rebase (split?, sorry not sure of terminology) back to commit #3f1c3ca and moving the 2 or 3 other scopes (Appbar/Header, Markdown, etc) included within this PR into their own PRs.
My reasoning mainly being that:

We all agree this PR is too big as mentioned above
Styling goes somewhat out of whack when upgrading from MUI 4 -> 5, particularly around the light mode styling of AppBar/Header and, particularly befuddling, the links in sectionTableBody.tsx ⁉

@EricPedley @ap0nia Thoughts?

I know we're a tad far along into this PR, but I'm pretty strongly in favor of some sort of rebase (split?, sorry not sure of terminology) back to commit #3f1c3ca (pre-refactor) and moving the 2 or 3 other scopes (Appbar/Header, Markdown, etc) included within this PR into their own PRs.

Sure let's do that so we can get it merged faster

Not sure why Github-Actions isn't deploying a new staging instance @ap0nia @EricPedley

Me when short PR


cannot mount bucket

Hello, just registered to BackBlaze, create an app-key and a bucket named marioborg. Tried to mount it but fails with the following message:
mario@mario3 ~/dl % b2fuse --config_filename ~/local/etc/b2fuse.yaml ~/mnt/tmp
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/fuse.py", line 495, in _wrapper
return func(*args, **kwargs) or 0
File "/usr/local/lib/python2.7/dist-packages/fuse.py", line 693, in readdir
fip.contents.fh):
File "/usr/local/lib/python2.7/dist-packages/fuse.py", line 800, in call
return getattr(self, op)(*args)
File "/usr/local/lib/python2.7/dist-packages/b2fuse/b2fuse_main.py", line 236, in readdir
self._update_directory_structure()
File "/usr/local/lib/python2.7/dist-packages/b2fuse/b2fuse_main.py", line 131, in update_directory_structure
online_files = [l[0].as_dict() for l in self.bucket_api.ls()]#self.bucket_api.list_file_names()['files']
File "/usr/local/lib/python2.7/dist-packages/logfury/v0_1/trace_call.py", line 84, in wrapper
return function(*wrapee_args, **wrapee_kwargs)
File "/usr/local/lib/python2.7/dist-packages/b2fuse/cached_bucket.py", line 86, in ls
result = [f for f in super(CachedBucket, self).ls()]
File "/usr/local/lib/python2.7/dist-packages/b2/bucket.py", line 230, in ls
response = session.list_file_names(self.id, start_file_name, fetch_count)
File "/usr/local/lib/python2.7/dist-packages/b2/session.py", line 38, in wrapper
return f(api_url, account_auth_token, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/b2/raw_api.py", line 351, in list_file_names
maxFileCount=max_file_count
File "/usr/local/lib/python2.7/dist-packages/b2/raw_api.py", line 139, in _post_json
return self.b2_http.post_json_return_json(url, headers, params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 299, in post_json_return_json
return self.post_content_return_json(url, headers, data, try_count, params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 272, in post_content_return_json
response = _translate_and_retry(do_post, try_count, post_params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 116, in _translate_and_retry
return _translate_errors(fcn, post_params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 52, in _translate_errors
int(error['status']), error['code'], error['message'], post_params
BadJson: Bad request: Invalid bucketId: marioborg

BucketID is the alphanumeric string, you have entered the bucket name.
On Sun, Apr 8, 2018, 18:31 mariocarro<EMAIL_ADDRESS>wrote:

Hello, just registered to BackBlaze, create an app-key and a bucket named
marioborg. Tried to mount it but fails with the following message:
mario@mario3 ~/dl % b2fuse --config_filename ~/local/etc/b2fuse.yaml
~/mnt/tmp
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/fuse.py", line 495, in
_wrapper
return func(*args, **kwargs) or 0
File "/usr/local/lib/python2.7/dist-packages/fuse.py", line 693, in readdir
fip.contents.fh):
File "/usr/local/lib/python2.7/dist-packages/fuse.py", line 800, in call
return getattr(self, op)(*args)
File "/usr/local/lib/python2.7/dist-packages/b2fuse/b2fuse_main.py", line
236, in readdir
self._update_directory_structure()
File "/usr/local/lib/python2.7/dist-packages/b2fuse/b2fuse_main.py", line
131, in
*update_directory_structure online_files = [l[0].as_dict() for l in
self.bucket_api.ls
http://self.bucket_api.ls()]#self.bucket_api.list_file_names()['files']
File "/usr/local/lib/python2.7/dist-packages/logfury/v0_1/trace_call.py",
line 84, in wrapper return function(wrapee_args, **wrapee_kwargs) File
"/usr/local/lib/python2.7/dist-packages/b2fuse/cached_bucket.py", line 86,
in ls result = [f for f in super(CachedBucket, self).ls()] File
"/usr/local/lib/python2.7/dist-packages/b2/bucket.py", line 230, in ls
response = session.list_file_names(self.id http://self.id,
start_file_name, fetch_count)
File "/usr/local/lib/python2.7/dist-packages/b2/session.py", line 38, in
wrapper
return f(api_url, account_auth_token, *args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/b2/raw_api.py", line 351, in
list_file_names
maxFileCount=max_file_count
File "/usr/local/lib/python2.7/dist-packages/b2/raw_api.py", line 139, in
_post_json
return self.b2_http.post_json_return_json(url, headers, params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 299, in
post_json_return_json
return self.post_content_return_json(url, headers, data, try_count, params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 272, in
post_content_return_json
response = _translate_and_retry(do_post, try_count, post_params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 116, in
_translate_and_retry
return _translate_errors(fcn, post_params)
File "/usr/local/lib/python2.7/dist-packages/b2/b2http.py", line 52, in
_translate_errors
int(error['status']), error['code'], error['message'], post_params
BadJson: Bad request: Invalid bucketId: marioborg
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sondree/b2_fuse/issues/66, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLAWea8dmf4S7Dh2xFRtvug7WdOwYxzks5tmjtQgaJpZM4TLmmp
.

Lol, of course! Thanks...


Homebridge 1.3.1 warnings every minute

[23/02/2021, 10:47:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:47:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:48:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:48:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:49:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:49:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:50:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 10:50:06] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
### DEBUG MODE:
[23/02/2021, 13:27:30] [Yeelight] {"method":"set_ct_abx","params":[5524.861878453039,"smooth",400],"id":14}
[23/02/2021, 13:27:30] [Yeelight] { id: 14, result: [ 'ok' ] }
[23/02/2021, 13:27:30] [homebridge-yeelight-wifi] This plugin generated a warning from the characteristic 'Color Temperature': SET handler returned write response value, though the characteristic doesn't support write response. See https://git.io/JtMGR for more info.
[23/02/2021, 13:27:30] [homebridge-yeelight-wifi] Error:
at Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2164:105)
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1645:22
at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:9:18
at Characteristic. (/usr/local/lib/node_modules/homebridge-yeelight-wifi/bulbs/temperature.js:20:15)
at processTicksAndRejections (internal/process/task_queues.js:93:5)

Feel free to dig deeper and fix those! :)

@okonet teach me how to fix

Adaptive lightning is a feature of homebridge which sets CT on devices automatically every minute. You can't control it, so I think the issue isn't really in it but in the way the set request is handled in this library. I have no idea myself how to fix it.

@okonet Its an homebridge issues?

No, I don’t think. They started to issue warning with the v1.3 that’s why it started to be visible.

This is probably caused by passing a second argument to the callback when setting characteristics, I'll open a PR if someone can test, as I don't have access to the the bulbs at the moment.
https://github.com/vieira/homebridge-yeelight-wifi/blob/67ff4b470f0d34bb87a01fb41d230fe695dc568d/bulbs/temperature.js#L18-L25

Ah that would make sense! Thanks for pointing out.

This is probably caused by passing a second argument to the callback when setting characteristics, I'll open a PR if someone can test, as I don't have access to the the bulbs at the moment.
https://github.com/vieira/homebridge-yeelight-wifi/blob/67ff4b470f0d34bb87a01fb41d230fe695dc568d/bulbs/temperature.js#L18-L25

@vieira can you tag it? I will test

I have sent a request for review to @okonet, as he is maintaining this now I will let him handle it as any other PR.


Timex.to_datetime/2 fails for Date on DST boundaries in certain timezones

Steps to reproduce
iex(73)> Timex.to_datetime(~D[2019-11-02], "America/Sao_Paulo")
#DateTime<2019-11-02 00:00:00-03:00 -03 America/Sao_Paulo>
iex(74)> Timex.to_datetime(~D[2019-11-03], "America/Sao_Paulo")
{:error, {:could_not_resolve_timezone, "America/Sao_Paulo",<PHONE_NUMBER>0, :wall}}

Description of issue
This happens in timezones that "leap forward" at midnight.

What are the expected results?

I would expect a DateTime object that correctly handles the DST transition, i.e.
iex(75)> Timex.to_datetime(~D[2019-11-03], "America/Sao_Paulo")
#DateTime<2019-11-03 01:00:00-02:00 -02 America/Sao_Paulo>

Luxon handles this correctly:
> DateTime.fromObject({year: 2019,month: 11, day: 02, zone: 'America/Sao_Paulo'}).toISO()
'2019-11-02T00:00:00.000-03:00'
> DateTime.fromObject({year: 2019,month: 11, day: 03, zone: 'America/Sao_Paulo'}).toISO()
'2019-11-03T01:00:00.000-02:00'

You may be running into my issue created last year #491

I just saw:
{:error,
 {:could_not_resolve_timezone, "America/Los_Angeles",<PHONE_NUMBER>7, :wall}}

I also saw a few hundred of these errors on Saturday.

I'm getting this error with "2019-03-09T20:47:42.585791-06:00" |> Timex.parse!("{ISO:Extended}") |> Timex.Timezone.convert("America/Chicago")

this should not closed


Carousel in Chrome shows vertical scroll

I open this page:
https://blog.getbootstrap.com/
And see following result:

Looks like a bug. Sorry, if I have broken some rules of contribution. I presume Blog uses latest BS version and doesn't plan to show vertical scroll.
OSX 10.11.6 (15G1212)
Chrome Version 56.0.2924.51 beta (64-bit)

I think you'll find that the scrollbar is caused by that example being a embedded JSBin, rather than an issue with the carousel itself.

Closing because this is on the blog and not this repo.


Adjustments for java version on project - remain at java 8 for current stream release (bug fixes)

coverage: 87.183%. remained the same
when pulling 3e1fa8369f2c3dfa976e03dc839494e84498024b on hazendaz:master
into 6428f0953b6c1c44f93a12e9518abe9219dde126 on mybatis:master.


Running from non-project-root fails to resolve tsconfig "paths"

Acknowledgements

[X] I searched existing issues before opening this one to avoid duplicates
[X] I understand this is not a place for seek help, but to report a bug
[X] I understand that the bug must be proven first with a minimal reproduction
[X] I will be polite, respectful, and considerate of people's time and effort

Minimal reproduction URL
https://stackblitz.com/edit/node-hpyz3n
Version
4.7.0
Node.js version
18.18.2
Package manager
yarn
Operating system
Windows
Problem & Expected behavior
What happened?
I added a custom path into tsconfig.json: "paths": {"@/*": ["./*"]}. Then if I run tsx index.ts in a project directory, all ok. If I run it from other directory, e.g. in the linked stackblitz:
cd ..
node-hpyz3n/node_modules/.bin/tsx node-hpyz3n/index.ts

then tsx cannot resolve modules referred to by "@/", e.g. import<EMAIL_ADDRESS>This prevents using tsx as a loader for cli tools of projects that use tsconfig paths, as in:
// cli.ts
#!/usr/bin/env tsx
import<EMAIL_ADDRESS>...

// package.json
{
  "bin": {"my-tool":"cli.ts"},
  ...
}

// shell
$ cd my-project
$ yarn link
$ cd /some/other/path
$ my-tool

This behavior doesn't seem to depend on path template names (@, @src, without @, etc).
What did you expect instead?
For tsx to resolve tsconfig paths based on a resolved project root, e.g. tsconfig.json/compilerOptions/{rootDir,baseUrl}. Or maybe based on tsconfig.json's location.
So, basically, if regular imports work relative to the importing source file, tsconfig-paths imports, being baseUrl-relative in normal circumstances, should work relative to where tsconfig.json thinks the root is. I believe there's no reason to resolve modules outside of a project root.
Do you have an error stack trace?
Error: Cannot find module<EMAIL_ADDRESS>Require stack:
- /home/projects/node-hpyz3n/index.ts
    at Module._resolveFilename (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:54:12642)
    at d.default._resolveFilename (file:///home/projects/node-hpyz3n/node_modules/.pnpm/@esbuild-kit+cjs-loader@2.4.0/node_modules/@esbuild-kit/cjs-loader/dist/index.js:1:1529)
    at Module._load (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:54:10056)
    at Module.require (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:54:13775)
    at i (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:98:2198)
    at _0x16f7fc (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:352:194520)
    at eval (file:///home/projects/node-hpyz3n/index.ts:2:132)
    at Object.eval (file:///home/projects/node-hpyz3n/index.ts:3:3)
    at Object.function (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:352:195362)
    at Module._compile (https://nodehpyz3n-b5hh.w-credentialless.staticblitz.com/blitz.6f234770.js:54:14871) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/home/projects/node-hpyz3n/index.ts' ]
}

Do you have documentation links? Do you have screenshots?
Nope.
Contributions

[ ] I plan to open a pull request for this issue
[ ] I plan to make a financial contribution to this project

I think this is because the current working directory that get-tsconfig uses is the path you're running in, this causes it to get tsconfig from 'uplevel' of the package root that you are running it in, and it does not use the tsconfig in your tsx-enabled library

Please fix your reproduction to:

Remove unnecessary code
Remove extraneous steps; specifically in your case, move the TS project to a nested dir so you don't need to ask others to run a more complex command.

Done. A nested dir doesn't work with stackblitz due to path issues, but I modified .stackblitzrc so it takes the described steps and reproduces the issue immediately.

https://github.com/privatenumber/tsx#custom-tsconfigjson-path

By default, tsconfig.json will be detected from the current working directory.

this is not practical, at least resolve it relative to the entry. e.g tsx index.ts, resolve tsconfig.json relative to index.ts.
About not practical:
use tsx in shebang: #/usr/bin/env tsx and link module to global, and use cli in any cwd.
with current behavior(resolve tsconfig in cwd), a hard-coded tsconfig absolute path is needed.
file bin.ts
#!/usr/bin/env tsx --tsconfig /absolute/path/of/tsconfig.json

ts-node's behavior

When searching, it is resolved using the same search behavior as tsc. By default, this search is performed relative to the entrypoint script. In --cwdMode or if no entrypoint is specified -- for example when using the REPL -- the search is performed relative to --cwd / process.cwd().

Workaround seems to be setting the TSX_TSCONFIG_PATH env manually before running tsx e.g.
export TSX_TSCONFIG_PATH=./tsconfig.json && tsx index.ts


Feature :: percentage step to mongo

This step computes the percentage of total, i.e. for every row the value is divided
by the total as the sum of every values in a column. The computation can be performed
by group if specified. The result can be either output inplace or in a new column if specified
Closes https://github.com/ToucanToco/vue-query-builder/issues/68

Codecov Report

Merging #96 into master will increase coverage by 0.64%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #96      +/-   ##
==========================================
+ Coverage   84.34%   84.98%   +0.64%
==========================================
  Files          11       11
  Lines         281      293      +12
  Branches       31       33       +2
==========================================
+ Hits          237      249      +12
  Misses         38       38
  Partials        6        6

Impacted Files
Coverage Δ

src/lib/translators/base.ts
97.77% <100%> (+0.05%)
:arrow_up:

src/lib/translators/mongo.ts
98.9% <100%> (+0.15%)
:arrow_up:

Continue to review full report at Codecov.

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


feat(fabric-driver): added weaver fabric driver as cacti package

Pull Request Requirements

[ ] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[ ] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[ ] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[ ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[ ] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

@sandeepnRES Can you edit the opening comment and add some description (in bullet points) about what this feature is and how it is part of the Cacti integration roadmap?

Added package LGTM. Please add some descriptions as per my comments before merging though.

Added package LGTM. Please add some descriptions as per my comments before merging though.

@sandeepnRES Big +1 on that. However trivial/straightforward it seems to us, it is always good to explain for future contributors/maintainers what the change is in a little more detail with some historical context, etc.

@sandeepnRES CI is failing, could you investigate? I think the package name is duplicated in both places and that's causing the scripts to fail

@sandeepnRES Do you need any help investigating this one?

Hi @petermetz What do you think will be better, to rename this package. Or to remove the one inside weaver directory from packages declared in root package.json

Hi @petermetz @VRamakrishna @outSH
Sorry for such a long delay, I've now renamed the package to cacti-plugin-weaver-driver-fabric
Haven't called it ledger connector yet, just to differentiate the original ledger connector and driver, once we combine both, then probably we can use that name.

@sandeepnRES OK, works for me. Please run yarn install to update the lock file.
> configure
> npm run init-registries && yarn install && yarn build:dev:backend

> init-registries
> npm config set @iroha2:registry=https://nexus.iroha.tech/repository/npm-group/

➤ YN0000: Yarn detected that the current workflow is executed from a public pull request. For safety the hardened mode has been enabled.
➤ YN0000: It will prevent malicious lockfile manipulations, in exchange for a slower install time. You can opt-out if necessary; check our documentation for more details.

➤ YN0000: · Yarn 4.1.0
➤ YN0000: ┌ Resolution step
Resolution step
➤ YN0000: └ Completed in 23s 737ms
➤ YN0000: ┌ Post-resolution validation
Post-resolution validation
➤ YN0028: +"@hyperledger/cacti-plugin-weaver-driver-fabric@workspace:packages/cacti-plugin-weaver-driver-fabric":
➤ YN0028: +  version: 0.0.0-use.local
➤ YN0028: +  resolution: "@hyperledger/cacti-plugin-weaver-driver-fabric@workspace:packages/cacti-plugin-weaver-driver-fabric"
➤ YN0028: +  languageName: unknown
➤ YN0028: +  linkType: soft
➤ YN0028: +
➤ YN0028: The lockfile would have been modified by this install, which is explicitly forbidden.
➤ YN0000: └ Completed in 0s 243ms
➤ YN0000: · Failed with errors in 24s 2ms
Error: Process completed with exit code 1.


Drawing multiple edges between two nodes with neo4jd3

Drawing multiple edges between two nodes with neo4jd3,thanks!

@heboliufengjie  do you have any solution?

@heboliufengjie  @MelvinZang  #39


Remove record_type

Remove record_type column since not (anymore) part of table schema in AWS Glue.

@tjbanghart found one more thing

@tjbanghart updated with some more details


haproxy static pod cannot reference a pull secret

Static pods are not allowed to reference secrets.
The present behavior is that the kubelet is able to fetch the static pod image using the pull secret we lay down on the host in /var/lib/kubelet/config.json.
By referencing a secret, we launch the haproxy pod on the host, but the kubelet is rejected from mirroring the pod back to the API server.
"Failed creating a mirror pod for ... is forbidden: a mirror pod may not reference secrets"

/test e2e-aws

/lgtm

/approve


Add automations based on Solar Elevation

This adds a solar elevation attribute to the sun component.
It also adds a config attribute to the numeric state trigger so that you can specify the name of an attribute trigger than just a state.
Ideally we'd update the sun card to display the elevation too, which will make it easier to set up an automation. This is beyond my expertise!
This PR allows automations that are based on sunrise/sunset - but where the offsets are degrees rather than hours. The problem with time offsets is that for things like lights they don't adjust well across the seasons.
Intended to fix #640
My sense is this is harder to set-up than a time based sunrise/sunset automation (the sun angle isn't intuitive), however once setup it should work better across the seasons.
Perhaps helpful for the documentation to say that dusk is between 0 and -6.
Replacement for https://github.com/balloob/home-assistant/pull/674

Can you add some tests for the attribute support for numeric_value automation platform?

@balloob Added some tests - happy to add more / remove / restructure if needed.
The pylint errors are hopefully unrelated!

Bueno! Ignore the CI failures. PyLint got an upgrade and messed some things up.


[Refactor] refactor ddl executor createFunction & dropFunction

Signed-off-by: zombee0<EMAIL_ADDRESS>What type of PR is this：

[ ] refactor

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

refactor ddl executor createFunction & dropFunction to make GlobalStateMgr simple

[FE PR Coverage check]
:disappointed: fail : 0 / 26 (00.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/execution/CreateFunctionExecutor.java
0
12
00.00%

:large_blue_circle:
com/starrocks/persist/EditLog.java
0
2
00.00%

:large_blue_circle:
com/starrocks/execution/DropFunctionExecutor.java
0
12
00.00%

run starrocks_fe_unittest

[FE PR Coverage check]
:disappointed: fail : 0 / 22 (00.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/execution/CreateFunctionExecutor.java
0
6
00.00%

:large_blue_circle:
com/starrocks/persist/EditLog.java
0
10
00.00%

:large_blue_circle:
com/starrocks/execution/DropFunctionExecutor.java
0
6
00.00%

[FE PR Coverage check]
:disappointed: fail : 0 / 26 (00.00%)
file detail

path
covered line
new line
coverage

:large_blue_circle:
com/starrocks/catalog/Database.java
0
12
00.00%

:large_blue_circle:
com/starrocks/execution/CreateFunctionExecutor.java
0
6
00.00%

:large_blue_circle:
com/starrocks/persist/EditLog.java
0
2
00.00%

:large_blue_circle:
com/starrocks/execution/DropFunctionExecutor.java
0
6
00.00%


Node 20 - Breaking Change?

Hi,
we noticed our builds failing (using setup-sam@v2)  this morning because we have no support yet for Node 20 on our self-hosted runners. Our current workaround is to target a specific commit hash right before the upgrade to Node 20.

Perhaps you should consider releasing this change as a V3?
Thanks,
Maarten

This has broken our builds for self-hosted runners as well.

@jkruse14 I am talking with the team now. I don't understand why this affected self hosted runners but we were using a very old version of Node. So my advice is either update to Node20 or lock to a hash, at the moment. I know this isn't the best answer but we need to weigh what is best to do.

Chatted with the team. We are going to leave this at v2 and not revert/release a v3.
Thought process:
This impacts Self Hosted runners that do not install Node20. Github hosted runners have Node20 installed. If we were to revert, we would be back to using a Node version (16) which is not longer supported as of Sept 2023. In addition, pushing a v3 would require everyone to upgrade instead of only customers locked to an unsupported Node Version.
If you are impacted, your path forward is to install Node20 onto the system or lock the github action to 8aee2f4a7fe48544e1468ff08d28b88b99021291 by updating aws-actions/setup-sam@v2 to aws-actions/setup-sam@8aee2f4a7fe48544e1468ff08d28b88b99021291. We understand this isn't ideal for impacted customers but believe this is the best path to take.

@jfuss - Thank you for the information and the steps to move forward. While I understand the reasoning behind the decision to leave this commit in the v2 tag, I would like to say that this is not good, nor standard, practice. This is a breaking change, in such a case the best practice would be to bump the version. Previous releases of software should only change patching purposes, not for breaking changes.


Handling international (Swedish) characters

Lists with mixed lower/upper case Swedish characters don't work properly.
Gist example including explanation of the problem: https://gist.github.com/1453745

Ouch, thanks for the heads up. I will look in to the problem as soon as possible!

I'm closing all unicode errors with a reference to #385 :wave:


Package URl
<EMAIL_ADDRESS>CPE
cpe:2.3:a:cecil:cecil:<IP_ADDRESS>:::::::*
CVE
CVE-2023-4914
ODC Integration
None
ODC Version
8.4.3
Description
Vulnerability in https://github.com/Cecilapp/Cecil/commit/00dc79f10ce723034b7140d79f4ac731d1d902eb is reported for package "Mono.Cecil.".
Source :https://github.com/jbevain/cecil

It should refer the package from the source repository but instead of that it is referring from https://github.com/cecilapp/cecil Hence showing the "Mono.Cecil." package as vulnerable.

Duplicate of #6257


User can create an entry.

💰 Motivation
Coders will want to capture tidbits they pick up during their research.
📐 Plan
Create a responsive form that allows users to store an image URL with some notes about a specific topic.
🖼 Wireframes

✅ Task List

[x] Add a div[data-view="entry-form"] to the HTML.
[x] Add a form for creating a journal entry to the div[data-view="entry-form"].
[x] Ensure that the form looks nice on both mobile-sized and desktop-sized screens.
[x] Make all inputs of the journal entry form required.
[x] Listen for 'input' events on the photoUrl input to update the src attribute of the photo preview when the input value changes.
[x] Listen for 'submit' events on the journal entry form and:

[x] Put the form's input values into a new object.
[x] Add the nextEntryId to the object.
[x] Increment the nextEntryId on the data model.
[x] Prepend the new object to the entries in the data model.
[x] Reset the image preview's `src' attribute.
[x] Reset the form inputs.

[x] Verify that new entries are saved to local storage along with the rest of the data model on page reload.
[x] Verify that each new entry receives an incrementing entryId.
[x] Remove all CSS styling that had no affect or was otherwise unnecessary.
[x] Test all functionality again in a private browsing session.
[x] Fix all errors.


fix serde_bytes derive

Restrict #[serde(with = "serde_bytes"] to be only used for Vec<u8> and &[u8] in struct field.

Actually this is fine, Rust type checker is able to detect this error. We don't need to catch this from the Rust AST in proc macro.


[KYUUBI #4609] get engineRefId in KyuubiConnection

Why are the changes needed?

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

@turboFei

- backend service metric test *** FAILED ***
  8 did not equal 7 (BackendServiceMetricSuite.scala:81)

Codecov Report

Merging #4610 (c40fd71) into master (8a526ce) will increase coverage by 0.01%.
The diff coverage is 50.00%.

@@             Coverage Diff              @@
##             master    #4610      +/-   ##
============================================
+ Coverage     53.32%   53.33%   +0.01%
  Complexity       13       13
============================================
  Files           577      577
  Lines         31584    31591       +7
  Branches       4248     4249       +1
============================================
+ Hits          16843    16850       +7
- Misses        13151    13156       +5
+ Partials       1590     1585       -5

Impacted Files
Coverage Δ

.../org/apache/kyuubi/jdbc/hive/KyuubiConnection.java
5.64% <0.00%> (-0.04%)
:arrow_down:

...ain/scala/org/apache/kyuubi/engine/EngineRef.scala
70.76% <100.00%> (+0.22%)
:arrow_up:

.../kyuubi/operation/KyuubiApplicationOperation.scala
43.47% <100.00%> (+2.56%)
:arrow_up:

...ala/org/apache/kyuubi/operation/LaunchEngine.scala
89.65% <100.00%> (+0.36%)
:arrow_up:

... and 6 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

thanks, merging to master


Reference VS Code (and Studio?) for DVC plots

Report
Some places where it would be helpful to mention VS Code (and maybe Studio):
https://dvc.org/doc/command-reference/plots
This might seem odd in a CLI ref, but right now it states:

DVC generates plots as static HTML webpages that can be open with a web browser. They can also be saved as SVG or PNG image files from the browser.

Since VS Code provides a better experience, why not mention it?
https://dvc.org/doc/start/experiments/visualization
@jorgeorpinel @shcheklein Thoughts?

Agree to both (VS Code and Studio).
Probably in https://dvc.org/doc/start/experiments/visualization first and foremost.

might seem odd in a CLI ref

It's OK to add to the CLI ref too, since most of the plots info is there still (will get extracted eventually)

Or maybe in the parent (https://dvc.org/doc/start/experiments) even.

Started #3735 for the VS Code links.
The pending question is: do we add Studio links in all (or most) places where VS Code is linked from? Or just the plots-related ones for now (i.e. in the same PR) ?

Wait this looks mostly like a dupe of https://github.com/iterative/dvc.org/issues/3717.


Is it possible to use react-virtual in flexbox?

Describe the bug
When parentElement (return of getScrollElement) is in flexbox it expands parent element. Maybe this is intended behavior if it is I think that it should be stated in the docs.
Your minimal, reproducible example
https://codesandbox.io/p/sandbox/hopeful-silence-pggrx2?embed=1&file=%2Fsrc%2Fmain.tsx%3A6%2C19
Steps to reproduce
Open the sandbox, the parent element with id "parent-ref" is overflowing its parent element.
Expected behavior
The parent element with id "parent-ref" should fill only available space, it should not expand its parent.
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform

[Linux, Firefox, Chrome etc] I do not think that this issue is platform dependent.

tanstack-virtual version
3.0.0-beta.61
TypeScript version
No response
Additional context
No response
Terms & Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

@skopz356 yes it is, you need to set min-width: 0 o flex item, checkout https://stackoverflow.com/questions/36247140/why-dont-flex-items-shrink-past-content-size/36247448#36247448

Hey @piecyk, does this package support flex-wrap too?


Remove node and yarn requirements for building from source

Fixes #2202

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5ce573535e04b3fc01fff1a5d262a3be938a4cbd/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ada500c271bd5ba0c6e70d4c0ea84e1a65348636/


Invalid value 52 for parameter page parameter is invalid.

Hi I have sample code:
    with open('temp_users.json', 'w') as f:
        all_data = []
        print "Searching users",
        for user in tweepy.Cursor(api.search_users,q = "ziemniaki").items():
            print ".",
            sys.stdout.flush()
            all_data.append(user._json)
        f.write(json.dumps(all_data))
        f.close()
    print ""
    return

And I got this error:
raise TweepError(error_msg, resp)
tweepy.error.TweepError: [{u'message': u'Invalid value 52 for parameter page parameter is invalid.', u'code': 44}]

And second uncaught exception:
    raise TweepError(error_msg, resp)
tweepy.error.TweepError: [{u'message': u'Rate limit exceeded', u'code': 88}]

Same problem here, has anyone been able to fix it?

I have same problem. I use as doc - http://docs.tweepy.org/en/v3.2.0/api.html#API.search
results = twitterApi.search(
            q = request.args.get("q"),
            rpp = 50,
            page = 2
        )

It seems the page parameter is not supported. Suggestion: remove 'page' from the docs

I answered this in the stackoverflow. Basically, you can use count param.

Twitter gives you only the first 1000 results for a search. 20 results per page * 50 pages = 1000 results. Hence the next hit with the page number 52 onward gives error (not sure why page 51 works, may be to compensate for one or two results filtered in the previous searches).
Refer: https://developer.twitter.com/en/docs/accounts-and-users/follow-search-get-users/api-reference/get-users-search

@vinog-git is correct.
The issue is that the users/search endpoint returns an error when attempting to paginate past 1000 results, instead of returning a list of 0 items, as PageIterator expects to raise StopIteration:
https://github.com/tweepy/tweepy/blob/51f680c27af5bc55cde2688cb0ef7b5e0b05c38f/tweepy/cursor.py#L156-L171
@j0g1 Your second exception is simply caused by exceeding the rate limit, as the error says.
See the wait_on_rate_limit parameter for API for a way to handle this.
@serkandaglioglu That is not relevant to this issue, as you're using API.search, (rather than API.search_users) which uses the standard search API and does not have a page parameter.
For updating the documentation for API.search, see #1199. CC: @qxx
@tdatu The count parameter simply specifies the limit for results to return per page.
It does not affect this issue; e.g. count=10 will result in the error Invalid value 102 for parameter page parameter is invalid. when attempting to iterate past the 1000th result.
In fact, since the default and maximum for count is 20, count=100 as in your Stack Overflow answer, does nothing. See the documentation for the users/search endpoint.

It's because searching for users is limited to return 1000 results through the basic Twitter API:
https://developer.twitter.com/en/docs/accounts-and-users/follow-search-get-users/api-reference/get-users-search
So you can put in .pages(51) and then it won't throw an error. If you want to run it again, however, it's just going to give the same 1000 results as before so you'll need to change the query to give different results.


feat: introduce build workflow

Signed-off-by: Phil Adams<EMAIL_ADDRESS>

:tada: This PR is included in version 3.17.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


ability to xinclude in testng files

Hi Guys,
This is related to defect  95 with this description:
Add ability to include XML files (XInclude)
I know this defect was closed because of the ability to use suite-files but that is only allowed at the suite level.  It doesn't allow for lots of flexibility say having the ability to split out a ton of common parameters and classes used across several  cases into another xml file.  Can the solution proposed in that defect (which makes the xml parser xinclude aware) be used?  Thanks a bunch!

Almost all of the capabilities with respect to altering suite can be achieved via the TestNG listener org.testng.IAlterSuiteListener


Map not initialized

<EMAIL_ADDRESS>In this file, approximately 549 lines indicate that the causalConsistencyCache variable has not been initialized and cannot be assigned a value

No initialization operation was found in the entire project

when will this bug be fixed?


POST request executing with statuscode = 200 but going to onFailure.

I am posting a request to my server and its returning with statusCode = 200 but its going to onFailure.
I tested my code using "https://httpbin.org/post" and its working fine.
But when I request to my server it returns with this exception
org.json.JSONException: Response cannot be parsed as JSON data
                                   at com.loopj.android.http.JsonHttpResponseHandler$1$1.run(JsonHttpResponseHandler.java:158)
                                   at android.os.Handler.handleCallback(Handler.java:739)
                                   at android.os.Handler.dispatchMessage(Handler.java:95)
                                   at android.os.Looper.loop(Looper.java:148)
                                   at android.app.ActivityThread.main(ActivityThread.java:5417)
                                   at java.lang.reflect.Method.invoke(Native Method)
                                   at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
                                   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

hello bro, any solution for this case?
im have same problem

Are you free free post your server address ?


Error: error reading llm response: bufio.Scanner: token too long

I'm passing in about 62 articles that I wrote from the web and trying to get some analysis on them, and I keep seeing this error:

Error: error reading llm response: bufio.Scanner: token too long

Some text response comes back and then after a couple sentences it throws that error.
Is there a better way to do this or is my machine just not capable? Running a M1 Macbook air.
function generate_output() {
  echo -e "Below is a series of articles that I wrote\n"
  echo -e "\nEach article is prefixed with the string 'Here's another article:'\n"
  echo -e "\nStarting Articles\n"

  files=(*.txt)
  count=${#files[@]}
  i=0

  for file in "${files[@]}"; do
    cat "$file"
    ((i++))
    if [ $i -lt $count ]; then
      echo -e "\nHere's another article:\n"
    fi
  done

  echo -e "\nEnd of Articles\n"
  echo -e "\nCan you interpret some common themes from this series of articles?\n"
  # echo -e "\nWhat is the core theme from these articles?\n"
  # echo -e "\nWrite a bio for this author.\n"
}

ollama run mistral "$(generate_output)"
# ollama run codellama "$(generate_output)"

Thanks for reporting this. I've opened #692 to get the error fixed.
As a side note, the context window for the LLM wont be able to fit a lot of long articles, they will be automatically truncated. A better approach to this would be breaking this down into individual requests, then sending a final request that asks the LLM to create a summary based on those shorter outputs.

@BruceMacD thanks for the feedback, just to confirm I should do this via curl and not piping / arguments via shell script? memory is able to persist across curl requests?

You could still use piping. I'd just suggest breaking up the piped requests into smaller prompts so that the model doesn't lose some context.

@BruceMacD from expierence new lines \n are split and each line is sent as a prompt I had no way of providing blocks of text with new lines as a single prompt via piping.


PR review speed

Category

[ ] Bug
[ ] Feature Request
[x] Question

Brief Intro
Idea about solving the speed of reviewing PR
More Details
It seems that currently reviewing PR speed is kind of slow. Want to create this issue to get some feedback about the speed of reviewing PR.

Here are some ideas how to solve it.

Add more reviewers
Get a plan for each week or each month. How many PRs need to be reviewed. We can rank the importance of PRs. Like fatal bug, new features, small issues, PR waiting time etc. Based on the rank to clean up PRs in the queue.

@kelvinlauKL @rwenderlich @vincentngo

@remlostime Thanks for bringing this up, you've brought up good points.
As the repo gets more popular, we'll be adding more reviewers. Traffic certainly has picked up lately. We generally plan for a couple of PRs per week per reviewer, but the Swift 4 migration created a backlog of things for us to take a look at.
I do acknowledge the need for a more speedy resolution to resolve the bucket of PRs though. Thanks again for the feedback, it's appreciated.

@kelvinlauKL Thanks for the reply. That helps.


Evaluate the predictions.pkl provided on CAFA3 with CAFA_assessment_tool

I left lines 152-162 of the code in evaluate_deepgoplus.py uncommented and added the following export file command. The DeepGOPlus_1_all.txt file was generated using the provided predictions.pkl file from CAFA3. Afterwards it was evaluated using the official evaluation tool and the results obtained were not the same as in the paper. I assume I can't export the txt file directly, so where do I need to modify to and get the same results as in the paper?
  print("exporting predictions to CAFA submission format")
  txt_out=[]

  txt_out.append('AUTHOR None\n')
  txt_out.append('MODEL 1\n')
  txt_out.append('KEYWORDS natural language processing.\n')
  for i, row in enumerate(test_df.itertuples()):
      prot_id = row.proteins
      for go_id, score in deep_preds[i].items():
          #print(f'{prot_id}\t{go_id}\t{score:.2f}')
          score_str = "{0:.2f}".format(score)
          if(score_str!="0.00"):
              txt_out.append(str(prot_id)+"\t"+str(go_id)+"\t"+score_str+"\n")
  txt_out.append('END')
  with open(filename, 'w') as f:
      f.writelines(txt_out)

Hi,
You need to use this tool to get the same results as in the paper for CAFA3 evaluation https://github.com/ashleyzhou972/CAFA_assessment_tool
If I remember correctly this file should have the txt files deepgoplus-cafa.tar.gz

I think I have used evaluate_cafa3.py script to generate them.

Thank you for taking the time to reply to me, I will try it again. The previous try didn't turn out right, as I said the first time I asked you

Hello, Dr. Kulmanov，
I am back, I have tested several times. The above is tested with the txt file generated by data-cafa3/predictions.pkl, the bottom is tested with the txt provided directly by you.
%Results of the txt file generated using the predictions.pkl file you provided
%Results of the txt file generated using the predictions.pkl file you provided
Ontology	Type	Mode	 | Fmax	Threshold	Coverage
bpo	NK	partial	 | 0.3864840946855839	0.18	1.0
bpo	NK	full	 | 0.3864840946855839	0.18	1.0
bpo	LK	partial	 | 0.4072675565869404	0.17	1.0
bpo	LK	full	 | 0.4072675565869404	0.17	1.0
cco	NK	partial	 | 0.6106824202178297	0.25	1.0
cco	NK	full	 | 0.6106824202178297	0.25	1.0
cco	LK	partial	 | 0.6000260772486744	0.22	1.0
cco	LK	full	 | 0.6000260772486744	0.22	1.0
mfo	NK	partial	 | 0.5549217805948832	0.12	1.0
mfo	NK	full	 | 0.5549217805948832	0.12	1.0
mfo	LK	partial	 | 0.5376631411272229	0.11	1.0
mfo	LK	full	 | 0.5376631411272229	0.11	1.0

%Results on CAFA_assessment_tool using the txt file you provided
Species:all
Ontology	Type	Mode	 | Fmax	Threshold	Coverage
bpo	NK	partial	 | 0.3899217629352804	0.18	1.0
bpo	NK	full	 | 0.3899217629352804	0.18	1.0
bpo	LK	partial	 | 0.4098261625978569	0.14	1.0
bpo	LK	full	 | 0.4098261625978569	0.14	1.0
cco	NK	partial	 | 0.6126849280111355	0.25	1.0
cco	NK	full	 | 0.6126849280111355	0.25	1.0
cco	LK	partial	 | 0.5963076619060491	0.23	1.0
cco	LK	full	 | 0.5963076619060491	0.23	1.0
mfo	NK	partial	 | 0.5561658907106347	0.12	1.0
mfo	NK	full	 | 0.5561658907106347	0.12	1.0
mfo	LK	partial	 | 0.5217672872688168	0.11	1.0
mfo	LK	full	 | 0.5217672872688168	0.11	1.0

The thresholds on NK are the same for both, but the values of Fmax are somewhat different. Why is it so different? This question has been bothering me for weeks, or maybe you can illuminate my mind.

Hi, I need to rerun everything and check before I can give an answer for this. One possible reason might be the ontology version, or if you re-train the model you might get some other results. We've been updating the model several times, maybe we changed something there, I'm not really sure. But, I think the results are not significantly different and are almost the same as in the paper. Checkout our latest model called DeepGOZero

Thank you very much for your reply, the version of the ontology I used is go_cafa3.obo. I just took DeepGOPlus's predictions.pkl on cafa and verified it without retraining the model.I look forward to hearing from you again after you check. I will read your latest paper carefully and I believe it will give me a lot of ideas.
Thanks again.

I think I have used evaluate_cafa3.py script to generate them. Uncomment lines 124-132

when I used evaluate_cafa3.py, one of input files is predictions.pkl, how to generate this file? I want to evaluate our annotation results

furthermore, since the related functions have been developed, whether the evaluate_cafa3 can be added into your website?

hello simon，You can refer to https://github.com/bio-ontology-research-group/deepgoplus/blob/master/deepgoplus.py to generate predictions.pkl. line 186

Thank you. I will try it.
At 2023-04-10 11:34:45, "pencorn" @.***> wrote:
hello simon，You can refer to https://github.com/bio-ontology-research-group/deepgoplus/blob/master/deepgoplus.py to generate predictions.pkl. line 186
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Hello, Dr. Kulmanov， I am back, I have tested several times. The above is tested with the txt file generated by data-cafa3/predictions.pkl, the bottom is tested with the txt provided directly by you. %Results of the txt file generated using the predictions.pkl file you provided
%Results of the txt file generated using the predictions.pkl file you provided
Ontology	Type	Mode	 | Fmax	Threshold	Coverage
bpo	NK	partial	 | 0.3864840946855839	0.18	1.0
bpo	NK	full	 | 0.3864840946855839	0.18	1.0
bpo	LK	partial	 | 0.4072675565869404	0.17	1.0
bpo	LK	full	 | 0.4072675565869404	0.17	1.0
cco	NK	partial	 | 0.6106824202178297	0.25	1.0
cco	NK	full	 | 0.6106824202178297	0.25	1.0
cco	LK	partial	 | 0.6000260772486744	0.22	1.0
cco	LK	full	 | 0.6000260772486744	0.22	1.0
mfo	NK	partial	 | 0.5549217805948832	0.12	1.0
mfo	NK	full	 | 0.5549217805948832	0.12	1.0
mfo	LK	partial	 | 0.5376631411272229	0.11	1.0
mfo	LK	full	 | 0.5376631411272229	0.11	1.0

%Results on CAFA_assessment_tool using the txt file you provided
Species:all
Ontology	Type	Mode	 | Fmax	Threshold	Coverage
bpo	NK	partial	 | 0.3899217629352804	0.18	1.0
bpo	NK	full	 | 0.3899217629352804	0.18	1.0
bpo	LK	partial	 | 0.4098261625978569	0.14	1.0
bpo	LK	full	 | 0.4098261625978569	0.14	1.0
cco	NK	partial	 | 0.6126849280111355	0.25	1.0
cco	NK	full	 | 0.6126849280111355	0.25	1.0
cco	LK	partial	 | 0.5963076619060491	0.23	1.0
cco	LK	full	 | 0.5963076619060491	0.23	1.0
mfo	NK	partial	 | 0.5561658907106347	0.12	1.0
mfo	NK	full	 | 0.5561658907106347	0.12	1.0
mfo	LK	partial	 | 0.5217672872688168	0.11	1.0
mfo	LK	full	 | 0.5217672872688168	0.11	1.0

The thresholds on NK are the same for both, but the values of Fmax are somewhat different. Why is it so different? This question has been bothering me for weeks, or maybe you can illuminate my mind.

How can I get the txt files from the prediction.pkl file ,I uncommented the 124-132 ,but there's no file generated ,I changed lines 124-132 to
print("exporting predictions to CAFA submission format")
txt_out=[]
txt_out.append('AUTHOR None\n')
txt_out.append('MODEL 1\n')
txt_out.append('KEYWORDS natural language processing.\n')
for i, row in enumerate(test_df.itertuples()):
prot_id = row.proteins
for go_id, score in deep_preds[i].items():
#print(f'{prot_id}\t{go_id}\t{score:.2f}')
score_str = "{0:.2f}".format(score)
if(score_str!="0.00"):
txt_out.append(str(prot_id)+"\t"+str(go_id)+"\t"+score_str+"\n")
txt_out.append('END')
with open(filename, 'w') as f:
f.writelines(txt_out).
But the files generated each time are the same ， how can I get the four files(mf bp cc and the all.txt files).Can you give me some guidance

Hello,
evaluate_cafa3.py script has a parameter for sub ontology selection '--ont', you need to run it three times with 'mf', 'bp' and 'cc' parameters. To get 'all' file just concatenate the three files.


Migrate API v2 endpoints

Following endpoints are available on api.balancer.fi which need to be migrated:

[x] Pools list fetching - /pools/

Used by Frontend - pools table

[x] Single pool fetching - /pools//poolId

Used by frontend - single pool page

[ ] SOR - /sor

Used by Cowswap
Moving to beets API once SORv2 is implemented there

[ ] Order - /order

Maybe Used by Cowswap? (unsure if they ever switched to it)
Could move to beets API eventually after SOR

[ ] Tokens - /tokens

Not used by any services

[ ] /check-wallet

Used by the frontend to check if wallet is flagged by TRM

[ ] /tenderly

Was used by SDK, No longer used

[ ] /hal

Picks up new pool creations on Ethereum/Polygon/Arbitrum/Gnosis and creates a PR to allowlist it on Frontend, and allowlist tokens in Tokenlists repo

[ ] /defender

Same as /hal but works for Base and Avalanche too (so 6 chains total), both webhooks always run but they create the same PR with same details so it's ok if both run.

Tokens, Pool list and single pool fetching supported by api v3


ObjectId serialization optimizations

ObjectId(byte[]) reads directly from array rather than wrapping in a
ByteBuffer
toString/fromString using fewer intermediate objects
new ObjectId(ByteBuffer) constructor

The ObjectId class has changed substantially in master since this was submitted.  Any interest in trying to re-apply your changes to the latest on master?

Closing, much has changed since this initial patch with the new 3.x series of the driver.  As such this no longer can be applied cleanly.


Update minSdkVersion to 14.

NativeScript/NativeScript#694

run ci

Hey @vbresults
Thanks for your contribution!
Changes to the runtime project as far as minSdk is concerned are safe, but changing the minSdk versions inside the project-template (used in every nativescript android project) can have an adverse effect unless we can ensure that all components used on top of the runtime (like the tns-core-modules, and many community-driven plugins) are compatible with the drastic change of version proposed in the PR.
Developers who wish to experiment with lower versions of the android SDK can override the configuration in their app/App_Resources/Android/app.gradle file.


Top level suggestions are not working

Description:
$subject with the below code. Suggestions for the math: are invalide
import ballerina/math;

const J2000 = 2451545;
const DEGREE = math:

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

According to the grammar above syntax is not supported.  So, we'll avoid this invalid suggestions


systemd is out of date.

Issue description
Arch is already on 238.
238 fixes some PAM issues so having this up sooner than later would be very appreciated!
Steps to reproduce
N/A
Technical details

system: "x86_64-linux"
host os: Linux 4.14.24, NixOS, 18.03pre130932.cc4677c36ee (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0
channels(root): "nixos, nixpkgs"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

I'd open a pull request, but a big project like this I'm not too sure how to navigate the patches and other nuances something like systemd needs to have to work with nixos. If it's as simple as just changing the hash and download link and whatever else, then please say so.

I'm actually not sure why (what's different?) but NixOS uses a fork of systemd, perhaps a PR to that repo would be a starting point?
https://github.com/NixOS/systemd

@Chiiruno Regarding the PAM fixes: I can't a mention in the NEWS file of systemd. Are they critical? Should we backport this to 18.03?
Otherwise the changelog looks fine to me, even for a 18.03 backport.
To update systemd a new branch has to be created on our systemd fork with all our patches rebased to the current tag. This is pretty easy and I can do it if required.

Just a recent change there: upstream systemd has long defaulted to breaking the very idea of screen, tmux and POSIX-required nohup by cleaning up user processes on logout regardless of the daemonised state. This is apparently because Gnome cannot keep track of its own daemons, and also cannot put them into a separate cgroup. When that version landed in Nixpkgs, NixOS default config for logind has been updated to switch this functionality off. Recently, config handling has changed, so just the default got patched.
Also, the log shows that special handling of / and /usr is extended to /nix and /nix/storem, that hardcoded /lib/modules check is removed etc.

@fpletz No, it is not critical except for bcachefs and ecryptfs users. #32279 #30333
I'm a bit of a newbie, so I can't tell you whether or not this should be backported to 18.03, I can say I'd like it to be.

Ah, those PAM issues. Awesome. Thanks! I'll look into it. cc @vcunat

Fixed by #37647 for staging/master and https://github.com/NixOS/nixpkgs/compare/361bd591ea4a...2d2ab94cd2c7 for 18.03.

Well, this is a problem -- see #37744.
I suspect any fix for the mouse problem won't make it into 18.03.

Security and bug -fixes are the point of stable releases.


HIVE-25004. HPL/SQL subsequent statements are failing after typing a

Error signal stuck after the first failure causing subsequent statements to fail.

cc: @mustafaiman

👍


[Cleanup] Remove unused StaticOutputLibraryFileExtension

This field isn't used anywhere, so just a simple code cleanup.

Closing this, it might be used in some platform plugins...
It'll have to wait until the whole extensions and platforms capacities are reworked.


nc_set_log_level() should always be defined, but a no-op if logging is not enabled.

I regret the way that I implemented the nc_set_log_level() function. It is not included in the library unless logging is enabled.
This means that every client library has to keep track of whether this function is present or not, or provide a (no-op) version of the function to stop their links from breaking.
This is happening to me right now with the PIO library:
CMakeFiles/pio_unit_test.dir/nc_set_log_level2.c.o: In function nc_set_log_level2_': /home/ed/pio3/ParallelIO/tests/unit/nc_set_log_level2.c:7: undefined reference to nc_set_log_level'
collect2: error: ld returned 1 exit status
What I did with the PIO logging function, and what would make more sense with the netcdf one, is to always define the function, but just have it do nothing if logging is not defined. Then user code could use logging in development, and then just move the code to production without taking out the call to nc_set_log_level().
This is already the case with the LOG() macro (that is, it can be used in code, and will evaluate to nothing of logging is not enabled). But this is not true of the nc_set_log_level() function.
To execute the change is trivial, and I can submit a PR, but I wanted to see what the netcdf team thinks.

Makes sense to me, and wouldn't cause any harm that I can think of off the top of my head.  What do you think @DennisHeimbigner?

I agree, this seems quite reasonable.

Actually it might cause some downstream pertubation, and it might be best to add a configure option that did it the old way.
The reason it could cause downstream problems is some librarys and programs have no-doubt defined their own versions of it, because they are used to it being not present in production.
So those users, if any, could use the configure option to get a quick upgrade working, and then take the time to tear out whatever code they have to support a sometimes-missing nc_set_log_level().

Something like --provide-set-log-level-stub would work; I agree that we
don't want to cause a collision for those who already have a work around in
place, good thinking!
On Mon, Dec 19, 2016 at 2:37 PM, Imperial Fleet Commander Tarth <
<EMAIL_ADDRESS>wrote:

Actually it might cause some downstream pertubation, and it might be best
to add a configure option that did it the old way.
The reason it could cause downstream problems is some librarys and
programs have no-doubt defined their own versions of it, because they are
used to it being not present in production.
So those users, if any, could use the configure option to get a quick
upgrade working, and then take the time to tear out whatever code they have
to support a sometimes-missing nc_set_log_level().
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Unidata/netcdf-c/issues/341#issuecomment-268086053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEH-Unk6Jz_Ud36KLRF4-PMAb6WteKrTks5rJvkugaJpZM4LRNC_
.

I'm hitting this error with PIO1
/opt/apps/cmake/3.8.2/share/cmake-3.8/Modules/CheckFunctionExists.c:17: undefined reference to nc_set_log_level'`

If this is a PIO error, you should put on the PIO github project, not the netCDF one.
Both PIO and netCDF have an --enable-logging as a configure option. Try building PIO without it. If that doesn't work, put up an issue in the PIO project:
https://github.com/NCAR/ParallelIO


Dedicated GitHub user for release commits

Currently all release-related commits made by Travis are committed as @jamescway.

hehe yeah they do :)

... and so userzipkinci was born


Example provided for 80 -> 8080 redirect fails on ubuntu14

The example in your readme for redirect traffic from port 80 to 8080 does not work.  It looks like this issue was filed once years ago when jira was still the place.
https://tickets.opscode.com/browse/COOK-1004
I am currently running into this exact same issue following the steps outlined in your readme.  Is the solution really what is described in the ticket?  Why would this be the example listed in the readme then? Am I missing something?
[2015-01-29T15:53:39-05:00] ERROR: execute[rebuild-iptables] (iptables::default line 23) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '25'
---- Begin output of /usr/sbin/rebuild-iptables ----
STDOUT:
STDERR: Bad argument `*nat'
Error occurred at line: 14
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
rebuild-iptables: iptables-restore failed! - 512 at /usr/sbin/rebuild-iptables line 134.
---- End output of /usr/sbin/rebuild-iptables ----
Ran /usr/sbin/rebuild-iptables returned 25
       [2015-01-29T15:53:39-05:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

followed the README instructions on 1404 and it just worked fine.  don't know if this bug got fixed in the past 18 months or if there was some other issue, but can't replicate, so closing


Host routing pattern not match when host contains port

Describe the bug
Host routing pattern not match when host contains port
if you are running server behind a port like 8080  and
when  you hit browser for gateway.lcl:8080   this will not match a pattern gateway.lcl
spring:
  cloud:
    gateway:
      routes:
        - id: gateway
          uri: https://example.org
          predicates:
            - Host= gateway.lcl

Sample
i created this repo to simulate the error and how to fix it in this url https://github.com/ashraf-revo/gateway-error/tree/issue-host-name
.

Closing in favor of #3037

@spencergibb is there any plan to review the pr or see this issue


Is there a demonstration about dubbo+consul

Is there a demonstration about dubbo+consul

refer my project to solve:
https://github.com/imgoby/spring-cloud-alibaba-graalvm/tree/main/spring-cloud-alibaba-starter-dubbo


Target cluster joins federation fine but after a "while", kubefed-controller-manager shows ClusterNotReachable

What happened:
Target cluster joins federation fine but after a "while", kubefed-controller-manager shows ClusterNotReachable
What you expected to happen:
Target cluster to stay in federation
How to reproduce it (as minimally and precisely as possible):
kubefedctl join target-cluster --cluster-context target-cluster --host-cluster-name host-cluster --host-cluster-context host-cluster --v=2 --kubefed-namespace=kube-federation-system
Let that above work and wait 40 minutes or so.
Output of above command looked fine:
I0930 09:40:54.868390   23317 join.go:160] Args and flags: name target-cluster, host: host-cluster, host-system-namespace: kube-federation-system, kubeconfig: , cluster-context: target-cluster, secret-name: , dry-run: false
I0930 09:40:57.574874   23317 join.go:242] Performing preflight checks.
I0930 09:40:57.766002   23317 join.go:248] Creating kube-federation-system namespace in joining cluster
I0930 09:40:57.960535   23317 join.go:386] Already existing kube-federation-system namespace
I0930 09:40:57.960577   23317 join.go:256] Created kube-federation-system namespace in joining cluster
I0930 09:40:57.960607   23317 join.go:407] Creating service account in joining cluster: target-cluster
I0930 09:40:58.162961   23317 join.go:417] Created service account: target-cluster-host-cluster in joining cluster: target-cluster
I0930 09:40:58.163008   23317 join.go:445] Creating cluster role and binding for service account: target-cluster-host-cluster in joining cluster: target-cluster
I0930 09:40:58.951307   23317 join.go:454] Created cluster role and binding for service account: target-cluster-host-cluster in joining cluster: target-cluster
I0930 09:40:58.951355   23317 join.go:813] Creating cluster credentials secret in host cluster
I0930 09:40:59.334572   23317 join.go:839] Using secret named: target-cluster-host-cluster-token-qrxzf
I0930 09:40:59.538259   23317 join.go:882] Created secret in host cluster named: target-cluster-pp2gn
I0930 09:40:59.970396   23317 join.go:284] Created federated cluster resource

Anything else we need to know?:
when the cluster goes unhealthy, this is the log in kubefed-controller-manager
E0929 23:31:32.200579       1 clusterclient.go:131] Failed to do cluster health check for cluster "target-cluster": the server has asked for the client to provide credentials

Environment:

Kubernetes version (use kubectl version)
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.9-eks-4c6976"

KubeFed version
KubeFed controller-manager version: version.Info{Version:"v0.4.0-13-gb31dd08", GitCommit:"b31dd086f79e8c18a4eb08735d6af40d778b6af1", GitTreeState:"clean", BuildDate:"2020-09-28T09:37:05Z", GoVersion:"go1.14.7", Compiler:"gc", Platform:"linux/amd64"}

/kind bug

@kiich thanks for reporting this bug. After running kubefedctl join, would you please run kubectl get kubefedclusters -Aw and paste the output here? Does the cluster get ready eventually?

Thanks for getting back @makkes
This turned out to be user error 🤦  where we were using the "generated" token as our secret on the host cluster which only lasted for 1 hour! once we used the proper token, this stayed up and target cluster in federation continued to stay.
Appreciate you getting back - i'm closing this one now. thanks!


Add Google Cloud DNS to products.json

This is needed for it to appear in the left navbar of the Reference tab. I work as part of this team at Google (alexdupuy@).
The Cloud DNS cmdlets page https://googlecloudplatform.github.io/google-cloud-powershell/cmdlets/google-cloud-dns.html gets a 404, it seems like the dns-cmdlets branch wasn't merged?

This also includes unrelated change, will re-re-submit the PR.


unbinding Binding

Sometimes it's useful to have Binding that unbinds some input symbols.
For example,
data Input = A | B | C

bound_A :: Binding s Input
bound_A = binds $ on A `run` putStrLn "hoge"

unbind_A :: Binding s Input
unbind_A = ... -- something that unbind input A

Then,
bound_A  <> unbind_A == mempty
unbind_A <> bound_A  == bound_A

This can be implemented by changing the value type of Binding map from Action ... to Maybe (Action ...). Because Binding and Binder are opaque, the change would be additive (i.e. no need to major version bump).

If you want this feature, just comment here.


FindTBB.cmake problems

It should look for libtbbmalloc.so, not libtbbmalloc.so.2. On my OS it's libtbbmalloc.so.4
Please drop the numeric suffix.
Also you shouldn't require tbb_debug.so libs by default. I tried -DTBB_LIBRARY_DEBUG:BOOL=OFF, it passed config stage and later failed:
-- Installing: /usr/ports/science/ospray/work/stage/usr/local/lib/libtbbmalloc.so
CMake Error at builddir/ospray/intel64/cmake_install.cmake:31 (file):
  file INSTALL cannot find
  "/usr/ports/science/ospray/work/OSPRay-087dc8a/ospray/TBB_LIBRARY_DEBUG-NOTFOUND".
Call Stack (most recent call first):
  cmake_install.cmake:61 (include)

A fix is difficult:

we cannot search for libtbbmalloc.so, because this is only a reference to libtbbmalloc.so.2 and will thus brake the package.tgz
so version 4 on your system is strange: even the lastest version on https://www.threadingbuildingblocks.org/ still has .2

cmake-modules uses their macro CHECK_LIBRARY_EXISTS (LIBRARY FUNCTION LOCATION VARIABLE) in share/cmake/Modules/CheckLibraryExists.cmakeand checks for libraries in this fashion: CHECK_LIBRARY_EXISTS("dnet" "dnet_ntoa" "" X11_LIB_DNET_HAS_DNET_NTOA), without ever mentioning their numeric suffix.
Maybe you can add dependency on cmake-modules and just use this macro?

Well, maybe. The need to search for suffix .2 is actually only for the redistribution in the binary packages, not for building and running OSPRay. Changing this is on our TODO list anyway, so this issues may go away in conjunction.
Still, where does libtbbmalloc.so.4 come from? A custom build of TBB? It's a very unusual case. So, I'll leave it open, but it is low prio.

For some reason, suffix 4 is hardcoded in the FreeBSD port, devel/tbb. For some reason, tbb doesn't build the suffixed library, and the port code assigns the suffix.

The so suffix signifies the API version of the library, which is often (but not necessarily, as in the case with TBB) identical to the major version. So it seems that the FreeBSD port code should be changed to use a hardcoded suffix 2.

Ok, I created the bug report for this for the FreeBSD port.

Thank you. Also for reporting all the other issues and thus helping OSPRay to become more mature.

you're welcome!

Hi, I am not quite sure if this is totally related to this issue, but I am wandering why OSPRay is installing the tbb libraries. In other words, I had to remove from ospray/CMakeLists.txt the following lines from to avoid conflicts my Ubuntu system installation of TBB:
   INSTALL(PROGRAMS ${TBB_LIBRARY} ${TBB_LIBRARY_MALLOC} ${TBB_LIBRARY_DEBUG} ${TBB_LIBRARY_MALLOC_DEBUG}             DESTINATION ${CMAKE_INSTALL_LIBDIR} COMPONENT lib) # /intel64?
Do we want OSPRay to install those libraries or should OSPRay rely on pre-requeries such as embree and TBB?
Cheers,
Cyrille

You are right. In the current devel branch (and coming release) this behavior is already changed: 3rd-party dependencies  are not installed per default anymore (only when OSPRAY_INSTALL_DEPENDENCIES is set).

Ok, thanks!


Kubeconform does not report invalid metadata.name

Kubeconform 0.6.4
❯ kubeconform -v
development

❯ cat /tmp/ns.yml
apiVersion: v1
kind: Namespace
metadata:
  name: NameSpaceName

❯ kubeconform -verbose /tmp/ns.yml
/tmp/ns.yml - Namespace NameSpaceName is valid

❯ kubectl apply -f /tmp/ns.yml
The Namespace "NameSpaceName" is invalid: metadata.name: Invalid value: "NameSpaceName": a lowercase RFC 1123 label must consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (e.g. 'my-name',  or '123-abc', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?')

Kubeconform should not allow this.

This also happens when metadata.name is too long :
metadata.name: Invalid value: "…-toooo-long": must be no more than 52 characters


Chrome Extension to check grammar of the sentence

Is your feature request related to a problem? Please describe.
When I write any email or write any application, notice or chat i find many issues that if this sentence grammar is correct of not. To solve this many times i have to switch my tab and check here and there. It is annoying sometimes as it break my concentration and writing flow.
Describe the solution you'd like
I will make a chrome extension that will check the grammar of the sentence that i will select and give me a suggestion if any changes is needed.
How do we know when the feature is complete?
I will make add all the files before raising the PR and submit a PR with the code of the chrome extension.

Please assign me this under GSSOC'24 I will make this and create a extension that will solve the problem of many people including myself as well

@Sulagna-Dutta-Roy Mam I'd like to work on this issue, if this hasn't been solved yet.
Thank you!


PatMe should(?) use Dalamud's general channel

That's what the developer of Tidy Chat said here when I reported that it was suppressing the /patme output:
https://github.com/NadyaNayme/TidyChat/issues/51
Hope this is helpful!

Tidy Chat is killing a lot of chat types by design, that what it's supposed to do. System channel is especially heavily affected, and that's where PatMe outputs its texts. There's no "general channel", unless they mean Say channel, which is not appropriate for my counter outputs.
Can switch to something like Notice (idk, server info?) or Echo (macro output) and maybe it won't collide.

Tidy Chat is killing a lot of chat types by design, that what it's supposed to do. System channel is especially heavily affected, and that's where PatMe outputs its texts. There's no "general channel", unless they mean Say channel, which is not appropriate for my counter outputs.
Can switch to something like Notice (idk, server info?) or Echo (macro output) and maybe it won't collide.

You should use ChatGui.Print() which uses Dalamud's General Chat setting - which is set to Debug by default but can be set to go to pretty much any chat channel. This is what most plugins do and Tidy Chat does not filter anything that sends to Debug since 100% of Debug channel messages are Dalamud or Dalamud Plugins as that is the only way to send anything to that channel.


Combine tasks to scan up to target split size using parquet row group information

Merged. Thanks for fixing this, @samarthjain!


wsgi:error

Hi, I'm having an issue with this project that just happened today. Yesterday it ran fine so I'm not sure what's up. I'm getting wsgi:error constantly when trying to add inputs/outputs and nothing is streaming. Here is an example (with ip addresses and host names edited out):
[Thu Jul 04 01:29:03.657654 2019] [wsgi:error] [pid 4245:tid<PHONE_NUMBER>27616] [client ...:15844] INSERT INTO CapInputNames  ( InputInterface, InputId, InputUrl )  VALUES( "URL", "0", "rtmp://<IP_ADDRESS>/live" ) , referer: http://********.com:8888/
Thank you!

The ingest_url should be a location on ngnix server with POST enabled.


DEX-359 Add roles and profile image to users listing api

The API now returns something like this:
[
    {
        "is_internal": true,
        "is_exporter": false,
        "is_active": true,
        "profile_fileupload": {
            "created": "2021-07-09T20:20:31.888901+00:00",
            "mime_type": "image/png",
            "guid": "ec220d3a-36c4-43a2-a062-3343eeb025bc",
            "src": "/api/v1/fileuploads/src/ec220d3a-36c4-43a2-a062-3343eeb025bc",
            "updated": "2021-07-09T20:20:31.888927+00:00"
        },
        "in_alpha": false,
        "is_admin": true,
        "is_user_manager": false,
        "is_staff": false,
        "guid": "366cb80a-e971-4576-b851-8c75177d1d6a",
        "is_researcher": false,
        "full_name": "",
        "in_beta": false,
        "is_contributor": true,
        "email"<EMAIL_ADDRESS>    },
    ...

/rebase

/rebase

There's some (probably) unrelated test failures I need to fix

Test fixed in #241

/rebase

code all looks good to me, but wanted to confirm:  is this listing (and this level-of-detail) only something admin-like folks can see?  just curious cuz wondering if any-old-user can see this, if that might be leaking too much info.  (e.g. who has what roles)

/rebase

/rebase

code all looks good to me, but wanted to confirm: is this listing (and this level-of-detail) only something admin-like folks can see? just curious cuz wondering if any-old-user can see this, if that might be leaking too much info. (e.g. who has what roles)

@naknomum I think that makes sense.  It's definitely possible to change schema according to permission, I think I've seen it somewhere...

Lets roll with it for now. It can be added to the admin user list page, and then when we need it somewhere less secure we can discuss what should be omitted in another schema.

Oh yeah I forgot the API is already protected so this is ok :+1:


timer

The Timer claims to
# next time, sleep however long is left of our interval, taking
# off the time we took to run

but we only measure the time of spawn_worker, not the actual entrypoint run
looks like this has been broken a very long time
try e.g.
import time
from nameko.timer import timer

clock = time.time()

class Service(object):
    name = 'timertest'

    @timer(1)
    def tick(self):
        print 'tick', time.time() - clock
        time.sleep(5)

we should either remove the broken "feature", or if we want this despite living without it for this long, fix it (can use a pattern similar to the http entrypoint handler https://github.com/onefinestay/nameko/blob/master/nameko/web/handlers.py#L48)

I'm afraid i don't understand you..
You want to wait on finish of last round and then new one will start, don't you?

the problem is that in the current implementation, we measure how long self.handle_timer_tick(). but that function calls spawn_worker which is asynchronous, and returns as soon as the handler is spawned, and doesn't wait for it to finish.
in the example above, you see 'tick' every second, even though the handler takes 5 seconds to run

I'm in favour of fixing this. I think the semantics should be either:

At most once per interval seconds or
Exactly interval seconds after the previous execution finishes

Looks like @Sparkycz's PR does the second option.

to me it looks like the pr waits interval - elapsed_time, which is what the original code tried to do, and my preferred choice i think. is this your option 1?

the both PRs are wrong.. i'll send the first one now and meanwhile i'm trying to solve the second one. I'm sorry I havn't have the time for it..

Currently it probably does what we want. If the service method works longer than interval Timer waits for the completion and then fires the next one.

@davidszotten Yep, waiting interval - elapsed_time is Option 1 and also my preference.
@Sparkycz I will add a few comments to the PR. Please address them and then we'll merge this down. Thanks!

Is this still being worked on?  If it's just a matter of finishing up the tests I can give it a try

@daviskirk I think almost certainly not. A fix would be great!

@mattbennett see #579


Add skip subscription manager patch to devscripts role

https://github.com/openshift-metal3/dev-scripts/pull/1674 enables CRB repos on RHEL using subscription-manager to devscript. It breaks downstream baremetal job.
In downstream, we add custom crb repos. The systems are not subscribed to subscription manager. It is blocking the pipelines.
https://github.com/openshift-metal3/dev-scripts/pull/1681 runs subscription-manager command when system is subscribed. Since it is not merged yet. Let's copy the patch in devscripts role to unblock it.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

/approve
makes sense. Enforcing subscription isn't a good :/. PR has also been submitted against dev-scripts repository via https://github.com/openshift-metal3/dev-scripts/pull/1681

/lgtm


Store the desktop and mobile topbar backgrounds in the same variable

This has been accomplished with the newest update to the :root variables.
--swatch-topmenu-border-color and --swatch-topmenu-bg-color control the color of the topbar menu. The actual gradients are still separate variables due to needing to be different heights.


Question: is SubscribeBlockTracker safe to use?

I noticed the SubscribeBlockTracker while digging around packages trying to lower the number of eth_getBlockByNumber requests in web3-provider-engine. Is it safe to use? Seems to be working. However it's not exported, nor mentioned anywhere in the docs.
Tagging @jamespic as he seems to have implemented it 2 years ago - hope you don't mind the ping.

Well, it was safe to use when I wrote it two years ago 😉.
If I remember rightly, at the time I was interested in interesting with API endpoints that support push subscriptions, like websockets and TCP IPC. But the project I was using it for ended up going a different way (I'm not using it now), and a lot has changed in this space in those two years. So if it were me, I'd test it before using it on a real project.

😀

There are tests for this, so in that sense, we know it works, but we still don't use it for anything at MetaMask. I'd echo @jamespic's advice with the expectation that it may go away at some point in the future. If people still need it after that point, then we can accommodate another solution.


typo in "install_genome_data.sh"

line 135:
ENH="http://mitra.stanford.edu/kundaje/genome_data/mm10/ataqc/mmm10_enh_dhs_ucsc.bed.gz"
thx!

Thanks for reporting this. fixed in the commit 11a2ad6.


Adding resource based permissions

As far as I can tell, the permissions system is purely role-based. For example, if I have a role which gives me the EditMeetingComment permission, then I am capable of editing all meeting comments.
Say a meeting comment should only be editable by the one who made the comment (or to add some complication, it could also be edited by a sysadmin). What would be a good way of extending the project?
Perhaps something like adding ACLs to the User access controller? It's not clear to me when permissions would be added/changed/removed - always at the controller level, or in integration events? I think the latter case could require that you pass around the identity of the user to the actions and events, which seems not ideal.
Any ideas on how to implement this? (Or is it already there and I've totally missed it)

Ah ok upon further digging I see that these are encoded as rules inside the aggregates - the Meetings domain has IMember context which accesses the user id from the IExecutionContextAccessor, and then checks that e.g. the current user is also the one who authored the comment. So mystery solved I guess.
I still wonder how this would work with the case I mentioned where a comment can be edited by either the author or a sysadmin. Or maybe a comment might also be edited by some trigger that's not caused by a user via the API, rather a Cron job or something.


rekit-plugin-redux-saga  not installing properly

As mentioned already in the Gitter Channel I thought I file an issue as well.
Steps to reproduce:
npm install -g rekit@latest
rekit create cf03
cd cf03
npm install rekit-core@latest rekit-studio@latest redux-saga
rekit install rekit-plugin-redux-saga
npm install
npm start
Everything compiles and start the 3 servers. When I try to add a new Feature in Rekit Studio i get the following error:

If I look at the source files there is also no "rootSaga.js" and no Saga Middleware injected in the Apps index.js

Either I do something terrible wrong or there might be a bug in the plugin-code.
Thanks for the great work on Rekit, which helps a beginner in React and Redux stuff to grasp concepts and insights around this cool stuff.

Thanks @supnate. Will try this out immediately :-)

Sorry to bother again. Maybe I'm asking "noob" questions:
I tried the following in exact order:
rekit create cf01
cd cf01
npm install
rekit install rekit-plugin-redux-saga
npm start

If I open Rekit Studio and try to add new feature I get the same error as mentioned above in picture 1.
I have globally installed react-saga and im using the following versions:
node --version
v9.5.0
npm --version
5.6.0

rekit-plugin-redux-saga is installed in the node_modules folder. But still no rootSaga.js in /src/common.
I'm running the terminal as Admin, so there should be no issues writing files. Here is the output after the rekit install rekit-plugin-redux-saga command:
rekit install rekit-plugin-redux-saga
Installing plugin:  rekit-plugin-redux-saga
Writing to package.json...
Executing install.js if exists...
Done.: 30012.496ms

Hi @supnate
This did the trick!
After adding another async action to a existing feature the needed adjustments to the necessary files where made. After this I can also create a new feature  without errors.
Thanks so much, no I can continue to explore the "rekit-world"!

That's great! Thanks for the patience! It's really a bug should be fixed.

I'm using Rekit in my current project with redux-saga and rekit-redux-saga plugin. I noticed immediately that something was not working properly and I decided to fixed myself.
I believe that the rekit-redux-saga library was not updated (yet) to be compatible with the last version of redux-saga.
Here are the changes I did to make it work again
# src/common/rootSaga.js
import { all } from "redux-saga/effects";
...
function* rootSaga() {
  yield all(sagas.map(/* istanbul ignore next */ saga => saga())); // The all function was not before in this line
}

The redux-saga templates will still import the "delay" function that is not available anymore. Just remove that import. It's used only for demonstration purposes anyway.


Tweak username taken/deleted error messages

note the frontend uses there own message in the username taken case:

cc @cecileboucheron

merging over unrelated circle failure


[MINOR][CORE][TESTS] Fix EventLogFileWritersSuite typo

What changes were proposed in this pull request?
A simple typo fix
Why are the changes needed?
Not truly necessary, I just saw it and fixed it
Does this PR introduce any user-facing change?
No
How was this patch tested?
n/a
Was this patch authored or co-authored using generative AI tooling?
No

cc @dongjoon-hyun

It is not appropriate to use SPARK-34503, which was fixed in v3.2.0.
It would be greatly appreciated if you could modify your title to include [MINOR][TESTS] for minor revisions.
Also, please ensure that there are no spelling, grammar or punctuation errors in EventLogFileWritersSuite.

Ya, right. We cannot use the released JIRA issue ID. I removed the ID from the PR title according to @yaooqinn 's advice, @surjikal .

Is this the only typo in this test suite, @surjikal ?

No other typos. I just double checked using a spell checker.
Side note: I wasn't intentionally searching for typos btw, I just stumbled upon it.

Ya, right. We cannot use the released JIRA issue ID. I removed the ID from the PR title according to yaooqinn's advice

Noted for next time, thanks for the edit!

I just amended the commit message. I realize I used the issue as the branch name... is this a problem?

Hi @surjikal, after reviewing the CI https://github.com/apache/spark/pull/43895/checks?check_run_id=18834027975, you need to enable it by following the instructions provided.

I realize I used the issue id as the branch name too... is this a problem?

It's alright, as it doesn't impact the process of reviewing or committing a PR.

@yaooqinn Apologies, I had assumed I didn't need to do it, given the nature of the change.
This is done.