Bug ? The glyphs rendered are not on the same line

Strange text rendering results when I render English and Chinese characters at the same time
Here is the rendering results of nanovg and sdl_ttf

Compared to SDL_ TTF,The Chinese glyphs and English glyphs seem to be not in the same line
It was much lower than English glyphs
It looks doesnot very good
Here is the code

//text and the fontsize
const char *text = "啊AB啊C啊D啊E啊F界 Hello哈哈哈World";
float fontsize = 12;

//Setup nanovg ctxt
...
//Load ttf
//Microsoft Ya Hei
int f = nvgCreateFont(ctxt,"font","./msyh.ttc");
TTF_Font *ttf = TTF_OpenFont("./msyh.ttc",fontsize);

//SDL_TTF Render text
SDL_Color color;
color.r = 0;
color.g = 0;
color.b = 0;
color.a = 255;

SDL_Surface *surf = TTF_RenderUTF8_Blended(ttf,text,color);

TTF_CloseFont(font);

int image = nvgCreateImageRGBA(
        ctxt,
        surf->w,
        surf->h,
        NVG_IMAGE_NEAREST,
        (Uint8*)surf->pixels
);
...

//Clear background
//nvgBeginFrame ...

//nanovg draw text
nvgBeginPath(ctxt);
nvgFillColor(ctxt,nvgRGB(0,0,0));
nvgFontFaceId(ctxt,f);
nvgFontSize(ctxt,fontsize);
nvgTextAlign(ctxt,NVG_ALIGN_TOP |  NVG_ALIGN_LEFT);
nvgText(ctxt,100,300,text,nullptr);
nvgFill(ctxt);
//SDL_ttf draw text
nvgBeginPath(ctxt);
nvgRect(ctxt,100,100,surf->w,surf->h);
nvgFillPaint(ctxt,nvgImagePattern(ctxt,
      100,
      100,
      surf->w,
      surf->h,
      0.0f/180.0f*NVG_PI,
      image,
      1.0f
 ));
nvgFill(ctxt);

//EndFrame ...
//SwapBuffer ...

Here is the font
msyh.zip
Can anyone help me?

The difference could be the way SDL/nanovg load the fonts. There are many parameters to freetype. What I would try is build ftview or ftgrid  from the freetype-demos and check out the various "hinting" and anti-aliasing modes, which sometimes give surprising differences. You'd probably have to patch nanovg, to use your desired font mode.

@mulle-nat @memononen
But when i change the hinting in fons__tt_buildGlyphBitmap into different flags such as FT_LOAD_DEFAULT or FT_LOAD_NO_AUTOHINT,it didnot works
It still perform as previous
I had already try all hintings and anti-aliasing modes
And and noticed the lsb in fontstash didnot be used in anywhere,what is the lsb used for
I think the difference is the font metrics is not be handled correctly
Because i saw the way of getting the font metrics in SDL_ttf is different from nanovg
in TTF_initFontMetrics

    /* Make sure that our font face is scalable (global metrics) */
    if (FT_IS_SCALABLE(face)) {
        /* Get the scalable font metrics for this font */
        FT_Fixed scale       = face->size->metrics.y_scale;
        font->ascent         = FT_CEIL(FT_MulFix(face->ascender, scale));
        font->descent        = FT_CEIL(FT_MulFix(face->descender, scale));
        font->height         = FT_CEIL(FT_MulFix(face->ascender - face->descender, scale));
        font->lineskip       = FT_CEIL(FT_MulFix(face->height, scale));
        underline_offset     = FT_FLOOR(FT_MulFix(face->underline_position, scale));
        font->line_thickness = FT_FLOOR(FT_MulFix(face->underline_thickness, scale));
    } else {
        /* Get the font metrics for this font, for the selected size */
        font->ascent         = FT_CEIL(face->size->metrics.ascender);
        font->descent        = FT_CEIL(face->size->metrics.descender);
        font->height         = FT_CEIL(face->size->metrics.height);
        font->lineskip       = FT_CEIL(face->size->metrics.height);
        /* face->underline_position and face->underline_height are only
         * relevant for scalable formats (see freetype.h FT_FaceRec) */
        underline_offset     = font->descent / 2;
        font->line_thickness = 1;
    }

As far as I understand nanovg, nanovg places each character into a small part of a large texture with a one pixel border around it. The actual rasterization is done by FreeType. Specifically here ftError = FT_Load_Glyph(font->font, glyph, FT_LOAD_RENDER | FT_LOAD_FORCE_AUTOHINT | FT_LOAD_TARGET_LIGHT); I would suspect that FT_LOAD_TARGET_LIGHT is the culprit, that's responsible for the visual difference. If it's not, I would start trial and erroring myself to success, as I have no further ideas :)

After omitting FT_LOAD_TARGET_LIGHT, the visual difference still exist,it just make the text sharper.

@mulle-nat Did you get any progress of it?

I am not doing anything. As I wrote in my previous reply, I have no further ideas.

@BusyStudent Were you able to solve the problem ?

@BusyStudent Were you able to solve the problem ?

Yes,I have find the reason,The reason is fontstash didnot handle bearingX and bearingY correctly,
But I still didnot how to patch it by a clear way. It has big difference with SDL_ttf,And there are too many magic number
Here is my code,It works,but dirty
//in fons__getGlyph
	glyph->index = g;
	glyph->x0 = (short)gx;
	glyph->y0 = (short)gy;
	glyph->x1 = (short)(glyph->x0+gw);
	glyph->y1 = (short)(glyph->y0+gh);
	glyph->xadv = (short)(scale * advance * 10.0f);//Why 10.0f
	glyph->xoff = (short)(x0 - pad);
	glyph->yoff = (short)(y0 - pad) - y1;//< Just here

@mulle-nat oh,sorry.It only works on current font... I read the old version of SDL_ttf.
My finnal idea is to add harbuzz to get offset / advance like here

Interesting. I use harfbuzz in my projects, because it improved the looks, but that's about what I know. I didn't think of suggesting it to you, because I see it do better kerning (better spacing in the x-axis), but maybe it also also does y-axis offsets. So your idea sounds worth trying to me. Good luck.

@mulle-nat Did you doing anything? I try to add hb in fonsTextIterInit,but after calling hb_shape. I received an all zero value array in hb_buffer_get_glyph_positions

The way I use harfbuzz is that I am building my own freetype library and define it to use harfbuzz. So in effect, if harfbuzz were to fix your problem, it would be doing so transparently to nanovg by providing better values through freetype.

Fixed,After using my reimplementation of fontstash


not recive Proofs Found

not recive Proofs Found

not recive Proofs Found

What plots do you use?

k32

2021-09-18T02:36:29.531 farmer achi.farmer.farmer         : ERROR    Invalid proof of space {'challenge': '0xfb30dfedd4791ab9a3f97a084281deab32fdfa38e598fc37de64da38cc82631e',
'plot_public_key': '0x8b7007e9258eb63ff39eda8487a0f2600eef3c4de914e8909686e2b28b86321a62ccab94ea80c3db1228a2cecba40fe4',
'pool_contract_puzzle_hash': '0x54a072787f703b03c88ce0a7a481ddc0124d612657a03d5321374bc14588944d',
'pool_public_key': None,
'proof': '0x363ef5669051e74738b95fc2550d5f5626dec4fc4da8ef3314a3726c405c2cdac797a9bc7c0cf34c6ca9bbec46edcd929bfed52540a8779cae51a3a4204dcdd553b2692e7e85c4c8653ed5b98a8ba81f9ba2250a0c0697a43d00754b80cf8d6910094cdabaa2975cfc95a7bcbabf42239009b34bb0db276bd6a99e0f3137944f4bc10c31235cb02fec99693c22dd2cb0fc556a78904a5aaed31d158d9f14142fd60f7af61cb7a70b3824e93aceb03dbeb98d32a6ff0434bc8a9d5a2481c29d541e05343e145f81db22b228f6c464125c0b87af7d5b52495d0accaf5f1b1ce0a496e7eb2a763527fab1bf826bd90c5aeb2f85fa899c0c474a01e059c2f98f9428',
'size': 32}

What plots do you use?

Looks like you are using Chia's plots... Achi plots are incompatible with other PoSp and PoT blockchains. Incompatibility of Achi plots with other blockchains will help Achi to gain maximum decentralization and become an unique cryptocurrency with high long term potential. Please read FAQ https://achicoin.org/faq/


Support for REST API in Gen 2 applications

Is your feature request related to a problem? Please describe.
It seems as though support was dropped for REST APIs in the new Gen2 backends when working with mobile apps. When using amplify_outputs.json to configure my application, I get misconfigurations and crashes (I know the format is correct because it works for my Next.js app).
Describe the solution you'd like
Please add support for REST APIs like you have for other platforms like web.
Example: Next.js support
Describe alternatives you've considered
I am considering building my own support for this by building a custom dispatching layer. However, this is keeping me from migrating to Gen 2 and pushing me to move away from Amplify all together.
Is the feature request related to any of the existing Amplify categories?
API
Additional context
No response

Thank you for submitting the feature request - our team will post updates here.

Hello,
If you are using Gen 1, you may still continue to use it for REST API use cases.
For Gen2, you can still deploy your APIGateway backend following steps here: https://docs.amplify.aws/javascript/build-a-backend/add-aws-services/rest-api/set-up-rest-api/
However, native client libraries currently don't support it. You may use https://github.com/awslabs/aws-sdk-swift directly for REST API use cases


Added Bread & Hearth for Singapore

Added a new cafe for Singapore :D

What's with the power? :)

I don't remember if there's power sockets for the cafe :)

LGTM then. Thanks!


how to display post content in full page?

Hello,
Thank you very much for the theme.
How to display single post content in full page? It is showing in middle now.

To display single post content in full width, you need to adjust the layout and prose styles. Here’s a summary of the solution:
1.	Update the Layout:
Modify BaseLayout.astro to accept a dynamic isSinglePost property. Use w-full max-w-none to make the layout span the full width when isSinglePost is true.
2.	Adjust Post Page Styles:
In src/pages/posts/[...slug].astro, pass isSinglePost={true} to BaseLayout. Update the  class to include prose, ensuring typography optimization while allowing content to scale. Add lg:prose-lg or xl:prose-xl for larger screens if needed.
3.	Optional Tailwind Config Customization:
Modify @tailwindcss/typography in tailwind.config.js to remove default prose width limits by setting maxWidth: "100%" in the typography plugin.
This approach ensures the single post content spans the full page while keeping clean typography.


Set make_edpm_compute_baremetal var

https://github.com/openstack-k8s-operators/install_yamls/pull/320 sets the openstack_runner_img for baremetal edpm deployment.
edpm-ansible baremetal edpm job builds the runner image. we can reuse the built runner image via make_edpm_compute_baremetal var.
It will help to test proper code in the CI.

recheck

recheck

recheck  edpm-ansible-crc-podified-edpm-baremetal

recheck

recheck

recheck

@raukadah Though the jobs are green, I don't think the IMAGE  set with make_edpm_deploy_params makes it to ENV.
{"level":"info","ts":"2023-06-15T06:34:01Z","logger":"openstackansibleee-resource","msg":"OpenStackAnsibleEE defaults initialized","defaults":{"ContainerImageURL":"quay.io/openstack-k8s-operators/openstack-ansibleee-runner:latest"}}
https://logserver.rdoproject.org/91/191/87e5a50e93b4767c58c8f4b2a8f3599875610f1c/github-check/edpm-ansible-crc-podified-edpm-deployment/6097c90/ci-framework-data/logs/edpm/pods/openstack-ansibleee-operator-controller-manager-584ddbc7d77n4rk-logs.txt

recheck

recheck


Cannot add data to map by "browse your files"

I could not upload data using the "browse your files" function. Nothing was loaded after selecting an .csv or .geojson file. It used to work a few weeks earlier. The drag and drop function still works for the same file.

OS: Windows 10
Browser: Chrome
Version: 73.0.3683.103

Are you using kepler.gl/#/demo website or running kepler.gl locally? Can you open your browser console and send us any error you can see?

I am using kepler.gl/#/demo website. I only see two warnings in the Chrome browser console:
bundle.js:131 Global fetch is deprecated and will be unsupported in a future version. Please pass fetch function as option when instantiating dropbox instance: new Dropbox({fetch})
bundle.js:51 This page appears to be missing CSS declarations for Mapbox GL JS, which may cause the map to display incorrectly. Please ensure your page includes mapbox-gl.css, as described in https://www.mapbox.com/mapbox-gl-js/api/.

Thank you. I was able to reproduce the bug. Fix will come out soon.

I have the same question.🧐

This was fixed and release in 1.0.0-1 version


Usage shows 0

What happened:

usage shows as 0 as shown below:
$ pvsadm purge vms --instance-name upstream-core-lon04 --dry-run
I1116 17:36:36.042158   96720 root.go:49] Using an API key from IBMCLOUD_API_KEY environment variable
Usage:
+-----------+--------+------------+------------+---------+------------+-----------------+
| INSTANCES | MEMORY | PROC UNITS | PROCESSORS | STORAGE | STORAGESSD | STORAGESTANDARD |
+-----------+--------+------------+------------+---------+------------+-----------------+
|         0 |      0 |        0.0 |          0 |    0.00 |       0.00 |            0.00 |
+-----------+--------+------------+------------+---------+------------+-----------------+

What you expected to happen:
Shouldn't be 0 considering the vms present in service instance
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

pvsadm version (use pvsadm version):
Environment - On-Prem or IBM PowerVS:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

This data isn't accurate anymore, we may just need to remove this table displaying from the tool, ptal
/assign @KeerthanaAP

@mkumatag why do we need to remove the table, Can we update the table with the proper data?

@mkumatag why do we need to remove the table, Can we update the table with the proper data?

The API used for collecting data is not populating the appropriate data, when I check with the dev team what I got know that the this API is really implemented properly yet, hence thinking about remove the table itself.
Do you mind creating a support ticket for the same and get an official reply from the team and then remove the content if my understanding right!

Sure, will create a support ticket for this.


Implement a quick search box on the homepage for catalogNumber

Similar to the search box present on https://scientific-collections.gbif.org/, put a search box within the hero image that allows the user to search based on catalogNumber. Ideally, if no exact match is found for the catalog number, then search altCatalogNumber, identifier, occurence id, before returning no value.

The UI components will not provide that logic, but you could add an API call yourself to do that logic before linking to the search UI.
If this is a general usecase we could also consider adding a generic ID resolver of a sort. Something in the backend that looks across various combinations and variations to find likely candidate specimens. It would probably be slow though. And probably never be perfect. But it might be good enough that it is useful. I believe Rod Page once did a proof of concept for something similar.

Indeed: https://material-examined.herokuapp.com/?q=BM000944668
I tried with some of your catalog numbers, but those didn't work unfortunately
https://material-examined.herokuapp.com/?q=v241795


Support for property getter/setters, including those with a defined default value

We have a number of cases where a component wants to expose a property whose value is managed by a separate object (which is not a DOM element). The most natural way to implement this is to define a property getter/setter that proxies requests to the other object. It's not clear from the docs whether something like this is supported.
First question: is there some official way of defining a getter/setter like this today?
As it turns out, one can get most of the way there by defining a property in both the properties block and defining a getter/setter with the same name. See http://jsbin.com/yonara/edit. The key bit:
    get foo() { ... },
    set foo(value) { ... },

    properties: {
      foo: String
    }

This works mostly as expected, with one issue: if the proxied object defines a default value for the property, an initial value for the property cannot be set on a component instance in a markup attribute. In the demo, the attempt to set the foo attribute fails:
<test-element foo="bar"></test-element>

If the proxied object is modified to remove the property's default value ("Hello"), then the above markup works.
Digging in a bit, when Polymer is applying attributes to properties, _applyConfig() gets the value of the foo property and inspects to see if the value is defined. It appears that it wants to avoid stomping on values that have already been set since the component was created. However, since the proxied object already defines an initial value for the foo property ("Hello"), _applyConfig will conclude that the property has been set, and fail to apply the attribute as expected.
Second question: any suggestions for working around this?

This would go a long way towards replacing the expression filters and to/from model functionality that was dropped in the move to Polymer 1.0.

+1
Polymer team any updates on this? There seems to be no valid replacement for get() in Polymer 1.0
I can see observer as a possible replacement for set()

The real issue here is that when using getters and setters, there is no way to declare the dependencies of those functions to the observation and databinding system.
You may not need it for this case (you do if you share Thing with any other element or function), but the risk of confusion is very high if users start making getter/setter backed properties that will not update as they expect.
Instead we provide computed properties for the getter use case, and observers for the setter use case.

@azakus Sorry for the late response. Doesn't computedProperties make the property read only ? I also felt computed / observers is the best solution to this problem. Unfortunately they can't be used together while getters setters can!
From the docs:

The value is interpreted as a method name and argument list. The method is invoked to calculate the value whenever any of the argument values changes. Computed properties are always read-only. See Computed properties for more information.

@gaurav21r @azakus I thinking of you because now I'm developing an element with a property that should accept only url string...and a filter applied by a setter would be the perfect solution for this kind of property behavior...I know exists other workarounds...but they still remain workarounds!

In ES6 it is idiomatic to provide getters or static getters for constants, e.g.,
static get DEFAULT_NAME { return 'constant'; }  // static getter
get DEFAULT_NAME { return 'constant'; }  // regular getter
and reference it in several places in the JS. Naturally, one would also want to use this from the template:
[[DEFAULT_NAME]]
The lack of this feature in Polymer this is related to this issue.


youtube-dl-exec needs Python. python 2.7.17 doesn't satisfy the version requirement of >=3.7. You can skip this check passing YOUTUBE_DL_SKIP_PYTHON_CHECK=1

I'm using this package with firebase cloud functions, It is working fine on local host but when I try to deploy , it gives me this error, my machine has python installed with version 3.11.3, but it is still saying that I've version 2.7.17, I'm not ever able to skip python check, Please Help

Hello, can you paste the error stack trace?

And here my python version

Hi, I've tried
YOUTUBE_DL_SKIP_PYTHON_CHECK=1 npm install
But it gives the same error and I've also tried on MacBook. It's is working fine locally but it's only giving this error when I deploy my function on firebase

Sorry but I can't help there; If it's working locally then clearly is a Firebase thing ☹

Ok, I'll try to deploy my node js file somewhere else. BTW thanks for replying


Fixed time stamps I think

Fixes an issue with the time stamps and accounts for nresets > 1 and throws error if nresets < 1. Seems to produce the correct elapsed times and does not truncate after 1 integration as shown in #81 and #80 .

Coverage increased (+24.5%) to 81.427% when pulling 69a439b5eaecca992056b6ba6722b79a96185bfb on hover2pi:resets_issue into 733d67f2ce7ae84dbf375c30cbd0c36b906137a9 on spacetelescope:master.


kuksa-client docker image does not work

> docker run -it amd64/kuksa-client:441558b
Welcome to kuksa viss client 0.1.6

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/kuksa_viss_client/kuksa_viss_client/__main__.py", line 257, in <module>
    sys.exit(main())
  File "/kuksa_viss_client/kuksa_viss_client/__main__.py", line 253, in main
    clientApp = TestClient()
  File "/kuksa_viss_client/kuksa_viss_client/__main__.py", line 108, in __init__
    with open(os.path.join(scriptDir, 'logo'), 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/kuksa_viss_client/kuksa_viss_client/logo'

We need more tests 😭

totally agree, plan it pls!
Tested on my pc, it works, but on jenkins produced containers do not work!


Boilerplate: Update to 2a6a579ee07b3df9809fe696606f1138154b4e04

Conventions:

openshift/golang-osd-operator: Update

https://github.com/openshift/boilerplate/compare/b81a6aa09228cdea486c7700fa67a4096509987c...2a6a579ee07b3df9809fe696606f1138154b4e04
commit: 1c13a6d23ef92603bbae32d5fb8f543789fc579c
author: Christoph Blecker
Update image tag in test files
commit: 4d1f8a2678f70f7c64c0ae16800049e3feee64cc
author: Christoph Blecker
Update build_image script to work with RHEL8/go1.17
commit:<PHONE_NUMBER>9339ecb2f9d5d5ff7df0f43b159776
author: Christoph Blecker
Switch to RHEL8 builder image
commit: 03deceeda6b7b39b22e4eae06d59de78e5fdbbf0
author: Eric Fried
Update README for image tagging quirks
Clarify a couple of things in the README wrt image tagging:

You have to push the new tag to your origin as well as upstream.
You have to edit the tag in a couple of in-repo files as well.

commit: b1c28646013edcecdcc7ab0631bd43c3183184b4
author: Eric Fried
Fix broken link in README
The release repo moved the file where we import our backing image.
commit: 35c3064256d88136a6eaa75ced0660a7426d3c70
author: Eric Fried
Remove support for hack/generate-operator-bundle.py
Support for using a "local" (within the consuming repo)
hack/generate-operator-bundle.py script was included as a bridge while
consumers were cutting over to use the common bundle generator. That has
happened. Get rid of the old script, make targets, and support.
commit: 5f249984fba668d090b3ee2194dd0e98e506d43c
author: Ron Green
fix(CONTAINER_ENGINE): allow setting the env
after #201 didn't work, I updated it a bit
now you can set the env and it's not overriden
What type of PR is this?
(bug/feature/cleanup/documentation/test/refactor)
What this PR does / why we need it?
Which Jira/Github issue(s) this PR fixes?
Fixes #
Special notes for your reviewer:
Pre-checks (if applicable):

[ ] Tested latest changes against a cluster
[ ] Ran make generate command locally to validate code changes
[ ] Included documentation changes with PR

Codecov Report

Merging #41 (87fa9d4) into master (608a6f5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #41   +/-   ##
=======================================
  Coverage   61.74%   61.74%
=======================================
  Files          22       22
  Lines        1132     1132
=======================================
  Hits          699      699
  Misses        375      375
  Partials       58       58

/approve

/lgtm


Exclude node_modules from js loaders

Probably a good idea to exclude js files in node_modules from being run through loaders.

@Shraymonks thank you!


Issue with Preact throwing an error

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
No error should be thrown.
Current Behavior 😯
An error is thrown.
Context 🔦
https://github.com/developit/preact/issues/1293

No error should be thrown.No error should be thrown.

It should. We declared it in our public API: https://material-ui.com/api/modal/#props
Does preact not validate propTypes? Please include the code that triggered this error.

Given the discussion on preact side, I think that it's safe to close the issue. It would be great to add an example with preact.


Expand connector property metadata

The existing endpoint for exposing connector medata should also return for each property the information about:

required (boolean)
category (string or enum?)
allowed values for enums (list of values)

see #55


Fix bridge /healthcheck endpoint

Remove rejected from perf report when there is conflict (409)

Coverage increased (+4.8%) to 90.893% when pulling 1611e699e0fb23b5ba7e2fbace2fd1c12cdfa66e on SAP:fix_bridge_monitoring into edc077379bcfac5aed683244d1fd0572d63cc4e6 on cloudfoundry-incubator:master.


UC protected project being returned in list of admin projects even if the admin is not a member of the UC

Steps:

Admin with UC user_tag creates a UC protected project
Remove UC user_tag from database
Reload admin landing page, UC protected project is still shown in the list

see #2209


Question: Lolipop support

Is full Lollipop support planned?
Currently. one cannot move system apps in Lollipop.

I don't know how to get the other way round working - if you do, feel free to contribute to the project

I usually do that manually by moving stuff from /system/app or /system/priv-app to /data/app. Is there a barrier in doing this with Lollipop? Is it because the multiple users thing?

I don't know what exactly the issue was (I don't have any rooted Lollipop device any more), but I know that it didn't work at that time

As far as I know it is now filders moved between /system[/] and /data/app[/] but I have had little luck myself so there is something missing from my understanding in some cases

j4velinSystemaAppMover#10


Breakpoints reordering randomly

I added a breakpoint on the line and another on some column. Then I started typing (in a different file) and the breakpoints flip around on each keystroke. Not in debug mode.

Good catch.
The issue was that breakpoint were flipping location in the sorter if one breakpoint had the column and the other not.


Demo rhel9

Replaced by https://github.com/ome/prod-playbooks/pull/379
Adding only the demo-server playbook. The tests are minimal, basically just syntax. Could not make the full test work.
@jburel I had the demo-server playbook already in prep, I just forgot about it when we discussed.
Happy to add the training-server playbook too.

I am not getting forward here, because of
Molecule ome-demoserver > syntax
  Warning: : Invalid characters were found in group names but not replaced, use
  -vvvv to see details
  ERROR! the role 'ome.postgresql' was not found in /home/runner/work/prod-playbooks/prod-playbooks/roles:/home/runner/.cache/molecule/prod-playbooks/ome-demoserver/roles:/home/runner/work/prod-playbooks:/home/runner/.ansible/roles:/usr/share/ansible/roles:/etc/ansible/roles:/home/runner/work/prod-playbooks/prod-playbooks
  The error appears to be in '/home/runner/work/prod-playbooks/prod-playbooks/ome-demoserver.yml': line 101, column 7, but may
  be elsewhere in the file depending on the exact syntax problem.
  The offending line appears to be:
      - role: ome.postgresql

This error ^^^ can be solved if I commit the whole roles folder to this PR. I genuinely do not understand where the roles are installed in the GHA and why the subsequent syntax does not find them.
any ideas please @sbesson @khaledk2 ?

Replaced by https://github.com/ome/prod-playbooks/pull/379 - sorry for the noise.


Split the Context class

This is part of the new C++ API serie #131
A Data_Store class similar to a map<string, Data_descriptor> should be extracted from the Context and made accessible by a data() member function.
A types() member function should provide access to a map<string, Datatype_template>&
This issue is only about splitting the class, not making any change to them.

unassigned @tpaluszk


double click on error line.

Allow to jump  to error line by double-click on the error line message (or by pressing F4)
(see "closed issues" for more information)

Good idea!


i18n: update chinese (traditional) translation

Issue: #584

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.

[x]  issue was opened to discuss proposed changes before starting implementation.
[x]  during development, node version specified in package.json was used (ie using nvm).
[x]  package versions and package-lock.json were not changed (npm install --no-save).
[x]  app version number was not changed.
[x]  all new code has tests to ensure against regressions.
[x] npm run lint reports no offenses.
[ ] npm run test is error-free.
[x]  README and CHANGELOG were updated accordingly.

Description of the Change
Update Chinese (Traditional) translation for stretchly (redesigned).

Verification Process

Other information

k
v

glossary
stretchly-glossary-0519.zip

@hovancik It appears like something wrong when I ran npm run test.
Looks like this isn't from me.
  85 passing (55s)
  1 failing

  1) UntilMorning
       Default Settings
         loadMorningTime() returns morning time:

      AssertionError: expected 22 to equal -2
      + expected - actual

      -22
      +-2

      at Context.<anonymous> (test/untilMorning.js:52:76)
      at processImmediate (internal/timers.js:456:21)
      at process.topLevelDomainCallback (domain.js:137:15)

@pan93412 you can ignore this error, for some reason this test only works in CI

@hovancik Ok you can merge it

@pan93412 let me check the changes, because github shows CZ and SK were changes as well


Proposal to use std::constructible_from in str_t to support objects with explicit conversion to string_view

Hi,
Thanks for the great library!
We have some strong types which wraps std::string. These provide explicit operator std::string_view(); However if this type is a key in a json dictionary, it will have extra quotes pre/appended to it (Foo{"hello"} -> "\"hello\"").
We traced the code to:
template <opts Opts, class Key, class Value, is_context Ctx>
GLZ_ALWAYS_INLINE void write_pair_content(const Key& key, Value&& value, Ctx& ctx, auto&&... args)
{
   if constexpr (str_t<Key> || char_t<Key> || glaze_enum_t<Key> || Opts.quoted_num) {
      write<JSON>::op<Opts>(key, ctx, args...);
   }
   else {
      write<JSON>::op<opt_false<Opts, &opts::raw_string>>(quoted_t<const Key>{key}, ctx, args...);
   }
...

and the definition of str_t to
template <class T>
concept str_t = (!std::same_as<std::nullptr_t, T> && std::convertible_to<std::decay_t<T>, std::string_view>) ||
                array_char_t<T>;

Due to our class not being implicitly convertible to string_view, we end up in the else block, getting the key quoted.
Would it be possible to use the std::constructible_from<std::string_view, T> instead of the std::convertible_to in the str_t definition, as it would allow structs with explicit conversions to also function as keys without quotes?
Godbolt example of the concepts: https://godbolt.org/z/KbKa8nY7c
Might be related to #1477 but the proposed solution is a bit different.

Thanks for suggesting this. I made the change and merged it in (#1486). Everything passes and I think it is a logical request.

Thanks!


[Android] Authentication works on some android devices but not redirecring back to my flutter app after complete authentication on othet devices

Issue:
We are trying to request  a connection from flutter app to another application. This requires receiving a response from the third party application. but our flutter app keeps relaunching just before receiving the response. However, it works as expected on some devices while on other devices the issue persist.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.3, on macOS 14.1 23B74 darwin-x64, locale en-NG)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.94.0)
[✓] Connected device (3 available)
! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with the
same local area network as this Mac.
The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources
Working on and Android device
https://github.com/user-attachments/assets/2319cadd-41ae-4f31-971d-ba06c7f0571d
In this case , when the auth is completed, it's relaunching the app rather than to continue from where it was before auth
https://github.com/user-attachments/assets/9d219ec6-f416-49e7-99ae-b23956b49b23

Hey @Mubaola23 can you please confirm the details of the second device? Also, it looked like the network connectivity was slow in the second video since it took a lot of time to complete the authentication?

Any update? I am facing same issue


CLI 6: Ability to customize minifier configuration

With CLI 1.x I could ng eject and have a script modify the ejected configuration, but after updating to 6.0.0-rc.7 it seems that's no longer an option. Is there a recommended new way to do this, or would it be possible to have a way added to angular.json?
Alternatively, is eject expected to return any time soon (like before the final v6 release)?
(This is a blocker for upgrading to Angular 6 because we need the ability to provide a list of mangle exceptions to uglify.)

Got it, thanks.

For anyone else with the same issue, just patching node_modules/uglifyjs-webpack-plugin/dist/uglify/minify.js seems to do the job for now.


Update fetal anomaly to fetal diagnosis

Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.

What are we trying to do? @KatSDC is making some clutch edits to special circumstances. Because we're a production system, we're going to want to update what's already in our prod db.

What feature or behavior is this required for? Completing the job in #776

How should we solve this issue? By running a quick one-liner as follows in rails console:

Patient.where(special_circumstances: 'Fetal anomaly').each { |pt| pt.update special_circumstances: pt.special_circumstances.map { |circ| circ.gsub(/Fetal anomaly/, 'Fetal diagnosis') } }

In a nutshell: Find people who have a circumstance Fetal anomaly, sub out for Fetal diagnosis, resave to special circumstances.
I'll be running this as part of our scheduled deployment on 1/1.

Ran this in prod - closing.

Ran this in prod - closing.


Exercise 57: metaphor issue - the bee doesn't die!

Only ant can be .still_alive = true. 🤣
https://youtu.be/_5YbPhOFC20?t=1682

@unional Ha ha, you're right. :rofl:  :bee: :ant:
I should have the ants store something a bee wouldn't have!

Ants collect milk from aphids, for example. To do this, they hold them similar to a sheep herd. So one possibility would be the ant remembers on which leaf it was already during the day.


Add content-type header = application/json for create and update actions

Following PR  Split codec from scheme #17922 on k8s server.
cc @simon3z

@abonas I think that post and put support :content_type in the request. E.g.
rest_client[ns_prefix + resource_name(entity_type)].post(hash.to_json, @headers, :content_type => 'application/json')

It looks just slightly better (because closer to the to_json transformation), but I don't know if it works.
(Not sure if it's worth investigating, up to you)
Should we do something for what format we expect in the response? E.g. passing the Accept: application/json header to be sure to receive json?

@abonas I think that post and put support :content_type in the request. E.g.
rest_client[ns_prefix + resource_name(entity_type)].post(hash.to_json, @headers, :content_type => 'application/json')
It looks just slightly better (because closer to the to_json transformation), but I don't know if it works.
(Not sure if it's worth investigating, up to you)

I thought about it too, saw some examples that use it. What bothered me is that eventually content type is a header, and there is already a headers object passed. Differentiating it can confuse the reader since it will create 2 different ways of passing headers.
Thoughts?

Should we do something for what format we expect in the response? E.g. passing the Accept: application/json header to be sure to receive json?

It does work without passing Accept, and I remember there were some exceptions that were sent in response as text instead of json from k8s server ( a bug, but still...) , so passing Accept can actually prevent the client from getting an exception from the server.
So I tend to say not to send Accept at the moment.

OK :+1:


Rough animation for camera to "focus" on object

@PWhiddy
@bellenot
Looks very good!
Seems to be, one should update OrbitControl with new camera position.

Thanks! Hm yes updating orbits focus didn't seem to be enough


Add stretching of modules and  modules-center toggling

This Patch allows the stretching of modules-{left,center,right} as well add a "expand" flag to AModule. This allows one module to consume the leftover space.
To allow the left or right modules to fully consume the center, the changes also include a way to remove the center box (center_) altogether.
This is useful for use-cases like: https://github.com/Alexays/Waybar/issues/1561

Any Interest in looking at this? The 51 come from touching nearly all man pages.
One point to discuss, should this PR be considered, would be whether the script should execute before or after the format resolving.


Delete Profile Not Working for Onedrive Synced Profiles

When a profile has it's onedrive synced to the machine the user profile folder and all of their onedrive contents remain after the autodeletion/maintenance occurs.
Everything else gets deleted, but the onedrive folder remains inside the user folder. So the user folder remains as well.

@brockettc. Sir will you mention the content source , from where you read

@RAJU2529 https://docs.microsoft.com/en-us/windows/configuration/set-up-shared-or-guest-pc
AccountManagement:DeletionPolicy

Hello, @brockettc thank you for providing feedback.
The issues section of this repository is intended for product documentation issues only.
Please consider opening a product support ticket by the following link below for your problem so that it gets resolved quickly.
Windows 10 Support
Thank you.


fix: renamed numpy_batch to numpy_sample throughout the codebase

Pull Request
Description
This pull request renames the numpy_batch folder to numpy_sample because we only deal with samples, not batches. All relevant references and imports have been updated to reflect this change. The modification aligns the naming convention with the actual functionality for better clarity and consistency.
Fixes #103
How Has This Been Tested?

Ran unit tests to verify functionality after renaming the directory.

Checked all imports and ensured there were no unresolved references.

Verified that the application runs without errors after the changes.

[x] Yes

The renaming does not change the logic of data processing, but it does ensure the terminology accurately reflects the operations being performed. I have verified that it runs successfully after the changes, ensuring there is no disruption in functionality.

[x] Yes

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code.
[x] I have made corresponding changes to the documentation.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] I have checked my code and corrected any misspellings.

Thanks so much @Tim1119 for doing this and jumping on this so quickly

Thanks so much @Tim1119 for doing this and jumping on this so quickly

You're welcome

Thank you for the suggestions @felix-e-h-p . I'll implement the changes, refactoring the function into modular helpers as recommended while ensuring the core behavior and tests remain the same.


Add effect for Ray of Enfeeblement

I think we should wait before doing container effects that only apply conditions. I know we have a few in already but I'd really like to find a solution that doesn't involve making a ton of new effects. This one may end up being on the edge of it because of the ChoiceSet but if we could do something akin to what extempore effects does (but with automation) then we could shortcut needing this at all.


[Bug] Binding only works when user click on JS  option for Default Date property on Datepicker widget and then binds

Description: There is no error when user bind the Default Date property on Datepicker without clicking JS option

In Date picker we do not accept JS query without clicking on the JS option
Expected Behaviour: If it’s input field then by default it should accept JS query without having JS option.

@vivekverma2312 it's not an input field right? It's actually a date selector field

@vivekverma2312 IIUC the behaviour is correct here, When JS is not enabled the user can see the datepicker popup and otherwise and enter the expression to be evaluated. Closing this for now, Please reopen if required


add bool to enable speech input

Motivation and Context
Hide the speech input if it hasn't been enabled in the .env file;
This prevents an invalid key and/or the lack of a key for a speech resource from generating an error when it's not present.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

in the last conversations we had about Azure Speech we said we would automatically turn it on/off, without asking the user to do extra work

Sorry, that was my recommendation without knowing the past conversation. Thanks for the push and I do like the latest change which has less asks on the user side.

thanks @amsacha <3


Adding auth networks

I am running truenas SCALE is on a different network then the k8s cluster.
When this looks up the ip of truenas to generate the auth network, it doesn't take into account that cluster is elsewhere.
Would it be possible to add an argument to specify alternative auth networks?

Hi, thanks for filing this issue. This is fixable for sure. We're a bit narrow-minded in storage assuming that iSCSI traffic is supposed to reside on a flat L2 network. This will most likely be implemented as a StorageClass parameter to use node based auth networks and not array based.
Or would you like to hardcode CIDR networks in the StorageClass?

I believe either solution would resolve the issue. Allowing to add a cidr directly is possibly the most flexible solution, as you never know what other weird network setups you may find.

+1
Hardcoded CIDR is also fine in my use case.

I took a look here and it was not as easy as I thought. For TrueNAS SCALE the auth_networks are set on the target during volume publication. This means that the StorageClass parameters are not available in this request.
The only way I can implement this without breaking all sorts of boundaries is to allow users to hardcode CIDRs in the Helm chart. The auth_networks are then "global" for the TrueNAS CSP running on the cluster. This should be fine in most cases as the data networks are usually somewhat uniform. It could however open up for other problems as you need to specify an entire subnet.
Since CHAP will most likely be introduced in the next version after v2.4.2 I think it would be safe enough to hardcode subnets in auth_networks during install and use CHAP for authorization.
Thoughts?


Add rounded cube primitive

Such polygons, much smooth! #141

There is an algorithm here that you could take inspiration from.

Thats pretty neat

I suppose that could be used as a bevel feature?

I wonder if it works well with just one segment.

https://catlikecoding.com/unity/tutorials/rounded-cube/

I would like to try my hand on this.
Already started reading related code.

I created #160 specifically to deal with this PR. You can now chamfer a cube into smithereens.
PolygonFactory:
bool ChamferPolygons(List<Polygon> polygons, List<Edge> edges, float distance, int iterations, out List<Polygon> resultPolygons)

Now that this method is available it should be a lot easier to build this primitive type. The advantage over just chamfering manually is that the size of the edges will remain consistent with the bounds tool... maybe. I found #141 to be quite a challenge.
We have to make some fundamental changes to how SabreCSG tells brushes about invalidations because not every call to Invalidate() is an appropriate moment to update our geometry (like a position change, which causes movement to slow down to a stuttering crawl). It would be great to add another argument like this:
void Invalidate(bool polygonsChanged, InvalidateReason reason)

Then any reasons can inherit from the base abstract class InvalidateReason and possibly even provide additional information through public properties. This is a lot more future-proof than an enum reason as we may run out of flags.


Bug Report

Describe the bug
I can use mly.interface.images_in_bbox in api colab, however, when I try to use this api on my local machine,it returns  HTTPSConnectionPool(host='tiles.mapillary.com', port=443): Max retries exceeded with url.  Perhaps Chinese ban the port or any other reason?
Colab demo result

To Reproduce
local machine result.

Screenshots

To Reproduce
local machine code
import mapillary as mly
import geopandas as gpd
import os
import requests
headers = {'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/81.0.4044.138 Safari/537.36'}
os.environ['HTTP_PROXY'] = 'http://<IP_ADDRESS>:33210'
os.environ['HTTPS_PROXY'] = 'http://<IP_ADDRESS>:33210'
mly.interface.set_access_token('MLY|5175886149161658|4099af83a040b4c64a3891bdcc8314cf')
region_dict =  {
     'west': 8.97291281111626,
     'south': 35.35651235634347,
     'east': 9.09945112532228,
     'north': 35.460110419672326
}
result = mly.interface.images_in_bbox(test_dict)

colab demo
import mapillary as mly
import geopandas as gpd
import os
import requests
mly.interface.set_access_token('MLY|5175886149161658|4099af83a040b4c64a3891bdcc8314cf')
region_dict =  {
     'west': 8.97291281111626,
     'south': 35.35651235634347,
     'east': 9.09945112532228,
     'north': 35.460110419672326
}
result = mly.interface.images_in_bbox(region_dict)

Your local machine's internet access blocks your request and thus your connection with the API service, hence the 443 error.
Using the os.environ variables as you have set don't really have much impact. In the end, the local network address you are on is <IP_ADDRESS>. It is rather the internet service you are connected to that does not let your machine send a request to the API service. Nothing to be fixed via the code here.


Images not created for new topographies

With the current setup it often happens that images are not created for new topographies.
This should be fixed with #787 and #802.

Should have been fixed by #802.


Using Stryker with a MeteorJS project

I'm working with Meteor, testing with Mocha, and would really love to use Stryker.
Problem is, since Stryker is its own runner, it won't find any Meteor packages (or so it seems):
(function (exports, require, module, __filename, __dirname) { import {HTTP} from 'meteor/http';
                                                              ^^^^^^
SyntaxError: Unexpected token import
    at createScript (vm.js:56:10)
    at Object.runInThisContext (vm.js:97:10)
    at Module._compile (module.js:542:28)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at /Project/node_modules/mocha/lib/mocha.js:231:27
[2017-11-21 07:22:12.750] [ERROR] StrykerCli - an error occurred Error: Something went wrong in the initial test run

Any ideas on how to make it work?

Hi @aviadbd , thanks reporting this issue.
Could you provide is with some more information? I've never used Meteor myself, could you explain how your build process works? I'm assuming that this line of code import {HTTP} from 'meteor/http'; comes from your code somewhere. NodeJS does not support import statements yet, so what kind of transpiler are you using? Babel? Webpack?

Ok, but the tests are clearly running on plain node, seeing the nodejs function wrapper siganture here: (function (exports, require, module, __filename, __dirname) . It seems to me that meteor doesn't use the mocha test runner, but something like karma instead. Can you confirm this? Could you maybe provide a small test project for us that looks like your application (meteor + es6 + a way to run the tests)?

Maybe I didn't explain well?
When I run tests using Meteor, it complies (transpiles?) the sources correctly and then uses a test driver to run the tests. It can use many test drivers packaged for the task, specifically I use Mocha.
Please see a great example as the Todos App, at https://github.com/meteor/todos/ .
An example test, using Mocha and Chai (the recommended setup at Meteor's own site), could be found here: https://github.com/meteor/todos/blob/master/imports/api/lists/server/lists.tests.js

Ok, thanks for your additional explanation. I want to take a closer look when i get some time (which is hopefully by the end of this week). For the time being, you could try to run stryker on the intermediary files that meteor transpiles for you.
Basically what needs to happen is that every mutation to the source file gets transpiled by stryker using meteor (or whatever bundler meteor internally uses).

I'm not sure that's actually possible, as I'm not sure the transpiled project keeps the same structure of the original project; therefore, choosing the files to mutate might prove hard.
I can wait a week or two. Please tell me if you want me to check something.

@aviadbd Could you see what happens if you use https://www.npmjs.com/package/stryker-javascript-mutator in the project? (This probably won't mean we support your project. I'm just curious what happens)

@simondel  I'm trying to understand why it would be any different; its still running on code that has dependencies that can't be found (the Meteor dependencies). Am I wrong?

We have decided that we won't focus on building Meteor support. Would you be willing to build this yourself or shall we close this issue?

Hey Guys,
Found a solution by mocking the Meteor Framework :)
I created a repo for this.
You can check it out at https://github.com/gugacavalieri/stryker-meteor-integration
Many thanks to https://github.com/pcorey/unit-testing-with-testdouble

@gugacavalieri awesome you were able to pull it off! I see you're trying to setup the mutation score badge. If you're having trouble with it, please don't hesitate to drop us a line at gitter: https://gitter.im/stryker-mutator/stryker

@nicojs Thanks ! Will check again why it is not rendering and let you know :smile:

As a workaround is available, I'm closing this issue for now.


Fix issues in help text

Purpose
$title.
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/20409
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/20410

Codecov Report

Merging #20422 into release-stage will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           release-stage   #20422   +/-   ##
==============================================
  Coverage          15.21%   15.21%
==============================================
  Files                 50       50
  Lines               1341     1341
  Branches             208      208
==============================================
  Hits                 204      204
  Misses              1121     1121
  Partials              16       16

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 d6cafd4...2a761b8. Read the comment docs.


Memory issues when using tarFileAtPath

It seems that using file system methods should ensure that things are chunked to avoid memory issues, however when taring a 1.5GB file using tarFileAtPath I get a huge memory spike up to 500MB+ and then a resulting crash. compressFileAtPath also causes this issue. Pretty sure that shouldn't happen so wanted to report it. Any ideas?

Well.. the memory spike is no surprise. We have to handle the data in-memory.
Any details on the crash? A crash log or stack trace would help.

It should be a surprise! As mentioned in my issue I use file system methods, and the docs state manages memory properly to support large files. So it shouldn't handle all the date in-memory.
I've not got any traces available unfortunately as I had to use another library pretty quickly. So I just want to inform the author there are memory issues and can be repro'd if you use the above methods with a 1.5GB directory.

Indeed. What the readme really means to say is that you shouldn't try to keep all files in memory.
But when you're creating the tarfile, they are copied in memory either way.
So you're right. That is wrong.
I've already changed the code so that it writes the tar file in chunks, but I have to test it and also figure out what the performance impact is. Might need to tweak the code a little bit...

Please give this a try and see whether it really works. I cleaned up the whole memory situation a bit so hopefully it's more efficient now :)

@drallgood thanks for the PR and looking into it. I'll try and test it out with a large file too when I get a moment, been having trouble keeping up with Open Source stuff lately :cry:.

@mwaterfall Can you please help me with the name of another library you used to zip/unzip tar files?


Cannot catch nested token

Describe the bug
  auth_token:
    source: !request
      recipe: get_token
    selector: $.data.token
    #selector: $['data']['token']

Cannot catch the token inside the response under data
{
  "data": {
    "token": "eyJ0eX.vbsgsdg.ddsfd"
  },
  "success": true
}

To Reproduce
Steps to reproduce the behavior

Clone my repo: git clone git@github.com:AuroraLantean/axum-jwt.git

Expected behavior
Compile and run the Axum server:
cargo run --bin axum-auth

Install Slumber:
https://slumber.lucaspickering.me/
See the slumber.yml file in the root directory...
Run Slumber commands:
$ slumber then use the UI to run APIs
OR
$ slumber request -p local public_view | jq

$ slumber request -p local get_token | jq
{
  "data": {
    "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJlbWFpbCI6ImpvaG5kb2VAZ21haWwuY29tIiwiZXhwIjoxNzE3MTc0MTg5fQ.CmJoHeHBT_fi-VMBgoVjaXEN_dV1CNlxHSbP7X9md2Y"
  },
  "success": true
}

$ slumber request -p local secret_view | jq
{
  "data": {
    "message": "No token provided"
  },
  "success": false
}

Screenshots
Version (please complete the following information):

OS: LinuxMint  21.3 Virginia, based on: Ubuntu 22.04 jammy
Terminal: Zsh
Slumber Version:  slumber 1.3.2

My bad... I made a mistake using Slumber...
Docs: https://slumber.lucaspickering.me/book/api/request_collection/authentication.html
For Jwt tokens, I would really suggest you put an example in your doc like:
  #slumber request -p local secret_view | jq
  secret_view: !request
    method: GET
    url: "{{host}}/secret-view"
    authentication:
      !bearer "{{chains.auth_token}}"

@AuroraLantean Glad you figured it out, and thanks for the suggestion. Where in the docs would you want to find this? I'm always looking to improve the docs.

@LucasPickering could you put an example here: https://slumber.lucaspickering.me/book/api/request_collection/authentication.html ?


Update extend-data-volume.md

Updating article to remove unsupported OS versions and instructions for shrinking a Windows partition
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

@jeffhughes-msft The changes will be live. This PR will be closed.


add create mask, directory mask, force user and writable configs

non-mandatory configurations that help in the configuration of some environments and allow the writing of guest users(https://github.com/crazy-max/docker-samba/issues/56)

Please update readme, thanks.

What about this pull request? Will it be merged?

The entry point adjustment doesn't work the way I expected, it turned out to be a false correction and I canceled the PR.
For my need Im using dperson/samba.


Remove lazyConnect from Cluster redisOptions

It is already being set by the cluster to true and there is no way to override it: https://github.com/luin/ioredis/blob/main/lib/cluster/ConnectionPool.ts#L84

lazyConnect is actually supported (though I can't recall why we want to allow that) since this.redisOptions overrides { lazyConnect: true } given how _.defaults works.


Textbox Control - Multi-line Support

Can multi-line support be added to the textbox control, so that pressing return inserts a new line?
The control is already capable of displaying multiple lines if you populate the Text property - but editing does not work well as you cannot navigate beyond the first line:

I think the problem is here: https://github.com/LokiMidgard/NSCI/blob/a4a96cbf4f2d3600accf7a34ed6fec898d5a261b/NSCI/UI/Controls/TextBox.cs#L62
Also if the textbox would be to small for the text (including single line) I think it will also be rendered wrong.
I won't get to work on this project this week, and I'm not sure if I can make it next week.
Sorry for the delay.


touying:0.5.3

I am submitting

[ ] a new package
[x] an update for a package

Description:
Features

feat: add strecth parameter for #alternatives[] function class. This allows us to handle cases where the internal element is a context expression.
feat: add config-common(align-enum-marker-with-baseline: true) for aligning the enum marker with the baseline.
feat: add linebreaks option to components.mini-slides. https://github.com/touying-typ/touying/pull/96
feat: add <touying:skip> label to skip a new-section-slide.
feat: add config-common(show-hide-set-list-marker-none: true) to make the markers of list and enum invisible after #pause.
feat: add config-common(bibliography-as-footnote: bibliography(title: none, "ref.bib")) to display the bibliography in footnotes.
refactor: add config-common(show-strong-with-alert: true) configuration to display strong text with an alert. (small breaking change for some themes)
refactor: refactor display-current-heading for preserving heading style in title and subtitle. https://github.com/touying-typ/touying/issues/71
refactor: make new-section-slide-fn function class can receive body parameter. We can use receive-body-for-new-section-slide-fn to control it. (Breaking change)

For example, you can add #speaker-note[] for a new section slide, like = Section Title \ #speaker-note[].
If you don't want to append content to the body of the new section slide, you can use --- after the section title.

Fixes

fix outdated documentation.
fix bug of enable-frozen-states-and-counters in handout mode.
fix unusable square() function. https://github.com/touying-typ/touying/issues/73
fix hidden footer for show-notes-on-second-screen: bottom. https://github.com/touying-typ/touying/issues/89
fix metadata element in table cells. https://github.com/touying-typ/touying/issues/77 https://github.com/touying-typ/touying/issues/95
fix auto-offset-for-heading to false by default.
fix uncover/only hides more content than it should. https://github.com/touying-typ/touying/issues/85
theme(simple): fix wrong title and subtitle. https://github.com/touying-typ/touying/issues/70

Thanks!

@elegaanz Could we possibly add a checkbox in the pull request template for checking for correct semantic versioning? This package update contains a breaking change which is even listed in the changelog but the update is a patch: 0.5.2 -> 0.5.3.

@elegaanz Could we possibly add a checkbox in the pull request template for checking for correct semantic versioning? This package update contains a breaking change which is even listed in the changelog but the update is a patch: 0.5.2 -> 0.5.3.

Thanks for the comments. Every version of touying basically contains more or less breaking changes, and it is difficult to determine whether a version is a patch or not. My current strategy is that if there's only one or so breaking changes, then I'm not going to add a major version. If you have a better idea, welcome to discuss.

Is there a particular reason why it is undesirable to just make it 0.6.0? I don't see the downside of this, and it has the advantage that I know when it is save to upgrade. I came across this because I updated from 0.5.2 to 0.5.3 only to find a huge number of my slides were broken, but the idea of semantic versioning is that the version number should tell me if that is going to happen.

Okay, that's probably just a difference in perception. Because every update of Touying brings a bit of a breaking update, if you add a major version whenever there is a breaking update (no matter how big or small), the last bit of the version number will not be used at all, that is, every update will not be compatible. I was thinking about whether this version should be called 0.6.0, but in the end I didn't think it was a major refactoring update like 0.5.0, so I ended up just calling it 0.5.3.
I think it's a compatible version with only a small number of users need a few changes. For example, touying's example doesn't encourage you to write the slide content directly under a first-level heading, but rather encourages you to create a second-level heading that users won't run into a breaking change if they follow the examples. Even if you encounter this breaking change, I think you only need to add some --- marks to solve it, so it's an easy breaking change to deal with, and it doesn't involve too many changes.

Technically, when you are on the 0.x.y series, semantic versioning does not really have any rules, anything can break at any time.
Still, it is possible to add this checkbox to the PR template. However, in general it is quite hard for reviewers to check that semver is indeed respected: you would have to diff the two versions and understand how the package works, which is just too time consuming. So the checkbox would really just be a reminder for package authors.

@OrangeX4 Thanks for the reply! I don't personally agree but your position is totally fair enough, and perfectly reasonable. While I've got you here thanks for touying btw, I just gave a talk yesterday with slides made using it and it was a joy to use!

@elegaanz That is precisely why I think it would be a good idea to have such a checkbox (independent of my position on this particular instance and major version zero), because it is so difficult to actually verify as a reviewer. Up to you though!


Missing required parameter: client_id

Hi!
I'm facing an issue that I don't understand!
I am developing a react-native (js) app which try to access Spotify api using the Implicit Grant Flow.
Here is my method to get the access token:
async function getTokenFromAPI() {
    try {
        var params = {
            client_id: '<client_id>',
            response_type: 'token',
            redirect_uri: 'http://localhost:8888/callback'
        };

        var esc = encodeURIComponent;
        var query = Object.keys(params)
            .map(k => `${esc(k)}=${esc(params[k])}`)
            .join('&');

        fetch('https://accounts.spotify.com/authorize', query).then(function (response) {
            console.log('response, ' + JSON.stringify(response));
            return response;
        })
    } catch(error) {
        console.error(error);
    }
}

but It answers that:
Missing required parameter: client_id
I also used Postman to check if my request is good and I get the same response...
Is there something wrong? On there doc they tell that it is a GET method with only 3 parameters..
Thank you in advance for any workaround!

I think the problem is with the fetch call. You most likely want to write
fetch('https://accounts.spotify.com/authorize?' + query)

I'm closing this issue as it's not related with the library.


chore: test whether circleci works

What was wrong?
TODO
How was it fixed?
TODO
To-Do

[ ] Clean up commit history and use conventional commits.

CI passes again when re-running, so whatever was causing the problem seems to have been transient. Since I can't identify the exact cause, I don't have any ideas for preventing it in the future. I'll at least look around for PRs that need to have CI restarted.


Regression in commits from dec 24

Packet capture: (can filter by bootp and open in wireshark) (see packets 50 and 51)
wireshark.zip
Pixiecore log:
[DHCP] Offering to boot 08:00:27:4e:15:86
[DHCP] Offering to boot 08:00:27:4e:15:86
[DHCP] Offering to boot 08:00:27:4e:15:86
^[[24~[DHCP] Offering to boot 08:00:27:4e:15:86
[DHCP] Offering to boot 08:00:27:4e:15:86
[DHCP] Offering to boot 08:00:27:4e:15:86
[DHCP] Offering to boot 08:00:27:4e:15:86
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[TFTP] Sent "4c:cc:6a:ce:90:8c/7" to <IP_ADDRESS>:1821
[TFTP] Sent "4c:cc:6a:ce:90:8c/7" to <IP_ADDRESS>:1822
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c
[TFTP] Sent "4c:cc:6a:ce:90:8c/7" to <IP_ADDRESS>:1823
[TFTP] Sent "4c:cc:6a:ce:90:8c/7" to <IP_ADDRESS>:1824
[DHCP] Offering to boot 4c:cc:6a:ce:90:8c

Machine boot log: note: I think that this is unrelated to #51 because it happens on physical and virtual hardware alike.

We were able to solve this by moving back to a pixiecore built on December 17.  Next I'm going to build the bug-51 branch.  Thanks for your help, @danderson !

Damnit! Thanks for the report, looking. At first glance, there's no obvious changes to that phase of boot, that section is just grabbing a static TFTP file. The MAC address is normal, but it's basically only for data continuity in the logs, so you can track a MAC through each stage of boot. The important part is the /0, which should serve an ipxe for the x86 arch...

Okay, looking at your pcap and screenshot, something is weird: in the pcap, Pixiecore is running on <IP_ADDRESS>, but in your screenshot, the virtualbox firmware is trying to download the next boot stage from <IP_ADDRESS>
I've seen this before, when there are multiple competing PXE and ProxyDHCP servers on the network. The PXE spec doesn't specify how to merge incoming responses for ProxyDHCP, so you can end up using a server IP from one response, but a filename from another... Unfortunately, I don't see <IP_ADDRESS> in the pcap, so I have no idea how this machine is somehow convincing your virtualbox to boot from it...
Does this make sense to you? Is there maybe a second pixiecore/other PXE server running?

Hi, I'm new to both Pixiecore and PXE booting in general. As a minor anecdote that I think might be related, I was having trouble booting a small device yesterday and happened upon your conversation as it was unfolding. I tried using several of the "quick" options just to rule out any mistakes I might have made invoking Pixiecore, but the results were the same. Sure enough, rolling back to October 17th in pixiecore enabled my device to load everything and boot.
This may be a completely different issue, but given the title of the issue I figured I would post it in here first since i-dont-know-what-im-doing.jpg.
Attached is a pcap I took using the debug command I found in pixiecore. The device would reboot immediately upon failure to boot, but I was able to glean a reference to this error in the output: ipxe.org/3c092083
boot.pcap.zip
I'm not sure how else to be most helpful, but here is a basic description of my setup:
My host machine is a Macbook Pro with VirtualBox. On my host there is a VM with a bridged network adapter, and this VM runs Pixiecore. On my local network there is a small device capable of booting over the network.

Okay, so that's two reports now that rolling back fixes things. I need to reproduce this locally somehow so I can bisect...

Okay! I can reproduce this in virtualbox with the architecture:

Virtualbox VM with no hard drive, bridged network, configured to boot from network.
Pixiecore running on the virtualbox host machine

I see the same symptoms, where the TFTP file inexplicably doesn't get served.
In parallel, I'm able to netboot a standard KVM machine, so it's something specific to virtualbox that's broken.
Bisecting...

Debugging a bit before I bisect... It looks like the virtualbox copy of ipxe never tries to speak TFTP at all, network capture only shows the DHCP exchange (which completes correctly afaict), and then the virtualbox firmware just fails without even trying to speak TFTP...

Verified again by comparing with a KVM VM, and I can definitely see DHCP+TFTP happening with that one.
So, a recent change made virtualbox's strange version of ipxe unhappy. Digging...

Found one solution: you need to install the virtualbox extension pack at https://www.virtualbox.org/wiki/Downloads . According to various internet sources, PXE boot from internal iPXE when using an emulated intel NIC is known-broken, and the "fix" is to install the extension pack, which provides the standard intel PXE ROM. This ROM can boot correctly, no problem.
I'm not sure I can fix virtualbox's builtin borked ipxe :( Their iPXE claims that it supports TFTP, but when I try and make it speak TFTP, it just fails without ever connecting to anything, with an error that makes no sense. So, that's not encouraging... I'll keep digging, but it's possible the "solution" will just be "don't use virtualbox, or if you have to use virtualbox, install the extension pack"
@cdata I suspect your own problem is something different, based on the fact that your setup is reversed (running pixiecore on virtualbox, booting a physical system). I'll investigate your report as soon as I close this one with a documentation fix.

@danderson for us it was not only VirtualBox that was broken. We had the same issue (mac address of client showing up as a filename) when booting using bare metal, too.

The MAC address in the filename is normal, we tell the firmware to boot //, so that the TFTP server knows which machine is requesting a boot file. You should see that in all boot attempts, and it shouldn't be a problem. Are you seeing problems with booting bare metal as well (no VirtualBox anywhere in the setup) ?

Okay, I think I've found what makes the embedded virtualbox iPXE unhappy. For some reason, it doesn't like the standard PXE format of specifying next-server+filename as a way of saying "you should boot with tftp://<next-server>/<filename>. Instead, it tries to interpret the filename <mac>/<arch> as a boot URL, and fails because it's not a URL.
I verified manually that if I give it a "filename" of tftp://<next-server>/<mac>/<arch>, virtualbox's ipxe is capable of chainloading to Pixiecore's ipxe, and from there we can successfully boot.
So, I think the change we need is:

Always chainload to Pixiecore's iPXE, so we have a known set of features.
When we want to chainload, detect if the PXE firmware is iPXE or non-iPXE. If iPXE, set the filename to tftp://<next-server>/<mac>/<arch>. Otherwise, set the filename to <mac>/<arch>.

This will require some refactoring of the boot logic, so it'll take a bit of time to make the change. I'll report back once it's done.

Okay, new problem... I implemented this, but now after chainloading to Pixiecore's iPXE, it cannot configure the network any more... iPXE's website says this can be a problem when you chainload undionly.kpxe (which is what we chainload), due to buggy firmwares :(

So, recapping, the failure you see here is actually a result of both of my attempts to fix #51. The obvious way to fix the problem triggered a bunch of bugs in my understanding of ipxe, and ipxe itself. I've updated #51 with the plan to fix Virtualbox booting.
Unclear if @cdata's issue is the same. The error he's getting suggests that it is, and if so, it's possible my virtualbox fix will also fix that. I'm filing a new bug to investigate that.


HAWQ-133. Remove MD Versioning code

We will implement a simpler invalidation-based solution instead of versioning. This will be used by the Query Optimizer to manage Metadata Cache.

@armenatzoglou @foyzur please take a look.

LGTM. Any reason why we cannot revert the previous commits and let Git handle the cleanup job?

LGTM +1

I removed the extra GUCs and logging / instrumentation code. Please take a look.

@foyzur The code is well contained, and this is easier than reverting a few tens of commits (in my opinion). Do you have any specific concern?

If it's 10s of commits, then it makes sense.
On Jan 12, 2016 4:55 PM, "George Caragea"<EMAIL_ADDRESS>wrote:

@foyzur https://github.com/foyzur The code is well contained, and this
is easier than reverting a few tens of commits (in my opinion). Do you have
any specific concern?
—
Reply to this email directly or view it on GitHub
https://github.com/apache/incubator-hawq/pull/261#issuecomment-171115184
.


Turned pydantic into a weak dependancy

Hot Fix
Turning pydantic into a weak dependency.

Since pydantic isnt a req anymore, you'll need to modify the github action scripts to manually install pydantic so that the tests run

I've added pydantic to the CI workflow, I'll need to iterate with the automatic testing because I'm not sure if it's enough

Good catch, although to address this I need to change a few more things. I need to make sure the file with pydantic import is not part of the Caustics root import, and is only imported in the function that requires it, which is in the simulator I believe

Correct me if I am wrong, but I think the approach I took solve the problem. The only thing exposed to the root level imports is build_simulator, so I made sure all the import statements related to Pydantic were used only inside the function definition. As such, Pydantic is now made a weak dependency. Caustics should attempt to import it only if build_simulator is called


getting_started example not work well.

Following https://usehelix.com/getting_started, found some issues.

rake irb only worked when into flipper/crates/text_transform/ directory.
But, rake build is worked in flipper, so i think this is a issue

default, Rails development use spring to boost rake, but not worked in
flipper/crates/text_transform/

 ╭─ 21:20  zw963 ⮀ ~/Project/rust/flipper ⮀ ⭠ (4c623dd) master ➦ ruby-2.3.4@flipper
 ╰─ $ rails --version
rRails 5.1.2

 ╭─ 21:20  zw963 ⮀ ~/Project/rust/flipper ⮀ ⭠ (4c623dd) master ➦ ruby-2.3.4@flipper
 ╰─ $ ruby --version
ruby 2.3.4p301 (2017-03-30 revision 58214) [x86_64-linux]

 ╭─ 21:20  zw963 ⮀ ~/Project/rust/flipper ⮀ ⭠ (4c623dd) master ➦ ruby-2.3.4@flipper
 ╰─ $ 127  rustc --version
rustc 1.18.0 (03fc9d622 2017-06-06)

As we see, no rake irb task.
 ╭─ 21:22  zw963 ⮀ ~/Project/rust/flipper ⮀ ⭠ (4c623dd) master ➦ ruby-2.3.4@flipper
 ╰─ $ 2  rake -T |grep -i helix
rake build                              # Build Helix projects in crates
rake clobber                            # Clobber Helix builds in crates

Need add following code to make rspec work

+++ b/crates/text_transform/Rakefile
@@ -1,6 +1,7 @@
 require 'bundler/setup'
 import 'lib/tasks/helix_runtime.rake'

+require 'rspec/core/rake_task'
 RSpec::Core::RakeTask.new(:spec) do |t|
   t.verbose = false
 end

Thanks for filing this issue!

I think this is a documentation error. The rake irb task is intended for basic testing of individual crates so I think it's ok to have to change into the crate directory to run it. I'll update the guide.
I'm not sure what you mean.
The generated crate Rakefile doesn't have an RSpec task in it. I'm confused as to why you think we need to add the require. You'd have to go through these steps to add RSpec to any project, right?

I've updated the website to correct the Getting Started Guide.

I think this is a documentation error. The rake irb task is intended for basic testing of individual crates so I think it's ok to have to change into the crate directory to run it. I'll update the guide.

I see document update, thanks

I'm not sure what you mean.
What i means is:  spring rake some:task not worked in flipper/crates/text_transform/.
As you know, It worked prefect in filpper directory. anywhy, maybe this not a issue too?

The generated crate Rakefile doesn't have an RSpec task in it. I'm confused as to why you think we need to add the require. You'd have to go through these steps to add RSpec to any project, right?

What i means is Step 4: Adding a feature in document. following example is not worked.
require 'bundler/setup'
require 'rspec/core/rake_task'
import 'lib/tasks/helix_runtime.rake'

RSpec::Core::RakeTask.new(:spec) do |t|
  t.verbose = false
end

task :spec => :build
task :default => :spec

in my local machine, i have to add require 'rspec/core/rake_task' to make it
rake command work.


Error building nginx with brotli

As seen on the docker ci / locally :
https://hub.docker.com/r/wonderfall/boring-nginx/builds/bwefentucfdxnpfiddjx4q5/

Yeah relate to this : https://github.com/Wonderfall/dockerfiles/pull/73#issuecomment-267810201
It's easy to fix but the major concern now is how to compile nginx 1.11.7 against BoringSSL without error.


[Feature][Connector-V2] JDBC source support string type as partition key

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Although the implementation supports string types as partitioning keys, this design is not very reasonable. Firstly, it affects the table_ The MD5 hash function is applied to each value in the name column, and the obtained hash value is modulo 10, followed by an absolute value. Only rows with a result equal to 1 will be selected.
For example, the specified partition is 10:
The actual SQL executed in the business library is:
partition 1：
SELECT * FROM (
select * from metastore_bdc.collect_dct_table_info
) tt where ABS(MD5(table_name) % 10) = 1;
partition 2：
SELECT * FROM (
select * from metastore_bdc.collect_dct_table_info
) tt where ABS(MD5(table_name) % 10) = 2;
。。。

As shown in the figure, this type of query runs through the entire table in the business library and does not utilize index keys, resulting in no performance improvement.
Suggested reference: Sqoop's method of string segmentation, digitizing existing Unicode characters
Reference link：https://blog.csdn.net/fyhailin/article/details/79069475

Thanks @2416210017 !

As shown in the figure, this type of query runs through the entire table in the business library and does not utilize index keys, resulting in no performance improvement.

Yes, this way not perfect. Just the simple way to implement this feature.

Suggested reference: Sqoop's method of string segmentation, digitizing existing Unicode characters

Can you create an issue for this? (If you can create a PR for this would be wonderful).

Of course, the issue has been submitted:https://github.com/apache/seatunnel/issues/5432 thank you for your reply!


Trinity ListDeserializationError during fast sync

What is wrong?
concurrent.futures.process._RemoteTraceback:
"""
Traceback (most recent call last):
  File "/Users/piper/.pyenv/versions/3.6.3/lib/python3.6/concurrent/futures/process.py", line 175, in _process_worker
    r = call_item.fn(*call_item.args, **call_item.kwargs)
  File "/Users/piper/sites/py-evm/p2p/p2p_proto.py", line 56, in decode
    raw_decoded = cast(Dict[str, int], super(Disconnect, self).decode(data))
  File "/Users/piper/sites/py-evm/p2p/protocol.py", line 85, in decode
    return self.decode_payload(data[1:])
  File "/Users/piper/sites/py-evm/p2p/protocol.py", line 72, in decode_payload
    data = rlp.decode(rlp_data, sedes=decoder)
  File "/Users/piper/python-environments/trinity/lib/python3.6/site-packages/rlp/codec.py", line 220, in decode
    obj = sedes.deserialize(item, **kwargs)
  File "/Users/piper/python-environments/trinity/lib/python3.6/site-packages/eth_utils/functional.py", line 22, in inner
    return callback(fn(*args, **kwargs))
  File "/Users/piper/python-environments/trinity/lib/python3.6/site-packages/rlp/sedes/lists.py", line 84, in deserialize
    raise ListDeserializationError('List has wrong length', serial)
rlp.exceptions.ListDeserializationError: List has wrong length
"""

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/piper/sites/py-evm/p2p/peer.py", line 739, in connect
    self.cancel_token)
  File "/Users/piper/sites/py-evm/p2p/peer.py", line 143, in handshake
    await peer.do_p2p_handshake()
  File "/Users/piper/sites/py-evm/p2p/peer.py", line 222, in do_p2p_handshake
    cmd, msg = await self.read_msg()
  File "/Users/piper/sites/py-evm/p2p/peer.py", line 324, in read_msg
    token=self.cancel_token)
  File "/Users/piper/sites/py-evm/p2p/cancel_token.py", line 110, in wait_with_token
    return done.pop().result()
rlp.exceptions.ListDeserializationError: List has wrong length

This error occurs semi-regularly during fast sync.
How can it be fixed
Explicit error handling.

This is one example of a message that causes this:
b'\x01\xf8{\x05\xa9odash/v1.0.0-stable/windows-amd64/go1.8.3\xcc\xc5\x83eth?\xc5\x83eth>\x80\xb8@.\x1bb\x00s>\xb77W\xb6\x1bhK{V\x865\x8b\x0e\x15\x86\x90\xeb)\x90-\xee\xd0]\x95<\xac\xe2 \xc4\xf9\xf3\x01\xb4\x8a\xee\xdc\xea\x90b\xc4\t\xc9d\x18S$\xbb\xc9\xa1gI\x1clY\xe0\x94\xc4\xf9'

The first byte is the command id. In this case it is 0x01, which is the Disconnect command, but the payload (see below) matches exactly that of the Hello command (see https://github.com/ethereum/wiki/wiki/ÐΞVp2p-Wire-Protocol), which suggests a broken client implementation.
>>> rlp.decode(d[1:])
[b'\x05', b'odash/v1.0.0-stable/windows-amd64/go1.8.3', [[b'eth', b'?'], [b'eth', b'>']], b'', b'.\x1bb\x00s>\xb77W\xb6\x1bhK{V\x865\x8b\x0e\x15\x86\x90\xeb)\x90-\xee\xd0]\x95<\xac\xe2 \xc4\xf9\xf3\x01\xb4\x8a\xee\xdc\xea\x90b\xc4\t\xc9d\x18S$\xbb\xc9\xa1gI\x1clY\xe0\x94\xc4\xf9']

And we're not the first ones to notice that: https://github.com/ethereum/pyethapp/issues/288
I think the best alternative here is to catch that exception in Disconnect.decode() and log a warning

Closing as addressed by #839


Change intersectsBoundingVolume to public

Does anybody have any objection of making public the following function?
boolean GVRSceneObject::intersectsBoundingVolume(float ox, float oy, float oz, float dx, float dy, float dz);
Do I have any alternative function?
I need it :)

Should be ok. We already have one overload public.

Thank you,
I will make a pull request soon.


Allow to specify soc-maxima and soc-minima as a range

          Side-question from #885: Wouldn't it be nice to allow to specify ``soc-maxima`` (and minima of course) as a range, so one would not have to send all consecutive points?

"soc-maxima": [
    {
        "value": 51,
        "start": "2024-02-05T12:00:00+01:00",
        "end": "2024-02-05T13:30:00+01:00"
    }
]

One problem I see is overlaps but that should cause an error.
Originally posted by @nhoening in https://github.com/FlexMeasures/flexmeasures/pull/885#discussion_r1375131453

Tech spike is on the way.


Mekanism Bins

I want these things to hold a silly amount of materials, especially since we can configure them to do so. At the same time, though, I want to adjust their recipes to use more exotic materials. To start, here are the storage capacities I'm suggesting:

basic bin: 4,096
advanced bin: 32,768
elite bin: 262,144
ultimate bin: 2,000,000,000

As such, the basic bin should be made of gunmetal. The advanced bins and up should require steel. We should edit the textures to match. The elite bin should require the reinforced alloy (which takes osmium), and the ultimate bin should take a void tear (which should explain the 2 billion capacity).

I changed the storage capacity of the bins in Commit https://github.com/belathus/Wanderlust-Renewed/commit/a2aa11ff92efa3a3d37e0885473e03fda1645fd5. Now, I just need to change the recipes to match.


consider depreciating infinite timeout Consumer.Poll()

Are there any practical situations where anyone would want to use Consumer.Poll() over a variant that has a timeout parameter?
Generally, you will want to poll the consumer with a relatively short timeout to allow controlled shutdown of the application.
Perhaps we want to add a variant that accepts a CancellationToken instead? Perhaps in that variant we would also want to encapsulate the poll loop?

Agree with this - the user can still call Poll(-1) to get the same (just add it in documentation), we don't want a new user to call Poll() by mistake and have a blocking thread for any reason
I liked the RdKafka Start and Stop in EventConsumer (basically just like the automatic poll loop in the Producer) Add a StartBackgroundPoll and StopBackgroudPoll has some sense

Hi do you planing to suppor async api for consumer ? Current implementation with Poll and event looks not very straightforward.

Hi!
Can you elaborate where an async method would make sense (compared to event or polling)?
Poll or consume won't do any action to the broker (internal fetch from broker are automatically done internally by the library by batch, poll/consume will just fetch from an internal queue, which is immediate)
An async method would be the same than calling Consume with a timeout (eventually 0) at the place where you except your await
Perhaps we could separate the consumer queue (which deliver consumer messages) from standard queue (metadata, commit callbak&other) by config to allow more scenario
Also we could not depreciate consume - I can see cases where we might not want event
(I'm not a confluent guy so they may have other opinion )

Looks like I did not fully understood the underlying system, earlier I was under impression that poll is a blocking IO operation, so I was thinking it would be more straight forward to consume bulks of messages from the network via async polling operations. If I use manual commit it would be best to commit it after I processed entire bulk.

It seems like both Consume and Poll actually should be async in the case where the client-side event queue is empty, in which case it should return a task that returns when additional events have been enqueued.
Without consume, it's actually very difficult to do flow control properly, since I can't stop polling for messages without stopping the polling for other events. You could solve this by adding an event filter argument to Poll. That way you can keep the polling loop alive without missing or buffering messages.

The 1.0 consumer has depreciated the Poll method, and introduced a Consume method with no timeout parameter but with CancellationToken instead. There is also a ConsumeAsync method, since there are scenarios that call for this, though that is not final (the implementation depends on Task.Run, which is not ideal).
The 'start' and 'stop' methods on the Consumer are definitely not coming back, though it may make sense to create a higher level class that builds on Consumer.


Fixed broken links in the Tables' Samples README.

Links ended up broken after moving the code snippets classes.

/azp run java - tables - ci

/check-enforcer evaluate


Add support for mulitple transactions on one session

will fix #1008

Codecov Report

Merging #1015 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #1015      +/-   ##
=========================================
+ Coverage   54.29%   54.3%   +0.01%
=========================================
  Files          41      41
  Lines        7548    7550       +2
=========================================
+ Hits         4098    4100       +2
  Misses       2934    2934
  Partials      516     516

Impacted Files
Coverage Δ

session_tx.go
91.66% <100%> (+0.36%)
: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 a8bd843...ce01583. Read the comment docs.


Can't load old models

 File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 14, in <module>     from modules import shared, devices, sd_samplers, upscaler, extensions, localization, ui_tempdir   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_samplers.py", line 11, in <module>     from modules import prompt_parser, devices, processing, images   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 15, in <module>     import modules.sd_hijack   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_hijack.py", line 31, in <module>     ldm.modules.attention.BasicTransformerBlock.ATTENTION_MODES["softmax-xformers"] = ldm.modules.attention.CrossAttention AttributeError: type object 'BasicTransformerBlock' has no attribute 'ATTENTION_MODES'

delete the folder sd and use the latest colab https://colab.research.google.com/github/TheLastBen/fast-stable-diffusion/blob/main/fast_stable_diffusion_AUTOMATIC1111.ipynb

Thanks! it worked!