Panic runtime error: invalid memory address or nil pointer deference

Which version of the AzCopy was used?
10.6.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows 10
What command did you run?
azcopy list https://blobstoragelink/projectname
What problem was encountered?
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0xa8bf9a]
goroutine 1 [running]:
github.com/Azure/azure-storage-azcopy/cmd.(*blobFSTraverser).traverse(0xc00088a040, 0x0, 0xc00095a140, 0x12b3ac0, 0x0, 0x0, 0x0, 0x0)
/home/vsts/work/1/s/cmd/zc_traverser_blobfs.go:172 +0x98a
github.com/Azure/azure-storage-azcopy/cmd.(*copyEnumerator).enumerate(0xc00097e180, 0x76f9958200000000, 0xa009ce70614acf80)
/home/vsts/work/1/s/cmd/zc_enumerator.go:629 +0x6e
github.com/Azure/azure-storage-azcopy/cmd.(*cookedCopyCmdArgs).processCopyJobPartOrders(0xc000100380, 0x0, 0x0)
/home/vsts/work/1/s/cmd/copy.go:1142 +0x5ff
github.com/Azure/azure-storage-azcopy/cmd.(*cookedCopyCmdArgs).process(0xc000100380, 0x74, 0xb)
/home/vsts/work/1/s/cmd/copy.go:947 +0xbc
github.com/Azure/azure-storage-azcopy/cmd.init.2.func2(0xc0001ee280, 0xc0001eccc0, 0x2, 0x3)
/home/vsts/work/1/s/cmd/copy.go:1517 +0x1ba
github.com/spf13/cobra.(*Command).execute(0xc0001ee280, 0xc0001ecc00, 0x3, 0x3, 0xc0001ee280, 0xc0001ecc00)
/home/vsts/go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:766 +0x2b1
github.com/spf13/cobra.(*Command).ExecuteC(0x128f800, 0xc00001aa00, 0xc00013bdc8, 0x40d06f)
/home/vsts/go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:852 +0x2f1
github.com/spf13/cobra.(*Command).Execute(...)
/home/vsts/go/pkg/mod/github.com/spf13/cobra@v0.0.3/command.go:800
github.com/Azure/azure-storage-azcopy/cmd.Execute(0xc00001d0a0, 0x16, 0xc00001d0a0, 0x16, 0xc00001d0e0, 0x1c, 0x7fffffff)
/home/vsts/work/1/s/cmd/root.go:140 +0xd6
main.main()
/home/vsts/work/1/s/main.go:82 +0x3cb
How can we reproduce the problem in the simplest way?
By running azcopy list on a blob storage with over 800 files. When I watch the command execute, I see that it manages to output about 900 of them, and then the failure occurs. I have tested the same command on a different blob storage that has 800 files, and I have not encountered any issues there.
Have you found a mitigation/solution?
No.

Duplicate Issue: https://github.com/Azure/azure-storage-azcopy/issues/1208

Closing the duplicate. Tracked at #1208


Break long words into characters

Closes #55
(Actually I think the op of #55 is more about https://github.com/LuisMayo/objection_engine/issues/73#issuecomment-1114305732 rather than the comment below, but anyway...)

render_comment_list([Comment(text_content="音声合成ソフトVOCALOIDをボーカルに用いたオリジナル楽曲を発表している音楽プロデューサー、ボカロP。別名は蜜柑星P。配偶者はクリエイターの夏背。 ")], output_filename="output.mp4")

Before:

After:

(That overflow should be fixed separately)

I'm AFK right now. I'll check in the following days. Thank you very much for the PR, this was something I wanted to do for a while

This does NOT close #55 , it only addresses a comment in that issue.
However this works and fix Japanese and other non-whitespace languages so I'm really grateful for that.
Thanks!

This does NOT close #55 , it only addresses a comment in that issue. However this works and fix Japanese and other non-whitespace languages so I'm really grateful for that. Thanks!

Does #73 covers that?

Well, you opened #73 so you're the one to evaluate whether it's fixed or not. So feel free to close that issue.
I'd think it's fixed yeah

https://github.com/LuisMayo/objection_engine/pull/74#issuecomment-1114307436 is about #73, and I think that's the only remaining part in #55, or is there anything else?

#55 is not about overflow, quite the contrary, sometimes the video split a sentences in two messages even if it would fit in only one message, making messages unnecessary large

Sounds like that's still about comments_to_scene, fixing one should ideally fix another. But let's keep them for now, thanks!

Thank YOU :-)


optional secondary header

One option to do optional secondary header,
alternatively maybe a macro?

Took a brief look while mobile and looks good! Will look at it in some more detail when I get a chance to run it.
Maybe this is my relative inexperience with rust, but do you always need to specify the value of the S generic even if you dont need to parse the secondary header?
Also, this is one part I had trouble with when i tried to add something like this way back when: the CCSDS spec allows either a payload, or a secondary header, or a secondary header and a payload. Is it going to be easy to allow the payload to also be optional, but in a way thay both cannot be none at the same time?
Also ultimately it would be nice to have unit tests to demonstrate usage and validate that it works as intended. I can add those later though.
Thanks so much for your contribution!

Yeah, I'm just working on the tests to see how well it works. At the moment this only works if you specify a Secondary Header.
Re optional payload: I think the payload vector can just be left empty if no payload is expected

Oh also, i noticed theres a phantomdata field and was wondering what the purpose of that was. Should have included that in my last comment too

At the moment this only works if you specify a Secondary Header.

No worries, in that case my plan was to just have a Premade empty header struct that people can pass in if they have no secondary header. Or maybe an overloaded method that does that for you (if rust supports that).

Oh also, i noticed theres a phantomdata field and was wondering what the purpose of that was. Should have included that in my last comment too

It's needed for the lifetime parameter. Otherwise the compiler complains that it is not used.

Or maybe an overloaded method that does that for you (if rust supports that).

From my experience it doesn't, haven't really tried it with functions, but for structs etc it doesn't allow that

Overloading is possible with macros though. Not sure if we can achieve 100% what you're imagining

Nah, overloading was just an idea. No big deal if its not possible.

Well i totally forgot about this. You mentioned you were working on tests. Do you have any unit test cases to help demo the functionality?


Add small integer support to all Mysql, SqlServer and Sqlite

Because PostgresAdapter already had crappy support for small integer it's added to the other adapters aswel. This makes it possible to refactor the crappy code in PostgresAdapter.

Awesome, thanks!


Issue warning to user if provisioning is ended abruptly

As a user, if I close or exit user, show me a warning informing me that my provisioning flow will get cancelled.
Give me option to either resume provisioning or continue to exit from Composer

@JaskeeratBedi-cmk do you mean exiting the Composer application?

@JaskeeratBedi-cmk do you mean exiting the Composer application?

@tonyanziano created this issue after discussing with @luhan2017 & @Wenyi Luo. The idea is to have a modal pop-up whenever user tries to exit Composer, if the provisioning is in progress.
Will have to think about the right interaction if Composer is being used in browser, application...

@tonyanziano created this issue after discussing with @luhan2017 & @Wenyi Luo. The idea is to have a modal pop-up whenever user tries to exit Composer, if the provisioning is in progress.
Will have to think about the right interaction if Composer is being used in browser, application...


Process only undeleted workflows in cls exports

Classification dump workers should only export classifications from workflows that have not been deleted (via the Activatable module). That is, only workflows with activated_state: "active" should have their classifications included.
rationale: some deleted workflows have malformed tasks that occasionally cause exports to fail due to  an un-tracked-down PFE bug. This should be happening anyway, and will clean/speed up exports for researchers.
This should not be confused with active, which is a flag researchers can set. Those classifications are correctly included already.
Describe your change here.
Review checklist

[ ] First, the most important one: is this PR small enough that you can actually review it? Feel free to just reject a branch if the changes are hard to review due to the length of the diff.
[ ] If there are any migrations, will they the previous version of the app work correctly after they've been run (e.g. the don't remove columns still known about by ActiveRecord).
[ ] If anything changed with regards to the public API, are those changes also documented in the apiary.apib file?
[ ] Are all the changes covered by tests? Think about any possible edge cases that might be left untested.

The reason for the broken exports is that PFE bug that borks the task. This doesn't fix that bug or that borked classification, but it seems that classification is on a workflow they deleted anyway. In that sense it's a workaround, but we shouldn't include these anyway and best case scenario we don't see that pop up anymore (and exports are minutely faster!).


work around bug that can cause missing profile information

Fixes #15.

Unfortunately, this workaround does not work in the following case:

user visits public board while not logged in
user logs in

@dwrensha
Take your time, good night, I'll look at it and test after night's sleep. Does this affect both standalone and Sandstorm version?

Outside of Sandstorm, this PR does not completely fix #15 because it fails to handle the case when a use is logging in while visiting a board. In Sandstorm, this PR makes Wekan totally unusable.


kintan is good

This PR will.

improve UX
make Cogent employee happy
get more Kintan stamps

Please read the code of conduct.


AzureCliCredential fails due to Python deprecation message getting mixed with token output

Package Name: azure-identity
Package Version: 1.10.0
Operating System: WSL
Python Version: 3.6.0

Describe the bug
In https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/azure/identity/_credentials/azure_cli.py#L137, the option "stderr": subprocess.STDOUT makes check_output also include stderr in the returned string. I was trying to use this package in a container with a somewhat out-of-date python setup, which caused az account get-access-token to output some warnings to stderr:

Since _run_command's return value is parsed as JSON, this caused an exception and resulted in a somewhat confusing error message:
azure.core.exceptions.ClientAuthenticationError: DefaultAzureCredential failed to retrieve a token from the included credentials.
...

To Reproduce
(Environment-specific, but reasoning for this issue described above)
Expected behavior
AzureCliCredential should work

I haven't got to it yet but I'm happy to send in a PR to fix this... Just need to bounce my thoughts first since I'm quite new to this and haven't looked into it a lot yet:
I think we can change the stderr option of the check_output call to PIPE. This way, in case of any error, the CalledProcessError that gets thrown will have the stderr content, which we can relay in our ClientAuthenticationError exception to provide more information to the user, if something does go wrong. And in my case this will just ignore the python warning message.
Let me know if I should follow this and work on a pull request.

@micromaomao thanks for reporting this! @xiangyan99 @pvaneck could either of you take a look at this?

Thank you @micromaomao.
To help me understand better, in your case, it looks to me az account command outputs warning rather than the token.
How can we make it work?

Hi @xiangyan99 thanks for following up.
The issue is not that az does not output the token - it does, but it also outputs a warning (probably caused by a third-party library), which causes the JSON parsing in azure-identity to fail.
I have suggested a solution above. If the team agrees that this is a sensible approach I'm happy to make a pull request.

@micromaomao Thanks for the confirmation. Please feel free to propose a PR and thanks for your contribution.


intent returned for all words spoken  Bug: 🐛

### Using @speechly/browser-client

Gave one sample intent like short_notes with list take_notes and tried saying other sample words (something else) which doesn't match to the given intent, but got response for same intent.
Also got more than one response for single voice input in speechly dashboard app console as well as in my local machine.
Note:  These are done with starter pricing in speechly

For Reference: check the below images

Can you try to sort out this??

@thiyaga05
About getting an intent for an "unrelated" utterance:
Yes, this is the way our system is currently designed to work. That is, it does not distinguish between related and unrelated utterances, but considers everything the user says as potentially relevant, and thus maps every utterance to one of the intents.
If you need to catch unrelated utterances, you must design a separate "catchall" intent that matches these. Our recommended way to do this is to collect a number (~100 or so) of such utterances, try to make them as diverse as possible but not overlapping with our actual intents, and include these as part of your configuration.
About receiving multiple responses:
This is also how our API is designed to work. Rather than returning a single response, our API sends back a stream of responses that represent an accumulated view of the speech recognition results. This is to allow the UI to respond as quickly as possible after the user has started speaking. While we recommend updating the UI as new responses are received, you can also wait until the ongoing "segment" object has its final flag set to true, and only read the fields of the segment at this point.


cant start docker 1.10 with ipv6 disabled via ipv6.disable=1 and an existing bridge with an IP

Issue description
Docker 1.10 fails to run if you are using ipv6.disable=1 in your boot config and the docker0 bridge already exists. This is due to an upstream docker issue, https://github.com/docker/libnetwork/issues/892, so I'm putting it here for documentation sake.
Steps to reproduce
Set boot.kernelParams = [ "ipv6.disable=1" ];
Set virtualisation.docker.enable = true;
$ docker --version
Docker version 1.10.3, build a34a1d59
Reboot, start docker. Stop docker, then restart docker. Docker will not start:
INFO[0000] Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be used to set a preferred IP address  FATA[0000] Error starting daemon: Error initializing network controller: Error creating default "bridge" network: Failed to setup IP tables, cannot acquire Interface address: Interface docker0 has no IPv4 addresses
Can be fixed, temporarily, by using  ip link set docker0 down; brctl delbr docker0; before starting docker.
Technical details

System:  16.03.1242.c5cbda2 (Emu)
Nix version:  nix-env (Nix) 1.11.2
Nixpkgs version: 16.03.1242.c5cbda2

We have docker 1.12 in unstable and nixos 16.09, do you have the same issue if you update to latest docker?

@offlinehacker Nope! Thanks.


UI Fixes

The UI is currently pretty cool (uses CSS grid, is responsive, etc) but there are still some weird things. Especially on small laptop screens.

2d3f3bcbc6d0d9907f6a188bbe2ff4ccbab9b8f3 may fix some of the issues I'm seeing, will test out further before closing.

This seems okay now on my smaller work laptop so closing, maybe more things in the future will come up


Problem running Project1 out of the box

Dear FDSE Team,
I am a researcher from Paderborn, Germany, currently investigating control schemes of Rayleigh Benard Convection systems.
Currently I'm using a python package called shenfun for the fluid dynamics simulation (https://shenfun.readthedocs.io/en/latest/rayleighbenard.html) but I want to see if I can use Oceananigans to have a julia-only solution and hopefully get a speed up aswell.
Now, after searching through the Oceananigans Discussions I stumbled upon a post by @johnryantaylor advertising this repository and I found that Project 1 seems really similar to the Rayleigh Benard problem stated in the link above (what is temperature in the Rayleigh Benard system looks exactly like buoyancy in Project 1 when looking at the equations).
Now, I am by no means a fluid dynamics expert so it is an open question to me if I can really just treat buoyancy like temperature and go with it.
However, I was confronted with problems when trying to run gravitycurrent.jl.
These functions are defined as 3 dimensional:

The comments in the file and the readme also imply a 3D system but julia tries to access these functions with only two arguments:

After inspection it looks to me (keep in mind that I am a newbie so I am not 100% sure) that the set up grid is in fact 2D:

After manually defining 2D versions of said functions the whole gravitycurrent.jl ran through.
There was still another issue in plot_gravitycurrent.jl where I had to change b_ic[:, 1, 1] to b_ic[:, 1, 1, 1] in line 34 but that just looks like they changed the conventions of FieldTimeSeries.
Are/were you aware of this situation?
Is my fix right or did the error appear because I did something wrong?
Best
Jan

Hi @janstenner, thanks for the message.  This is due to a change in the Oceananigans interface.  When we wrote the projects the initial conditions always had to be 3D functions in Oceananigans, even when running 2D problems.  This has since changed.  I can update the scripts accordingly.  In the meantime, if you run activate and instantiate from the package manager inside the FDSE directory, the code should work as written since that will ensure that it uses the version of Oceananigans for which the code was written.
As a more general comment, 3D Rayleigh-Benard convection is definitely possible with Oceananigans, and if you have access to a GPU then you should see a significant speed-up.

Thank you so much for the quick reply.
Yes, I did run the files in my own Project with the newest julia and Oceananigans versions available.
Your explanation makes total sense now.
3D Rayleigh Benard would be totally great - but that is a future thing for me. First I want to set up a 2D version and still wonder if the buoyancy b is as easily interchangable (or interpretable as) the temperature T. Do you by chance know something about that?
If not I will just experiment away and talk to some other people who can hopefully shed some light into that for me.
By the way thank you for the great project you have here!

When you non-dimensionalize the equations buoyancy and temperature and interchangeable.  Alternatively, you can use temperature in Oceananigans with a linear or nonlinear equation of state (you can even easily write your own equation of state).

Thank you so much for confirming that!
Best wishes!


Prompt user for input if none is given

when a user does not respond to prompt re-send prompt for input. limit to 2 or 3 times.

Please not this functionality only works on smart speakers.

JB


Is it possible to preventDefault on dp.change ?

Is it possible to preventDefault on dp.change ?

+1

There are all events fire only notifications. You cannot change data indside your handlers.

Hi, somehow this would apply for eonasdan dp.change event too.
https://stackoverflow.com/questions/24251955/preventdefault-not-working-for-change-event
this should be close as is not a error on the code but on the design itself of JavaScript

I understand now. But, how can i prevent that dp.change fires twice? I'm using the version 4.17.47.
Thanks in advance!

Use global variable.
var isFirstTime = false;
Inside your event
if (isFirstTime !== true) {
   isFirstTime = true;
}

Hi, I’ll be closing issues that have been answered by the community.


Custom camera icons not showing in actual color of image

[x] I have verified there are no duplicate active or recent bugs, questions, or requests
[x] I have verified that I am using the latest version of Material Camera.
[x] I have given my issue a non-generic title.

Include the following:

Material Camera version: 0.4.4
Device OS version: 6.0.1
Device Manufacturer: Samsung
Device Name: Galaxy S7 Edge

Also, please wrap Java with correct syntax highlighting.
MaterialCamera materialCamera = new MaterialCamera(this)
            .showPortraitWarning(false)
            .countdownSeconds(10f)
            .autoSubmit(false)
            .allowRetry(true)
            .retryExits(true)
            .iconRecord(R.drawable.recordbigwebstart)
            .iconStop(R.drawable.recordbigweb)
            .qualityProfile(MaterialCamera.QUALITY_720P)
            .primaryColor(getResources().getColor(R.color.colorPrimary))
            .defaultToFrontFacing(true);
    materialCamera.start(CAMERA_RQ);

Reproduction Steps
I was working at some point but suddenly it just changed.

Set custom icon with color, for ex. Red
Run and the color of the icon won't be like the image

Expected Result
Actual image saved from photoshop as png
Actual Result
image is all white. The images are for start recording and stop recording. Tried different sizes, all the same

Hey @franklinexpress: I can take a look at this sometime in the next couple weeks. If you wouldn't mind uploading an example icon so I don't have to make one for testing that would be helpful. Thanks!

I just don't have much time to get into it now, I moved on to create my own camera but I'm still curious to see the end result of this, thanks!

This is currently intended behavior, icons are tinted white or black depending on the "lightness" of your accent color. That's kind of part of Material philosophy (action buttons).

Right, but don't want to follow that "philosophy", I was wondering where I could make the changes, wen't through the code for bit but no avail

https://github.com/afollestad/material-camera/blob/cde4b0c3f3317445e6ebf3995022e7f417b833cf/library/src/main/java/com/afollestad/materialcamera/internal/BaseCameraFragment.java#L102


Fix error in code example for custom Async handlers

There is an error in code example for adding a custom async handler that will actually not activate async handling at all.
Also, my sublime config removed some blank spaces at ends of lines, hope that is ok.

Hey @radanskoric, thank you for this!!

np, glad to help :)


[Feature Reqest] Add dump crash log

Will be easier to share crash log directly for troubleshooting

Very useful, especially on the beta version for users who find difficult to get the logcat (also pc needed)


VR: Add device resolution to HMD. Init at startup.

BREAKING: bgfx::getHMD() now returns a valid pointer
if the VR runtime was initialized. This is different
from existing behavior where getHMD returned NULL until
a bgfx::reset(... BGFX_RESET_HMD) was issued. Applications
must now check HMD::flags for the current state of the VR
runtime. The following code has the code change required:
const bgfx::HMD* hmd = bgfx::getHMD() if (NULL != hmd)
becomes:
const bgfx::HMD* hmd = bgfx::getHMD() if (NULL != hmd && 0 != (hmd->flags & BGFX_HMD_RENDRERING)) { 	// rendering logic }
See the updated examples for details.
This allows applications to create the appropriately
sized back buffer for the HMD device by using the new device
resolution fields HMD::deviceHeight and HMD::deviceWidth.
These values report the pixel resolution of the attached
HMD hardware.
This also allows applications to query the reported HMD
resolution immediately after bgfx::init. This prevents
the device from being cycled which generates rendring
artifacts on startup - namely flashing back to a black
screen and reseting the Health+Warning disaply.
This involves initialization the ovrHmd device on
initialization, but deferring rendering until
postReset has been called. This adds an addiional
memory overhead of 32k to builds defining BGFX_CONFIG_USE_OVR.
The overhead for current builds is ~1.9MB for calls to
ovr_Initialize, so the additional overhead is pretty
trivial (+1.8%)

This is a great change, thank you!


Test reports are not being published to Azure Pipelines

Tests are running in the pipeline, but results are not being published for reporting. Azure Pipelines provides excellent reporting capabilities that help you with:
Easy analysis and troubleshooting for failed tests - the test reports show all relevant details (error message, stack trace, failing for how long, etc.) to make it easy to analyze failed tests.
Timing analysis - Test duration information helps you figure out long running tests, so that you can improve test collateral to speed up the pipelines.
Build-on-build trends/analytics help you get rich insights, for e.g., easily identify top failing tests.
The fix required is to generate a test results trx files while running tests(via dotnet test) and update the YAML file to publish these test reports.
I am a Software Engineer on the Azure Pipelines team and will be happy to raise a PR to address this.

@vagisha-nidhi thanks, can't wait to see your PR

The test report looks nice. Thank you


Update some CI servers to java 17

Android has a bug https://github.com/flutter/flutter/issues/125181 where the latest AGP (google vended tooling for building android apps) does not work with the latest 3.7, 3.10 or master.
To use the latest AGP version the host machine must have java 17 which was bundled with Android Studio Flamingo released last week to stable.
While working on a fix I discovered that our build servers have java 11 and cannot build my patch.

It is possible that deployment of this bug is blocked by
https://github.com/flutter/flutter/issues/122213
and
https://github.com/flutter/flutter/issues/123636

It appears that this bug is blocking test adoption of AGP version 8.0. There are some packages (webview_flutter_android) that have updated to AGP version 8 but their example apps have not and the examples are what are used to tests.
Notes
Java 17 required by AGP 8.0
https://developer.android.com/build/releases/gradle-plugin#jdk-17-agp
Java 11 bytecode started shipping in AGP 7.4.
https://developer.android.com/build/releases/past-releases/agp-7-4-0-release-notes#jvm-11-bytecode

Example failed build
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8783182333869110145/+/u/run_test.dart_for_build_tests_shard_and_subshard_1_3/test_stdout
A problem occurred evaluating project ':app'.
[        ] > Failed to apply plugin 'com.android.internal.application'.
[        ]    > Android Gradle plugin requires Java 17 to run. You are currently using Java 11.
[        ]       Your current JDK is located in /b/s/w/ir/cache/java
[        ]       You can try some of the following options:
[        ]        - changing the IDE settings.
[        ]        - changing the JAVA_HOME environment variable.
[        ]        - changing `org.gradle.java.home` in `gradle.properties`.

Assigned and priority set by conversation with @reidbaker

New instances for the following packages have been created with openjdk 17 and tagged with version:17:
https://chrome-infra-packages.appspot.com/p/flutter/java/openjdk
https://chrome-infra-packages.appspot.com/p/flutter_internal/java/openjdk
I ran a sampling of builds with these packages to sanity check them, and it seems to be working. There are a couple of failures that have been send to @reidbaker for further analysis.
It should be ready to use for testing/deployment.

We have had a series of flakes that I think have been resolved but now some servers have been able to be run with java 17 and at least one windows, linux and mac machine is amongst the group. Resolving.


SPUserProfileSyncConnection: fails to select specific OU

Details of the scenario you tried and the problem that is occurring
I am trying to configure connection with only specific OUs. For example, I am trying to sync only "Production Users" OU. However, as result, I have all domain OUs added to connection:

Verbose logs showing the problem
VERBOSE: [batch01]: LCM:  [ Start  Resource ]  [[SPUserProfileSyncConnection]contoso]
VERBOSE: [batch01]: LCM:  [ Start  Test     ]  [[SPUserProfileSyncConnection]contoso]
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Testing for user profile service
 sync connection contoso_local
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Getting user profile service
sync connection contoso_local
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Executing as the local run as
user contoso\_spadm16
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Leaving BeginProcessing Method
of Get-SPServiceApplication.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Leaving ProcessRecord Method of
Get-SPServiceApplication.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Leaving EndProcessing Method of
Get-SPServiceApplication.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Getting SPContext for Proxy
group SPServiceApplicationProxyGroup
VERBOSE: [batch01]: LCM:  [ End    Test     ]  [[SPUserProfileSyncConnection]contoso]  in 5.4220 seconds.
VERBOSE: [batch01]: LCM:  [ Start  Set      ]  [[SPUserProfileSyncConnection]contoso]
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Setting user profile service
sync connection contoso_local
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] UseSSL is not specified.
Assuming that SSL is not required.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] UseDisabledFilter is not
specified. Assuming that disabled accounts should not be filtered.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Executing as the local run as
user contoso\_spadm16
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Importing function
'Get-SPDSCADSIObject'.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Importing function
'Get-TargetResource'.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Importing function
'Set-TargetResource'.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Importing function
'Test-TargetResource'.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Leaving BeginProcessing Method
of Get-SPServiceApplication.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Leaving ProcessRecord Method of
Get-SPServiceApplication.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Leaving EndProcessing Method of
Get-SPServiceApplication.
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Getting SPContext for Proxy
group SPServiceApplicationProxyGroup
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] retrieving
UserProfileConfigManager
VERBOSE: [batch01]:                            [[SPUserProfileSyncConnection]contoso] Creating a new connection
VERBOSE: [batch01]: LCM:  [ End    Set      ]  [[SPUserProfileSyncConnection]contoso]  in 20.0440 seconds.

Suggested solution to the issue
none
The DSC configuration that is used to reproduce the issue (as detailed as possible)
            SPUserProfileSyncConnection contoso
            {
                UserProfileService      = "User Profile Service Application"
                Forest                  = "contoso.local"
                Name                    = "contoso_local"
                ConnectionCredentials   = $SPADSyncAccountCredential
                IncludedOUs             = @("OU=Production Users,DC=contoso,DC=local")
                ExcludedOUs             = @("CN=Computers,DC=contoso,DC=local")
                Force                   = $false
                ConnectionType          = "ActiveDirectory"
                PsDscRunAsCredential    = $SPInstallAccountCredential
            }

The operating system the target node is running
OsName               : Microsoft Windows Server 2012 R2 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsBuildLabEx    : 9600.19153.amd64fre.winblue_ltsb.180908-0600
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

Version of SharePoint that is used (e.g. SharePoint 2016)
SharePoint 2013
Version and build of PowerShell the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.14409.1005
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1005
CLRVersion                     4.0.30319.34014
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Version of the DSC module that was used ('dev' if using current dev branch)
2.6

Seems like even though it shows all OUs marked, it only exports desired OUs:

So this looks like a UI issue. We will have to check if there is some additional step required to update the UI correctly.


Receiving Failed to Synchronize Cache for Repo errors when running docker build after gitclone.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to https://github.com/vmware/tern#getting-started-with-docker
Run the first step to git clone the repo to local. Navigate to /tern/ directory.
Run the following command from step 2 (Build the Docker image)
docker build -t ternd .
See error

Error in terminal
$ docker build -t ternd .
Sending build context to Docker daemon  10.29MB
Step 1/6 : FROM photon:3.0
 ---> 63da4c9ea81a
Step 2/6 : RUN tdnf remove -y toybox && tdnf install -y tar findutils attr util-linux python3 python3-pip python3-setuptools git
 ---> Running in 8b0473962454
curl#7: Couldn't connect to server
Error: Failed to synchronize cache for repo 'VMware Photon Linux 3.0 (x86_64)' from 'https://dl.bintray.com/vmware/photon_release_3.0_x86_64'
curl#7: Couldn't connect to server
Error: Failed to synchronize cache for repo 'VMware Photon Extras 3.0 (x86_64)' from 'https://dl.bintray.com/vmware/photon_extras_3.0_x86_64'
curl#7: Couldn't connect to server
Error: Failed to synchronize cache for repo 'VMware Photon Linux 3.0 (x86_64) Updates' from 'https://dl.bintray.com/vmware/photon_updates_3.0_x86_64'
Error(1030) : The operation would result in removing the protected package : tdnf
Refreshing metadata for: 'VMware Photon Linux 3.0 (x86_64)'
Disabling Repo: 'VMware Photon Linux 3.0 (x86_64)'
Refreshing metadata for: 'VMware Photon Extras 3.0 (x86_64)'
Disabling Repo: 'VMware Photon Extras 3.0 (x86_64)'
Refreshing metadata for: 'VMware Photon Linux 3.0 (x86_64) Updates'
Disabling Repo: 'VMware Photon Linux 3.0 (x86_64) Updates'
The command '/bin/sh -c tdnf remove -y toybox && tdnf install -y tar findutils attr util-linux python3 python3-pip python3-setuptools git' returned a non-zero code: 6

Expected behavior
I expected to be able to build the solution.
Environment you are running Tern on
Enter all that apply
Docker Desktop (Windows) <IP_ADDRESS>

Container OS: Linux
Python version: 3.82

Please attach files if they exist
n/a

FWIW as a data point, I was not able to reproduce this issue on my Ubuntu VM even when running docker build --no-cache -t ternd . in order to force a metadata update (i.e. re-pulling the RPMs to install)

Closing as we determined this was an issue with the local docker client not being able to connect externally rather than an issue with Tern (or Photon).


az webpubsub client start errors with TypeError: As of 3.10, the *loop* parameter was removed from Lock() since it is no longer necessary

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Related command
$ az webpubsub client start --name twitch-pubsub --resource-group twitchRG --user user1 --hub-name hub1
The command failed with an unexpected error. Here is the traceback:
As of 3.10, the *loop* parameter was removed from Lock() since it is no longer necessary
Traceback (most recent call last):
  File "/opt/az/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 663, in execute
    raise ex
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 697, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 333, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/home/anthony/.azure/cliextensions/webpubsub/azext_webpubsub/client.py", line 58, in start_client
    asyncio.get_event_loop().run_until_complete(connect(token['url']))
  File "/opt/az/lib/python3.10/asyncio/base_events.py", line 646, in run_until_complete
    return future.result()
  File "/home/anthony/.azure/cliextensions/webpubsub/azext_webpubsub/client.py", line 43, in connect
    async with websockets.connect(url, subprotocols=['json.webpubsub.azure.v1']) as ws:
  File "/home/anthony/.azure/cliextensions/webpubsub/websockets/client.py", line 517, in __aenter__
    return await self
  File "/home/anthony/.azure/cliextensions/webpubsub/websockets/client.py", line 535, in __await_impl__
    transport, protocol = await self._create_connection()
  File "/opt/az/lib/python3.10/asyncio/base_events.py", line 1089, in create_connection
    transport, protocol = await self._create_connection_transport(
  File "/opt/az/lib/python3.10/asyncio/base_events.py", line 1107, in _create_connection_transport
    protocol = protocol_factory()
  File "/home/anthony/.azure/cliextensions/webpubsub/websockets/client.py", line 69, in __init__
    super().__init__(**kwargs)
  File "/home/anthony/.azure/cliextensions/webpubsub/websockets/protocol.py", line 235, in __init__
    self._drain_lock = asyncio.Lock(
  File "/opt/az/lib/python3.10/asyncio/locks.py", line 78, in __init__
    super().__init__(loop=loop)
  File "/opt/az/lib/python3.10/asyncio/mixins.py", line 17, in __init__
    raise TypeError(
TypeError: As of 3.10, the *loop* parameter was removed from Lock() since it is no longer necessary

Extension name (the extension in question)
webpubsub
Description of issue (in as much detail as possible)
appears this just needs an upgrade
I was able to work around by running (I'm in azure cloud shell):
/opt/az/bin/python3.10 -m pip install websockets --upgrade --target ~/.azure/cliextensions/webpubsub/

route to CXP team


Test selfdrive/selfdrived

selfdrived wasn't getting tested as it was left out of testpaths, we should really remove that.
Fix in: https://github.com/commaai/openpilot/pull/33571

We should just remove the hard-coded selfdrive paths, but that relies on https://github.com/pytest-dev/pytest-cpp/pull/147 for some catch2 tests


Google Maps now requires an API Key

Google has now made it a requirement that an API Key be used with the placement on maps on new sites, this changed on the 22nd of June - http://googlegeodevelopers.blogspot.com.au/2016/06/building-for-scale-updates-to-google.html
The current Google Map block uses the API keyless, which is already causing problems:
http://www.concrete5.org/community/forums/usage/google-maps-not-working/
Existing placements of maps should continue to work keyless though.
As it's a sitewide setting, the input of an API key will be needed somewhere in the dashboard, the google map block updated to use the key when it adds the google maps script to the footer, and probably some sort of warning/error message if the map is placed with an API key.

We probably should shoot to get this into 5.7.x as well as v8.

How much needs to be on this one dashboard page? In other words, do we consider capturing API keys for multiple Google products (Maps, YouTube, Google+, reCAPTCHA), multiple vendors, or solely Google Maps?

I would think we'd fall back to doing this the way we did it in 5.6 and
earlier – where the API key is some kind of config value or stored in the
block only. Something easy. I really don't like the idea of having a
"Google-specific" page in our dashboard (that isn't part of a specific
add-on, of course.)
On Tue, Jun 28, 2016 at 7:59 AM, Corey Reed<EMAIL_ADDRESS>wrote:

How much needs to be on this one dashboard page? In other words, do we
consider capturing API keys for multiple Google products (Maps, YouTube,
Google+, reCAPTCHA), multiple vendors, or solely Google Maps?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/concrete5/concrete5/issues/3986#issuecomment-229076194,
or mute the thread
https://github.com/notifications/unsubscribe/AAgNwSEHbuJlry-gFbJPLu1vZudCLs-Sks5qQTbQgaJpZM4I-Qd9
.

What about a single page for API-keys?

That's certainly reasonable – but youd' need to build it in such a way that
keys can be added to this page programmatically, and probably grouped
together (So you'd have your various Google keys grouped together, etc...)
Actually it occurs to me you might be able to do this with smart
configuration... If we had app.api_keys as a config value, you could make
the next array key be the group, and the next key the key...
so if you had
app.api_keys.flickr.photos
app.api_keys.twitter.twitter
app.api_keys.google.maps
app.api_keys.google.charts
It would list
Flickr
Photos
[       ]
Google
Maps
[    ]
Charts
[    ]
Twitter
Twitter
[     ]
And all you'd have to do as a package is just define a new empty
configuration key in the right format, and it'd be added to the page.
Thoughts? @korvinszanto ?
On Tue, Jun 28, 2016 at 8:42 AM, a3020<EMAIL_ADDRESS>wrote:

What about a single page for API-keys?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/concrete5/concrete5/issues/3986#issuecomment-229089943,
or mute the thread
https://github.com/notifications/unsubscribe/AAgNwVHHEKvf12uSgELB_aqtcGejATZ8ks5qQUDKgaJpZM4I-Qd9
.

I guess if we set up a generic API Keys dashboard, like @a3020 suggested, we'd need a way to add/register new options. Then you'd want a way for add-ons to register new dependencies with the dashboard.

@aembler You beat me to it with your smart config suggestion. I like it! Guess we'll see if @KorvinSzanto shoots some holes in it. ;)

+1 for generic API key config page.

why not build a config page for more than API keys? I keep on getting request from people who have a hard time figuring out where to set the email sender (for example). Mark certain parameters as advanced, show them only if requested and so on. That way we could also set an API url, not just the keys.

I keep on getting request from people who have a hard time figuring out where to set the email sender (for example)

Tell them to use Handyman :wink:
It allows you to configure all the hidden configuration parameters (and that's why it's paid, I have to always keep an eye on every core change).

I would pay you some money if we could integrate that into the core!

If it gets integrated into the core, I'd lose the incentive to keep it up-to-date :wink:
BTW, I think it's a decision that's up to the core team: many people miss a configuration page like this (ie a kind of a firefox about:config for c5)

I like the idea of a configuration page that exposes all the configuration settings through the dashboard.
Handyman does look excellent.

I think @mlocati 's addon is a good one; I don't see us adding a page that duplicates its functionality into the core. However, the fact remains that we need some place to store this Google maps API key and this is a problem today.
I vote that we fix this problem (in develop and in the 5.7.x) branch ASAP by adding an API key field back to the Google Maps block like we had it before, and fixing the JS so that it works again. Make this API be stored in the config value 'app.api_keys.google.maps'. Then, later we can add a dashboard page that lists all the API keys found in the namespace like I mentioned above – that isn't a requirement to get this thing moving, so let's not wait and debate while concrete5 effectively can't place a google map on a new site.

Although this is very portion of the entire concrete5 site, I wonder if concrete5 has multi-domain add-ons.
Maybe we could have an option that Google Map can choose to use API key individually stored in block or globally stored.
Perhaps, we won't worry about it for 5.7.x, but we'll think about it at Ver.8.

any plans for users of 5.6?


python311Packages.openhomedevice: 2.0.2 -> 2.1

Diff: https://github.com/bazwilliams/openhomedevice/compare/2.0.2...2.1
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

2 packages built:

python310Packages.openhomedevice
python311Packages.openhomedevice


Now Deployment Error

Node - 10.15.3
Npm - 6.13.0
Now version - 16.5.2
I have a mono repo app with svelte and @now/node backend in the api folder. Development with now dev works fine but deploying with now doesnt and the deplyment fails.
Here are what the logs says....

03:09:36 PM | Installing build runtime...
-- | --
03:09:37 PM | Build runtime installed: 922.221ms
03:09:38 PM | Installing build runtime...
03:09:38 PM | Looking up build cache...
03:09:39 PM | Build cache found [10.53 MB, 11610 files]
03:09:39 PM | Build cache unpacked: 736.131ms
03:09:39 PM | Build runtime installed: 835.653ms
03:09:39 PM | Installing dependencies...
03:09:39 PM | Installing build runtime...
03:09:39 PM | Looking up build cache...
03:09:40 PM | Build cache found [10.53 MB, 11610 files]
03:09:40 PM | Build cache unpacked: 884.162ms
03:09:40 PM | Build runtime installed: 1065.469ms
03:09:41 PM | Installing build runtime...
03:09:41 PM | Installing dependencies...
03:09:41 PM | Looking up build cache...
03:09:42 PM | Build cache found [10.53 MB, 11565 files]
03:09:42 PM | Build cache unpacked: 890.959ms
03:09:42 PM | Build runtime installed: 1082.285ms
03:09:43 PM | Installing build runtime...
03:09:43 PM | Installing dependencies...
03:09:43 PM | Looking up build cache...
03:09:44 PM | Build runtime installed: 1039.344ms
03:09:44 PM | npm ERR! path /zeit/304efe5c/node_modules/sequelize
03:09:44 PM | npm ERR! code EISGIT
03:09:44 PM | npm ERR! git /zeit/304efe5c/node_modules/sequelize: Appears to be a git repo or submodule.
03:09:44 PM | npm ERR! git     /zeit/304efe5c/node_modules/sequelize
03:09:44 PM | npm ERR! git Refusing to remove it. Update manually,
03:09:44 PM | npm ERR! git or move it out of the way first.

Ideally if am able to locate the /zeit folder in question, i will be able to remove all the sub git folders. Where is it located ?

Hi Kofi,
This looks like a bug with sequelize according to https://github.com/sequelize/sequelize/issues/11143
Can you try updating that dependency? npm i sequelize@latest

@styfle Thanks for the response. However doing that still give me the same error

Installing build runtime...
--
03:48:52 PM | Build runtime installed: 1129.107ms
03:48:52 PM | Looking up build cache...
03:48:53 PM | Installing build runtime...
03:48:53 PM | Build cache found [10.70 MB, 11780 files]
03:48:53 PM | Build cache unpacked: 755.945ms
03:48:54 PM | Installing dependencies...
03:48:58 PM | npm ERR! path /zeit/775ed094/node_modules/sequelize
03:48:58 PM | npm ERR! code EISGIT
03:48:58 PM | npm ERR! git /zeit/775ed094/node_modules/sequelize: Appears to be a git repo or submodule.
03:48:58 PM | npm ERR! git     /zeit/775ed094/node_modules/sequelize
03:48:58 PM | npm ERR! git Refusing to remove it. Update manually,
03:48:58 PM | npm ERR! git or move it out of the way first.
03:48:58 PM | npm ERR! A complete log of this run can be found in:
03:48:58 PM | npm ERR!     /zeit/.npm/_logs/2019-11-14T15_48_58_817Z-debug.log
03:48:58 PM | Error: Exited with 1
03:48:58 PM | at ChildProcess.child.on (/zeit/9ad14beef95a56a0/.build-utils/.builder/node_modules/@now/static-build/dist/index.js:23760:24)
03:48:58 PM | at emitTwo (events.js:126:13)
03:48:58 PM | at ChildProcess.emit (events.js:214:7)
03:48:58 PM | at maybeClose (internal/child_process.js:925:16)
03:48:58 PM | at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
03:48:58 PM | worker exited with code 20 and signal null

Can you post the contents of package.json?

@styfle sure
{
  "name": "svelte-app",
  "version": "1.0.0",
  "devDependencies": {
    "rollup": "^1.12.0",
    "rollup-plugin-commonjs": "^10.0.0",
    "rollup-plugin-livereload": "^1.0.0",
    "rollup-plugin-node-resolve": "^5.2.0",
    "rollup-plugin-svelte": "^5.0.3",
    "rollup-plugin-terser": "^5.1.2",
    "svelte": "^3.0.0"
  },
  "dependencies": {
    "@beyonk/svelte-notifications": "^2.0.3",
    "bulma": "^0.8.0",
    "node-sass": "^4.13.0",
    "pg": "^7.12.1",
    "pg-hstore": "^2.3.3",
    "rollup-plugin-postcss": "^2.0.3",
    "sequelize": "4.44.2",
    "sequelize-cli": "^5.5.1",
    "sirv-cli": "^0.4.4"
  },
  "scripts": {
    "build": "rollup -c",
    "dev": "rollup -c -w",
    "start": "sirv public --single",
    "start:dev": "sirv public --single --dev"
  }
}

That looks correct 🤔
You could try to delete node_modules and package-lock.json and then run npm install again to regenerate the lock file.
If that doesn't work, there is an even newer version of sequelize 4.44.3 you could try.

Okay @styfle will try that and see.

That looks correct 🤔
You could try to delete node_modules and package-lock.json and then run npm install again to regenerate the lock file.
If that doesn't work, there is an even newer version of sequelize 4.44.3 you could try.

Still the same error result. Error still persist for higher version of Sequelize like 5. I feel its the way the dependencies are being pulled in or perhaps there's a build cache where zeit is pulling sequelize  and the other dependencies from.

You're right, there is a build cache for the node_modules directory.
You can skip the cache by using the now --force flag or renaming your project.

@styfle Yes it worked!!. But one small problem my lamda functions are not working or perhaps i need to reference them fully now ?

You're right, there is a build cache for the node_modules directory.
You can skip the cache by using the now --force flag or renaming your project.

Are you lambda functions in the /api folder? What is not working?

@styfle yes they are. My svelte app cant access them but when i use the zeit dashboard to invoke the lamdas i get the response in the browser correctly

If it works when visiting the function url directly /api/users for example, then it sounds like your fetch/xhr URL is incorrect.

@styfle i cant even view it directly in the browser unless i view source and invoke the lambda on the zeit dashboard. When i view chrome dev tools i see the 404 response being returned on fetch invocation. preview the response further i see
 The page could not be found.

RESOURCE_NOT_FOUND

unless i view source and invoke the lambda on the zeit dashboard

What does this mean? Can you provide the URL your are invoking?

unless i view source and invoke the lambda on the zeit dashboard

What does this mean? Can you provide the URL your are invoking?

This is the url https://dekspoll-8yprknzt7.now.sh/
You can try and access it and click on any of the buttons and inspect the page via dev tools  in chrome to see the error.

@styfle At this point i feel my now.json file is the culprit. Please have a look
{
    "version": 2,
    "builds": [
        {"src": "api/*.js", "use": "@now/node"},
        {"src": "package.json", "use": "@now/static-build"}
    ],
    "routes" : [
        {"src": "api/","dest":"api/controllers/index.js"},
        {"src": "api/positions","dest":"api/positions.js"},
        {"src": "api/candidates","dest":"api/candidates.js"},
        {"src": "api/vote", "dest":"api/save-vote.js"},
        {"src": "api/results", "dest":"api/get-polls.js"}
    ],
    "env": {
        "db_host": "@db_host",
        "db_port": "@db_port",
        "db_user": "@db_user",
        "db_pass": "@db_pass",
        "db_data": "@db_data"
    }
}

I don't see a /api/results there defined.
I think you should remove the builds key and simplify your routes:
{
    "version": 2,
    "routes" : [
        {"src": "api/","dest":"api/controllers/index.js"},
        {"src": "api/vote", "dest":"api/save-vote.js"},
        {"src": "api/results", "dest":"api/get-polls.js"}
    ],
    "env": {
        "db_host": "@db_host",
        "db_port": "@db_port",
        "db_user": "@db_user",
        "db_pass": "@db_pass",
        "db_data": "@db_data"
    }
}

You could even rename those files so that you have /api/index.js, /api/vote.js, /api/results.js and then you wouldn't need any routes at all.

@styfle  Thanks soo much for your help. That worked as well.


Any suggestions of how to use with Speech LLMs

Hello
Thanks for making the code available.
Any recommendations regarding using this codec with audio LLMs?
Best
Musharraf

Hi @mush42, similar to mainstream codecs like SoundStream and EnCodec, ESC can also function as an acoustic tokenizer, generating codes from multiple streams. I suggest drawing inspiration from recent audio generative models (AudioLM, VALL-E, MusicGen) to effectively model the multi-level discrete codes.


Create CONTRIBUTING.md and CODE_OF_CONDUCT.md

These documents will let the OSC community know the guidelines for contributing to OSC as well as code of conduct/ethics the team and project follow.

@arvindn05 Arvind added code of condact to osc-core will add to other repos

@emanoelxavier please validate after fixed

@emanoelxavier created code of conduct for all the repos(left out nuage for now). Please validate and close

@arvindn05 please track with an issue on the pan and nuage plugins to have the same.


M2 gcs browser merging master

This PR brings the m2_gcs_browser branch up to date with the master branch in preparation for more work done in this branch. This branch had become a bit stale, which shows by the number of files changed.
There are no new changes included in this PR, all changes were reviewed and come directly from the master branch. Of course there were merge conflicts so a spot check here or there would be quite helpful.

@ILMTitan you are absolutely right, there's no reason why the .vcst file changes in this merge. I'll just accept the changes from master and move on. This branch is not adding any more VS level commands.

Actually that .vsct file is the same as the one in the master branch. The difference is because of the staleness of the branch.


Support list comparison in RQL

As of realm-core v12.5.0 RQL supports list comparisons, but the Dart SDK does not handle list arguments. Example:
realm.query('list = $0', [[1,2,3]]);

@nielsenko Are there any workaround for this?

What predicate are you trying to use?

I've tried this id IN { 1, 2, 3 } using string concat, but I'm unsure whether if this a way to go.

@thipokch I just accidentally revisited this issue, and saw I didn't respond to your reply. I'm very sorry about this oversight.
First, IN is different from =. The first checks for inclusion, the second for equality. But you hit a similar problem.
Yes string concatenation is the needed for now, but it is important that you do it on the query string itself, and not in the args, ie:
final list = [1,2,3];
realm.query(id IN {${list.join(',')}};

not
realm.query('id IN {$0}', [list]); // <-- won't work
realm.query('id IN {$0}', [list.join(',')]); // <-- won't work either

Query list arguments are now supported in Realm SDK 1.4.0


Track user last login option and fixes

This also hides the pop up notifications after 6 seconds

There is a Fastly CDN in place which caches pages.
However, with cookies, that is yet another decision the cache must take into account.
Page + cookie1  != Page + cookie2.
So even though a webpage might be served from the cache, it can't be with varying cookies.
It's preferable to not include more cookies. Or use browser localstorage.
If that's not possible, the next option is removing the cookie in the Fastly VCL code, on all pages where it's not required.
Is this needed on the /signup/ and /login/ pages, and otherwise could be removed?
If you add cookies, please let me know the details each time.

Now without cookies.


Fixing feature-effects compression

Closes #439.

coverage: 85.63%. remained the same when pulling 7df318b64dc66c2a854d0d87bcda837283c357f6 on 439-mehari-gzip into 4fd0c73c4bd75bf4aa5ef9a464713a2c5d4fada1 on main.


[ENH]: CIP - Expose Collection Dimensionality

Description of changes
Summarize the changes made by this PR.

New functionality

A new CIP to add ability for clients to view collection's dimensionality

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
Docs PR TBD

@beggers, some infra tests are failing for the past couple of days - https://github.com/chroma-core/chroma/actions/runs/7070701287/job/19247658540?pr=1217, got any idea?

I've seen a couple other similar flaky failures. I haven't investigated at all but I suspect we're running into the limits of what our Action runners can do. I'll look more deeply if it gets worse or I have a few free minutes.

@beggers, did you rerun it? Now all checks pass. @HammadB, this is ready for review.

Can we add a docs PR?

A few thoughts...

a valid workaround is len(collection.get(limit=1)['embeddings'][0]) right? if we simply want to expose this in our clients... perhaps it is better to do this than to add a new end to end method?
i dont like exposing dimensions as the method..... i think that it should be something more general like .describe or .info or .settings or.... something else.

Overall I don't think we should merge this, but I would like to here the "pro" case b/c im not sure i fully understand it

Lets do that - @jeffchuber are you OK with that?

I like .info() personally!

for renaming, let's enumerate 5-10 options (low effort, gives us confidence we are naming something well)

a valid workaround is len(collection.get(limit=1)['embeddings'][0]) right? if we simply want to expose this in our clients... perhaps it is better to do this than to add a new end to end method?

can we address this question?

a valid workaround is len(collection.get(limit=1)['embeddings'][0]) right? if we simply want to expose this in our clients... perhaps it is better to do this than to add a new end to end method?

I prefer doing something explicit, especially if we are renaming to info() (or similar) and plan to shove more information into this method in the future. Asking the client to fetch the embeddings when we store the dimensionality just feels hacky for no good reason . Also it makes future clients less implementation dependent. We could of course make the server do a get() but I think thats odd for no reason.

a valid workaround is len(collection.get(limit=1)['embeddings'][0]) right? if we simply want to expose this in our clients... perhaps it is better to do this than to add a new end to end method?

can we address this question?

@jeffchuber,I think if we fetch embeddings, we'll load the whole vector index, which seems like a side effect we might not want, given that the info is already available in SQLite. To put it into perspective, if you want to show stats on the UI, every time someone looks at their collections, we'll load all of them into memory.

ok im game for adding it - makes sense, thanks for the perspective
lets get the naming and interface right (likely a dict)
here's a chatGPT dump
describe: This name suggests the function provides a detailed description of the object, potentially including its attributes, types, and other relevant information. It implies a comprehensive overview rather than just a quick summary.

get_info: This is a straightforward and clear name. It indicates that the function retrieves and returns information about the object. This name is quite versatile and can be used in a variety of contexts.

settings: This name might be a bit misleading unless the function specifically returns configuration settings of the object. If the function is intended to return general information, this name might not be as appropriate.

details: Similar to describe, this name suggests that the function returns detailed information about the object. It implies a thorough examination.

overview: This name implies a more summarized view of the object, possibly less detailed than what describe or details might suggest.

inspect: This name suggests a detailed examination of the object, possibly including internal states and hidden attributes.

summarize: This name implies that the function provides a concise summary of the object, focusing on key aspects rather than extensive details.

get_attributes: If the function specifically returns the attributes of the object, this name would be very clear and descriptive.

I wouldn't say I like settings as it implies you can change settings.

In DB world I think describe is the go-to word

Synthetic data ftw:

Certainly! Let's score the method names on a scale of 1 to 10 based on their suitability in a database context for Python and Go, considering factors like clarity, convention, and intuitiveness:

describe:

Python: 9/10 (Widely recognized in similar contexts, very intuitive)
Go: 7/10 (Clear, but not as conventional in Go)
get_info:

Python: 8/10 (Pythonic and straightforward, but slightly generic)
Go: 8/10 (Clear and concise, fits Go's style)
details:

Python: 7/10 (Descriptive, but can be a bit vague)
Go: 8/10 (Direct and clear, good fit for Go)
inspect:

Python: 7/10 (Technical, suits Python's introspection but less common for DB)
Go: 6/10 (A bit less conventional, clear in purpose)
overview:

Python: 6/10 (Suggests summary, which might be misleading for detailed info)
Go: 5/10 (May not fully convey the depth of information provided)
summarize:

Python: 5/10 (Implies brevity, not ideal for detailed info)
Go: 4/10 (Might mislead about the function's depth)
settings:

Python: 3/10 (Misleading unless specifically about configuration settings)
Go: 3/10 (Not suitable unless for settings, could confuse)
get_attributes:

Python: 8/10 (Very clear if specifically about attributes, but narrow in scope)
Go: 7/10 (Explicit, but may be too specific if the method is more general)
These scores are based on how well the names align with each language's conventions and the expected functionality in a database context.

Lets do describe then and make the output a TypedDict

on it!

@HammadB TAL, I think it's ready.

Closing as dimensionality already exposed through collection model


feat: optimization the Cron.run method. make it clear and efficient

1、 use one loop is enough. use the reset variable flag whether to sort and reset time.sort entries and reset timer only At the beginning or change the entries
2、 use the time.reset to reset when recieve timer.C . so we can reuse the timer and don't need to sort

I think this code is less clear. No thanks


load_model failing when running validate_on_lfw

i'm trying to run your pre trained model as linked by the wiki, but it seems that there's an inconsistency between the ckpt file and the meta file.  The initial error I get when I try loading the model is
not found: Tensor name "conv1_7x7_1/batch_norm/batch_norm/beta/ExponentialMovingAverage_1" not found in checkpoint files /orpix/research/facenet/facenet/src/models/model.ckpt-500000
Can you let me know if I'm doing something wrong here? thanks

The similar problem encountered when I am try to import the "model.ckpt-500000" mode:
Not found: Tensor name "incept3c/in3_conv5x5_19/weights/ExponentialMovingAverage_1" not found in checkpoint files

I reverted the validate_on_lfw.py to the version which loads the model without needing the meta file, and it worked.  It appears as if the provided meta file is not compatible with the trained ckpt model file.  If you load the model by creating variables using the call to inference and then restoring all the variables, it works

Great, thanks. But how to change the  validate_on_lfw.py file?

i looked at this revision and changed my file based on this - load the model as he was doing it before this change
https://github.com/davidsandberg/facenet/commit/d17aa066d6ac205576d9b165b59ee206109e27e7

This is a bit strange. Just to make sure I understand correctly... On the wiki there is a link to a zip file that contains both the model parameters and the meta-file (that contains the model definition). Are you using this meta-file?
Here is what it looks like when extracted:
david@deeplab1:~/datasets$ ls -al ~/Downloads/20160514-234418/
total 88256
drwxrwxr-x 2 david david     4096 jul 19 08:27 .
drwxr-xr-x 6 david david    12288 jul 19 08:27 ..
-rw------- 1 david david 83731015 jul  8 00:13 model.ckpt-500000
-rw------- 1 david david  6616113 jul  8 00:13 model.ckpt-500000.meta

And when I run validate_on_lfw.py i set the parameter
--model_file ~/Downloads/20160514-234418/model.ckpt-500000
And when I run this it loads the model without any problems.

I am sure the same model and meta data is used.

@davidsandberg , I downloaded the exact zip file you reference, and I get an error related to a variable ExponentialMovingAverage_1 not being found just as @GangqiangZhao  described as well.  I can try again later to double check

Which Tensorflow release are you using? I'm on TF r0.9. I'm not sure that this problem is related to tensorflow release but I have difficulties seeing what else it could be.

I am using the master version in Github.

After updating the numpy to 1.11 version, I am finally able to complete the lfw validation on Tensorflow version r0.8. It looks like the problem is caused by the different version of tensorflow and some unknown tensorflow install setup.

I reverted to TF r0.8 and it's still working fine. I'm on numpy 1.10.2.

I was on gtx1080, cuda8.0, TF r0.9 and numpy 1.11 version. I was also experiencing same error. But after downgrading TF to r0.8 it works fine with the last commit.
77b66a2bb06def3437f75e71a996fe0552059abb

Maybe it is caused by different version of tensorflow?
For my case, when I execute validate_on_lfw.py using tensorflow r0.9, I met serveral errors as follows:

......
W tensorflow/core/framework/op_kernel.cc:936] Not found: Tensor name "incept4e/in2_conv3x3_45/batch_norm/batch_norm/gamma/ExponentialMovingAverage_1" not found in checkpoint files models/model.ckpt-500000
[[Node: ema_restore/restore_slice_447 = RestoreSlice[dt=DT_FLOAT, preferred_shard=-1, _device="/job:localhost/replica:0/task:0/cpu:0"](_recv_ema_restore/Const_0, ema_restore/restore_slice_447/tensor_name, ema_restore/restore_slice_447/shape_and_slice)]]
E tensorflow/core/client/tensor_c_api.cc:485] Tensor name "incept4e/in2_conv3x3_45/batch_norm/batch_norm/gamma/ExponentialMovingAverage_1" not found in checkpoint files models/model.ckpt-500000
[[Node: ema_restore/restore_slice_447 = RestoreSlice[dt=DT_FLOAT, preferred_shard=-1, _device="/job:localhost/replica:0/task:0/cpu:0"](_recv_ema_restore/Const_0, ema_restore/restore_slice_447/tensor_name, ema_restore/restore_slice_447/shape_and_slice)]]
[[Node: ema_restore/restore_slice_462/_84 = _Recvclient_terminated=false, recv_device="/job:localhost/replica:0/task:0/gpu:2", send_device="/job:localhost/replica:0/task:0/cpu:0", send_device_incarnation=1, tensor_name="edge_3252_ema_restore/restore_slice_462", tensor_type=DT_FLOAT, _device="/job:localhost/replica:0/task:0/gpu:2"]]
......

While after I uninstalled r0.9 and rollback to tensorflow r0.8, it is working fine now.

I think the issue might have been solved since some problem of function load_model() in facenet.py has been fixed.

I don't know why "images_placeholder.get_shape()[1]" returns (?,?)
Is anyone getting the same error?

@lbg940131 I thought the "?" might mean the size can be changed according to the number of the images you feed


Adding shell script to update JavaScript files from a web blockly repo.

Also including pulling updated JavaScript files from google/blockly master.

This change is

Fixes #355.

Review status: 0 of 5 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Support reading and writing from stdin

Allows the user to pipe input to nbt-dump instead of providing an input file. Useful if the input is coming from another terminal task, such as decoding nbt from base64.
For example:
echo 'CgAAAwgAYmxvY2tfaWTbAwAACAQAbmFtZRkAbWluZWNyYWZ0OmN5YW5fdGVycmFjb3R0YQQJAG5hbWVfaGFzaN09COzMuHwAAwoAbmV0d29ya19pZIWPCzoKBgBzdGF0ZXMAAwcAdmVyc2lvbgRGFAEA' | base64 --decode | nbt-dump

Thanks!


feat(meta): support BTreeMapTransaction that avoids copying the whole BTreeMap

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Currently in our hummock manager, we use VarTransaction<BTreeMap> to wrap a hummock manager state that is of BTreeMap type to do some transactional work. The current implementation of VarTransaction<BTreeMap> will take a copy of the BTreeMap and all modifications will be applied to the BTreeMap copy. When it is applied to a transaction, we will iterate the BTreeMap copy and the original BTreeMap and apply the upsert and delete by comparing the two values of the same key one by one. Upon commit the BTreeMap copy will replace the original BTreeMap. Although we have BTreeMapEntryTransaction to avoid copying the BTreeMap but still able to update the BTreeMap, it only allows modifying one BTreeMap entry. In case we want to insert or delete multiple entries in a transaction, we still need the VarTransaction<BTreeMap>.
However, taking a copy of BTreeMap may impact the performance when the BTreeMap gets large. In a previous commit 4a75d24972639f00d2ad4f36d298d4075ceb7e7c on the main branch, a unit test named hummock::compactor_tests::tests::test_compaction_drop_key_by_ttl commit 1000 epochs in total (the unit test has be modified recently to committing much less than 1000 times and it is much faster), with 1 SST added to HummockVersion in each epoch. All operations are in-memory, and it should not take too much time. However, the unit test takes about 5 seconds to finish. The flamegraph shows that half of the time is spent on BTreeMap related stuffs (the rest half are protobuf encoding).

In this PR, we introduce a BTreeMapTransaction, which supports basic BTreeMap operation such as get, get_mut, insert and remove. It has a field staging to record all the insert, remove and update(generated by modification on get_mut) operations on the BTreeMap entry. When we read the BTreeMap with get and get_mut, it will merge the value in staging and the original tree. Upon commit it will apply the change on staging to the original BTreeMap. With this PR, the unit test mentioned takes 2 seconds to finish, and in the flamegraph we can barely see any BTreeMap operation.

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

Would you mind give more information such as CPU of meta-service ?

Provide some comparison metrics:
Current main:

With this PR

With this PR, the memory usage meta decreases compared with the current main branch, though the memory usage is low. And since the bottleneck for real process time is committing ETCD, the overall real process time is basically the same in both cases.
Since the benchmark is not long-running, the state stored in meta is relatively small. But I think while the system gets long-running and the state becomes large, we can benefit from avoiding copying the whole BTreeMap.


Cannot update to 1.15

rustup update stable is currently failing for me
→ rustup update stable
info: syncing channel updates for 'stable-x86_64-apple-darwin'
info: downloading component 'rustc'
 31.9 MiB /  31.9 MiB (100 %)   5.1 MiB/s ETA:   0 s
info: downloading component 'rust-std'
 42.4 MiB /  42.4 MiB (100 %)   3.5 MiB/s ETA:   0 s
info: downloading component 'cargo'
info: downloading component 'rust-docs'
  6.9 MiB /   6.9 MiB (100 %)   3.3 MiB/s ETA:   0 s
info: installing component 'rustc'
info: rolling back changes
error: failed to install component: 'rustc-x86_64-apple-darwin', detected conflict: '"lib/rustlib/etc/gdb_load_rust_pretty_printers.py"'

I also tried a rustup self update before trying again and got the same result, versions I tried on were
→ rustup --version
rustup 0.6.5 (88ef618 2016-11-04)
→ rustup --version
rustup 1.0.0 (17b6d21 2016-12-15)

This is updating from
→ rustc +stable --version
rustc 1.14.0 (e8a012324 2016-12-16)

In case this was related to some really old rust install I checked if I had this file anywhere else, but it's only in rustup managed installs and the rust source:
→ find / -name 'gdb_load_rust_pretty_printers.py' 2>/dev/null
/Users/Nemo157/.rustup/toolchains/beta-x86_64-apple-darwin/lib/rustlib/etc/gdb_load_rust_pretty_printers.py
/Users/Nemo157/.rustup/toolchains/nightly-2017-01-06-x86_64-apple-darwin/lib/rustlib/etc/gdb_load_rust_pretty_printers.py
/Users/Nemo157/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/etc/gdb_load_rust_pretty_printers.py
/Users/Nemo157/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/etc/gdb_load_rust_pretty_printers.py
/Users/Nemo157/sources/rust/src/etc/gdb_load_rust_pretty_printers.py

I've been able to update many times in the past, so not sure what's different about this release. I also just updated beta to 1.15.0-beta.5 a couple of days ago fine.
I normally develop on nightly anyway, so I'll leave stable as is in case someone has any debugging commands I could run.

Thanks for the report @Nemo157.
I have a hunch of what happened here, and am hopeful it won't happen again. Need further investigation.

@brson Status?

I still have not touched my stable toolchain since I reported this, just tried again in case something changed between rustup 1.0 and now, still get the same error message
→ rustc +stable --version
rustc 1.14.0 (e8a012324 2016-12-16)

→ rustup --version
rustup 1.0.0 (17b6d21 2016-12-15)

→ rustup update stable
info: syncing channel updates for 'stable-x86_64-apple-darwin'
info: downloading component 'rustc'
 32.8 MiB /  32.8 MiB (100 %)   2.1 MiB/s ETA:   0 s
info: downloading component 'rust-std'
 43.9 MiB /  43.9 MiB (100 %)   3.0 MiB/s ETA:   0 s
info: downloading component 'cargo'
info: downloading component 'rust-docs'
  9.9 MiB /   9.9 MiB (100 %)   3.2 MiB/s ETA:   0 s
info: installing component 'rustc'
info: rolling back changes
error: failed to install component: 'rustc-x86_64-apple-darwin', detected conflict: '"lib/rustlib/etc/gdb_rust_pretty_printing.py"'

→ rustup self update
info: checking for self-updates
info: downloading self-update
info: rustup updated successfully to 1.2.0

→ rustup update stable
info: syncing channel updates for 'stable-x86_64-apple-darwin'
info: downloading component 'rustc'
 32.8 MiB /  32.8 MiB (100 %)   3.2 MiB/s ETA:   0 s
info: downloading component 'rust-std'
 43.9 MiB /  43.9 MiB (100 %)   3.3 MiB/s ETA:   0 s
info: downloading component 'cargo'
  3.5 MiB /   3.5 MiB (100 %)   3.1 MiB/s ETA:   0 s
info: downloading component 'rust-docs'
  9.9 MiB /   9.9 MiB (100 %)   3.3 MiB/s ETA:   0 s
info: installing component 'rustc'
info: rolling back changes
error: failed to install component: 'rustc-x86_64-apple-darwin', detected conflict: '"lib/rustlib/etc/gdb_rust_pretty_printing.py"'

still willing to run any kind of debugging commands if anyone has some.

I had a similar problem when trying to update stable-x86_64-pc-windows-msvc on Windows (rustup version 1.5.0).
I solved it by removing the manifest file of the component that had the conflict (in my case .rustup\toolchains\stable-x86_64-pc-windows-msvc\lib\rustlib\manifest-rust-src).
After this rustup update succeeded.

I am having a similar issue installing 1.33.0-nightly (f960f377f 2018-12-24) alongside a fresh installation of 1.31.1-stable (b6c32da9b 2012-12-18) on target x86-64-unknown-linux-gnu.
Steps to reproduce:

Remove current installation - rm -rf ~/.cargo ~/.rustup
Install rustup according to the rustup.rs website - curl https://sh.rustup.rs | sh
Attempt to install nightly - rustup toolchain install nightly

Output of rustup toolchain install nightly:
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2018-12-25, rust version 1.33.0-nightly (f960f377f 2018-12-24)
info: downloading component 'rustc'
 82.5 MiB /  82.5 MiB (100 %)   3.3 MiB/s ETA:   0 s
info: downloading component 'rust-std'
 71.5 MiB /  71.5 MiB (100 %)   5.7 MiB/s ETA:   0 s
info: downloading component 'cargo'
info: downloading component 'rust-docs'
  8.5 MiB /   8.5 MiB (100 %)   5.4 MiB/s ETA:   0 s
info: installing component 'rustc'
info: installing component 'rust-std'
info: rolling back changes
error: failed to install component: 'rust-std-x86_64-unknown-linux-gnu', detected conflict: '"lib/rustlib/x86_64-unknown-linux-gnu/lib/libLLVM-8svn.so"'

Output of rustup show:
Default host: x86_64-unknown-linux-gnu

stable-x86_64-unknown-linux-gnu (default)
rustc 1.31.1 (b6c32da9b 2018-12-18)

The file ~/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libLLVM-8svn.so exists before and after attempting installation, and it is the only toolchain installed. Removing that file before attempting to install nightly does not work (same error), but the file reappears during installation of nightly, which seems odd.

Main issue is #1590. Current workaround is rustup toolchain add nightly-2018-12-23

Main issue is #1590. Current workaround is rustup toolchain add nightly-2018-12-23

# rustc +stable --version
rustc 1.31.1 (b6c32da9b 2018-12-18)

# rustup toolchain add nightly-2018-12-23
info: syncing channel updates for 'nightly-2018-12-23-x86_64-unknown-linux-gnu'

nightly-2018-12-23-x86_64-unknown-linux-gnu unchanged - rustc 1.33.0-nightly (2d3e909e4 2018-12-22)

# rustup toolchain install nightly-x86_64-unknown-linux-gnu
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: latest update on 2018-12-25, rust version 1.33.0-nightly (f960f377f 2018-12-24)
info: downloading component 'rustc'
info: downloading component 'rust-std'
info: downloading component 'cargo'
info: downloading component 'rust-docs'
info: installing component 'rustc'
info: installing component 'rust-std'
info: rolling back changes

error: failed to install component: 'rust-std-x86_64-unknown-linux-gnu', detected conflict: '"lib/rustlib/x86_64-unknown-linux-gnu/lib/libLLVM-8svn.so"'

This happened for me as well on my Windows device just now, trying to update to latest stable. Even after restarting the computer (which pretty much works for fixing anything) the error occurred. I ended up deleting all of the folders in the toolchain directory, then running the update process again. Success!

This is another instance of missing/corrupt manifest data. Without knowledge of the installed file, rustup cannot remove it prior to installing the updated version, and then hits a conflict due to the file already existing, and you get the error.
We've got a bunch of these bugs scattered all over the place, I'm closing them all to bring order. See #2417.


Auth flow, model endpoint, and results visibility

Users can now log in with an EDSL auth token to retrieve their API key and write it to .env
Model.available() now uses the pricing JSON from Coop as a fallback to identify available models
Jobs.run() now has an optional parameter, remote_inference_results_visibility, that determines the initial visibility of the Results object from remote inference

@onmyraedar Am I not using this parameter correctly? Thanks!

Hi! You're using it correctly. Which EDSL version are you on?

I am updating and pulling from main but still showing  0.1.37.dev1

I'm going to reinstall, something not right.

@onmyraedar all set now, these work fine for me, thx!

Thanks for letting me know!


flickering Track ID variable

Hello, we connected a tascam ss-crd250n with companion (3.2.0) and want to display the current track-ID. When no media is loaded (no SD/USB/CD) there is a "0" as variable. When we put a USB Stick/SD/CD in the tascam, the number is flickering between a number (100/200/400) and very short time the track number.
Here is a photo that shows the glitch as good as i could capture it:

Do you know that problem? Did we configered something wrong?

Thats the Log. Thanks for the fast response!

I can see the problem. Can you try the version in this fork and let me know how it goes (I dont have access to a unit):
https://github.com/phillipivan/companion-module-tascam-cd/tree/master
If you dont know how to build that let me know and I can email a build to you.

Thanks for the fast response! I would be very grateful if you could explain to me, how i build it!

There are instructions here but it can take a while to get the environment setup and going the first time.
Happy to email a build to you if you message me your address.

companion-module-tascam-cd.zip
Put this in a sub-folder inside a companion-modules-dev folder and point companion at it.
If companion reports a version of 2.0.3 for the module then its running this version. Let me know how you go.

Thanks the module 2.0.3 is running, now i must go to the company where we installed the player and have to test it. I will keep contact to you if the bug is fixed!

When you test it can you please also check the Track Time Variable, especially as you change modes with the Current Track Time Sense.

companion-module-tascam-cd.zip
Actually try this. It should also do the follow:
End of Media feedback.
Timer mode (set with Current Track Time Sense) is saved in the device config, and the time polling should pick up this value.

Now I had the time to check the patch! It works great, thank you very much for your fast response and great work! The track id and the current timecode is working great. Do you need any evidence?

Nope. Thank you.
The updated module is in recent Betas, and will be in the next companion release.


Fix: Add documentation for updating the Verifier Lambda

After initial deploy, user might need to update the Verifier with tags or other attributes. Adding a few examples on updating the Verifier will be useful. Consider including the SAM and AWScli examples etc

Done


Implement InvalidPopExpressionMismatch checker

The InvalidPopExpressionMismatch occurs when the operand of pop expression does not contain listTy or contain non-listTy types.
Type analysis log with mismatches:
* 2 type mismatches are detected.
[InvalidPopExpressionMismatch] pop in GeneratorYield (step 8, 11:14 - 12:128)
- actual  : Absent
[InvalidPopExpressionMismatch] pop in INTRINSICS.ForInIteratorPrototype.next
- actual  : List[String] | Undefined

and fix ListTy for better prune type operation

Currently, it seems that ListTy[Bot] != Bot. Thus, if this is an error, then it should be fixed first.


When I using deepmerge in vite project

When I merge the #10 , I got this error in browser and dev mode
Uncaught SyntaxError: import not found: default

It located the 1st line in request.ts
import merge from 'deepmerge'
^^^^^^

@levchak0910  Do you have any idea?

I forgot add deepmerge to package.json
It seems somewhere in development time i discarded files in my IDE and forget add this dependency again
(Shame on me)
Fixed

Oh... I think it should throw "not found module xxx" it's confusing.


Tensorflower gardener reverting changes made in PRs

I had a couple of PRs merged before release of 2.5, and one after that. None of the changes in those PRs are now reflected in the code on master branch. Is this some internal process?
The PRs before release are  #48000 #48491 and the one after the release is #48610
In all the three PRs, if we see in the History section of the file, we see Tensorflower gardener pushing the changes, but reverting them in the very next commit under the title "Internal change". Can someone please tell what's going on?
Following are the screenshots as well as links to the commits made by tensorflower-gardener
#48000: Internal change

#48610: Internal change

In general, we are trying to be a little bit more transparent about this process and to automate the notification to the contibutors.
See https://github.com/google/copybara/issues/155
/cc @mihaimaruseac @nikitamaia @theadactyl

@bhack
Ok,  but what does that mean about the PRs? Are they reassessed internally or something?
Also, on a side note, about the DepthwiseConv1D issue, I couldn't get it to build on my PC with a quarter of the resources. Thus, I will  try to use colab for that henceforth.

It about something that was gone wrong internally so you are not the only one and we have other rollback conmit. You can see a recent one at https://github.com/tensorflow/tensorflow/commit/07dd16b3a09e0cfa007d9694251dd6b2cbdf36ad
About Depthwise please leave a comment about your compiling experience/issues in its own ticket as It could have something in common to other contributors candidates experience.

Yes, I saw that some of the merged PRs by external contributors were rolled back. So, I suppose those will be merged again later, right?

About Depthwise please leave a comment about your compiling experience/issues in its own ticket as It could have something in common to other contributors candidates experience.

Sure, will do

So, I suppose those will be merged again later, right?

I don't think so as on Github you cannot re-open/unmerge PRs.
This why I want to improve the bot to automatically notify PR and re-open Its own linked ISSUES (when available) on rollbacks.
Then the internal Team member/reviewer can add additional comments about what happened internally and if the contributor can do something else and re-open a new "clone PR".
Probably there is also a better process but I currently I have no internal visibility to understand why rollbacks happens and why they are not blocked before merge by CI checks (probably Is this related to some missing coverage about internal assets?)

Got it, thanks

So, internally all Google code (from all projects) is in one big repository. We have tests for other projects that depend on TF. when any test is broken, there is an automatic rollback phase. Sometimes, some Googler that saw the PRs is able to notify the PR that it got rolled back, provide help as to why that happened, etc. But this is not a given, sadly.

I still think that we have margins to automate the bot as copybara API are available.

@mihaimaruseac
Thanks for the explanation. In that case is there any way that I can make sure that future PRs are clean?

There is some work that is currently planned for the OSS DevInfra team so that the gap between internal and external code is minimized. Unfortunately, if other projects rely on internal code there is nothing that can be done from the OSS side and someone in TF team needs to take to bring the other internal project up to date with the new changes.

Thanks for the prompt and detailed explanation.

@AdityaKane2001
Could you please move this issue to closed status ,as it is resolved.Thanks


faster featurizer

The old Cython featurizer only took two minutes on low1 once dummies had been created; this new one takes two hours. Dunno how long dummies took, but not two hours.
What's the significant difference? Speed that up....

Actually, apparently it only takes 20 minutes on low1. (Why are the initial ones so much slower?)

One thing that might help is to call MKL straight instead of through numpy: gemm would save a dot-then-scale, sincos is much faster than np.sin plus np.cos (https://github.com/numpy/numpy/issues/2626#issuecomment-235785553), probably some other savings to be had in rff_embedding (or use fastfood).


[BUG] AJAX error when attempting to connect Blocto wallet to RPS app

Current Behavior
Currently, requests to Blocto are not successful when connecting Blocto wallet to the RPS game. Currently hangs after entering Blocto credentials to login and connect my wallet.
Update: Looks like there's a 401 response on a GET request to https://flow-wallet-dev.blocto.app/blocto/account/assets? with response of {"error_code":"auth_fail","message":"invalid token"}
Expected Behavior
When a user elects to connect their Blocto wallet to the RPS game, the request should be successful and they should be presented with a multi-sign transaction that adds the app account as a child to their wallet-managed account.
Steps To Reproduce
Run the RPS client locally against Testnet and proceed through gameplay until you win a game. Then hit "settings' and connect your account.
Environment
- OS: macOS 13.4.1 (c)
- Node: 16.6.0
- npm: 9.8.0

What are you currently working on that this is blocking?
No response

cc: @JeffreyDoyle @gregsantos I know you're both working on other things atm, but wondering if you all might know offhand why this error is coming up. I couldn't find anything in the Blocto docs

Interesting, I was able to connect my blocto wallet.
but when browser is incognito, I get the "AjaxError" error.

Yeah, that's totally what's going on. That's what I get for trying to debug frontend 😅 Thanks for clearing that up, I'll close the issue now.

I was able to login to flow port incognito, so I'm a bit confused. I can see if what differences there are with login.


Make the install target work and test it.

This fixes #650. To make the install target work we need to install
nlohmann/json.hpp in a directory that does not conflict with other
possible locations for the file. It seems that
google/cloud/storage/internal is a good fit for that.
Had to fix the CMake configuration files to define the CURL::CURL target
if it is not defined. Some older versions of CMake (which we support)
may not set that target and it is easier to write the CMake files
assuming it exists.
Simplified the tests for Bazel as a dependency, they were getting rather
long.
I created a test that verifies the install target by actually installing
the code and using the installed code to compile a program. The same
program is compiled with Bazel, but with our code as a dependency.
Finally, the same test program is compiled using make(1), to verify the
generated pkg-config(1) files are useful.

This change is

PTAL.

@frankyn I am going to assume this is Okay then, and merge. If you want me to change anything we can do that in a future PR.


seed file working - creates db with users, sellers, addresses, brews,…

… units, and products
closes #18

looks fine. the order of promises makes seeding sense. the name change is good.


Calculating variant cost price doesn't work with more than one stock record and empty cost price

When variant has more then one stock record and at least one of them has empty cost price (which is optional), then calling get_cost_price method of ProductVariant results in the following error:
/home/marcin/mirumeeWorkspace/saleor/saleor/saleor/product/models.py in select_stockrecord(self, quantity)
    294             lambda stock: stock.quantity_available >= quantity,
    295             self.stock.all())
--> 296         stock = sorted(stock, key=lambda stock: stock.cost_price, reverse=True)
    297         if stock:
    298             return stock[0]

TypeError: unorderable types: NoneType() < NoneType()

I'm not sure how do we want to select the stock record with lowest price when some of them don't have the cost price set. We could require the cost price or assume zero price in this case. What do you think @patrys?

I think it does not matter which we pick (either favor the ones with None or favor the lowest known and fallback to None if not available) as long as we document it in the docstrings.


Change Language ID to Locale class.

Issue

none

Overview (Required)

Language ID of String changes to Locale class.

Links

https://github.com/DroidKaigi/conference-app-2017/pull/242

This is different from this link content, but is it ok?
Or should I fix it in the same way?

Looks good 👍

Thank you for improvement!


build: remove kaop from bundle

Coverage remained the same at 89.908% when pulling 3b673ad6041feea5b38784bee22838663740fc8f on remove-kaopjs-bundle into 951919b9933769aeb53065d8534f8d45dbb0fc8b on master.


python37Packages.cachy: 0.2.0 -> 0.3.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-cachy/versions.
meta.description for python37Packages.cachy is: '"Cachy provides a simple yet effective caching library"'.
meta.homepage for python37Packages.cachy is: '"https://github.com/sdispater/cachy"

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.3.0 with grep in /nix/store/bsksgfjxwhl663c18dc6sxy82w7r69h9-python3.7-cachy-0.3.0

directory tree listing: https://gist.github.com/d6a0e4a5de1c3a117649c1bcfe6c81ab

du listing: https://gist.github.com/2fee798815ec0ffd28a197b311d0e242

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

20 total rebuild path(s)
5 package rebuild(s)
5 x86_64-linux rebuild(s)
5 i686-linux rebuild(s)
5 x86_64-darwin rebuild(s)
5 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
poetry
python27Packages.cachy
python27Packages.poetry
python37Packages.cachy
python37Packages.poetry

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bsksgfjxwhl663c18dc6sxy82w7r69h9-python3.7-cachy-0.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python37Packages.cachy https://github.com/r-ryantm/nixpkgs/archive/af5e9214dd46aaa3c7e8cb17500939e5274d1883.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bsksgfjxwhl663c18dc6sxy82w7r69h9-python3.7-cachy-0.3.0
ls -la /nix/store/bsksgfjxwhl663c18dc6sxy82w7r69h9-python3.7-cachy-0.3.0/bin

cc @jbaum98 for testing.

@jbaum98 ping

closing for #72445