RangeError: Wrong length! Error. or Error: 400 PHONE_CODE_EXPIRED CODE#400 PHONE_CODE_EXPIRED

here is sample
when i receive activation code and use it to sign in telegram by below sample code get this error.
RangeError: Wrong length!
use babel for transcompile to es5.
code :
`
const login = async () => {
try {
const phone = '+98........................'

const info = JSON.parse(fs.readFileSync('code.json'));
const code = info.phoneCode;
const phone_code_hash = info.phone_code_hash;

const res = await telegram('auth.signIn', {
  phone_number: phone,
  phone_code_hash,
  phone_code: code
})

const { user } = res
const {
  first_name = '',
  username = ''
} = user

console.log('signIn', first_name, username, user.phone)
return first_name

} catch (error) {
console.error(error)
}
}`
UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): RangeError: Wrong length!

You should check every constants to make sure they are valid first.
always surround all your codes with three `

@sajadghobadi How did you receive a phone code hash from a file?
Looks like it does not exist at all
Hash is what you must inquire from the server
Example

@zerobias Probably he split the login process into two parts: getCode and signIn.

@zerobias and @wfjsw   thanks lot for response
this error occurre for cheep!(sorry) mistake. i must pass phone_code_hash to signIn method but in truly i send undefined!!!
change and correct phone hash code to
const res = await telegram('auth.signIn', {   phone_number: phone,   phone_code_hash:phone_code_hash,   phone_code: code })
My final target is this : read messages from channel list(example:['channel1','channel2','chanell3'])
for do this is run below step

call auth.sendCode method and write phone_code_hash  to file named code.json
write manually activation code that i received in my phone  to file named code.json
then i trying to login by those values in code.json by call auth.signIn (@wfjsw  you right exactly in split send code and login in to step)
but i get this error always  : Error: 400 PHONE_CODE_EXPIRED CODE#400 PHONE_CODE_EXPIRED

please help me if you can.
thnaks.
sorry for my bad en

@zerobias  you can't help?

@sajadghobadi Have you used the code as string or number type? Phone, code and hash fields must be string, not number.
I think this code.json should fails
{
  "code": 12345
}

So better to try this
{
  "code": "12345"
}

@sajadghobadi
Hmm...Expired? You should try to understand it.
The main problem is that you are too slow to get you authenticated. Try to be quick next time.
However, depend on what you are doing, there is a rare case. According to https://t.me/MadelineProto/23
#UndocumentedAPIChangeOfTheDay
Telegram automatically invalidates your login code if it is sent to any chat on telegram before the login, this problem can be avoided simply by appending or pretending some chars to the code.
Thanks to @usage_tg for finding that out.

Time to debug on your own.

@sajadghobadi I also had such a error until I request code and sent the result within one connection

(also make sure that you are using the same auth keypair for auth)

@FragsterAt how did you grab the code from telegram to the code, i am getting response only for phone_code_hash and phone_code sent from telegram official to my telegram chat.
I copied the login_code from app, try pasted in
client("auth.signIn", {
phone_number:   number,
phone_code_hash: result.phone_code_hash,
phone_code:      "39480",
}).then((result) => {
console.log("User:", result);
});
But always getting PHONE_CODE_EXPIRED.
@wfjsw tried this but no luck appending or pretending return PHONE_CODE_INVALID
Some one please help.
#UndocumentedAPIChangeOfTheDay
Telegram automatically invalidates your login code if it is sent to any chat on telegram before the login, this problem can be avoided simply by appending or pretending some chars to the code.
Thanks to @usage_tg for finding that out.

@javeedrahman please use three backticks for code blocks

@goodmind okay sure got it.

Here is the Sample code trying::
const phone = {
  num : '+9199999999999',
  code: '22222'
}
const config = {
  // NOTE: if you FORK the project you MUST use your APP ID.
  // Otherwise YOUR APPLICATION WILL BE BLOCKED BY TELEGRAM
  // You can obtain your own APP ID for your application here: https://my.telegram.org
  id  : 49631,
  hash: 'fb050b8f6771e15bfda5df2409931569'
}

var telegram = MTProto({
    layer: 57,
    api_id: config.id,
});

  const run = async ()  => {
      try {
        const { phone_code_hash } = await telegram('auth.sendCode', {
              phone_number  : phone.num,
              current_number: false,
              api_id        : config.id,
              api_hash      : config.hash
        })
        console.log('phone_code_hash', phone_code_hash)
        res = await telegram('auth.signIn', {
          phone_number: phone.num,
          phone_code_hash,
          phone_code  : "83118"
        })
        console.log('signIn', res)
        console.log('\n Logined as user')
        console.dir(res.user, { colors: true })
      } catch (err) {
        console.log('err', err)
      }
  }
  run()

Were you able to figure this out?

@dundas  https://github.com/zerobias/telegram-mtproto/issues/124#issuecomment-367972932

They say if you are receive security code by sms and to telegram application then it will be expired. I don't reproduce it. Receiving code in telegram i still have valid security code and was able to sign in.
Check the client instance, it should be same across whole application lifecycle.
Client's configuration should define storage (where to put information about data center connection)
If you are using different phone numbers clean up previously created storage (remove storage json file)


Bugfix in benchmark example

fixed race condition bug in benchmark example, client thread could be spawned before configuration was complete, resulting in a "ConnectionRefused" error in around 75% of runs on my multithreaded machine

I don't understand how this can fix an error: neither in the old or new place where the thread is spawned is smoltcp running yet. When it runs (the loop below), the socket is added. There's no way for smoltcp to return a RST.
Are you sure your network configuration is OK? Are you setting it up according to the README? In particular, you do NOT have to set the IP <IP_ADDRESS> to tap0 on the linux side. If you do that, Linux itself could be replying with the RST.

I am 100% sure this fixes the error. I have checked multiple times, the weird thing was that it oncurred on only 1 of my machines and on that machine, the example would actually run correctly occasionally (like 5% of the times), which already implies some kind of race-codnition bug.
I think that in the old position the spawned thread starts reading/writing immediatly before the buffers and handles are set up properly, thus leading to the error.

The thread opens a Linux TCP socket  that talks to smoltcp through the TAP interface. If smoltcp isn't running yet, all the packets Linux sends to the TAP get lost, which causes the Linux TCP socket to wait around and retry sending the SYN. The only way you're getting ConnectionReset is if smoltcp replies with a RST, which is not possible because it's not running yet.
Can you post trace-level logs of the error ocurring, and the output of ip addr?

Sorry haven't found the time for this yet, will soon send the details of the error I get


Deselect prior-selected phassets

LOVE TLPhotoPicker! It's great!
The only thing I can't figure out is how to deselect phassets that were selected in a prior photo-picking session.  For example, if I have two phassets chosen, 1 & 2, then hit Done, when I come back into picking photos, I want none chosen, not the 1 & 2 from my prior session.  I closely searched through all the issues and didn't see anything that addressed this; sorry if I missed something.
I thought that this might be a configure option, but I can't find one that applies. Any help appreciated!

@RapDevPro
For Example
https://github.com/tilltue/TLPhotoPicker/blob/master/Example/TLPhotoPicker/ViewController.swift
et viewController = CustomPhotoPickerViewController()
        viewController.delegate = self
        viewController.didExceedMaximumNumberOfSelection = { [weak self] (picker) in
            self?.showExceededMaximumAlert(vc: picker)
        }
        var configure = TLPhotosPickerConfigure()
        configure.numberOfColumn = 3
        viewController.configure = configure
        //viewController.selectedAssets = self.selectedAssets <- ' Do not set selectedAssets.'

        self.present(viewController, animated: true, completion: nil)

Thank you! Don't know how I missed that.


Drag And Drop By Coordinates: drop arg does not work for GUI element "virtual joystick"

Drag And Drop By Coordinates tested with chromium and webkit
Short overview:
it makes a difference to test the keyword
•	with a draggable element which stays where it was dropped
•	or with a virtual joystick which tends to return to its default position when it is dropped
Suggested solution see below
Description of the system under test and a speculation why it behaves unexpectedly
There was a new drop argument introduced with  v12.2.0 which defaults to True. It was tested with the draggable GUI element and obviously worked fine. However the keyword does not meet the expectations when the GUI element moves by itself to a default position when it is dropped. Testing with a virtual joystick showed, that a sequence of Drag And Drop By Coordinates statements with drop=False had the same behaviour as with drop=True. It looks as if the Browser Lib keyword Drag And Drop By Coordinates is not yet designed to continue a previous call of Drag And Drop By Coordinates with drop=False. The call of Drag And Drop By Coordinates seems to expect and initialize a dropped mouse.
For moving the draggable element it makes no difference whether drop is set to True or False. However when a virtual joystick is moved outside its center and the next Drag And Drop By Coordinates is called, the test shows:

the joystick first returns to its origin, even when drop was set to False.
In consequence the next Drag And Drop By Coordinates is executed with a mouse that is not centered on the joystick.
When the first movement was long enough the joystick even does not move any more. This happens when the from coordinates don’t hit the joystick in its default position.

Test case with expected behaviour
Drag a GUI element, the lightened disk, from its origin O to point D passing the points A, B and C.
Drag And Drop By Coordinates    ${Ox}    ${Oy}    ${Ax}    ${Ay}    10    False
Drag And Drop By Coordinates    ${Ax}    ${Ay}    ${Bx}    ${By}    10    False
Drag And Drop By Coordinates    ${Bx}    ${By}    ${Cx}    ${Cy}    10    False
Drag And Drop By Coordinates    ${Cx}    ${Cy}    ${Dx}    ${Dy}    10    False
Drag And Drop By Coordinates    ${Dx}    ${Dy}    ${Ox}    ${Oy}    10    True

The element shall move on a smooth/continuos path, without dropping. When the virtual joystick element is dropped at D the disk shall return to the origin O.

(Mockup)
What the real test shows (chromium and webkit):

The orange line does start at the origin O instead of A.
Every line starts at the origin although the drop parameter was set to False.
Obviously the drop=False state is not kept from one keyword call to the next.
Movement from A to B, wanted (green) and real (red):

interaction.py, line 943 ff:
self.mouse_button(MouseButtonAction.down, x=from_x, y=from_y)
self.mouse_move(x=to_x, y=to_y, steps=steps)
if drop:
   self.mouse_button(MouseButtonAction.up)

I can't see what happens when self.mouse_button is run.
I just suppose that the first line releases the mouse button of a previous move.
Maybe the desired behaviour is not reached by the drop argument.
Suggested solution
A solution might be to run the keyword with optional args for additional points between "from" and "to" coordinates:
from_x <float>
from_y <float>
to_x <float>
to_y <float>
steps = 1<int>
by_x1 <float>
by_y1 <float>
by_x2 <float>
by_y2 <float>
...
by_xN <float>
by_yN <float>  # where N is number of points between "from" and "to"

line 944 would be run in a loop for all the N points and the final point.
The functionality of argument steps would not change. It would control the number of mouse move events on each of the N distances.

@allcontributors please add @UliSei  for userTesting.

I am goint to implement the suggested solution.
Variant  1.) Argument drop will be deleted then. Instead it is possible to call the keyword with an optional argument, a list of coordinates:
[ [x1, y1], [x2, y2], ...[xN, yN] ].
Variant 2.) A data structure which includes the start and end point would be more generic:
[ [from_x, from_y], [x1, y1], [x2, y2], ...[xN, yN], [to_x, to_y] ].
But then it would be necessary to change the calls of the keyword at any place where it is used so far.
Variant 1 is to be preferred?

@UliSei
Could you give us a test page?
Or implement a test page with a virtual joystick first into our test web app?
then lets discuss what should be the expected behavior.
ok?

I would actually expect to use a different keyword sequence.
Drag And Drop By Coordinates    ${Ox}    ${Oy}    ${Ax}    ${Ay}    10    False
Mouse Move    ${Bx}    ${By}    10
Mouse Move    ${Cx}    ${Cy}    10
Mouse Move    ${Dx}    ${Dy}    10
Mouse Move    ${Ox}    ${Oy}    10
Mouse Button    up

Therefore i would say, we have to discuss the expected behavior.
i personally am not a big fan of that argument to not lift the mouse button.
Because then it is not a Drag&Drop it is just a Drag.

Or even better to understand:
${cntr}=    Get Element    joystick_panel.container    # this is the main object that stays static
Hover    ${cntr}
Mouse Button    down
Mouse Move Relative To    ${cntr}    100     0
Mouse Move Relative To    ${cntr}    0     -100
Mouse Move Relative To    ${cntr}    -100     0
Mouse Move Relative To    ${cntr}    0     100
Hover    ${cntr}
Mouse Button    up

it would be much more maintainable, because the drag and drop coordinates are no relative coordinates but absolute ones on the page. And you should only use these with calculated values from the current state of the page. And i think a good calculation anker in this case is the center of the boundingBox of the joystick 🕹 element itself.

The described issue itself is, that sending a mouse down event is only possible, if the mouse is not already down.
so if you send a mouse down event (on relative coordinate x100 y0) and then moves 100 pixel up and 100 pixel left, the joystick just moves from the center point 100up and 100left.
other joystick implementations it could be that the joystick in that case first snaps to x100 y0 and then follows you mouse.
The only thing imho we could do is to remember the button state of that keyword and depending on the state do the mouse down or not.
But in that case it is again just a mouse move...
and that would imho be too much magic.

Thanks a lot!
So I managed to move the joystick by this sequence  ...
    Mouse Move    ${centerX}    ${centerY}
    Mouse Button    down
    Mouse Move    ${centerRightX}    ${centerRightY}    ${STEPS}
    Mouse Move    ${centerUpX}       ${centerUpY}       ${STEPS}
    Mouse Move    ${centerLeftX}     ${centerLeftY}     ${STEPS}
    Mouse Move    ${centerDownX}     ${centerDownY}     ${STEPS}
    Mouse Move    ${centerX}         ${centerY}         ${STEPS}
    Mouse Button    up

... with the desired result:

From my point of view the remaining task is just to reset the "Drag And Drop By Coordinates" keyword as it was before - without the drop argument. Do you agree?

Did you do the drop argument to that keyword some weeks ago?
if so, and if you agree that it is not helpful because of these circumstances, then i agree and we could remove that argument again. In the hope no one else wanted to use it. 😁

Yes :-)
Since the argument can not be used for the purpose it was designed for it's useless and better to remove it.
I am going to prepare a PR.

Unfortunately there was one job of 23 where a timeout occurred after 30sec:
https://github.com/MarketSquare/robotframework-browser/actions/runs/2339630527

This is normal. Sadly sometimes. Due to slow resources in Github Actions
i retriggered the job

Thanks @Snooz82 - the CI pipeline now ended successfully!


Add ValidateBasic tests for Channel Upgrade Types

Summary
Follow up for #3451
Add validate basic tests for Upgrade and Upgrade Fields

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

can I handle this issue?

seems this was done with 6d80a3698ff4996c460e14fa299a76939bee165c?

Indeed, thanks for noticing that, @DimitrisJim!
Closed by https://github.com/cosmos/ibc-go/pull/3709.


docs(metrics): reformat serviceMonitor Helm variable descriptions

Which issue(s) this PR fixes:
longhorn/longhorn#8142
What this PR does / why we need it:
Final description formatting per @jillian-maroket's review of https://github.com/longhorn/website/pull/945.

@mergify backport v1.7.x v1.6.x


Support for Azure and AWS on Gardener

Description
Changes proposed in this pull request:

Support for provisioning AKS clusters via Gardener
Support for provisioning AWS clusters via Gardener
New examples added

Related issue(s)

https://github.com/kyma-incubator/compass/issues/403

Hi @Maladie,
first of all, thanks for your contribution.
The PR looks good and we would merge it, but unfortunately we are undergoing a gardener schema change at the moment to improve usability and add more configuration options (see https://github.com/kyma-incubator/hydroform/pull/27).
This will be merged next and therefore this PR will have to wait for a couple of days.
Sorry for the inconvenience.

Hi @Maladie,
we just merged the new gardener schema into Hydroform and it would be great if you could adapt your PR to the changes.
Thanks!

Thanks @clebs, will do.

@clebs PR adapted to new schema


[BUG] GenericNode fails when InputT and OutputT are different

The default constructor for RxNode fails under this condition.
Currently the lambda linking the observer and the subscriber is done in the body of the GenericNode constructor using this->make_stream, but that lambda needs to be moved to the RxNode constructor which takes a lambda.

Bug fix and test added as part of PR #123


Feature/documentation jenkins slaves

Issue Number:
Implementation description
@devonfw/devonfw-shop-floor

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Subtask] Support replace preparedStatement for Trino-jdbc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the subtask
Support replace preparedStatement for Trino-jdbc for the parent #3901
Parent issue
#3901
Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

@ulysses-you  can you assign this issue to me?


Add GIDS to list

Its a dated but still worth mentioning.

Thanks for adding this and making sure the date is in the correct order! :smile:


Adding Seurat's RPCA method to Benchmarking tasks?

Hello!
I noticed that Seurat's RPCA integration method was not included in either the 'Batch integration embed' task or the 'Batch integration feature' task. I know that RPCA is capable of both and it's a method that is often the first off-the-shelf R method that people choose, so I would be interested in seeing this added.
I would also be happy to work on this too!

Hi @andrewdchen,
Please feel free to add the method. We'd love to see it included here.
@danielStrobl: you had started adding it as well, no? Were there environment handling issues?

You can use the the documentation to guide you and  you can always ask us for guidance. https://openproblems.bio/documentation/create_component/add_a_method
We also have a coworking session on the Openproblems Discord on Friday. https://openproblems.bio/events/weekly_coworking/

I think that was in v1 where I was having the environment issues with seurat


makes credentials expiration UTC/localtime aware

Connecting to a Redshift cluster with Okta as the IdP was causing the login_url to be opened twice. The original issue is the fact that STS credentials expiration datetime was set in UTC and checked against local time (which is UTC+2 in my case). Local time was always an hour ahead (UTC+2 - STS session length of 1 hour) in my case and credentials were considered expired as soon as they were created.
Additionally fixes test collection by changing the setup.cfg - this could potentially be a different PR.
Logs look like this
2021-07-15 13:55:08,636 - redshift_connector.credentials_holder - DEBUG - Credentials will expire at 2021-07-15 12:55:08+00:00 (UTC), local time is 2021-07-15 13:55:08.636606+02:00.
Difference between local time and UTC time is 2 hours.

Description

Motivation and Context
Local time was always an hour ahead (UTC+2 - STS session length of 1 hour) in my case and credentials were considered expired as soon as they were created. Fixes #40
Testing
Executed the following script in the CEST (Europe/Amsterdam) to verify that login_url was opened only once
import redshift_connector

conn = redshift_connector.connect(
    iam=True,
    ssl=True,
    host="REDSHIFT_ENDPOINT",
    port=5439,
    database="DB_NAME",
    db_user="IDP_USERNAME",
    region="AWS_REGION",
    cluster_identifier="CLUSTER_NAME",
    login_url="IDP_LOGIN_URL",
    credentials_provider="BrowserSamlCredentialsProvider",
    user="",
    password=""
)

cursor: redshift_connector.Cursor = conn.cursor()
cursor.execute("select current_user")

result = cursor.fetchone()
print(result)

It would be great to have unit tests for this change but I am unsure how to
Screenshots (if appropriate)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Checklist

[x] Local run of ./build.sh succeeds
[x] Code changes have been run against the repository's pre-commit hooks
[x] Commit messages follow Conventional Commit Specification
[x] I have read the README document
[x] I have added tests to cover my changes
[x] I have run all unit tests using pytest test/unit and they are passing.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you @ivica-k ! We will run this PR through our internal test suite and follow up with any feedback next week :)

I'm not entirely satisfied with the tests I wrote.

LGTM -- thank you!

Woot! That was super quick, thank you!


azure-storage has been deprecated

npm WARN deprecated<EMAIL_ADDRESS>Please note: newer packages @azure/storage-blob, @azure/storage-queue and @azure/storage-file are available as of November 2019 and @azure/data-tables is available as of June 2021. While the legacy azure-storage package will continue to receive critical bug fixes, we strongly encourage you to upgrade. Migration guide can be found: https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/storage/MigrationGuide.md

async createReadStream(artifactPath) {
      const read = await blobService
        .getContainerClient(containerName)
        .getBlobClient(artifactPath)
        .download();

      const stream = new Readable().wrap(read!.readableStreamBody!);

      return stream as NodeJS.ReadStream;
    },
createWriteStream(artifactPath) {
      return blobService
        .getContainerClient(containerName)
        .getBlobClient(artifactPath).getBlockBlobClient().uploadStream();
    },

I gave a go, the new sdk design is awful IMO...you have to pass a Readable to uploadStream(readable) Any suggestion to make it work without change too much code?


[4.2-06-11] Re-apply "[migrator] migrator: avoid inserting base name while renaming if users' member access doesn't specify the base name. rdar://40373279"

Previously, we saw that unconditionally omitting type names can lead to
build errors (rdar://40458118). This revised fix omits type names only when
the new member name is identical to the old one.

@swift-ci please test


Any results on the validation set?

Thanks for your valuable work! I wonder if there are any results on the validation set (if used)? Such as the validation ppl values.

This has been on our to-do list. We have some train/val/test loss numbers but I don't think we have them systematically for every model.


Bugfix: Cookies file causes wget failures

Describe the bug
Steps to reproduce
On Arch Linux,
Screenshots or log output

Software versions

OS:                        ([e.g. macOS 10.14] the operating system you're running ArchiveBox on)
ArchiveBox version:        (git rev-parse HEAD | head -c7 [e.g. d798117] commit ID of the version you're running)
Python version:            (python3 --version [e.g. 3.7.0])
Chrome version:            (chromium-browser --version [e.g. <IP_ADDRESS>] if relevant to bug)

Please post the full output of archivebox version with no redactions.

Please post the full output of archivebox version with no redactions.

Hi. I have the same Problem since 0.5.3:

[+] [2021-01-18 09:45:20] "www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18"
https://www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18
./archive/1610963120.590836
title
favicon
wget
! Failed to archive link: Exception: Exception in archive_methods.save_wget(Link(url=https://www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18))
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/init.py", line 108, in archive_link
result = method_function(link=link, out_dir=out_dir)
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/wget.py", line 121, in save_wget
**timer.stats,
File "", line 11, in init
File "/usr/local/lib/python3.7/dist-packages/archivebox/index/schema.py", line 46, in post_init
self.typecheck()
File "/usr/local/lib/python3.7/dist-packages/archivebox/index/schema.py", line 57, in typecheck
assert all(isinstance(arg, str) and arg for arg in self.cmd)
AssertionError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/bin/archivebox", line 10, in
sys.exit(main())
File "/usr/local/lib/python3.7/dist-packages/archivebox/cli/init.py", line 133, in main
pwd=pwd or OUTPUT_DIR,
File "/usr/local/lib/python3.7/dist-packages/archivebox/cli/init.py", line 69, in run_subcommand
module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
File "/usr/local/lib/python3.7/dist-packages/archivebox/cli/archivebox_add.py", line 93, in main
out_dir=pwd or OUTPUT_DIR,
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/main.py", line 593, in add
archive_links(new_links, overwrite=False, **archive_kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/init.py", line 173, in archive_links
archive_link(to_archive, overwrite=overwrite, methods=methods, out_dir=Path(link.link_dir))
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/init.py", line 125, in archive_link
)) from e
Exception: Exception in archive_methods.save_wget(Link(url=https://www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18))

archivebox version:

~/archive$ archivebox version
Warning: using insecure memory!
 I have the same Problem since 0.5.3:

[+] [2021-01-18 09:45:20] "www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18"
https://www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18
./archive/1610963120.590836
title
favicon
wget
! Failed to archive link: Exception: Exception in archive_methods.save_wget(Link(url=https://www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18))
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/init.py", line 108, in archive_link
result = method_function(link=link, out_dir=out_dir)
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/wget.py", line 121, in save_wget
**timer.stats,
File "", line 11, in init
File "/usr/local/lib/python3.7/dist-packages/archivebox/index/schema.py", line 46, in post_init
self.typecheck()
File "/usr/local/lib/python3.7/dist-packages/archivebox/index/schema.py", line 57, in typecheck
assert all(isinstance(arg, str) and arg for arg in self.cmd)
AssertionError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/bin/archivebox", line 10, in
sys.exit(main())
File "/usr/local/lib/python3.7/dist-packages/archivebox/cli/init.py", line 133, in main
pwd=pwd or OUTPUT_DIR,
File "/usr/local/lib/python3.7/dist-packages/archivebox/cli/init.py", line 69, in run_subcommand
module.main(args=subcommand_args, stdin=stdin, pwd=pwd)    # type: ignore
File "/usr/local/lib/python3.7/dist-packages/archivebox/cli/archivebox_add.py", line 93, in main
out_dir=pwd or OUTPUT_DIR,
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/main.py", line 593, in add
archive_links(new_links, overwrite=False, **archive_kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/init.py", line 173, in archive_links
archive_link(to_archive, overwrite=overwrite, methods=methods, out_dir=Path(link.link_dir))
File "/usr/local/lib/python3.7/dist-packages/archivebox/util.py", line 112, in typechecked_function
return func(*args, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/archivebox/extractors/init.py", line 125, in archive_link
)) from e
Exception: Exception in archive_methods.save_wget(Link(url=https://www.poftut.com/how-to-update-upgrade-a-python-package-with-pip/#2021-01-18))

archivebox version:

~/archive$ archivebox version
Warning: using insecure memory!

I've just commented it out in my config:

root@raspberrypi:/export/container/debian/home/user/archive# grep -i cook ArchiveBox.conf
#COOKIES_FILE = /home/user/cookies.txt
root@raspberrypi:/export/container/debian/home/user/archive# file ../cookies.txt
../cookies.txt: Netscape cookie, UTF-8 Unicode text, with very long lines
root@raspberrypi:/export/container/debian/home/user/archive#

Long time ago i used this command to enable cookies:

archivebox config --set COOKIES_FILE=/home/user/cookies.txt

I've just commented it out in my config:

root@raspberrypi:/export/container/debian/home/user/archive# grep -i cook ArchiveBox.conf
#COOKIES_FILE = /home/user/cookies.txt
root@raspberrypi:/export/container/debian/home/user/archive# file ../cookies.txt
../cookies.txt: Netscape cookie, UTF-8 Unicode text, with very long lines
root@raspberrypi:/export/container/debian/home/user/archive#

Long time ago i used this command to enable cookies:

archivebox config --set COOKIES_FILE=/home/user/cookies.txt

Ah I think it's because it's read as a pathlib.Path in the config loading process, and needs to be converted to a str before being added to the wget command during the extraction process CMD = ['wget', ...].

Ah I think it's because it's read as a pathlib.Path in the config loading process, and needs to be converted to a str before being added to the wget command during the extraction process CMD = ['wget', ...].


Vscode debugging c/c++ does not respond or prompt when the.net framework version is too low

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: x64-1.58.2
OS Version: win7

Steps to Reproduce:

/extC


Test simultaneous Production and Development deployment

The workflow is documented here: https://github.com/FraunhoferCESE/madcap/wiki/Deployment-of-Appengine-Endpoints


[BUG]: CenterofExcellenceAuditComponents_1_17_managed.zip asks for value of "Developer Compliance Center URL" environment variable

Describe the bug
CenterofExcellenceAuditComponents_1_17_managed.zip asks for value of  Developer Compliance Center URL not Archive Site (URL) Environment Variable.
Component (please tell us which flow or app you are experiencing issues with):
CenterofExcellenceAuditComponents
Version 1.17

Environment Variable

To Reproduce
Steps to reproduce the behavior:

Import CenterofExcellenceAuditComponents_1_17_managed.zip
Create the site
click on "See Environment Variable"
See error

Expected behavior
I expect to see Archive Site URL not Developer Compliance Center URL
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Duplicate of #325


Querying firestore documents with subscribe never fetches

just never finishes fetching. setting subscribe to false fetches instantly
const ref = doc(firestore, "games", id);

const { data, isLoading } = useFirestoreDocumentData(["games", id], ref, {
    subscribe: true,
});

it does work with useFirestoreQuery
"@react-query-firebase/firestore": "^1.0.0-dev.7"
"firebase": "^9.11.0"
"react-query": "^3.39.2"

Also noticed this, happens with RTDB as well. It does return once an update to the DB occurs though. I'm guessing some interaction with React Query regarding the updates isn't right

any chances for a merge? :)

I am also experiencing the same problem, so it would be very appriciated if it got fixed

While waiting for this fix, I created a temporary custom hook.
`
useFireStoreDocTemp.ts
import {
DocumentData,
DocumentReference,
getDoc,
onSnapshot,
} from "firebase/firestore";
import { useEffect } from "react";
import { useQuery } from "react-query";
interface IProps {
keyName: Partial<string[]>;
docRef: DocumentReference;
subscribe?: boolean;
}
export const useFirestoreDocument = ({
keyName,
docRef,
subscribe,
}: IProps) => {
const query = useQuery(keyName, async () => {
const docSnap = await getDoc(docRef);
return docSnap.data();

});
useEffect(() => {
if (subscribe) {
const unsub = onSnapshot(docRef, (doc) => {
query.refetch();
});
  return () => unsub();
}

}, [subscribe]);
return query;
};
`
Usage:
  const query = useFirestoreDocument({     keyName: ["game", id],     docRef,     subscribe: true,   });

would be nice to have this fix merged. I rewrote whole app to use-query-firebase and now due this I have to rewrite it back or use custom logic when need to subscribe to document changes...
Please, make it work. Thanks!

For getting docs
`import { DocumentData, getDocs, onSnapshot, Query } from "firebase/firestore"
import { useEffect } from "react"
import { useQuery } from "react-query"
interface IProps {
keyName: Partial<string[]>
query: Query
subscribe?: boolean
}
export const useCustomFireStoreQuery = ({ keyName, query, subscribe = false }: IProps) => {
const getQuery = useQuery(keyName, async () => {
const snapshot = await getDocs(query)
return snapshot
})
useEffect(() => {
if (subscribe) {
const unsub = onSnapshot(query, (doc) => {
getQuery.refetch()
})
return () => unsub()
}
}, [subscribe])
return getQuery
}`


Feature/materialrecipes

Description
Added all the material item recipes (that I could find).
Didn't do any recipe with a block as result.
Some items are still missing (like tools) and will need a recipe add a later date.
Checklist:

[x] My code follows the style guidelines of this project (.editorconfig, most IDEs will use this for you)
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Yep, all good for merge if there's nothing else


Cluster Scoped KubeArmor Security Policy

Feature Request
Short Description
As a User, I want to apply a policy which is applicable across cluster where I should be able to mention exclusions.
Is your feature request related to a problem? Please describe the use case.
Need to write policies for each namespace manually
Describe the solution you'd like
Create a new CRD with ClusterKubeArmorSecurityPolicy. Example Policy:
apiVersion: security.kubearmor.com/v1
+kind: ClusterKubeArmorPolicy
metadata:
  name: ksp-block-cis-tmp-no-exec
  namespace: default
spec:
  tags: ["MySQL", "CIS"]
  message: "Alert! mysql history file access denied!"
  selector:
+    exclude:
+         namespace:
+          - kube-system
+          - kubearmor
  process:
    severity: 1
    matchDirectories:
    - dir: /tmp/
      recursive: true
    action: Block

Describe alternatives you've considered
Manually create for each namespace

Can I work this on this issue?


Update README.md (Streamlit UI clarifications)

Introduction
To contribute code to the Pathway project, start by discussing your proposed changes on Discord or by filing an issue.
Once approved, follow the fork + pull request model against the main branch, ensuring you've signed the contributor license agreement.
Context

How has this been tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature or improvement (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Related issue(s):

Checklist:

[ ] My code follows the code style of this project,
[ ] My change requires a change to the documentation,
[ ] I described the modification in the CHANGELOG.md file.

Closes #75

Already merged with d69a192 via copybara.


Add pagination to the page revisions view

Will help organize and allow scale for high-revision count scenarios such as that in #3633.

This would definitely be beneficial where I'm at. I suspect this woudl be for many.


Feature Request

Please pull the Event Log collection out of the Auth trace section and capture them all the time.

I see this was implemented, closing request. Thank you!


[bug] - Final form arrays poor performance

Describe the bug
You can see when adding/removing steps how janky the animation is. This is due to heavy re-renders and checking by final form
To Reproduce
Add remove how-to step or add a console log during the render method to count
Expected behavior
Minimal renders
Additional context
Common issue, discussion and potential solutions:
https://github.com/final-form/react-final-form-arrays/issues/22
https://github.com/final-form/react-final-form/issues/336
https://github.com/final-form/react-final-form/issues/190
https://codesandbox.io/s/32r824vxy1

Any update on this?
The performance is very poor. I removed all the fields except the array field (with just two sub fields) and it is still the same.

As a quick update, 3 months later and issues still open but some people say that latest versions should add some improvement. We are stuck on v3 so it would be worth somebody testing whether upgrade to v6 can be done without breaking too much!


Heading Consistency

Trivial change to match other headers (noun describing what is done rather than the agent doing it).

CI gfxreconstruct build queued with queue ID 8092.


added test to add label on etcd cluster services

When creating Etcd clusters, we want to be able to differentiate the peer service and the client service using labels.
The main reason is that Prometheus-Operator can't easily differentiate on service names, only on labels.
This PR is adding a specific label that tels the peer service can be used to scrape metrics.

poor @etcd-bot, all alone managing the PRs 🤖


Poor Result when avoiding a polygonal curve

Thanks for your great tool
I'm drawing text labels next to specific points along a curve.
I'd like to avoid collisions between text-boxes but also with the curve itself. Unfortunately passing the curve points in x and y results in a clearly non-optimal solution. The bottom label crosses the line and other labels seem to be quite far from their expected target position.
I've also tried "adjustText" (https://github.com/Phlya/adjustText/issues/173). Your solution seems to work better, but still not perfectly suited.
Question: Am I using textalloc in a incorrect way? Or should I implement a custom solution?
ta.allocate_text(plt.gcf(), plt.gca(),
                 list_x, list_y,
                 list_text,
                 x_scatter=x_peaks, y_scatter=y_peaks,
                 textsize=8,
                 textcolor="b",
                 x_lines=[curve_x], y_lines=[curve_y],
                 max_distance=0.1,
                 min_distance=0.012,
                 margin=0.01,
                 linewidth=0.5,
                 nbr_candidates=1000,
                 draw_lines=True)

Hi, your usage looks correct to me, and it should definitively work for your scenario. Without all your code it is a bit difficult to find the reason for why it looks completely wrong, but I suspect it could be related to setting aspect_ratio, transforms and/or plotting on an image, which I'm having issues with and will try to solve when I can find the time (https://github.com/ckjellson/textalloc/issues/13, https://github.com/ckjellson/textalloc/issues/17).
Have you set the aspect ratio yourself, used a transform in previous calls, or done anything with images in the plot?
Created an example which works for me at least:
import textalloc as ta
curvex = [1,2,3,4,5,4,3,4,5,6,7,8,9]
curvey = [0,3,6,4,7,8,9,9,6,4,3,2,5]

fig,ax = plt.subplots()
ax.plot(curvex, curvey)
ta.allocate_text(plt.gcf(), plt.gca(),
                 curvex, curvey,
                 ["testingtesting" for _ in curvex],
                 textsize=8,
                 textcolor="b",
                 x_lines=[curvex], y_lines=[curvey],
                 max_distance=0.15,
                 min_distance=0.012,
                 margin=0.01,
                 linewidth=0.5,
                 nbr_candidates=1000,
                 draw_lines=True)

Your example looks great!
I'll generate a snippet to reproduce the error

Here's a minimal reproducible example (With the JSON data).
Indeed, I'm calling plt.axis('equal') and plt.gca().invert_yaxis() which seem to perturb your code.
It works perfectly fine without these calls.
For the Y-inversion I can easily transformed the Y values directly.
import json
import matplotlib.pyplot as plt
import textalloc as ta

path = "data/test.json"

with open(path, encoding="utf-8") as f:
    data = json.load(f)
    curve_x = data["curve_x"]
    curve_y = data["curve_y"]
    list_x = data["list_x"]
    list_y = data["list_y"]
    list_text = data["list_text"]

plt.plot(curve_x, curve_y, color="r", lw=2)
plt.plot(list_x, list_y, '^', color="g", markersize=10)

ta.allocate_text(plt.gcf(), plt.gca(),
                 list_x, list_y,
                 list_text,
                 x_scatter=list_x, y_scatter=list_y,
                 textsize=8,
                 textcolor="b",
                 x_lines=[curve_x], y_lines=[curve_y],
                 max_distance=0.1,
                 min_distance=0.012,
                 margin=0.01,
                 linewidth=0.5,
                 nbr_candidates=1000,
                 draw_lines=True)

# plt.axis('equal')
# plt.gca().invert_yaxis()

plt.show()

test.json

Great, then there doesn't seem to be any new problems, so I will try to  find time to solve the aspect ratio issues. Hope you can make it work well enough in the mean time!
By the way, I noticed your code takes multiple seconds to finish and it's probably because there are so many line-segments in the polygon. You could probably decrease nbr_candidates (to 50-100) and instead play with max_distance, min_distance, and margin to get what you want much quicker.

Great
I used a really a high value for nbr_candidates just to make sure it wasn't the source of imprecision. I'll decrease it and play with max_distance, min_distance, and margin
Thanks :)

@ckjellson
I've just tested decreasing the number of candidates to 100 and it crosses the polygon.
Since performance is not an issue, I'll stick to a large number!
nbr_candidates=100:

nbr_candidates=1000:

Alright, I think it is an effect of setting a very low min_distance while the text-strings are long, making the nearest candidates untenable. In other words increasing the min_distance could help.
Additionally, I believe that the aspect ratio issues are finally solved as well!

Ok I see! :+1:
Unfortunately, adding the  ha='center' to the kwargs isn't correctly handled (eventhough it doesn't change the actual bbox around the text). And plt.axis('equal') and plt.gca().invert_yaxis() are still not handled correctly as well :thinking:
with  ha='center':

plt.axis('equal') or any other aspect, and also plotting on images now works, you just have to run it before allocate_text.
The aspect ratio fix did not solve the issues with invert_axis and ha="center" as you say, so I'll reopen this issue and see what can be done.

Moved to using display coordinates and added support for the ha-argument, so both plt.gca().invert_yaxis() and ha="center" should now work. Please let me know if you are still having issues!

Thanks!!
Unfortunately I'm currently on vacation and won't have access to my laptop until the end of the week. I'll test it on my data once I'm back :)

Thanks, plt.axis('equal')  and ha=center work great!
but the lines are not correctly drawn when plt.gca().invert_yaxis() is called. I'll flip my Y coordinates manually beforehand

Did you run plt.gca().invert_yaxis() before or after the call to textalloc? For me it works perfectly as long as all transformations of the plot have been performed before the call to textalloc.

You're right, sorry :+1:


Possible unused dependency blocking upgrade to python 3.11

Description of Issue
I've just been trying to get this twint fork running on python 3.11, but was coming up against issues installing the requirements, as cchardet doesn't have compatibility for 3.11 (see this issue). There's a fork linked in that thread which is compatible with 3.11, but when I went looking through the twint code for any instances of cchardet I couldn't find anything - it doesn't seem to be imported or referenced anywhere other than the requirements.
Unless I'm missing something, it might be worth removing it as a requirement for the sake of onward compatibility (and the nice performance boost from 3.11!).
I've done some basic tests on my own build and had no issues with removing it, although as it's an encoding library and these were only English language tweets it's perhaps worth some testing with other languages too.
Environment Details
Running in a venv with python 3.11, on macOS Monterey 12.6.1

@M-C-Sec Thanks for your report.
I agree with your opinion and I'll remove cChardet from requirements.
cChardet was added at db08c90502a99361877b85c51739f7906cc0c971 but it seems cChardet has never been imported as you say.


Reporting/Get-Archive-Backlog.ps1 prevents clean run with Params

What happened:
Typo on top of Reporting/Get-Archive-Backlog.ps1 prevents clean run with Params
What you expected to happen:
Not the above :)
How to reproduce it (as minimally and precisely as possible):
Just run it and the result is to ignore params and reflect a failure on the line.
Anything else we need to know?:
It just might be the 4 on the topmost line. Also, the examples and authentication docs need clarification.

I guess we can close this issue now?


Fix RegExp character class compilation on unicode ranges.

JerryScript-DCO-1.0-Signed-off-by: László Langó<EMAIL_ADDRESS>

This bug was found in IoT.js, related issue: https://github.com/Samsung/iotjs/issues/1057

LGTM


Missed styles.css in "dist/cjm/styles.css"

Thank you for good package
I have a project with Next.Js, where we use cjm module configuration.
I got an error

It can be fixed by adding styles.css to dist/csm folder in npm package.

Hi @dkarpov-w . Thanks for making me aware of this! A fix has been published.


Declared "set_full_screen( )" in all supported backends

set_full_screen() is now declared in all the supported backends and has been implemented in the dummy backend. Now, coverage for the window.py can also be increased by implementing tests for set_full_screen in the core module.
PR Checklist:

[X] All new features have been tested
[X] All new features have been documented
[X] I have read the CONTRIBUTING.md file
[x] I will abide by the code of conduct

Although I don't know much about this as well but according to me Window should be the one containing this API as in the case of multi-window applications each window will have the freedom to go to full screen mode independently. Although I also agree with your point that it's the app that ultimately goes to full screen mode but it would be much simpler and most logical to have this API on Window rather than App. In this case we can simply have a check to avoid App going to full screen mode again and again.

The mapping of which window goes on which screen might be something you want to modify, but it's the app as a whole that is put into "full screen" mode. Thoughts?

I'm slightly confused, and have different responses based on what full screen means in context (which I think is understandable considering how many UI contexts toga supports).  Does full screen just mean "maximized window"?  In which case, its obvious that set full screen should be on the windows api.  This makes sense for most desktop operating systems, but is meaningless on most mobile platforms.
Does full screen mean "hide desktop UI elements, and take over the full display"?  then that is obviously an api on the application itself... when you are talking about desktop apps.  for mobile... it's still a little bit meaningless, since, that's pretty much the default state for mobile apps.

@tritium21 "Full screen" in this context means "overtaking the entire display" - as in the way games or a slide deck operates.
Part of that API will need to be mapping windows to screens - so, for example, a slide presentation tool will have 2 windows (the slides, and the presenter notes); if there is a secondary screen attached (a monitor, or a projector), the slides go to the monitor/secondary display, and the speaker notes go to the laptop/primary display.
But, crucially - you can't make one window full screen, and have the other not be full screen. Either the app is in full screen mode, or it isn't. This, for me, is why the API belongs on the App, not the window.
And yes - it's meaningless for mobile apps, as they essentially always operate in what is effectively "full screen" mode.

But, crucially - you can't make one window full screen, and have the other not be full screen. Either the app is in full screen mode, or it isn't. This, for me, is why the API belongs on the App, not the window.

... It's been a while since I've had to look, but IIRC Microsoft PowerPoint does just this.  It puts the slides in full screen, but keeps the presenter notes in a normal window.
I know on Windows (the OS), there is a concept of "Windowed fullscreen mode" (gamers are well aware of it for the potential performance boost, but that's besides the point).  It can take over an entire single display (or many displays), from within the windowing system without making lower level calls to take over the hardware.  (You know this is happening usually because starting a game doesn't mess with your second monitor or flash the screen to black, and your desktop icons are exactly where you left them before you started the application, not that I'm bitter or anything).  When an application does this, it can still spawn regular windows on secondary (and tertiary, etc.) displays.
I have no idea how that concept maps onto GTK or OSX.  It's also possible that it sufficiently complicates the code of Toga to support that model, so on those basis, I agree that fullscreen is a concept best mapped to the application, not the window.

@tritium21 Thanks for that Windows platform detail - that's good to know.
However, as you say, it doesn't ultimately change the conclusion - it's an API that still makes sense at the application level. Applications know what windows they have, and which "screens" that are available, so "App.go fullscreen()" is a call to that needs to tell window 1 to go to screen 2, and window 2 to screen 1, and window 3 does nothing - which on macOS would mean it can't be seen, and on Windows would mean you might be able to see it on a third monitor if you had one.

So, finally according to the discussions, we should migrate the full_screen property to App API and implement the logic accordingly. Right?

@Axle7XStriker Correct

Does this look fine or do I need to make some other changes as well to complete the migration process?


import View and Button from react-native

When add new Sceen, the sample use 'View' and 'Button', but the code didn't notice user to import them.
It will be crash when running. Especially for the novice, it will cost time to find the problem.

If you follow the guide from top to bottom, a set of imports is already documented.
So I think this change would be redundant.

Yes, you're right. init app has imported 'View', but no 'Button'. like this:
import {
  AppRegistry,
  StyleSheet,
  Text,
  View
} from 'react-native';


It seems that this software does not support the latest Animal Crossing: New Horizons V2 05, because your other project is set to read-only. You can only be contacted here.

Hello, I don't know why your other project seems to be set as read-only, but this matter is very important. I can only disturb you here. Sorry. Use ACHN port R18 At 8:00, the game version was 2.05. The functions of this software could not be used and displayed garbled codes, including the inability to modify the vegetable price, the inability to read and place items on the map, the inability to modify the time in the game, the inability to read residents, character names, item columns, etc.Please look at the picture below.I use machine translation, so the language is not very accurate.

Yes, the old version does not work.
Please update.


[TypeScript Resolvers] defaultMapper: any doesn't work anymore

Describe the bug
If you set the property
generates:
  src/generated/graphql.ts:
    config:
      defaultMapper: any

any is not used for non mapped (return) values. Instead it uses the generated type.
Behavior described here:

Every other, not mapped type follows the default convention, so in order to overwrite it you can use the defaultMapper option

https://graphql-code-generator.com/docs/plugins/typescript-resolvers#mappers-overwrite-parents-and-resolved-values
To Reproduce
Add defaultMapper: any to config and generate code.
Expected behavior
For every type not specified in the mapping config, it should take any as the value and not the generated type
Environment:

OS: Mac OS
Codegen: 1.0.2
Node: 10.15.0

Fixed in 1.0.3


chore: Add create_volume to swagger docs

Added a utoipa::path to the create_volume handler
Updated flake so postgres works in NixOS
Replaced ucan path dependencies with actual UCAN versions (@blaine this would still cause a runtime error, right? What's the github URL that I could depend on?)

Hm. We need a way to run kubo during tests.

Replaced ucan path dependencies with actual UCAN versions (@blaine this would still cause a runtime error, right? What's the github URL that I could depend on?)

Yeah, it's because the ucan:* "unscoped" bug in rs-ucan will result in proof chain validation failure. The "fix" I put in the vendored version was here: https://github.com/blaine/rs-ucan/tree/temporary-unscoped-fix (just a one line change), and I'm actually not sure the benefit of having a separate type for unscoped ucan: URIs so this may be the best overall fix (plus deleting related code)?
Anyhow, it's just on validating volume changes that things will fail until that issue gets resolved, or we can use a different resource (e.g. https://{domain}/api/account/{username}/*) instead of ucan:*

Ah - sorry for the huge diff in flake.nix. I actually have a nix formatter installed.

Hm. We need a way to run kubo during tests.

Might make more sense to just mock for CI?
Either way, can we get this merged so it's easier to build & run and work on a kubo testing strategy in a different PR?

Yeah, let's merge.


[SSOC] New Project In Place of COMING SOON!!

I want to add a new project in the place of coming soon.

The project is a job listing web app. The users also have the option to add new jobs. Users can also search jobs via country, state, job company, job requirements, etc.
I have built this project using only HTML , CSS and JavaScript. This is a great learning for people who thinks we can only add new jobs via backend technologies. This project helps in exceeding the limit of the developer and is a great learning project.
Please assign me this issue so that I can add this project and add my contribution to this community.

I would like to work on this issue under SSOC 2.0


kinematic mappings

update get_kinematics to output cursor in 3d and add an option to output hand coordinates in world (x: right, y:up, z:forward) coordinates instead of what they currently are (random according to where they came from)
also add functions to get mappings (either fixed or incremental) in the world coordinate system

ok i think i changed everything we talked about

I revised the docstring a little because I think my earlier comment was too vague and it was just easier to directly change it! Does it make sense?


Package the bots as a docker image

Published: https://github.com/kleros/kleros-v2/pkgs/container/kleros-v2-bots


Don't use floats when dividing the partitions

Also modify the test so plen % clen != 0 (so the ceil logic is tested)
@wvanbergen

:cool: :+1:


[Discussion] - json-schema builder

This is a very obvious use-case and I'm sure it has been discussed at some point, so my apologies if this is a duplicate issue/discussion. (BTW: is there a discussion group somewhere for this project?)
So here's the question to stem the discussion:
Has anyone attempted feeding the json-schema schema into ASF yet, in order to build a form that is capable of creating a json-schema?

This question has been asked many times, and the upfront limitation is the support of $ref, oneOf, anyOf and allOf... etc. They planned "this fall" and "soonish", not sure how it goes tho.

Someone started planning a schema builder asking for feedback on features, can't remember who, but there is a repo someone started for it. Sorry to be so vague, don't have time to look it up now.

Hi guys,  built a simple implemention of the builder. I would love to get feedback. http://ralphowino.github.io/schema-form-builder

@rowino I believe Nicklas just invited you to our Gitter, we are more than interested in what you have done, please join us in Gitter :)

I'm closing this issue as @vicary has really answered the issue, although I will add that there is a link to our Gitter group from the main page https://gitter.im/json-schema-form/angular-schema-form, see you there @ryedin  :)


Drop checksumFeed

From reading, this shouldn't break demo loading for demos recorded before this commit. This changes the netcode however, so this PR is against 0.54.0/sync.

lgtm. Seems like it is a remnant of the old FS code. we don't use it anymore so it can be safely deleted.


datetimeindex resample issue

Hi- I am observing odd behavior when trying to use resample on an uneven datetimeindex. See the below code to reproduce:
import pandas as pd
import numpy as np

bug_datetimeindex = pd.date_range('2013-12-30', '2014-01-07')
bug_datetimeindex = bug_datetimeindex.drop([ \
pd.Timestamp('2014-01-01'), \
pd.Timestamp('2013-12-31'), \
pd.Timestamp('2014-01-04'), \
pd.Timestamp('2014-01-05')
])
temp_df = pd.DataFrame(index=bug_datetimeindex, data=np.random.randn(len(bug_datetimeindex), 2))
temp_df.resample('B')

throws up a ValueError: Length mismatch: Expected axis has 5 elements, new values have 7 elements
Using asfreq() does not throw up this error on my machine.
I am running pd 0.17.1 on Python 3.4.4. off Anaconda for Windows.

this was just fixed in master (it broke 0.18.0rc1 as well), see the issue here.
so 0.18.0 will release soon


Feature/297 check test codes for signature working

Closes #297

This PR fixes signature related unit test issues with most of the packages.
The following ones still have issues for @tahpot to investigate:

[ ] account-node
[ ] client-ts
[ ] storage-link
[ ] verifiable-credentials

All the tests pass, however there is an issue with SBT tests.
I suspect mintedTokenIds and burntTokenIds needs updating.
This is approved, subject to the SBT tests being fixed by @ITStar10 .


Add link to changelog next to version number (Tested Working)

PR Checklist

Please check all that apply to this PR using "x":

[x] I have checked that this PR is not a duplicate of an existing PR (open, closed or merged)
[x] I have checked that this PR does not introduce a breaking change
[ ] This PR introduces breaking changes and I have provided a detailed explanation below

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting)
[ ] Refactoring (no functional changes)
[ ] Documentation changes
[ ] Other - Please describe:

Fixes
Issue Number:
What is the current behavior?
Nothing
What is the new behavior?
Added a link to the changelog that takes you to the page on GitHub with the whole changelog.
Other information

I tested it by running from source on Linux Ubuntu 20.04 and it shows everything correctly and the link works properly.

Great idea!


Overflow crash

This issue can be reproduced ONLY when compiling the CLI in Debug; it does NOT occur when compiling the CLI in Release.
Run
$ cargo build -p cbor-diag-cli

then run
$ echo a300470128bf0000002c01c11a62978f4d02a100820400 | ./target/debug/cbor-diag --to diag
thread 'main' panicked at 'attempt to subtract with overflow', src/encode/diag.rs:42:42

The CBOR diagnostic notation of the hex string is
{
    0: h'0128bf0000002c',
    1: 1(1654099789_2),
    2: {0: [4, 0]},
}

The crash occurs because the len variable is hardcoded to 4 and the max parameter given to the estimate() function is less than 4, overflowing the unsigned subtraction max - len.
Thanks a lot for making and sharing this library!

Thanks for the report. The reason it only crashes in debug builds is that -C overflow-checks is only enabled by default in them (so in release it underflows and I think just wastes time estimating the length far in excess of the max allowed length, but still should behave correctly).
Looks like it should be a simple fix of switching to saturating_sub throughout the estimation code. I should be able to get that fixed tonight.


Local Reading Cache

Add a cache so if the device does not have a network connection, it can store the data locally until one becomes available.

This has been implemented.


UI: Radio Buttons

It would be nice to have alternate styles for radio buttons added to the UI section

Only a year and a half late. Hows this:
How's this?
http://codepen.io/dbox/pen/bdEgoQ/?editors=110
The mixin has to be called on the label.
Let me know what you think. I can easily do a pull request to add the mixin, but writing the test for this one might be hard for me.

Woah, this looks great! Love the ones on the left especially. Would love a pull request for those ones, if possible!

It's all the same mixin. Left would be default, then you can pass options
for the others. Shaded, etc.
I'll do a pr. Will let you know if I need help with tests.
On Sat, May 9, 2015 at 11:08 AM Jeff Escalante<EMAIL_ADDRESS>wrote:

Woah, this looks great! Love the ones on the left especially. Would love a
pull request for those ones, if possible!
—
Reply to this email directly or view it on GitHub
https://github.com/jenius/axis/issues/109#issuecomment-100510771.

Ah ok. Really no need for all that at the moment, we could just start with the simplest one. Axis doesn't aim to do full styling, just provide a quick simple base for you to build on and customize :grinning:
That would also make it easier to test and implement!

So pass main selected color at least? Or nothing?
On Sat, May 9, 2015 at 12:06 PM Jeff Escalante<EMAIL_ADDRESS>wrote:

Ah ok. Really no need for all that at the moment, we could just start with
the simplest one. Axis doesn't aim to do full styling, just provide a quick
simple base for you to build on and customize [image: :grinning:]
That would also make it easier to test and implement!
—
Reply to this email directly or view it on GitHub
https://github.com/jenius/axis/issues/109#issuecomment-100518072.

Yeah having color as an option sounds great!


add support for composite types

Support for migrating composite types in the format of:
"CREATE TYPE ... AS (...)"
I haven't found the time to add tests yet, would be nice if someone could add those.

Well actually you cant "CREATE OR REPLACE" a Type. You have to remove it and create it again.

Well actually you cant "CREATE OR REPLACE" a Type. You have to remove it and create it again. Or alter it

You are right. CREATE OR REPLACE doesn't exist for types. But removing and re-adding it is not an option here because the whole point of migrations is that you don't lose your references. You'd need to set CASCADE and that would delete all functions and tables referencing your type.
Instead we need to run ALTER TYPE to update the type accordingly (drop, change or add attributes themselves).
My next commit will propose a possible solution.

My implementation only checks if the regtype of the type in the db and the defined one are the same, not the regmod. That is because the system function in postgres needed for checking this is only added in version 17: https://www.postgresql.org/docs/17/functions-info.html (to_regtypemod)
How does this project handle compatibility? Should the code be compatible with <17 and >17 (with a different implementation) or only >17 or is it fine if it's not "perfect" but compatible with all versions (the way I implemented it right here)?
I also noticed that the definition retrieved from the database might rename types using their alias. For example if you define an attribute using type VARCHAR, the retrieved type from the db is character varying making the definition different. Does anyone have any suggestion on how we could fix this? Right now I just ignore that fact so if you create a type that uses a type "VARCHAR", it will always detect the attribute as having a changed type.

thanks for opening this but we're unlikely to support any new entities that do not support create or replace directly
I'd recommend using op.execute("...") for managing your composite types


AudioCueEditor Yakuza 5 fighter voices don't work

When trying to open fighter voices from Yakuza 5 Remastered, the tool throws an error:
"cannot get command at index 0 on SynthParameterPallet because it is out of range."
Log file: ace_log.txt
This doesn't happen with fighter voices from other games on the same engine or a few other acbs from 5 that I tried.
I've attached a few example acbs.
sound.par.unpack.zip

Looks like an issue with the implementation for ParameterPallet values in the last update. Those ACBs are an older version that don't even have that value and ACE is setting it as the default value (0).

Fixed in 0.8.2


Support for Unity

Hi. I want to leverage yaml-rust to open, modify, and save Unity scene files. Out the gate I've hit multiple issues.
1. Can't parse common scene files.
This is due to the error: mapping values are not allowed in this context at line ### column ##
Scene files frequently contains lines such as this: --- !u!114 &137567736 stripped
This is apparently a common issue. This may be invalid YAML. I'm not sure.
2. Missing tag support
Unity makes heavy use of document tags. If yaml-rust can load a unity scene file then emitting it back out drops all of the document tags. This is a catastrophic failure.
--- !u!29 &1
3. Different emitter style
Unity's YAML is compact.
m_LocalPosition: {x: 0, y: 3, z: 0}
yaml-rust is not.
m_LocalPosition:
    x: 0
    y: 3
    z: 0

Number 1 may be invalid YAML syntax, in which case it should probably be handled separately and more explicitly. But #2 and #3 seem like they should be correct to fix?

Disclaimer: not a maintainer.
If you already enumerate different points of incompatibility, maybe it makes sense to split the issue up. It makes much more sense to track the individual points, imo.

Unity's YAML is compact.
m_LocalPosition: {x: 0, y: 3, z: 0}

This is simply a flow-style map (YAML defines a block and a flow style)

If you already enumerate different points of incompatibility, maybe it makes sense to split the issue up.

I thought about that. Ultimately it’s likely to be a series of issues. The value of each individual did may be minimal. I figured it’s better to start with the real goal (work with Unity) and break it up later if appropriate.


refactor: use observer pattern to play scene

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Using isPlaying to start the scene playing is a bit counter-intuitive: you'd expect it to track the state of the scene, not cause it to start.
My first attempt at fixing this https://github.com/freeCodeCamp/freeCodeCamp/pull/57295 meant we suddenly had to deal with null scenes, which wasn't pretty.
This PR makes use of the observer pattern so that we can keep all the scene state inside scene and allow any component to start the scene playing, via a .notify call. This means we don't have to handle null scene data, except insofar as we don't create the scene component. Also, we can share the SceneSubject with anything that needs to start the scene - at the moment, hotkeys and an on-click listener in Scene.
Also, it should make it easier to implement pausing (ref: https://github.com/freeCodeCamp/freeCodeCamp/issues/55293) since it's easy to extend the subject to notify based on different events.

I couldn't recreate the error, @ShaunSHamilton, but I did find another bug: it was possible to start multiple scenes running at once. I fixed that simply by ignoring multiple play requests. Not the most elegant solution, but it seems to work.

Where do we do that?

Exam Environment app.

@ShaunSHamilton no rush, but I've not been able to reproduce the error. If it still happens for you, let me know.

I was able to reproduce this on firefox, not chrome or safari.

Thanks, Tom. Same steps as Shaun?

yup. Load the first dialogue and press the play hotkey before it's loaded.


Remove the logging module

In GitLab by @arisilon on Nov 22, 2019, 15:20
This module offers very little advantages over the standard Python logging module since it added a QueueHandler in 3.2.

In GitLab by @arisilon on Jan 5, 2021, 19:30
mentioned in commit 3e9454ed31632f27323211f2b75224232f2eb017


doesn't expand on enter on a newly opened go file

test case:
$ go mod init test
$ touch main.go
$ nvim main.go
try to select package main from the menu
like

it goes to the next line instead of selecting the item
nvim-cmp config:
local cmp = require "cmp"
local lspkind = require "lspkind"
local keymap = require "cmp.utils.keymap"
local map = cmp.mapping

cmp.setup {
	snippet = {
		expand = function(args)
			vim.fn["vsnip#anonymous"](args.body)
		end,
	},

	mapping = {
		["<C-k>"] = map.select_prev_item(),
		["<C-j>"] = map.select_next_item(),
		['<C-e>'] = cmp.mapping.close(),

		["<Tab>"] = map(function(fallback)
			if vim.fn.pumvisible() == 1 then
				vim.fn.feedkeys(keymap.t "<C-n>", "n")
			elseif vim.fn["vsnip#available"](1) == 1 then
				vim.fn.feedkeys(keymap.t "<Plug>(vsnip-expand-or-jump)", "")
			else
				fallback()
			end
		end, {
			"i",
			"s",
		}),

		["<S-Tab>"] = map(function(fallback)
			if vim.fn.pumvisible() == 1 then
				vim.fn.feedkeys(keymap.t "<C-p>", "n")
			elseif vim.fn["vsnip#available"](-1) == 1 then
				vim.fn.feedkeys(keymap.t "<Plug>(vsnip-jump-prev)", "")
			else
				fallback()
			end
		end, {
			"i",
			"s",
		}),
	},

	sources = {
		{ name = "nvim_lsp" },
		{ name = "buffer" },
		{ name = "vsnip" },
		{ name = "path" },
		{ name = "emoji" },
	},

	-- preselect = cmp.PreselectMode.None,

	completion = {
		completeopt = 'menu,menuone,noinsert',
	},

	formatting = {
		format = function(_, vim_item)
			vim_item.kind = lspkind.presets.default[vim_item.kind] .. ' ' .. vim_item.kind
			return vim_item
		end,
	},
}

autopair config:
local npairs = require "nvim-autopairs"
local npairs_cmp = require "nvim-autopairs.completion.cmp"

npairs.setup {
	check_ts = true,
}

npairs_cmp.setup {
	map_cr = true,
	map_complete = true,
}

@mortezadadgar You should add the <CR> mapping.
cmp.setup {
  mapping = {
    ['<CR>'] = cmp.mapping.confirm()
  }
}

@hrsh7th autopair doesn't cover that? it's mentioned in readme

I don't know (it is not nvim-cmp ).
Do you get it working?

@hrsh7th yes but I will loss autopair  mapping on opening new pairs, @windwp do you have any idea

I hope nvim-autopairs does the mapping to . (nvim-cmp handles it automatically.)

@mortezadadgar  please check reamde  you call a cmp setup first than you call my snippet setup  for cmp
@hrsh7th
do you want to add an option to add a ( pair on function method item.
https://github.com/windwp/nvim-autopairs/blob/master/lua/nvim-autopairs/completion/cmp.lua#L28
if you add that i will remove that snippet and only use this code.
 vim.api.nvim_set_keymap(
            'i',
            '<CR>',
            'v:lua.MPairs.autopairs_cr()',
            { expr = true, noremap = true }
        )

so nvim-cmp will handle all another thing.

nvim-cmp handles mappings to <CR> even if they are already defined.
So the pairs-wise plugin just needs to map to <CR> without worrying about nvim-cmp.
(google translated)

@windwp thanks it's working now!

@hrsh7th  yes I know it.
but my snippet provides another feature to map_complete item on function item
https://github.com/hrsh7th/nvim-cmp/issues/14#issuecomment-897493673
if you can add this on nvim_cmp so I will remove that on my plugin and i will remove that map_cr too

@windwp I thought you are using event.on_confirm_done for it. Don't you use it?

Yes, it is working now. but I want to ask do you want to add that feature inside nvim-cmp?
then I will remove my code to do that and of course, I will remove that mapping <cr> on function too.

No. I don't implemente it in nvim-cmp.
I think some features should realize with...

Confirm completion item

It should implemente by cmp.setup { mapping = { ['<CR>'] = ... } }

Fix bracket indentation on <CR>

It should realize by nvim-autopairs.
I think nvim-autopairs should map to <CR> without worrying about nvim-cmp.

Because nvim-cmp care about the mapping that already mapped to the buffer.

Add bracket automatically when confirmed item is function or method kind

It should be realized by nvim-autopairs
It will be use cmp.setup { event = { on_confirm_done = function... } }

https://github.com/windwp/nvim-autopairs/blob/master/lua/nvim-autopairs/completion/cmp.lua
please take a look of that link i didn't do anything special on that i just follow what you are talking above


Property Animations

Adds support for animating style and layout properties.
Example
let animation = cx
    .add_animation(std::time::Duration::from_secs(1))
    .add_keyframe(0.0, |keyframe| keyframe.set_background_color(Color::red()))
    .add_keyframe(1.0, |keyframe| keyframe.set_background_color(Color::blue()))
    .build();

Element::new(cx)
    .size(Pixels(200.0))
    .background_color(Color::red())
    .on_press(move |cx| cx.play_animation(animation));

Animations can also be applied as CSS transitions:
.test {
    background-color: red;
    transition: background-color 2.0 0.0;
}

.test:hover {
    background-color: blue;
    transition: background-color 2.0 0.0;
}

My three main concerns are:

the use of polling to animate. I believe this is excessive and we should have a timer to control animations, pending the timers PR.
we're accumulating a lot of code which is just doing the same thing for each style property. We should maybe consider writing a for_each_style function or macro, or maybe like for_each_animatable_style.
We still need to figure out how to animate something disappearing

Other than that this seems good, and I think these concerns can be deferred to other issues.


chore(main): release uniform 0.15.0

:robot: I have created a release beep boop
0.15.0 (2024-12-29)
Features

add tailwind info color range (061291e)
pixels,uniform: add Table to pixels and fix story of FieldArray (179dd1a)
uniform: big refactoring of fieldArray implementation (cd84a2c)

Bug Fixes

deps: update @nextui monorepo (#647) (aaa6914)
deps: update dependency framer-motion to v11.15.0 (#632) (38246f9)
deps: update dependency react-hook-form to v7.54.2 (#644) (e0a4274)
uniform: add FieldCopyTestIdButton test (31233a8)
uniform: add tests for Form component (ecb4318)
uniform: adjust removeNullishFields to only remove nullish fields from objects (e800345)
uniform: always disable debug in tests (28476a9)
uniform: export useInput hook (d75c8c3)
uniform: fix hooks index file (6875186)
uniform: fixes for FieldArray (1d9bba9)
uniform: more refactoring and fixes for FieldArray (b8514fa)
uniform: refactor Controller tests (add109e)
uniform: refactor nullish fields logic (de92895)
uniform: restructure FieldArray components (cb719af)
uniform: some tailwind variants refactoring of FieldArray (96a135b)
uniform: use useInput from hooks (8c7f6c9)
use v8 for coverage + exclude some code (d2cc6d8)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

uniform-v0.15.0
:sunflower:


about reproduction

Thank you for disclosing your python script!
I want to reproduce your result of technical paper.
In the paper of Table2, you produced four modeles.
I think "config.yaml" on github is for model No 1.
How can I reproduce model No 2,3,4 ?
Best regards

Thanks for your interest! I have uploaded other configuration files. Please refer to reademe/training/other model settings.
Regards,


test: get non friends

write a test that verifies a user's ability to get non friends

closing see #20


octoprint: fix build due to black

This is a quick fix for the build error described in #165323
Signed-off-by: florian on nixos (Florian Brandes<EMAIL_ADDRESS>Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package built:

octoprint

@ofborg eval

Result of nixpkgs-review pr 165389 run on aarch64-darwin 1

1 package built:

octoprint

It would be a much better idea to remove black from whatever it is using instead of using an older version.

Hi @SuperSandro2000
I figured out the dependency on black. The dependency graph looks like this:
  /nix/store/kjrycs7dg6rjpfm292l8067yfvkhqdxq-python3.9-black-22.1.0.drv
  /nix/store/w53810z4gpvzjql74v9vbccr7ax84pgm-python3.9-ipython-8.0.1.drv
  /nix/store/2hic8mycpw8mgym52r6v74vh7dha96bs-python3.9-python-dotenv-0.19.2.drv
  /nix/store/b3daf7cb9jljf16z8ivcrd3vjgjbz4qx-python3.9-Flask-1.1.4.drv
  /nix/store/0nzqh8x8mbnf2jmkx8qqa4h06x37vdlg-python3.9-flask-login-0.5.0.drv
  /nix/store/xypr2mx5ln80rw6svvxf5rk6czljiz23-python3.9-Flask-SQLAlchemy-2.5.1.drv
  /nix/store/zmrdgh08bw0d73f2jpddsxlf7yzz9q8y-python3.9-factory-boy-3.2.1.drv
  /nix/store/nhijyvv8v4xywmlrflhilsxad3mlynsx-python3.9-pytest-randomly-3.11.0.drv
  /nix/store/26dl4ijj969jj91cgsygkkg79g4y28fm-python3.9-httplib2-0.20.3.drv
  /nix/store/jskyy09y8wj4nxbp2f35dxyc0d243fv8-python3.9-Flask-RESTful-0.3.9.drv
  /nix/store/w7hl3n3qykk9sdh1hx4fnl1dlpc18sh4-python3.9-Flask-Limiter-1.4.drv
  /nix/store/w80ja2ls3xg0ghhh0yhc0w3m50is3xy4-python3.9-httpbin-0.7.0.drv
  /nix/store/2bi64wmc89jnc1h7cpqqzazv2ajvl7dd-python3.9-pytest-httpbin-1.0.1.drv
  /nix/store/ppxjx5j6rkyv0klg7n9lvjv808q05sn0-python3.9-uvicorn-0.16.0.drv
  /nix/store/wwbh01qzv1y8gdzm5db0z22c0qdgyhcr-python3.9-httpcore-0.14.4.drv
  /nix/store/z21jndk0anc6dmviq4d1255dfdy0wbz2-python3.9-httpx-0.21.3.drv
  /nix/store/plpsjr2hb8l215kgq7sp6rphsjll1bcc-python3.9-sanic-testing-0.8.2.drv
  /nix/store/h1v56fsx0gb7cj990kbdx0p9glxf7fwp-python3.9-sanic-21.12.1.drv
  /nix/store/2kdigbbkbihiv9ayrrbh4489mma9il3z-python3.9-sanic-testing-0.8.2.drv
  /nix/store/rz8npi2yp2y32f61hknv0bpwv2897d06-python3.9-Flask-Script-2.0.6.drv
  /nix/store/3wh7hnyl2lha8dd6xq69sjyz1wm5hgbd-python3.9-Flask-Assets-2.0.drv
  /nix/store/v4sh28fr316mmqd7yhw5cxvjp0cj6rmq-python3.9-httpretty-1.1.4.drv
  /nix/store/ir6yz3lzg2sw6m4w5cxk1al2cijgfv45-python3.9-adal-1.2.7.drv
  /nix/store/j11bagzr9dxfc2k4q16j6rcs58pd12fh-python3.9-msrest-0.6.21.drv
  /nix/store/j5q7vymfg75q4h8prfkq1c2f78qyxpr4-python3.9-msrestazure-0.6.4.drv
  /nix/store/akpp3k6iyzlkdg1yzv2f5isclg3inq97-python3.9-azure-servicebus-7.5.0.drv
  /nix/store/a82nlbcrk2dhy21h56hn8qkqr5jvjlqd-python3.9-kombu-5.2.4.drv
  /nix/store/nj91kq2m9gmvgwmpjrr0cwnr4y7cja3f-python3.9-Flask-Cors-3.0.10.drv
  /nix/store/l67jki7vm62r3hfrnss9lkvb2rchmfrr-python3.9-moto-3.0.2.drv
  /nix/store/n826jv3f2n8agm0rz1117d4cvlfga03k-python3.9-Flask-Babel-1.0.0.drv
  /nix/store/rn0xkx8ind6gds2864cx0daazb08kaas-python3.9-falcon-3.0.1.drv
  /nix/store/rrpm4cfx4vca6dc2n2cxa2pqgjliq3ii-python3.9-celery-5.2.3.drv
  /nix/store/pqkn1zfhmv9w45whyh6jhxwi9q7bgzlc-python3.9-sentry-sdk-1.5.8.drv
  /nix/store/mwfqc4531zr75ywj054q11xgkld1bwbh-python3.9-OctoPrint-1.7.3.drv

So ipython requires black as a build input.
I think the way forward is to merge  #165328 in order to update octoprint and remove all those old version dependencies.


OrderedImportsFixer - Not configuring the import type sorting still sort by type when using alpha sorting

The comments in the code are telling me that using null for the importsOrder rather than an array is expected to sort all imports together without grouping them by type.
while this seems true for length sorting AFAICT (I haven't tried it to check it), it is not true for alpha sorting, as sortAlphabetically starts by comparing the import type.
So for alpha sorting, null in importsOrder actually enforces array('class', 'const', 'function'), and there is no way to enforce it.
Is it really the expected behavior ? Or just a bug ?

Confirmed;
with fixer sorting alpha and null as order;
Input
<?php
use const some\b\{ConstB};
use const some\b\{ConstA};
use Z\Y;
use Z\X;
use function some\b\{fn_a, fn_b};
use function some\a\{fn_a, fn_b};

Output
<?php
use Z\X;
use Z\Y;
use const some\b\{ConstA};
use const some\b\{ConstB};
use function some\a\{fn_a, fn_b};
use function some\b\{fn_a, fn_b};

and not;
<?php
use const some\b\{ConstA};
use const some\b\{ConstB};
use Z\X;
use Z\Y;
use function some\a\{fn_a, fn_b};
use function some\b\{fn_a, fn_b};

The question is; if no order is defined, how to fix the following;
<?php
use const some\b\{ConstB};
use const some\b\{ConstA};
use ZZ\Y;
use ZZ\X;
use function some\b\{fn_a, fn_b};
use function some\a\{fn_a, fn_b};
use AZ\Y;
use AZ\X;

move the classes from ZZ NS to the end, or move the AZ NS ones above ZZ NS ones?
Or, using another example; if no grouping is used at all, is something like this wanted;
<?php
use const A\b\{ConstB};
use B\A;
use const C\b\{ConstB};
use D\A;
use function E\a\{fn_a, fn_b};

Well, if you don't enable grouping, I would say that the last snippet is acceptable (btw, it is what PhpStorm creates when adding imports automatically).
and if you use length sorting rather than alpha sorting, you indeed end up with a list mixing different types of imports, as grouping is not apply at the sorting level for it.

Alright, all clear what option is missing ATM, thanks :)

currently, alpha + null and alpha + array('class', 'const', 'function') are doing exactly the same (through different code paths).
In the second case, grouping is totally expected (as it was requested). But I think the first case should not apply grouping (making it consistent with the behavior of length + null)

Agreed, however since this configuration option is already released it would be a BC break to change it. I propose to use different option value to get the result.

no, alpha + null shall not do the grouping. if it does, it was wrongly introduced BC breaker and we need to fix it.

This wasn't introduced as BC breaker, alpha + null has always done this grouping AFAIK (as before that the fixer would break on the PHP 7 code (https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1989))

@SpacePossum but then, null does not have the same behavior for length and alpha sorting.
Looks like the PR 1989 decided to always apply grouping.
A solution to keep BC could be to change the default grouping to keep the existing one (forcing people to disable grouping by setting null)


Tooltips on tabs show at incorrect times.

If you command+tab switch to Atom from another application, and your mouse just happens to be on top of a tab (GUI Tab at the top of the screen), then the tooltip appears showing the file name. This should not be the case. The tooltip should only show if you explicitly moved your mouse onto the tab (or in the tab) and stopped moving on the tab.

Duplicate of this pretty much: https://github.com/atom/atom/issues/10882


Separate handler for :on-timeout?

Hey @danielcompton, I'm wondering if you think there's any merit to adding a separate handler specifically for if the timeout you specify is hit? Happy to submit a patch. FWIW I began using this yesterday and think it'd be useful.

@Samstiles belatedly closing.  wontfix.  We've just updated the README to be clearer about what happens in the case of timeouts.


Move to updated Elixir and Erlang versions

Thanks!
Seems like we have some legit memory failures and I think we might need to exclude 1.4/1.5 for OTP 21.

Yeah memory measurements somehow break... the old scenario from @michalmuskala (that we gladly tested) breaks and so does some simple stuff like:  fn -> Enum.map([1, 2, 3], fn i -> i + 1 end) end
It gets exactly the same heap information before/after... which makes no sense unless this scenario is now optimized/inlined as well:
[
  old_heap_block_size: 0,
  heap_block_size: 233,
  mbuf_size: 0,
  recent_size: 0,
  stack_size: 13,
  old_heap_size: 0,
  heap_size: 220,
  bin_vheap_size: 0,
  bin_vheap_block_size: 46422,
  bin_old_vheap_size: 0,
  bin_old_vheap_block_size: 46422
]
[
  old_heap_block_size: 0,
  heap_block_size: 233,
  mbuf_size: 0,
  recent_size: 0,
  stack_size: 13,
  old_heap_size: 0,
  heap_size: 220,
  bin_vheap_size: 0,
  bin_vheap_block_size: 46422,
  bin_old_vheap_size: 0,
  bin_old_vheap_block_size: 46422
]

(also no memory collected)

In case anyone sees this and thinks wtf they aren't working on this... we are but it's hard and we're scratching all our heads.

Ok the memory measurement problems exist whether we merge this or not... I think we'll skip the problematic tests on OTP 21 until we merge them :)


PARQUET-1517: [C++] Crypto package updates to match the final spec

An initial version of crypto package is merged. This PR updates the crypto code to
conform the signed off specification (wire protocol updates, signature tag creation, AAD support, etc)
improve performance by extending cipher lifecycle to file writing/reading - instead of creating cipher on each encrypt/decrypt operation

@ggershinsky can you add a PR description that summarizes the changes you've made here, for the project changelog?

We went with Revital over these comments, all of them make sense to us, we'll make the respective changes.

Please be sure to run clang-format-7 (using make format) and make lint on the codebase -- it is currently failing lint checks

@wesm , we've addressed your comments. If you're ok with the current version, please merge it, so the staging branch can pick up these 2 new files, upon rebase.


Use nightly version with a specific date

This is needed because the build of arrow2 is broken after this version.
Using nightly with a date is more predictable too.

This should fix the build for #298


⚠ Bofrost.es has degraded performance

In b395d8a, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1316 ms

Resolved: Bofrost.es performance has improved in 5a7c2e9 after 13 minutes.


Vertex AI Experiments - Compare pipeline runs - Notebook review

If you are opening a PR for Official Notebooks under the notebooks/official folder, follow this mandatory checklist:

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[x] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[x] This notebook has been added to the CODEOWNERS file under the Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

Ready to be reviewed. As this PR, the linter code modifies both this notebook and the comparing_local_trained_models.ipynb. Any ideas?

Hi @andrewferlitsch, as I mentioned above, the linter modifies both comparing_pipeline_runs and the comparing_local_trained_models notebooks. But the one to review is only the 1st one. I will resolve all your comments on the 2nd one because I have already implemented in the #852 PR you closed yesterday. And I will resolve conflicts. Thanks

Ready to be merged


Expected Behavior
Naviating from menu to /elements (or any other page) should works, but it generate a link to '/' instead.
Accessing /elements/ directly in webbrowser works, but it's the link generated in the index that fail.
pageRef is correct in menus.en.toml
Steps to Reproduce

install fresh install
yarn run dev
click on element from menu bar
it fails
try by adding /elements/ to url. it works

Code Reproduction URL
No response
Additional Information
No response

I experienced the same behaviour with other sites from the pages folder.
This can be solved by moving files from pages folder up to the language specific content folder.
Worked for me running the command "hugo server".


Restyle coverage viz bottom sidebar error message for consistency.

Description
This is a follow-up to https://github.com/chanzuckerberg/idseq-web/pull/3315.
Jenn made a comment on the design of the error message. Since the issue was blocking the deploy, I moved the re-styling to this follow-up PR.
Before:

After:

Notes

There are enough differences between the other "no data message" and this one that I decided to just duplicate the html markup. The styling is shared between the two instances.

Tests

Verified that the message looks as expected and the styling of other links is unaffected.

Nice! thanks @MarkAZhang!


fix flaky test testClone in TestTaskMonitor

testClone is detected as flaky by NonDex since the origin task monitor and the cloned one are represented as JSON objects, which are in a non-deterministic order. Therefore, I used JSONAssert to check if they are equal instead.

This is just a fork of https://github.com/apache/hbase. I think if you want to contribute to hbase, you should submit a PR there. Before doing so I recommend reading https://hbase.apache.org/book.html#getting.involved


master -> main

Minor change
NO issue for discussion of these changes.
Release checklist

[ ] Authors updated in cf-conventions.adoc?
[ ] Next version in cf-conventions.adoc up to date? Versioning inspired by SemVer.
[ ] history.adoc up to date?
[ ] Conformance document up-to-date?

For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then master always is a draft for the next version.

Thanks, Antonio, looks good to me.

Can this be merged -- or am I missing something here?

It looks ready to merge.


fix: update describe_numeric_pandas.py

fix np.NaN -> np.nan

Hi @sregy ,
thank you for your contribution. Nevertheless this PR is a duplicate of another one that was previously reviewed and approved.
This is great initiative but I do recommend that you check the history of issues , selected backlog for development and more importantly already open PRs so you don't have to invest your time with duplicate developments.


Add Yatopia Related Data

There has been some drama around Yatopia so I figured I'd add some data for the drama generator.

adding yourself is a cardinal sin

@MiniDigger alright. I thought people would find it funny but I removed my self if it's such a big deal.


Transactions stuck/slow on metamask.

Describe the bug
I have been trying to do different transactions on taiko testnet through metamask, and i noticed it takes time before it will eventually  go through and sometimes it will get stuck and i hope the team will attend to this issue in order to enhance a smooth transaction.
Steps to reproduce
Steps to reproduce here.
Additional context
Additional context here.

The problem is from matamask, you need to always click approve before any transaction can go through


can you give me your real dataset  and your utt and label dict? thank you very much

Hi, I am really sorry for the late reply!!! You can apply for the real dataset at https://www.asvspoof.org/database.
Let me know if you have any further questions.


No spaces in sitemap.xml

The v2 docs sitemap at https://v2.docs.influxdata.com/sitemap.xml doesn't have spaces between URLs and timestamps. This might be leading to Googlebot not being able to read it, and some pages not showing up in Google search results and/or their SERP position being lower.
Relevant URLs
https://v2.docs.influxdata.com/sitemap.xml
What products and version are you using?
v2 of our documentation

Everything looks fine in Chrome; I was looking in Firefox when I wrote the above.


add extra jwt header function to encode()

It is required for OpenID Connect Spec of http://openid.net/specs/openid-connect-core-1_0.html#Signing

Thanks!

published v0.4.0


Toggl Desktop Win 7.2.233 : List of projects is empty

When I try to set the project for a task, the only element in the dropdown list is "No project"

Windows 8.1 Enterprise 64bits

Sorry, just saw this is duplicate of issue #1447


Events not getting updated with Firefox

I'm hosting Dashing with Ubuntu 12.04 with nginx 1.4.2, Ruby 2.0.0 and Passenger 4.0.14. It works fine otherwise, but the widgets don't update with Firefox, although they do with Chrome. Firefox console shows messages "Connection opened" and milliseconds after that, "Connection error". Checking /events with curl shows that it gets updated correctly, which is also evident as Chrome is displaying updates normally.
I've tried adding these lines to nginx configuration, as someone suggested they could help the server sent events work:

proxy_set_header Connection '';
proxy_http_version 1.1;
chunked_transfer_encoding off;

But it doesn't help.  Thanks for Dashing though, it is very cool a framework.

Same trouble here. +1

CentOS 6.6, Ruby 1.9.3, RubyGems 1.8.29, Puma 2.11.3, and Dashing 1.3.4.
Any word on this?
I am also experiencing these same issues on Firefox and Chrome.
Firefox console:
"Connection opened" open { target: EventSource, isTrusted: true, currentTarget: EventSource, eventPhase: 2, bubbles: false, cancelable: false, defaultPrevented: false, timeStamp:<PHONE_NUMBER>507814, originalTarget: EventSource, explicitOriginalTarget: EventSource, NONE: 0 }  application.js:15007:11
"Connection error" error { target: EventSource, isTrusted: true, currentTarget: EventSource, eventPhase: 2, bubbles: false, cancelable: false, defaultPrevented: false, timeStamp:<PHONE_NUMBER>546253, originalTarget: EventSource, explicitOriginalTarget: EventSource, NONE: 0 }
Chrome console:
Connection opened Eventbubbles: falsecancelBubble: falsecancelable: falsecurrentTarget: EventSourcedefaultPrevented: falseeventPhase: 0path: Array[0]returnValue: truesrcElement: EventSourcetarget: EventSourcetimeStamp:<PHONE_NUMBER>514type: "open"__proto__: Event application.js:15011
Connection error Eventbubbles: falsecancelBubble: falsecancelable: falsecurrentTarget: EventSourcedefaultPrevented: falseeventPhase: 0path: Array[0]returnValue: truesrcElement: EventSourcetarget: EventSourcetimeStamp:<PHONE_NUMBER>529type: "error"__proto__: Event

+1 I'm occasionally seeing this too - any updates?
Once it starts nothing gets updated and the onData/ready functions in the widgets don't appear to be getting executed anymore.