unexpected Crash v<IP_ADDRESS>

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
GitHub
Running as admin
No
Area(s) with issue?
General
Steps to reproduce
Crshed during running
`
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.19045.0
IntPtr Length: 8
x64: True
Date: 06.01.2023 07:54:05
Exception:
System.InvalidOperationException: Dispatcher processing has been suspended, but messages are still being processed.
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
`
2023-01-06.txt
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

/dup #18166
Can you please add some more info in that issue on how this happens to you?
I'd be curious to know if https://github.com/microsoft/PowerToys/issues/18166#issuecomment-1332887065 might be the case for you as well.

For any users that are able to replicate this consistently, can you please update to 0.68.1 and disable thumbnail generation to verify if it fixes the issue? Please let us know on #18166!


[Feature] Release binaries

Currently you release bundled up files. I think it would be a better idea to release the binaries as-is

The reason I bundled them was because the windows binary had two files and I felt it would be weird to have one zip and two binaries.

I find it's more weird to do that. I recommend doing what most projects do and just release both the windows binaries in the releases.
Additionally this is better as if I just want one windows binary why get both...

Fixed. The windows build had a .pdb file but I guess that's not very important.


Consider improved Dockerfile generation

I suggest integrating what NMica Dockerfile generation does to improve the efficiency of layering.
https://github.com/NMica/NMica
Here's an in-depth blog post on what it does
http://stakhov.pro/building-efficient-net-docker-images/

Sorry for the delay in getting back to you. I think this is definitely a good idea for when we're publishing.
So if I'm understanding how this works correctly this package:

reads the project.assets.json, and then categorizes the assets based on where they came from
then copies them into separate folders during publish
the places those into separate docker layers

Is that correct?

Yes

is there some way already to export locally the Dockerfile that tye will build?

tye build should be what you are looking for.

I don't think so. We don't persist the file to to disk in a way the user can see.

Ah, build only creates the image without pushing it. I thought it would create the file that would be used for images. We could consider updating the generate command to support it.


Ensure reconcile requests are generated correctly

When a placementbinding references multiple subjects, the mapper should
always loop through entire subjects to generate reconcile request even when a
policyset couldn't be retrieved.
Signed-off-by: Yu Cao<EMAIL_ADDRESS>

/hold to add test cases

/unhold
@willkutler this pr is ready for review.


Enable external redis server

At present chart does not allow to easily use external Redis - it requires overwriting of $ENV variables.
This feature adds support for external Redis server.

implemented by #143


One fix and one feature for MQTT dealing with link stealing

Hi Justin, could I ask you if it is possible to add some specific logs for tracing the stealing link issue.
I mean, I think it would be very useful to have some logs to identify both the use cases, i.e.:

a client trying to open a connection with a clientId already used is able to steal the connection to another client already connected with the same clientId (default use case)
a client trying to open a connection with a clientId already used is not able to do that (allowLinkStealing=false use case)
since it would be very useful to be able to explain a customer the reason why a client cannot connect, or why a client already connected looses its connection (depending on the configuration).
A proposal (if possible obviously) could be to have some specific Audit Logs for tracing this specific use cases since they could be relevant.
Many thanks

FTI - full test-suite passed.


Numpy version issues while calling NamesMatcher() function

File "/usr/local/lib/python3.7/dist-packages/names_matcher/algorithm.py", line 109     distances = np.ones(((offset := len(parts1)) + len(parts2),) * 2)                                  ^ SyntaxError: invalid syntax
While running in colab, I installed the library, and then restarted the runtime environment. But, even after restarting, it gives this error. @athenianco please help.

I am sorry to say that py 3.7 is not supported.
https://github.com/athenianco/names-matcher/blob/8f177a6a23852bdd1ea01935c3e6f8c131224ab1/setup.py#L39
Unfortunately, we don't plan to support 3.7 because we are using the new syntax everywhere.


multiple item selection

i am getting a response in dropdownlist and i want to post back selected items from dropdown anyone can help with demonstration please??

Here's a Dropdown multiple-selection example: https://github.com/flutter/flutter/pull/25955#issuecomment-466215221

Closing, as it looks like the example has been provided.


[Release Radar Request] Wagtail 6.0

Open Source Project name
Wagtail
What is your project?
Wagtail is the most popular Python CMS. It combines Django’s powerful customization capabilities with a delightful user interface.
Version
6.0
Date
February 7, 2024
Description of breaking changes
Wagtail 6.0 ships with Django 5.0 support, a new searchable and filterable listing UI, the accessibility checker built into the admin interface, and a brand new 10-step tutorial for developers.
GitHub Repo
https://github.com/wagtail/wagtail
Website
https://wagtail.org/
Link to changelog
https://wagtail.org/blog/wagtail-6-0/
Social media
https://twitter.com/WagtailCMS/status/1755275592042250269
Anything else to add?
This release marks Wagtail’s 10th birthday! On our blog, we separately reflected on 10 years of Wagtail.

Congrats on being featured in the February Release Radar 🥳

Read the blog here
Feel free to retweet Mish's tweet featuring you


Trpc

Description

Screenshots

Steps to verify/test this change:

[ ] Verify changes work as expected on staging instance

Final Checks:

[ ] Verify successful deployment

(optional)

[ ] Write tests
[ ] Write documentation

Issues

Closes #

There's a bug with the schedule: the name of the current quarter ("Summerwk2") does not match the name of the terms in the WebSoc current quarter ("Summer Week 2"), so there is a bug in the getTermDeptNum route in the schedule router.
see https://peterportal.org/course/I&CSCI6B

Reviews and roadmap not migrated yet


Resolve "Status code of HTTP error messages is not 4xx or 5xx"

Closes https://github.com/EricLBuehler/mistral.rs/issues/97
curl -v http://localhost:1234/v1/chat/completions \
-H "Content-Type: application/json" \
-H "Authorization: Bearer EMPTY" \
-d '{
"model": "mistral",
"stop": "\n\n\n",
"temperature": 0,
"top_p": 0.1,
"frequency_penalty": 1.0,
"max_tokens": 256,
"messages": [
{
    "role": "user",
    "content": "Write a story about Rust error handling."
}
]
}'
*   Trying <IP_ADDRESS>:1234...
* Connected to localhost (<IP_ADDRESS>) port 1234 (#0)
> POST /v1/chat/completions HTTP/1.1
> Host: localhost:1234
> User-Agent: curl/7.81.0
> Accept: */*
> Content-Type: application/json
> Authorization: Bearer EMPTY
> Content-Length: 216
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 500 Internal Server Error
< content-type: application/json
< content-length: 105
< date: Tue, 09 Apr 2024 22:42:53 GMT
<
* Connection #0 to host localhost left intact
{"message":"Stop sequence '[\"\\n\\n\\n\"]' encodes to multiple tokens when it should only encode to 1."}l

$ python3 chat.py
Enter system prompt >>> A
>>>

Traceback (most recent call last):
  File "/home/lucas/oss/mistral.rs/examples/server/chat.py", line 17, in <module>
    completion = openai.chat.completions.create(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_utils/_utils.py", line 299, in wrapper
    return func(*args, **kwargs)
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/resources/chat/completions.py", line 598, in create
    return self._post(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 1055, in post
    return cast(ResponseT, self.request(cast_to, opts, stream=stream, stream_cls=stream_cls))
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 834, in request
    return self._request(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 865, in _request
    return self._retry_request(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 925, in _retry_request
    return self._request(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 865, in _request
    return self._retry_request(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 925, in _retry_request
    return self._request(
  File "/home/lucas/.local/lib/python3.10/site-packages/openai/_base_client.py", line 877, in _request
    raise self._make_status_error_from_response(err.response) from None
openai.InternalServerError: Error code: 500 - {'message': 'invalid operation: Conversation roles must alternate user/assistant/user/assistant/... (in chat_template:1)'}

Thank you!


Datefile adapter - symlink not updating to new path after capistrano deploy

I believe the issue is with testing @original_filename, perhaps its just the filename, but it should be the full path

PING


chore(hare4): add missing test cleanup exit

Motivation
A missing return statement was missing on test cleanup channel select case.
Description
...
Test Plan

TODO

[ ] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

bors merge


add OIDC kubernetes authentication capability

aws EK kube uses OIDC to auth using IAM roles, it needs the sts dependency to be able to use this auth method.

Thanks a lot for contributing this PR @hanfi!  This is an important change, and it will help out anyone running this app on kubernetes.  We can get this one merged and released as a new version within the next few days.

This got closed in release 1.0.3 via issue #54.  You can now get the oidc support by pulling docker image version 1.0.3.
Thanks again for the contribution @hanfi


OCPBUGS-29613: test: add a test for invalid CSRs

This works for newer k8s API servers. Bug is reported against 4.15 ... wondering if the 1.28->1.29 bump is the fix?

/jira refresh

This will pass once our mgmt cluster is moved to 4.16

/test e2e-aws

/lgtm


events not firing in options.chart.events

chart: {
         type: 'column',
         events: {
                 drilldown: function(e) { console.log("drilldown fired"); },
                 drillup: function(e) { console.log("drillup fired"); },
                 click: function(e) { console.log("click fired"); }
          }
}

This code is a part of my chart options. Why are the drilldown and drillup events not firing, whereas the click event fires correctly whenever i click on the canvas?

I noticed this as well, it looks like there is a bug in the deepAssign logic where the base object they merge with the user provided chart options overrides the event handlers you pass in.

same issue here with 0.5.5, Could you make it work? I've already import the drilldown module
export function highchartsFactory() {
let highcharts = require('highcharts');
let highchartsMore = require('highcharts/highcharts-more');
let gauge = require('highcharts/modules/solid-gauge');
let map = require('highcharts/modules/map');
let drilldown = require('highcharts/modules/drilldown');
highchartsMore(highcharts);
gauge(highcharts);
map(highcharts);
drilldown(highcharts);

return highcharts;

}

I'm getting the same issue. Drilldown works when using 'basic drilldown' option like this.
However, when I use this example(without changing ANY module imports), it doesn't seem to work. No Drilldown event gets fired.

@joel00 I was able to get it to work in options.chart.events.
However, in order to handle  drilldown and drillup events, I did this in my template :
<chart [options]="options"      (drilldown)="onDrilldown()"      (drillup)="onDrillup()"> </chart> and defining the onDrilldown() and onDrillup() methods in my component.
Both events are firing correctly.

@shreyanshd thanks I can trigger the drilldown and drillup events...... but cannot figure it out how to assign the new map/data as the example in: http://jsfiddle.net/gh/get/library/pure/highcharts/highcharts/tree/master/samples/maps/demo/map-drilldown/
I'm trying:
drilldown(event: any) {
const point = event.originalEvent.point;
console.log(point.id);
this.chart.showLoading('Loading');   <=== works
this.chart.addSeriesAsDrilldown(point.id, {
data: this.data,
mapData: newMap, <===== getting compiling error
name: point.id,
dataLabels: { <= getting compiling error
enabled: true,
format: '{point.name}'
}
});
}
Could you put me in the right path?


Added demo_ prefix to interlock label

Customer feedback received for the demo stack example:
It leads users to expect that if they define a network in their compose file that they can use that network name in the Interlock network label which is not the case.  The example "works" because the service is only attached to a single network, but in actuality the Interlock network label would need to be prefixed with the stack name in order for the example to work correctly.

The concern is valid; so I have added demo_ as a prefix to the com.docker.lb.network label.

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 89fb933e063d2e7757f8c1644e69e80e348c5293
https://deploy-preview-7699--docsdocker.netlify.com


fix(@ngtools/webpack): only emit import default helper when needed

Previously, the import default TypeScript helper was emitted for every file when in JIT mode.  This was unused code in the majority of cases.  The helper is now emitted only when needed.  For this package that would be when an Angular component decorator's resource URL properties are adjusted to support JIT execution with Webpack.

Also merged to 9.1.x patch branch.


Configuration customization

User story
As a system administrator, I want to easily change facet and sort options of my InvenioRDM instance, so that I can customize RDM to my needs.
Tasks

Ensure that it easy and simple to override the service and resource config from the config in the cookiecut folder.

Closing in favor of inveniosoftware/invenio-records-resources#127


convered to dark mode

convered to dark mode
various changes to default sprites

The pack checker also found an extra .png in the resizeable_mode folder. Once you delete that it should be good to go to merge.
File side_panel_background - Copy.png in folder resizeable_mode is redundant


Add python file for #506

Related Issue
Solved issue number: #506  number that will be closed through this PR
Describe the changes you've made
Added python file for this diagonal difference problem
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
Python
Checklist:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have documented the code.
[x] New and existing unit tests pass locally with my changes.

@Sriram-bb63 Add some comments to your code.


Improve user experience for running migrations after deployment

Problem
Running migrations on deployment typically means you only have compiled output, not the project system. In theory, ef.exe/ef.dll should work well in this scenario, but figuring out all the arguments requires deep knowledge of how these tools work and is opaque to most users. Furthermore, ef.exe does not end up in compiled output, which requires users to do some NuGet cache spelunking to get the file.
Possible solutions

generate response files at design-time that ef.exe can parse on deployment
generate bash/cmd files that contain all the arguments for running an ef.exe command on compiled output
add msbuild targets to optionally put ef.exe/ef.dll in build output on publish

cc @rowanmiller we move this to backlog for now but we can discuss pulling it in 1.1.0 or whether we should have better documentation on how to do it manually.

Any progress on this?  I am keen to use this in our application as we are ready to migrate to new environments.  I notice that ef.exe is now part of preview 3 and 4 and whilst the --help for the console app is somewhat helpful, a more detailed explanation of the options and commands would be helpful.

I've helped this scenario a little bit by logging our call to dotnet exec ef.dll in the PMC and CLI tools when -v (verbose) is specified.

@bricelam -- Any updates on how to get this to work with the current version of EFCore?  As a little background, I'm trying to do an assembly-based migration (not code-based) from TFS Release Management.
Thanks,
-Ben

Look at the output of dotnet ef database update --vervbose to see how it calls ef.exe (or ef.dll)

Thanks for the tip, @bricelam.  To make it easier to call from an automated build or TFS Release Management, I turned the calls into a batch script.  https://www.benday.com/2017/03/17/deploy-entity-framework-core-migrations-from-a-dll/

what about an app published on linux, where ef.dll is nowhere to be found?

Hi @pdesterlich --
It works almost exactly the same but the paths are slightly different.  I've just updated my blog post (https://www.benday.com/2017/03/17/deploy-entity-framework-core-migrations-from-a-dll/) to include a bash shell script for doing the deployment plus a sample of how to call it.
Here's a direct link to the bash script: https://www.benday.com/wp-content/uploads/2017/03/deploy-ef-migrations.sh_.txt

thank you @benday for the reply, but it seems to me i'm missing something.
what if i don't have a .nuget directory in my $HOME folder?
maybe a bit of information about my test setup can help you to help me
i have an asp.net core project, developed both on windows and linux; now i'm trying to deploy on a linux server; for my test i'm using a local virtual machine with ubuntu server 16.04 (i'm following more or less a tutorial found here: https://www.junian.net/2017/01/running-your-first-aspnet-core-web-app-on-ubuntu-16-04.html )
I installed dotnet core with .deb package (instructions here: https://www.microsoft.com/net/core#linuxubuntu), then i copied my published app (dotnet publish -c Release) in /var/www/app-folder/
When i run my app (with dotnet app-name.dll, or with service as in tutorial above) for some reason the first migration is automatically run, but any subsequent migration is ignored (the same happen in my dev machine if i try to run on a non existent database).
I have no .nuget dir anywhere on the server, and i have no ef.dll file also.
I could easily generate a migration script and manually apply it to the database, but i'd like to use migration on the deploy machine.
What am i missing?

Hmm.  If you can build your dotnet core project on that Ubuntu machine ("dotnet build"), then you definitely have a .nuget folder somewhere.  I know that sometimes I get confused when I need to find something in a hidden folder in Linux -- any chance you aren't seeing your $HOME/.nuget directory because that folder is a hidden folder?
What happens if you run the following lines?:
cd $HOME
ls -la
Do you see a .nuget folder now?
What about if you run "cd $HOME/.nuget"?

Well my ubuntu dev machine is a different machine from my ubuntu server.
I already tried "ls -la" on home dir in ubuntu server but as said there isn't a .nuget dir.
Keep in mind that everything i'm doing is on an ubuntu server wich is only a deploy server, no development is done on that server

oh...that's tricky.  :)
I think you're going to have to find a way to include ef.dll in your build output.  It should be pretty easy -- just copy the file from $HOME/.nuget on your dev box and include it in your output files.

Hi guys, I've also faced this problem. When I execute script from https://www.benday.com/wp-content/uploads/2017/03/deploy-ef-migrations.bat_.txt I receive
dotnet exec needs a managed .dll or .exe extension
My input arg is dll like it was described in the article. When I run dotnet ef database update from project directory everything works fine. You can find csproj below.
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup Label="Configuration" Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'">
    <OutputType>exe</OutputType>
    <NuGetPackageRoot> $(USERPROFILE)\.nuget\packages\</NuGetPackageRoot>
  </PropertyGroup>
  <PropertyGroup>
    <TargetFramework>netcoreapp1.1</TargetFramework>
    <GenerateAssemblyConfigurationAttribute>false</GenerateAssemblyConfigurationAttribute>
    <GenerateAssemblyCompanyAttribute>false</GenerateAssemblyCompanyAttribute>
    <GenerateAssemblyProductAttribute>false</GenerateAssemblyProductAttribute>
    <ApplicationIcon />
    <OutputTypeEx>exe</OutputTypeEx>
    <StartupObject />
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Abp.EntityFrameworkCore" Version="2.1.3" />
    <PackageReference Include="Abp.ZeroCore.EntityFrameworkCore" Version="2.1.3" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="1.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="1.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer.Design" Version="1.1.2" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="1.1.1">
      <PrivateAssets>All</PrivateAssets>
    </PackageReference>
    <PackageReference Include="Microsoft.Extensions.Configuration" Version="1.1.2" />
  </ItemGroup>
  <ItemGroup>
    <DotNetCliToolReference Include="Microsoft.EntityFrameworkCore.Tools.DotNet" Version="1.0.0" />
  </ItemGroup>
  <ItemGroup>
    <Folder Include="Migrations\" />
  </ItemGroup>
</Project>

dotnet --info returns
.NET Command Line Tools (2.0.0-preview1-005977)
Product Information:
 Version:            2.0.0-preview1-005977
 Commit SHA-1 hash:  414cab8a0b
Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.0.0-preview1-005977\
Microsoft .NET Core Shared Framework Host
  Version  : 2.0.0-preview1-002111-00
  Build    : 1ff021936263d492539399688f46fd3827169983

Version 1.0.0 of the Microsoft.EntityFrameworkCore.Tools.DotNet package isn't compatible with the .NET Core SDK 2.0. Add the following global.json to your solution.
{
  "sdk": {
    "version": "1.0.4"
  }
}

For .NET Core 2.0 the script by @benday (a huge help) needs modifying.  The runtimeconfig arg was needed, a few other args were not.  Of course the early suggestion by using -v during a working migration helps.  Looking forward to a better solution when running EF commands outside of the csproj.
EfMigrationsNamespace=$1
EfMigrationsDllName=$1.dll
EfMigrationsDllDepsJson=$1.deps.json
DllDir=$PWD
EfMigrationsDllDepsJsonPath=$PWD/$EfMigrationsDllDepsJson
PathToRuntimeConfig=$PWD/$1.runtimeconfig.json
PathToNuGetPackages=$HOME/.nuget/packages
PathToEfDll=$PWD/ef.dll

dotnet exec --depsfile ./$EfMigrationsDllDepsJson --additionalprobingpath $PathToNuGetPackages --runtimeconfig $PathToRuntimeConfig $PathToEfDll database update --assembly ./$EfMigrationsDllName --startup-assembly ./$EfMigrationsDllName --project-dir . --verbose --root-namespace $EfMigrationsNamespace

Hey @Nogbit --
I've been meaning to post an update to the script.  I've got a batch script working but (for whatever reason) it seems like there's some inconsistency about where that ef.dll is located for some people's machines.
If you're trying to deploy from a TFS build or a TFS release, I've got a better solution that hides the existence of the ef.dll location and skips the deployment script.  You can download/install this TFS extension and use the Deploy EF Core Migrations task directly in your build.  https://marketplace.visualstudio.com/items?itemName=bendayconsulting.build-task
I do a demo of how to use that task in a DevOps video I did for Channel 9.  The ef core task part of the demo starts at about 48 min and 45 secs.  https://channel9.msdn.com/Events/dotnetConf/2017/T219
If TFS isn't an option, here's the updated batch script:
set EfMigrationsNamespace=%1
set EfMigrationsDllName=%1.dll
set EfMigrationsDllDepsJson=%1.deps.json
set DllDir=%cd%
set PathToNuGetPackages=%USERPROFILE%\.nuget\packages
set NuGetFallbackFolder="C:\Program Files\dotnet\sdk\NuGetFallbackFolder"
set PathToEfDll="C:\Program Files\dotnet\sdk\NuGetFallbackFolder\microsoft.entityframeworkcore.tools.dotnet\2.0.0\tools\netcoreapp2.0\ef.dll"

dotnet exec --depsfile .\%EfMigrationsDllDepsJson% --additionalprobingpath %PathToNuGetPackages% --additionalprobingpath %NuGetFallbackFolder% %PathToEfDll% database update --assembly .\%EfMigrationsDllName% --startup-assembly .\%EfMigrationsDllName% --project-dir . --data-dir %DllDir% --verbose --root-namespace %EfMigrationsNamespace%

-Ben

I'm building and deploying on and to Linux.  I have to manually copy that ef.dll from my nuget dir to my /bin/Release as part of a separate deploy bash script.  After the deploy runs it then runs the script I posted above.  Works great, even with zero nuget folders on the server.  Thanks for your help on this, it was your blog post I found when googling.

@Nogbit --
Managing the location of that ef.dll is about 75% of the problem, huh?  :)
FYI, my TFS build task is cross-plat and works on Linux and on Windows build agents.

Closing in favor of https://github.com/aspnet/EntityFramework.Docs/issues/691


[tracking] efm does not supports rootMarkers for linting

this is a tracking ticket for an issue to be fixed in efm - https://github.com/mattn/efm-langserver/issues/254
currently efm only checks for rootMarkers in formatting requests ( implemented in https://github.com/mattn/efm-langserver/issues/213 )
and skips the formatter if the root marker is not found
but it does not do this for lint requests
so the actionlint from #35 will run for ALL yaml files, not just yaml files inside a .githubdir

maybe not? though i am unable to get actionlint to skip generic yaml

found the real issue here https://github.com/creativenull/efmls-configs-nvim/pull/37


Opensource

My Open-source Project is about "CNCF"
It will help you understand about CNCF.
## Description 📜
Deliverables - 👇
Create a new repo under your own GitHub account.
Make 3 sample pages [eg - About open source, Version control system, about git/GitHub, etc] with whatever language you are comfortable with [may it be HTML, CSS, react, angular, etc.]
Host the same repo/website using GitHub pages, Heroku, or netlify [Whichever platform you are comfortable with]
Create a new file named projects made under this repo [if the file is already present no need to create again]
Paste you're hosted and GitHub URLs in it and create a PR
Fixes #401

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[x] Open Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[ x] I follow Contributing Guidelines & Code of conduct of this project.
[x ] I have performed a self-review of my own code or work.
[x ] I have commented my code, particularly in hard-to-understand areas.
[x ] My changes generates no new warnings.
[x ] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Create PR from your_fork_repo :Opensource branch to girlscript : Opensource branch


size of chart not 100% ok, left and/or right units are a bit offscreen

Hi,
I use 1.3.4 ..... and problems also with legend :-(
Here I want to point out, that the size of the chart might have problems:
some charts show units/ticks on the right side. Now there units might be off the screen, e.g. when some units are small in size (e.g. 0kWh) and other ticks are larger (e.g.14 kWh). Than the 14 kWh has not enough space and part of the letter h is not displayed, the small unit 0 kWh ist displayed exact (but not taking into account of larger units/ticks)
Other charts without left units/ticks leave a lot of space like some unvisible unit is there. This was different before, the left border of the chart was very near to the left side of the screen.
Other charts with left units/ticks are too small. not exactly like the right unit/ticks problem, but without the small/large background: everything is clipped a bit at the left side.
I guess that all these problems are closly related to each other, as they are all introduced around 1.3.0++
Good luck with 1.3.5!
cu
Harvey

Fixed in 1.3.5


Feature Idea: Preset Accordion Styling

Hi! I love this package! It makes setting up high quality accordions super convenient. One suggestion is it would be great to get some preset styling so that we don't have to write our own styling before pushing code to production.

Hey @prm-darrow thank you so much for the suggestion. We have provided a few styled examples that can help people quickly get started or preview the components. I generally feel that styling of an accordion is highly opinionated and tied to the system design being used. Thus it’s not very beneficial to include preset styling into this package. I'm closing this issue as of now.


Thank you!

Just wanted to say thank you ;)
Your script helped me a lot: https://gitlab.com/gitlab-org/gitlab-ce/issues/21608#note_22336463

sure! thanks to @abulimov for porting it to python. that was the hottest pull request of all time.


feat: initial version

what

This adds the first version of the module for Spacelift AWS Integrations.
Example of Integrations created from examples/complete:

why

Support all the desired Spacelift resources as code.

references

internal task

Summary by CodeRabbit

New Features

Updated the README to focus on managing Spacelift AWS integrations, including detailed usage examples and input/output parameters.
Introduced a new Terraform configuration file for integrating Cloud Posse's standard inputs.
Added a structured approach for AWS integrations, including specific configurations for each account.
New module and resource configurations enhance AWS integration capabilities.

Bug Fixes

Removed outdated output variables and ensured new outputs reflect current AWS integration mappings.

Documentation

Comprehensive updates to the README and examples to enhance clarity and usability for end-users.

Chores

Repository name and badge link updated to reflect the new focus on Spacelift AWS integrations.
Updated provider configurations to ensure compatibility with the latest requirements.

After reading this, I'm a little worried that these child modules for spaces + aws-integration are too simple... Let's roll with them and think on it, but in reading them... all we're doing is creating some additional layer abstraction over the original resources that doesn't provide much value e.g. it doesn't provide much useful business logic and they only wrap single resources. That concerns me, but I think we go with it for now. In the future, we may want to rethink how we ship these types of resources.

Yeah, that's why my initial idea was to to create a subfolder with these. modules in terraform-spacelift-automation. I think I spent more time on writing README + examples than on actual TF code 🙈

Yeah, that's why my initial idea was to to create a subfolder with these. modules in terraform-spacelift-automation. I think I spent more time on writing README + examples than on actual TF code 🙈

Yeah... :shipit:. Where we draw the line is hard. We have drawn it too wide this time around, but we'll come up with some better thoughts on how we deal with this in the future.


Add new runtime tests to validate the order of probe firing

Multiple probes are allowed to be attached to the same event. When this happens, bpftrace tries to ensure that the probes fire in the order that they're defined in the script.
e.g. this script should always print a sequence of "abc" and not "cba":
tracepoint:syscalls:sys_enter_read { printf("a") }
tracepoint:syscalls:sys_enter_read { printf("b") }
tracepoint:syscalls:sys_enter_read { printf("c") }

For reference, this is the code that controls the order in which we load duplicate probes and defines the order they fire in: https://github.com/bpftrace/bpftrace/blob/bc73244963f206814ae45ec78ebe52cd389f6381/src/bpftrace.cpp#L952-L976
This area of code may be changing in the future, with #3128 and/or #2334, so it'd be good to add some test coverage.
For as many of the different probe types as is practical, we should try to write new runtime tests that confirm they fire in the correct order.

I'd like to give it a try, can you assign me?

@shawnh2 sure, let us know if you need any help. Thanks!

Hi, sorry for the delay of this issue.
This runtime test, do you mean like: https://github.com/bpftrace/bpftrace/blob/1517d1cc9b7436069412d764ae32d34c9e58afd7/tests/runtime/probe#L352-L355
and
https://github.com/bpftrace/bpftrace/blob/master/tests/runtime/scripts/tracepoint_order.bt
but for other probes ?

Maybe another test for probes that are attached in reverse order would be good.

Yes, exactly like the tracepoint_order/kprobe_order/etc. tests (I'd forgotten we had those!), but for all the probe types we support.


Entity not created for backoffice

The implicit Backoffice clone and pull looks to run only on start, and does not create an associated repository in the DB. This prevents a deployment from pinning this to a specific release, as well as not having visibility of this from queries to the repositories endpoint.
This issue is more for discussion, rather than a bug / enhancement request - is this the correct behaviour?

There should be a base www repo (for nginx custom error pages etc) - backoffice doesn't need to be apart of this and we could have it as a default entry, not a difficult change. The current implementation is minimum viable product.
There should be a periodic pull of the www repo (I think once an hour)

backoffice is pulled here

@caspiano, that looks to be just a pull. There's no repository model created, which means that it is not listed by the /repositories endpoint.

I believe we are not explicitly creating a backoffice repository.

@KimBurgess it's not locked in stone though, open for discussion

We should definitely provide a way of pinning this so that deploy state is not bound to an external variable. Default behaviour could be to follow HEAD on a primary repo, but having a supported / simple way to break from this will assist with test environments, along with ensuring that people involved in running deployed instances have control over what is updated, when.
Given that there's already a mechanism for this via the existing repositories management, this seems like a neat fix.

Perhaps we should have an attribute to ensure that users cannot remove the backoffice repository, along the lines of a protected bool?

protected seems a bit much, need an init task so we can restore it / set it up initially


single quotes in MQTT trigger topics

Home Assistant release with the issue:

0.92.2
Last working Home Assistant release (if known):
unknown, if it ever worked
Operating environment (Hass.io/Docker/Windows/etc.):
virtual environment Python 3.5 on a Raspberry Pi 3
Component/platform:
https://www.home-assistant.io/docs/automation/trigger/
Description of problem:
MQTT trigger topics for automations don't support the use of single quotes.
Despite it should be avoided, on MQTT side it's allowed to have blank spaces in topics.
It works fine using double quotes or none at all. I can't tell if there is the different interpretation is expected behaviour, as I've not found any documentation about it.
We should either note it down in the documentation or support the use of single quotes to prevent others from tripping.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- alias: "this one works"
  trigger:
    platform: mqtt
    topic: "mytopic/status"
    payload: "click"
  action:
    - service:  notify.pushover
      data:
        title: 'Test message'
        message: 'MQTT event catched'

- alias: "this does not work"
  trigger:
    platform: mqtt
    topic: 'mytopic/status'
    payload: "click"
  action:
    - service:  notify.pushover
      data:
        title: 'Test message'
        message: 'MQTT event catched'

Traceback (if applicable):
no errors, warnings or other information are issued

Additional information:

In a 2nd take I couldn't recreate the problem.


How to delete nested item from form collection properties?

For example i have Album and a few Song in them, and i need add one song and remove two.
class Album < ActiveRecord::Base
   has_many :songs
end

class Song < ActiveRecord::Base
end

class AlbumForm < Reform::Form
  collection :songs do
     title
   end
end

And test for example:
album = Album.create(songs: [Song.new(title: 'song 1'), Song.new(title: 'song 2')])
attrs = {
  songs: [
    { title: 'song 3' }
  ]
}

put :update, song: attrs

expect(album.songs.count).to eq(1)

I mean maybe _destroy attributes, as in accept_nested_attributes

In chapter 7 of the book is an example how to do it manually. Here's the code: https://github.com/apotonick/gemgem-trbrb/blob/chapter-7/app/concepts/thing/crud.rb#L81
The chapter will be published in the next 10 days.

This is explained in chapter 7. Let me know if you still need help!!! :beers:


nixos/docker: ensure ipv4 forwarding is enabled

Motivation for this change
Fixes #118656
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

I believe this change broke evaluation when both docker and NAT are enabled, so this:
{
  networking.nat.enable = true;
  virtualisation.docker.enable = true;
}

leads to this:
error: The unique option `boot.kernel.sysctl.net.ipv4.conf.all.forwarding' is defined multiple times. Definition values:
       - In `/nix/store/fh7qqd2j7zkhfjzj31njl9k66b0fl3p3-source/nixos/modules/virtualisation/docker.nix': true
       - In `/nix/store/fh7qqd2j7zkhfjzj31njl9k66b0fl3p3-source/nixos/modules/services/networking/nat.nix': true
(use '--show-trace' to show detailed location information)

I think this should be reverted for now then. I am thinking if the following change would be useful though (I actually have little knowledge of the internals of the options system):
diff --git a/nixos/modules/config/sysctl.nix b/nixos/modules/config/sysctl.nix
index e59c7a32c28..a5ee435c956 100644
--- a/nixos/modules/config/sysctl.nix
+++ b/nixos/modules/config/sysctl.nix
@@ -11,7 +11,7 @@ let
         checkType = x: isBool x || isString x || isInt x || x == null;
       in
         checkType val || (val._type or "" == "override" && checkType val.content);
-    merge = loc: defs: mergeOneOption loc (filterOverrides defs);
+    merge = loc: defs: mergeEqualOption loc (filterOverrides defs);
   };

 in

if it is easy to fix, why reverting?

if it is easy to fix, why reverting?

Because I don't know of the side effects of my proposed fix but feel free to create the PR with my proposed change and maybe somebody knows whether that's a valid fix.

Thanks @mohe2015, I will do some research into it and then submit a PR. I kind of feel responsible for fixing this issue. I will then tag you in for review, if you don't mind.

Sure. https://github.com/NixOS/nixpkgs/pull/122810 is also a proposed fix that doesn't seems to have been linked.


Latest version does not work with react native 0.47.2

I was trying to use version v0.5.0 and I am bumping into  https://github.com/luggit/react-native-config/issues/83 while creating archieve. I was using v0.3.1 earlier. Downgrading it to v0.3.1 works fine.
P.S: This happens in production(release) mode. Attaching screenshot here for my production scheme pre build step.

mode

it works with 0.6.0... closing the issue


confuse about the depth supervision

Hi, thanks for your great work!
In the code and tutorial, the depth supervision is conducted on the rendered_depth. But in paper the depth supervision is on  ray termination, i.e., h(t).

Both of them are different ways of depth supervision. We provide both losses in the code.

Are they depth_loss and sigma_loss respectively?


Create builtin for Alejandra

https://github.com/kamadorueda/alejandra

Let's make it the oficial makes formatter.


brave: 1.71.118 -> 1.71.121

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for brave is: Privacy-oriented browser for Desktop and Laptop computers
meta.homepage for brave is: https://brave.com/
meta.changelog for brave is: https://github.com/brave/brave-browser/blob/master/CHANGELOG_DESKTOP.md#171121
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.71.121 with grep in /nix/store/scicsrf7l96a74321hv16gw30ajn2b18-brave-1.71.121
found 1.71.121 in filename of file in /nix/store/scicsrf7l96a74321hv16gw30ajn2b18-brave-1.71.121

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

brave

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/scicsrf7l96a74321hv16gw30ajn2b18-brave-1.71.121 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A brave https://github.com/r-ryantm/nixpkgs/archive/ab77e629960585dd61b61fd6e696b261c639ead2.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/ab77e629960585dd61b61fd6e696b261c639ead2#brave

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/scicsrf7l96a74321hv16gw30ajn2b18-brave-1.71.121
ls -la /nix/store/scicsrf7l96a74321hv16gw30ajn2b18-brave-1.71.121/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

brave

Maintainer pings
cc @uskudnik @rht @JeffLabonte @nasirhm @buckley310 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

LGTM. Tested web browsing with it.
@NixOS/nixpkgs-merge-bot merge


WIP - Address table: one to many address

What's new
Added get_unique_addresses_from_str method in functions.py module.
The function takes an address string, parses the string, and returns a list of all
unique addresses based on the following delimiters:

semicolon (;) - treated as delimiter for multiple unique addresses
'and' - treated as delimiter for multiple unique addresses
ampersand (&) - treated as delimiter for address number ranges
dash (-) - treated as delimiter for address number ranges

The function handles all potential composites of the delimiters noted above in a given address string. For processing composites, first handles 'complete' address delimiters (;, 'and'), and then address number range delimiters (&, -).
Notes
I intentionally did not include any address validation in this method because I feel that should be decoupled and applied as need in context outside of this utility method.
Testing
Review cases in unit test, run to confirm all tests pass. Add additional test cases if I missed any edge cases and run unit test.
To Do

Utilize the new function to complete the 'address table'

@jkwening this is great, and especially thank you for the super thorough testing.
We may end up needing a few more situations - unfortunately there's a bunch more messy formats. However I'd also like to send some of the one-off problem cases back up to the source and see if they'll fix them in their database instead of adding lots of extra logic to deal with it all on our end. We might consider adding a hotfix list for situations like that. Some examples in the DHCD data set that look like they might not be handled in this (albeit already robust) solution:

Incomplete use of dash address: 1401-09 11TH ST NW
Comma separated numbers: 1825,1827,1829,1837,1839,1841,1843,1845,1860,1862,1864 CENTRAL PLACE, NE
Mixing of commas and & for numbers: 24, 52, & 230 BATES ST NW
Mixing of commas and dash separated numbers with &: 1416-1428,1432,1436 & 1440 R ST NW
Different meaning of  &: HAYES STREET &ANACOSTIA AVENUE, NORTH EAST (this would be falsely split into two addresses, even though it's actually a street corner that should be one invalid address)

The one of those that I think makes sense to try to add is the comma separated numbers. The other odd ones I might put into a hotfix list that we map from current messy format into a parseable format and put the hotfix mapping as the first step of the get address function. What do you think?

Regardless of how we handle the rest of those cases, I'm merging this in now and will work on the next step of using this function to make the new table.

Moved this into an issue so let's continue the conversation in #496 instead of this PR since after merging it is hidden from the main pull request list.


Rename @export_range's noslider option to no_slider

As @Calinou suggested no_slider is more consistent with the other export range options such as "or_greater" and "or_lesser".

Thanks!


Add icons to cross margin trades

Add icons to differentiate isolated from cross margin trades in trade history (dashboard) and leaderboard.
Description

Add isolated and cross margin icons on two tables

Related issue

#1429

@asherism - We may want to consider adding these icons in other places but I didn't want to make the change without your feedback. Two places I considered:


Bug: "Provider returned invalid result object after apply" after applying an in-place update to timescale_service

│ Error: Provider returned invalid result object after apply
│
│ After the apply operation, the provider still indicated an unknown value
│ for timescale_service.RESOURCE_NAME.password. All values must be known after apply,
│ so this is always a bug in the provider and should be reported in the
│ provider's own repository. Terraform will still save the other known object
│ values in the state.

We're running into the same error when changing the memory_gb and milli_cpu values on an already existing database:
  # timescale_service.database will be updated in-place
  ~ resource "timescale_service" "database" {
      ~ hostname                  = "REDACTED.vpc.tsdb.forge.timescale.com" -> (known after apply)
        id                        = "REDACTED"
      ~ memory_gb                 = 128 -> 64
      ~ milli_cpu                 = 32000 -> 16000
        name                      = "production-tsdb"
      + password                  = (sensitive value)
      + pooler_hostname           = (known after apply)
      + pooler_port               = (known after apply)
      ~ port                      = 5432 -> (known after apply)
      + replica_hostname          = (known after apply)
      + replica_port              = (known after apply)
        # (7 unchanged attributes hidden)
    }

This results in the exact same error as the issue author reported, about the password not being available.
I think the problem here might be that this Terraform provider only outputs the password at service creation. From the docs:

The password is provided once during service creation

We store this password in an AWS secret after creation, but this seems to cause problems when doing an in-place update on a running instance. If we could provide our own password upfront and pass it to the resource, that would also work, unless the Timescale team has a better approach. Thanks!

the v1.12.0 provider release makes password a configurable attribute and should ultimately solve the import issue observed


pluggable storage

as per #419 - make it possible to replace the storage with a custom driver
Unfortunately I had to make this static/global config because the storage can't be a property of the Persistence class unless various static calls to Persistence.ensureDirectoryExists() are removed. Otherwise it would be easy to make the storage an option to Datastore and use multiple storage drivers at the same time.
This change is backwards compatible. When setStorage() is not called then simply the default storage driver is being used.
Browser and node tests pass.
Hope you accept this PR or use it as an inspiration for a different approach (for #419). Thanks.

new PR is on the way, please ignore this one...

New, improved PR: #427


Allow merging of custom and default completion items

My unsuccessful searching to solve this makes me think this needs to be a feature request - I would like the ability to merge the automatically generated completion items with my suggested completion items. I have a sample here - https://github.com/jhndnnqsc/monaco-test/blob/main/src/App.js. In this example, if the user hits ctrl+space provideCompletionItems returns an empty array and the automatic list is shown.

If the user hits the '.' character a suggestion list is returned - in this case only the suggested items are included

It seems like it would be useful to be able to automatically combine the two lists - if there is a method for that already please let me know.

@alexdima This looks like a duplicate of #1850 to me.


etcdserver: set applied index correctly

Fix https://github.com/coreos/etcd/issues/5950
/cc @gyuho

@heyitsanthony Fixed.

lgtm. thanks!

@xiang90 Could you explain how this fixes that ErrTooManyRequests issue for me? Thanks.

lgtm

@gyuho This does not need to be back-ported. We recently added a new mechanism to ensure the max gap between committed index and applied index, so that we wont submit proposal faster than we can apply. See https://github.com/coreos/etcd/pull/5927. We need to ensure the applied index is calculated correctly.

@xiang90 Got it. Thanks!


Running the test code

So I configured a docker with your code and exact code copies.
The configuration file lists
# Parameter section begins here. Edit to change number of test scenes, which model to use, output path.
MAX_NUM_TEST_SCENES=1
NUM_HIERARCHY_LEVELS=3
BASE_OUTPUT_DIR=../results

# Fill in path to test scenes
TEST_SCENES_PATH_3='../data/vox19'
TEST_SCENES_PATH_2='../data/vox9'
TEST_SCENES_PATH_1='../data/vox5'

# Fill in model to use here
PREDICT_SEMANTICS=0
HIERARCHY_LEVEL_3_MODEL='../models/completion/hierarchy1of3'
HIERARCHY_LEVEL_2_MODEL='../models/completion/hierarchy2of3'
HIERARCHY_LEVEL_1_MODEL='../models/completion/hierarchy3of3'

# Specify output folders for each hierarchy level.
OUTPUT_FOLDER_3=${BASE_OUTPUT_DIR}/vis_level3
OUTPUT_FOLDER_2=${BASE_OUTPUT_DIR}/vis_level2
OUTPUT_FOLDER_1=${BASE_OUTPUT_DIR}/vis_level1

When running the shell script from src folder, the first hierarchy is loaded, but when it tries to save the results I get an error
Processing hierarchy level 3, scene 1 of 1: ../data/vox19/e582d82458819d07c184a49feac3ca85__0__.tfrecords.
Traceback (most recent call last):
  File "complete_scan.py", line 394, in <module>
    tf.app.run(main)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/platform/app.py", line 125, in run
    _sys.exit(main(argv))
  File "complete_scan.py", line 325, in main
    assign_fn(session)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/framework/python/ops/variables.py", line 697, in callback
    saver.restore(session, model_path)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/saver.py", line 1713, in restore
    raise ValueError("Can't load save_path when it is None.")
ValueError: Can't load save_path when it is None.

Which in my opinion means that the paths are somehow configured incorrectly. Any clues on where to look?

I ran it and got the same error. Have you solved it?

Since I am posting this nope

Changed the tensorflow version back from 1.10 to 1.3 same issue
This makes me believe it is in the paths still somewhere and not in the actual tensor code behind it

Will keep trying stuff out, we really need this implementation to work :D

I retraced the issue to the following line. This is for the GPU version of tensorflow. Going to check whether CPU has same issues.
To me it seems that in the lines below
if FLAGS.model_checkpoint:
      checkpoint_path = os.path.join(model_path, FLAGS.model_checkpoint
else:
      checkpoint_path = tf.train.latest_checkpoint(model_path)
assign_fn = tf.contrib.framework.assign_from_checkpoint_fn(
      checkpoint_path, tf.contrib.framework.get_variables_to_restore())

are the actual issue, where I am guessing the pretrained checkpoints of the model are read from the folder. However, it seems that at the end of this loop, in the first iteration, checkpoint_path stays empty, and thus running the assign_fn code, fails because paths are incorrect.
Will keep you posted on the evolution.

Same issue for GPU version.
All the subsequent errors are due to the fact that in the first run the result cannot be saved, and thus in hierarchy level 2, there is nothing to grab from level 1.

I found this page where the following is stated

So, to summarize, Tensorflow models for versions greater than 0.10 look like this:
checkpoint file
*.data file
*.index file
*.meta file

Which means that basically the interface of TF 1.3 is expecting a checkpoint file pointing to the last saved state. I will now look into what to generate for this.

Ok solution found, you need for each model folder a file called checkpoint with the following content
model_checkpoint_path: "model.ckpt"
all_model_checkpoint_paths: "model.ckpt"

Once you have that, it works glamoursly :) @angeladai  I suggest you add those to help people in the future =/

good job, dude!
by the way,
HIERARCHY_LEVEL_3_MODEL='../models/completion/hierarchy1of3'
HIERARCHY_LEVEL_2_MODEL='../models/completion/hierarchy2of3'
HIERARCHY_LEVEL_1_MODEL='../models/completion/hierarchy3of3'

seems should be
HIERARCHY_LEVEL_3_MODEL='../models/completion/hierarchy3of3'
HIERARCHY_LEVEL_2_MODEL='../models/completion/hierarchy2of3'
HIERARCHY_LEVEL_1_MODEL='../models/completion/hierarchy1of3'

@livc thats only an impression ;) we eventually changed the inner concepts, but somehow, and for some weird reason, they switched it up ... be aware of that when running the default model. In the long run we replaced everything with vox19cm vox9cm and vox5cm labels instead of 1of3 2of3 and 3of3

HI
I am having some error when running sh run_complete_scans_hierarchical.sh
I have specify the path to model and test scene in run_complete_scans_hierarchical.sh file.
PLEASE can you take a look to this ERROR:
Use eager execution and:
tf.data.TFRecordDataset(path)
Traceback (most recent call last):
File "complete_scan.py", line 396, in
tf.app.run(main)
File "/home/shanshan/anaconda3/envs/tf2.7/lib/python2.7/site-packages/tensorflow/python/platform/app.py", line 125, in run
sys.exit(main(argv))
File "complete_scan.py", line 302, in main
FLAGS.num_quant_levels, FLAGS.p_norm, FLAGS.predict_semantics)
File "complete_scan.py", line 130, in read_inputs
assert os.path.isfile(previous_file)
AssertionError
run_complete_scans_hierarchical.sh: 107: run_complete_scans_hierarchical.sh: count++: not found
run_complete_scans_hierarchical.sh: 108: run_complete_scans_hierarchical.sh: count: not found
Processing hierarchy level 1, scene 1 of 1: /home/shanshan/Documents/vox5/e78488fccfc6871503d32753d43aa6ce__0_.tfrecords.

Ok solution found, you need for each model folder a file called checkpoint with the following content
model_checkpoint_path: "model.ckpt"
all_model_checkpoint_paths: "model.ckpt"

Once you have that, it works glamoursly :) @angeladai I suggest you add those to help people in the future =/

hi @StevenPuttemans
that means to copy that checkpoint file inside of the models folder ?


simple markdown support for chat

it would be useful for mentors to have markdown formating when it comes to messages
often things like how to rename room follows

you need to !boss yourself first
then do $rename namehere

would be better to look as

you need to !boss yourself
then do $rename

If we implement this: we should avoid rendering the headers [#]. The larger text could be abused / obnoxious in chat.


Accept "sso" tag

I'm developing a service broker compatible with Single Sign-On for PCF.
https://github.com/maki-home/uaa
Because spring-cloud-sso-connector only accepts the service whose name is p-identity, my service broker can't leverage with this connector.
This commit allows this connector to accept services which contains sso in the tags.

Any chance you could have a look?


Bring back the 2 separate buttons for tips and supports

Is your feature request related to a problem? Please describe.
Merging together tips and supports into a single interface makes it significantly easier to accidentally send a tip to someone when you intended it to be a support, having a checkbox to decide whether you're sending a tip or support isn't enough separation between these 2 concepts.

This will burn a lot of new users who don't understand the difference.
Describe the solution you'd like
Provide 2 separate buttons for tip and support like has been previously done up until now, doing this doesn't require making a new interface for supports to be made as it already exists when you try to support your own content

Describe alternatives you've considered
An alternative to this is using a single interface and providing multiple tabs rather than using a checkbox as the current implementation uses.
Additional context
I'm not going to risk sending supports to any users besides myself while this interface exists.

This doesn't limit the number of choices, they still have the choice between tip and support but now the support option has just been made a little harder to find. If most users have no idea what a support is then it's important to show them an interface that explains what it is and luckily you guys have already made an interface that does that when supporting your own channel.

Please do this sooner rather than later. I put a lot of money on supports for other creators and am going to end up clicking the wrong button at some point... or just stop supporting other creators until I know that the possibility that I can simply tick/confirm and lose my money is gone.

This doesn't limit the number of choices, they still have the choice between tip and support but now the support option has just been made a little harder to find.

^ agreed.
Also. Having a tick/confirm as the barrier between "support" and "lose all your money" is not a UX that can "be used by a drunk person in the dark." (A card change does not do much).
I'm sure there are other ways to simplify things for new users while also encouraging tip usage. A wizard, perhaps?
I remember someone on discord -- I think it was actually @BrodieRobertson -- suggested simply changing the term "Support" to "Boost" and having a "Boost" button and a "Tip" button.

We're going to make a change here again in the near future.


use decimal numbers for logging packet numbers, stream offsets and byte counts

Codecov Report

Merging #2497 into master will decrease coverage by 0.11%.
The diff coverage is 68.75%.

@@            Coverage Diff             @@
##           master    #2497      +/-   ##
==========================================
- Coverage   85.90%   85.79%   -0.11%
==========================================
  Files         122      123       +1
  Lines        9425     9452      +27
==========================================
+ Hits         8096     8109      +13
- Misses        986      996      +10
- Partials      343      347       +4

Impacted Files
Coverage Δ

internal/ackhandler/received_packet_tracker.go
79.55% <0.00%> (ø)

internal/ackhandler/sent_packet_handler.go
71.05% <0.00%> (ø)

session.go
73.99% <0.00%> (-1.09%)
:arrow_down:

internal/flowcontrol/stream_flow_controller.go
100.00% <100.00%> (ø)

internal/wire/extended_header.go
88.57% <100.00%> (ø)

internal/wire/log.go
87.50% <100.00%> (-1.97%)
:arrow_down:

internal/wire/transport_parameters.go
89.38% <100.00%> (ø)

internal/congestion/cubic_sender.go
90.78% <0.00%> (-1.47%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


Name catalogs

Please use more meaningful names for ids of catalogs to see what is master and navigation catalog more easily. Right now we get only long numbers, likely the hash or seed.

Agree that naming them would be helpful. Would adding a (random) name in front help?

Purpose would be nice first aka storefront/navigation/master plus something unique.


Target native CPU on foundryup -b

We should compile Foundry with RUSTFLAGS="-C target-cpu=native" cargo build --release --bin forge if you use foundryup -b.
https://github.com/gakonst/foundry/pull/918#issuecomment-1071732702

should we also do this on -r as well (assuming the value is not set to the main repository)?

Yes

Fixed


NO OUTPUT [SELECT] STORE PROCEDURE ORACLE

HI, have a problem with de out data in my store procedure.
i need out a lot data in a SELECT * FROM [TABLE] but de program or somtheng else not work.
example:
CREATE OR REPLACE PROCEDURE GESTION_DESA.GETAPPS(RT OUT SYS_REFCURSOR)
IS
BEGIN
OPEN RT FOR
SELECT * FROM sistema_aplicacion;
END GETAPPS;
execute:
DECLARE ouput_ refcursor;
exec getapps(ouput_);
ERROR:
SQL Error [6550] [65000]: ORA-06550: línea 5, columna 0:
PLS-00103: Se ha encontrado el símbolo "end-of-file" cuando se esperaba uno de los siguientes:
begin function pragma procedure subtype type
 current cursor delete
exists prior
System information:

Operating system (distribution) and version w10
DBeaver version 7.1.1
Additional extensions

declare doesn't work that way, in Dbeaver at least, it would be the opening of a pl/sql block. Also dbeaver uses CALL instead of EXEC for calling a stored procedure.
Not entirely sure, but you could try
call getapps(?);

The ? should work as an output parameter, but never tried it myself.

@apeiranoIS Do you have a possibility to check the advice?

there isn't update on issue for a long time.
Ticket closed. If issue is still actual for you - feel free to reopen the ticket with additional info.