Federated Server functions

Add some new functions to manage a federated server.
This includes parts of the code from https://github.com/CartoDB/cartodb-postgresql/pull/373 and https://github.com/CartoDB/cartodb-postgresql/pull/381 and probably deprecates code recently added to CDB_ForeignTable.
As a WIP it still misses quite a bit of tests around corner cases (server / schema not existing, odd names...) and has some TODO's left (permissions, possible improvements) but it can be reviewed so we confirm this is the API we want to use.
Public functions:

CDB_Federated_Server_List_Servers(server TEXT DEFAULT '%')
CDB_Federated_Server_Register_PG(server TEXT, config JSONB)
CDB_Federated_Server_Unregister(server TEXT)
CDB_Federated_Server_List_Remote_Schemas(server TEXT)
CDB_Federated_Server_List_Remote_Tables(server TEXT, remote_schema TEXT)
CDB_Federated_Table_Register(
server TEXT,
remote_schema TEXT,
remote_table TEXT,
id_column TEXT,
geom_column TEXT DEFAULT NULL,
webmercator_column TEXT DEFAULT NULL,
local_name NAME DEFAULT NULL
)
CDB_Federated_Table_Unregister(
server TEXT,
remote_schema TEXT,
remote_table TEXT
)
CDB_Federated_Server_List_Registered_Tables(
server TEXT,
remote_schema TEXT
)

Hope listings have some ORDER BY somewhere to avoid testability issues.

All listing functions use ORDER BY so it's covered.


Update reference generator for 1.21

This PR updates the configuration API reference generator for 1.21. Main changes:

Update go.mod version for 1.21 (v0.21.0 for vendored packages)
Introduce klog for logging/debugging
Updated Makefile considering that Go 1.16 has some issues related to using modules

/lgtm


Unable to switch to VR mode using Ctrl + Tab keys in MSFS2020 using PimaxXR v0.4.0 on 8KX

Describe the bug
Unable to switch to VR mode using Ctrl + Tab keys in MSFS2020. Pressing the keys does not turn on VR in my Pimax 8KX headset.
Environment

PimaxXR v0.4.0
PiTool v<IP_ADDRESS>7
Pimax 8KX with Firmware v<IP_ADDRESS>9
MSFS2020 v<IP_ADDRESS>

PimaxXR runtime settings (as per default on install)

To Reproduce

Start PiTool .
Start headset.
Start PimaxXR, ensure set to PimaxXR mode
Run MSFS2020 from PiTool Game list.
Create a new flight, and wait for it to load.
Press Ctrl + Tab keys.

Expected behavior
MSFS2020 switches to VR mode and I can see the image in the headset.
Log file
pimax-openxr.log
Workaround
Uninstall PimaxXR v0.4.0, then install PimaxXR v0.3.4 - Ctrl + Tab keys work as expected and can use headset.

Based on the log file you are just seeing a transient bug from Pitool. A reboot should fix it.
Also this version of Pitool is largely outdated, you are something like 9 versions behind... please upgrade.

Based on the log file you are just seeing a transient bug from Pitool. A reboot should fix it.
Also this version of Pitool is largely outdated, you are something like 9 versions behind... please upgrade.

Thanks for your fast response. PC restart did not resolve the issue.
Check Version in PiTool states I already have the latest version. At Pimax download site a newer version doesn't exist, and I can't find anything else on their web site to suggest a newer version is available. I found this link but it's not a Pimax domain link so I'm not going to risk running it.

If that did not solve the issue then it just means 0.4.0 isn't compatible. But again your pitool is over a year old.
The check for update feature is broken.
Pimax is really bad at publishing official updates
You can see here their announcement for the new release of Pimax Client.
https://www.reddit.com/r/Pimax/comments/14az2e7/pimax_client_v112/

If that did not solve the issue then it just means 0.4.0 isn't compatible. But again your pitool is over a year old.
The check for update feature is broken.
Pimax is really bad at publishing official updates You can see here their announcement for the new release of Pimax Client.
https://www.reddit.com/r/Pimax/comments/14az2e7/pimax_client_v112/

I found this link for Pimax Client versions - once I realized Pimax Client replaces installing PiTool directly.
After installing Pimax Client inc. upgrading it to v<IP_ADDRESS>, the Ctrl + Tab keys in MSFS2020 now work to switch to VR.
Thank you for your help! 👍

It's a little confusing yes. Glad it's working now.


Minor improvements & cleanup after #13

Hi @platisd just a minor cleanup:

Replace += by =;
Rename variables to better express their meaning;
Remove extra variables.

Unfortunately, current version is still not able to work properly with multi-line fixes like this one. However, I have no idea yet how to implement this properly, because I don't know how to create suggestions on GitHub that refer to multiple lines at once (AFAIK this is just impossible, but I may be wrong). I can try to split such suggestions into separate lines and then create a separate entry for each line, but I don't want to do this yet :)

because I don't know how to create suggestions on GitHub that refer to multiple lines at once (AFAIK this is just impossible, but I may be wrong).

From what I recall, GitHub has yet to offer an API for this, so you're right!

Unfortunately, current version is still not able to work properly with multi-line fixes like this one.
....
I can try to split such suggestions into separate lines and then create a separate entry for each line, but I don't want to do this yet :)

Hmmmm, it gets more complex indeed. :/ I'll try to give it some thought too.


Review and make an analysis about what is failing within "Filter by value" analysis form

There are several bugs described in this milestone, but we should check if the current implementation could be valid and good for the future or we should redone it.
In my opinion, we should, at least, add those necessary tests we don't have right now. Apart from that, fix those ugly JS bugs we have in some scenenarios. But in any case, a small research and analysis about what should be changed is necessary.
cc @matallo @nobuti

There are also some features missing such as getting the TOP / BOTTOM X results based on a numeric column.

I added the missing tests for filter by value in https://github.com/CartoDB/cartodb/pull/12199, but as the implementation is likely to change, they would probably change too
¯\_(ツ)_/¯

Stale issue. Closing 👋


Autodiff to require C++17?

Hi @kedarbhat,
In the dev-atan2 branch I just commited an update to apply_coefficients_with_horner() that includes the use of lambdas that accept a parameter pack. This is called by atan2(). In the case of atan2(), there are 2 independent variables but I wanted to use this opportunity to motivate a helper function apply_coefficients_with_horner() that generalizes to any number of independent variables. This seems to be most efficiently written with lambdas that accept auto... parameters.
Do you see a reasonable way to implement this in C++11 with MSVC14 compatibility?
I've added example/atan2.cpp to test it with, along with updating test/test_autodiff5.cpp.

Since generic/variadic lambdas are involved, there are a few things that might work; GCC has an extension for template lambdas (different syntax than normal generic lambdas), but I doubt this would be portable. A function object would be the most straightforward way to do this, I think.

A function object would be the most straightforward way to do this, I think.

Good idea, I'll try that.

I've created a Curry template class for the C++11 version to mimic the [&](auto... indices){} variadic lambda in the C++17 version. This is getting close, but gives a linker error when compiling in C++11:
g++ -std=c++11 -Iinclude -I$HOME/src/boost_1_70_0 example/atan2.cpp

undefined reference to `boost::math::differentiation::autodiff_v1::detail::fvar<double, 5ul>::order_sum'

This looks similar to issues around odr-use of the static constexpr size_t order_sum member as discussed here for instance. (Though it's possible it's a different diagnosis altogether.) I was wondering if you would be able to take a shot at supporting this in C++11? The C++17 version works fine. The Curry class isn't needed, if you see a better way around it. The goal would just be to support the functionality of the apply_coefficients template functions in C++11 from the dev-atan2 branch without having to downgrade the C++17 version.

I’ll take a look in a little bit.

Thank you. I'd like to better understand why this is happening for C++11. In the meantime, I added a conditional preprocessor check in apply_coefficients to emphasize that this is a hack:
#ifndef BOOST_NO_CXX17_IF_CONSTEXPR
    size_t i = std::min(order, order_sum);
#else
    size_t i = std::min(order, get_order_sum<fvar<RealType,Order>>::value);
#endif

I'm using Definitions and ODR as my reference. I also found a similar problem on stackoverflow.com.
Taking the code back to commit d658a48f6249eed5cebe0d0b93953bf579a11b28). Here are some observations about the issue which finally manifested:
We're missing namespace scope declarations of order_sum and depth**. This should have broken other parts of the code, and we've never had namespace scope declarations of those variables, so this doesn't entirely make sense of the issue, but it does "fix" the code if the declarations are added at namespace scope as below:
template<typename RealType, std::size_t Order>
constexpr std::size_t fvar<RealType, Order>::depth;
template<typename RealType, std::size_t Order>
constexpr std::size_t fvar<RealType, Order>::order_sum;

In C++17, the requirement for a namespace scope definition of a static constexpr data member is deprecated, which is why you were able to build in C++17 without issue, but C++11/C++14 both failed.
Not understanding why this hasn't been an issue previously, I see that the only uses of order_sum that are ODR-used are those uses wherein order_sum is passed into std::min.
size_t i = std::min(order, order_sum);
Since std::min accepts it arguments as references, we need namespace scope declarations if we're going to pass in order_sum as an argument.
Changing the std::min lines (causing ODR-usage) to size_t i = order <= order_sum ? order : order_sum;, the problem disappears.
I'll send a PR shortly, but to maintain portability and to avoid cluttering the code unnecessarily, we can use aliases to std::integral_constant for depth/order_sum, and will need to add ::value to access the static constant within std::integral_constant.  The point of this is to keep the code as standard-agnostic as possible.

to maintain portability and to avoid cluttering the code unnecessarily, we can use aliases to std::integral_constant for depth/order_sum, and will need to add ::value to access the static constant within std::integral_constant. The point of this is to keep the code as standard-agnostic as possible.

Generally speaking, I really don't want to sacrifice new C++ language features for backward compatibility. This is the whole reason for a separate autodiff_cpp11.hpp file.
This change seems to me to be a downgrade of the C++17 version. I would really like to keep order_sum as either a constexpr variable or method. I would much rather keep the version with:
#ifndef BOOST_NO_CXX17_IF_CONSTEXPR
    size_t i = std::min(order, order_sum);
#else
    size_t i = std::min(order, get_order_sum<fvar<RealType,Order>>::value);
#endif

to make it clear that there is compiler-versioning issue here.
In any case, thank you for looking into this and bringing clarity to this issue.

Actually thanks to your research this code makes the issue more clear 7818e27b
#ifndef BOOST_NO_CXX17_IF_CONSTEXPR
    size_t i = std::min(order, order_sum);
#else
    size_t i = order < order_sum ? order : order_sum;
#endif


Include decoded logs in forge test --json

Component
Forge
Describe the feature you would like
forge test --json currently includes raw logging information in its output, e.g:
        "logs": [
          {
            "address": "0x0000000000000000000000000000000000000000",
            "topics": [
              "0x41304facd9323d75b11bcdd609cb38effffdb05710f7caf0e9b16c6d9d709f50"
            ],
            "data": "0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000033132330000000000000000000000000000000000000000000000000000000000"
          }
        ],

It would be nice if it could also include the decoded/interpreted logs, as commands consuming this json are not likely to have the ability to decode these logs.
Additional context
This is to support parsing test output information for inclusion in an editor plugin which allows forge tests to be run continuously when developing.

Is this feasible, and if so, does the forge team agree that it would be useful? Trying to figure out if I should go down another path for testing results rather than using the json :)

I can't think of any downside here, since this is just additional info
should be easy to add

I will like to work on this one @mattsse as my first foundry contribution please. :grin:
@Willyham Can you give an example of the json output you want ?

Good question, I hadn't really thought of that. Possibly it should just be an extra field of logLines or decodedLogs or something in the existing output?
The existing non-json command simply prints the logs for each test, so I don't think there's any more structured data available that we'd want anyway?

Existing format looks like this:
{
  "test/Contract.t.sol:ContractTest": {
    "duration": {
      "secs": 0,
      "nanos": 287125
    },
    "test_results": {
      "testComplexFunc()": {
        "success": true,
        "reason": null,
        "counterexample": null,
        "logs": [
          {
            "address": "0x0000000000000000000000000000000000000000",
            "topics": [
              "0x41304facd9323d75b11bcdd609cb38effffdb05710f7caf0e9b16c6d9d709f50"
            ],
            "data": "0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000011546869732069732061206c6f6720313030000000000000000000000000000000"
          }
        ],
        "kind": {
          "Standard": 8602
        },
        "traces": [],
        "labeled_addresses": {}
      },
      "testComplexFuncAgain()": {
        "success": true,
        "reason": null,
        "counterexample": null,
        "logs": [
          {
            "address": "0x0000000000000000000000000000000000000000",
            "topics": [
              "0x41304facd9323d75b11bcdd609cb38effffdb05710f7caf0e9b16c6d9d709f50"
            ],
            "data": "0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000012546869732069732061206c6f6720313030300000000000000000000000000000"
          }
        ],
        "kind": {
          "Standard": 8636
        },
        "traces": [],
        "labeled_addresses": {}
      }
    },
    "warnings": []
  }
}

Maybe a decoded (or should it be deserialized?) property within the logs array?

What should this property look like really ? Do you want to decode the event data or its signature ? :grin:

We want the same log data which is printed by the CLI. In the above case the logs were generated by calling console.log from solidity. We need to turn the encoded data into a UTF-8 string (I'm assuming it's utf8 encoded).
Example of print from the CLI:
[PASS] testComplexFunc() (gas: 8602)
Logs:
  This is a log

The string "this is a log" should be included for this test in the json output. Note that there may but multiple logs per test, and each should be distinct (so we probably want an array of decoded logs)

Sorry for the delay @Willyham ! :sweat:
A decoded_logs field will be available on the tests json output once the #3543 PR is merged.


Not able to integrate this plugin in my angular 2 based project

Hi Rafal,
I am trying to integrate this plugin in my angular 2 based project. I followed the declaration structure as mentioned in Demo example. npm is throwing error when FileManager module is imported in @NgModule
After adding FileManagerModule in @NgModule import section I am always getting errors as-
ERROR in ./src/app/admin/admin.module.ts
Module not found: Error: Can't resolve '@rign/angular2-filemanager/main' in 'myproject\src\app\admin'
resolve '@rign/angular2-filemanager/main' in 'myproject\src\app\admin'
  Parsed request is a module
using description file: myproject\package.json (relative path: ./src/app/admin)
    Field 'browser' doesn't contain a valid alias configuration
  after using description file: myproject\package.json (relative path: ./src/app/admin)
    resolve as module
myproject\node_modules doesn't exist or is not a directory.

Hi,
Demo used internal src directory to import FilemanagerModule. In you project you should install @rign/angular2-filemanager in latest version (currently, 1.3.0) and import all package elements form '@rign/angular2/tree', so it should like:
import {FilemanagerModule} from '@rign/angular2-filemanager
Please, give me feedback if I have right

Thanks Rafal. You are right. I was trying import modules from
import {FilemanagerModule} from '@rign/angular2-filemanager/main'

Hi Rafal,
Sorry to disturb you again but need your help in 2 issues.

Now when running that file manager page in browser console gives an StaticInjectorError as below -

can you explain or guide me, how to implement the back-end API side functionality to link tree folder structure to blob storage

Ad. 1.
It seems that you miss some other modules that have to be initialized:
imports: [
  ...,
  BrowserAnimationsModule,
  ConfirmationPopoverModule.forRoot(),
  EffectsModule.forRoot([]),
  FileManagerModule.forRoot(fileManagerConfiguration),
  StoreModule.forRoot({}),
  TreeModule.forRoot(),
  TranslateModule.forRoot(),
]

Ad.2 You have to implement on your backend endpoint to get list of items like this one
interface IOuterNode {
    id: string;
    treeId?: string;
    name: string;
    parentId?: string | null;
    children?: Array<string>;
    parents?: Array<string>;
}

Also endpoint for files should return list of items like
interface IOuterFile {
    id: string | number;
    folderId?: string;
    name: string;
    thumbnailUrl: string;
    url: string;
    width: number;
    height: number;
    type: string;
    data?: string;
    size?: number;
    selected?: boolean;
}

Duplicated comment #20


Fixed small typo on afterChangeHook params

Description

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

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

Checklist:

[x] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[x] I have made corresponding changes to the documentation

Hey @gonzam88 — I believe this is an incorrect change. Looking at the global update operation here:
https://github.com/payloadcms/payload/blob/master/src/globals/operations/update.ts#L250
It looks like the afterChange argument does indeed contain doc and not data. Am I missing something?

Oops you are right. I meant to change line 76  where return data; should be return doc; right? Sorry for the mixup


RC Spot-Check Test: keplers-laws 1.1.0-rc.3

RC Spot-Check Test
Mentions: @AgustinVallejo @DianaTavares @arouinfar @kathy-phet
Simulation links

github repository for issues
phet top-level directory
sim: all_phet.html

Test Matrices
General Test:

[x] Tester = NS , Platform = mac + safari, Time = .5
[ ] Tester = , Platform = , Time =

Additional Features Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Features included

[x] Alternative Input
[x] UI Sound
[x] Sonification

Focus and Special Instructions

Issues to Verify
These issues should have the "status:ready-for-review" label. Unless an issue says to close after verifying, assign the
issue back to the developer.

[x] https://github.com/phetsims/keplers-laws/issues/185
[x] https://github.com/phetsims/keplers-laws/issues/184
[x] https://github.com/phetsims/keplers-laws/issues/177
[x] https://github.com/phetsims/keplers-laws/issues/80

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test some query parameters. (See QA Book for a
list of query parameters.)
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
is a problem.
As the RC ends, notify the developer of any new QA credits that need to be added.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

@KatieWoe could you please include the QA credits after you guys are done with this? Thanks! We're very close!

https://github.com/phetsims/keplers-laws/issues/80 Today we discussed about the credits and I was told linking this issue is helpful.

@AgustinVallejo and @DianaTavares does it matter that the axes rotate when checking/unchecking Always Circular?
https://github.com/phetsims/qa/assets/87318828/9765f0cd-6af5-40ba-92b4-4d2a2351704b

I also noticed some visual oddities when changing the window size. Probably not worth an issue, but let me know if you want one.

Spot check is done

@KatieWoe yes, could you please open an issue for that? Even if it probably gets deferred, to have it on record, because it definitely seems odd and doesn't seem to be happening to other sims.


Trace trap? Nsfw filter?

Occasionally, I noticed that I am not getting result and getting "trace trap"? Is there like safety filter with Swift Diffusion? Can I just turn it off because it's local anyway.

This was actually when I tried running img2img for the first time. It never worked. I did supply the init_img.png

On the other computer (intel mac), it also crashes:
(mpsFileLoc): /AppleInternal/Library/BuildRoots/810eba08-405a-11ed-86e9-6af958a02716/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm:288:0: error: the result shape is not compatible with the input shape
(mpsFileLoc): /AppleInternal/Library/BuildRoots/810eba08-405a-11ed-86e9-6af958a02716/Library/Caches/com.apple.xbs/Sources/MetalPerformanceShadersGraph/mpsgraph/MetalPerformanceShadersGraph/Core/Files/MPSGraphUtilities.mm:288:0: note: see current operation: %3 = "mps.reshape"(%1, %2) : (tensor<8454272xf32>, tensor<5xsi32>) -> tensor<1x128x257x32x8xf32>
Segmentation fault: 11

Are you on NHWC branch? I didn't tweak img2img with NHWC yet. main branch should work on M1s.

If you pull the latest on liu/nhwc, it should work for img2img now. Did necessary tweak to make it work.

It did not work on both, I tried it first on the master, but it keeps on complaining, "trace trap". Can you make a video demo maybe I missed something.
I have the model in one folder, and the output will be in the same folder as the model.
I know the example script is all in different folder. So what I did was just to replace txt2img line into img2img, with source image in the same folder as main.swift of img2img, but still not working, I don't know why.
Can you have example script for img2img? Thanks.

One thing to keep in mind, where the main.swift file is carries no significance at all.
For usage example:
I will put init_img.png, with exactly 512x512 size (this is important as I don't resize in the script at all, again, these scripts are more like demos) under /Users/administrator/workspace/swift-diffusion. This is the same directory where sd-v1.4.ckpt resides. Then, I can run:
bazel run examples:img2img --compilation_mode=opt -- /Users/administrator/workspace/swift-diffusion "horse riding with mid-century armors, intrinsic details, volumentric lighting"

If this still crashes, try to run:
bazel run examples:img2img --compilation_mode=dbg -- /Users/administrator/workspace/swift-diffusion "horse riding with mid-century armors, intrinsic details, volumentric lighting"

--compliation_mode=dbg will give more error messages than the trace trap you saw.
So two things important here:

make sure the directory for init_img.png is the same as you put the model file;
make sure the file is exactly 512x512 in dimensions.

That's it, I missed STEP ONE! I originally put the init_img.png under img2img folder.

However every now and then, I still did get crashing "zsh: trace trap  bazel run examples:img2img --compilation_mode=opt --  " --> safety feature? Can I remove this?

There is no safety features. Probably something to do with NaN's. I haven't fully figured out, but sometimes it will end up with some NaN's and need to re-run. Probably from seeding, or from fp16 compute. You can switch back to FP32 to see if the error gone.

I tried Float32, but somewhat the calculation become really long time, the final result looking amazing however (not sure if changing the Float affect the output of stable diffusion).
So my trick is simply to make .script file with 1000 lines of bazel swift diffusion command to do batch output.
So the NaN issue still happen time to time again.

I use the M1 more, because it's faster, 40 seconds to generate output. The Intel one is too slow 10 minutes per image if lucky.
Let say I make 100 batch overnight, just a few will give NaN and move to the next one.
I usually generate image + seed number (random), the one that crashes will escape/produce none. Maybe I could print the seed? and give you prompt as well to check why this happens?

Yeah, if you did the following modification, it would generate a "runtime-data-seed.dbg" file upon crash, and this will give me a good initial point for txt2img debug:
https://github.com/liuliu/swift-diffusion/compare/liu/nhwc...liu/with-data?expand=1

@liuliu Do I need to add the following modification myself (never done it before) or just for now, if I am up to date, maybe just generate this file anyway?
I am just back to this today and seems like the repo is updating itself (?).

INFO: Found 1 target...
Target //examples:txt2img up-to-date:
  bazel-bin/examples/txt2img
INFO: Elapsed time: 0.324s, Critical Path: 0.00s
INFO: 1 process: 1 internal.

INFO: Found 1 target...
Target //examples:txt2img up-to-date:
  bazel-bin/examples/txt2img
INFO: Elapsed time: 0.420s, Critical Path: 0.01s
INFO: 1 process: 1 internal.

INFO: Found 1 target...
Target //examples:txt2img up-to-date:
  bazel-bin/examples/txt2img
INFO: Elapsed time: 0.324s, Critical Path: 0.00s
INFO: 1 process: 1 internal.

INFO: Found 1 target...
Target //examples:txt2img up-to-date:
  bazel-bin/examples/txt2img
INFO: Elapsed time: 0.420s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Running command line: bazel-bin/examples/txt2img /Users/blendersushi/Documents/swift-diffusion-main/model 'at a beautiful beach, an astronaut riding a pig wINFO: Build completed successfully, 1 total action
2989718031

Thanks, let me check tomorrow!

I cannot reprod locally on my M1 Mac Mini machine, here is the change I made against bb919dbd8b8914c3f153b84dfdd66f4101d3e2d0:
diff --git a/examples/txt2img/main.swift b/examples/txt2img/main.swift
index b23b20c..7973eca 100644
--- a/examples/txt2img/main.swift
+++ b/examples/txt2img/main.swift
@@ -32,7 +32,7 @@ extension DiffusionModel {
   }
 }

-DynamicGraph.setSeed(40)
+DynamicGraph.setSeed(1282314562)
 DynamicGraph.memoryEfficient = true

 let unconditionalGuidanceScale: Float = 7.5
@@ -126,6 +126,7 @@ graph.withNoGrad {
   DynamicGraph.setProfiler(true)
   // Now do PLMS sampling.
   for i in 0..<model.steps {
+    print("step \(i)")
     let timestep = model.timesteps - model.timesteps / model.steps * (i + 1) + 1
     let t = graph.variable(Tensor<UseFloatingPoint>(from: ts[i]))
     let tNext = Tensor<UseFloatingPoint>(from: ts[min(i + 1, ts.count - 1)])

Here is the command I use to run:
bazel run examples:txt2img --compilation_mode=dbg --run_under=lldb -- /Users/administrator/workspace/swift-diffusion "at a beautiful beach, an astronaut riding a pig with wings trending on artstation, 4k, hyperrealistic, focused, extreme details cinematic, stanley artgerm lau, wlop, rossdraws"

Hi Liu, the Trace Trap still happenings...
Target //examples:txt2img up-to-date:
  bazel-bin/examples/txt2img
INFO: Elapsed time: 276.743s, Critical Path: 233.81s
INFO: 257 processes: 52 internal, 198 darwin-sandbox, 7 worker.
INFO: Build completed successfully, 257 total actions
INFO: Running command line: bazel-bin/examples/txt2img /Users/blendersushi/Downloads/swift-diffusion-main/modeINFO: Build completed successfully, 257 total actions
Total time 60.565213084220886
(base) blendersushi@192-168-1-101 swift-diffusion-main % bazel run examples:txt2img --compilation_mode=opt -- /Users/blendersushi/Downloads/swift-diffusion-main/model/ "a photograph of a tiny astronaut riding a giant"

INFO: Invocation ID: 1e5ebcff-b7d3-4e52-bea3-840c76029705
INFO: Analyzed target //examples:txt2img (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //examples:txt2img up-to-date:
  bazel-bin/examples/txt2img
INFO: Elapsed time: 4.404s, Critical Path: 3.97s
INFO: 4 processes: 1 internal, 2 darwin-sandbox, 1 worker.
INFO: Build completed successfully, 4 total actions
INFO: Running command line: bazel-bin/examples/txt2img /Users/blendersushi/Downloads/swift-diffusion-main/model/ INFO: Build completed successfully, 4 total actions
1887431285
Total time 57.43638300895691
zsh: trace trap  bazel run examples:txt2img --compilation_mode=opt --
(base) blendersushi@192-168-1-101 swift-diffusion-main %

OK. I encountered similar problems on iPad, but not on M1. I am pretty confident it is NaN somewhere but I am not sure where is the source. Need to dig deeper.


404 when listing packages

I'm getting a 404 when performing nuget list -source http://mydomain/nuget
The 404 is actually coming from /Nuget/$metadata.
Anyone have any ideas as to what may be causing this?  FWIW I can successfully publish via the cmd.

I wasn't sure if this was the proper place to ask questions like this or not so I created http://stackoverflow.com/questions/7800832/404-when-listing-packages-via-nugetcommandline

I figured it out.  I had to do http://mydomain/nuget/api/feeds

Glad you were able to figure it out, @mpatersonhsp. I'm sorry I wasn't able to respond sooner.

No worries at all @anglicangeek.  I also ran into another problem once I figured that out though.
https://gist.github.com/1296799
config.SetServiceOperationAccessRule("Search", ServiceOperationRights.AllRead);
was throwing an exception:
System.ArgumentException was unhandled by user code
Message=The given name 'Search' was not found in the service operations.
Parameter name: name
Source=System.Data.Services
ParamName=name
StackTrace:
at System.Data.Services.DataServiceConfiguration.SetServiceOperationAccessRule(String name, ServiceOperationRights rights)
at NuGetGallery.FeedServiceBase`1.InitializeService(DataServiceConfiguration config) in C:\NuGetGallery\Website\DataServices\FeedServiceBase.cs:line 36
InnerException:
I really don't know anything about OData or WCF data services so I just changed it to:
config.SetServiceOperationAccessRule("*", ServiceOperationRights.AllRead);

I've never seen this @mpatersonhsp. I've tried using a clean clone on three different machines. Anything unusual about your setup? Did you change any project settings, perhaps?

The only thing that I can think of is that my database is on a separate server.  Due to this (or something related to it) Build-solution.ps1 fails at the UpdateDatabase build step.  When I ran the website for the first time it created the db automatically.  that is really the only thing that I could see as being unusual....


Fixed layout issue when changing contentSize while keyboard is shown.

Let me know if you have any questions about this request.

This should be fixed in 1.8.4

This is not fixed in 1.8.4; here is an example of what is happening now.

Here is an example of what happens when I add my changes to version 1.8.4

I am running into this same issue.

I've pushed 1.8.5 to fix the issue you mentioned.


https://docs.cloudfoundry.org/services/api.html points to 2.12

It looks like this link still points to 2.12 but it sounds like 2.13 is released.

@bmelville Where did you get that link from?
If I go to https://docs.cloudfoundry.org/services/ and click on Open Service Broker API I get to the v2.13 spec.

Closing due to inactivity. Please reopen again if this is still an issue.


Implement support to make the open orders flow functional

What is the motivation for adding/enhancing this feature?

What are the acceptance criteria?

[ ] ...

Can you complete this feature request by yourself?

[x] YES
[ ] NO

Additional information

Reference Link: https://github.com/hotwax/oms-documentation/blob/fulfillment/Fulfillment/APIs/outstanding-orders.adoc

Approach:
On Open orders page:

fetch orders whenever page mounts and store them in orders state, using OISGIR doc with following filters

quantityNotAvailable: 0
orderTypeId: SALES_ORDER
orderStatusId: ORDER_APPROVED
isPicked: N
-shipmentMethodTypeId: STOREPICKUP
-fulfillmentStatus: Cancelled
shipmentMethodTypeId: *
facilityId: facilityId

Faceting the data for getting shipping methods:

    shipmentMethodTypeIdFacet: {
      "excludeTags":"shipmentMethodTypeIdFilter",
      "field":"shipmentMethodTypeId",
      "mincount":1,
      "limit":-1,
      "sort":"index",
      "type":"terms",
      "facet": {
        "ordersCount": "unique(orderId)"
      }
    }

The number of orders displayed on the open page depends on the picklist size selected, hence no infinite scrolling is required.

Some Points:

We are not fetching the picker information on the basis of facilityId, as discussed. Also the entity used does not have support to query on facilityId
Currently picker information search only works on firstName and externalId, as due to some limitation on api side.


fix(examples): add missing ts-node dependency

Types of changes

[x] Bug fix (a non-breaking change which fixes an issue)
[ ] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Update TS examples to last spec which explictly need ts-node dependency to handle runtime such as nuxt.config.ts

Codecov Report

Merging #5742 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #5742   +/-   ##
=====================================
  Coverage   95.6%   95.6%
=====================================
  Files         82      82
  Lines       2662    2662
  Branches     683     683
=====================================
  Hits        2545    2545
  Misses        98      98
  Partials      19      19

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 0f609df...151ceb3. Read the comment docs.

Codecov Report

Merging #5742 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev   #5742   +/-   ##
=====================================
  Coverage   95.6%   95.6%
=====================================
  Files         82      82
  Lines       2662    2662
  Branches     683     683
=====================================
  Hits        2545    2545
  Misses        98      98
  Partials      19      19

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 0f609df...151ceb3. Read the comment docs.


Will you release the pre-training code on distantly supervised data?

The pre-training code for distantly supervised data is identical to the one in this repo for the train set data.
Just pass the DocRED distant data file, set your training hyper-parameters, and start your training~
Although there is one note: there exists one instance from DocRED distant that contains NO entity, you would want to remove it first before traning, or there will be index error.


Star routes seem to get priority over other routes which have trailing '/'

Original issue in Ember: https://github.com/emberjs/ember.js/issues/13211
I have a failing test for route-recognizer, I'll open a PR in just a moment. There is an ember working demo  on the original issue.
I don't yet fully understand the mechanics of route-recognizer, but it seems that starting with 0.1.6 (and later) when you have a route that has just a trailing '/' as it's path, star routes end up prioritized over it. For example:
router.add([
  { path: "/foo/:dynamic", handler: handler1 },
  { path: "/baz/:dynamic", handler: handler2 },
  { path: "/", handler: handler3 }
]);
router.add([
  { path: "/foo/:dynamic", handler: handler1 },
  { path: "/*wildcard", handler: handlerWildcard }
]);

// Returns the `/*wildcard` route, rather than the above route.
router.recognize("/foo/r3/baz/w10");

Edit: Failing Test: #83

May be related to this commit: 0499446f80c649a2df64ced5cc5458742a57c423
I'm a bit busy in life atm but I added it to my to-do list to look more into this when I've got time. Thanks for raising the issue!

@jmeas Yeap, I can confirm that that is the culprit.

Thanks for verifying @workmanw . Do you know when that ember version is scheduled to be released? I'd like to get it fixed in time for that!

I don't. I could make a guess ... but it'd just be a guess. Maybe @rwjblue could provide a better timeline.

I have a suspicion that it's related to this line:
https://github.com/tildeio/route-recognizer/blob/master/lib/route-recognizer.js#L134
which is the line I was least certain of when updating the algorithm. The tests passed here, so I figured it might be okay :p
My first idea is to just delete that line. In that case, empty segments wouldn't contribute to the specificity at all. I'll need to think more about the implications of that,  though.. I'm on my phone atm so I can't do further testing.

Do you know when that ember version is scheduled to be released?

https://github.com/tildeio/route-recognizer/commit/0499446f80c649a2df64ced5cc5458742a57c423 (included since 0.1.6 of this lib).  Ember updated from 0.1.5 to 0.1.9 in https://github.com/emberjs/ember.js/pull/13104 which will be used in Ember 2.6.0-beta.1 (when we release it) sometime next week.

I submitted https://github.com/emberjs/ember.js/pull/13286 to downgrade route-recognizer to 0.1.5 (which is what is used in Ember 2.4/2.5) until we can get this fixed.

@jmeas I tried commenting out the suspecting line in my test app, https://github.com/tildeio/route-recognizer/blob/master/lib/route-recognizer.js#L134, but it still seems busted :(. I'm guessing you thought there was more to it, but I just wanted to follow back up.

np @workmanw the issue should be fixed in #84


Possible leaks in AsyncLock

Hi, @kekyo , I'm looking through your code,  https://github.com/kekyo/FlashCap/blob/854186a445e494548480ae0d6b607c1bf009eb57/FlashCap.Core/Internal/AsyncLock.cs#L47
here it registered a cancel callback, but it never dispose even when lock is acquired, ct would hold on to all the tcs until it's cancelled. In my case I create one CancellationTokenSource, only Cancel when the app is closed, if any race condition happen it would add a registration to the linked list inside cts
maybe add something like this:
        if (ct != default)
        {
            var registration = ct.Register(() => tcs.TrySetCanceled());
            tcs.Task.ContinueWith(_ => registration.Dispose(), TaskContinuationOptions.ExecuteSynchronously); // dispose registration after task completion
        }

I see it was done in AsyncEx lib
https://github.com/StephenCleary/AsyncEx/blob/master/src/Nito.AsyncEx.Coordination/AsyncWaitQueue.cs#L82

Thanks and fixed.


Incorrect link for secret permissions with DefaultMode

This is a Bug Report

Problem: The link for secret permissions with DefaultMode under persistent storage in Windows storage is incorrect. It is redirecting to the https://kubernetes.io/docs/concepts/configuration/secret/#secret-files-permissions instead of that it should redirect to the https://kubernetes.io/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys.
As given in the PR, the commit (line 195) shows the heading is changed to Set POSIX permissions for Secret Keys from Secret file permissions.
Proposed Solution: secret permissions with DefaultMode should redirect to the https://kubernetes.io/docs/tasks/inject-data-application/distribute-credentials-secure/#set-posix-permissions-for-secret-keys instead of https://kubernetes.io/docs/concepts/configuration/secret/#secret-files-permissions
Page to Update: https://kubernetes.io/docs/concepts/storage/windows-storage/

/language en
/sig docs
/sig storage

I would like to work on it.
/assign

/triage accepted
A fixup/clarification is welcome.

/assign

The issue is fixed here: #43402


Set name for all vagrant images (#39)

This addresses the enhancement in issue #39.
The resolution for issue #31 added config.vm.define NAME to the Vagrantfiles for the OracleLinux 6 and OracleLinux 7 boxes, so that Vagrant identifies the VM using the NAME variable, instead of "default", during vagrant up/suspend/halt/destroy/status operations.  This pull request adds the same to the remaining boxes (except for the Kubernetes box, which is already compliant, per @AmedeeBulle).
To validate, cd to the directory with the Vagrantfile and run vagrant status.  It isn't necessary to actually create the box.  Vagrant should identify the boxes as follows:

DockerEngine:  "ol7-docker-engine"
LAMP:  "ol7-lamp"
OracleDatabase <IP_ADDRESS>:  "oracle11g-xe-vagrant"
OracleDatabase <IP_ADDRESS>:  "oracle-12201-vagrant"
OracleLinux preview:  "uek5-preview"

Yep, agree on this change.
Whenever possible we want to maintain a standard on different boxes.


Bug fix - tint / alpha was broken for non batched graphics objects

Easy but important bug fix :P

Verified: https://pixijs.io/v5-render-tests/?bugfix/graphic-alpha

Somehow i missed that thing, but it was fixed in my fork.. Good catch!


Blockchain Patch

Listening has been refactored to use CRON/timers (in keeping with Scheduler) rather than asyncio.
Blockchain Gateway/Utils are cleaned.
Tests for Gateway/Utils are cleaned. The integration test for the Gateway is on #31

@kiddyboots216 curious to know, why the shift from asyncio to CRON/Timers? Also, what from the list of changes wasn't addressed in this PR?
@neeleshdodda44 and @nzoghb, I'm letting you take over this PR as reviewers since you started reviewing first. I'm just here spectating lol.


Max Memory to Use Validation Message

The upper limit should be the amount of memory available on the user's PC, not max int.

TODO
allow customized error message for intControlSetting


Is it still maintained?

Is the project still alive? I am about to start to implement an app using this

Very much so. Build away!


Source code and tests inside deployed container

Is this intended?

Yes, we add everything to the docker image toward the end of the Dockerfile because it's easier than adding only the necessary bits. It's just easy to miss something or forget to add something if you change it in the future. I would definitely entertain a pull request for being more explicit. I'm just worried someone will add a config needed at runtime and they won't realize they need to add it in the Dockerfile as well so they'll spend hours wondering why the deployed version doesn't work.


STYLE: Improve style in miscellaneous tests

STYLE: Increase consistency in test argument check message
STYLE: Conform to ITK style guidelines in test ending message
STYLE: Conform to ITK comment style for within-code comments (tests)
STYLE: Remove empty comment lines in tests
STYLE: Remove uninformative standard output messages in tests
STYLE: Do not allow lonely std output endl statements in misc tests
STYLE: Improve printed message style across miscellaneous tests

PR Checklist

[X] No API changes were made (or the changes have been approved)
[X] No major design changes were made (or the changes have been approved)

Please rebase to resolve conflicts.

Please rebase to resolve conflicts.

Done.


eliminate (most) log.Fatalf from library code

log.Critf instead and return nil or similar (original error) and let the called crash instead of the library

done a big chunk in #206 but also need to move some nil check to err check


Add Folia's support channels to the guidelines

Noticed while reading the guidelines that Folia's support channels aren't included.

Please update the "Last updated" section


Update to version 3.0.0

I upgraded the dockerfile to the newest version of Piwik.

thanks did you test it?

Yes. I just run the first start and tried to track requested.
It worked so far.


Archived workflow workflow column should be json

Summary
The workflow column in the argo_archived_workflows is of type text and should be of type json.
Motivation
Making it json type would make it much easier to query in postgresql.
I ran this after installation, which works but would be nice if defaulted to json:
alter table argo_archived_workflows ALTER COLUMN workflow TYPE JSON USING workflow::json;

Proposal
How do you think this should be implemented?
Set the type to json.

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Nice idea, would you like to submit a PR please? Should be just a case of adding a line to migrate.go.

Probably should do https://dev.mysql.com/doc/refman/8.0/en/json.html too

This is easy!
References:

https://www.slideshare.net/billkarwin/how-to-use-json-in-mysql-wrong

Great idea. What about doing the same for the argo_workflows_table? Also using jsonb rather than json in Postgres would save space.

@mark9white argo_workflows_table is an internal table and you should not read from this table as you can predict what data it will contain.

@mark9white For whatever reason we have been using plain json on 2.4, but jsonb likely would make more sense.


Debugging VS Code with VS Code is flaky and frustrating

Sorry, that's it. Cannot say more, the experience is a lottery - it sometimes works flawless, it sometimes doesn't work. That it works only randomly is frustrating but what's worst is that I don't feel empowered to provide any kind of qualified feedback. I cannot file good issues and have to resort to ranting. I believe most have confirmed the broken window theory and just moved back to devtools or never made the switch.

For some background: I am trying to use the "VS Code" launch config. I am trying to debug tests with newish test integration. Symptoms are hangs and crashes, sometimes right after starting, sometimes after reloading, sometimes after the Nth debug attempt.

/cc @eamodio @rebornix @joaomoreno who have expressed positive or negative emotions towards debugging in the recent past

related to @alexdima's issue: https://github.com/microsoft/vscode/issues/126826

I asked in general probably more than twice about how to reliably debug VS Code or tests and also asked for @connor4312 and @roblourens personally for help. Maybe with one more bug to fix the experience can be smooth but I want to share my overall feeling with debugging in VS Code for the last couple of years and workarounds I ended up with

Debugging single unit/integration tests is flaky

At the beginning the breakpoint seldomly hit when debugging single file, the test always finished before the debugger is attached (https://github.com/microsoft/vscode/issues/125567). I then started to use await new Promise(c => setTimeout(c, 3000));
Recently there are good fixes in js debug so breakpoints will mostly hit but occasionally the process failed probably because of crash crash on debugging https://github.com/microsoft/vscode/issues/122225

Debug VS Code all processes fail pretty often, I can't call it random as when it fails it's 100%. No clue why is that

might be timeout Alex is seeing https://github.com/microsoft/vscode/issues/126826
might be crash as above https://github.com/microsoft/vscode/issues/122225
sometimes it succeed connecting, but breakpoints never hit (breakpoints should just work for all processes, right?). I saw this happening in a few ppl's machines
disconnect doesn't always work, have to right click kills the process
At the end, whenever I want to troubleshoot end to end, say notebook, what I do now is (almost work every time)

Run OSS, open extension host code, set breakpoints
Debug a notebook extension, in the new window use chrome dev tools in the renderer process

In addition to above, with the extensions starting to use bundler, I sometime find breakpoints doesn't hit in ts file but only in js file, it seems random but when that happens my confidence with source map becomes low and by the end of the day, I stopped using source map in both VS Code and browser dev tools.
With that being said, I'm not happy with all the workarounds so often gave the builtin debugger another try, it's getting better though the randomness is still there. I would love to see a clear detailed guidance for troubleshooting (it would be great if it's a command like Toubleshoot Keyboard Shortcuts) and we can file good bug reports.

Related:

https://github.com/microsoft/vscode/issues/127397
https://github.com/microsoft/vscode/issues/127396
https://github.com/microsoft/vscode/issues/127345

Recently talking with @isidorn and @bpasero, we had the idea to have a PM-drive selfhosting effort They would collect information from team members of what the biggest selfhosting pains are and whether and why they are or are not using VS Code core features. They would then help prioritize work and get it on the plan accordingly. The goal is to maximize selfhosting by putting highlight on areas with most pain.
—-
Specifically on selfhost debugging: I share your sentiments today. While it was great back in January/February, I can no longer say the same. I subscribe to the lottery analogy, which is the worst situation since it makes us silently ditch the feature, which I’ve certainly done recently.

They would collect information from team members of what the biggest selfhosting pains are

I like that and that's also the idea of the papercut label

PM driven sounds good. Here's the state of where the mentioned bugs stand for me:

#122225 remains the big one, at least for me. @deepak1556 please let me know if there's anything I can do to help with that. If it's insurmountable I could try to just brute force and try to disable features or behavior in the debugger until the crashes stop, but this is not sustainable. I would assume this is being caused by setting breakpoints via regexes; while these patterns are long, they're also pretty simple.
#126826 is on my to do. I believe this is something going wrong in VS Code itself where the extension host doesn't get launched in debug mode, but it's racey. I want to look at this this week.

There is a similar error for the main process and renderer. Electron behaves like Chrome, where only the first "main process" will look at the debugging instructions, so if an OSS window or main process is already open not in debug mode, then the debug ports will not be opened and a connection refused will happen.
This can be fixed by using a separate user data dir for VS code when launched in debug mode, like we do for Chrome, but this could make life difficult. In Chrome there is a lockfile which we warn about if it's present when launching, but we don't have a similar file in VS Code right now.

#127397 we'll see about. Ben mentioned devtools does this as well, it may or may not be something we can control/work around.
#125567 there's now code to wait for at least one breakpoint to be verified by js-debug before the test session starts. However, while breakpoints are set in parallel it's possible that this could be insufficient--and there's also a 7-second timeout which may not be sufficient on certain machines. @rebornix are you still seeing this today, and when you are is it the case that either you have multiple breakpoints set, or you see that log in the test output?

In addition to above, with the extensions starting to use bundler, I sometime find breakpoints doesn't hit in ts file but only in js file, it seems random but when that happens my confidence with source map becomes low and by the end of the day, I stopped using source map in both VS Code and browser dev tools

This is, as far as I've seen, always a configuration issue in the compiler/bundler or launch config. If you have examples of cases where this happens, please share them and I can take a look.

I would love to see a clear detailed guidance for troubleshooting (it would be great if it's a command like Toubleshoot Keyboard Shortcuts) and we can file good bug reports.

If you have breakpoints that are set but unverified, use the "Debug: Diagnose Breakpoint Problems" command while the debug session is running.
Otherwise, add "trace: true" to the launch config and share the resulting log.

With regard to debugging tests specifically, I will use the new test run configurations API to allow running in browsers which should avoid most of these issues (by using a newer Chromium/V8 version where bugs aren't present.)

There is a similar error for the main process and renderer. Electron behaves like Chrome, where only the first "main process" will look at the debugging instructions, so if an OSS window or main process is already open not in debug mode, then the debug ports will not be opened and a connection refused will happen.

For this, I did two things:

Launching OSS from the configuration will now use a .profile-oss folder in the workspace by default, and
There is now a lockfile, so if there's an existing Code instance running from that profile directory but not listening on the debug port, you will be presented with the same dialog we show in the browser case:

@connor4312 for 122225 it would help if there are reliable steps to repro the crash, I will add some logs in the runtime this week to better understand the regex causing the crash.

Debugging a unit test with a breakpoint set anywhere in the codebase reproduces the issue ~50% of the time for me. You can use Test: Show Output to see the console output and confirm when a crash happens.

I'm currently seeing from "Test: Show Output"
./scripts/test test/unit/electron/index.js --reporter full-json-stream --grep /^(NotebookTextModel multiple inserts in one edit$)/ --remote-debugging-port=9222 --timeout=0 --waitServer=53242

[16776:0803/203559.179:ERROR:tcp_socket_win.cc(353)] bind() returned an error: Only one usage of each socket address (protocol/network address/port) is normally permitted. (0x2740)
[16776:0803/203559.179:ERROR:devtools_http_handler.cc(298)] Cannot start http server for devtools.

and logs for netstat -ab and apparently it's being used
 [Code - Insiders.exe]
  TCP    <IP_ADDRESS>:9222         kubernetes:57079       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57081       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57083       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57084       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57085       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57086       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57087       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57088       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57093       TIME_WAIT
  TCP    <IP_ADDRESS>:9222         kubernetes:57094       TIME_WAIT
  TCP    <IP_ADDRESS>:9656         <IP_ADDRESS>:0              LISTENING

Can we try to detect which process is actually using that port to help us self-troubleshoot what's going on?

Ok, if you have Remote Container extension installed, it will use 9222 then you can't debug VS Code at all.
Disabling the extension at least gets rid of this error, but now I got an infinite progress of "Running tests", which simply does nothing
./scripts/test test/unit/electron/index.js --reporter full-json-stream --grep /^(NotebookTextModel multiple inserts in one edit$)/ --remote-debugging-port=9222 --timeout=0 --waitServer=64769

DevTools listening on ws://<IP_ADDRESS>:9222/devtools/browser/b7ed2d74-b60b-4144-9f9d-00797742016b
[23856:0803/205139.940:INFO:CONSOLE(29729)] "'window.webkitStorageInfo' is deprecated. Please use 'navigator.webkitTemporaryStorage' or 'navigator.webkitPersistentStorage' instead.", source: file:///C:/Users/rebor/code/vscode/node_modules/mocha/mocha.js (29729)
[23856:0803/205140.310:INFO:CONSOLE(33)] "The vm module of Node.js is deprecated in the renderer process and will be removed.", source: electron/js2c/renderer_init.js (33)

@chrmarti on the Remote Containers issue Peng mentioned ^
@rebornix I don't repro that,

Does that happen even when not in debugging
If not, does it eventually run after ~15 seconds?
If so, please add trace: true to the "Attach to VS Code" config

@connor4312

running is fine
it never finishes, I waited several minutes but didn't see any progress
will do that and share the log

@connor4312 here is the log after waiting for a few minutes
vscode-debugadapter-45eeec47.json.gz

@rebornix thanks, I think I see what's up, seems to be a subtle change in recent Chrome/Electron versions that you're hitting based on timing. Here's a vsix for a nightly build that has a prospective patch: https://memes.peet.io/img/a5d9867c-9921-41e2-843c-163b8eed82a1.vsix

Followup from PM: this seems to be an Electron bug; a fs.readdir call in the glob module we use to discover unit tests never fires its callback. Deepack is working on an Electron build with additional logging to diagnose the issue.

When debugging VS Code by using the "VS Code" launch config, I was frequently running into this crash:

When trying to understand why/when this happens, I noticed that breakpoints (or the number of breakpoints) are the trigger. Without breakpoints I was never crashing; with around 10 breakpoints crashes occurred 6 out of ten.
A workaround is to deactivate all breakpoints temporarily:

and activate them individually after startup and CPU activity has calmed down.

@weinand I suspect you're hitting this: https://github.com/microsoft/vscode/issues/122225 If you send a crash report to Deepak, he will be able to confirm if it's the same issue or different.

@rebornix for the freeze issue, can you try running with --disable-features=CalculateNativeWinOcclusion. It is very likely the cause of getting the event loop suspended.

I've now included the aforementioned flag, as well as the flag for the breakpoint crash issue, in the launch config and selfhost test provider by default.

@rebornix for the freeze issue, can you try running with --disable-features=CalculateNativeWinOcclusion. It is very likely the cause of getting the event loop suspended.

Is there a way to set this flag in a config file instead of editing the shortcut which opens VSC?
Also, why isn't this issue handled? I shouldn't need to do this stuff, I guess ...

@snalesso the freeze issue is tracked in https://github.com/microsoft/vscode/issues/123257


Add Markdown and reStructuredText to supported files.

Just had a .md files where I used preview-generator so I just added it, it works as it's plain text, the "implementation" is trivial and it works.
I also added reStructuredText while I'm at it.
It lacks color, but it already lacks color for json, color could be added in a separate PR.
Checkpoints

[x] If relevant, manual tests have been done to ensure the stability of the whole application and that the involved feature works
[ ] Automated tests covering the feature or the fix, have been written, deemed irrelevant (give the reason), or an issue has been created to implement the test (give the link)
[x] The PR or the original issue contains a short summary of the implemented solution.

Thanks @JulienPalard :+1:

You're welcome! See you at PyConFR?


Migrating next 13

📝 Changed routes:
4 deleted routes:

/404
/
/post/[slug]
/sitemap.xml

Commit 3a8531bf6471212ffb97712cca32a8a2d2b42c82 (https://blog-26np7730w-herbievine.vercel.app).


Split data subscriber lambda

Closes nasa/opera-sds-pcm#51

@maseca You need to separate two lambda functions in separate directory and create requirements.txt and setup.py for each directory.


Autocurry feature

Automatic curry-ing of all undeclared variables inside anonymous functions to the function's external context by implicitly enriching function's list of parameters. This feature is optional and can be opted-out through the new no_closures feature.
This PR is a first part of implementation of true mutable closures.

I suggested a number of stylistic changes.  Otherwise this is ready to merge.

@schungx Done. All issues fixed.

Great.  Thanks.  I'll write up the documentation in the book (or would you like to do that)?

I did some minor style refactors, then put in the correct position for variables not found.

@schungx I suppose the end-user can bypass this issue by introducing a local variable explicitly and without init value like this:
let f = |y| { let z; eval("let z = 0"); x + y + z };

It will put some additional overhead, but not too expensive I think. Anyway, the no_capture feature was exactly for such situations: if the user don't need or don't want such syntax-suger he can turn it off. Any syntax-sugar has drawbacks.
Furthermore we can introduce a new keyword such as local z; that will explicitly say that the variable is supposed to be somehow present in the anon function scope's so it should be bound to the external context, but the Engine will not interpret it anyhow, it will be for the parsing stage only.

Well, I guess let's leave it at this.  I don't think it is too much of a problem, because the only way for a variable access within a function not to throw an error is through an eval that defines that variable.
So throwing an error earlier might not matter much -- unless the user uses eval, he/she gets an error anyway when running the function.
And if the user uses eval, then I guess he/she just needs to be careful!

@Eliah-Lakhin   I find that your addition of externals open up yet other possibilities.  For example, it is now possible to make special function calls such that functions can refer to variables in the execution scope.
I'm planning to add something like this:
fn foo(x) { y += x; }

let y = 41;

foo(1);      // error - 'y' not found

foo!(1);    // bang (similar to Rust's macros) means execute in the current context
               // 'y' is in foo's externals set, so it is copied into the scope for this call
               // and then updated back to the scope after the call

y == 42;

The latest master has this feature.  You can do func!(...) to call the function within the current scope.
I ended up having to clone the entire Scope object in order to please the borrow checker.  Function resolution doesn't happen early enough (since it depends on the types of arguments) for us to cherry-pick the variables to clone.  By the time the argument types are obtained, the Scope is already locked by a mutable reference to the first argument and it is no longer possible to get values out of it.


[BEAM-734] Add support for Spark Streaming Listeners..

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

R: @jbonofre

It would be great to include Jira ID in the commit message. It allows git integration to add a comment in the Jira with the commit ID. It could be fixed before merge with a commit --amend.

Forgot about that,. I'll do it before I merge. Thank!

LGTM


Can we know what other person session was used for sending a given message?

Your use case
If so could stop precise what instance session sent the message.
What would you like to do?
Why would you like to do it?
How would you like to achieve it?
Have you considered any alternatives?
No response
Additional context
No response

... > Original event source > content > device_id
Sender > SECURITY > N sessions, hovering each one shows the associated device ID.
How to avoid checking manually with a linear complexity?


Kinesis Elasticsearch Sink: unify logger configuration

See #1367

Pushing back...

This should be in a Kinesis release, not a Snowplow CLI release

Bringing forwards as pretty straightforward add


Top bar icons are visible over full screen visualizations

Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?

[X] Yes, I can't use Enso because of this issue.

Is this a regression?

[X] Yes, previous version of Enso did not have this issue.

What issue are you facing?

User can not interact with the visualization or close it if they accidentally clicked on one of the buttons.
Expected behaviour
Top bar icons should not be on the top of full screen visualization
How we can reproduce it?
No response
Screenshots or screencasts
No response
Logs
No response
Enso Version
nightly 09.08
Browser or standalone distribution
Standalone distribution (local project)
Browser Version or standalone distribution
standalone
Operating System
MacOS
Operating System Version
No response
Hardware you are using
No response

Introduced by #7488, I missed it on the QA.

unfortunately i'm not sure there's an easy fix. the React dashboard sets z-index: 10 so the top bar draws over the IDE...
... actually i guess it can be fixed by moving the dashboard after the IDE, in index.html?

actually i'm not sure that would help... fullscreen visualizations probably need some kind of z-index still, otherwise it's impossible to show the top bar when fullscreen viz is not open, but hide it when fullscreen viz is open

Actually, I guess it should be fine to put the top bar in the "back" layer (z-index: 1)
https://github.com/enso-org/enso/blob/5d6f902383ac27c9e762ee1b79d99ac309ac5f77/lib/rust/ensogl/core/src/display/scene.rs#L560


Rename 'firetv' to 'androidtv' and add Android TV functionality

Description:
This is a continuation of https://github.com/home-assistant/home-assistant/pull/21872.
This is a BREAKING CHANGE. Users will need to change - platform: firetv to - platform: androidtv in their configuration.
Pull request in home-assistant.io with documentation (if applicable): https://github.com/home-assistant/home-assistant.io/pull/8913
Example entry for configuration.yaml (if applicable):
media_player:
  # Use the Python ADB implementation without authentication
  - platform: androidtv
    name: Android TV 1
    host: <IP_ADDRESS>

  # Use the Python ADB implementation with authentication
  - platform: androidtv
    name: Android TV 2
    host: <IP_ADDRESS>
    adbkey: "/config/android/adbkey"

  # Use an ADB server for sending ADB commands
  - platform: androidtv
    name: Android TV 3
    host: <IP_ADDRESS>
    adb_server_ip: <IP_ADDRESS>

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

This is ready for review! Hopefully it can get merged in before the deadline for the next release!

Small comment. Move services into __init__ and run it under that namespace. Remove this ANDROIDTV_DOMAIN thing on media_player

I'm a bit unclear on what you're saying here. Is the xiaomi_aqara platform an example of what you're talking about?

https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/fastdotcom
With new data structure, we run service under that namespace

@pvizeli the service is already registered under the component. It doesn't really matter what module in the component does the actual registration.

For me the volume_level is wrongly reported. The media player component expects a value between 0  and 1 but i received values up until 4 (max volume on my sound bar is 44).

For me the volume_level is wrongly reported. The media player component expects a value between 0  and 1 but i received values up until 4 (max volume on my sound bar is 44).

You should submit an issue in the androidtv repo.
Here's the line causing the issue: https://github.com/JeffLIrion/python-androidtv/blob/38a01f2ddba7aefb835391b1b3a756a84ed6e044/androidtv/androidtv.py#L330
It would be ideal if the max volume could be determined programmatically. Otherwise, it could be provided as an input (and as a config parameter for the HA component).

@pvizeli is it OK if I leave it as is and register the androidtv.adb_command service in media_player.py?

I don't know why the Hound check is taking forever. It passed earlier and it should pass now. Could someone please restart that test.

We should not change the registration of the ADB command service. It's good as is. Custom services should be registered under the embedding component as it's done here already.

Great, now we will see androidtv,
Working for all device.


Time to train

Hi,
Thank you for sharing your awesome work!
Could you please share how much time it took to train the full network and the hardware you used?
I couldn't find any additional explanation about the training time or hardware.
Thanks!

Hey, bro, have you ever tried training and timing?

Hey, thank you guys for put attention on our work. Meanwhile, I feel sorry for not being reply the issues in time. Here is the answer for those questions above.

The training time: our algorithm is one of the incremental SfM, where the training time is up to the total number of scenes images. For example, in Scan65, DTU the total training time is around 10 hours for 49 images in a single GPU 2080 Ti.
Speeding up the training is on our TODO lists
Setting to reduce the training time: If you can not bear so long training time, you can use the setting that close the SDF-base Triangulation (Traditional Triangulation + Neural Bundle Adjustment). The drop of Precise is bearable, which was reported in the ablation study in our paper.


[BUG] Toasts don't work anymore (version 0.5.1)

Describe the bug
app.router.hdrs += (Style(toast_css), Script(toast_js, type="module"))
    ^^^^^^^^^^^^^^^
AttributeError: 'RouterX' object has no attribute 'hdrs'

Minimal Reproducible Example
Provide a minimal code snippet that reproduces the issue. This is crucial for us to understand and fix the bug quickly.
from fasthtml.common import *

app, rt = fast_app(live=True, debug=True)

setup_toasts(app)

@app.route('/')
def index():
    return html(
        body(
            h1("Hello, World!")
        )
    )

Expected behavior
setup_toasts(app) should work properly.
app.router._app.hdrs += (Style(toast_css), Script(toast_js, type="module")) should probably  do the trick.
Environment Information
Please provide the following version information:

fastlite version: fastlite==0.0.9
fastcore version: fastcore==1.7.4
fasthtml version: python-fasthtml==0.5.1

Confirmation
Please confirm the following:

[x] I have read the FAQ (https://docs.fastht.ml/explains/faq.html)
[x] I have provided a minimal reproducible example
[x] I have included the versions of fastlite, fastcore, and fasthtml
[x] I understand that this is a volunteer open source project with no commercial support.

Additional context
Add any other context about the problem here.
Screenshots
If applicable, add screenshots to help explain your problem.

duplicate to #385


[EG] Beta update serialization

Was incorrectly serializing CloudEventCNCF because of logic flows - updates to simplify

/azp run python - eventgrid - tests

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-eventgrid


capitalize "y/n" for clearer intent

First off, thank you for maintaining and making this project publicly available for others! Fist bump :fist_right:
During the install script process, if you press enter, choice becomes an empty string and will default to "no". The convention in this case is to capitalize the default answer so users know what happens when they auto-accept prompts.
I figured this is such an insignificant change that it doesn't need a note in the CHANGELOG, but please let me know if you'd prefer I add this in.
Thanks! :)

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


Remove Budget Details Page for Applicant

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @rafasdc


ORION-3575 Add transformers to transfer_resource

Add support of Transformation and Transformers to the Terraform provider for transfer.
Refactor the Terraform provider in question slightly to support multilevel structure of Transformers.

The current version contains no DBT tests because DBT transformer cannot be created because of an issue https://st.yandex-team.ru/ORION-3652. It will be fixed soon, but right now it does not work.

I have also changed the name and signature of AsRequest() to convert() in order to match the function names in transfer_endpoint resources in the last commit.


Create a Jenkins image and guidelines for testing

It would be great if the users had an opportunity to quickly test the theme with the latest version of the Jenkins core (or a branch) and with the a set of plugins and configurations. I would like to build it on the top of the https://github.com/oleg-nenashev/demo-jenkins-config-as-code demo

For now we should build it based on https://github.com/jenkinsci/jenkins/pull/4752 .
Work in progress

Is this complete @oleg-nenashev ?

I think so. It kinda works. Will need an update once the Jenkins core PRs are merged and released, but good for testing now


Fix sass deprecation warnings

Update Bootstrap version to 4.6.1
Use sass-migrator to migrate division used in TimeSlider.scss and AppMainContainer.scss

npx sass-migrator division packages/components/src/TimeSlider.scss
npx sass-migrator division packages/code-studio/src/main/AppMainContainer.scss

Visual smoke test to ensure visual consistency
Use scss aware at-rule-no-unknown
Fixes #484

This is going to need a through review, and possibly further style changes. I think we pinned bootstrap for a reason.

Bootstrap's changelogs
https://github.com/twbs/bootstrap/releases?q=v4.4&expanded=true
Looks like there could potentially be a break in 4.5.2 on .row selector (although we could just add that back globally?). Not sure on others

@dsmmcken @mattrunyon I've done a pretty thorough review of the styles and styleguide, and everything looks to be good. With the row CSS, it's only used in the style guide and WidgetPanelTooltip, and seems to be fine in both locations. form-row in FormattingSectionContent also looks to be fine.


Publish v3.2.0 to NPM!

The latest SRI feature is cannot be used easily unless the latest version is published

Thanks for the reminder, this has now been published to npm.


[Bug] offline mode doesn't work in Firefox

Firefox: 72.0.2
This Extension: 0.7.0
While using offline mode, searching standard library, the result list will show, but cannot navigate to after push Enter.

duplicated with #9 #7.


If we post to the inbox of a deleted user, send a 404 or 410 error.

This PR addresses the issue #348.
Few questions I had:

Currently I am only checking if a deletedAt field exists in an account to return 410, should I also check if that date is more than one year old and return 404 accordingly?
The issue said that this logic should not throw, but I implemented the changes using throws. Please let me know if this works.

Thanks @KrinsKumar !
If you wish, you could add a test for inboxes in case a user doesn't exist.

I have added a test, I will merge the PR once you approve the test
Here is a screenshot of the tests passing


Fix lint sdi12

Varun Sreedharan Univesity of California Santa Cruz jLab Undergraduate Researcher
Purpose of the PR
Fixing linting errors for SDI 12 library
Development Environment
Mac OSX, Platform IO Core 6.1.15
Test Procedure
I ran cpplint to check to make sure there were no linting errors
Additional Context
Ignored c cast issues, ignored linting errors for auto generated STM32 code, ignored linting errors for including libraries
Relevant Issues
https://github.com/jlab-sensing/ENTS-node-firmware/issues/111

Merge after #133


How to serve my UI files?

Problem statement
I generated server code using go-swagger with my swagger.yaml file like below.
$ swagger generate server --exclude-main -A myapp -t gen -f ./swagger.yaml

And I want to add new handler to serve my own UI files.
In this case, is middleware only solution to serve UI files? Or can I add new handler to serve files without middleware?
// Handler example which I want to add to swagger server
func pastaWorkspacePage(w http.ResponseWriter, r *http.Request) {
	http.ServeFile(w, r, "./static/workspace.html")
}

Environment
swagger version: 0.13.0
go version: 1.9.2
OS:  MacOS 17.3.0 Darwin

i too am curious. what is the best way to achieve this?

Take a look at cmd/swagger/commands/serve.go

Every swagger generated server comes with the redoc UI baked in at /{basepath}/docs

You can potentially serve your file using multiple handlers for your single multiplexer:
mux := http.NewServeMux()
mux.Handle("/", app.APIHandler(nil))
fileserver := http.FileServer(http.Dir("./static"))
mux.Handle("/static/", http.StripPrefix("/static", fileserver))
...
http.ListenAndServe(":8080", mux)


Cannot use any other icon except bootstrap?

I think I'm doing something wrong, but no matter what I try, only bootstrap works.
For example, with:
module:
  imports:
  - path: github.com/hugomods/icons/vendors/tabler

And on a page somewhere:
{{< ico tabler home >}}

In the terminal I get:
WARN  [icons] tabler's home doesn't exist.

I've tried various other providers and names of things. But bootstrap is the only one that works.
Any ideas?

Tha't because Tabler icons are separated into multiple folders (categories), you can use the following instead.
{{< ico "tabler/filled" "home" >}}

You can find and filter icons here.

Closed as per above comment.


feat: add elevate workflow to react-apollo and vue-apollo example projects

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (25bc4b7) 86.20% compared to head (bf986ff) 86.20%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2521   +/-   ##
=======================================
  Coverage   86.20%   86.20%
=======================================
  Files          86       86
  Lines        9400     9400
  Branches      481      481
=======================================
  Hits         8103     8103
  Misses       1297     1297

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Myaccount and Console Apps keeps on loading after updating the callback URLs to a different offset

How to reproduce:

Get IS 5.12.0 alpha 15 pack and up the server with 9444 port by setting a offset in deployment.toml (offset = 1)
Down the server
Remove the offset = 1 to in the deployment.toml
Up the server again
Try to access my account or console will get a error message as registered callback url in invalid
Then login to management console and try to update service providers console and myaccounts callback url to port 9443 as its not updated by default ( which should happen automatically when you offset the port but not happening)
Will get a error as cannot update the SP due to a permission issue
So down server and add below config to deployment.toml make the 2 apps editable

[system_applications] read_only_apps = []
9. Then log back to management console and update the callback urls for myaccount and console to port 9443
10. Try to access myaccount or console from browser
Actual Behavior
Can access management console but after these steps myaccount and console keeps on loading and doesnt get loaded
https://user-images.githubusercontent.com/31848014/157638003-ff1a7894-4cbf-4092-a917-bf6b55ff4ea8.mp4

Env
IS 5.12.0 alpha 15

To load the myaccount and console properly, we also need to change the Identity Provider Entity ID in Identity Provider Entity ID on Main -> Identity Providers -> Resident -> Inbound Authentication Configuration -> OAuth2/OpenID Connect Configuration to port 9443.
Identity Provider Entity ID: https://localhost:9443/oauth2/token
That configuration is mentioned in the blog [1] as well.
[1] https://medium.com/identity-beyond-borders/fix-invalid-id-token-issue-in-wso2-identity-server-5-11-0-6bd9f7dc5db6

@Maliesha Don't these configurations needs to get updated automatically in the relevant places when you do a port offset?
If its not happening at the moment or we dont have a plan to fix it better to include all the places that a user needs to update in the wso2 docs as a blog is not a official document that a user might refer.

@ShanikaWickramasinghe It is not good due to the reason mentioned in the StackOverflow comment [1].
[1] https://stackoverflow.com/questions/65353663/myaccount-and-console-apps-in-wso2is-5-11-0-are-not-working-when-the-server-star/65354774#65354774


Update gcompress_zip.go

Fix index out of range error while the zipfile has dir __MAXOSX

Codecov Report
Patch and project coverage have no change.

Comparison is base (2ece368) 78.88% compared to head (aaa28c1) 78.89%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2694   +/-   ##
=======================================
  Coverage   78.88%   78.89%
=======================================
  Files         632      632
  Lines       51872    51872
=======================================
+ Hits        40918    40922    +4
+ Misses       8928     8925    -3
+ Partials     2026     2025    -1

Flag
Coverage Δ

go-1.15-386
78.89% <0.00%> (-0.02%)
:arrow_down:

go-1.15-amd64
78.91% <0.00%> (+0.03%)
:arrow_up:

go-1.16-386
78.88% <0.00%> (?)

go-1.16-amd64
78.90% <0.00%> (?)

go-1.17-386
78.88% <0.00%> (-0.03%)
:arrow_down:

go-1.17-amd64
78.92% <0.00%> (ø)

go-1.18-386
78.83% <0.00%> (-0.02%)
:arrow_down:

go-1.18-amd64
78.84% <0.00%> (+0.03%)
:arrow_up:

go-1.19-386
78.88% <0.00%> (-0.02%)
:arrow_down:

go-1.19-amd64
78.89% <0.00%> (-0.03%)
:arrow_down:

go-1.20-386
78.91% <0.00%> (?)

go-1.20-amd64
78.88% <0.00%> (+0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

encoding/gcompress/gcompress_zip.go
53.19% <0.00%> (ø)

... and 3 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Incorrect number of red/blue/neutral cards

Today, we've played multiple games where blue has had 5-6 cards when red has had 2 or more over them. Maybe the bug is around here somewhere? https://github.com/eraether/WatchWordBot/blob/master/src/main/java/com/raether/watchwordbot/BuildableWatchWordGrid.java#L38-L43

Yep, the issue is that the
List unassignedTileIndicies = getUnassignedTileIndicies();
is outside the while loop, so it is likely to reassign cards to the same index.  Putting it inside the while loop should fix the issue.


chore(main): release 0.36.1

:robot: I have created a release beep boop
0.36.1 (2023-09-13)
Features

Connections: hide gcs connection service_account_key value (#428) (373c73e)

Bug Fixes

Align vertically the label in description list (#427) (8b4d954)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-frontend/releases/tag/0.36.1 :sunflower:


Anko DSL Preview Plugin is not compatible with IDEA 2016.1

Anko DSL Preview Plugin 0.8.2 is incompatible with the latest version of IntelliJ IDEA (2016.1).

+1

I have the same problem in version 2017.1.3
The IDE wont run while the plugin is enable.


Update to Cadence v1.0.0-preview.35

Description
Automatically update to:

onflow/cadence v1.0.0-preview.35
onflow/flow-go-sdk v1.0.0-preview.37
onflow/flow-go 604590f19db9
onflow/flow-emulator v1.0.0-preview.33
onflow/cadence-tools/test v1.0.0-preview.33
onflow/cadence-tools/lint v1.0.0-preview.33
onflow/cadence-tools/languageserver v1.0.0-preview.33
onflow/flixkit-go v1.2.1-cadence-v1-preview.19
onflow/flowkit/v2 v2.0.0-stable-cadence-alpha.25
onflow/flow-evm-gateway v0.21.0

Codecov Report
Attention: Patch coverage is 93.75000% with 1 line in your changes missing coverage. Please review.

Project coverage is 33.97%. Comparing base (db96781) to head (e778984).

Files
Patch %
Lines

internal/events/events.go
93.75%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1664      +/-   ##
==========================================
+ Coverage   33.90%   33.97%   +0.07%
==========================================
  Files         100      100
  Lines        6241     6248       +7
==========================================
+ Hits         2116     2123       +7
  Misses       3841     3841
  Partials      284      284

Flag
Coverage Δ

unittests
33.97% <93.75%> (+0.07%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


【Feature Suggestion】Provide RESTful API

Hi ,
I think that it's awesome if kube-aws provide a RESTful API.
Something like
kube-aws service up
to start a service, so I can send request to CRUD a cluster or other operations.

Hi @zhangtiny123, thanks for your interest on kube-aws!
Sounds cool but would you mind sharing us your use-case for that?

@mumoshu  Sorry for the late reply..
I'm building a system which:

Manage multiple k8s clusters for different teams and different regions.
Use the specified credentials to call specified k8s API.

So I want a series of APIs to manage the CRUD operations of clusters, and get the specified k8s API credentials..
What do you think about building this service into kube-aws as a sub-module?

@zhangtiny123 Thanks for the reply!
I like the idea of creating a multi-tenant web app to manage kube-aws clusters but I'd say that what you would really like to have is not a set of RESTful APIs.
IMHO, just adding RESTful APIs to kube-aws won't add actual values because it seems to imply a web application backed by kube-aws, which stores various configuration files to a local filesystem.
It won't scale very well and it a scalability of that level is acceptable, you can author your web app to invoke kube-aws commands as of today.
What I believe you'd need is an ability, which can also be implemented outside of kube-aws, to store various configurations per cluster per kube-aws version.
A list of configurations would include

cluster.yaml
credentials
cloud-config
stack-template
kubeconfig
etc

If we had such ability, adding RESTful APIs would make sense only when your web app is written in a programming language other than golang, or you'd like not to invoke kube-aws commands but integrate with it via an interface other than exec, and you've chosen RESTful API for that.
I'd rather suggest you to draw an overview of the system you're trying to develop, and which part(s) of it can actually be served with kube-aws!
Did my explanation make sense to you? Please feel free to add more replies if necessary.

@mumoshu Yes, it does make sense. Thanks a lot.


Creating Analysis/Insight Questions

The differences between the reported and the actual inflation on a national level.
The breakdown of the food and energy components of the actual inflation. Energy will be further broken down into gasoline.
The differences in inflation between the four different US regions.
Time range: 08/2012 - 08/2022


use soft anti-affinity rules

#3788

There seem to be a glitch in the testing pipeline....

@andrey-dubnik Thanks for this PR! Would you please fix DCO issue?

@andrey-dubnik Thanks for this PR! Would you please fix DCO issue? You can refer to here about how to fix it.

@Taction I can see the commit DCO complains about is signed... do you see any possible cause why DCO complains about it?

See here: https://docs.dapr.io/contributing/contributing-overview/#i-didnt-sign-my-commit-now-what

@andrey-dubnik You do have pushed a signed commit with hash cda2ae0, but your first commit with hash 2e30320 is still there with unsigned status. The expected behaviour should be to replace the first commit rather than append a new commit.
Besides, if it is too confusing for you to solve this, feel free to open another pr and copy your changes to that.

By the looks of it the PR does not actually have all the necessary changes, I will create a new one


rake: Failed to execute /usr/bin/rake

I guess my Linux system doesn't come with much:
$ brew install -v gist
==> Downloading https://github.com/defunkt/gist/archive/v4.5.0.tar.gz
Already downloaded: /home/mgi.polymtl.ca/doorba/.cache/Homebrew/gist-4.5.0.tar.gz
==> Verifying gist-4.5.0.tar.gz checksum
tar xzf /home/mgi.polymtl.ca/doorba/.cache/Homebrew/gist-4.5.0.tar.gz
==> /usr/bin/rake install prefix=/home/mgi.polymtl.ca/doorba/.linuxbrew/Cellar/gist/4.5.0
Failed to execute: /usr/bin/rake

Linux is quite unreliable when it comes to what you can assume is installed on the system, unfortunately. brew install ruby did the job. Perhaps gem install gist would also have done it?!

Currently Homebrew assumes that rake is installed in the same directory as ruby.
https://github.com/Linuxbrew/brew/blob/master/Library/Homebrew/extend/fileutils.rb#L105
That requirement could be relaxed for Linuxbrew to check first in RUBY_BIN and if it's not found there to fall back to PATH. A PR would be welcome. Even better if it's merged upstream to Homebrew/brew.

Thanks for the bug reports, Dominique.

No problem, sorry for the deluge of small issues.

Not at all. It's helpful to document these installation issues.


waffle.io Badge

Merge this to receive a badge indicating the number of issues in the ready column on your waffle.io board at https://waffle.io/Leproslack/saop
This was requested by a real person (user zelcam) on waffle.io, we're not trying to spam you.

lolwut


Lighting API

Currently both the environment map and scene lighting are hardcoded:
https://github.com/nerfstudio-project/viser/blob/ba17c7c40c955a85c845b685a767fbdd9bac6ba2/src/viser/client/src/App.tsx#L452-L458
This is usually fine, but we want to expose a lighting API. This will be particularly useful when we want to use viser for rendering.
Lighting API
Ideally we can support some or all of:

AmbientLight
DirectionalLight
HemisphereLight
LightProbe
PointLight
RectAreaLight
SpotLight

with a Python API that looks like:

scene.add_light_ambient(...)
scene.add_light_directional(...)
scene.add_light_hemisphere(...)
etc

Shadows
We might also consider supporting shadows. There's a hardcoded example in this commit: https://github.com/nerfstudio-project/viser/commit/fd2c7684f4102566e02aefb2fed5479d24896557. This could potentially be a future PR though.
Environment maps
It would also be nice to support overriding the environment map, maybe:

scene.set_environment_map(hdri: bytes | None)

where None will remove the existing (default) environment map.
Default lights
There's a question of what to do about the default lights, which probably we want to leave in. Some options:

Always leave them enabled.
Expose them as "default" scene nodes the same way we currently handle /WorldAxes via scene.world_axes. This makes them removable.
Add a separate API for toggling the default lights. Perhaps scene.enable_default_lights(enabled: bool)?
Remove them automatically when any lights are manually added.

I'm currently biased for option 3 for a balance of being explicit + versatility. But could be convinced otherwise, there might also be other options I haven't thought of.

ok

Resolved by #277


Getting ActionController::InvalidAuthenticityToken exception when signing in

Hi,
I'm using Rails <IP_ADDRESS> and Devise 4.2.0 and am getting a ActionController::InvalidAuthenticityToken exception only when signing in. If I remove the gem, sign in, add the gem and restart the server I don't get any exception when requesting pages.  The handle_unverified_request method is being called right before the exception is raised.
Please help.

Do you have a minimal sample project that demonstrates this?

I just pushed a brand new project https://github.com/bennyzr/rails-devise-pundit using the template https://github.com/RailsApps/rails-devise-pundit. I am seeing the same error when trying to login.

It seems like a new session object is being created when logging-in which doesn't match-up with the client's CSRF token.

@bennyzr I've added one commit at https://github.com/lowjoel/rails-devise-pundit to make the application work (I was getting pundit errors, and missing the sign in/out nav links)... and I don't get any problems signing in or out.

I cloned your version and tested it. When clicking on the "sign in" link and entering<EMAIL_ADDRESS>with the password "changeme" you will not get authenticated and you will see "Can't verify CSRF token authenticity." in the log. Try clicking on the Users link and you will get a 401. If you add the with: exception option from the protect_from_forgery directive in the ApplicationController file you will see the exception I am referring to.

@bennyzr: this was added into the Devise readme: https://github.com/plataformatec/devise/pull/4033/files
use protect_from_forgery with: :exception, prepend: true


Bug: built-in connectors not visible in UI

Bug description
This might be a question rather... when starting conduit, the UI is not showing the built-in connectors. Is this expected behavior?

Steps to reproduce

run conduit
new pipeline
new source
no built-in connectors available

Version
0.11.1 darwin/arm64

Hey @nadilas! Welcome to Conduit!:)
You're right in the sense that it's a bug. However, we've deprecated the UI and we'll completely remove it pretty soon. I recommend that you use the pipeline configuration files instead, since that's the recommended (and easiest) way to create pipelines.
The team will (probably today) discuss this and we'll decide whether or not to fix this bug (depending on when exactly we'll remove the UI).
Let us know if you need something more!

Thanks @hariso, I agree with @nickchomey that you should not spend the effort on this as well then. We’ll go recommended route. 👍

Thank you all for chiming in and your understanding. We need to make sunsetting the UI while producing a great DevEx via a CLI a priority.  🙏
This is a design document I put together some time ago which I'm planning to revisit once we tackle the Conduit CLI. If you have the time, it'd be much appreciated that you can look at it.
Thanks again.