Have an option to remove index.js from public directory

I want to use Klap as an app bundler, not for a library.
I'm not sure how to properly to do this but I'd like to setup Klap just to write a web app like with Parcel.
So I don't want index.js or any other JS files to be in public, now I get this:
Error: Could not resolve entry module (public/index.js).

Any way to avoid using this?

I am unsure what the end goal for your use case is, but in my opinion an app scope is much larger of an use case.
We would need to determine ways to handle CSS, cache busting and whole lot of other concerns.
My intent for klap is to create a tool optimized for NPM library use case. However, we might be able to accept small changes if they help solve app bundler use case.

@osdevisnot the case is using Klap as a web app bundler, e.g. having a similar experience like in Parcel.
In Parcel you just set an html file, then (optionally) edit package.json menus and it works, without limitations,
I understand that Klap is more like Microbundle 2, but I'd like to use it as a bundler because it is the only one bundler with ESM support that can be used for web development (web dev with Rollup sucks let's be honest, Parcel doesn't have ESM output, Pax is written in Rust and is hard to setup)

I may be reading this between the lines, but I believe you are looking for klap.example option.

I may be reading this between the lines, but I believe you are looking for klap.example option.

I didn't mean that, I meant Klap to be more flexible, not only buildings libs but also apps.
Like:
// src/index.js

import { h, render } from 'preact'

/** @jsx h */

render(
Hello World
, document.getElementById('app'))

// package.json

{
  "source": "src/index.js",
   "module": "dist/index.esm.js"
}

and then in index.html


feat: bump custom emoji limit to 250 and stickers limit to 50

Closes #266

this should prolly be an env var

this should prolly be an env var

That's true.

lgtm other then a nit of the imports being on the same line

I personally like them on the same line :p

and that's why its a nit


How to set the contrast of color image of kinect for azure?

When I use kinect for azure to run orbslam2, I found I get less feature points than other rgbd camera under the same resolution condition. I think this maybe the contrast of color image is lower than other image, which is given by other rgbd camera. Also I lookup the documents of API of azure kinect. I cann't find the api for changing the contrast of color image. Could somesome know how to change the contrast of color image? or Maybe give some suggestions to let me know how to tune some parameters to get more fearture points of color image ?

Thank you very much
在 2019-08-27 04:26:56，wes-b<EMAIL_ADDRESS>写道：
Check out k4a_device_set_color_control at https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___functions_gae81269489170b26b7f0bbe1a7f9d31d6.html#gae81269489170b26b7f0bbe1a7f9d31d6. We don't have a sample directly for this purpose, but you should be able to find a couple of examples in the code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Setting labels.color to the same value changes what is rendered

Setting the color on a labels layer to the current value of Labels.color changes the rendering completely, the layer becomes invisible on screen. This is happening because Layer.color_mode is being changed in the Layer.color setter
I would expect that getting the value of a property then setting the same value should leave the rendering unchanged
setup:
blobs = data.binary_blobs(length=128, volume_fraction=0.1, n_dim=3)
viewer = napari.Viewer(ndisplay=3)
labels = ndi.label(blobs)[0]
labels_layer = viewer.add_labels(labels, name='blob ID')
initial_state = labels_layer._get_state()

example:
print(labels_layer.color, labels_layer.color_mode)
{0: array([0., 0., 0., 0.], dtype=float32), None: array([0., 0., 0., 1.], dtype=float32)} auto
labels_layer.color = labels_layer.color
print(labels_layer.color, labels_layer.color_mode)
{0: array([0., 0., 0., 0.], dtype=float32), None: array([0., 0., 0., 1.], dtype=float32)} direct

before setting labels_layer.color:

after setting labels_layer.color:

That's no good @alisterburt! Can you see an easy way to fix? Would be nice to have to update color_mode at all there. Looks like it was done in #1339 and improved in #1362. If so a PR would be welcome :-)

Closed by #3275


GK Hack week branch merge

Merging branch from the GK hack week which adds new equation objects. Process of merging gkylzero into G2 has also begun, with small changes to things like the grid indices (starting at 1 instead of 0 now)

This branch has lots of valuable work that needs to be merged into the main-line. We will rebranch to fix GK issues.
The Linux build seems to be failing, for reasons I do not understand. I am accepting the PR anyway as we can then fix once the merge is complete. It is possible there is something funcky about the way github actions are setup on the Linux container. We will find out.


Should select default meter check if one has already been selected?

I recently got updated to your latest revision which has some good improvements. I ran into some trouble with the select_default_meter() method though. I have a logging script that periodically gets the 1 minute gateway usage data, as well as streaming the realtime data with connect_and_subscribe_forever(). The function to read the gateway data is a coroutine and i create a task to run it periodically. Then i call select_default_meter() and connect_and_subscribe_forever() to start the streaming.
I also call select_default_meter() in the coroutine to get the gateway data, since it can happen before the streaming starts sometimes. The issue i ran into was that eventually it failed to find a meter for some reason ( i didn't get much logging info about why, nor do i think its a real problem, requests seem to fail occasionally.) which cleared the selected meter, and then broke the realtime streaming the next time it needed to request another fastpoll.
My workaround is to have the coroutine check if there is a selected meter already and skip the select_default_meter(), but to do that i have to access a protected member.
if duke_energy._gateway_auth_info.meter_id is None:
    await duke_energy.select_default_meter()

What do you think about having the select_default_meter() method check if a meter has already been selected and not try to reselect if it has? That way i can safely call it repeatedly. Alternately maybe we could add a better way to check if a meter has been selected? Thoughts?

If you wanted to go with that approach, I'd just suggest making a different method that wraps select_default_meter(). My intention with select_default_meter() is that it would ignore any previously selected meter and pull the new one. If it checks the existing one, even if it is a valid meter, there's no way to say it is the "default" one. A wrapper method could be more explicit with re-use existing or fall back to selecting default.
def reselect_meter_or_select_default():
    if current meter is valid:
        # use existing meter
    else:
        select_default_meter()

But I'll point out that this is really being necessitated by unnecessarily selecting the meter multiple times. That's really intended to be a one-time operation. The operation itself is pretty slow (usually 5-10 seconds for me) and probably flakey as you mention. I wouldn't want to do it every minute.
So I have pretty much an identical pattern to you in my Home Assistant integration. Gateway usage data is requested every 60 seconds via a co-routine and the real-time streaming runs on a separate co-routine. The simple way that I handle this is to select the default meter before initiating those co-routines. Maybe you could just switch up the pattern there?
https://github.com/mjmeli/ha-duke-energy-gateway/blob/main/custom_components/duke_energy_gateway/__init__.py#L54


/run mounted in container as exec

Attempts to fix travis-ci/travis-ci/issues/7062 to enable build systems that generate executable contents and data on shm to be able to execute it.
The go-dockerclient supports this https://github.com/fsouza/go-dockerclient/commit/be34fed0d2cfd8c02f8ecb2bebbc7ce1cd3b9c03

@grooverdan Ahoy!  Thanks for the PR 😺  I like this, but I want to make sure it's configurable at runtime.  Do you want to take a crack at doing that, or are you OK with me basing work on top of your change?

Please just base your work on top of this.
I really don't have a test environment and was flying blind a bit. Also also don't know how configurable you want it or where all the code bits that make it configurable are. Based on that, letting you take over is the sanest approach.


The header delays returning to the right place after scrolling over the top.

https://github.com/auroral-ui/hexo-theme-aurora/assets/35170687/f5470ffb-7dd4-40cc-bc71-53555b0d159e

This issue is still exist.

In latest 2.4 3:
https://github.com/auroral-ui/hexo-theme-aurora/assets/35170687/70ef7040-ced1-44c1-80f2-fb0da3de9fb1


FIRDesigner multiplies is deprecated

Looked like an ominous warning
filter/FIRDesigner.cpp:462:25: warning: 'bind1st<std::__1::multiplies<std::__1::complex<double>>, double>' is deprecated [-Wdeprecated-declarations]
                   std::bind1st(std::multiplies<std::complex<double>>(),_gain));

Lambdas are nicer anyway.


Problems in chat codeblocks show as workspace problems

Type: Bug
I'm still experiencing the issue that was supposed to have been fixed by this ticket. I just upgraded and am on 1.87.2.
https://github.com/microsoft/vscode/issues/206644
Every time I use Copilot on a section of code, a temp file is generated and then a list of "problems" show up in the problem pane for that temp file.  When I restart VS Code, the file is gone and so are the "problems".
VS Code version: Code 1.87.2 (Universal) (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:21:31.043Z)
OS version: Darwin arm64 23.3.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Max (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
2, 2, 3

Memory (System)
32.00GB (1.90GB free)

Process Argv
--crash-reporter-id f096d041-49ea-4575-8003-9acc21f3ab4b

Screen Reader
no

VM
0%

Extensions (19)

Extension
Author (truncated)
Version

sort-imports
ama
6.3.1

turbo-console-log
Cha
2.10.4

vscode-eslint
dba
2.4.4

vscode-wasm
dts
1.4.1

gitlens
eam
14.9.0

prettier-vscode
esb
10.1.0

auto-rename-tag
for
0.1.10

copilot
Git
1.172.0

copilot-chat
Git
0.13.1

vscode-graphql
Gra
0.9.3

vscode-graphql-execution
Gra
0.2.6

vscode-graphql-syntax
Gra
1.3.4

vscode-peacock
joh
4.2.2

solidity
Jua
0.0.173

prettify-json
moh
0.0.3

color-highlight
nau
2.5.0

vscode-vyper
tin
0.0.15

alphabetical-sorter
ue
2.0.1

vscodeintellicode
Vis
1.2.30

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vscaat:30438848
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfcontrol:30979541
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
dsvsc020:30976470

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

See https://github.com/microsoft/vscode/issues/206644#issuecomment-1995812703. Only fixed in 1.88


enum  cannot be embedded in struct like this：[14397]

struct  Foo{
enum Bar{
a,
b
};
Bar bar;
};
Change to below, generator works:
struct  Foo{
enum Bar{
a,
b
}bar;
};
Can you fix this bug ? @Eprosima   ,because I have hundreds of IDL files to deal with

Hi @xiaokezhou,
The standard does not allow the definition of enumerations inside the struct definition. Therefore, what you are reporting it is not really an issue.
However, you have found indirectly a bug. As you report, in the second case, although the generated files does not include the variable bar in the struct, there is no failing message and the type support files are generated though not as the user expects.
I am going to open a new issue with this bug and close this issue as it is the expected behavior according to the specification.


Changing colour of string in bot framework

Is there any option to change the font color of string that is sent from bot to user instead of default black in  .NET?
I am trying to change the color of text appearing in cards in bots

Hi @dipumon, which channel are you using?

I am using skype channel.

Skype doesn't support changing font color. https://docs.botframework.com/en-us/csharp/builder/sdkreference/activities.html has a list of supported tags.

can we change the color of the text we send in Webchat Directline? Also can we send at least the CSS class name so that with help of that class name, we can change the color at our webchat end?

Hi @anandvardhandas
If you are not using the iframed version of webchat, you can override the css using normal means of css overriding.
Please ask your question on StackOverflow, and someone will assist you promptly.  (The Bot Framework team prefers that the GitHub repository be used for bug reports and feature requests.)


Run autoconf to generate configure script.

Not needed in rpm spec, will run autoconf in jenkins source tarball build job.


Fix #92219 - skip word separator in settings search

This PR fixes #92219
Root cause: The dash('-') and dot('.') are both belong with word separator. If search dash('-') in settings, the dot('.') will also be shown.
How to test: Search dash('-') in settings.

I don't understand this - can you explain what you are searching for with - off? If we require word separators to match then a query like auto.save won't match files.autoSave, if I understand correctly. And I think foo-bar should match foo bar, it seems like an appropriate level of fuzziness.

Oh. I misunderstood this issue. I'll close this PR.


Request for Baseline Training Code

I hope this message finds you well. I have been working on a project that builds upon your methodology and have successfully utilized the open-sourced code you provided. However, I encountered some challenges when attempting to replicate the baseline results reported in your paper. Specifically, the baseline performance on LA dataset I obtained (i.e., only use 10% labeled data for training) is significantly lower than the results you have described.
To ensure that my implementation aligns accurately with your experiments, I was wondering if you could share the original baseline training code. Having access to this would greatly aid in reproducing the baseline results and furthering my research based on your work.
Thank you very much for your time and assistance.

Thank you for your interest in our work! The code you need to replicate the baseline results is already available in this repository.
When conducting our experiments, we observed that under the DTC setting with 10% labeled data (only 8 examples), the performance was not satisfactory. We suspected this might be due to bias introduced by the dataset splits, as such a small sample size can lead to significant variability in training and evaluation.
To address this, we restructured the dataset across different splits to reduce the potential bias caused by fixed splits. The baseline results reported in our paper are based on this cross-split setting.
For the DTC setting with 20% labeled data, our method performs well and achieves good results.
To further assist you, I have uploaded the pre-trained weights to the following link: https://drive.google.com/drive/folders/15nipv6zz_87TzvM_x-JcRRIasuy9nex0?usp=drive_link.
If you have any additional questions or need further clarification, please feel free to reach out.

I'll go through and organize the materials from the previous project related to splits and weights. This includes checking if the data and weights are usable and compatible. It might take some time to review and test everything.


CRUD Field: checkbox

Added in https://github.com/tabacitu/crud/commit/22f1be45d101c6243e04dabe811777489d85b16c


Update Orgs Using Aeryn

Added styled-components

Danger doesn't seem to have a token, anyone know what's up with that? cc @orta

Thanks a lot for contributing to Moya! I've invited you to join the Moya GitHub organization – no pressure to accept! If you'd like more information on what that means, check out our contributor guidelines and feel free to reach out with any questions.

Hehe I know that message from somewhere @ashfurrow 😜

Meta 😬
Sent with GitHawk

Thank you! 😃


Polish spring-cloud-launcher README

Use relative links, add mention of dataflow, fix example that mentions dataflow but had other applications in the code.

Thanks!


"Show More" menu doesn't appear with tabs

Hey there, this plugin is extremely nice and well done :)
The only problem I'm having is that when the number of tabs exceeds the width of the panel container, it does not show the "..." for showing more, it just keeps breaking down into multiple rows. I even tried putting your raw example into my project and it still won't show the "..." Any clue what might be the cause? Here are the relevant versions of the modules being used:
"react": "15.0.1",
"react-dom": "15.0.1",

Do you run code locally? Or this bug comes from the live demo?

 Or this bug comes from the live demo?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

What browser do you use?
 Or this bug comes from the live demo?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm using Chrome on Mac OSX
On Tue, Jun 7, 2016 at 8:11 PM, maslianok<EMAIL_ADDRESS>wrote:

What browser do you use?
 Or this bug comes from the live demo?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maslianok/react-responsive-tabs/issues/1#issuecomment-224249792,
or mute the thread
https://github.com/notifications/unsubscribe/AFWipg04gWRT_lyCe4kpDjrNPP2kpL3oks5qJVHcgaJpZM4IvfPX
.

Please update to v0.5.3

Ah thankyou so much it works perfectly :D
If I may ask...do you know if there's a way inside the component that, when
in responsive mode, none of the tabs are selected, if the page is being
loaded the first time? Like not have the first tab selected by default when
in mobile view? Would something like that be possible?
Thanks again, your plugin is amazing :)
On Tue, Jun 7, 2016 at 9:18 PM, maslianok<EMAIL_ADDRESS>wrote:

Please update to v0.5.3
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maslianok/react-responsive-tabs/issues/1#issuecomment-224262937,
or mute the thread
https://github.com/notifications/unsubscribe/AFWipjlrFfqkInhCCpE499KUW7oS-OGDks5qJWGOgaJpZM4IvfPX
.


Add intellisense for workbench.action.findInFiles args

Feature or bug.  The workbench.action.findInFiles command can be used in a keybinding like so:
  {
    "key": "ctrl+shift+f",
    "command": "workbench.action.findInFiles",
    "args": {
      "query": "some (regex)",
      "replace": "boy $1 swell",
      "triggerSearch": true,
      "filesToInclude": "",
      "isRegex": true,
    }
  },

All args are at https://github.com/microsoft/vscode/blob/9a987a1cd0d3413ffda4ed41268d9f9ee8b7565f/src/vs/workbench/contrib/search/browser/searchActions.ts#L163-L172
but these are not surfaced through intellisense when creating the keybinding within the args object.

I don't think any command args get intellisense, so that would be a general feature request, is that right @aeschli?

See https://github.com/microsoft/vscode/issues/95582 example therein - insertSnippet does too - there must be more.  sendSequence does not.

@roblourens See https://github.com/microsoft/vscode/blob/master/src/vs/editor/browser/controller/coreCommands.ts#L231


Validate and default https

Caravan must run on https in order to communicate with the wallets.  If you try to access http content you get a "mixed content" error so this updates the defaults and validation accordingly

I think that its a mistake to entirely disallow https urls for local CORS proxies, as I have been able to get them working locally without mixed-mode errors.

It warns but does not restrict, so maybe I should just revert the validation or just withdraw this request.


Added credit to earth.gif

I also tried this. It does not work for me :(.

@tjarkdoering Could you add the Link to the image like you suggested?
I think the best would be to directly link the blog of hers:
https://tabletopwhale.com/


Adjust verbosity of model window commands

if you have the model window open, I think that the "model" is implied
I think it's also useful to add chain to these commands
This also aligns the naming of the model output from 'model take response' (I think we should use the same name everywhere for the model output/response)

The reason I have this more verbose is given the fact that it could conflict with other user commands related to pasting since it is pretty generic.
But I think this is fine, and probably not too likely to conflict. Ok with merging if you want.

That's a good point-I followed the pattern of the homophones window to enable it only when the window is open now.

I'd like to also add context/thread to this.

Looks fine but a bit worried that 6 buttons on one window is a bit much. Let's keep it for now but might want to refactor this later or remove buttons.

It is a lot of buttons so I definitely would support a way to condense it if it's possible-however I'm pretty glad that there is some way to interactively select how you want to handle the model response. It's pretty powerful!

Talon currently can't do horizontal buttons or columns in imgui. So I guess for right now we can just merge this since there isn't a better option. I am not sure if model chain is needed since it is just a helper and doesn't add any behavior really, but we can keep it

Personally I really like model chain-I think it's really handy to have it in the window UI especially since you're pausing for a moment to think about the response you're more likely to know that you want to select it when you input it as well. I'm gonna merge this for now and we can think about it some more-thanks!


get cm256 using git subtree

Explain the changes

Remove the cm256 directory - preparing to fetch it using git subtree
Run git subtree add --squash -P src/native/third_party/cm256 git://github.com/catid/cm256.git master in order to get the cm256 directory
Cleaned the cm256 directory to match the one we had previously
Manually added @yselkowitz changes from https://github.com/catid/gf256/pull/6

Hi @yselkowitz
Can you have a look?

@liranmauda Please notice we added a DCO check - you need to sign off your commits with  git commit --signoff --amend or git rebase --signoff master to mass signoff all commits rebased on top of master.

I saw that 🙂
git rebase HEAD~5 --signoff giving me hard time...

The P&Z specific commit (which is the only net change) is correct, I can't comment as to the git subtree infrastructure side of it.

Closing this PR as it turns out that handling with git subtree is hard when rebasing.
Eventually it creates a commit (the squash commit) that have those values:
git-subtree-dir: src/native/third_party/cm256
git-subtree-split: caa2022c140a6f5ff32b8b2b5ac3b7131da99ca9

and a merge commit.
We should probably use git submodules instead.
It creates a repo inside of our repo.
That repo contained a .gitmodules file in the root directory which have:
submodule "native_modules/cm256"]
	path = native_modules/cm256
	url = https://github.com/noobaa/cm256

and git submodule status will look like this:
caa2022c140a6f5ff32b8b2b5ac3b7131da99ca9 native_modules/cm256

which contains the commit hash.


target branch

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


[SPARK-45948][K8S] Make single-pod spark jobs respect spark.app.id

What changes were proposed in this pull request?
This PR aims to make single-pod Spark jobs respect spark.app.id in K8s environment.
Why are the changes needed?
Since Apache Spark 3.4.0, SPARK-42190 allows users to run single-pod Spark jobs in K8s environment by utilizing LocalSchedulerBackend in the driver pod. However, LocalSchedulerBackend doesn't respect spark.app.id while KubernetesClusterSchedulerBackend does. This PR aims to improve K8s UX by reducing the behavior difference between single-pod Spark jobs and multi-pod Spark jobs in K8s environment.
Does this PR introduce any user-facing change?
Yes, but it's more consistent with the existing general K8s jobs.
How was this patch tested?
Pass the CIs with the newly added test case.
Was this patch authored or co-authored using generative AI tooling?
No.

Could you review this when you have some time, please, @LuciferYang ?

Thank you, @yaooqinn and @LuciferYang !

All tests passed. Merged to master.


testrunner exit registration

This patch gets exit registration and setup working in the test
environment.
Sadly the exit clients still can't reach the outside world, since the
nftables exit forwarding setup does not seem to have been tested.

One fun thing I noticed while doing this is that all encrypted messages between the client and the exit take an exit client identity, which contains all the info needed for registration this results in strange codepaths where you need contact details set to request the list of active exits even though nothing on the other end touches this data.
This breaks my usual condition of 'never send data that's not used' and is also problematic as we go forward trying to re-model the exit organization to match the new paradigm.

I've also removed the separate althea_address field, it was simply more trouble than it was worth by a long shot handling the various possibilities is just not easy.


Add favicon + Update distro test table + update a common issue

This adds a favicon on all html pages

The common issue update is regarding the VRAM issue in response to this:

Tested distros update:

Added EndavourOS
Added Manjaro
Added openSUSE Tumbleweed

The common issue update is regarding the VRAM issue in response to this:

Tested distros update:

Added EndavourOS
Added Manjaro
Added openSUSE Tumbleweed

Nice! Lemme merge this.


"_before" prop is missing "content" attribute

Hi there, I found a bug in _before prop.
The content attribute is missing.
I have to use css api as a workaround.
Core version: 1.5.7

Wordaround:
<Flex
        flexDirection={'column'}
        position={'relative'}
        pb={'spacings.2'}
        _before={{
          display: 'block',
          position: 'absolute',
          left: 0,
          bottom: 0,
          right: 0,
          height: '1px',
          background: 'colors.line',
        }}
        className={css`
          &::before {
              content: '';
          }
        `}
      >
       ....
</Flex>

Thanks for the report! This should be resolved once #393 is merged. Will take a look!


Update sai submodule to upstream

All PRs submitted to OCP/SAI to fix issues related to saithrift-server generation have been merged. This PR changes DASH to using upstream SAI repo as a submodule.
Relevant SAI PRs:
https://github.com/opencomputeproject/SAI/pull/1492
https://github.com/opencomputeproject/SAI/pull/1514
https://github.com/opencomputeproject/SAI/pull/1533
https://github.com/opencomputeproject/SAI/pull/1558

LGTM.  Please merge.  Thanks a lot for taking care of this.


Lock down floating dependencies

Debian just released bullseye as stable so now "stable" points to an
entirely different version.  Instead of using stable/testing/unstable we
should use the actual release names(ex: stretch, buster, bullseye) so
that when Debian releases the build doesn't break.

Fixes: https://github.com/PelionIoT/distro-pelion-edge/issues/205


Perfomance and design fix: reducing number of eaten exceptions.

Hi Jack,
Our team uses SQLNexus.
I propose some refactoring to reduce eaten exceptions quantity and path to DLL fix in sqlnexus.csproj.

Thank you for your contribution @rud0x7b6 and apologies for getting back to you on this after so long.
This PR makes sense. We will test it and merge if all good or come back with some suggestions
@gambit9009


some TLDs has been added since last update...

I will fork it into gxed organization.

And also see the autogenerate branch or master on gxed.


netdriver: Add support for non-TCP protocols

Many daemons use Unix domain sockets to communicate with their clients.
This change amends libhfnetdriver with support for all
SOCK_STREAM-compatible address families while retaining the previous
behaviour of probing TCP on IPv4 and IPv6.
A newly introduced, weak-linked "HonggfuzzNetDriverServerAddress"
function allows users of the library to provide their own destination
socket address, e.g.:
  int HonggfuzzNetDriverServerAddress(struct sockaddr* addr,
    socklen_t* addrlen)
  {
    struct sockaddr_un saddr = {
      .sun_family = AF_UNIX,
    };
    char tempdir[PATH_MAX];

    if (HonggfuzzNetDriverTempdir(tempdir, sizeof(tempdir)) < 0) {
      return -1;
    }

    snprintf(saddr.sun_path, sizeof(saddr.sun_path), "%s/pipe",
      tempdir);

    memcpy(addr, &saddr, sizeof(saddr));
    *addrlen = sizeof(saddr);

    return 0;
  }

With the above function libhfnetdriver will probe the Unix socket named
"pipe" in the temporary directory provided by
"HonggfuzzNetDriverTempdir" until connections are accepted and will then
proceed to fuzz as it would a TCP connection.

Please give me some time to review it. I'm sure the code is quite correct, I just need to think about the whole configuration API. E.g. should we still rely on weak functions, or maybe use envvars to configure all that, or both.
honggfuzz -E HFND_DEST_ADDR=unix://...
etc.

Please give me some time to review it.

Sure, take the time you need.

honggfuzz -E HFND_DEST_ADDR=unix://...

If I may add my CHF 0.05: The weak-linked function working with struct sockaddr_* allows fuzzing via all compatible address families without requiring modifications in the fuzzer and there's no need for a parser. Relying on external environment variables makes it impossible for the fuzzer to specify the path (which may not be known until the program is started, see commit bfed5ea505d0).
If the growing number of weak-linked functions is a concern another option could be to switch to a configuration structure. Pseudo code for a fuzzer:
int HonggfuzzNetDriverConfig(struct honggfuzz_netdriver_config *cfg) {
  static char *tmpdir = "/foo/bar";

  cfg->size = sizeof(*cfg);
  cfg->tmpdir = tmpdir;
  cfg->other_option = 1;

  struct sockaddr_un* addr = (struct sockaddr_un*)cfg->target_address;
  addr->sun_family = AF_UNIX;
  addr->sun_path = "…";
}

Binary compatibility is a bigger concern with this variant, hence setting the size to allow libhfnetdriver to work with older/smaller versions of the structure.

Makes sense, the only comment I have about your code is that there're no length checks  for struct sockaddr* addr. You pass *addrlength, but it's only used as a return value, and not when modifying sockaddr;
Would it be possible to rewrite it, so it maybe does the following.
socklen_t HonggfuzzNetDriverServerAddress(struct sockaddr** addr) {
   static __thread sockaddr_... sa;
  *addr = &sa;
   sa.blabla = blabla;
  return somelength;
}

This way we can avoid the input legtht problem, as it's basically the function owning the struct (which is in TLS, which is static, which can be used out of function scope).

I'm sorry Michael, could you hold on with your PR for now. I'm rewriting the code, so it's easier to add your AF_UNIX plug. After that it should be a single function change

Ok, done in https://github.com/google/honggfuzz/commit/1ea443f8cf676129ddba5327f41a97f565b0c3a9
Would it be possible to implement your AF_UNIX connections on top of that?
If you'd like default checking for TmpfsDir()/pipe, I think you can add this check after checks for TCP4 and TCP6.

Would it be possible to rewrite it, so it maybe does the following.
socklen_t HonggfuzzNetDriverServerAddress(struct sockaddr** addr) {
[…]

This way we can avoid the input legtht problem, as it's basically the function owning the struct (which is in TLS, which is static, which can be used out of function scope).

I didn't want to make the client code the owner of the address storage and by returning the struct length as the return value it becomes impossible to return an error status (e.g. if the fuzzer has code that can fail for some reason).

Ok, done in 1ea443f
Would it be possible to implement your AF_UNIX connections on top of that?

I don't know without studying your changes in-depth. It's neigh impossible to say because the commit message doesn't describe the changes at a high level.
I know you own the code, but I spent considerable time working out an interface that works for fuzzing AF_UNIX and other non-TCP families without breaking compatibility with existing code and actually tested it (e.g. attempting to set TCP_NODELAY on AF_UNIX will fail). netDriver_waitForServerReady seems excessively repetitive. There was no clear need for a "rewrite".

I'm sorry it turned out this way. My fault!
I'll try to improve on the github log messaging, and on discussing the pull request fronts.
To my defense, I felt like the old code structure was tied too much towards TCP, and even support for TCP/IPv6 was somewhat a hack.
I'll take a look at your original PR one more time, and try to implement the functionality you were looking for on my own, to avoid putting the burden of understanding the new code on you, I hope that's ok.

FYI: I believe the needed functionality is now implemented by https://github.com/google/honggfuzz/commit/6814cb6a032ab0963bc37493ec4f7f640389daaf
If you're still interested in this code, please feel free to test it.
FWIW: I think that returning socklen_t might be a better option here. First, it's simpler, and simpler is typically better. I don't think we need error handling there. The HonggfuzzNetDriverServerAddress() should either return 0 (function not interested in setting address), or fail hard with panic() (LOG_F here). There's no recovery from error in this path. We shouldn't be trying to connect to default ports if HonggfuzzNetDriverServerAddress() fails, because it means that the code wanted the netdriver to something very specific, and failed to describe it.

@robertswiecki, thanks for the changes. It'll be a few days before I have time again to work on this.

I've only found one minor issue, patch is in #292.

Thanks for verifying!
QQ: Would you mind me changing the default path from ${tmpdir}/pipe to ${tmpdir}/sock or ${tmpdir}/socket
It's a bit bikeshedding on my part, but technically it is a socket and not a pipe.
Also.. we're currently supporting SOCK_STREAM only, and I've seen that samba sometimes uses SOCK_DGRAM with AF_UNIX (e.g. the samba-tool uses it). Do you think that supporting it would be useful?

QQ: Would you mind me changing the default path from ${tmpdir}/pipe to ${tmpdir}/sock or ${tmpdir}/socket

Not at all. The code I'm working on is going to supply its own socket path anyway.

Also.. we're currently supporting SOCK_STREAM only, and I've seen that samba sometimes uses SOCK_DGRAM with AF_UNIX (e.g. the samba-tool uses it). Do you think that supporting it would be useful?

Yes, that would also allow fuzzing other protocols, e.g. DNS servers via UDP.

@hansmi  Would it be posible to take a look at https://github.com/google/honggfuzz/pull/293 ?
It changes the declaration of HonggfuzzNetDriverServerAddress(), but I think the feature is new enough (and you're probably the only user now) to break the compatibility.
This implements the type/protocol params settings, and gets rid of static __threads vars.

@robertswiecki, I have to come back to this reply:

If the growing number of weak-linked functions is a concern another option could be to switch to a configuration structure. Pseudo code for a fuzzer:
int HonggfuzzNetDriverConfig(struct honggfuzz_netdriver_config *cfg) {
…
}

In my usecase I want to modify the data before sending it to the target server as the requests contain two separate length integers. I'm currently using the following local change with the fuzzing code providing its own LLVMFuzzerTestOneInput calling HonggfuzzNetDriverTestOneInput after doing its magic:
--- a/libhfnetdriver/netdriver.c
+++ b/libhfnetdriver/netdriver.c
@@ -401,7 +401,14 @@ int LLVMFuzzerInitialize(int *argc, char ***argv) {
     return 0;
 }

+int HonggfuzzNetDriverTestOneInput(const uint8_t *buf, size_t len);
+
+__attribute__((weak))
 int LLVMFuzzerTestOneInput(const uint8_t *buf, size_t len) {
+       return HonggfuzzNetDriverTestOneInput(buf, len);
+}
+
+int HonggfuzzNetDriverTestOneInput(const uint8_t *buf, size_t len) {
     int sock = netDriver_sockConnAddr((const struct sockaddr *)&hfnd_globals.dest_addr.addr,
         hfnd_globals.dest_addr.slen, hfnd_globals.dest_addr.type, hfnd_globals.dest_addr.protocol);
     if (sock == -1) {

Would you be willing to consider a change from the current individual weak-linked functions to a larger configuration structure? Do you have another idea to curb the growth?

Sorry for late reply, I missed this.
The config idea sounds intriguing, it can actually also solve the problem of making local changes to the data (custom mutators?), as it can technically contain a function pointer to a mutator function, like the one that is described here: https://github.com/google/fuzzing/blob/master/docs/structure-aware-fuzzing.md
My personal TCP fuzzing cases don't require such heavy configuration, but I'm totally ok with enhancements, if your use-cases call for it.


[Add] : Add Notion Website in Blogs Sub-Category in Resources Section

Site URL
https://www.notion.so/
Description of the above provided site

This Notion Website Bunch of Options List like Blogs, Guides &Tutorials, Webinars and Much More.
Interactivity with Developers At One Place using Community Option in Notion Website

Category
Resources
Sub Category
blogs
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

You're assigned now @NarendraKoya999

Hi @CBID2 . Please Look at once Unassigned Issues raised by Me. If Possible, Assign that Issues as soon as Possible

@rupali-codes . Why you can removed level Label?

@rupali-codes  . Please close this Issue . This Issue related PR Already Merged

@CBID2 . Please Close this PR. It's Already Merged and Added Labels Also


feat: Add TypeAliases

Expose types from dependencies by declaring public typealias.
This means that the user does not need to import the dependency to use that type

Codecov Report

Merging #49 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #49   +/-   ##
=======================================
  Coverage   30.05%   30.05%
=======================================
  Files           6        6
  Lines        1364     1364
=======================================
  Hits          410      410
  Misses        954      954

Flag
Coverage Δ

#SwiftKueryORM
30.05% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

Sources/SwiftKueryORM/Model.swift
38.5% <ø> (ø)
:arrow_up:

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 7f3a95d...afb29c1. Read the comment docs.

Note this is SemVer minor so requires a 0.3.0 release.


High RAM usage during colcon build

Description
I'm working in WSL with 3.74GiB of RAM and 1GiB of swap (Neither I cannot add more RAM to the machine nor increase the swap partition).
Whenever I try to compile the source the compiler gets killed, e.g.:
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
gmake[2]: *** [src/CMakeFiles/moveit_task_constructor_core.dir/build.make:174: src/CMakeFiles/moveit_task_constructor_core.dir/storage.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:256: src/CMakeFiles/moveit_task_constructor_core.dir/all] Error 2

I checked and both the RAM and the swap gets fully saturated.
My questions are:

Is there a way to tell the compiler to launch less threads (--parallel-workers 1 it's not enough)?
Is it possible to provide a version working with pre-build binaries?

Environment

ROS Distro: Humble
OS Version: Ubuntu 22.04 (inside WSL 2)
Source, commit hash 20be39797b17e460fda48975a0a8ee25f8ad87ac

Steps to reproduce
Run colcon build --mixin release --parallel-workers 1
Thank you very much!

Possible solution to question number 1:
Before running colcon build, set the MAKEFLAGS environment variable to j1:
$ export MAKEFLAGS=-j1
$ colcon build --mixin release --parallel-workers 1

Source:

Set number of threads used by make permanently

Hi,
I'm new to ROS and also hit myself on this issues that is not yet modified in the docs.
the colcon build ros2 humble.
I've upgrade also my memory up to 16Gb and have the last intell processor with 12 thread, also a Dedicated Nvidia Graphics Card.


git-town: 9.0.1 -> 10.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/git-town/git-town/releases.
meta.description for git-town is: Generic, high-level git support for git-flow workflows
meta.homepage for git-town is: https://www.git-town.com/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 10.0.0 with grep in /nix/store/3yb37ldksxgrjxaf1i0gxlpqpz2npkyw-git-town-10.0.0
found 10.0.0 in filename of file in /nix/store/3yb37ldksxgrjxaf1i0gxlpqpz2npkyw-git-town-10.0.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
git-town

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/1fe22f3ba8d3a191b776991f60b4b2543c73d0b7#git-town

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/3yb37ldksxgrjxaf1i0gxlpqpz2npkyw-git-town-10.0.0
ls -la /nix/store/3yb37ldksxgrjxaf1i0gxlpqpz2npkyw-git-town-10.0.0/bin

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

1 package built:

git-town

Maintainer pings
cc @allonsy @blaggacao for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/git-town/git-town/releases.
meta.description for git-town is: Generic, high-level git support for git-flow workflows
meta.homepage for git-town is: https://www.git-town.com/
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 10.0.1 with grep in /nix/store/9nvjw4x9967wddw6xq20m820zsa3ywc9-git-town-10.0.1
found 10.0.1 in filename of file in /nix/store/9nvjw4x9967wddw6xq20m820zsa3ywc9-git-town-10.0.1

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
git-town

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/f56b520024cf2f8b9717bf0da192d0ddfa722554#git-town

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9nvjw4x9967wddw6xq20m820zsa3ywc9-git-town-10.0.1
ls -la /nix/store/9nvjw4x9967wddw6xq20m820zsa3ywc9-git-town-10.0.1/bin

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

1 package built:

git-town

Maintainer pings
cc @allonsy @blaggacao for testing.


feature: implement support for classical shadows and computing expectation values with them

Issue #, if available: N/A
Description of changes:
Add support for Braket devices (local and remote) to compute expectation values with the classical shadows technique.
The implementation is a little weird because we have to work around how the current PL device API "expects" plugins to interact with the ShadowExpvalMP transform. Each snapshot is a single-shot run so for remote devices, we can use batching to speed up the computation.
Testing done:
Basic integration tests added. Very open to suggestions.
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Do you think we'll need a warning for users who try this on actual hardware, given how expensive single-shot measurements can actually be?


Group S3 policies by action rather than resource

Problem

The initial version of storage access grouped IAM policies by S3 prefix. This is problematic because the number of S3 prefixes may be large and cause policy size limit issues.
Additionally, once we implement deny rules on subpaths, this grouping will make those policies easier to reason about (at least in my head).
Issue number, if available:
Changes

Group policies by S3 action, which we are only supporting a few of. This will keep the policy size from growing linearly with the number of S3 prefixes.
The updated tests should make it fairly obvious how the policies are being changed. Note that the permissions being granted by the policy is NOT changed by this PR.
There's also a little bit of type refactoring included.
You may notice a few of the test cases where there are multiple actions on a single S3 prefix actually create a larger policy document now. There is a potential optimization we can make to group by both action and prefix when they are the same. This optimization can be made if/when needed in the future.
Corresponding docs PR, if applicable:
Validation

Updated existing unit test coverage.
Checklist

[x] If this PR includes a functional change to the runtime behavior of the code, I have added or updated automated test coverage for this change.
[x] If this PR requires a change to the Project Architecture README, I have included that update in this PR.
[x] If this PR requires a docs update, I have linked to that docs PR above.
[x] If this PR modifies E2E tests, makes changes to resource provisioning, or makes SDK calls, I have run the PR checks with the run-e2e label set.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Github forced me to approve so many times 😂

Github forced me to approve so many times 😂

@0618 You just approve that much lol


.net dependency walker when managed code dll are being loaded

Hello,
in a search for CLR based DLL's dependency walker your tool showed. A nice feature is not to crash on a compiled C# DLL - just showing the mscoree.dll dependency.
A nice addition would be to walk through the CLR dependency tree when encountering such a DLL.

Weird, both the v1.7 GUI and the CLI works for  mscoree.dll:

Can you give me additional info about your crash, or maybe sending me your  mscoree.dll ?
About your second point, Win32 and CLR are two separate Windows subsystems, so it would be better to display the CLR dependency tree in a separate standalone tool IMO. Moreover I don't know enough about C# and CLR to properly display the information in a useful way.

Dependencies works fine with mscoree.dll, and shows similar resultas as yours.
What I mean is when try to see the dependencies of for example log4net.dll from the log4net nuget package, it will not show the .net assemblies log4net depends on.
Something in fact ,net dependency walker which I found later : https://www.workshell.co.uk/products/netdepends/

If I understand it correctly you want to see the dependency of your dependency. I think this could be related to the bit from the readme that says (correct me if I'm wrong):
Dependencies currently does not recursively resolve child imports when parsing a new PE since it can be really memory-hungry to do so ( it can over a GB even for "simple" PEs ). This behaviour can be overriden (app-wide) via a property located in "Options->Properties->Tree build behaviour".
Tree build behaviours available :

ChildOnly (default) : only process PE child imports and nothing beyond.

RecursiveOnlyOnDirectImports : do not process delayload dlls.

Recursive : Full recursive analysis. You better have time and RAM on your hands if you activate this

@Pascal7z : I've added assembly enumeration for C# binaries with commit https://github.com/lucasg/Dependencies/commit/b5278e45e491e2c1d94c9250d970cd59ede0d5c9. This will be available in the next release.
Before :

After:


Browse aspect versions for /entities Rest.LI endpoint

Is your feature request related to a problem? Please describe.
Story 1
As an API user, given I have  entity URN and aspect name, I want to have posibility to:

get a list of aspect versions
get a specific version of aspect

Story 2
As an API user, given I have entity URN, I want to get history of entity changes across all snapshots. Something like:
 select urn,aspect,version,metadata,createdon from metadata_aspect_v2 order by createdon;

Describe the solution you'd like
I see no easy way to retrieve non-latest aspects while it is useful for a lot of needs

@gabe-lyons : FYI since your latest PR might have addressed this.

Hi folks!
We are now managing feature requests through our new portal to improve visibility & prioritize work into our public roadmap. If this request is still relevant, please create a new issue so we can gauge current interest from the Community & prioritize work accordingly.
We'll close out this issue in the meantime. Feel free to reach out to me on DataHub Slack with any questions!


fix: Connect to discord modal appears for connected users

Closes #1527
The issue cause is that after the user connects to discord, the query gets the user's data from the cache instead of the server where it's the most updated.
This PR sets the query fetchPolicy to network-only so it'll always get the most updated data from the server instead of the cache. This will prevent any outdated data.
Article that helped

Lets say I have already connected to discord. I then log out of c0d3.com, and then log back in. Will the changes in this PR prevent the connect to discord modal from popping back up?

Lets say I have already connected to discord. I then log out of c0d3.com, and then log back in. Will the changes in this PR prevent the connect to discord modal from popping back up?

Yes, the modal won't appear. I tested it.

Also, how is c0d3 currently identifying whether the user has connected to discord before or not?

It identifies it based on whether the discordRefreshToken exists or not. Code


dead nodes block drivers' execution on other nodes

Steps to reproduce the behavior (Required)

CREATE TABLE '...'
INSERT INTO '....'
SELECT  '....'

a query running on several nodes, if a node is dead like because of OOM, related drivers on other nodes may be blocked for a long time, which is _brpc_timeout_ms(std::min(3600, fragment_ctx->runtime_state()->query_options().query_timeout) * 1000) and the mysql client is holded. this blocking behavior is not as expected.
Expected behavior (Required)
the query stops soon.
Real behavior (Required)
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()
main

current reproduce step:
use ssb_100g on pipeline_benchmark or benchmark04 cluster.
2 mysql client run the following sql to trigger OOM, so to reproduce the issue listed below.
SELECT S_NATION, COUNT(DISTINCT C_NAME) FROM lineorder_flat GROUP BY S_NATION;
SELECT S_NATION, COUNT(distinct LO_PARTKEY), COUNT(DISTINCT C_NAME) FROM lineorder_flat GROUP BY S_NATION;


i2c_write_blocking() hanging on SDK 2.1.0

After switching from SDK 2.0.0 to 2.1.0, I noticed that ss_oled OLED panel library stopped working (it hangs when initializing the OLED panel).
This issue was clearly introduced in SDK 2.1.0, as issue is not present in 2.0.0 or 1.5.0.
I traced the hang to i2c_write_blocking() call:
ss_oled/BitBang_I2C.c(322):
 rc = i2c_write_blocking(i2c0, iAddr, &u8Register, 1, true); // true to keep master control of bus

(at least on  Pico W  the i2c_write_blocking() call never returns)
Curiously, after I changed this line to following, that fixed the problem:
rc = i2c_write_timeout_us(pI2C->i2c, iAddr, &u8Register, 1, true, 100000); // true to keep master control of bus

(also its not timing out but succeeding normally, so blocking write should not hang either?)

@tjko If you're keen, you could try reverting a couple of changes? It would be helpful to know which caused the problem. My bet would be on the first. I have a SSD1306 but it'll be a couple of days before I can test it...
commit 68778b1135783f374155df4d609737cd3036b027
commit 3bc866395cc755f344d341a7f0b13b99d641cb0f

@peterharperuk , I reverted the change https://github.com/raspberrypi/pico-sdk/commit/68778b1135783f374155df4d609737cd3036b027 and fixed the hang as well.
I have two devices on the I2C bus:
0x38 AHT21  (Temperature/Pressure sensor)
0x3c SH1107 (1.5" 128x128 OLED Panel)
I also noticed that if I only have the OLED panel connected, I don't see the 'hang'...

Thanks. Do you know if the lockup occurs if you just have the AHT21 connected?

No, since lockup happens in the ss_oled library, and when there is no panel found in the bus it won't get far enough to initialize it...
I noticed that the sensor library uses 'non-blocking' functions (i2c_write_timeout_us(), i2c_read_timeout_us()), so new SDK didn't cause any issues with it.
I'm initializing I2C sensors first, before trying to initialize the OLED panel, maybe the condition is triggered by first accessing another device with "non-blocking" read/write calls and then trying to initialize OLED panel, where the library is using the "blocking" read/write calls...


Does not connect to websocket server on Windows NT 4

Title.
If anyone would like to help fix this, let me know.
I'm open to changing the libraries used (websocketpp+asio) if it means DM on NT 4 will be able to connect to Discord's websocket servers.

https://github.com/pocoproject/poco
https://github.com/Qihoo360/evpp

Would any of them help? I think Poco will help since I see that it supports WebSocket.

I have my doubts. Probably it's asio screwing up SSL.

What's screwing up SSL?

I can't tell you for sure because I wasn't able to find a concrete cause.

I'm just stating that Poco might be an alternative that will work to fix this issue.

And I think it is asynchronous.

I guess none of those will help.


Cow: Watch yt1d.online

Cow requests the watch of the watch_keyword yt1d\.online. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

yt1d\.online has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


fix maxZoom conflict

hi @treenewbee and sorry for the late answer, I'm just trying to do a bit of cleaning chore: can you be a bit more explicit on which conflict you are trying to solve ? Thanks in advance!

hi @treenewbee and sorry for the late answer, I'm just trying to do a bit of cleaning chore: can you be a bit more explicit on which conflict you are trying to solve ? Thanks in advance!

so maxZoom is originally referring to zoom level where the points reach maximum intensity (as intensity scales with zoom), I added min/maxZoom which is the min max to draw the heat map layer. My thinking is to avoid confusion, rename it "maxIntensityZoom" so it is clear what it actually does.


Inactive backend

Wanted to test generator-connector again, but there seems to be a problem now:
I'm trying to start the generator, but the backend isn't active.

So I don't receive any message, that generator does anything. And each time I run docker-compose up, I see following messages:

Any guesses?

Have you already rebuild the backend container?

Ehm.. how? :) You mean mvn install? It was a new clone, so all files were fresh. I did mvn install, than for UI npm i (wasn't probably needed, but anyway) and tried to start docker-compose up.

With docker build backend --no-cache
Some days ago I pushed some changes to the structure of the docker image. Most likely, that's why you get this error message and rebuilding should fix this. Usually, this step is not necessary. Only in this situation, since the dockerfile itself changed.

Should there really stay "backend" or something different, like backend-container name/ip?

docker-compose, not docker, sorry


HdfsDataSegmentPusher: Properly include scheme, host in output path if necessary.

Fixes #3576.

👍

@gianm will this always put "hdfs://host:port" in the load spec even if same was not specified in the "storageDirectory"
i'm asking because we sometimes move segments from one hdfs cluster to another while keeping the absolute path of all the segment files same. Earlier, since "host:port" wasn't present in the db so no db updates were required to do this kind of movement.
wondering if that is still the case after this PR?

@himanshug if the storageDirectory has no scheme (just /path/to/blah), it will stay relative in the loadSpec . See the UTs, one of them is for a storageDirectory with no scheme.

@gianm that sounds good, thanks.


rescue PG::ConnectionBad

PG:ConnectionBad is thrown if the database cannot be communicated with while using 0.17.1 of the pg gem (Rails/ActiveRecord 4.2).  This prevents rake assets:precompile from running successfully when a model utilizing acts_as_geolocated is loaded during asset compilation (Devise loads the user model, for example).
This became an issue for me on Heroku where I am using qgtunnel in my Procfile to route traffic through a proxy (i.e. the Procfile is only used when starting the server).  Since the proxy is not available during Heroku's bundle invocation the DB connection fails, which also causes asset compilation to fail.

No problem thank you for merging this.

Thanks for the PR

No problem thank you for merging this.


Implement the rest of Set Operators

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

[ ] INTERSECT
[ ] INTERSECT ALL
[ ] EXCEPT
[ ] EXCEPT ALL

Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Please assign me, thanks! @houqp

First of all, I'll implement INTERSECT
My direct idea is to rewrite it to left-semi Join
such as
SELECT a1 FROM t1 INTERSECT SELECT a2 FROM t2;

to

SELECT DISTINCT a1 FROM t1 LEFT SEMI JOIN t2 ON a1 is distinct from a2

How do you think about it? @houqp @alamb @Dandandan
If it's ok, I think I should implement is distinct from firstly.  https://www.postgresql.org/docs/14/functions-comparison.html

Creating / using is distinct from makes sense to me 👍  ). Good thinking @xudong963

It looks like PostgreSQL has some explicit operator (HashSetOp) for these kind of things:
> explain select * from demo intersect select * from demo;

HashSetOp Intersect  (cost=0.00..30.40 rows=160 width=458)
  ->  Append  (cost=0.00..28.00 rows=320 width=458)
        ->  Subquery Scan on "*SELECT* 1"  (cost=0.00..13.20 rows=160 width=458)
              ->  Seq Scan on demo  (cost=0.00..11.60 rows=160 width=454)
        ->  Subquery Scan on "*SELECT* 2"  (cost=0.00..13.20 rows=160 width=458)
              ->  Seq Scan on demo demo_1  (cost=0.00..11.60 rows=160 width=454)

I can see the potential benefit of implementing some special physical operator to implement INTERSECT / EXCEPT -- it might be potentially faster than the general purpose join operator
However, that being said, using a general purpose SEMI join as you have suggested @xudong963  would definitely be my preference to keep the DF code base simpler, unless there is some compelling performance measurement / need for a faster implementation

@Dandandan  has made https://github.com/apache/arrow-datafusion/pull/1117 to add is distinct from

After https://github.com/apache/arrow-datafusion/pull/1135 merged, I believe the issue will be closed quickly, because on the basis of https://github.com/apache/arrow-datafusion/pull/1135, EXCEPT can be implemented by ANTI JOIN with null_equal_null.

The issue needs to reopen, there are other things to do, such as Expect support. @alamb

Reopening as github API got a little too excited

All related PRs have finished, after merging, the issue can be closed. Thanks for your help! @alamb @Dandandan @houqp


Connection Error on dl_docs

Hi, when trying to download documents I get connection error. Worked fine in the past...
Error log
pytr dl_docs .
23:19:02 Found credentials file
23:19:02 Phone: +49160********, PIN: ****
23:19:03 Web session resumed
23:19:03 Logged in
23:19:03 Awaiting #1  timeline
23:19:03 Connecting to websocket ...
Traceback (most recent call last):
  File "/usr/local/bin/pytr", line 10, in <module>
    sys.exit(main())
  File "/Library/Python/3.7/site-packages/pytr/main.py", line 152, in main
    asyncio.get_event_loop().run_until_complete(dl.dl_loop())
  File "/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.7/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/Library/Python/3.7/site-packages/pytr/dl.py", line 34, in dl_loop
    await self.tl.get_next_timeline(max_age_timestamp=self.since_timestamp)
  File "/Library/Python/3.7/site-packages/pytr/utils.py", line 100, in get_next_timeline
    await self.tr.timeline()
  File "/Library/Python/3.7/site-packages/pytr/api.py", line 438, in timeline
    return await self.subscribe({'type': 'timeline', 'after': after})
  File "/Library/Python/3.7/site-packages/pytr/api.py", line 288, in subscribe
    ws = await self._get_ws()
  File "/Library/Python/3.7/site-packages/pytr/api.py", line 274, in _get_ws
    raise ValueError(f'Connection Error: {response}')
ValueError: Connection Error: failed 31

Environment

OS: Mac OS 14.2.1 (23C71)
pytr version: (pytr: error: unrecognized arguments: -V)

Solution: Update way outdated pytr (0.0.X) to newer version (0.1.9). Works again.


Make mentions distinct

Pull Request Etiquette
There are several guidelines you should follow in order for your
Pull Request to be merged.

[x] I have checked the PRs for upcoming features/bug fixes.
[x] I have read the contributing guidelines.

It is sometimes better to include more changes in a single commit.
If you find yourself having an overwhelming amount of commits, you
can rebase your branch.

Description
This makes sure we only add users/roles/channels once to the list

It would be cheaper memory-wise to do a .contains check before adding rather than making a Set and making a List


User can update items in Whishlist

The user should be able to update the Quantity of an item in the whishlist, and should also be able to remove that item from the whishlist.


krakendauth: Track groups get call as separate txn

Ref: https://github.com/Unacademy/krakend-auth/pull/11

LGTM


Grader: Allow SIGINT to be handled when waiting for a subprocess (fixes #144)

When forking a child process, both the parent and the children reside in
the same process group. Signals like SIGINT that directed to a process
group will be distributed to all processes in the group. However, the
grader did not receive SIGINT when issuing [Ctrl]+[C] in a hosting
terminal. This is due to to the grader using system to start the child
processes.
As per the man-pages of system for
FreeBSD,
macOS
and Linux, signal SIGINT will be
ignored while the application waits for the child process to finish.
Unfortunately, the return value of Python's os.system is
platform-dependent.
This commit instead uses subprocess.run which under the hood calls an
execve-like function. SIGINT will not be masked by this and will be
received by both the child git processes and the parent grader
process.

@Blazefrost Very nice! Thank you. Could you please check the failing grader target? I am not sure if it is related to your PR.

I finally found out what was wrong. It was actually the unit test itself that failed because it mocked a replaced function. See b0f8df3 for a detailed write-up

@Blazefrost Sounds complicated :/ the build is still failing :/ can you please check?

Didn't the checks suceed? While the first commit, 6c66b80, is marked as failed, GitHub says that 9 checks were successful and two are expected

@Blazefrost You are right. Seems to work :)


feat: allow parallel, remove '--force'

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


chore(controller): update djangorestframework to 3.0.4

See https://github.com/tomchristie/django-rest-framework/compare/3.0.3...3.0.4

If only we could use this with our current implementation of UUID fields. Sigh.
code lgtm

Code LGTM.


Deprecate :for directive.

Removing the use of the :for directives in tests required updating the tests' expected results.
Running the tests emits :for directive deprecation warnings. Tests need to still be included on the :for directive so this is a necessary evil.

Hi @djgoku!
Thank you so much for the PR. I believe we need to rethink the decision to add this deprecation and keep :for, now that HEEx has introduced it to its own syntax. As far as I know, there might be some new LV features coming in the future that may depend on that syntax.
My suggestion would be to remove the deprecation warning and update the docs accordingly. @Malian, @miguel-s and @davydog187, WDYT?
@djgoku please let me know if you'd be willing to work on that and thank you again for the PR.

Really it all depends on this part:

there might be some new LV features coming in the future that may depend on that syntax.

Any spoilers you can shere? 😁
If Surface's template syntax {#for} can support these new features I would still vote for deprecating :for. Having two different ways of achieving the same thing is more work in maintenance and also more confusing to document.
If {#for} can't support these new features then having both "for" versions with different capabilities has the potential to become quite confusing. Maybe {#for} should be deprecated?

Maybe {#for} should be deprecated?

One of the main reason I use Surface is that the template engine allows us to have clearer templates compare to what Heex offers. I know this is maybe subjective and just my opinion, but my fear is that if we decide to deprecate {#for} why should we keep the other blocks expressions? And, if we decide to keep the other block expressions, I am pretty sure we will receive requests to add {#for} every month ^^
I am also afraid that if we decide to keep the deprecation, it will affect the Surface user adoption. In conclusion, I am in favor of keeping :for.

One of the main reason I use Surface is that the template engine allows us to have clearer templates compare to what Heex offers.

+1 on this. I love the template syntax and {#for}!
Maybe I worry too much, but I think having {#for} and :for will be confusing if the functionality of both diverges.

Maybe I worry too much, but I think having {#for} and :for will be confusing if the functionality of both diverges.

Sorry, miss click for the close/open the pull request ^^

Maybe I worry too much, but I think having {#for} and :for will be confusing if the functionality of both diverges.
It could be an issue indeed.

There's no way will ever deprecate {#for} as it is the only way that allow us to work with multiple nodes. The question is only if we should keep :for.
My idea is to keep it for now until we have a better picture of how it will evolve in LV. There are some ideas to use it in cases where {#for} won't fit. One example is if we ever want to allow dynamic slots, which is been a common request by users, there might be a chance to implement it in a more natural way using :for as it keeps the requirement of the slot being a direct child of the parent component defining the slot. There might also be some developments regarding using streams to dynamically update view content.
LV already accept <%= for ... do %> and :for as well as the if counterparts. We already agreed we're keeping :if, so it doesn't sound that odd to me. If in the future :for turns out to be redundant, we can circle back to the discussion.

LV already accept <%= for ... do %> and :for

That's a great point. Always forget about the LV syntax...

We already agreed we're keeping :if

Missed this discussion, sorry. I agree that if we keep :if it does make sense to also keep :for.

@msaraiva I would be in favor of keeping :for in its current form, for two reasons

I believe there is actual utility in it over {#for} for building concise lists
For the reasons you highlighted with the future of LV

My suggestion would be to remove the deprecation warning and update the docs accordingly. @Malian, @miguel-s and @davydog187, WDYT?

@msaraiva I'll remove the deprecation warning. But I am not sure what is meant by update the docs. I'll see both {#for [1] and :for
[2] are documented. So I am not sure if there are any other places that need to be updated.
Should I keep all my test changes that switched from :for to {#for?
Sorry for the late reply.
[1] https://github.com/surface-ui/surface_site/blob/e8058cd5fa4d5c684743325f7e8a850437bd571f/lib/surface_site_web/live/template_syntax.ex#L207-L227
[2] https://github.com/surface-ui/surface_site/blob/e8058cd5fa4d5c684743325f7e8a850437bd571f/lib/surface_site_web/live/template_syntax.ex#L272-L273

Since LV implemented :for as well, we're not deprecating it anymore. Thank you all for the discussion.


Placeholder attribute issue

Challenge http://www.freecodecamp.com/challenges/waypoint-add-placeholder-text-to-a-text-field has an issue.
I think I wrote the correct code, but I keep recive this error: Set the value of your placeholder attribute to "cat photo URL".

You do not need to create a new input; just add the placeholder attribute to the existing one.

Thank you!

thanks


File too large to open - but only 700meg

Issue Type: Bug
Hi when opening a 700meg file it says "file cannot be opened in the editor because it is too large". I already set set memory for large files = 8192. It used to work well for files of 2gig+ before this update. Would be nice if this can be fixed
VS Code version: Code 1.55.2 (3c4e3df9e89829dce27b7b5c24508306b151f30d, 2021-04-13T09:35:57.887Z)
OS version: Windows_NT x64 10.0.18363
Extensions (3)

Extension
Author (truncated)
Version

python
ms-
2021.3.680753044

vscode-pylance
ms-
2021.4.0

jupyter
ms-
2021.5.745244803

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry244:30276681
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt875:30259475
pythonvsnew554:30281908
pythontb:30283811
wslfolderdoc:30282074
vspre833:30267464
pythonptprofiler:30281270
vshan820:30276952
pythondataviewer:30285071
vscus158cf:30286554
vscgsv2:30286881

Can you make that file available somehow?

Sample_file - first 100 lines.txt
Hi thanks for replying. I see now the cause are some unicode "control characters". If I change those to ordinary ASCII then the file opens in VC. Here is a file with the first 100 lines. A file consisting of simply the first line repeated 1367846 times, will recreate the problem. The resulting file is then 684 meg or 718 119 150 bytes. If you would rather like the full file, you can say what the best way would be for me to upload it. We could also change the title of this thread to something like "file with unicode control characters won't open" I guess. Much appreciated!

I see now the cause are some unicode "control characters".

Can you prepare a file that contains those characters? We have some logic to detect if a file is binary or not, mainly looking for zero-bytes and then refuse to show the file in the text editor.

Hi the small sample file above has the characters. They are at col 308 (4 chars) and then on about 7 subsequent places (4 chars each). When I try to open the small file above, VC says at first "this file is not displayed in the editor because it is either binary or uses an unsupported text encoding. Do you want to open it anyway". When I click on "anyway" the funnies show as NUL. I only realised later that these chars are the problem, sorry. It would be nice though to have seen the encoding warning before the big file warning. I can easily upload the big file somewhere if you like .. Github won't allow me to do it here in this thread, but maybe there is an alternative location we could use e.g. my own main (sadly a bit empty) Github page? What do you suggest. Thanks again

I decided to simply remove the logic that would try to check on the size of the file and now we always show the message that allows to open the editor differently, given we have protections in place that guard against opening too large files.

Verification: open a file > 200 MB containing a 0x00 zero byte sequence and verify you are offered to open it in the text editor.

Hi thank you so much for the effort! Yes this is a good solution, then one knows what is going on.
Would I have to download a test version of VC for this ... or is it already in the latest update?

Works now in VC insiders! Thanks so much /verified


How to get the ARCHIVE_KEY?

“Run the following code in two different places and they will replicate the contents of the given ARCHIVE_KEY”
How to get the ARCHIVE_KEY?

@tiandiyiqi are you looking for an existing archive to test with? You can try my blog's key if you want.
const ARCHIVE_KEY = Buffer.from('0a9e202b8055721bd2bc93b3c9bbc03efdbda9cfee91f01a123fdeaadeba303e', 'hex')


Game crashes randomly

The game crashes randomly, for example - I'm riding my bike and suddenly it crashes. I've noticed that crashes occur more often in free play than during missions, but they also happen sometimes when I'm doing a mission. Sometimes there are missions during which the game crashes all the time, and during some missions it does not crash at all.
I'm currently completing the "Preppies Vandalized" mission. I tried to complete it several times, but each time the game crashed. During this mission, the first time the game crashed when I left the warehouse, the second time when I was riding my bike to the place, the third time when I returned to the gym and pressed pause (the game often crashes after pressing esc/tab), the fourth time it crashed again when I was riding a bike and after the fifth time it crashed and I hadn't even started the mission yet, I tried to enter the mission start marker and suddenly - crash.
My OS is Windows 10 and I have tried everything. Playing with the patch, without the patch, Windows XP SP3 compatibility mode, running game as administrator, DPI scaling, changing resolution, reinstalling Bully, disabling shadows, changing CPU affinity and nothing worked, the game still crashes. The only mods I use are this patch and widescreen fix. My computer is low end and these crashes are certainly not related to a too powerful processor or graphics card.
Please help. I've tried everything and the game still crashes. I am attaching some crash dump files. (file size limit here is 25 mb and my DMP files are usually 39 mb, so i'll give link to google drive)
https://drive.google.com/drive/folders/1T8OKd1CvmhgZ2VsS1-uQPobEDt27Cgfp?usp=drive_link

Try changing CustomMemoryMgr from = 0 to = 1. Worked like a charm for me.

I changed this and everything worked great for a while, but then it started crashing again


make findProgramAddress public

Can the "findProgramAddress" function in the PublicKey extension be made public.  It is currently private and therefore can't be used by applications to directly calculate Program Derived Addresses (PDA's).
File to update:  Extensions  /  PublicKey  /  PublicKey+AssociatedTokenProgram.swift

@DruidCastle I've got a PR that actually fixes this, but it is draft because I wanted to get some discussion on the approach to see if it's a good (re. adding support for anchor contract instructions). Do you think it's worth splitting this part of it out into a separate PR?

It is now.


RangeError: Array buffer allocation failed when mounting the indexeddb partition

When trying to write a relatively large number of files (over 600) to indexeddb and reloading the page in a web browser, I get a mount error:
chunk-3CTS4YNX.js?v=fa2b0238:9430 Uncaught RangeError: Array buffer allocation failed
    at new ArrayBuffer (<anonymous>)
    at PreloadFile._write (chunk-3CTS4YNX.js?v=fa2b0238:9430:44)
    at PreloadFile.writeSync (chunk-3CTS4YNX.js?v=fa2b0238:9465:31)
    at AsyncFS.crossCopy (chunk-3CTS4YNX.js?v=fa2b0238:14045:20)
    at async AsyncFS.crossCopy (chunk-3CTS4YNX.js?v=fa2b0238:14062:9)
    at async AsyncFS.crossCopy (chunk-3CTS4YNX.js?v=fa2b0238:14062:9)
    at async AsyncFS.crossCopy (chunk-3CTS4YNX.js?v=fa2b0238:14062:9)
    at async AsyncFS.ready (chunk-3CTS4YNX.js?v=fa2b0238:13961:9)
    at async resolveMountConfig (chunk-3CTS4YNX.js?v=fa2b0238:13843:3)
    at async configure (chunk-3CTS4YNX.js?v=fa2b0238:13877:35)
Show 3 more frames

This error is not reproduced when the number of files is small
supressed property is empty in the error
reproduction example: https://stackblitz.com/edit/vitejs-vite-vghser?file=src%2Fmain.ts (just wait until the files are created, then reload the page with the browser console open.)

@Artawower,
Thanks for opening an issue. From some research, this error seems like it could be due to an out-of memory issue or incorrect length. According to MDN,

RangeError
Thrown in one of the following cases:
length or maxByteLength is larger than Number.MAX_SAFE_INTEGER (≥ 253) or negative.
length is larger than maxByteLength.

source
If you could provide the values used when attempting to create the ArrayBuffer, that would be very useful.
Here is the affected line: https://github.com/zen-fs/core/blob/d4969b5ee0865d3c2d82edecfaa621769cd66561/src/file.ts#L469

The end value is 5125 (same as other files). This is the locale scope before the error occurred
locale-scope.txt

I've been unable to reproduce the error. Could you please let me know what platform (e.g. Chrome 128 or Node 20.6.1) you're using? Additionally, if you could try to reproduce the error on another platform, that would be great.
Thanks.

I've been unable to reproduce the error

In the example I gave, does the mount work without error on your machine?
I am using chrome, interestingly this error does not appear in firefox for example.. I also tried reproducing the problem on other platforms (windows/linux), the result is the same
In node environment I also don't see this error, however I don't know how to use IndexedDB mount in node, so I used InMemory approach, maybe that's the issue
Perhaps there are some additional steps I can help you with to reproduce the error?

In the example I gave, does the mount work without error on your machine?

Yes

I am using chrome, interestingly this error does not appear in firefox for example.. I also tried reproducing the problem on other platforms (windows/linux), the result is the same

I am using Firefox, so that may be part of it.

In node environment I also don't see this error, however I don't know how to use IndexedDB mount in node, so I used InMemory approach, maybe that's the issue

You'll need to import a polyfill.

Perhaps there are some additional steps I can help you with to reproduce the error?

I think I can try to debug this on Chrome. Unfortunately, I suspect this is a vendor-specific limitation, not something inherently wrong with ZenFS' code. I'll let you know if I confirm the bug.

Okay, I can confirm this is a problem with Chrome. However, it appears this isn't a problem with ZenFS but rather a limitation in V8. It looks like this error comes from builtins-arraybuffer.cc!ConstructBuffer, and is caused when the "Allocation of backing store failed."


‘RouteRandomizer.sol’

Description
With the completion of the ‘Lootbox.sol’ contract, it occurs to me that this idea of routing to a random contract with the same inputs does not need to be limited to Crafter contracts. You can put Transformer or Minter contracts behind it as well! Perhaps if you hold a special nft, it behaves as a lootbox 98% of the time, but 2% of the time it upgrades your sword. Or maybe a minting can be held where the contract from which you are minting has probabilities involved. I think that this is a really cool concept and would be great to have as one of the contracts whose support is gated behind holding the OWL NFT (or a certain amount of $OWL). And the ‘Lootbox.sol’ can be a great teaser and demonstration of the usecase. For free, game developers can route randomize Crafter contracts but to route randomize other plugins or even mix and match, they’ll have to be a holder.
Implementation

Initializer will initialize array of contract addresses and array of signatures (must be same size)
‘randomizeRoute(bytes[] memory args)’ whose argument array contains the respective arguments from the array of signatures
First argument in array of signatures will always be address that will be filled in to be ‘_msgSender()’ by ‘randomizeRoute()’
All functions that are able to be called by the ‘RouteRandomizer.sol’ contract must be refactored. The function must be prepended with _ and made internal. Then, address argument is prepended to the internal function. Finally, two functions are created of the same name without the ‘_’. One takes the address as the parameter and is protected by ‘onlyRole(FORWARDER_ROLE)’. The other one doesn’t have an address parameter. Both function will call the internal function but the protected one passes the parameterized address while the other simply passes ‘_msgSender()’.

/cib

@aqzhen Add boolean routed on Transformer.sol and  Crafter contracts to indicate it is part of a RouteRandomizer scheme. It would be problematic if the Crafter or Transformer could be called directly.


#47: Add new issue templates

:white_check_mark: Build ArmorPowerShell 1.0.201-ixscfdpk completed (commit https://github.com/tlindsay42/ArmorPowerShell/commit/0957e86f08 by @tlindsay42)


rkt: Avoid possible panic

Fixes #3109
See the comment there for more details about this

Semaphore doesn't let me rekick the build for some reason, but Jenkins is all green.

Confirming running a while true; do echo "creating nginx"; kubectl create -f nginx.yaml; sleep 10; echo "deleting nginx"; kubectl delete -f nginx.yaml; sleep 10; done for the last 1.5hrs in the minikube buildroot image didn't mark the node being down :+1:


Replace the crate async_trait with rust native support

Prerequisites
affected version: Master
make sure to check this before filing an issue:

[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed

Describe what you would like to have
Native support for async traits has been added to rust form Version 1.75, which should be able to replace using the crate async_trait in the most cases, especially with a stand-alone application where no other apps have dependencies on the codes like with libraries to consider.
I want to try to replace the crate async_trait with the native rust solution, but at first I want to make sure that there are no problems to enforce the developers to use rust Version 1.75+.
Besides that we need to adjust the GitHub Pipelines to make sure that the latest rust version is installed

make sense

@DmitryAstafyev Should I try to implement this in the CLI tool at first, or it's better to wait to make sure that there is no problem with forcing the minimum rust Version to be 1.75?

@AmmarAbouZor hello.
I think CLI stuff and this issue don't depend on each other. For CLI we already have PR. As for this issue, it can go as a separate PR and you are welcome to create it from your fork as well.

@DmitryAstafyev I thought it would some restriction because some developers in the team can't install rust Version 1.75, then they can't build either the app or the CLI-tool.
I'll provide a PR to CLI-tool at first to check if we can apply it since the native support has its restrictions with concurrency too.

So I've tried to apply the native async-trait on the CLI-tool and got some weird build error about cycles inside the traits, then I've tried to build it using rust nightly to get error messages which make sense:
    --> src/target.rs:48:30
    |
48  |     pub fn get(&self) -> Box<dyn Manager + Sync + Send> {
    |                              ^^^^^^^^^^^^^^^^^^^^^^^^^ `Manager` cannot be made into an object
note: for a trait to be "object safe" it needs to allow building a vtable to allow the call to be resolvable dynamically; for more information visit <https://doc.rust-lang.org/reference/items/traits.html#object-safety>
   --> src/modules/mod.rs:78:14
    |
61  | pub trait Manager {
    |           ------- this trait cannot be made into an object...
...
78  |     async fn reset(&self) -> Result<SpawnResult, Error> {
    |              ^^^^^ ...because method `reset` is `async`

After reading the announcement of async traits in rust blog I've found out that dynamic dispatch still not supported with native rust. link.
I think we can postpone this until there is a proper support for native async-traits in rust.
@DmitryAstafyev Should we leave this issue open as reminder to check the progress of this issue with rust or we can just close it and open another once the native support is there?

To Info: I could replace the async trait in the indexer project with the native async rust but we decided to postpone it for a little to make sure all build systems support rust version 1.75

@AmmarAbouZor sorry, I've missed your comment. Let's focus on CLI... this issue "linked" to @sudeeptarlekar. It's in draft state and doesn't have hi-priority for now.


Remember to say that Microsoft Office and all related trademarks are owned by Microsoft Corporation. All rights reserved.

Fixed.


Document the tap-to-toggle demo in the catalog

Source code should include dense documentation explaining the material motion aspects of the code.

🎊 My diff is ready for review at http://codereview.cc/D1578


WRF Website Slug Validation

Can we add a validation message to the URL field of the self-organised notification form?
We already have the suggested format in the help text, so we are wondering if we could add a notification type validation message that could prompt correction if AMY will reject the workshop slug.
Context: AMY's slug field includes validation that prevents us from entering events that include underscores in the first 11 characters. For example, 2020-12-15-SITE_LESSON  is an accepted slug but 2020-12-15_SITE_LESSON or 2020_12_15-SITE_LESSON are not. That is okay.
Situation: We currently follow-up on the workshop slug after the form has been submitted and we are hoping to add a validation warning so that those who can change the slug are notified that the slug might need to be changed sooner.
Request: For user.github.io links entered into the URL field that do not meet AMY validation for the slug field. Please add a notice that reads: Would you be able to update the slug of the workshop webpage prior to submitting this notification? If so, we recommend using the following slug: YEAR-MM-DD-site-online. If not, that's okay and please feel free to submit the form.
Request 2: For user.github.io links entered into the URL field in the repo format github.com/username/slug . Please add a notice that reads: Please adjust the URL format so that it points to the workshop website. The format for this is username.github.io/slug.
Priority: Not Urgent. We currently have a manual workaround for the workflows affected by this validation issue.

@maneesha  - please feel free to adjust the wording of the notifications as needed.

This looks good to me.

@Talishask which form do you mean in request 1, and which in request 2?

Hey @pbanaszkiewicz - This is all in reference to the self-organised form.


Mocha test suite factory function should not be async

We discovered in https://github.com/microsoft/vscode/pull/187482#discussion_r1259551063 that some of our suite factory methods are async and can impact other tests as a result. After discussion, we have decided that we should limit suite factory methods so they cannot be async.
The first step is to write an eslint rule to find async suite factory methods.
The second step is to fix all the places this occurs:

[x] src\vs\editor\contrib\find\test\browser\findController.test.ts @alexdima
[x] src\vs\workbench\contrib\search\test\common\extractRange.test.ts @Tyriar
[x] src\vs\workbench\contrib\terminal\test\common\history.test.ts @Tyriar
[x] src\vs\workbench\contrib\terminal\test\node\terminalProfiles.test.ts @Tyriar
[x] src\vs\workbench\contrib\terminal\test\browser\xterm\decorationAddon.test.ts @meganrogge
[x] src\vs\workbench\contrib\terminal\test\browser\xterm\shellIntegrationAddon.test.ts @Tyriar
[x] src\vs\workbench\contrib\terminalContrib\quickFix\test\browser\quickFixAddon.test.ts @meganrogge

Once the PR for the eslint rule is in, you should just be able to see a warning by opening the file listed. To fix, make the second argument to the suite factory function sync (example: https://github.com/microsoft/vscode/pull/188380).
If you need to run async code during your suite setup, consider using a suiteSetup.

Now that debt week is beginning, please consider taking a look at the errors above so that we can merge this new eslint rule and prevent more unreliable tests to be written!

There were no awaits so I think we can just remove them all which I did in https://github.com/microsoft/vscode/pull/189171, merging that will close this out.

Great, thanks @Tyriar!

Oh opps, this will auto close. I see you will need to update the branch on https://github.com/microsoft/vscode/pull/188378 and merge in before this is closed.


Makefile:29: dmlc-core/make/dmlc.mk: No such file or directory make: *** No rule to make target 'dmlc-core/make/dmlc.mk'.

There is a problem with compiling. It must have been introduced recently, as I successful in installing xgboost a week ago.
git clone https://github.com/dmlc/xgboost.git
cd xgboost
make
returns:
Makefile:29: dmlc-core/make/dmlc.mk: No such file or directory
make: *** No rule to make target 'dmlc-core/make/dmlc.mk'.  Stop.

We need a recursive clone, see https://xgboost.readthedocs.org/en/latest/build.html#building-on-ubuntu-debian

Thank you. I was not aware of a change.

Could you please update wormhole making rules accordingly? It uses just 'clone' and gets the same error.

I just got the same error.  I was following the directions listed on dmlc/wormhole which led to the error.  Good thing I found this otherwise I would have given up trying to get started.

in wormhole home directory
cd ./repo/xgboost
cp -rf ../dmlc-core/* dmlc-core/
git clone your rabit and complier it
cd ./repo/xgboost
git clone https://github.com/dmlc/rabit.git
cd ./rabit && make && cd -
g++ -std=c++0x -Wall -O3 -msse2 -Wno-unknown-pragmas -funroll-loops -Iinclude -Idmlc-core/include -Irabit/include -fPIC -DDISABLE_OPENMP -shared -o lib/libxgboost.so build/learner.o build/logging.o build/c_api/c_api.o build/c_api/c_api_error.o build/common/common.o build/data/data.o build/data/simple_csr_source.o build/data/simple_dmatrix.o build/data/sparse_page_dmatrix.o build/data/sparse_page_raw_format.o build/data/sparse_page_source.o build/gbm/gblinear.o build/gbm/gbm.o build/gbm/gbtree.o build/metric/elementwise_metric.o build/metric/metric.o build/metric/multiclass_metric.o build/metric/rank_metric.o build/objective/multiclass_obj.o build/objective/objective.o build/objective/rank_obj.o build/objective/regression_obj.o build/tree/tree_model.o build/tree/tree_updater.o build/tree/updater_colmaker.o build/tree/updater_histmaker.o build/tree/updater_prune.o build/tree/updater_refresh.o build/tree/updater_skmaker.o build/tree/updater_sync.o dmlc-core/libdmlc.a -lm -fopenmp -lglog
ld: library not found for -lgomp
clang: error: linker command failed with exit code 1 (use -v to see invocation)
And now I known my mac g++ is clang, it can not support openmp.

@firstboy0513  What about trying brew install clang-omp?

Thanks @thirdwing , A good advise to use clang-omp, but now some symbols links error, I'll try to re-complie it later.
clang-omp++ -std=c++0x -Wall -O3 -msse2  -Wno-unknown-pragmas -funroll-loops -Iinclude   -Idmlc-core/include -Irabit/include -fPIC -DDISABLE_OPENMP -shared -o lib/libxgboost.so build/learner.o build/logging.o build/c_api/c_api.o build/c_api/c_api_error.o build/common/common.o build/data/data.o build/data/simple_csr_source.o build/data/simple_dmatrix.o build/data/sparse_page_dmatrix.o build/data/sparse_page_raw_format.o build/data/sparse_page_source.o build/gbm/gblinear.o build/gbm/gbm.o build/gbm/gbtree.o build/metric/elementwise_metric.o build/metric/metric.o build/metric/multiclass_metric.o build/metric/rank_metric.o build/objective/multiclass_obj.o build/objective/objective.o build/objective/rank_obj.o build/objective/regression_obj.o build/tree/tree_model.o build/tree/tree_updater.o build/tree/updater_colmaker.o build/tree/updater_histmaker.o build/tree/updater_prune.o build/tree/updater_refresh.o build/tree/updater_skmaker.o build/tree/updater_sync.o dmlc-core/libdmlc.a -pthread -lm  -fopenmp -lglog
clang-3.5: warning: argument unused during compilation: '-pthread'
Undefined symbols for architecture x86_64:
  "__ZN5rabit6engine10Allreduce_EPvmmPFvPKvS1_iRKN3MPI8DatatypeEENS0_3mpi8DataTypeENSA_6OpTypeEPFvS1_ES1_", referenced from:
      __ZN7xgboost11LearnerImpl13LazyInitModelEv in learner.o
      __ZNK7xgboost6metric13EvalEWiseBaseINS0_21EvalPoissionNegLogLikEE4EvalERKNSt3__16vectorIfNS4_9allocatorIfEEEERKNS_8MetaInfoEb in elementwise_metric.o
      __ZNK7xgboost6metric13EvalEWiseBaseINS0_9EvalErrorEE4EvalERKNSt3__16vectorIfNS4_9allocatorIfEEEERKNS_8MetaInfoEb in elementwise_metric.o
      __ZNK7xgboost6metric13EvalEWiseBaseINS0_11EvalLogLossEE4EvalERKNSt3__16vectorIfNS4_9allocatorIfEEEERKNS_8MetaInfoEb in elementwise_metric.o
      __ZNK7xgboost6metric13EvalEWiseBaseINS0_8EvalRMSEEE4EvalERKNSt3__16vectorIfNS4_9allocatorIfEEEERKNS_8MetaInfoEb in elementwise_metric.o
      __ZNK7xgboost6metric14EvalMClassBaseINS0_16EvalMultiLogLossEE4EvalERKNSt3__16vectorIfNS4_9allocatorIfEEEERKNS_8MetaInfoEb in multiclass_metric.o
      __ZNK7xgboost6metric14EvalMClassBaseINS0_14EvalMatchErrorEE4EvalERKNSt3__16vectorIfNS4_9allocatorIfEEEERKNS_8MetaInfoEb in multiclass_metric.o
...
ld: symbol(s) not found for architecture x86_64
clang-3.5: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [lib/libxgboost.so] Error 1
make: *** [repo/xgboost/xgboost] Error 2

@firstboy0513 Have you make clean_all?


price sorting is broken

Did you change from the default region? Might be related to that.

@powdahound I had some rows selected (highlighted), but once I removed that and refreshed the page it works fine now... Or there might have been a new deploy today maybe that fixed that now? Can't seem to replicate the error now, anyway. I'm closing the isssue.