Memory Region and VSA bug fixes

This PR addresses multiple issues

[x]  #266

[x]  #264

[x]  #265

[x]  #263

This fixes #266 and #264, which is great, but doesn't fix #265 since the heap regions are still not showing up in the output anywhere.
I'm not sure why you say this addresses #100 since that's not really related to this and was fixed a long time ago, do you mean #263? With these changes, that is still an issue for indirect_calls/functionpointer/clang:BAP and indirect_calls/functionpointer/clang_pic:BAP (it seems to vary a bit which variations are affected which is why I think it's potentially some sort of non-deterministic iteration-order issue).
For instance, for indirect_calls/functionpointer/clang:BAP I get the following output:
    R29, Gamma_R29 := bvadd64(R31, 32bv64), Gamma_R31;
    stack_13, Gamma_stack_13 := memory_store32_le(stack_13, bvadd64(R29,<PHONE_NUMBER>3709551612bv64), 0bv32), gamma_store32(Gamma_stack_13, bvadd64(R29,<PHONE_NUMBER>3709551612bv64), true);
    assume {:captureState "%000003ee"} true;
    stack_7, Gamma_stack_7 := memory_store32_le(stack_7, bvadd64(R29,<PHONE_NUMBER>3709551608bv64), R0[32:0]), gamma_store32(Gamma_stack_7, bvadd64(R29,<PHONE_NUMBER>3709551608bv64), Gamma_R0);
    assume {:captureState "%000003f6"} true;
    R8, Gamma_R8 := zero_extend32_32(memory_load32_le(stack_18, bvadd64(R29,<PHONE_NUMBER>3709551608bv64))), gamma_load32(Gamma_stack_18, bvadd64(R29,<PHONE_NUMBER>3709551608bv64));

You can see the last two accesses clearly have the same index but they are incorrectly given different stack regions.
There is still an issue issue with the VSA (same as the one here which has only been partially fixed: https://github.com/UQ-PAC/BASIL/issues/264#issuecomment-2467354520) for the following cases:

correct/basic_lock_read/gcc_pic:BAP
correct/initialisation/clang_pic:BAP
correct/initialisation/gcc_pic:BAP

For correct/basic_lock_read/gcc_pic:BAP, the relevant parts of the .bir are below.
000002fe: R0 := 0x10000
00000305: R0 := mem[R0 + 0xFD8, el]:u64
0000030c: R0 := pad:64[mem[R0, el]:u32]
00000312: #4 := 31:0[R0] - 1

The address 0x10FD8 points to the address of z (0x11018), so after %00000305, R0 == 0x11018 and after %0000030c R0 is equal to the value stored at z. The issue is on the second iteration of the analyses( which uses the VSA results) at %00000312, the VSA incorrectly has that R0 == 0x11018 which is not correct.

All good, it's very close to being all fixed!

@l-kent I think the latest commit should address most of the issues. I will work on merging main into this branch

I can handle merging it, I'll look at that now.

This most recent set of changes has introduced a lot of regressions, so it's not suitable for merging.

Unit tests?

You can run MemoryRegionSystemTestsBAP and MemoryRegionSystemTestsGTIRB to see. Before yesterday's changes, only these tests were failing in MemoryRegionSystemTestsBAP, since you had fixed most of the outstanding issues by early last week:

correct/basic_lock_read/gcc_pic:BAP
correct/initialisation/clang_pic:BAP
correct/initialisation/gcc_pic:BAP

With the most recent changes, now all of the following tests fail:

correct/basic_arrays_write/gcc:BAP
correct/basic_arrays_write/gcc_pic:BAP
correct/basic_function_call_reader/clang_pic:BAP
correct/basic_lock_read/gcc:BAP
correct/basic_lock_read/gcc_pic:BAP
correct/basic_lock_security_read/gcc_pic:BAP
correct/basic_lock_security_write/clang:BAP
correct/basic_lock_security_write/clang_pic:BAP
correct/basic_lock_security_write/gcc:BAP
correct/basic_lock_security_write/gcc_pic:BAP
correct/basic_sec_policy_write/clang:BAP
correct/basic_sec_policy_write/clang_pic:BAP
correct/basic_sec_policy_write/gcc:BAP
correct/basic_sec_policy_write/gcc_pic:BAP
correct/ifbranches/gcc:BAP
correct/initialisation/clang_pic:BAP
correct/initialisation/gcc_pic:BAP
correct/using_gamma_conditional/clang:BAP
correct/using_gamma_conditional/clang_pic:BAP

I'll have a look at why these are failing.

There seems to be a bug in the stack identification. In most of these cases the issue is that there is no region identified for the first stack access.
The only exceptions are the following two cases, which are still partially bugged as described in #264:

correct/initialisation/clang_pic:BAP
correct/initialisation/gcc_pic:BAP

The issue is that there is an inconsistency between the GRA results and the MMM's dataMap. This is caused by the GRA creating incorrect regions that override the correct regions in the MMM.
These incorrect regions are of size 1 and created through this call:
https://github.com/UQ-PAC/BASIL/blob/1185796a6c753212373600593517d896cb604e5b/src/main/scala/analysis/GlobalRegionAnalysis.scala#L167

For correct/initialisation/clang:BAP, the main problem happens when that line is called for the line %00000371. The relevant parts of the .bir are below:
00000305: R9 := 0x10000
0000030c: R9 := mem[R9 + 0xFC8, el]:u64

0000036b: R8 := pad:64[mem[R9, el]:u32]
00000371: R8 := pad:64[31:0[R8] + 3]

0x10FC8 contains the value 0x11040, which is the address of the global variable a. At %00000371, R8 is equal to the contents of a, but tryCoerceIntoData evaluates it as 0x11040 instead, so the GRA incorrectly creates a new, non-existent region of size 1 with address 0x11043 (69699 in decimal) which overrides the correct region with 0x11040 as they overlap.

tryCoerceIntoData evaluates R8 at %00000371 incorrectly because that is the result the VSA gives.

The heap identification doesn't seem to be working in all cases yet, but it's a start at least.
For malloc_with_local/clang:BAP, these are the relevant allocations and heap accesses in the .bir file:
0000038f: call @malloc with return %00000391

000003a3: call @malloc with return %000003a5

000003cc: mem := mem with [R9] <- 7:0[R8] // heap access to location allocated at malloc 0000038f

000003e0: mem := mem with [R9, el]:u32 <- 31:0[R8] // heap access to location allocated at malloc 000003a3

000003ee: R1 := pad:64[mem[R8]] // heap access to location allocated at malloc 0000038f

0000040f: R1 := pad:64[mem[R8, el]:u32] // heap access to location allocated at malloc 000003a3

Currently, %000003cc and %000003e0 are correctly identified as heap accesses (to separate heap locations), but %000003ee and %0000040f are incorrectly identified as stack accesses.

For correct/initialisation/clang:BAP, the main problem happens when that line is called for the line %00000371. The relevant parts of the .bir are below:
00000305: R9 := 0x10000
0000030c: R9 := mem[R9 + 0xFC8, el]:u64

0000036b: R8 := pad:64[mem[R9, el]:u32]
00000371: R8 := pad:64[31:0[R8] + 3]

0x10FC8 contains the value 0x11040, which is the address of the global variable a. At %00000371, R8 is equal to the contents of a, but tryCoerceIntoData evaluates it as 0x11040 instead, so the GRA incorrectly creates a new, non-existent region of size 1 with address 0x11043 (69699 in decimal) which overrides the correct region with 0x11040 as they overlap.

Hi @l-kent I am exploring correct/initialisation/clang_pic:BAP, can you please give me some clues as to why this example does not verify even after the latest changes that do not create that non-existent region?

There is still an inconsistency between the GRA result and the MMM dataMap - the dataMap now has no region with address 69696 (there should be one of size 4) at all, but the GRA result has a region with address 69696 and size 8.

I haven't figured out why that region is missing from the MMM dataMap yet. The size issue in the GRA result is probably related to something being loaded from the symbol table data somewhere. The GRA result is also inconsistent as it (correctly) has a region with address 69700 with size 4, which overlaps the region at address 69696 with (incorrect) size 8.

All the other issues seem to be solved though, which is great.

There is still an inconsistency between the GRA result and the MMM dataMap - the dataMap now has no region with address 69696 (there should be one of size 4) at all, but the GRA result has a region with address 69696 and size 8.

In globals list we have
69696 -> a
and global sizes
a -> 64
which means region 69696 should be of size 8 not 4?

a is an array containing two 32-bit values. We want our regions to be based on the accesses that actually happen in the program.

I tried to merge this in but I can't merge this in without breaking things so I will leave it for another time.

That is okay. This branch doesn't have the change of MemoryLoad as a statement so it is a fair bit of changes. Thanks for trying I will help merge after the demo

I've merged main into this branch and fixed one problem that was my fault but there are still further issues. I've made it throw an exception when the RegionInjector can't find a region in the MMM that should be there.

These are what currently fail:

correct/basic_arrays_write/clang:BAP *** FAILED *** MMM returned region for 69684 with size 1 bytes which does not match requested size 4 bytes
correct/basic_arrays_write/clang_O2:BAP *** FAILED *** failed to find region with address 69684 of size 4 bytes
correct/basic_arrays_write/gcc:BAP *** FAILED *** MMM returned region for 69656 with size 1 bytes which does not match requested size 4 bytes
correct/basic_arrays_write/gcc_O2:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/no_interference_update_x/clang:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/no_interference_update_x/clang_pic:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/no_interference_update_x/gcc:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/no_interference_update_x/gcc_O2:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/no_interference_update_x/gcc_pic:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/no_interference_update_y/clang:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/no_interference_update_y/clang_pic:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/no_interference_update_y/gcc:BAP *** FAILED *** failed to find region with address 69652 of size 4 bytes
correct/no_interference_update_y/gcc_O2:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/no_interference_update_y/gcc_pic:BAP *** FAILED *** failed to find region with address 69652 of size 4 bytes
correct/secret_write/clang_O2:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/secret_write/gcc_O2:BAP *** FAILED *** failed to find region with address 69660 of size 4 bytes
correct/using_gamma_conditional/clang:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/using_gamma_conditional/clang_O2:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/using_gamma_conditional/clang_pic:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/using_gamma_conditional/gcc:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/using_gamma_conditional/gcc_pic:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/using_gamma_write_z/clang:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/using_gamma_write_z/clang_pic:BAP *** FAILED *** failed to find region with address 69688 of size 4 bytes
correct/using_gamma_write_z/gcc:BAP *** FAILED *** failed to find region with address 69652 of size 4 bytes
correct/using_gamma_write_z/gcc_O2:BAP *** FAILED *** failed to find region with address 69656 of size 4 bytes
correct/using_gamma_write_z/gcc_pic:BAP *** FAILED *** failed to find region with address 69652 of size 4 bytes

The issue seems to mostly be with regions loaded from the symbol table being incorrectly deleted or overwritten.

I don't really understand why this is only happening now, but convertMemoryRegions in MemoryModelMap seems to be causing the problems - if a region loaded from the symbol table is not in the GRA result, it is completely removed. We want to keep non-conflicting regions from the symbol table around, and may just need to adjust the size of ones that do conflict?

There are also some issues with stack & heap identification as seen in MemoryRegionTestsMRA but we don't need to fix those right away.

This still fails for the following two cases:

correct/basic_arrays_write/clang:BAP *** FAILED *** MMM returned region for 69684 with size 1 bytes which does not match requested size 4 bytes
correct/basic_arrays_write/gcc:BAP *** FAILED *** MMM returned region for 69656 with size 1 bytes which does not match requested size 4 bytes

The other bug which was causing most of the failures has been fixed though, great!

Thanks for checking Liam. I have got it to pass everything except initialisation/clang_O2 which I will chase
Command: List(boogie, /printVerifiedProceduresCount:0, /timeLimit:10, /useArrayAxioms, ./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl)
./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl(200,5): Error: a postcondition could not be proved on this return path
./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl(145,3): Related location: this is the postcondition that could not be proved
Execution trace:
./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl(157,3): lmain
./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl(200,5): Error: a postcondition could not be proved on this return path
./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl(144,3): Related location: this is the postcondition that could not be proved
Execution trace:
./src/test/correct/initialisation/clang_O2/initialisation_bap.bpl(157,3): lmain


Close to Liquadation, although I gave back my dTokens

I write this for a guy from telegram.
He gave back his loan and nevertheless the vault showed a "Gefährdet" (=in danger close to liquidation).
Is this just a display error?
Or could have been it, that his collateral would have gone in liquidation even if he did pay back his loans?
You can see it in the picture.

Wouldn't be that well if it's a bug 😅
Thanks

I run into the same issue after paying back the loan almost entirely (0.00000374@AAPL left).
collateralization ratio is in the + 1'000'000%.

got resolved after paying back the small fraction of the loan (0.00000374@AAP)

Hi @defichainislove @SacWheeler, we will be checking on this issue. Our initial investigation is it might be linked to a very small amount of loans. For now, you can try to payback this very small amount, but we will check on our end also.

Hi, this might be due to fluctuations on interest rates while the payment has not been made. This is solved on 0.21.0 where you are allowed to overpay a bit to make sure everything is covered. Excess payment will be returned to your wallet.


Feature Request: wrap long names

title says it all. self-provided descriptions aren't very compatible, making usage hard to grok (see: right hand side):
     $ ➜ End of line                                 l ➜ Right
     % ➜ Matching character: '()', '{}', '[]'        S ➜ Add a surrounding pair around a motion, o …
     0 ➜ Start of line                               s ➜ Add a surrounding pair around a motion (n …
     ^ ➜ Start of line (non-blank)                   t ➜ Move before next char

for information density's sake, i've chosen to not increase my max-column width.

I have the same problem. It would be cool if we could switch between layouts - for example, between a narrow-column and a wide-column layout - on the fly.


404

Why 404
http://<IP_ADDRESS>:8000/telescope
After I installed muhammadhuzaifa/telescope-guzzle-watcher

@Jobians that's not how it works, please study the https://laravel.com/docs/11.x/telescope first and then use this package if required.
If you need anything else I would be happy to contribute.

@huzaifaarain Brother I used the inbuilt Http, thanks.


[BEAM-9165] clean up python sdk harness status http server.

The http server is no longer needed as the thread dumps can be captured via runner.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Portable_Python PreCommit

R: @pabloem


Major refactor of the GUI

Describe changes:
Reorganized the main GUI and the AutoTrain GUI.

Now it's much easier to control multiple GUIs with one screen
The GUI is now responsive, i.e., supports dynamic scaling
Tabs and scrollable areas make button placement and information display much cleaner and more streamlined.

This screenshot shows two GUIs running side-by-side, leaving room for camera views in the bottom. Note they are on different "tabs".

And the user can freely resize the GUI without blocking important information and control buttons

Together with the updated AutoTrain dialog

What issues or discussions does this update address?

https://github.com/AllenNeuralDynamics/aind-behavior-blog/discussions/102
resolves https://github.com/AllenNeuralDynamics/aind-behavior-blog/issues/128
resolves https://github.com/AllenNeuralDynamics/aind-behavior-blog/issues/129

Describe the expected change in behavior from the perspective of the experimenter

Although there is no change in functionality, experimenters may need some time to familiarize themselves with the new configuration
Bug reports and feedback from the experimenters are important.

Describe the outcome of testing this update on a rig in 447

[x] tested on my PC
[ ] test in 447

This looks great! Thanks for doing the detailed work. Lets get @XX-Yin's approval before we merge, since he will also be using the GUI on the ephys computer

This looks great, Han, thank you so much! We will provide feedback as we begin to use it, but I already think it will be much more functional!

This is amazing thank you!

These changes look great for use in the training box. However, it is better to access most of the information (training parameters, stage control, optogenetics, visualization panel...) from the main window, since we need to check them frequently. We also have a screen dedicated to behavior in the ephys room. We should figure out how to reconcile these two configurations (ephys and training). Sorry, I'm unable to approve the pull request at this time even it's great for behavior training as it will take more time to make an ephys version based on it.

Since eventually we don't have to (and should not) change any training parameters or lickport position during ephys recording, I don't see a long term need for an ephys-specific version that has all information in one page like before. Even if you have some ephys-specific "plugins", it would be still better to build upon the new responsive and tab design. So for now, I would suggest we merge this PR to enhance the user experience in the behavior room first. Then you could take your time to adapt it for the ephys rig if necessary (by loading rig-specific ui etc).

@XX-Yin @hanhou Lets discuss this in person on monday. I think maintaining to versions of the GUI for ephys and behavior is going to be a huge headache. I bet we can find a streamlined version of the GUI that works for both.

Yes, let's discuss on Monday. One solution is to maintain two ForagingGUI.ui (one for training rig and one for ephys rig). We can use one of them when we open the GUI.

Tested the new GUI on Rig 2D with Travis.

I have tested this new GUI in 447-2-D. Per discussion #178, I'm merging this to production_test now

Oh, I thought the idea was to merge it tomorrow after the production merge, so it gets tested next monday. I guess having Travis test it today is sufficient.

Oh sorry I messed up with the standard procedure. We should not merge anything to production branch until the last one is merged to main, right? Should I reverse it?

Yes, the standard procedure would be to not merge things to production_testing between monday morning (when the testing rig updates to production_testing) and tuesday (after the production_merge).
If you want to be a super rule-follower you can reverse it. But since travis tested it with a live mouse today, and we are not quite back to normal procedure, I think its OK to keep the PR as - is. Your call

Okay, I'll keep the PR as it is this time and will not merge anything between Monday morning and Tuesday in the future.


Certain Buffs/Debuffs not showing up/being tracked

When reporting, please verify the issue with only this addon enabled and no others unless explicitly reporting an incompatibility between this addon an another. Likewise, please fill in the below information to the best of your ability — this information helps us a great deal.
Issue description:
Some Buffs/Debuffs from Castle Nathria are not showing up on the raid frames (specifically Concentrated Anima and Gluttonous Miasma, I even tried the spell IDs with no results.
How to reproduce:

Add the debuff to track list to appear in different location
Fight boss and watch.

Technical info:
Retail
Additional context:
Add any other context about the problem here.
Screenshots:
If applicable, add screenshots to help explain your problem.
Lua error log:
Attach the Lua error log here (please use code tags)

Hrm odd. This is hard to test because I need to be fighting the boss to see the issue. In general, there's no specific reason why these certain spells won't be tracked as long as the name typed in matches the aura name exactly...
The hardest part is I have no idea how to test this...

Hrm odd. This is hard to test because I need to be fighting the boss to see the issue. In general, there's no specific reason why these certain spells won't be tracked as long as the name typed in matches the aura name exactly...
The hardest part is I have no idea how to test this...


Web site https://www.runeasymail.com/ down

Hello,
Sorry to say that, but you did not renew your GoDaddy domain hosting.
"NOTICE: This domain name expired on 10/16/2018 and is pending renewal or deletion."
Would like to make something ?
Thank you ,
Jean

Hello @jgdubuis
Yes, I know there is a new domain. I have just set it up.
http://easy.supersecure.email
If you still experience an issue with that, please ping me. Closing this ticket  :)
Thanks,
Gyuner


Sema: Fix capture lifetime issue in protocol conformance sendable mismatch [5.7]

Cherry-pick of https://github.com/apple/swift/pull/59558.
The closure passed in to diagnoseOrDefer() outlives the ConformanceChecker
instance, so instead of capturing 'this', pull out the 'DC' instance
variable directly.

@swift-ci Please test


storage: flash_map: Fix partition device retrieval

Change the default behaviour of the flash partition choice when no
matching compatible is found. The new default is the grandparent node
of the fixed-partition.
As the grandparent node is what the jedec_spi_nor and nordic_qspi_nor
compatibles were selecting, remove these as separate checks.
This allows the flash_map API to be used for implementations of the
flash API other than the 3 originally specified (soc_nv_flash,
jedec_spi_nor & nordic_qspi_nor).
Fixes #26397
Signed-off-by: Jordan Yates<EMAIL_ADDRESS>

This pull request is predicated on the assumption that the correct flash device for all fixed-partition instances is the grandparent node of that partition.

Built and checked on nrf52840.


Parse error in Nickel files with wildcard type annotations

Describe the bug
Trying to format the following file with Topiary:
(let { a : { b : Number } = { b }} = { a = { b = "no" }} in
b) : _

results in this error:
[2023-05-26T09:12:17Z ERROR topiary] Parsing error between line 2, column 4 and line 2, column 7

Expected behavior
This is valid Nickel, so it should parse (& format) correctly.

I think this is a bug in the tree-sitter grammar; (fun {x,x} => x) : _ produces a parse error without topiary being involved.


Driver swapping with Zadig is a real bummer in windows

Hello noble contribiutors.
I'm using this module on Mac os with no problem at all. And I was also able to make it work on windows as well. The only problem is that in order for this module to function on windows properly, you have to swap the bluetooth driver with Zadig which practically makes the blutooth adaptor useless. E.g. you cannot turn your adaptor on and off in windows or connect your bluetooth headset.
This constraint makes this great module impractical for commercial usage since the client must willingly mess his/her computer's bluetooth and this is just too much to ask.
I know the techniques required to roll back to the standard driver whenever you want but this isn't something that any user would want.
Is there any solution or a workaround to avoid messing with the driver? Like OSX/ Mac.
Thanks.

Unfortunately not. Stuck on this as well. I'm using the more maintained @abandonware/bleno library to try and get it to run on windows but the code doesn't detect a stateChange.
I'm trying to make it work on windows. I've replaced a Bluetooth 2.0 USB driver with Zadig WinUSB and the "No compatible Bluetooth 4.0 USB Device found error" is gone. The library detects a stateChange and emits it but the listener doesn't pick it up for some reason. I've tried running all the library examples, the noble/bleno examples and the node-bluetooth-hci-socket  examples but nothing. It runs with no error but just doesn't pick up the stateChange.
Can you let me know the versions of node and node-gyp you are using on your windows machine?

I see that https://github.com/hbldh/bleak somehow manages to use BLE on Windows, without requiring you to replace the driver... perhaps something similar could be implemented here?

@RamlahAziz
Hello. I wish I saw your message earlier. Try using theGecko/noble. Add this line in dependencies in your packages.json:
"noble": "theGecko/noble"

@JJTech0130 Thanks for your suggestion.
If only we could notify the contributors.
@sandeepmistry


Include upper part

Create a separate module which includes the upper part (so that both the toggle/player background and the notification background becomes transparent).

Check the Releases tab


Problem: The program cannot be exited

Very nice project, thanks for your efforts. But I encountered a problem in use, The program cannot be exited.
The following is an example:
import {Redisson} from 'node-redisson';

const redisson = new Redisson({
    redis: {
        options: {
            host: 'localhost',
            password: '123456',
        },
    },
});

async function test() {
    const lock = redisson.getLock('Example:LockName');
    await lock.lock();
    await lock.unlock();
}

await test();

await redisson.redis.quit();
console.info('done');

In the example, 'done' is output, but the program does not exit.

Thanks for your feedback, I will check it.

The reason for this problem is that NodeRedisson will also hold another Redis connection for subscription.
I adds a quit() method for Redisson in v1.0.3 , so you can do this:
// quit the redisson client
await redisson.quit();


Support GtkBindings

I tried adding these to Gir.toml, but I get a panic with "Missing memory management functions for {}" with {} being BindingArg, BindingEntry, BindingSet, and BindingSignal. Is resolving that memory management stuff under active development or what is the current state of it?

Is plain records, currently I don't know, what to do with it (part https://github.com/gtk-rs/gir/issues/103 without separate issue)


Fix Drag Lifecycle events not fired for data transfers

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Bug fix

What is the current behavior? (You can also link to an open issue here)

https://github.com/akserg/ng2-dnd/issues/175

What is the new behavior (if this is a feature change)?

"Lifecycle" events are now correctly emitted when a file is dragged over a dnd-droppable-Enabled element.

Other information:

@fridolin-koch - Any idea why the CI Build failed? This PR would be an excellent addition...

@MNorgren I guess it was unrelated to my pr, I rebased on master and now it works


Forever stop, does not kill forever-monitor child

Working in<EMAIL_ADDRESS>does not work in latest forever.
server.js:
var http = require('http');
http.createServer(function (req, res) {
res.end('bye')
}).listen(1337);

monitor.js:
var forever = require('forever-monitor');

var child = new (forever.Monitor)('server.js', {
    max: 3,
    killTree: true,
    silent: true,
    args: []
});

child.on('exit', function () {
    console.log('your-filename.js has exited after 3 restarts');
});

child.start();

running:
forever start monitor.js
forever stop monitor.js
server.js still keeps running in background

Had the same issue. It seems like forever doesn't properly kill of deeper child processes.
Found a solution by this:
Use spawn:
var spawn = require('child_process').spawn;
// child processes by spawn
var children = [];
process.on('SIGTERM', function() {
    children.forEach(function(child) {
        child.kill();
    });
});

children.push(spawn('<the terminal command>'));

Then make sure forever --killSignal=SIGTERM is set. I used forever start --killSignal=SIGTERM app.js

For me, the child processes gets terminated on SIGINT but not SIGTERM.

SIGTERM is the recommended signal to use as suggested by nodejs docs
Putting these out here: appending these at the bottom of the script will allow for cleaner exist, and ensure that all children gets terminated when the parent exits:
process.on('exit', function() {
  children.forEach(function(child) {
    child.kill();
  });
  console.log('Exit: killed children')
});

var cleanExit = function() { process.exit() };
process.on('SIGINT', cleanExit); // catch ctrl-c
process.on('SIGTERM', cleanExit); // catch kill


Proposal: Add compaction support to RowContainer

Description
Part of https://github.com/facebookincubator/velox/issues/7180 to support spilling partial state.
RowContainer is backed by a set of memory allocations. Compaction is supposed to be invoked after some rows are erased(like spilling part of the rows): it tries defragmenting the memory to make some allocations free.
The compaction API returns [freedBytes, updatedRows], with freedBytes being freed space size, and updatedRows being a map from moved rows' original ptr to the updated ptr, to enable the caller to update the reference to rows.
Defragmentation Strategy:
What the defragmentation does is: it selects some of the allocations as target, moves rows located in these target allocations to free space of other allocations, then free the target allocations. When selecting the targets, it tries to maximize the freeable space.
RowContainer is backed by two kinds of memory allocation: small, non-contiguous allocation and large, contiguous allocation. We mainly focus on freeing contiguous allocations, since freeing non-contiguous only gives at most 256KB, which is negligible.
The selection process: iterate each large allocation starting from the largest one, if it can be absorbed by the rest of allocations(non-contiguous included), add it to the target set.
Detailed implementation:

Construct stats of allocations for selecting: size of the allocation, and free space: the size of free rows in this allocation plus the unused space if it's the last allocation.
Sort large allocations by {size, free_space} in decreasing order, then iterate over the sorted allocations: if total_free_space - free_space[i] >= size[i] - free_space[i], add allocation i to the target set, and total_free_space -= free_space[i].
Move rows: get target rows by listRows in target allocations, and move them to the following while recording the change in upadtedRows.

free rows of the rest of allocations
unused space of the rest of allocation, if any.

Free target allocations.

Following struct / functionalities are needed to support the feature:

struct AllocationCompactionStat: allocation's index, kind, size, free space.
vector<AllocationCompactionStat> RowContainer::getCompactionStats(): private method that builds stats for all allocation. It gets allocations' addr, size from AllocationPool, then for each free row, determine which allocation it's in, mark allocation id in row and update free space in AllocationCompactionStat.
RowContainer::listRows that supports only list rows within certain allocation.
AllocationPool::freeRanges(std::vector<int32_t> indices): To free target allocations from AllocationPool.

Tasks

[ ] struct AllocationCompactionStat, RowContainer::getCompactionStats() and tests.
[ ] RowContainer::listRows that supports only list rows within one allocation and tests.
[ ] AllocationPool::freeRanges(std::vector<int32_t> indices) and tests.
[ ] RowContainer::compact() and tests.

@mbasmanova Thanks for replying!
Sorry I didn't clarify the proposal was only targeted to AllocationPool used for fixed-size rows memory.
I overlooked HashStringAllocator as I thought it has its own mechanism to free to pool(turns out it's only for allocations directly from pool😥). And yeah, the HashStringAllocator part should be the key if the row contains string/complex types. I think I need to do some research on this and update this thread then.
Will let you know when this is ready. Thanks!

Hi @mbasmanova, I've updated the proposal with HashStringAllocator compaction, please take a look. Thanks!

@usurai Thank you for updating the proposal. Overall looks good % we need to come up with a test that help us evaluate the effectiveness of the proposed algorithms and tweak these if needed.
(Going forward, let's use Google Docs or similar to allow for each inline commenting.)

@mbasmanova
Google doc version: https://docs.google.com/document/d/11bsoVSPVjCS4yCoKmUAFIgy_xu9bUwsKzZ6dKHtnW5Q/edit?usp=sharing
My thought on testing is in Test Strategy section. Thanks!


Detect if current terminal supports emojis

Is there currently any way to detect if the current terminal supports Emojis? This would allow optionally using Emojis where supported. Thinking something like:
if (AnsiConsole.Capabilities.Supports.Emoji)
{
    AnsiConsole.MarkupLine(Emoji.Known.CheckBoxWithCheck + " Done");
}
else
{
    AnsiConsole.Markup("Done");
}

@stevenknox There is no way to detect this to my knowledge. One thing to check for is whether or not the terminal output encoding is Unicode, but it doesn't tell whether or not the terminal supports emojis.

No worries @patriksvensson - ill try checking for Unicode as suggested 👍

@stevenknox, might not work everywhere, but I've ran into a similar issue and have, so far, been able to force Unicode encoding with something like Console.OutputEncoding = Encoding.Unicode; by just tossing that at the start of my project.
Not sure if there's any downsides or gotchas to this cc @patriksvensson

Thanks @pdevito3 !


Docker doesn't configure UTS namespace or /etc/hostname correctly

Edit: My assertion about setting domainname may be suspect; see phemmer's comment and discussion below. The issue of erroneously passing the FQDN to syscall.Sethostname remains however.
Environment
vagrant@vagrant-ubuntu-utopic-64:~$ docker --version
Docker version 1.7.0, build 0baf609

Problem
Docker accepts a fully qualified domain name as the argument to --hostname, and models separate Hostname and Domainname fields in runconfig.Config; however once inside libcontainer only Hostname is modelled, and this erroneously includes the domain name which is then fed into syscall.Sethostname with the following results:
vagrant@vagrant-ubuntu-utopic-64:~$ docker run --hostname test.example.com -ti ubuntu
root@test:/# hostname
test.example.com
root@test:/# domainname
(none)

This is not correct; the value passed to syscall.Sethostname should be the unqualified hostname, and the remainder to syscall.Setdomainname. This would yield the expected output:
vagrant@vagrant-ubuntu-utopic-64:~$ docker run --hostname test.example.com -ti ubuntu
root@test:/# hostname
test
root@test:/# domainname
example.com

Currently, libcontainer does not invoke syscall.Setdomainname at all, leaving the domain name parameter of the UTS namespace uninitialised.
Docker is also incorrectly generating an /etc/hostname file with the fully qualified name - again this should be the unqualified name, and the FQDN set by aliasing in /etc/hosts.
It could also be argued that --hostname should be renamed to --fqdn, or changed so that it admits only an unqualified name and companioned by a new --domainname option to set the remainder.
Finally, the error message is uninformative:
docker run --hostname<PHONE_NUMBER>01234567890123456789012345678901234567890123456789.example.com -ti ubuntu
Error response from daemon: Cannot start container c1bb14c2a10b2341c185aed804ab6f625ca7a1164ea90ea4fd37ea56b6e2bed0: [8] System error: invalid argument

Consequences

UTS namepsace not correctly initialised
The underlying sethostname system call limits the hostname to 64 characters. Because Docker is calling it with the fully qualified name, the entire FQDN is limited to 64 characters (weaveworks/weave#1006)

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

The current behavior is the correct behavior. The value you pass to docker in --hostname is supposed to be the value you get back from the commands hostname and uname -n.
The "domainname" that you are referring to (the domainname command) is not related. From man 1 domainname:

domainname - show or set the system's NIS/YP domain name

What I think you are looking for is the dnsdomainname:
# docker run --hostname test.foo.com -ti ubuntu dnsdomainname
foo.com

What I think you are looking for is the dnsdomainname:

I am aware of dnsdomainname. My main concern is that we should not be setting the entire FQDN as the hostname, in either /etc/hostname or with syscall.Sethostname. Hostname should not include a DNS domain - naming of hosts is orthogonal to IP addressing and DNS.
This is strongly implied by man hostname:
The  recommended method of setting the FQDN is to make the hostname be an alias for the fully qualified name using /etc/hosts, DNS,
       or NIS. For example, if the hostname was "ursula", one might have a line in /etc/hosts which reads

              <IP_ADDRESS>    ursula.example.com ursula

This would yield the following:
$ hostname
ursula
$ dnsdomainname
example.com
$ hostname -f
ursula.example.com

I believe this would give you the correct behaviour in terms of field length limits: unqualified hostname limited to 64 characters by the kernel, and the domain part limited by the resolver implementation. (Incidentally, this interpretation lends strength to your argument about dnsdomain - that field is also kernel limited to 64 characters, in contravention of RFC1035 2.3.4 which specifies a maximum length of 255 characters on fully qualified names). Thoughts?

I'm really confused then. If you don't want a fully qualified hostname, then don't pass a fully qualified hostname.

I'm really confused then. If you don't want a fully qualified hostname, then don't pass a fully qualified hostname.

I do want a fully qualified hostname. My argument is that the way a Linux system is properly configured is to put the unqualified part into /ets/hostname and sethostname, and the domain part in /etc/hosts.

For further clarification; the original use of /etc/hostname and the value of sethostname was to store an unqualified name - as I said, DNS was orthogonal. Over time a common misconfiguration crept in of putting the FQDN into /etc/hostname (mainly I suspect because folks didn't realise that the correct way was to put an alias in /etc/hosts). To cope with this common misconfiguration, most tools have been bodged to cope with either scenario - see man hostname:
       /etc/hostname  Historically  this file was supposed to only contain the hostname and not the full canonical FQDN. Nowadays most
       software is able to cope with a full FQDN here. This file is read at boot time by the system initialization scripts to set  the
       hostname.

So for most things it's a non issue - everything you're likely to deploy inside the container can cope with things being configured either way. What is not the same though is the artificial limit on FQDN imposed by storing the entire qualified name in a kernel field which is applying a limit intended for the unqualified hostname.

I see what you're wanting now. But I argue the behavior of the docker --hostname parameter should not be touched. The parameter sets the system hostname, which is a special value tracked by the kernel. The domain name is irrelevant to the kernel. It doesn't care at all.
Now if the request is to automatically append a domain name to the hostname, and use it in the /etc/hosts file, this should be a new feature.
Also, using a fully qualified host name is not an uncommon practice. There are 2 different schools of thought about the hostname. The redhat school of thought, and the debian school of thought.
The redhat school says that hostname should be fully qualified. The debian school says that hostname should not be fully qualified.
By changing the behavior of --hostname, you may end up breaking redhat based containers, which many tools expect a fully qualified hostname (yes, the issues can usually be worked around though).

To add to @phemmer's comments, the way it works today is because we fixed an issue just under a year ago to support both Fedora/Redhat "view of the world" for hostnames as well as Ubuntu.  I'm curious if something has changed in the overall code path because when I fixed that issue, hostname on Ubuntu Docker images still resulted in the prefix, not FQDN, if I remember correctly.  I can look back at the issue and PR and see if we've regressed in some way, but overall, we do have to support both views which makes this whole area tricky.

Ahhh, the joys of fragmentation :smile: I appreciate that you have a difficult balancing act to do here - I wasn't aware that Redhat has standardised on storing the FQDN in /etc/hostname and sethostname. What are your thoughts about the artificial limit this imposes on the fully qualified name? It makes a mockery of e.g. #9333, because in reality the entire fully qualified name including domain is restricted to 64 characters... if nothing else is done, the code relating to validating --hostname needs to be revamped.

Seems like there is no issue here...Can we close this?

I would suggest if you do nothing else you should change the field validation so that you get a sensible error message when you pass an FQDN > getconf HOST_NAME_MAX to -h.

@estesp There definitely seems to be a regression on Ubuntu:
# docker --version
Docker version 1.8.2, build 0a8c2e3
# docker run --rm -it -h foo.bar.org ubuntu:vivid /bin/bash
root@foo:/# hostname
foo.bar.org
root@foo:/# hostname -f
foo.bar.org
root@foo:/# more /etc/hostname
foo.bar.org
root@foo:/# dnsdomainname
bar.org

I see similar behavior with Debian images.

@garyp What's the issue? that's what I would expect to see.

@phemmer hostname should return the unqualified hostname on Debian/Ubuntu systems (e.g. "foo" in my example above) and, likewise, /etc/hostname should contain the unqualified name. You yourself linked above to the Debian policy on this, which says:

The init script in runlevel S which is symlinked to "/etc/init.d/hostname.sh" sets the system hostname at boot time (using the hostname command) to the name stored in "/etc/hostname". This file should contain only the system hostname, not a fully qualified domain name.

hostname is a standard linux utility. It's the same utility on all distros, and behaves the exact same. The difference is that on debian based systems, it's standard for the hostname to not be fully qualified. Meaning that hostname simply shows the value that is set. If you don't want a fully qualified hostname, don't set it fully qualified.

Agreed on the hostname command. The root problem is that on Debian-based systems Docker dumps the FQDN into /etc/hostname. I can't just pass the unqualified hostname to Docker because then hostname -f will not return the FQDN. In short, on a properly-configured Debian-based system, the following should be true:
root@foo:/# hostname
foo
root@foo:/# hostname -f
foo.bar.org

The standard way to get the above results on Debian-based systems is for /etc/hostname to contain "foo" and /etc/hosts to contain " foo.bar.org foo". There is no way to achieve this state with Docker's current behavior:

If I pass --hostname foo to Docker, then /etc/hostname is correct ("foo") but /etc/hosts is wrong (" foo"), causing hostname -f to not return the FQDN.

If I pass --hostname foo.bar.org to Docker, then /etc/hosts is correct (" foo.bar.org foo") but /etc/hostname is wrong ("foo.bar.org"), causing hostname to return the FQDN instead of the unqualified name.

Yes, that i'll agree with. That is what I was referring to with the comment:

Now if the request is to automatically append a domain name to the hostname, and use it in the /etc/hosts file, this should be a new feature.

I'm not opposed to something which would allow the desired behavior, just that it should be a new feature. The --hostname option should remain setting the hostname to the kernel exactly as you passed it. Docker doesn't know what distro you're running, and even if it did, that kind of automatic switch would be a bad idea in my opinion.
The best solution I can think of for this would be a --fqdn option. If provided, it would be used in /etc/hosts. Then hostname would be the value provided to --hostname, and hostname -f would be the --fqdn value. This would be true for all distros.
But I think it would be best to track such a feature request in a new issue, so it has a clean history, and is clear that it is a feature request, and not a bug report.

To add to this debate, from #20180.
Linux has a limit of 64 characters for the in-kernel hostname (syscall.Sethostname), but the limit for DNS domains is 253 characters (a set of tokens <= 63 characters each). Smooshing the domainname into the hostname means my whole host+domain has to be less than 64. As far as I can tell there is no real workaround for this - it is just not possible to use longer domainnames.
Standard tools like hostname and dnsdomainname already operate correctly on docker, which populates the /etc/hosts file properly for the hostname. There's not actually any reason to smoosh them together, except to act more like (broken) RedHat systems with the FQDN in /etc/hostname.
The root of the problem is that the API has 2 fields (hostname and domainname) but the CLI only has hostname, but docker wants to offer both the shortest one-token name AND the FQDN as /etc/hosts aliases.  I'm sort of asserting that this is semantically wrong, though the horse has already left the barn.
CLI --hostname=foo.bar.com becomes:

hostname foo.bar.com
hostname -f foo.bar.com
dnsdomainname bar.com
/etc/hostname foo.bar.com
/etc/hosts foo.bar.com foo  # foo is what is broken

API hostname=foo domainname=""

hostname foo
hostname -f foo
dnsdomainname ``
/etc/hostname foo
/etc/hosts foo

API hostname=foo domainname=bar.com

hostname foo.bar.com  # this is what is broken
hostname -f foo.bar.com
dnsdomainname bar.com
/etc/hostname foo.bar.com # broken
/etc/hosts foo.bar.com foo

I'm assuming that any solution here has to retain the CLI's set of behaviors - as broken as it is semantically, it is useful and likely to cause pain.   I am also assuming that we do not want to add new CLI flags (CLI will just be "wrong" but compatible, for now).  Conversely, I am assuming that we can fix the two-part API case without causing too much anguish.  Do I interpret correctly?

The PR attached here adds a new flag to the API which says whether to make hostname be the FQDN or not.
A simpler approach might be to make the CLI not split the --hostname flag at all, leaving the domainname API field empty.  The /etc/hosts builder can do the split and offer both foo and foo.bar.com as hosts aliases.  No new API fields required.

#20200 implements the 2nd approach, which I think is a much better option.  I'm happy to polish it off if someone ACKs the fix.


Bancor Adapter and Substream

@zizou0x @kayibal
I can't spot what the problem is with the creation, as it gives this error with tycho:
Cannot find account with id: "..." where the ID is indeed the master vault address
Do you have any suggestions regarding this and, please, could you have a look?
I have tried with many different approaches, including the check by tx hash, but unfortunately it didn't help.
While testing via substreams gui, I am able to find the created component at that block and that tx with the given address, so I am sure the component is created.
--- EDIT:
The problem seems to be in extractor instance;
If component ID would not be found, runner.py would have failed with:
if comp_id not in components_by_id:
return TestResult.Failed(
f"'{comp_id}' not found in protocol components. "
f"Available components: {set(components_by_id.keys())}"
)
--- EDIT 2:
I also enabled skip_simulation flag to make sure the error was not related to a swap, feel free to re-enable it if necessary

@zizou0x I would like to suggest you also to use my logic to track ETH transfers in some global tycho file, along with extract_balance_deltas_from_tx (after applying the eventObject.at(index) logic instead of eventObject.field)


new user script remove_low_quality_photos.py

remove_low_quality_photos.py
This script estimates the quality of the images in a chunk.
When the image quality is less than 0.7, the image is removed form the chunk.

Thank you 👍


Moving data from content to front matter

This change is an iterative step to #105. Whether Gatsby or 11ty works at the end of the day, it's still important to wrangle the data into a format that's easier to work with.
Problem

Data for meetup posts exists in front matter, liquid assigns expressions, includes, and _config.yml. This makes it challenging to educate new contributors and to track down bugs.
Installing the Jekyll bits locally to merely view changes is a major PITA—especially for JavaScript folks without Ruby experience.

Solution

This PR consolidates the data related to meetup posts into basically two places: the /_data/ directory and the individual post's front matter. Reasonable attempts were made to maintain as much markup and visual parity with the existing site as is possible. All posts going back to January 2018 were updated to work with the new format.
A docker-compose file was added to the root directory to allow for running Jekyll in a container.

Lastly, a CONTRIBUTING-POSTS.md file was added to bring all this together and explain how it works.

Thanks for the approved review, @aaronj1335 . What are next steps? I.e., who merges?


Step 3 says Toolkit 8 but links to 9

The link https://developer.nvidia.com/cuda-downloads has downloads to version cuda_9.0.176_win10.exe but the step says to install Toolkit 8, so I am unsure which one is the right one

im getting error with cuda 9


option to specify detection language

like paddleocr --lang

You need to download the multi lang models here
Then pass the models in
const ocr = await Ocr.create({
  models: {
    detectionPath: '..',
    recognitionPath: '..',
    dictionaryPath: '..'
  }
})

(not planned)
auto download like example


Bug: run @arcgis/core test case with jest

when i install @arcgis/core with pnpm , jest test case running error:
`
Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

By default "node_modules" folder is ignored by transformers.

Here's what you can do:
 • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
 • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
 • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
 • If you need a custom transformation specify a "transform" option in your config.
 • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

You'll find more details and examples of these config options in the docs:
https://jestjs.io/docs/configuration
For information about custom transformations, see:
https://jestjs.io/docs/code-transformation

Details:

C:\develop\learn\web\BDD\jest\jest-demo\node_modules\.pnpm\@arcgis+core@4.23.7\node_modules\@arcgis\core\Map.js:5
import{_ as e}from"./chunks/tslib.es6.js";import s from"./Basemap.js..........

`
but when i install @arcgis/core with npm ,it's ok , I don't know what's going on
my demo respo url is :I don't know what's going on

I'm not sure if it's an issue with @arcgis/core or Jest. We have not tested extensively with pnpm and currently unsure if we need something in the package.json. Everything in core is set up as a pure ESM package, so I'm guessing this is a jest/pnpm issue. Will investigate in the future.

Thanks for your prompt reply，can you have a try with pnpm ,I will continue to pay attention to this qustion, thanks a lot

This is because pnpm uses modules installed in node_modules/.pnpm, so you need to update the transform in the jest config to take this into account.
{
    ...
    transformIgnorePatterns: ['node_modules/(?!\\.pnpm/)(?!(@arcgis|@esri|@stencil|@popperjs)/)']
    ...
}

awesome👍👍👍, In the end, it is necessary to convert the esm syntax of @arcgis/core，thank you very much.


"Please Log In" After entering correct password

Hello,
My issue is similar to: http://code.google.com/p/yourls/issues/detail?id=1262
I'm using PHP v 5.4.9 ... All tables were installed correctly. I inserted a cookie from http://yourls.org/cookie .. I also deleted the username, password, cookie and replaced to see if that fixed the problem. It did not. I only have 1 username and PW in the config.php file.
Basically, when you enter the correct information into the admin login it says "Please Log In" ... anything incorrect entered gets an "Invalid Username / Password" ...
I see the request for var_dump() in functions-auth.php or auth.php but I am not necessarily an expert - I was wondering if anyone might point me in the direction of the lines to place the var_dump on and on what variable so I can see where exactly it is breaking.
I am using the latest 1.7 master because I had to use the master as it fixed a table install issue I believe w/ the version of MySQL I saw on another issue. So tables were removed and now appear as installed correctly.
I also tried this: define( 'YOURLS_NO_HASH_PASSWORD', true ); .. but no help .. to see if it was something to do with the password not being hashed in config.php
Finally, I am running nginx w/ the following config, although this may be unrelated (running varnish, hence 8080 - excluded yourls domain/directory in varnish config w/ pass):
server {
listen <IP_ADDRESS>:8080;
server_name site.us;
port_in_redirect off;
access_log off;
error_log /var/log/nginx/site.us.error.log;
root /usr/share/nginx/www/site;
location / {
rewrite ^/([0-9a-z-]+)/?$ /s/yourls-go.php?id=$1 last;
location ~ .php$ {
try_files $uri =404;
fastcgi_split_path_info ^(.+.php)(/.+)$;
fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_index index.php;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
}
}
}
Thank you in advance for any guidance on how to identify this problem exactly. I am new to using var_dump.

I am facing the same issue. I configured correctly the config file. but I am not redirecting to main page it keeps asking me the "Please log in". As mentioned in the olde post Line number 90  include/functions_auth.php i just disabled it, then it is redirected to the main page. but all time I need to login if i click any link. please help me.

I just wanted to thank @ablanken for his comment on Mar 26 2014 which fixed the issue for me.
I'm running IIS8.5 with PHP5.6 and was having the issue as described above... but only when using IE. With Chrome it worked fine, but no joy with any version of IE that I managed to try logging in with.
The removal of the code snippet suggested fixed it for me, and now IE (and Chrome) both log in and work as expected.
Thanks!

I'm having this same issue. Can't log in with correct password. I know the issue has to be something related to the login process because I can go in and change to this: define( 'YOURLS_PRIVATE', false ); and it'll bypass the login completely and go right to my list of shortened URLs. Once I'm in there, everything works exactly as it should. So I guess until this issue is resolved, I'll just make it public for a few minutes while I do what I need to do and put the broken login back on when I'm done.
What a pain.

Check for any caching issues.

@GTMAN how can I check for caching issues? Where do I look?

I installed on Kinsta Nginx , then I changed the main domain and had same issue , Please login... in Config.php file changing the Cookie Random value fixed the issue for me. i.e. define( 'YOURLS_COOKIEKEY', 'asdfsafs868768afsafsaf9sksjdlfk87rjsadlkfjasl8' );

Hi,
I had this problem today on a server with 2 installs of Yourls.
The funny thing was that only one of the install had the problem. The other one was working fine.
Because of this I was able to debug it this way:

I replaced the files downloading the latest one from github. No luck.
I replaced the files using the other install that was working. Again, no luck, same issue.
I replaced the cookiekey and clear caches on my computer. Same thing.
Because I know that is the same server, I discarded issues with the cache on my server or nginx config issues.
So the only thing to test was the database.
I was going to dump it and upload it again but I decided to go to this url first:
myyourls.com/admin/upgrade.php
first time it did nothing, I reloaded it, and nothing, just the login page.
I put my credentials there and done! I was in on a page that said: You do not need to upgrade.

After this I can use the admin but the funny thing is that I cannot logout anymore.
When I logout and go to /admin/ the session is still open.
So this is clearly a problem with the cookies. It does not store the login cookie when accessing from admin/ but it does work with the url /admin/upgrade.php and it does not remove that one  when going to logout/ either.
I am considering to go back to 1.6 or 1.7 but I will try this next time.
Hope you can use this to find the issue.
I have also tested with PHP 5.6, 7.0 and 7.1 and the issue is still there.
This is a server setup with serverpilot.io, in case you want to test.

More info.
I compared both databases to try to find the issue.
On the table short_options on the field version, it is a 1.7 for the install that works and a 1.5 for the one that does not work.
So it seems that the upgrade is needed on the database but the system is not able to do it.
Any idea on how to upgrade the database? or how to export my redirects to a new database updated?

@planetahuevo It might be that YOURLS's database user does not have the required permissions to upgrade the database. That's the low-hanging fruit answer, at least.

What does need to be upgraded on the database? The urls and redirections works all the time and I can add new one. I really do not know where to look.

Hello. I just installed Yourls in a subfolder /s/ on my Web site and I faced the same problem... but I solved it.
In fact, I have 2 domain names: mywebsite.com and my-website.com (FAKE examples ;) ).
And for some historical reason, mywebsite.com automatically redirects to my-website.com.
But I wanted to use the "short" version with Yourls, so I configured like this:
define( 'YOURLS_SITE', 'http://mywebsite.com/s' );
As there's a redirection, it doesn't work. So I had to use the "long" version, and now it's OK:
define( 'YOURLS_SITE', 'http://my-website.com/s' );
Hope this can help one of you.

I am going with the fresh new install. I gave up to fix this one.
Any ideas on how to export and import the data?
Thanks

After some more tests, I am not sure anymore that the database is the problem, but the management of the cookies.

@planetahuevo Thanks a lot for your feedback. Could you elaborate the cookie issue?

You can read my reply 27 days ago: https://github.com/YOURLS/YOURLS/issues/1652#issuecomment-282912109
"So this is clearly a problem with the cookies. It does not store the login cookie when accessing from admin/ but it does work with the url /admin/upgrade.php and it does not remove that one when going to logout/ either."

Hi,
I had this problem and i've solve it.
in confiq.php file i 've only changed define( 'YOURLS_SITE', 'http://www.my website.com' ) to define( 'YOURLS_SITE', 'http://mywebsite.com' ). so I've only deleted www. from my website name .

medikiaei saves the day thanx!!!

Same problem here trying to run this inside a docker container. Always returns true when checking the password but then says please loging afterwards.  Yes I should upgrade to a newer version, but I wont even try taht until I can get a working test environment with the current version that is running in production. This code is really ahrd to follow cant find where its spazzing out.


deleted all things lol

youre free now

I can't accept this PR as it is merged into the wrong branch.


Add libguestfs tools to SIFT

libguestfs tools support mounting various types of virtual hard drive types.  Specifically, it works well with Microsoft's VHD and VHDX formats.  We need this to mount VHDX files from EZ's kape triage image tool.
Installation in the current SIFT is simple via apt:  apt-get install libguestfs-tools
More info: http://libguestfs.org/

This has been added.


chore(requirements): update docker-py to 1.10.6

See https://github.com/docker/docker-py/blob/release/docs/change_log.md#1106
Closes #1125.

Current coverage is 87.74% (diff: 100%)

Merging #1130 into master will not change coverage

@@             master      #1130   diff @@
==========================================
  Files            42         42
  Lines          3656       3656
  Methods           0          0
  Messages          0          0
  Branches        626        626
==========================================
  Hits           3208       3208
  Misses          295        295
  Partials        153        153

Powered by Codecov. Last update d24d628...e81be7a


Lock the bundle to OCP v4.10

Tested via https://github.com/infrawatch/service-telemetry-operator/pull/385


Add WAVM runtime

[x] I've read CONTRIBUTING.md.
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (https://help.github.com/articles/closing-issues-via-commit-messages/).

Thanks! Sorry for the delay, I just seen the PR!


TypeScriptGenerator - Generated toJSON method conflicts with STJ deserializing behavior

System.Text.Json when deserializing polymorphic objects expects $discriminator to be at the start of the object (https://github.com/dotnet/runtime/issues/72604).
In actual toJSON method template discriminator and base class properties are added to the JSON-object after the properties of the inheritor class.
Proposal is to change Class.liquid template by moving super.toJSON(data) call to the start of toJSON method:
    {% if HasInheritance and SupportsOverrideKeyword %}override {% endif %}toJSON(data?: any) {
        data = typeof data === 'object' ? data : {};
{% if HasInheritance -%}
        super.toJSON(data);
{% endif -%}
{% if HasIndexerProperty -%}
        for (var property in this) {
            if (this.hasOwnProperty(property))
                data[property] = this[property];
        }
{% endif -%}
{% if HasDiscriminator -%}
        data["{{ BaseDiscriminator }}"] = this._discriminator;
{% endif -%}
{% for property in Properties -%}
        {{ property.ConvertToJavaScriptCode | tab }}
{% endfor -%}
        return data;
    }

We have the same problem here! Trying to switch to System.Text.Json but failing to do so because .NET throws an exception.
My suggestion would also have been to move the base-call to the top which would be sense anyways in my opinion (sub class should always override stuff of base classes). Is there any reason not to make this change?


v8-315

v8 v3.15.11

@BrewTestBot test this please

Left some feedback here. Once that's addressed and the bot is happy, I'm content to merge this in.

@BrewTestBot test this please


Cannot Open .vott project  "app encountered an unknown error" Lost hundreds of labels.

Describe the bug
When trying to open the project file nothing loads and a popup window says "app encountered an unknown error".
To Reproduce
Steps to reproduce the behavior:

Open VoTT
Try to open existing project

Expected behavior
The project loads the images and the previously created labels.
Screenshots
Image:

I have the same problem. How to solve this issue please

Did you get the solutiion?

I have the same issue

Still facing same issue


No longer works with mongo with local strategy

Hi, using Sails v0.11 and Mongo 2.6.5 (all latest as of today) on my Mac 10.10, I have following issue:
I install new sails project from scratch with:
sails generate test
cd test
npm install sails-generate-auth passport passport-local bcryptjs validator sails-mongo --save

Then I follow exact same steps as defined inside README.md.
If I keep my model connection to "localDiskDb", all is working as expected (login + registration).
If I add mongo details inside config/connections.js:
someMongodbServer: {
    adapter: 'sails-mongo',
    host: '<IP_ADDRESS>',
    // port: 27017,
    database: 'db_test'
  },

And then modify config/models like:
connection: 'someMongodbServer',

When I lift, if i try to login even with wrong data and press login button: I get my browser "loading" then get browser error message (like timeout) - stuck on URL /auth/local, and nothing in sails console. If I try to register with proper info, i get redirected to registration page with no error.
For info, my models are created inside my mongo instance, but no data is recorded for passport stuff. If I also setup sessions to be processed via mongo, it works. But one thing I noticed is that inside my session, if I try to register many times, each registration data submitted is stored inside my session entry (incremental - can see all submissions in!) and all passwords in clear...
I will continue to investigate but help would be very appreciated.
Thanks ;-)

I'm having the same issue. Bleh.

This is identified bug. Solution is specific and described below. You need to modify your connection string inside your connection.js file in config folder as:
my_mongo_cnx: {
    adapter: 'sails-mongo',
    host: '<IP_ADDRESS>', // defaults to `localhost` if omitted
    port: 27017, // defaults to 27017 if omitted
    user: '', // or omit if not relevant
    password: '', // or omit if not relevant
    database: 'my_mongo_db', // or omit if not relevant
    // Fix issue: The issue with v0.10.7 and v0.11.0-1 has been traced to inappropriate connection configurations (PR #277)
    // Walk around below
    poolSize: 5,
    socketOptions: {
        noDelay: true,
        connectTimeoutMS: 0,
        socketTimeoutMS: 0
    }
  },

I'm having problems with PostgreSQL as well. Is this a global thing for all dbs?

Don't know, I only work with Mongo. Best guy to talk about is Mike McNiel
directly ;-)
Le samedi 27 juin 2015, Rob Sawyer<EMAIL_ADDRESS>a écrit :

I'm having problems with PostgreSQL as well. Is this a global thing for
all dbs?
—
Reply to this email directly or view it on GitHub
https://github.com/kasperisager/sails-generate-auth/issues/174#issuecomment-115934450
.

--
--
Mikael Grandsire
Mobile +33.(0)<IP_ADDRESS>.29
Email<EMAIL_ADDRESS>


Date Serialization doesn't work

Laravel Version: 7.0.4
PHP Version: 7.4.3
Database Driver & Version: MySQL 8.0.16

Description:
Date serialization doesn't work.
https://laravel.com/docs/7.x/eloquent-serialization#date-serialization
Steps To Reproduce:

Add this to any model:

protected function serializeDate(DateTimeInterface $date)
{
	return $date->format('Y-m-d H:i:s');
}

Try to return it directly from the controller (to return json)

There's not much to go on from here... can you please fill out the steps to reproduce and tell what you'd expect to happen?

Ok I've updated the steps but it's pretty straightforward to do it (just like documentation states)

This works perfectly well for me:
Route::get('/', function () {
    return User::first();
});

{"id":1,"name":"Mrs. Cleta Flatley IV","email":"nicola.paucek@example.com","email_verified_at":"2020-03-04 10:12:37","created_at":"2020-03-04 10:12:37","updated_at":"2020-03-04 10:12:37"}

Can you first please try one of the support channels below? If you can actually identify this as a bug, feel free to report back and I'll gladly help you out and re-open this issue.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

Thanks!

@driesvints If you return the user instance from the controller, then the date is serialized according to the format rules on the overwritten serializeDate function. However, if you return the date property, eg:
Route::get('/', function () {
    return User::first()->created_at;
});

then the date will be returned in ISO format, ignoring the formatting :disappointed:

Why was this even closed? I'm currently getting this issue.


NoMethodError for 'directory' on Chef 12.0.x

Chef 12.0.x has introduced some issues with resources inside of providers.  I already had PR #35 waiting to be pushed so I added the fix to it.  If anyone has this issue please use this repo:
https://github.com/hulu1522/lvm.git

Provided an alternate approach in https://github.com/opscode-cookbooks/lvm/issues/46 if you'd like to have a look. It includes a fix for Chef12 HWRP's only.


server error when registering a new user: TypeError: Cannot read property '_id' of undefined

I keep getting this error: "User validation failed"
Desktop/yourtube/yourtube/config/token.js:12
sub: user._id,
^
TypeError: Cannot read property '_id' of undefined
Any idea what is wrong with the register function? Thanks

A rough idea is that it's not getting the value of user, the user doesn't exist. Can you please compare it with the source code?

basically it's happening on testing the route with Postman after i downloaded the Yourtube folder and when I test the api's. all the api's work except the register user api. it gives me that error in terminal and in console it says: Failed to load resource: the server responded with a status of 404 (Not Found) http://localhost:3000/api/register
Again I'm working directly on the code downloaded from here. Initially was trying to implement in my own project and was getting the same error. Then I downloaded the project to see how it works and was getting the same error...

Redownloaded again and now the register API works, sorry for issue report, yesterday it was literally driving me nuts, must've been something with my connection while downloading.
Thanks

You ran all the bower and node install commands and also created a ..env file in the root of the project?

OKAY COOL!..I'll close this issue then


How can I use the format in the picture?

Such Beautiful!

> [!NOTE]
> Highlights information that users should take into account, even when skimming.

> [!TIP]
> Optional information to help a user be more successful.

> [!IMPORTANT]
> Crucial information necessary for users to succeed.

> [!WARNING]
> Critical content demanding immediate user attention due to potential risks.

> [!CAUTION]
> Negative potential consequences of an action.

https://github.com/orgs/community/discussions/16925

Thx!!! Love U


MemoryError

Hi,
We are trying to run your code on our machine as it is.
Our machine has a 16GB ram with free memory around 10GB.
Even then we are facing MemoryError in the following line:
train_j,train_i,train_rating = np.loadtxt(train_data_file,dtype=np.int32,skiprows=3,unpack=True)
Can you give us pointers on why and how we could be resolving this issue?
Thanks

The netflix data is several GB. You may need much more memory space because numpy requires that. Try the binary data we already pre-processed for you at here: https://ibm.box.com/s/5vmh77up8reodvihiq0ri66jltg9h4uh

Thank you.
On Wednesday, May 11, 2016, Wei Tan<EMAIL_ADDRESS>wrote:

The netflix data is several GB. You may need much more memory space
because numpy requires that. Try the binary data we already pre-processed
for you at here: https://ibm.box.com/s/5vmh77up8reodvihiq0ri66jltg9h4uh
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/wei-tan/CuMF/issues/5#issuecomment-218635980

Hi,
Sorry to bother you again. Just a quick question.  Can you please tell me
where can I find the actual dataset for Yahoo music? Your repository
doesn't seem like have one. I tried Yahoo website but got some weird
dataset.
Thank you for your time.
On Thu, May 12, 2016 at 4:05 PM, Wei Tan<EMAIL_ADDRESS>wrote:

Closed #5 https://github.com/wei-tan/CuMF/issues/5.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/wei-tan/CuMF/issues/5#event-659103448

http://webscope.sandbox.yahoo.com/catalog.php?datatype=c
Please download the "C15 - Yahoo! Music user ratings of musical tracks, albums, artists and genres, v 1.0 (1.5 Gbyte)" and format it as instructed here: https://github.com/wei-tan/CuMF/blob/master/scripts/prepare_input.ipynb

@isratnisa: we have updated code and readme regarding input data. Take a look if you still want to try cuMF :-)

Of course. Thank you.
On Friday, June 24, 2016, Wei Tan<EMAIL_ADDRESS>wrote:

@isratnisa https://github.com/isratnisa: we have updated code and
readme regarding input data. Take a look if you still want to try cuMF :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/wei-tan/CuMF/issues/5#issuecomment-228466194, or mute
the thread
https://github.com/notifications/unsubscribe/ARmEEsvQRVbzzyu3Rz34GMqt1aILCVDBks5qPEurgaJpZM4IcR7_
.


Publish CLI on NPM and as crate

See https://github.com/cozystack/cozyauth/issues/209#issuecomment-2299145500


Simd negate x64

Need to understand these failures. They don't seem related to the changes in either patchsets.


Vpython isn't rendering in Jupyter notebooks

Applies To

[X] Notebooks (.ipynb files)
[X] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
I was using the vpython library then, the output took too long to show.
What I expected :
I expected it to show the image of the sphere & show the controls
What I got:
The rendering of the object isn't happening. It's taking too long to render a simple object. I waited there for 10minutes but no luck.
Things I had tried:

I tried restarting vscode & my computer
It's working fine actually in jupyter-notebook

VS Code Version
Version: 1.70.0 (user setup) Commit: da76f93349a72022ca4670c1b84860304616aaa2 Date: 2022-08-04T04:38:16.462Z Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: <IP_ADDRESS>-electron.0 OS: Windows_NT x64 10.0.19044
Jupyter Extension Version
v2022.7.1102252217
Jupyter logs
Visual Studio Code (1.70.0, undefined, desktop)
Jupyter Extension Version: 2022.6.1201981810.
Python Extension Version: 2022.10.0.
Workspace folder e:\Sarath\ComputationalPhysics
info 22:29:22.661: ZMQ install verified.
User belongs to experiment group 'jupyterTest'
User belongs to experiment group 'jupyterEnhancedDataViewer'
info 22:29:23.353: LSP Notebooks experiment is disabled -- not in treatment group
info 22:29:23.834: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd011938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594.c:\Program Files\Python39\python.exe.c:\Program Files\Python39\python.exe.-m#ipykernel_launcher' (Python Path: , EnvType: Global, EnvName: '', Version: 3.9.3) for 'e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb' (disableUI=true)
info 22:29:23.839: Creating raw notebook for resource 'e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb'
info 22:29:23.839: Computing working directory for resource 'e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb'
info 22:29:24.146: Starting raw kernel 'Python 3.9.3 64-bit' for interpreter c:\Program Files\Python39\python.exe
info 22:29:24.247: Kernel launching with ports 9000,9001,9002,9003,9004. Start port is 9000
info 22:29:25.13: Experiment status for python is {"enabled":true,"optInto":[],"optOutFrom":[]}
info 22:29:25.259: Registering dummy command feature
info 22:29:25.633: Widget Message: Received IPyWidgetMessages.IPyWidgets_IsReadyRequest
info 22:29:26.837: Preferred Remote kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb is undefined
info 22:29:26.837: Find preferred kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb with metadata {"kernelspec":{"display_name":"Python 3.9.3 64-bit","language":"python","name":"python3"},"language_info":{"codemirror_mode":{"name":"ipython","version":3},"file_extension":".py","mimetype":"text/x-python","name":"python","nbconvert_exporter":"python","pygments_lexer":"ipython3","version":"3.9.3"},"vscode":{"interpreter":{"hash":"11938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594"}}} & preferred interpreter
info 22:29:26.853: Preferred Remote kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb is undefined
info 22:29:26.854: Preferred kernel .jvsc74a57bd011938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594.c:\Program Files\Python39\python.exe.c:\Program Files\Python39\python.exe.-m#ipykernel_launcher is exact match
info 22:29:26.856: PreferredConnection: .jvsc74a57bd011938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594.c:\Program Files\Python39\python.exe.c:\Program Files\Python39\python.exe.-m#ipykernel_launcher found for NotebookDocument: e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb
info 22:29:32.916: Process Execution: > c:\Program Files\Python39\python.exe -m pip list
> c:\Program Files\Python39\python.exe -m pip list
info 22:29:32.940: Process Execution: > c:\Program Files\Python39\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
> c:\Program Files\Python39\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
info 22:29:33.529: Creating daemon process for c:\Program Files\Python39\python.exe with env variables count 59
info 22:29:33.569: Process Execution: > c:\Program Files\Python39\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 4892
> c:\Program Files\Python39\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 4892
info 22:29:34.91: ipykernel version 6.13.0 for c:\Program Files\Python39\python.exe
info 22:29:34.91: ipykernel location c:\Program Files\Python39\lib\site-packages\ipykernel\__init__.py for c:\Program Files\Python39\python.exe
info 22:29:36.968: get interrupthandle daemon
info 22:29:37.6: Process Execution: > c:\Program Files\Python39\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9003 --control=9001 --hb=9000 --Session.signature_scheme="hmac-sha256" --Session.key=b"255d5667-8ed8-4dc2-8a0a-b47054d7d67b" --shell=9002 --transport="tcp" --iopub=9004 --f=c:\Users\Administrator\AppData\Roaming\jupyter\runtime\kernel-v2-4892sD52nc3ZrnLQ.json
> c:\Program Files\Python39\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9003 --control=9001 --hb=9000 --Session.signature_scheme="hmac-sha256" --Session.key=b"255d5667-8ed8-4dc2-8a0a-b47054d7d67b" --shell=9002 --transport="tcp" --iopub=9004 --f=c:\Users\Administrator\AppData\Roaming\jupyter\runtime\kernel-v2-4892sD52nc3ZrnLQ.json
info 22:29:37.6: Process Execution: cwd: e:\Sarath\ComputationalPhysics
cwd: e:\Sarath\ComputationalPhysics
info 22:29:37.904: Execute Cell 0 e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb
info 22:29:38.632: Preferred Remote kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb is undefined
info 22:29:38.632: Find preferred kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb with metadata {"kernelspec":{"display_name":"Python 3.9.3 64-bit","language":"python","name":"python3"},"language_info":{"codemirror_mode":{"name":"ipython","version":3},"file_extension":".py","mimetype":"text/x-python","name":"python","nbconvert_exporter":"python","pygments_lexer":"ipython3","version":"3.9.3"},"vscode":{"interpreter":{"hash":"11938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594"}}} & preferred interpreter
info 22:29:38.634: Preferred Remote kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb is undefined
info 22:29:38.634: Preferred kernel .jvsc74a57bd011938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594.c:\Program Files\Python39\python.exe.c:\Program Files\Python39\python.exe.-m#ipykernel_launcher is exact match
info 22:29:38.639: Preferred Remote kernel for e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb is undefined
warn 22:29:39.532: StdErr from Kernel Process c:\Program Files\Python39\lib\site-packages\traitlets\traitlets.py:2392: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use 'hmac-sha256' instead of '"hmac-sha256"' if you require traitlets >=5.
  warn(
c:\Program Files\Python39\lib\site-packages\traitlets\traitlets.py:2346: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use '255d5667-8ed8-4dc2-8a0a-b47054d7d67b' instead of 'b"255d5667-8ed8-4dc2-8a0a-b47054d7d67b"'.
  warn(

info 22:29:39.736: Kernel Output: NOTE: When using the `ipython kernel` entry point, Ctrl-C will not work.

To exit, you will have to explicitly quit this process, by either sending
"quit" from a client, or using Ctrl-\ in UNIX-like environments.

To read more about this, see https://github.com/ipython/ipython/issues/2049

To connect another client to this kernel, use:
    --existing c:\Users\Administrator\AppData\Roaming\jupyter\runtime\kernel-v2-4892sD52nc3ZrnLQ.json

info 22:29:40.29: Started kernel Python 3.9.3 64-bit., (Raw session started and connected)
info 22:29:40.35: Finished connecting fccb43bb-b370-4389-aa10-f25e7adcefde
info 22:29:40.41: UpdateWorkingDirectoryAndPath in Kernel
info 22:29:40.42: Executing silently Code (idle) = import os\nimport sys\n%cd "e:\Sarath\ComputationalPhysics"\nif os.getcwd() not in sys.path:\nsys.pa
info 22:29:40.71: Executing silently Code (completed) = import os\nimport sys\n%cd "e:\Sarath\ComputationalPhysics"\nif os.getcwd() not in sys.path:\nsys.pa with 1 output(s)
info 22:29:40.72: Waiting for idle on (kernel): b4929bd4-adb2-4a18-a633-366d5bed5dba -> idle
info 22:29:40.72: Finished waiting for idle on (kernel): b4929bd4-adb2-4a18-a633-366d5bed5dba -> idle
info 22:29:40.126: Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
info 22:29:40.126: Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
info 22:29:40.374: Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/Administrator/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/tmp/scripts/f32969acbfda228f24b597936499409070d85932e06ec704017c5f53d5ef18d6/jupyter
info 22:29:40.428: Cell 0 executed with state Success
info 22:29:49.650: Execute Cell 1 e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb
info 22:29:49.801: Cell 1 executed with state Success
info 22:29:55.619: Execute Cell 1 e:\Sarath\ComputationalPhysics\RandomWalk3D.ipynb
info 22:36:2.335: Starting interactive window for resource 'e:\Sarath\ComputationalPhysics\main.py'
info 22:36:2.532: Preferred Remote kernel for Interactive-1.interactive is undefined
info 22:36:2.816: Process Execution: > c:\Program Files\Python39\python.exe -m pip list
> c:\Program Files\Python39\python.exe -m pip list
info 22:36:3.70: Starting Jupyter Session id = 'startUsingPythonInterpreter:.jvsc74a57bd011938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594.c:\Program Files\Python39\python.exe.c:\Program Files\Python39\python.exe.-m#ipykernel_launcher' (Python Path: , EnvType: Global, EnvName: '', Version: 3.9.3) for 'Interactive-1.interactive' (disableUI=false)
info 22:36:3.72: Creating raw notebook for resource 'e:\Sarath\ComputationalPhysics\main.py'
info 22:36:3.72: Computing working directory for resource 'e:\Sarath\ComputationalPhysics\main.py'
info 22:36:3.76: Starting raw kernel 'Python 3.9.3 64-bit' for interpreter c:\Program Files\Python39\python.exe
info 22:36:3.336: Kernel launching with ports 9005,9006,9007,9008,9009. Start port is 9000
info 22:36:3.381: Process Execution: > c:\Program Files\Python39\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
> c:\Program Files\Python39\python.exe -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
info 22:36:3.418: Creating daemon process for c:\Program Files\Python39\python.exe with env variables count 59
info 22:36:3.477: Process Execution: > c:\Program Files\Python39\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 4892
> c:\Program Files\Python39\python.exe -m vscode_datascience_helpers.daemon --daemon-module=vscode_datascience_helpers.kernel_interrupt_daemon -v --ppid 4892
info 22:36:5.321: ipykernel version 6.13.0 for c:\Program Files\Python39\python.exe
info 22:36:5.321: ipykernel location c:\Program Files\Python39\lib\site-packages\ipykernel\__init__.py for c:\Program Files\Python39\python.exe
info 22:36:5.331: get interrupthandle daemon
info 22:36:5.410: Process Execution: > c:\Program Files\Python39\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9008 --control=9006 --hb=9005 --Session.signature_scheme="hmac-sha256" --Session.key=b"1b48348e-b7c6-4287-87ee-e7ff38d98ee8" --shell=9007 --transport="tcp" --iopub=9009 --f=c:\Users\Administrator\AppData\Roaming\jupyter\runtime\kernel-v2-4892I203SNkqf4Jm.json
> c:\Program Files\Python39\python.exe -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9008 --control=9006 --hb=9005 --Session.signature_scheme="hmac-sha256" --Session.key=b"1b48348e-b7c6-4287-87ee-e7ff38d98ee8" --shell=9007 --transport="tcp" --iopub=9009 --f=c:\Users\Administrator\AppData\Roaming\jupyter\runtime\kernel-v2-4892I203SNkqf4Jm.json
info 22:36:5.410: Process Execution: cwd: e:\Sarath\ComputationalPhysics
cwd: e:\Sarath\ComputationalPhysics
warn 22:36:7.37: StdErr from Kernel Process c:\Program Files\Python39\lib\site-packages\traitlets\traitlets.py:2392: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use 'hmac-sha256' instead of '"hmac-sha256"' if you require traitlets >=5.
  warn(

warn 22:36:7.37: StdErr from Kernel Process c:\Program Files\Python39\lib\site-packages\traitlets\traitlets.py:2346: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use '1b48348e-b7c6-4287-87ee-e7ff38d98ee8' instead of 'b"1b48348e-b7c6-4287-87ee-e7ff38d98ee8"'.
  warn(

info 22:36:7.147: Kernel Output: NOTE: When using the `ipython kernel` entry point, Ctrl-C will not work.

To exit, you will have to explicitly quit this process, by either sending
"quit" from a client, or using Ctrl-\ in UNIX-like environments.

To read more about this, see https://github.com/ipython/ipython/issues/2049

To connect another client to this kernel, use:
    --existing c:\Users\Administrator\AppData\Roaming\jupyter\runtime\kernel-v2-4892I203SNkqf4Jm.json

info 22:36:7.383: Started kernel Python 3.9.3 64-bit., (Raw session started and connected)
info 22:36:7.390: Finished connecting fccb43bb-b370-4389-aa10-f25e7adcefde
info 22:36:7.395: UpdateWorkingDirectoryAndPath in Kernel
info 22:36:7.419: Executing silently Code (idle) = import types as _VSCODE_types\nimport os\nimport hashlib as _VSCODE_hashlib\nfrom IPython import get_ip
info 22:36:7.464: Executing silently Code (completed) = import types as _VSCODE_types\nimport os\nimport hashlib as _VSCODE_hashlib\nfrom IPython import get_ip with 1 output(s)
info 22:36:7.464: Waiting for idle on (kernel): 1edf1f7d-1f3a-4c96-8e64-6f412983029e -> idle
info 22:36:7.464: Finished waiting for idle on (kernel): 1edf1f7d-1f3a-4c96-8e64-6f412983029e -> idle
info 22:36:7.476: Executing silently Code (idle) = __file__ = 'e:\\Sarath\\ComputationalPhysics\\main.py'
info 22:36:7.499: Widget Message: Received IPyWidgets_kernelOptions in ScriptManager
info 22:36:7.499: Widget Message: Received IPyWidgetMessages.IPyWidgets_kernelOptions
info 22:36:7.528: Executing silently Code (completed) = __file__ = 'e:\\Sarath\\ComputationalPhysics\\main.py' with 0 output(s)
info 22:36:7.532: Generated code for 1 = <ipython-input-1-1c535e1d5a06> with 5 lines
info 22:36:7.618: Widget Message: data-base-url set to https://file%2B.vscode-resource.vscode-cdn.net/c%3A/Users/Administrator/.vscode/extensions/ms-toolsai.jupyter-2022.6.1201981810/tmp/scripts/f32969acbfda228f24b597936499409070d85932e06ec704017c5f53d5ef18d6/jupyter
info 22:36:7.786: Cell 1 executed with state Success
info 22:36:10.202: Generated code for 2 = <ipython-input-2-265c8fd65f41> with 4 lines
info 22:38:58.607: Disposing kernel .jvsc74a57bd011938c6bc6919ae2720b4d5011047913343b08a43b18698fd82dedb0d4417594.c:\Program Files\Python39\python.exe.c:\Program Files\Python39\python.exe.-m#ipykernel_launcher for notebook Interactive-1.interactive due to selection of another kernel or closing of the notebook
info 22:38:58.607: Dispose Kernel 'Interactive-1.interactive' associated with 'e:\Sarath\ComputationalPhysics\main.py'
info 22:38:58.607: Cancel pending cells
info 22:38:58.621: kill daemon
info 22:38:58.634: Dispose Kernel 'Interactive-1.interactive' associated with 'e:\Sarath\ComputationalPhysics\main.py'
info 22:38:58.647: Cancel all remaining cells true || Idle || undefined
info 22:38:58.647: Cancel pending cells
info 22:38:58.655: Cell 2 executed with state Idle
error 22:38:58.655: Error in waiting for cell to complete Error: Canceled future for execute_request message before replies were done
    at t.KernelShellFutureHandler.dispose (c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:2:32353)
    at c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:2:51405
    at Map.forEach (<anonymous>)
    at y._clearKernelState (c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:2:51390)
    at y.dispose (c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:2:44872)
    at c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:24:251157
    at t.swallowExceptions (c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:29:120529)
    at dispose (c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:24:251135)
    at t.RawSession.dispose (c:\Users\Administrator\.vscode\extensions\ms-toolsai.jupyter-2022.6.1201981810\out\extension.node.js:24:256072)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
warn 22:38:58.658: Cell completed with errors {
  message: 'Canceled future for execute_request message before replies were done'
}

Coding Language and Runtime Version
Python 3.9.3 64bit
Language Extension Version (if applicable)
v2022.14.0
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

@Sarath191181208 Thanks for filing this issue,

please could you check the version of ipywidgets installed in your environment, is it 8 or 7.

import ipywidgets
print(ipywidgets.__version__)

ipywidgets==7.7.1

thanks, can you send the sample code so i can test this at my end

Yeah, sure
from vpython import sphere, canvas
scrn = canvas()
sphere()

closing as a duplicate of https://github.com/microsoft/vscode-jupyter/issues/1477#issuecomment-1158293684


feat(snippets): 增加 css 用户代码片段

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


[BUG] IsADirectoryError: [Errno 21] Is a directory: 'images/.ipynb_checkpoints'

Prerequisites

[X] I have read the documentation.
[X] I have checked other issues for similar problems.

Backend
Colab
Interface Used
UI
CLI Command
No response
UI Screenshots & Parameters
No response
Error Logs

INFO    Namespace(version=False, revision=None, tokenizer=None, image_path='images/', class_image_path=None, prompt='photo of VM', class_prompt=None, num_class_images=100, class_labels_conditioning=None, prior_preservation=None, prior_loss_weight=1.0, resolution=1024, center_crop=None, train_text_encoder=None, sample_batch_size=4, num_steps=500, checkpointing_steps=100000, resume_from_checkpoint=None, scale_lr=None, scheduler='constant', warmup_steps=0, num_cycles=1, lr_power=1.0, dataloader_num_workers=0, use_8bit_adam=None, adam_beta1=0.9, adam_beta2=0.999, adam_weight_decay=0.01, adam_epsilon=1e-08, max_grad_norm=1.0, allow_tf32=None, prior_generation_precision=None, local_rank=-1, xformers=None, pre_compute_text_embeddings=None, tokenizer_max_length=None, text_encoder_use_attention_mask=None, rank=4, xl=None, fp16=True, bf16=None, validation_prompt=None, num_validation_images=4, validation_epochs=50, checkpoints_total_limit=None, validation_images=None, logging=None, train=None, deploy=None, inference=None, username=None, backend='local-cli', token=None, repo_id=None, push_to_hub=None, model='stabilityai/stable-diffusion-xl-base-1.0', project_name='linkedin_pfp_project', seed=42, epochs=1, gradient_accumulation=4, disable_gradient_checkpointing=None, lr=0.0001, log='none', data_path=None, train_split='train', valid_split=None, batch_size=30, func=<function run_dreambooth_command_factory at 0x79cd083fed40>)
INFO    Running DreamBooth Training
WARNING Parameters supplied but not used: inference, train_split, log, version, backend, data_path, valid_split, train, func, deploy
INFO    Dataset: linkedin_pfp_project (dreambooth)

INFO    Saving concept images
INFO    images/IMG_20240120_175659.jpg
INFO    Saving concept images
INFO    images/IMG_20240120_170036.jpg
INFO    Saving concept images
INFO    images/IMG_20240120_180028.jpg
INFO    Saving concept images
INFO    images/.ipynb_checkpoints
Traceback (most recent call last):
File "/usr/local/bin/autotrain", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.10/dist-packages/autotrain/cli/autotrain.py", line 50, in main
command.run()
File "/usr/local/lib/python3.10/dist-packages/autotrain/cli/run_dreambooth.py", line 400, in run
params = dreambooth_munge_data(params, local=self.args.backend.startswith("local"))
File "/usr/local/lib/python3.10/dist-packages/autotrain/cli/utils.py", line 318, in dreambooth_munge_data
params.image_path = dset.prepare()
File "/usr/local/lib/python3.10/dist-packages/autotrain/dataset.py", line 81, in prepare
return preprocessor.prepare()
File "/usr/local/lib/python3.10/dist-packages/autotrain/preprocessor/dreambooth.py", line 93, in prepare
self._save_concept_images(_file)
File "/usr/local/lib/python3.10/dist-packages/autotrain/preprocessor/dreambooth.py", line 75, in _save_concept_images
with open(_file, "rb") as f:
IsADirectoryError: [Errno 21] Is a directory: 'images/.ipynb_checkpoints'

Additional Information
No response

i see a ipynb_checkpoints.ipynb file autogenerated in the directory that can't be deleted

you need to recreate the images/ folder. if you see closed issues, you'll find this being discussed. its not a software issue, the folder gets created by colab when you have images created immediately after creating the space. you can just right click on the folder and delete it (after making hidden files visible)

you need to recreate the images/ folder. if you see closed issues, you'll find this being discussed. its not a software issue, the folder gets created by colab when you have images created immediately after creating the space. you can just right click on the folder and delete it (after making hidden files visible)

correct, i just realized that now myself, i deleted the folder and reuploaded the images, bug went away

thanks @abhishekkrthakur


not

Hi Everyone,
I am using react-native-sqlite-2 plugin and i have created Db successfully and ii also got success in success callback but i am not able to find the created .db file in my android assets folder , even i have created www folder to root directory but i am not able to find db file in that also.
Here is my code..
const db = SQLite.openDatabase({name: "DOT_DB.db", createFromLocation : "~example.db", location: 'Library'}, 200000, this.openCB);
db.transaction(function (txn) {
  other code..........
  });
});