async-21: New TiledImageVisual [WIP]

Description

This PR adds a new texture-atlas-based tiled visual for octree rendering.

New classes: VispyTiledImageLayer, TiledImageVisual and TextureAtlas2D.

I renamed the older one to be VispyCompoundImageLayer, which creates one ImageVisual per tile.

This one will probably not be used, but useful for comparison for now.
Also good to create the crash in #1811. The crash is using PyQt5 only, not PySide2.

New QtRender GUI  features:

Dropdown to select layer type for test image.
New green/yellow/red framerate meter.

The new fast tiled rendering:

Mostly 60-30Hz but a few yellow frames (slower than 30Hz). This is all in RAM, async loading coming soon. Pixels are still magnified, I need to match it to screen pixels. Although I will add a GUI option for magnified because it makes it a lot easier to see the transitions.

That is an 8k x 8k image.
Details
Atlas-based Rendering?
You can still select the older VispyCompoundImageLayer rendering from the UI. It creates an ImageVisual per tile. This leads to big hiccups in framerate, and crashes under PyQt5.
The crashes were investigated in #1811 and there is no solution yet. The new VispyTiledImageLayer avoids the crashes because it does not alter the scene graph to add or remove tiles.
Also the new way it is much faster. No shader rebuild is necessary to add or remove tiles. And the partial updates of the atlas texture is fast. Finally, David Hoese (vispy) recommended the atlas approach. He did something atlas-based for SIFT that we looked at, although it's quite different.
GUI: Select Image Layer Type
New dropdown to create one of three types of image layers:

Image layer with the original visuals.
OctreeImage layer with VispyCompoundImageLayer visuals.
OctreeImage layer with new VispyTiledImageLayer visuals.

GUI: New Framerate Meter
Added an experimental framerate meter at the bottom of the QtRender widget. The motivation was the new tiled rendering is way less glitchy and faster, but it's mostly a question of transient slow frames. So this shows your current framerate but also recent slow frames. Which are important to know about.

Type of change

[x] New features in experimental code
[x] Necessary changes to in non-experimental code (I will add section below soon.)

Files

References
Texture Atlas

Texture Array - Khronos Wiki
Improve Batching Using Texture Atlases - NVIDIA Whitepaper
Texture atlases, wrapping and mip mapping - 0FPS Blog Post
Using Texture Atlas as Texture Array in OpenGL - Stack Overflow
Array Texture (2D) - Tutorial
Satellite Information Familiarization Tool - SIFT

Contains a texture atlas and tiled visual written by David Hoese, a lead Vispy maintainer.
See the source for TextureAtlas2d and TileGeolocatedImageVisual.

Numpy

Numpy's meshgrid Explained
Numpy Array Reshaping
Visualizing Strides

Rendering

Optimizing Subdivisions in Spatial Data Structures
Virtual World Sandbox Terrain Enging
OpenGL Tile Map Rendering

This is still WIP but the new VispyTiledImageLayer with TiledImageVisual and TextureAtlas2D all work at least the very basics. And it's FAST. But I was having trouble characterizing how slow the older "compound" visual was because steady-state they are both fast, but it's the creating new tiles which is chunky and glitchy in the old system.
So I created a new frame rate meter that I think does a good job of conveying not just the current frame rate but the recent history of slower frames. But in a very compact display not a strip chart or scrolling display. Needs some refined but already proving useful:

Wow love the frame rate meter, and it's history functionality!

Also it's logarithmic. I need to calibrate so the numbers are more meaningful, but yellow starts at around 100ms (10Hz) and red starts at around 400ms (2.5Hz). So the red lights are single frames taking over 500ms.

I wouldn't worry about that too much for this PR, I'm happy to merge as is and make an issue for followup PR where we might use a nice colormap of some form

I hand calibrated the framerate meter to be roughly this, from a code comment.
# GREEN: up to 31ms (32Hz)
# YELLOW: up to 312ms (3.1Hz)
# RED: up to 6000ms (0.16Hz)
So that seems good for now.  Basically green is good, yellow is getting bad fast, and red is pretty awful.

Cool, with a small/safe change to our vendored ImageVisual, our TiledImageVisual can now use ImageVisual's _build_color_transform method. So we don't need a copy of it. It still has a mostly copied _prepare_draw but we might be able to whittle that down.

I just realized this does not support non-power-of-2 images right now. The older VispyCompoundImageLayer did, it can create ImageVisuals of any size, for edge and corner tiles. But right now VispyTiledImage requires all tiles be the same size. We could cheat and just pad them with blank pixels. But the right solution is we accept tiles which are smaller, we pad them, but then we compute the smaller texture coordinates, so draw the exact right size tile with just the exact texels we want.
This might be worth doing in a small async-22. And then async-23 is async/ChunkLoader/zarr, hopefully.

I'm trying this out now. If I turn on NAPARI_OCTREE=1 then astronaut works great for me, but I get a segfault if I try and create a digits example fresh on launch
WARNING: Error drawing visual <vispy.visuals.line.line._GLLineVisual object at 0x7f80cd9f9940>
20:58:33 WARNING Error drawing visual <vispy.visuals.line.line._GLLineVisual object at 0x7f80cd9f9940>
/Users/nsofroniew/opt/anaconda3/bin/pythonw: line 3: 26075 Segmentation fault: 11  /Users/nsofroniew/opt/anaconda3/python.app/Contents/MacOS/python "$@"

Not sure if this is related to #1835 or not (I'll try and get to that review soon). Not sure it needs to be fixed now or in the future, but wanted to report.
I'm going to continue with review

I marked this read for review. I think after this async-22 can be small to support non-power-of-two images (edges and corners in the texture atlas. Then maybe async-23 async/ChunkLoader/zarr or at least heading there.

I added a design diagram. If we end up keeping this we'll want to update the rendering doc.

Thanks for the replies to my comments. Everything sounds reasonable, so I'm going to merge this now.


Add hparams and compliance checks for training and eval samples for all benchmarks

According to issue https://github.com/mlcommons/submission_training_1.0/issues/39, the number of training samples is 117266. Many submissions do hardcode this value, even though the reference does not. On that specific issue the submission in question used a different value.
The decision was to add train_samples, and eval_samples as hyperparameters + the related compliance checker rules so we avoid such issues in the future.

I am assuming we make the check on train_samples & eval_samples to match reference values for all benchmarks, as we noted this for RN50 in https://github.com/mlcommons/submission_training_1.0/issues/48 as well.
If you agree, lets edit the title of the issue.

Good point, Marek. since it is all the benchmarks, if you need any help let me know.
So, restating the problem: In the 1.0 submission training and eval samples were found to be off for a couple of submissions. This happened also in 0.7 and went undetected.
Let's add compliance checks to avoid such issues in the future.

I'll be addressing this issue, and this is scheduled to be put in for v2.0.


Adding k8s remapper for supporting Kibaan Inventory "Kubernetes Pod" page

This is the main PR needed for https://github.com/elastic/opentelemetry-dev/issues/180
It adds the remapping functionality for kubeletstats and k8scluster receivers

cc @AlexanderWert , @ChrsMark , @tetianakravchenko
This is the relevant PR for the remapping of k8s otel metrics in opentelemetry-lib. Lets sync on how to test it

Nice @gizas !

This is the relevant PR for the remapping of k8s otel metrics in opentelemetry-lib. Lets sync on how to test it

I guess we would need to import the opentelemetry-lib in the Elastic Specific processor in order to test this e2e?
I assume this Elastic Processor would need to be part of the https://github.com/elastic/opentelemetry-collector-components but I'm not 100% sure if and when this will happen.
@AlexanderWert should we prioritize the Elastic processor so as different teams/contributors can have this as base for the specific implementations that would be on top?

@AlexanderWert should we prioritize the Elastic processor so as different teams/contributors can have this as base for the specific implementations that would be on top?

IIUC, @ishleenk17 is already working on that

@AlexanderWert should we prioritize the Elastic processor so as different teams/contributors can have this as base for the specific implementations that would be on top?

IIUC, @ishleenk17 is already working on that

The code is ready in the private branch and I have pointed @gizas to use that for testing.
In the meantime, the PR is being reviewed for merging this code into the components repo.

@gizas FYI: I've tested this PR - https://github.com/tetianakravchenko/opentelemetry-collector-contrib/commit/808f7f179547910c5897e23f3c9b5346f353ebf3 (changes are based on the mentioned above private branch - https://github.com/tommyers-elastic/opentelemetry-collector-contrib/tree/routing-processor and use the reference to the local opentelemetry-lib)
all works:

(k8s integration assets and the ingest pipeline were installed to make it work)

FWIW, to fix the lint we would need to update the notices which could be done by either running make all OR make update-licenses.

@lahsivjar np. Do you want me to open a new story?
Also I dont have write access to this repo. Can you please merge this PR for me if no other objections?

@gizas Yes, let's open a tracking issue for the test package.
@ishleenk17 Could you take a 👀 and merge if all good?

@gizas : Changes look inline with the hostmetrics code.
Have we tested these changes, with the processor?

@ishleenk17 not with the elasticinframetricsprocessor (as we will need to make changes here  is not it?)
But we repeated the tests as mentioned here
Do we need to open a PR there as well?
@lahsivjar FYI: https://github.com/elastic/opentelemetry-lib/issues/22

Please add the invocation change required in the Elasticinframetricscode as well.

@gizas FYI: https://github.com/elastic/opentelemetry-collector-components/pull/14


feat(types): add v-model to props

Related: https://github.com/vuejs/jsx-next/pull/496
Any prop with a corresponding onUpdate: prop will be converted to a union of itself and v-model:${name}
There was some concern about this adding unwanted v-bind:v-model suggestions in volar, that may need to be addressed separately.

@KaelWD is this still an issue? If it is can you create an issue please, I might be missing the full scope of this 🤔


Allow user to retrieve more than one resource using "st2 resource get" CLI command

This pull request addresses one of my biggest minor annoyances with StackStorm CLI.
A lot of times when I'm debugging / troubleshooting things, I need to view multiple resources at once to see what is going on.
This means that currently I need to run more than one command to achieve that.
For example:
st2 execution get id1
st2 execution get id2
st2 execution get id3

This slows things down and means more typing (yes, I can use a bash alias or function, but that's not ideal and it's not available out of the box).
With this change, user can now view more than one resource using the get command.
The same pattern is already available with st2 execution cancel command (I added it a while ago).
For example:
st2 execution get id1 id2 id3

Example output:
st2 action get packs.unload packs.show
+---------------+--------------------------------------+
| Property      | Value                                |
+---------------+--------------------------------------+
| id            | 5e9ae3535550f016857e19f9             |
| uid           | action:packs:unload                  |
| ref           | packs.unload                         |
| pack          | packs                                |
| name          | unload                               |
| description   | Unregisters all content from a pack. |
| enabled       | True                                 |
| entry_point   | pack_mgmt/unload.py                  |
| runner_type   | python-script                        |
| parameters    | {                                    |
|               |     "packs": {                       |
|               |         "items": {                   |
|               |             "type": "string"         |
|               |         },                           |
|               |         "required": true,            |
|               |         "type": "array"              |
|               |     }                                |
|               | }                                    |
| metadata_file | actions/unload.yaml                  |
| notify        |                                      |
| output_schema |                                      |
| tags          |                                      |
+---------------+--------------------------------------+
+---------------+--------------------------------------------------------------+
| Property      | Value                                                        |
+---------------+--------------------------------------------------------------+
| id            | 5e9ae3535550f016857e19f7                                     |
| uid           | action:packs:show                                            |
| ref           | packs.show                                                   |
| pack          | packs                                                        |
| name          | show                                                         |
| description   | Get detailed information about pack from the remote          |
|               | StackStorm exchange index.                                   |
| enabled       | True                                                         |
| entry_point   | pack_mgmt/show_remote.py                                     |
| runner_type   | python-script                                                |
| parameters    | {                                                            |
|               |     "pack": {                                                |
|               |         "required": true,                                    |
|               |         "type": "string",                                    |
|               |         "description": "Name of pack to lookup"              |
|               |     }                                                        |
|               | }                                                            |
| metadata_file | actions/show.yaml                                            |
| notify        |                                                              |
| output_schema |                                                              |
| tags          |                                                              |
+---------------+--------------------------------------------------------------+

Open Questions / To Decide
Currently when a single source id is provided, the command behaves exactly in the same manner as it did before - it's fully backward compatible.
When retrieving multiple resources, if one of the provided resources is not found, we simply print that, but we don't immediately exit with non-zero status code and print other resources which were found.
As far as using the existing command name goes - I think that's better than adding yet another command (e.g. st2 <resource> get-more or similar) - the whole idea is that it's simple and it works out of the box so any other change which would make it less simple (e.g. new argument or filter to list command, etc.) is a no go.
TODO

[x] (Once agreed on the approach) Implement it for other non-resource "get" commands
[x] (Once agreed on the approach) Add tests

I've pushed a change which adds this support for all the "resource get" commands.
In addition to that, while working on this change, I cleaned up the code a bit - removed some overriden duplicated methods in sub-classes which are the same as in parent classes, made sure we don't re-hrow ResourceNotFoundError twice in some situations (no need to re-throw it, we can just propagate the original error), fixed inconsistency for "resource not found" errors - most commands would throw ResourceNotFoundError, but a couple would throw / propagate original OperationFailureException.

I tried to also add some end to end tests, but sadly I don't have many hours to deal with and wait on end to end tests.
So I added some more unit tests which verify this new notation works for all the commands - 986989f570a26646f92ceafcfc447dcc7dc6f531.

OK, this is now synced with latest master.
Resolving merge conflicts was too painful due to black changes, so I just manually re-applied my old changes on top of latest master.


Remove sorting pubs option on deployed site

Description

Remove sorting publication option on deployed site
Remove the pagination if the items can fit within a page
Refactor the sorting publications function to make it stable

Type of change

[ ] Bug fix
[ ] New feature
[ ] Refactoring
[ ] Documentation
[x] Improvement

Problem

Sorting publications options not required on deployed site
The current sorting function is not stable --> same options might lead to slightly different sorting order

Solution description
See description
Tests
All unit tests pass? N/A
Builds successfully? Yes
Attach screenshot of the expected result (e.g. UI of the website/ postman api call result/ database changes)

sorting/layout options removed, pagination removed if total publications less than 10 (can be fit within a page)

Relevant document/ link (if any) N/A
Risk
Low. Simple change on UI

Should you also remove the pagination on the publications page on the main site if there's less than 10 publications?


Remove unused test helpers

no longer needed as of #458

Trapped by // +build zeek once again ... this stuff is needed.


⚠ Fortnite has degraded performance

In 5b5b455, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1289 ms

Resolved: Fortnite performance has improved in c954167.


Error - data type 'int64 for float64'

Hi,
After multiple testing (v0.7.6), it seems that the cooler load and zoomify do not expect to deal with float values.
ValueError: cannot safely convert passed user dtype of int64 for float64 dtyped data in column 2
It means that only raw Hi-C counts can be loaded, but not normalized or transformed counts (pearson  correlation maps, observed/expected, etc.)
It would be great if future versions of cooler could fixed that to allow users to play with any type of data transformation and see them into HiGlass.
Best
N

Float propagation issues should all be fixed now (v0.8)!

This issue seems have been re-emerged. cooler load --count-as-float is broken in release v0.8.3. I haven't tested with the trunk.

Thanks for reporting. Does --field count=7:dtype=float work as an alternative?

Thanks Nezar!
Your suggestion seems to work at first (it sets the field type properly), but then cooler breaks at another place:
INFO:cooler.cli.load:fields: {'count': 6, 'bin2_id': 1, 'bin1_id': 0}
INFO:cooler.cli.load:dtypes: {'count': dtype('float64'), 'bin2_id': <type 'int'>, 'bin1_id': <type 'int'>}
INFO:cooler.cli.load:symmetric-upper: True
INFO:cooler.create:Writing chunk 0: /tmp/tmphkJLtB.multi.cool::0
INFO:cooler.create:Creating cooler at "/tmp/tmphkJLtB.multi.cool::/0"
INFO:cooler.create:Writing chroms
INFO:cooler.create:Writing bins
INFO:cooler.create:Writing pixels
Traceback (most recent call last):
  File "/prj/tools/python2/bin/cooler", line 10, in <module>
    sys.exit(cli())
  File "/prj/tools/python2/lib/python2.7/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/prj/tools/python2/lib/python2.7/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/prj/tools/python2/lib/python2.7/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/prj/tools/python2/lib/python2.7/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/prj/tools/python2/lib/python2.7/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/prj/tools/python2/lib/python2.7/site-packages/cooler/cli/load.py", line 305, in load
    h5opts=h5opts
  File "/prj/tools/python2/lib/python2.7/site-packages/cooler/create/_create.py", line 641, in create_from_unordered
    columns=columns, dtypes=dtypes, mode='a', **kwargs)
  File "/prj/tools/python2/lib/python2.7/site-packages/cooler/create/_create.py", line 574, in create
    file_path, target, meta.columns, iterable, h5opts, lock)
  File "/prj/tools/python2/lib/python2.7/site-packages/cooler/create/_create.py", line 230, in write_pixels
    dset[nnz:nnz+n] = chunk[col]
  File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "/prj/tools/python2/lib/python2.7/site-packages/h5py/_hl/dataset.py", line 708, in __setitem__
    self.id.write(mspace, fspace, val, mtype, dxpl=self._dxpl)                                                                                File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
  File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
  File "h5py/h5d.pyx", line 221, in h5py.h5d.DatasetID.write
  File "h5py/_proxy.pyx", line 132, in h5py._proxy.dset_rw
  File "h5py/_proxy.pyx", line 93, in h5py._proxy.H5PY_H5Dwrite
IOError: Can't write data (no appropriate function for conversion path)

I only could get cooler to work fixing the data type setting of the count column in dictionary output_field_dtypes in cli.load.

Would you mind sending a sample file? I can't seem to reproduce it.

Thanks @danydoerr. My mistake, I thought you were inputting a BG2-type file, where count is in column 7, but you were using a COO file. If you do --field count=3:dtype=float, it will work. In fact, because count is standard you can omit the column number so --field count:dtype=float will work too.

Thanks, works!


Inconsistent Javadoc annotations for org.gradle.api.tasks.testing.TestReport (gradle 7.4)

The gradle 7.4 RC1 javadoc has inconsistent annotations, getDestinationDir() is marked deprecated, to be replaced with ** getDestinationDirectory()**. How can something be deprecated when the replacement is considered EXPERIMENTAL?

Expected Behavior

Not applicable: code documentation only
Current Behavior

Not applicable: code documentation only
Context

We are using the "Deprecated" method calls. But in order to fix them, I have to use new APIs ... that are also creating a warning because "incubating"?!
Steps to Reproduce

Skipped, problem is obvious from the Javadoc alone.
Your Environment

Not applicable: code documentation only

We're going to be un-@Deprecating the old properties for now in the next 7.4 RC.  The plan is to go through at least one minor revision cycle so that the replacements can be promoted to stable first, prior to deprecating the methods they are replacing.  Note that even though the replacement methods are @Incubating, there is every intention to proceed down this path.  Please see the linked PR.


Enable mixed precision in cls task & Update mmcls version to v0.15.0

This PR includes

Update mmcls version to v0.15.0 to enable FP16
SAM optimizer for fp16

Has the OTE PR related to this PR been created? This is a library version upgrade, so testing is essential along with the 'init_venv' modification. MPA PR should also be merged after passing the OTE test.

I already have tested in OTE CI but didn't make OTE PR. I will make it after this is merged to develop.


add support for css @property

This PR adds support for CSS @property feature.

createVar - creates a @property definition, returns property var format var(--propertyName)
createGlobalVar - same as createVar but with a predefined name
getVarName - accepts a property var format and returns just a property name var(--propertyName) -> --propertyName

example:
import { style, createVar, keyframes, getVarName, fallbackVar } from '@vanilla-extract/css';

const color = createVar();
const angle = createVar({
  syntax: '<angle>',
  inherits: false,
  initialValue: '0deg',
});

const angleKeyframes = keyframes({
  '100%': {
    [getVarName(angle)]: '360deg',
  },
});

export const root = style({
  background: 'pink',
  color: 'blue',
  padding: '16px',
  transition: `opacity .1s ease, color .1s ease`, // Testing autoprefixer
  backgroundImage: `linear-gradient(${angle}, rgba(153, 70, 198, 0.35) 0%, rgba(28, 56, 240, 0.46) 100%)`,
  animation: `${angleKeyframes} 7s infinite ease-in-out both`,

  ':hover': {
    opacity: 0.8,
    color: color,
  },

  vars: {
    [color]: '#fef',
    [angle]: fallbackVar(angle, '138deg'),
  }
});

Thanks for the PR! This looks really great.
To me this is just an extension of our current createVar API. The fact that it's natively called @property definitely challenges our current naming, but I think for now VE needs to be consistent in calling them "vars". If we rename them to properties, we'd do this across the whole library in a future major version. I think it's okay that internals refer to it as "property" though since this future-proofs the integration package against API changes.
So I think we'd need to make the following changes for now:

Overload createVar so the API is createVar({ syntax: '<color>', inherits: false, initialValue: '#fff' }).
Rename createGlobalProperty to createGlobalVar.
Replace getPropertyName with getVarName (which already exists in our private package). This would need to be exposed from css and dynamic packages since you'd want this at both build time and run time.

@markdalgleish thanks for cleaning this up! is there something I should address before merging?

@markdalgleish any updates here, i'm really waiting for this feature?

@markdalgleish any updates here, i'm really waiting for this feature?

This would be a nice addition. Currently I can only use properties using globalStyle with a @ts-ignore. That feels a bit dirty
globalStyle(`@property --headerBackground1`, {
  // @ts-ignore
  syntax: `'<color>'`,
  initialValue: colorPrimitives.neutrals.whites.W100,
  inherits: false,
});

I'd like to bump this and see it land! 🙏  This would be a great feature for our design system to use.

Need this as well, any update to this PRs future @markdalgleish?

I am also needing this in our current library. Any update?

@z4o4z Hey, are you still interested in getting this PR over the line? If not, I may look at picking it up myself in the future.

hey @askoufis, i've added tests and updated docs. let me know if that looks good for you :) Thanks for helping with the PR!

@askoufis addressed the feedback + improved documentation. I found out that parcel doesn't support @property and all parcel-related playwright tests are failing now, not sure what to do with it...

@askoufis addressed the feedback + improved documentation. I found out that parcel doesn't support @property and all parcel-related playwright tests are failing now, not sure what to do with it...

looks like it's not the parcel issue itself, parcel uses lightningcss to build CSS, and lightningcss doesn't support @property keyword (playground) :(

looks like it wasn't an issue in the parcel, apparently initial-value is required for non * syntax, so it was failing with not really useful error. So i've made initialValue required on type level for non * syntax.

@markdalgleish Would you mind giving this another review when you've got some time?

Looks like linting is also failing, specifically prettier.

@askoufis thanks for the feedback! addressed everything

hey @askoufis @markdalgleish any chance we can merge it soon?

Bump.

bump! I just need this one as well ;)

This has been released in<EMAIL_ADDRESS>

yay!


[mesheryctl] system start not recognizing user's current context

Description
Meshery v0.5.0-beta-2 was released and an urgent defect has been identified in mesheryctl system start. This command does not recognize user’s current-context, and therefore, prevents them from starting Meshery.
$ mesheryctl system start
13:23:31 current context not set

Expected Behavior

start should read the current-context from user's meshconfig (config.yaml).
timestamp should not be shown to the user.

Environment:

Meshery Version: v0.5.0-beta-2

Fixed


OpenGL.Net 0.2.1 NuGet packcage seems to be missing GlControl

Release notes lists the addition of the GlControl, however it doesn't seem to be actually included in the package.
I can use the GlControl only after cloning the repo and building the solution myself.

The same problem. No GLControl in Toolbox and it can't be added.

I'll check within the next week.
Il mer 13 lug 2016, 11:03 LebedevaElen<EMAIL_ADDRESS>ha
scritto:

The same problem. No GLControl in Toolbox and it can't be added.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/luca-piccioni/OpenGL.Net/issues/10#issuecomment-232298943,
or mute the thread
https://github.com/notifications/unsubscribe/AEe6CdIL4iZUJvKB4CAr_sNgayOFPMFUks5qVKnhgaJpZM4JJvtO
.

Any update on this?

Yesterday I've released an updated version of the library. Due some unexpected trouble I've compiled it using Mono 4.2 on Linux. It should work all the same.
If someone can confirm that on Windows platform is working, I'll close the issue.

The GlControl doesn't show in the Toolbox bar, but now the control is up and running.


missing action

I hope I'm not duplicating any issues, but from #50 I got the impression that the use-case of synchronous actions was already resolved in v0.6+.
I'm using a custom middleware to handle API calls, more or less like from the real-world example in redux. So I dispatch an object that might look like
function loadUserData(id) {
  return {
    types: [USERDATA_PENDING, USERDATA_SUCCESS, USERDATA_FAILURE],
    [API]: {
      endpoint: '/whatever/user'
    },
   meta: { userId: id }
  }
}

within the api middleware authentication, caching etc will be handled (I know the whole thing could be maybe handled with sagas, but for now we just try to migrate bits and pieces and see how it works out).
Right the start of the middleware I dispatch the pending action
...
const [ pending, success, failure ] = action.types
dispatch({ type: pending, meta: action.meta })
...

In my saga now I listen to some user intent action (e.g. SHOW_PROFILE) from a component and try to make related calls along with other operations that might need to happen as a result
...
const { id } = yield take(SHOW_PROFILE)
(typeof id !== 'undefined') ? yield put(loadUserData) : yield put(<someOtherAction>)
const { meta: { userId }} = yield take(USERDATA_PENDING)
history.push(`/app/someurl/${userId}`)
...

in this scenario I miss the pending action, and the only way to take it is to wrap the dispatch call in the api middleware with a setTimeout function.
Is this case still a limitation of the library or am I missing something to handle these use-cases correctly?

I don't know what is expected to happen in this case, but why you need to take USERDATA_PENDING?
If it's always dispatched after you put loadUserData, I think you don't need it.
The success and failures actions being asynchronous should be taken normally.

Indeed success and failure will work as expected.
In this case I tried to navigate to a different page and showing a loading spinner directly after the interaction happened and wait on the new page for the actual response.

I think you can do that without taking the USERDATA_PENDING action. Navigation can be done as follow:
const { id } = yield take(SHOW_PROFILE)
(typeof id !== 'undefined') ? yield put(loadUserData) : yield put(<someOtherAction>)
// You don't need it, just navigate to the other page immediately
// yield take(USERDATA_PENDING)
yield call(history.push, 'other-page')

The loading spinner should be shown based on your app state, which is managed by your reducer.

Thanks for the suggestions, but this won't work because I need a key which is included in the meta tag of the action to get the navigation correct. I forgot to include these requirements in the original post (now its updated). I'm sure there might be other ways to work around the problem, but I was also curious to know if this is somehow expected behavior or if I been missing something, especially since I've got the impression that after v0.6 this might work.

@baabgai First let's understand why you're missing the action.
First thing to know is that the put effect is dispatched asynchronously in a microtask (you'll see why shortly); i.e. something like this
function runPutEffect(action) {
  Promise.resolve().then(() => dispatch(action))
}

what that means in your code is that yield put(loadUserData(...)) is not executed right away but shceduled in a microtask. so the current flow will first terminate (e.g. the code dispatching the action to the Saga) then the dispatch will be executed.
There are various reasons for this but in this case your example doesn't work precisely because of synchronous dispatching. Here is why
Suppose that redux-saga executes the put effects syncronously (i.e right away)
function runPutEffect(action) {
  dispatch(action)
}

What will happen in your example above is the following sequence

Some code (e.g. inside an UI component) dispatches SHOW_PROFILE

The Saga takes the action and yields the put(loadUserData(...)) effect

(We suppose) the Saga dispatches the loadUserData(...) action synchronously

The action goes through the Store's middleware pipeline and intercepted by your middleware

The middleware will dispatch({ type: pending, meta: action.meta }). and this the issue: because we're still in the middle of the first dispatch.

In other terms we've this call sequence
UIComponent:dispatch(SHOW_PROFILE)
-----------> Saga:take(SHOW_PROFILE)
-----------> Saga:put(loadUserData)
--------------------->Store:dispatch(loadUserData)
------------------------------->middleware:dispatch({ type: pending, meta: action.meta })
------------------------------->middleware:fires the ajax request
------------------------------->middleware:return
--------------------->Store:return
----------->Saga:take(USERDATA_PENDING)

so the issue here is precisely because the sequence is synchronous, when the Saga is calling put; It'll have for the dispatch call to return (Just as you wait for a val = func()). But since the middleware is dispatched inside the first dispatch, the Saga will not take the nested action because it's still waiting for the outer dispatch call to return.
and this is exactly what's happening in your example above: even if the Saga dispatches the action asynchronously, the whole sequence above will happen inside the same microtask (the dispatch and the nested dispatch).
So the solution is to dispatch the middleware action after the the saga action and not inside of it. And to do this you have also to dispatch your action asynchronously
const [ pending, success, failure ] = action.types
Promise.resolve(). then( () => dispatch({ type: pending, meta: action.meta }) )

I got the impression that the use-case of synchronous actions was already resolved in v0.6+.

0.6 solved the case for synchronously taking actions: i.e. the take effects will be resolved in the same task as when the action was dispatched (e.g. from a Component event handler). But the case for sync/async dispatches is more complicated (conceptually and not technically) because of the nested dispatch issue above.
I opted for the async dispatch because it provides a more predictable behavior for most of use cases. For example a common use case is for Sagas to dispatch actions at the start of the application
function* startupSaga() {
  yield put( loadStartupData() )
}

//...
createStore(reducer, applyMiddleware( createSagaMiddleware(startupSaga, ...) ))

The Saga dispatches an action right at the start. If we dispatch the action synchronously, it won't work because the code above will execute inside the applyMiddleware(...) call, i.e. before even the createStore returns.
You can also find more examples in those test cases

Is this case still a limitation of the library

TBH I can't answer this. I agree it has to do with the event model of Sagas (take/put). But I think it's also due to how Redux dispatching works.
Will this issue be gone if Redux flattened itself the dispatches (for example by ordering them in microtasks) ? I don't know. But I'd like to hear what @gaearon is thinking of this

Thanks a lot for the fast and detailed explanation. I had a similar issue already earlier with a thunk dispatching actions I missed, but I could work around that in a different way. Guess that was caused by the same behavior. Now it makes much more sense.
If this issue can't be considered a bug, maybe your explanations would fit somewhere in the docs (troubleshooting section?) to prevent people from running into that issue.
thanks again. saved me a lot of time getting my head around this issue.

If this issue can't be considered a bug, maybe your explanations would fit somewhere in the docs (troubleshooting section?) to prevent people from running into that issue.

Yes I think so

@baabgai it seems like a not too good decision. Why you need to yield put(loadUserData) instead of call api function that loads user details or returns already exists?
In this case, you split user loading logic into 2 sagas, while it should be in one place?
I think it might look like this:
...
const { id } = yield take(SHOW_PROFILE)
if (typeof id !== 'undefined') {
    yield put(loadingUserData()) // Fires USERDATA_PENDING action
    const {userId} = yield call(api.loadUserData)
    history.push(`/app/someurl/${userId}`)
} else {
    yield put(<someOtherAction>)
}
...

@panki that might be correct, but the reason for writing the saga as described was mainly driven by the fact that the custom api middleware (including various transformations on the requests) was already in place and I tried to fit a few sagas in our existing code base. If I had the time do more refactoring I guess this specific problem might not have manifested because you might implement it in a similar way you described.

FYI added a mention on the troubleshooting page(The put effect is also a blocking call section)
http://yelouafi.github.io/redux-saga/docs/Troubleshooting.html


Make an M1/arm64 compatible toolbox build

purpose
make toolbox fully compatible on M1 machines
things done in this PR

created a new Dockerfile which contains the arm64 version of Toolbox, with as many dependencies as possible changed to use arm64 versions of the binaries
updated Makefile targets to build new version
updated toolbox.mk to have a check for arm64 and switch to that image without any user input

important notes

as part of this, I've added a new tag for toolbox images, which is just appending -arm64 at the end of it
the base image for the arm64 version is debian:bullseye-slim instead of alpine. the reason for this is that the glibc binaries that are installed in the image build process are x86_64 only. this stops an image which is built locally on an M1/arm64 device from working.   in terms of image size, there seems to be only an increase of ~20mb from switching to the new  base (891MB for arm64 version, 844MB for x86 version)
separating into two different Dockerfiles seemed like the nicest way to go about doing this. I thought about having argument to change for the different architectures but tbh it was looking pretty bad - lots of different conditionals etc

Multi-arch support is something we definitely need to add and this is a good start but if we're going to do it I'd like us to do it in a way that leverages proper multi-arch images that share the same tag between architectures. There's quite a few articles out there that would indicate this shouldn't be too hard to wire up. See here and here.
Also, I'd like to understand why we can't do multi-arch and stick with Alpine. It may well be that this is not possible but before we switch base OS, I think we need to prove that it is not possible. Historically, Debian-based images have produced lots of security warnings in tools like Snyk which we then need to either action or ignore. If we do find that we need to switch to another base OS then we should publish a beta image first that we consume in a few of our more complicated build pipelines to make sure there aren't any issues.

I'd like to understand why we can't do multi-arch and stick with Alpine

The main reason I think this is the case is that the glibc dependency that we install in the build process does not work on ARM architecture - there's an open issue on the repo that's been there since 2019 but doesn't seem to have made any meaningful progress (check it out here)
This impacts the image build process when building on an M1/ARM based machine. Because the glibc doesn't install, awscli doesn't work either. Here's what happens when I run a locally built toolbox image that's based on Alpine
docker run -it seek/toolbox:latest-amd64 bash

bash-5.1# aws
/usr/local/bin/aws: error while loading shared libraries: libz.so.1: cannot open shared object file: No such file or directory

If sticking to Alpine is a non-negotiable requirement, a solution could be that these images are never built on an M1/ARM based machine and instead by someone who has an x86 based machine. I don't know if that actually would work but might be worth testing.
Alternatively, we can engage with Security and see if using Debian is an acceptable risk

The main reason I think this is the case is that the glibc dependency that we install in the build process does not work on ARM architecture - there's an open issue on the repo that's been there since 2019 but doesn't seem to have made any meaningful progress (check it out here)

That's fair enough.
Have you tested this build process? Can you build and publish both architectures on your M1? Could I on my x86? I would've thought each architecture would need to be built and pushed on a machine of that type 🤔 Won't you need to update the GitHub action scripts to do this?

Have you tested this build process? Can you build and publish both architectures on your M1? Could I on my x86?

I don't know if an image I build for x86 is going to work if it's published, due to the aforementioned glibc issues. The M1 build looks to be working fine - I'll be testing it a bit more with my own work today to see if it does work as expected. You should be able to on your x86 with no problems. (pls do try, it'd be good to get this flow tested)
I also don't have the ability to publish to Dockerhub afaik, so I can't chuck up a beta image for people to play around with to see if it all works

I would've thought each architecture would need to be built and pushed on a machine of that type

I think this is some Docker magic working in the background to some extent. No documentation about multiarch builds say anything about needing to be built on each architecture.

@antonbriganti-seek I think we want to reduce the differences between x86 and ARM to the bare minimum. So it would be better if we make both images based on the same base OS - i.e., Debian in this case. While you're at it, could you rename Dockerfile to Dockerfile.amd64 and we won't won't treat any particular image as the "default" - they're just different architectures that the container runtime will pull based on the host.
In the few tutorials I read, you need to build and publish the image for a given architecture on a specific host for that architecture - which would make sense. Because there is no flag you can give to Docker to say "build this for ARM even though the host is x86". And a lot of the time the Dockerfile is the same between architectures so if you build both on your M1 you'll just be pushing the same image twice and calling it something it's not.
https://blog.oddbit.com/post/2020-09-25-building-multi-architecture-im/


Add conditional showing of Science GCSE on Your application page

Context
A candidate is only required to have a Science GCSE if the level of the course they have chosen is a primary one. Currently, we always show the Science GCSE section on the Your application page but this should be conditional on the courses chosen.
Changes proposed in this pull request
This PR adds the showing of Science GCSE on the Your application page by adding a method called science_gcse_needed?. This returns true if any of courses chosen are primary and false for any other level.
We've also added in a feature flag called conditional_science_gcse as we'll need to always show the Science GCSE until we add conditional validation when reviewing and submitting an application in our next PR.
Screenshots

Guidance to review
Upcoming PRs will look at not showing it in the application review and not validating it at submission.
Link to Trello card
401 - Primary course conditional

For reference
This is how manage-courses-backend does this for Publish and Find:
https://github.com/DFE-Digital/manage-courses-backend/blob/24ae9c34c11c6479990132ab86374988c3c2c8d6/app/models/course.rb#L314-L328
It caters for the "Further education" case, where no GCSEs are needed. We won't get to that for a while.
The rules are set out in:
https://www.gov.uk/government/publications/initial-teacher-training-criteria/initial-teacher-training-itt-criteria-and-supporting-advice#c11-gcse-standard-equivalent


import 'package:cloud_firestore/cloud_firestore.dart'

Hi @Goumba96
When opening an issue, please try to provide all of the information indicated in the template.
Closing this issue, since no information has been provided.
Thank you.


On Start and Forever...

I still think On Start + Forever is confusing - especially as it's the default 1st experience for newbies.

This is a P1 because will we start using those blocks and we will have to add more conversion code if we change again.


Fork USWDS And Make Styling Changes

Fork a new project from USWDS and make PDS specific styling changes. We will follow the process that nasawds took.

This is now being rolled into Trade Study NASA-PDS/PDS.nasa.gov-UX#9


valueChanges list vector do not have $key

Hi, I have tried your examples for the new version AngularFire:5.0.0-rc.1. Doing the complete example app for Retrieving data as lists I found that  this.itemsRef.valueChanges() just return an array without $key value.
For that reason in the update or remove function it is impossible to do it.
I am not sure if you want that behavior on the valueChanges() method, but for the example, it does not work.
I found the solution using snapshotChanges() method and just doing a referent to intem.key.
Version info

Angular: 4.3.6
Firebase:4.5.0
AngularFire:5.0.0-rc.1
Sample data and security rules
Your code example.
template

Update
Delete

Add
Delete All
export class AppComponent {
itemsRef: AngularFireList;
items: Observable<any[]>;
constructor(db: AngularFireDatabase) {
this.itemsRef = db.list('messages');
this.items = this.itemsRef.valueChanges();
}
addItem(newName: string) {
this.itemsRef.push({ text: newName });
}
updateItem(key: string, newText: string) {
this.itemsRef.update(key, { text: newText });
}
deleteItem(key: string) {
this.itemsRef.remove(key);
}
deleteEverything() {
this.itemsRef.remove();
}
}
Fixed code example
template

Update
Delete

Add
Delete All
export class AppComponent {
itemsRef: AngularFireList;
items: Observable<any[]>;
constructor(db: AngularFireDatabase) {
this.itemsRef = db.list('messages');
this.items = this.itemsRef.snapshotChanges();
}
addItem(newName: string) {
this.itemsRef.push({ text: newName });
}
updateItem(key: string, newText: string) {
this.itemsRef.update(key, { text: newText });
}
deleteItem(key: string) {
this.itemsRef.remove(key);
}
deleteEverything() {
this.itemsRef.remove();
}
}

Hi @malagonandres! This is by design. The docs reference this and guide you in how to handle it. I recommend using .snapshotChanges().
There were issues in the past with special character mappings and instead we rely on doing transformations with observables. See the documentation for an example.


dbeaver unexpect close due to invalid pointer

System information:

ArchLinux
dbeaver 21.0.4
openjdk 15.0.2 2021-01-19, OpenJDK Runtime Environment (build 15.0.2+7), OpenJDK 64-Bit Server VM (build 15.0.2+7, mixed mode)

Connection specification:

Database name and version: MySQL and Oracle
Do you use tunnels or proxies (SSH, SOCKS, etc)? : No

Describe the problem you're observing:
When I edit a connection, and click OK, dbeaver freezes with no response, and then close.
Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs

log file of command LANG=en_US.UTF-8 dbeaver: dbeaver.log
and ~/.local/share/DBeaverData/workspace6/.metadata/dbeaver-debug.log:
dbeaver-debug.log, and the jvm log: hs_err_pid220752.log

Looks like a GTK error.
Can you provide more information about your environment, please?

@ShadelessFox Yes, I'm using ArchLinux with GNOME 40.1, gtk3 3.24.29. What else information should I provide?

That's enough for now, thank you.
We need further investigation, at least try to reproduce.
One more question, Is that an one-time situation or it keeps happening every time you're trying to perform described actions?

It keeps happening almost every time I trying to edit the connection setting.


Add XAttr to Link struct

This simply adds an XAttr field to the Link struct, as the JSON response for links (in e.g. ListChildren()) contains such a field, and it can be used to obtain the size and modification time of the original plaintext (not encrypted) file without further API calls, which can offer some big performance improvements (ref. rclone/rclone#8058).
From my tests, it exactly matches the XAttr field of the active revision obtained with ListRevisions().
(Side note: The active revision data included in the link JSON has an empty XAttr field, which may seem a little odd, but presumably it's because it would be redundant with the link's XAttr field, so there's no need to repeat it.)

Hey @lawmurray thanks for the PR!
Can you confirm that you have run the integration test when this change in place?
Thank you!

Yes, if by rlcone integration tests you mean go test -v in the backend/protondrive directory. That all works as before.

Is there anything more that you need from me to merge this and the related PR @henrybear327? Would be nice to get this work included in the rclone 1.69 milestone that's due by 20 October.

Is there anything more that you need from me to merge this and the related PR @henrybear327? Would be nice to get this work included in the rclone 1.69 milestone that's due by 20 October.

Hey @lawmurray,
Sorry for missing this email notification completely :(
I am in the process of moving this repo under the rclone org umbrella, so you can merge things directly soon!
Henry

Okay, thanks @henrybear327.
This particular pull request is almost trivial by the way, it just adds an attribute to a struct needed to get at the new information, and the other pull request that you already merged (https://github.com/henrybear327/Proton-API-Bridge/pull/28) depends on it.


NAV BAR OPTIMIZATION

The nav bar containing various details - phone number , address etc blends in with the background not providing good User experience and premium look . I believe my contribution will be good for your website . Would request you to assign me this task under hacktoberfest tag .

Please attach the hacktoberfest tag on the assigned issue.


Segfault in invalid code example

This one I've yet to follow the parser to understand what's going on. It seems however that a conditional not guarded with if after a for loop sets up a confused state for the parser that allows an incomplete malformed list to be interpreted as a method name with more than 16 arguments which causes a stack overflow
for (t in 1..1) 1 > t [1, 2, 3, 4, 5,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,]

Output
[root@graphite bin]# ./wren_test c.wren
< several lines of errors snipped >
[./c line 1] Error at ',': Methods cannot have more than 16 parameters.
[./c line 2] Error at end of file: Expect ']' after arguments.
Segmentation fault (core dumped)

Don't try to make much sense of/trust what comes after the first error.
Sometimes it recovers correctly, sometimes errors worsen.


Fixing state's name by replacing Risal with Rizal

What are the relevant tickets?
fixes https://github.com/mitodl/micromasters/issues/4653
What's this PR do?
Fixes typo in a state's name by replacing Risal with Rizal
How to test?
On micromaster do the following steps:

Log in and go to /profile/personal
Under "Where are you currently living" set the Country to "Philippines"
Open the drop-down for "State or Territory"
Search for state "Rizal", you will see "Risal" instead.

Now go to the package.json of micromasters and change iso-3166-2 dependency's commit id with hamza/replace-Risal-by-Rizal (ie: "iso-3166-2": "https://github.com/mitodl/iso-3166-2.js/#hamza/replace-Risal-by-Rizal",)
Now govern the same 4 steps mentioned above, you will see that now "Rizal" is showing up.
OR you can also test it by:
iso3166.subdivision("PH", "RIZ")
{
  type: 'Province',
  name: 'Rizal',      # new name
  countryName: 'Philippines',
  countryCode: 'PH',
  code: 'PH-RIZ',
  regionCode: 'RIZ'
}

Screenshots:
Before:

After:

@HamzaIbnFarooq make sure to create the micromasters corresponding PR for the updated iso-3366.js with your commit version.

@HamzaIbnFarooq make sure to create the micromasters corresponding PR for the updated iso-3366.js with your commit version and give the reference of that PR and assign that new PR for review to me.

Thanks @umarmughal824 for the remainder, will do once this PR gets merged.


(#897) Added a configuration for the MessageParameters

So now, when StandardMessage, TwitterMessage, GitterMessage,
or MicrosoftTeamsMessage are changed, the parameters
which are sent to string.Format can also be changed by
settings MessageParameters.
The default for MessageParameters is equal to the "old" value,
so this change is compatible with "old" settings where the
messages were either changed or unchanged.
fixes #897

@nils-a your changes have been merged, thanks for your contribution 👍


retention: Guarantee type-safeness when calling move_rows.

Passing an SQL (Composable) object into cursor.execute is
an idiomatic practice for psycopg2 not understood by django-stubs.
The .as_string method automatically gets invoked upon execution,
so the resulting query will be unchanged.
This ensures that all the keyword arguments in move_rows
have the correct types. Note that returning_id is supposed to be a
flag instead of a Composable Literal.
This is a part of the django-stubs refactorings #18777.

Screenshots and screen captures:
Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

This does not work in general.
>>> from psycopg2.sql import SQL, Identifier
>>> SQL("SELECT * FROM foo").string
'SELECT * FROM foo'
>>> SQL("SELECT * FROM {table}").format(table=Identifier("foo")).string
Traceback (most recent call last):
  File "<console>", line 1, in <module>
AttributeError: 'Composed' object has no attribute 'string'

This is pretty verbose and might discourage developers from using the safe Composable API in the future, so I’d rather fix django-stubs instead. Opened typeddjango/django-stubs#1029.

Thanks for the PR upstream @andersk! There is one remaining change to be applied from this branch.

Merged, thanks @PIG208!


RuntimeError: CUDA error: an illegal memory access was encountered

I was following the installation tutorial, selected pygmalion and then MAS opened, however as soon as I try to speak with Monika the game freezes and the following below appears on the command prompt. I'm not sure if it has anything to do with my GPU, it's a geforce RTX 2060 super which should have enough VRAM to do this kind of stuff since I use it for stable diffusion with zero issues.
Exception in thread Thread-7:
Traceback (most recent call last):
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\threading.py", line 932, in _bootstrap_inner
    self.run()
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "main.py", line 458, in listenToClient
    bot_message = inference_fn(pyg_model,tokenizer,history, received_msg,generation_settings,char_settings,history_length=context_size,count=pyg_count)
  File "A:\game storage\MonikA.I\run_pygmalion.py", line 36, in inference_fn
    model_output = run_raw_inference(model, tokenizer, prompt,
  File "A:\game storage\MonikA.I\pygmalion\model.py", line 70, in run_raw_inference
    logits = model.generate(stopping_criteria=stopping_criteria_list,
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\utils\_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\generation\utils.py", line 1437, in generate
    return self.sample(
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\generation\utils.py", line 2443, in sample
    outputs = self(
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\accelerate\hooks.py", line 158, in new_forward
    output = old_forward(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\models\gpt_neo\modeling_gpt_neo.py", line 741, in forward
    transformer_outputs = self.transformer(
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\accelerate\hooks.py", line 158, in new_forward
    output = old_forward(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\models\gpt_neo\modeling_gpt_neo.py", line 621, in forward
    outputs = block(
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\accelerate\hooks.py", line 158, in new_forward
    output = old_forward(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\models\gpt_neo\modeling_gpt_neo.py", line 327, in forward
    attn_outputs = self.attn(
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\accelerate\hooks.py", line 158, in new_forward
    output = old_forward(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\models\gpt_neo\modeling_gpt_neo.py", line 279, in forward
    return self.attention(
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\accelerate\hooks.py", line 158, in new_forward
    output = old_forward(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\transformers\models\gpt_neo\modeling_gpt_neo.py", line 223, in forward
    query = self.q_proj(hidden_states)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\nn\modules\module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\accelerate\hooks.py", line 158, in new_forward
    output = old_forward(*args, **kwargs)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\bitsandbytes\nn\modules.py", line 242, in forward
    out = bnb.matmul(x, self.weight, bias=self.bias, state=self.state)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\bitsandbytes\autograd\_functions.py", line 488, in matmul
    return MatMul8bitLt.apply(A, B, out, bias, state)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\torch\autograd\function.py", line 506, in apply
    return super().apply(*args, **kwargs)  # type: ignore[misc]
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\bitsandbytes\autograd\_functions.py", line 303, in forward
    CA, CAt, SCA, SCAt, coo_tensorA = F.double_quant(A.to(torch.float16), threshold=state.threshold)
  File "A:\game storage\MonikA.I\libs\pythonlib\lib\site-packages\bitsandbytes\functional.py", line 1634, in double_quant
    nnz = nnz_row_ptr[-1].item()
RuntimeError: CUDA error: an illegal memory access was encountered
CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.

i'm not really sure where to go from here, maybe i need to reinstall something or if i just need to start over.
thanks!

nevermind i figured it out, turns out i had to turn off int8 quantization as my GPU was not compatible.


Add druid mana bar

In wow classic, a druid needs to control mana all the time(for change form). We need sth like druid bar classic

Already added.


@conda-forge-admin, please add bot automerge

@conda-forge-admin, please add bot automerge

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/npx-feedstock#2.


White space first of =* operator

Version
2.14.2
Details
Hi,
I am using GridifyAsync for finding the records which some field contains some string starting with whitespace, but it ignores the first white space of that string.
e.g. I want to look for " Something" on column error:
error Like =* Something
the sql would be like:
SELECT *
FROM tbl_Log
WHERE Error Like '% Something%'

but it search for all strings in error column which has "Something".
Steps to reproduce

Step 1
make some table with string column
Step 2
search using below expression:
error Like =* Something

Hi @MrSEKIRO,
Thank you for the feedback. this is a known issue, You can find a temporary workaround  here
But I'll try to fix this issue in the next versions

For my case it just return the result if there Is no spaces and trimming is not needed.
I should wait for next version.
Tnx.

I just tested the leading space behavior and noticed you can escape it if needed. so another workaround would be this:
Like =*\ Something

But I'm also considering adding a new configuration to disable the AutoTrim feature. what do you think?

That may work but in my case I am doing some translations to Gridify filters and it won't fit well.
How about using quotations for Contains filters like that?

That may work but in my case I am doing some translations to Gridify filters and it won't fit well. How about using quotations for Contains filters like that?

If you mean something like this Error=*' Something' it will cause another problem, what if you want to search for a string that contains ' instead of space ... so basically it doesn't change anything and probably makes it worse because we need two escapes instead of one in that case. Error=*\' Something\'


Move/Change the maturity curve visual

I would recommend that you would move the maturity curve visual to be above the descriptions of the levels. Also the visual do not contain the levels that you describe, either change the headings or change the visual.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 42a648bf-51ec-f9da-6c4f-d721616fcdb1
Version Independent ID: 7bdb8bfa-289e-bee5-bc45-a0a6fb78d5ff
Content: Integrate data management and analytics into your cloud adoption strategy - Cloud Adoption Framework
Content Source: docs/scenarios/data-management/strategy.md
Service: cloud-adoption-framework
Sub-service: scenario
GitHub Login: @BrianBlanchard
Microsoft Alias: brblanch

Fixed in
commit 848996c477e05f653efc61bc9b4509ba99fc822f (HEAD -> collab-data-mesh-v1, origin/collab-data-mesh-v1)
Author: Simon Lidberg<EMAIL_ADDRESS>Date:   Wed Mar 2 14:23:36 2022 +0100
Move/Change the maturity curve visual #751

https://github.com/MicrosoftDocs/cloud-adoption-framework-pr/pull/3059

#please-close


Create/delete clusterpool

https://github.com/open-cluster-management/cm-cli/issues/38
Signed-off-by: Dominique Vernier<EMAIL_ADDRESS>

/hold

/unhold


how to select the most confident keypoint for pnp?

"when on the Occlusion dataset we only keep l = 10 most confident keypoints and abandon other low-confident keypoints".
hi~ I wonder how you select the most 10 confident keypoint for pnp? what's the confidence based on ?
I can't find the relevant code, could you give me some help?
best wishes.

confidences are defined by the values of kp heatmaps


Fix coverage reporting.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[x] Have you successfully run brew tests with your changes locally?

This should make coverage reports more credible.

Coverage is 63.26%, seems about right. 😄


Hard to see search options on mobile

When I go to the site on mobile with Chrome, and click on the search button, it brings up results without showing me what I searched for.  Is there a way to show the search criteria plus the results, like we have on the desktop view?

@jbskolnik @SciStarter this isn't working as expected. That should bring up a search form. Somewhere in all the change this got messed up. Have to look into it more.

changes made. should be good now.


don't drop completion popup

function test(e:{id:Int, itemId:Int, index:Int}):Void
{
	e.| <- don't drop completion popup
}

Do you mean, "The completion dialog never appears?"
Please provide some details: Version of plugin; version of IDEA (including Ultimate or CE); your OS.

Yes.
v.plugin: 0.10.0 for IDEA 16 - https://github.com/eliasku/intellij-haxe/releases/tag/v0.10.0-beta
Ultimate 2016.2, win 10


Add Kirikkale University

Kirikkale University > kku.edu.tr

@mehmetincesu I am sorry, the domain kku.edu.tr is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


Getting started ... in what development environment?

I am interested in writing a desktop Windows app and heard that Winforms is a good way to go. I came to this "Getting Started with Windows Forms" page hoping to get some info about how to start ... and yet I can't find where it even mentions a development environment. Do I need some version of Visual Studio? Help!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 82facee6-f1e6-f2aa-56c2-967708b2389f
Version Independent ID: cb2a1803-98a7-7900-bf20-281b6c55197e
Content: Getting Started with Windows Forms
Content Source: docs/framework/winforms/getting-started-with-windows-forms.md
Product: dotnet-framework
Technology: dotnet-winforms
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Yes, you need Visual Studio to develop WinForms applications. It's been available for many versions of Visual Studio if you want to use .NET Framework for your development. We're revisiting the WinForms documentation for the next release of .NET Core, so the prerequisites should be made more clear as well as having better get started materials.
For new development though, we do recommend that people use .NET Core to develop new applications with. @OliaG can you comment on the state of the designers on Visual Studio if folks want to develop a new WinForms app?


Create codeql-analysis.yml

https://github.com/A3ew3/merge-conflicts.git[](url)

A3ew3-patch-1


”Lungani” is listed in the drop-down menu

Description:
"Lungani" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Lungani" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Lungani, IAȘI".


#issue 5 Home page navbar

Have made a bootstrap navbar.

Thanks @taniyeahh7 , we will be merging this PR
Your contributions are appreciated!


Fix ordering of grid ids in torsion drive (FB) metadata

Description
This PR fixes a potential bug whereby the grid ids included in the metadata.json prodcued by the force balance TorsionProfileTargetFactory were ordered differently then in qdata.txt and scan.xyz.
This PR also adds a missed NotImplementedError when trying to fit forces using the force balance ab initio target.
Status

[X] Ready to go

The test failures are unrelated and should be fixed by #24 so I'll go ahead and merge this.


Feature request: set sys.stdout = None with --disable-console

On Linux, one can usually print stuff to a console. In Windows, with --disable-console, one cannot - at least, no one will see it.
With pyinstaller, sys.stdout is None in this case, which can be used to show output by other means (write to a log file, show a message box, ...). This seems to be in line with what pythonw.exe does, according to their documentation: https://github.com/pyinstaller/pyinstaller/commit/89c120e0ac3694a8707c5e850c0246328f632ac1
Also compare:
python.exe  -c "import sys; f = open('stdout_python.txt',  'w'); f.write(str(sys.stdout))"
pythonw.exe -c "import sys; f = open('stdout_pythonw.txt', 'w'); f.write(str(sys.stdout))"

more stdout_*.txt
<_io.TextIOWrapper name='<stdout>' mode='w' encoding='utf-8'>
None

So it seems to quite standard to have with sys.stdout == None in some cases.
Long story short, I think it would be useful to have sys.stdout = None with --disable-console in Nuitka as well.
(Same for stderr, I guess.)

The fact that pythonw.exe does this is indeed evidence of what it should be. However, I am not convinced that the reason people disable the console is that they tested their program with pythonw.exe or even know what it is.
But I accept that definitely this is something that should be supported. Maybe the forced output paths could allow doing that, since that will also affect non-Windows.
I think, it's also a shortcoming of __compiled__ that these modes are not all recognizable there. Otherwise a workaound that distiguishes console vs. no-console mode would be doable.

With #2038 we will probably revamp how console is handled, would be nice to get the options naming sane at that point.

I think, it's also a shortcoming of compiled that these modes are not all recognizable there. Otherwise a workaound that distiguishes console vs. no-console mode would be doable.

I generally agree with you that code should not need to know whether it runs in Nuitka or not (have read this elsewhere), so I don't actually think it has to be recognizable. I usually recognize if sys.stdout is useable by, well, checking sys.stdout is None. If that is ensured, I am happy :) Everything else is icing on the cake, but for the record, nothing that I would need. (Writing portable code implies one should only do things that one could do, for example, in pythonw.exe as well.)

Well, Nuitka has made sys.stdout usable. It redirects to NUL: though, which is barely a problem.
Compatibility is paramount to Nuitka, otherwise the differences get arbitrarily hard to debug.

Well, Nuitka has made sys.stdout usable.

Yes, sure - I should have been more exact. I probably meant "useful" :) while sys.stdout redirecting to NUL is usable, it's hardly useful, especially if it's not easy to see from the outside if is redirecting. Anyway, using __compile__ works of course - not super-elegant, but pragmatic enough.

Unless of course, you as a Python developer test your program with python.exe and one day, maybe after a dependency upgrade, the compile program starts crashing. I am defending it as a default, not as the only offer naturally. I guess this and the solution will be part of typical problems in the user manual soon.
But no worries, this option will soon be available. I just need to make my mind up, how the whole console business should be arranged. I am thinking that None may just be a value for the forced outputs in some form, obviously specific to these options I guess.
For obvious reasons, Nuitka doesn't really want to run with pythonw.exe itself (even raises an error dialog box if you try), so there has be a mode where you indicate that you want that.

I added support for the following things to factory version.
For all platforms, now --force-stdout-spec="%NONE%" will put the None value to sys.stdout. There is also --force-stderr-spec for sys.stderr.
Also, for all platforms, now %NULL% is available as a value too. That puts a file backed by os.devnull there. Previously and still now, this is done when disabling the console on Windows.
The forcing options do not yet cover sys.stdin. That is still doing the os.devnull stuff. I might add this as a feature too in the future, but I wasn't immediately aware if this even makes sense for None. I added that to avoid crashes in the past as well.

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

For the record: this is working fine on the develop branch. Thanks!

Since I am looking forward to this feature, may I ask if 1.6 will be released soon (as indicated by the recent rc9) or is that still far out (as indicated by the milestone, https://github.com/Nuitka/Nuitka/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.6)?

This is part of the stable release 1.6 that I just made.

Beautiful, thanks ;)


(PUP-5954) Make class merge an error

Before this, if a class was defined more than once their bodies would be merged. The output of a warning or error was under the control of the --strict flag.
Now, this is always an error except for the top scope class named '' (a.k.a 'main').

CLA signed by all contributors.

I dropped the commit that removed the << method. Instead I marked the entire class as @api private. I know that is not 100% correct - there are probably tools out there that need to use its methods. But I thought it was at least best to put up the "do not walk on the grass" sign.


change this to Any (capitalized) from the typing module

https://github.com/bessagroup/rvesimulator/blob/420db1b9b9b6800006a06689cb645cc71873bfe4/src/rvesimulator/additionals/ampitudesampler.py#L28

fixed


Parsing string into json doesn't preserve the order correctly.

Describe what you want to achieve.
I want to parse a json file from the web, downloaded into a string using libcurl, back into a json object.

Describe what you tried.
Image of code
This is what I've tried - the former cout prints the string that curl downloaded, which is in the correct order of the original json on the webserver. The second cout simply posts the same json but as a json object, which has been parsed by nlohmann::json. As you can see, it is completely jumbled up. When trying to access a nested part of the json, for example ["teams"]["players"] it returns null and crashes with error 305, cannot use operator[] with a string argument. If you need any more information please don't hesitate to reply.

Describe which system (OS, compiler) you are using.
VS2015 (v140) on Windows 10

Describe which version of the library you are using (release version, develop branch).
release

This is known: https://github.com/nlohmann/json#order-of-object-keys

Ok, but does this solve how to access nested Json elements? or is that something unrelated?

for example I want to access these parts, but it returns null with error 305

Does j["teams"][0]["players"][0]["name"] work?

Yes, that works a charm! Thanks so much! This may seem like a silly question, but what does the [0] actually do there? Thanks again.

It accesses the first element of an array, just like for a std::vector.

To be fixed with #2258.


KYC Order Book

KYC order book scenarios:

User not logged in:
Don't show KYC orders.
User logged in not KYC'd
Don't show KYC orders, only non-KYC orders
User has multiple KYC tokens
Show all non-KYC orders and all KYC orders the user owns KYC token for.

Will it be possible for KYC users to take KYC orders and create non-KYC orders?

@bthaile we should set some time aside next week to talk through this.

@justinbarry lets bring in @nuevoalex so he can check if the description makes sense.

Anyone can make or take non KYC orders.
I don't believe we should do any work on this for V2 launch personally. (Can be done after)

iced


Display message if user does not hold any stock or have sold all of t…

showing a proper message to the user.
Not showing stocks having quantity 0.

#206


InstrumentedExecutorService does not unregister metrics, nor expose a way to do so

InstrumentedExecutorService registers several metrics in its constructor, but they are never removed.  It is debatable whether shutdown/shutdownNow would be appropriate to hook into to unregister.  If it is not, then it would be up to the user of InstrumentedExecutorService to unregister them; however, doing so requires the caller to know the internals of InstrumentedExecutorService because it does not expose it's metrics.
I propose either exposing some sort of unregister method, or exposing the metrics/metric-names themselves.

My work-around has been to explicitly remote the metrics I know the InstrumentedExecutorService sets up in my own tear down method.

@Trinition Could you please describe your use case for unregistering these metrics?

Sure!
I have a system with various components that are started or stopped during it's normal course of operation. Some of those components are dynamic, and some use thread pools which I want to instrument.  So when such a component starts, I want it initializes an InstrumentedExecutorService named with the component's name, and I start getting metrics for it while that component is active.  When the component is done, it shuts down and ends its threadpool. But the metrics live on because InstrumentedExecutorService does not remove the metrics it had registered. As more components start and then stop, the registry becomes full of "dead" metrics for thread pools that won't come back (because they're dynamically named, even if the same type of component is activated again, the metrics have different names).

Any update on this? :)
I have a use case where I have to initialize a InstrumentedExecutorService with the same name and MetricRegistry, because the service was restarted.
With the newer updates of metrics, I see that there is now the register method used in the InstrumentedExecutorService , which makes my application throw the  following expection:
java.lang.IllegalArgumentException: A metric named my-metric already exists

For my use case it would actually be enough to reuse existing metrics by, for example, replacing
registry.register(MetricRegistry.name(name, "pool.size"), (Gauge<Integer>) executor::getPoolSize);

with
final MetricRegistry.MetricSupplier<Gauge<Integer>> supplier = () -> executor::getPoolSize;
registry.gauge(MetricRegistry.name(name, "pool.size"), supplier);

I would be willing to create a PR for all metrics, if this suggestion would be approved :)

@gitseti not sure I understand the status of the fix you've merged long time ago.
Did it reach actually some released version ?
If not, is there any workaround for this ?
Trying to upgrade, and have too many duplicate registration cases of InstrumentedExecutorService


No error thrown if push to blocked branch on GitHub

We have a repository, where pushing direct to branch master is protected by GitHub (configured on settings page).
When trying to push branch master from local repository to master on GitHub (via nodegit), expected result is to have an error thrown or an error code, that represents an error.
But, instead, it doesn't throw an error and doesn't return any error codes, they are undefined. Which is successful push, regard to nodegit documentation.
It took a lot of time to figure out why push was successful from nodegit perspective, but no changes on GitHub as a result.
Here is the code I'm using to push:
const errorCode = await remote.push([
        'refs/heads/master:refs/heads/master'
    ], {
    callbacks: {
        certificateCheck: () => 1,
        credentials: gitCredentialsCallback,
        transferProgress: gitTransferProgressCallback(remoteUrl)
    }
});

The issue was resolved by allowing push into master, of course, but the behavior of nodegit in this case is embarrassing and could lead to unexpected decisions, when debugging such case.

@ghaiklor Did you try setting a callback pushUpdateReference callback? The callback will be used to report whether the remote accepted or rejected the reference updates.
const errorCode = await remote.push([
        'refs/heads/master:refs/heads/master'
    ], {
    callbacks: {
        certificateCheck: () => 1,
        credentials: gitCredentialsCallback,
        transferProgress: gitTransferProgressCallback(remoteUrl)
        pushUpdateReference: function(refname, message) {
          console.log(refname + "\t" + message);
        }
    }
});

@rcjsuen no, I didn't. Let me check this and report asap.

@rcjsuen yep, it worked, thanks for pointing me to the right direction. My final solution turns out to be:
    // @see https://github.com/nodegit/nodegit/issues/1445
    // Since, we can't throw an error inside of callback, I've forced to have this flag to indicate errors
    let doesErrorOccur = false;
    const errorCode = await remote.push(refSpecs, {
        callbacks: {
            certificateCheck: () => 1,
            credentials: gitCredentialsCallback,
            transferProgress: gitTransferProgressCallback(remoteUrl),
            pushUpdateReference: (refname, message) => {
                if (message && message.length > 0) {
                    logger.error(chalk.red(`[${remoteUrl}]: ${refname} -> ${message}`));
                    doesErrorOccur = true;
                }
            }
        }
    });


Add Plex Discover Support

Can you add support for Plex Discover ?

Hi @fscorrupt, can you describe the kind of support you are looking for ? I just want to be sure to understand the use case you have in mind.

Hey, yeah sure.
with the new discover feature you can now search in plex for every movie/show, even if its not in your lib, it would be nice to have plugin support on the discovery page to make requests directly from plex web.

Love this idea btw :)

I've added Plex Discover support in the version v1.3.0 of the extension. Please try it out and let me know if everything works as expected. Enjoy ! 😃

wow, that was fast 😅
will have a look tomorrow!
thanks

hey, played a bit today works really well!
But i found a Show that does get request as another one..

This one was a tough one as Plex uses its own identifiers for movies and tv shows so I was using a title based search that can lead to mismatches like the one you mentioned.
After some experiments I found a way to extract the TMDB id from Plex and it seems to do the trick. If any of you can give me some feedback it would be great, thank you in advance ! (Make sure your extension is updated to v1.3.1 beforehand)

thanks again for the fast fix, I will test it intensively in the next few days! Rg

tried a bit with version 1.3.2.
i get on every show and movie media not found.

this is the complete Url: OuterRange
and i have X-Plex-Token with my token in it.

Fixed it with adding my server ip to custom server access url. it now works without problems. Thanks again!


Cannot build with Genesis Code

I tried building my game, it worked like a minute ago i swear.
Here's the log:

Which version of SGDK are you using?
Please note that built-in functions names may change from one SGDK version to another.
You may check changelog and SGDK inc folder to confirm that function VDP_setPaletteColor still exists under this name.

Thanks, resolved :D


Fix: Add CancellationScheduler option

Motivation:

#5683 is related to this issue.

Modifications:

Add CancellationScheduler option

Result:

The default value for the Cancellation option is false. Enabling this option enables Cancellation.
(Is this what you intended?)

Let me check a little more.
I'll end this PR.
I'm sorry.


Item settings (part 2)

Motivations
Allow modifying most of the item parameters through interface (take the design branch as an example)
Subtasks
In item edit, in an "Advanced parameters" tab: (as in "Settings" in the design branch)

a "Score & Validation" section, only for chapters and skills

"Validation criteria" with choices "Never", "All children validated", "All children but one validated", "All 'Categories' children validated", "One children validated"; matching 'None', 'All', 'AllButOne', 'Categories', 'One' of validation_type
no_score, "Disable score", switch true/false

"Display" section, for any type of items (all types but skills)

title_bar_visible, "Display header (not implemented)", switch  true/false
prompt_to_join_group_by_code, "Display group code header  (not implemented)", switch true/false
full_screen, "Full screen (not implemented)":     No/Based on type/Yes mapped to forceNo,default,forceYes

Fixed by #316


[Batch mode] Pass true to write_escaped.

A fix for supplementary file maps with weird characters in filenames.

@swift-ci please test source compatibility

@swift-ci please smoke test

Thanks. Yes, trying to get this in ASAP, assuming it works.

@davidungar Is this the fix for: rdar://problem/38642478 Swift CI: 2. Swift Source Compatibility Suite (master) - Siesta?

That’s a fix to one issue that kept this test from passing. But I think there’s another. AFAIK, the PR that caused siesta to fail has been reverted. I’m working on bug #2. Won’t be doing more for the next few hours, though.

David

On Mar 19, 2018, at 5:14 PM, Andrew Trick<EMAIL_ADDRESS>wrote:
@davidungar Is this the fix for: rdar://problem/38642478 Swift CI: 2. Swift Source Compatibility Suite (master) - Siesta?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Aha, there's an llvm::yaml::escape that we really should have found a while ago.

Thanks!

On Mar 20, 2018, at 8:58 AM, Jordan Rose<EMAIL_ADDRESS>wrote:
Aha, there's an llvm::yaml::escape that we really should have found a while ago.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/apple/swift/pull/15340#issuecomment-374652479, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcJ0AzvfHisDG59XgcBsrB_RoLTXg_rks5tgSdBgaJpZM4Swmi3.


Swap Bower with Yarn and other improvements

Commits are fairly verbose. No breaking changes.
Bower is deprecated, and Yarn is a "drop-in" replacement.
Moved all external js to npm dependencies.
I'm delaying the move from ionicons font to svgs due to styling issues.
Edit: commits affect different things, better not squash them.

@migueldemoura Awesome work!! Was planning on ditching Bower as well. Big thanks :-)


newsletter subscription

What does this PR do and why?
Provide a description of what this PR does. Link to any relevant GitHub issues, Notion tasks or Discord discussions.
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #3196   👈

This comment was auto-generated by Graphite.


downloadFile and uploadFile ignore headers object

Describe the bug
When downloading or uploading a file from a protected resource and sending an authorization header (or any other headers) the native iOS code doesn't use the headers to build the request.
Environments

[ ] Android
[x] iOS

To Reproduce
const options: any = {
      url: https://your-host/proteced-download,
      name: 'file',
      filePath: filePath,
      headers: {
        Authorization: `Bearer ${accessToken}`
      }
 };

Http.uploadFile(options)

Expected behavior
Both HttpDownloadFileOptions and HttpDownloadFileOptions extend HttpDownloadFileOptions which has the headers object as an optional parameter. The download/upload functions should accept the headers object like it does on Android.

Fixed already in capacitor-v3


CAMEL-17763: cleaned up unused exceptions in test code (nats)

The failure is not caused by this change, so I'll go ahead and merge it.


dist/react-waterfall.js is empty

Hi @didierfranc, looks like something went wrong during the latest release as of 21cbd0d dist/react-waterfall.js is empty.

Thanks this must be fixed ;)


Issue #1358: Add server_connect_end in slow log

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/1257/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/1364/ for details.

👍 - Looks good


Implementing Domain-Driven Design

https://www.jianshu.com/p/5ab2fa9d3892

已立项 https://github.com/gdut-yy/Implementing-Domain-Driven-Design-zh


Added legacy support for SNS.

Signed-off-by: AWSHurneyt<EMAIL_ADDRESS>Issue #, if available:
Added legacy support for SNS.
Description of changes:
CheckList:
[x] Commits are signed per the DCO using --signoff
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

These tests are failing because the 2.4 common-utils artifact isn't available yet. I manually published the common-utils with the SNS assets locally, and ./gradlew build.

Seems that the 2.4 distribution build is currently failing for several plugins.

Codecov Report

Merging #597 (3c79d4b) into main (2c7c652) will decrease coverage by 0.69%.
The diff coverage is 58.49%.

@@             Coverage Diff              @@
##               main     #597      +/-   ##
============================================
- Coverage     76.99%   76.29%   -0.70%
+ Complexity      178      116      -62
============================================
  Files           167      127      -40
  Lines          8576     6480    -2096
  Branches       1270      932     -338
============================================
- Hits           6603     4944    -1659
+ Misses         1337     1056     -281
+ Partials        636      480     -156

Impacted Files
Coverage Δ

...ain/kotlin/org/opensearch/alerting/AlertService.kt
78.19% <ø> (ø)

...rg/opensearch/alerting/BucketLevelMonitorRunner.kt
77.44% <ø> (ø)

.../opensearch/alerting/DocumentLevelMonitorRunner.kt
81.91% <ø> (ø)

...ain/kotlin/org/opensearch/alerting/InputService.kt
94.28% <ø> (ø)

...org/opensearch/alerting/QueryLevelMonitorRunner.kt
79.48% <ø> (ø)

...n/kotlin/org/opensearch/alerting/TriggerService.kt
73.21% <ø> (ø)

...search/alerting/action/AcknowledgeAlertResponse.kt
94.44% <ø> (ø)

...pensearch/alerting/action/ExecuteMonitorRequest.kt
100.00% <ø> (ø)

...ensearch/alerting/action/GetDestinationsRequest.kt
100.00% <ø> (ø)

...nsearch/alerting/action/GetEmailAccountResponse.kt
92.50% <ø> (ø)

... and 67 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Enable dynamic starting room

I've done some small changes to the world.py and game.py files to allow custom StartingRoom positions within map.txt. This should open up the option for custom maps to be made and played with without having to worry about the starting coordinates assigned within the Player class.
This is my first time using GitHub as a beginner python programmer, any advice and comments are greatly appreciated.
Have fun!!

Hi Victor,
Thanks for the pull request. This is a good idea, I think it would make the program more flexible. I have some suggestions on your implementation.

There doesn't seem to be much use in storing _game_map. Why not just record the starting position during the parsing of the map when the StartingRoom is encountered?
The Player class current initializes the player's position, but you're moving that into the game. the player's position should be initialized in just one place. I don't have an opinion on where, but having two player location initializations is confusing.

Feel free to make another commit and I can review the changes. Thanks!

Hi Phillip,
Thanks for taking the time to read through my changes. I've taken your suggestions into consideration and have made some changes to the program.
I've actually re-written your source for this tutorial in python 2 instead of just forking it. The commits here are copied from my repo with the ported source. The reason being I've just finished the python course from codecademy which was based on python 2.
In your opinion, would it be a good idea for me to move to python 3 or remain in python 2 as a beginner?

I've looked over these updates and everything looks good except for the variable name change I suggested. Once that's corrected, I should be able to merge these changes in. To be clear, you are OK with me updating the tutorial to match these changes, correct?
As for Python 2 vs 3, I don't see any reason to stick with 2. Python 3 came out in 2008! If you absolutely need to use a library that is only 2.7 compatible, then you have to use Python 2. But for the vast majority of projects, Python 3 is going to be fine.

OK. The variable name has been changed. Go right ahead with the tutorial update. I think it would be a good example of how the 'starting_position' variable can be defined as a Global variable which can be accessed from outside the function. It's something new and useful that I've learned and would love to share it with other beginners.
Will make another pull request when I have time to make more changes. Thanks again for the info and advice! =)