Update operation does not remove object from array

Describe the bug
The onetable doesn't overwrite array of objects and instead try to set each field in the object during update operation. Example: in database I could have 2 photos in the array, so during update user can change the name and remove one photo from array and I would expect the update operation to just overwrite the array but instead it tries to update fields in the object and it never remove item from array. Same issue happens when I pass empty array, none of photos are removed, as this is update operation I would expect to overwrite array and not try to update object each field in the array. Is this expecting behaviour?
Right now I have to do something like this, but if I have multiple arrays I need to do it for each array.
    const {photos, ...dynamoEntityWithoutPhotos} = dynamoEntity;

    const result = await fromPromise(
      this.db.update(dynamoEntityWithoutPhotos, {
        remove: ['status'],
        log: true,
        // TODO: I need to set below because empty array is not pick it up by onetable??
        set: {photos: dynamoEntity.photos},
      }),
      (error) => error as OneTableError,
    );

Update operation log
{
  "cmd": {
    "ConditionExpression": "(attribute_exists(#_0)) and (attribute_exists(#_1))",
    "ExpressionAttributeNames": {
      "#_0": "PK",
      "#_1": "SK",
      "#_5": "name",
      "#_6": "photos",
      "#_7": "key",
      "#_8": "createdAt",
      "#_11": "updatedAt",
      "#_12": "id"
    },
    "ExpressionAttributeValues": {
      ":_2": {
        "S": "90ddfd76-d8ef-4a71-b381-56b95e741847/855f95eb-a7b4-45fc-8487-fe86e3af6220.png"
      },
      ":_3": {
        "S": "2024-01-19T11:06:54.225Z"
      },
      ":_4": {
        "S": "image/png"
      },
      ":_5": {
        "S": ""
      },
      ":_6": {
        "S": "2024-01-18T21:18:23.475Z"
      },
      ":_7": {
        "S": "2024-01-19T11:12:45.963Z"
      },
      ":_10": {
        "S": "Fix Vent Fan"
      }
    },
    "TableName": "dev-home",
    "ReturnValues": "ALL_NEW",
    "UpdateExpression": "set #_6[0].#_7 = :_2, #_6[0].#_8 = :_3, #_6[0].#_9 = :_4, #_6[0].#_10 = :_5, #_8 = :_6, #_11 = :_7, #_12 = :_8, #_5 = :_10",
    "Key": {
      "PK": {
        "S": "HOME#90ddfd76-d8ef-4a71-b381-56b95e741847"
      },
      "SK": {
        "S": "PROJECT#23633923-3bc4-47f3-8027-950590213c80"
      }
    }
  },
  "items": [
    {
      "createdAt": "2024-01-18T21:18:23.475Z",
      "updatedAt": "2024-01-19T11:12:45.963Z",
      "id": "23633923-3bc4-47f3-8027-950590213c80",
      "name": "Fix Vent Fan",
      "photos": [
        {
          "key": "90ddfd76-d8ef-4a71-b381-56b95e741847/855f95eb-a7b4-45fc-8487-fe86e3af6220.png",
          "createdAt": "2024-01-19T11:06:54.225Z",
          "contentType": "image/png",
          "comment": ""
        },
        {
          "key": "90ddfd76-d8ef-4a71-b381-56b95e741847/cbfc2ffa-a745-4788-8c3b-7cb007673911.png",
          "createdAt": "2024-01-19T11:06:54.225Z",
          "contentType": "image/png",
          "comment": ""
        }
      ],
    }
  ],
  "op": "update",
  "properties": {
    "photos": [
      {
        "key": "90ddfd76-d8ef-4a71-b381-56b95e741847/855f95eb-a7b4-45fc-8487-fe86e3af6220.png",
        "createdAt": "2024-01-19T11:06:54.225Z",
        "contentType": "image/png",
        "comment": ""
      }
    ],
    "createdAt": "2024-01-18T21:18:23.475Z",
    "updatedAt": "2024-01-19T11:12:45.963Z",
    "PK": "HOME#90ddfd76-d8ef-4a71-b381-56b95e741847",
    "SK": "PROJECT#23633923-3bc4-47f3-8027-950590213c80",
    "id": "23633923-3bc4-47f3-8027-950590213c80",
    "name": "Fix Vent Fan",
    "type": "Project"
  },
  "params": {
    "exists": true,
    "parse": true,
    "high": true,
    "remove": [
      "status"
    ],
    "log": true,
    "checked": true
  }
}

Schema
const schema = {
  format: 'onetable:1.1.0',
  version: '1.0.0',
  indexes: {
    primary: { hash: 'PK', sort: 'SK' },
  },
  models: {
    Project: {
      ...schemaBase,
      PK: { type: String, value: 'HOME#${homeId}', required: true },
      SK: { type: String, value: 'PROJECT#${id}', required: true },
      id: { type: String, required: true },
      name: { type: String },
      photos: {
        type: Array,
        required: true,
        default: [],
        items: {
          type: Object,
          schema: {
            key: { type: String, required: true },
            createdAt: { type: String, required: true },
            contentType: { type: String, required: true },
            isHero: { type: Boolean },
            comment: { type: String },
            hasMoved: { type: Boolean },
          },
        },
      }
    }
  } as const,
  params: {
    ...schemaParamsBase,
  },
};

Depends on your settings of partial. If partial is true (the default now), it updates nested objects and arrays partially.
You can provide {partial: false} for the schema or for one API to override for that API and do an update of the top level property (array) and not element by element.


Having this error while launching the model from command prompt

When I try to generate images from the command prompt, I get this error.
What can be the issue?
File "C:\SHARK\shark\examples\shark_inference\stable_diffusion\main.py", line 104, in
unet = get_unet()
File "C:\SHARK\shark\examples\shark_inference\stable_diffusion\opt_params.py", line 72, in get_unet
return get_shark_model(bucket, model_name, iree_flags)
File "C:\SHARK\shark\examples\shark_inference\stable_diffusion\utils.py", line 58, in get_shark_model
return _compile_module(shark_module, model_name, extra_args)
File "C:\SHARK\shark\examples\shark_inference\stable_diffusion\utils.py", line 23, in _compile_module
shark_module.load_module(vmfb_path, extra_args=extra_args)
File "C:\SHARK\shark\shark_inference.py", line 209, in load_module
) = load_flatbuffer(
File "C:\SHARK\shark\iree_utils\compile_utils.py", line 314, in load_flatbuffer
return get_iree_module(flatbuffer_blob, device, func_name)
File "C:\SHARK\shark\iree_utils\compile_utils.py", line 288, in get_iree_module
ModuleCompiled = ctx.modules.module[func_name]
File "C:\SHARK\shark.venv\lib\site-packages\iree\runtime\system_api.py", line 168, in getitem
raise KeyError(f"Function '{name}' not found in module '{self}'")
KeyError: "Function 'forward' not found in module '<BoundModule <VmModule module : []>>'"

similar issue for me:
Traceback (most recent call last):
File "gradio\routes.py", line 337, in run_predict
File "gradio\blocks.py", line 1015, in process_api
File "gradio\blocks.py", line 833, in call_function
File "anyio\to_thread.py", line 31, in run_sync
File "anyio_backends_asyncio.py", line 937, in run_sync_in_worker_thread
File "anyio_backends_asyncio.py", line 867, in run
File "models\stable_diffusion\main.py", line 221, in stable_diff_inf
File "shark\shark_inference.py", line 136, in call
File "shark\shark_runner.py", line 90, in run
File "shark\iree_utils\compile_utils.py", line 362, in get_results
File "iree\runtime\system_api.py", line 168, in getitem
KeyError: "Function 'forward' not found in module '<BoundModule <VmModule module : []>>'"
Keyboard interruption in main thread... closing server.

Typically means your compile failed. Does your system have 16G or less system RAM ?
We are making some improvements to reduce memory usage

the shark_tank folder to delete can be found at
C:\Users<Your_USERNAME>.local\shark_tank

Everything works fine now, thanks for the updates and improvements!


Tasks imported from a package created with the fractal-tasks-template don't include information from meta file

Hi,
I tried to make a package from a few tasks I've created using the fractal-tasks-template. Everything went fine up until running the tasks that I collected from the package in fractal. The issue I run into is that the template does not specify any of the information usually included in the task meta-file.
Also, when tasks are collected from a package, the user that imported them is not the owner of the task, meaning that they can't be edited (and therefore I can't add a meta-file via the fractal client).
Did I maybe miss some step in the template creation (I tried to adhere to the instructions, but maybe something slipped by me or was not well documented)?
Thanks!

Thanks for reporting!
Did you add a meta property to the task in the manifest? This should be done by hand, as there is no obvious way for the template to guess what to put there.
This means e.g. modifying the manifest as in
{
  "manifest_version": "1",
  "task_list": [
    {
      "name": "Thresholding Task",
      "executable": "thresholding_task.py",
      "input_type": "zarr",
      "output_type": "zarr",
      "meta": {                                                  # START OF NEW BLOCK
        "cpus_per_task": 4,
        "mem": 16000,
        "parallelization_level": "image"
      },                                                         # END OF NEW BLOCK
      "args_schema": {
        "title": "ThresholdingTask",
        "type": "object",
        "properties": {
          "input_paths": {
            "title": "Input Paths",
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Path to the parent folder of the NGFF image. This task only supports a single input path. (standard argument for Fractal tasks, managed by Fractal server)."
          },
          "output_path": {
            "title": "Output Path",
            "type": "string",
            "description": "This argument is not used in this task. (standard argument for Fractal tasks, managed by Fractal server)."
          },
          "component": {
            "title": "Component",
            "type": "string",
            "description": "Path of the NGFF image, relative to `input_paths[0]`. (standard argument for Fractal tasks, managed by Fractal server)."
          },
          "metadata": {
            "title": "Metadata",
            "type": "object",
            "description": "This argument is not used in this task. (standard argument for Fractal tasks, managed by Fractal server)."
          }
        },
        "required": [
          "input_paths",
          "output_path",
          "component",
          "metadata"
        ],
        "additionalProperties": false
      },
      "docs_info": "Short description of thresholding_task.\n\nLong description of thresholding_task.",
      "docs_link": "https://example.com"
    }
  ],
  "has_args_schemas": true,
  "args_schema_version": "pydantic_v1"
}

@adrtsc does this solve your issue?
In terms of documentation, here are some possible improvement

Explicitly mention that this step is to be done by-hand, in the instructions (this is useful).
Maybe also include an empty meta property in the default manifest, so that the user can guess where new properties should go.

@adrtsc do you see these changes as sufficiently helpful?

Also, when tasks are collected from a package, the user that imported them is not the owner of the task, meaning that they can't be edited (and therefore I can't add a meta-file via the fractal client).

This is a known current behavior; maybe it will change in the future (discussion started at https://github.com/fractal-analytics-platform/fractal-server/issues/1084).

Hi @tcompa, I see, indeed I did not put the meta property in my manifest manually. I think your suggestions would be perfectly suitable to keep people from running into the same thing in the future.
Thanks!

Instructions fixed as of version v0.1.2 of this template.
Note that the version is visible when you run copier:
$ copier copy gh:fractal-analytics-platform/fractal-tasks-template your-package-name
🎤 Your full name (used in the project metadata)
   Your Name
🎤 Your email address (used in the project metadata)
<EMAIL_ADDRESS>🎤 Name of your project (prefer hyphens to underscores)
   my-project
🎤 Name of your top-level Python package (the one appearing in Python `import` statements)
   my_project
🎤 A URL for your project home page or documentation (optional)

🎤 A short description of the package
   Package description.

Copying from template version 0.1.2                    # <------------ see here
 identical  .
 identical  LICENSE
 identical  pyproject.toml
 identical  src
 identical  src/my_project
...

(I'm mentioning it in view of future changes, even if in this case nothing really changed apart from the README)

Great, thanks for updating the documentation for this @tcompa ! And thanks for reporting it @adrtsc !


ES - Invalid Memory Handle When Restarting/Deleting an Application with Tables (GSFC DCR 14483)

When you delete an application that uses tables (e.g. HK) and then restart another task (e.g. SC) for a second time, the ES task writes to the system log that there are invalid memory handles.

Seems like when tables get unregistered is where the errors are happening. Message says it got a bad pointer for this table, not sure if the app in messed up. This problem is not isolated to RestartApp. It occurs in DeleteApp as well. What it looks like is that the linked list is not getting cleaned up properly when an app is deleted or restarted.

Further investigation in the CFS Lab narrows the problem down to the RemoveAccessLink function in cfe_tbl_internal.c. The errors are being generated on table handles from the deleted app. The buffer that is trying to be placed back into the pool is set to NULL because it has already been put back into the pool. The tables that were "cleaned up" still contain the AppID of the deleted app. When the subsequent app is restarted, its AppID becomes that of the deleted app and inherits the table handles from the previous app. For example, the HK app has 2 tables and the SC app has 73 tables. When HK is deleted, the 2 tables are removed and the entries still contain the AppID of HK. When SC is restarted, it becomes the AppID that HK was. The reason the errors occur on the 2nd restart is because on the first restart SC had a unique AppID. On the second restart, it has inherited HKs original AppID. In this case, you will see 2 sets of errors when SC is restarted. The SC application did not show any adverse functionality because of these errors. All that is happening is that the PutPoolBuf function is reporting an error when trying to return a NULL buffer to the pool.

Imported from trac issue 90.  Created by sstrege on 2015-08-27T13:59:18, last modified: 2019-07-03T12:48:08

Trac comment by glimes on 2016-10-18 15:00:28:
redispatching these tickets to clear my name from the "owner" field,
so people willing to work on tickets will not think that I am already
working these issues ;)

Trac comment by glimes on 2016-11-08 14:17:08:
Current crop of cfe-next are all going into CFE 6.6

Trac comment by gdecaruf on 2018-02-08 15:27:04:
Ran into exact same issue.
the culprit is that the UsedFlag isn't checked when looping over Handles.  This leads to the call to CFE_TBL_RemoveAccessLink to fail in cfe_tbl_internal.c:1450 (CFE_TBL_CleanUpApp) because the restarted app was reassigned to the AppID that was previously owned by the other app that has been shutdown.  And so when it loops over the Table handles, it incorrectly tries to remove the access link to a tbl registry that has already been cleared previously.
Fix is to add Check for UsedFlag == TRUE
{{{
/* Check to see if the Handle belongs to the Application being deleted */
if (CFE_TBL_TaskData.Handles[i].AppId == AppId &&
CFE_TBL_TaskData.Handles[i].UsedFlag == TRUE)
...
}}}

Trac comment by jhageman on 2019-07-03 12:48:08:
Moved unfinished 6.6.1 issues to next minor release

Trac comment by gdecaruf on 2018-02-08 15:31:59:
What are the repercussions in a current build that doesn't have this fix?  Is it dangerous?  It seems to only fail with the memory access error and keep going.


Should we add "trojan-source" code detection?

Hey!
There are a paper about "trojan-source" attack and tool for detecting it.
Should we add a new warning for this attack?
If so, I can prepare PR for it.

Hello 👋,
This has already been implemented few months ago: https://github.com/NodeSecure/js-x-ray/pull/16

Awesome!
I haven’t seen it.


Change references from dcaf soft pledge to fund pledge

I rule and have completed some work on Case Manager that's ready for review!
I removed soft pledge and replace with #{FUND} pledge
I also replaced DCAF with the FUND constant where I could.  I figured we would want to continue to remove as many references in the code to DCAF as possible so that it will be easier to port over to other funds.  However, it is a bit out of scope, so let me know if you want me to revert any of it or move it to a new PR.
This pull request makes the following changes:

replaces all instances of soft pledge with #{FUND} pledge
replaces some instances of DCAF with #{FUND}
removed DCAF from the names of the pledge limit environmental variables (NOTE: these will need to be updated in Heroku as well)

It relates to the following issue #s:

Fixes https://github.com/DCAFEngineering/dcaf_case_management/issues/1125

Codecov Report

Merging #1158 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #1158   +/-   ##
=======================================
  Coverage   95.22%   95.22%
=======================================
  Files          52       52
  Lines        1151     1151
=======================================
  Hits         1096     1096
  Misses         55       55

Impacted Files
Coverage Δ

app/controllers/external_pledges_controller.rb
96.29% <ø> (ø)
:arrow_up:

app/helpers/patients_helper.rb
100% <100%> (ø)
:arrow_up:

app/controllers/patients_controller.rb
100% <100%> (ø)
:arrow_up:

app/models/concerns/pledgeable.rb
100% <100%> (ø)
:arrow_up:

app/models/user.rb
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@colinxfleming your changes are in and tests are passing!


Wrong video orientation in Kinesis Stream

Hi,
I am using Kinesis Video for live as well as on demand video playback in an android application. One thing i am stuck on now is getting wrong orientation while playing the video url.
AndroidCameraMediaSourceConfiguration.builder()
.withCameraId(String.valueOf(cameraId))
.withEncodingMimeType("video/avc")
.withHorizontalResolution(320)
.withVerticalResolution(240)
.withCameraFacing(1)
.withIsEncoderHardwareAccelerated(true)
.withFrameRate(FRAMERATE_20)
.withRetentionPeriodInHours(RETENTION_PERIOD_48_HOURS)
.withEncodingBitRate(BITRATE_384_KBPS)
.withCameraOrientation(0)
.withNalAdaptationFlags(StreamInfo.NalAdaptationFlags.NAL_ADAPTATION_ANNEXB_CPD_AND_FRAME_NALS)
.withIsAbsoluteTimecode(false));
Above is the configuration for media. Please help!

If anyone know the solution for this, please help! I have been stuck on this since a long time now.

Hi @gerahimanshu,
We're tracking this request with issue aws/aws-sdk-android#544.


TPI: Improve debug config selection in Flask

Refs: https://github.com/microsoft/vscode-python-debugger/issues/161

[ ] macOS @meganrogge
[ ] linux @jrieken
[ ] windows @devinvalenciano

Complexity: 3
Create Issue

Automatically detect a Flask file, and show it.
Steps

Open a Flask Project if you already have one or you can also create one following the steps in the Flask Tutorial.

Head over to the Run And Debug tab, and click on create a launch.json file.

A window will open with a list of options, choose Python Debugger > Django.

Verification

Valid flask file

Verifies that your flask config file was found correctly and is displayed in the list.
When you hover the item, verify that there is a button to open the file and that it works correctly.
Select this option and verify that a launch.json configuration is created with the choose option.

Invalid flask file (you can delete or change the name of the file)

Since no file was found, verify that a Default option is displayed.
Select this option and verify that a launch.json configuration is created with the choose option.

Browse a file

Click on the option Browse Files... and select the file that you want.
Verify that a launch.json configuration is created with the choose option, and that the path has been parsed correctly.

Add own value

You can also include your own text, type a path in the input box and press enter.
Verify that a launch.json configuration is created with the choose option.

Notes
Flask's application detection works by looking for the wsgi.py, app.py and init.py files in the root or in a subdirectory just one level lower and looking for them to have the declaration of a flask application app = Flask(. So you can try moving the python file and changing the name, and check that the detection still works.

A window will open with a list of options, choose Python Debugger > Django.

@paulacamargo25 Are you sure about "Django"? Shouldn't it be "Flask"?

A window will open with a list of options, choose Python Debugger > Django.

@paulacamargo25 Are you sure about "Django"? Shouldn't it be "Flask"?

Yes sorry, i just update the description


Working with planets?

Space Engineers requires DirectX11 for planets.
Does this affect the Dedicated-Server as well?
Am I able to go with wine 1.7.30+ and planets?

server in wine is currently broken, but because a different issue more information

I don't think the Forum is right and everything will be fine with 64bit.
Since it fails to load the planets map (and asteroids works fine) I guess it is likely the DX11 dependency.

directx11 is not a requirement for the server, that would be horrible for server providers if they would need a graphics card ;)
i just tested myself, the 32bit version runs out of memory when creating a world with the EarthEasyStart preset, even on my personal windows machine
BUT when you create the world with 64bit under windows and copy that to the linux machine the server starts up just fine

but as you can see, you still run into memory issues :/
and unless dotnet40 will start supporting 64bit, we won't be able to run the 64bit server ever

Hm, so we need to wait for a x64 .NET version, if it ever comes.
btw, nice Solarized theme tho ;)


Game calls SDL_Quit but not SDL_Init

The Game class calls SDL_Quit in the destructor, but has no corresponding SDL_Init in the constructor.

SDL documentation references:
SDL_Init
SDL_Quit
SDL_InitSubSystem
SDL_QuitSubSystem

Tagging #701 as likely related.

I believe Init is done in the Renderer. It's not intuitive and I'm game for finding a better way to do this.

Tagging #810 as possibly related.


Getting more done in GitHub with ZenHub

Hola! @skeswa has created a ZenHub account for the skeswa organization. ZenHub is the leading team collaboration and project management solution built for GitHub.

How do I use ZenHub?
To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.
What can ZenHub do?
ZenHub adds a series of enhancements directly inside the GitHub UI:

Real-time, customizable task boards for GitHub issues;
Burndown charts, estimates, and velocity tracking based on GitHub Milestones;
Personal to-do lists and task prioritization;
“+1” button for GitHub issues and comments;
Drag-and-drop file sharing;
Time-saving shortcuts like a quick repo switcher.

Add ZenHub to GitHub
Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @skeswa.

I'll agree, but only if we can call it trello

Re-opening this for visibility sake, should probably put this in the readme or wiki?


OpenLayers v5

The changes required should be fairly small:

Update imports in src/ol-layerswitcher.js to match ol v5 convention
Update globals in rollup config
Update/ test examples in this repo to use v5
Update/ test walkermatt/ol-layerswitcher-examples
Update README with a note about version compatibility
Bump major version
Release

WIP support for OpenLayers v5 in ol5 branch. Also see ol5 branch of ol-layerswitcher-examples repo for usage.
If you'd like to test in a project that uses OpenLayers v5 you can update the ol-layerswitcher dependency in package.json to use the ol5 branch in the repo:
"ol-layerswitcher": "git+https://github.com/walkermatt/ol-layerswitcher.git#ol5"


Fix path for eksa admin image project in presubmit

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Title: Navbar enhancement

Initiative (Required)
GSSoC 2024 Extd 🚀
Is your feature request related to a problem? Please describe.
The navbar looks too big and much designs are also not present. I want to design the navbar a bit and add effects for precision.
Please assign the issue to me and also add labels of hacktoberfest-accepted, gssoc-extd,and levels.
Describe the solution you'd like.
HOVER EFFECT TO BE ADDED TO NAVBAR.
BREADTH OF NAVBAR NEEDS TO BE DECREASED.
Add any other context or screenshots about the feature request here.
No response

I am the mentor of this project.
@ABHISIKTAcommits Hello
I appreciate your pull issue , can you give screenshot after update the output.


run error

Manifest merger failed : Attribute application@appComponentFactory value=(androidx.core.app.CoreComponentFactory) from [androidx.core:core:1.0.0] AndroidManifest.xml:22:18-86
is also present at [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91 value=(android.support.v4.app.CoreComponentFactory).
Suggestion: add 'tools:replace="android:appComponentFactory"' to  element at AndroidManifest.xml:7:5-117 to override.

Downgrading to 6.1.1 solved it for me. Maybe it's because they added AndroidX support in 7.0.0.

I think it only supports newer version of react-native. They should probably update the docs.

Adding below two lines in gradle.properties file fix this error but lead to more new errors.

android.useAndroidX=true
android.enableJetifier=true


Change from static to dynamic github app teams

dynamically generate a list of the application teams to be added to our repo from the json files, rather than using a static list that needs to be updated on new account creation.
modify the workflow to run on json file changes
update documentation

Well this is pretty awesome!


Add custom weapons and tools/ add these functions

ModPE.setWeapon(id,texture,textureData,name,maxAttack,maxDamage)
Block.setLevel(id,level)
ModPE.setPickaxe(id,texture,textureData,name,maxDamage,blockLevel,speedToBreakBlocks)
for example if the level is at or below the block may be obtained
ModPE.setAxe(id,texture,textureData,name,maxDamage,speedToBreakBlocks)
ModPE.setShovel(id,texture,textureData,name,maxDamage,speedToBreakBlocks)
speed to break blocks is the time to break a block between the speed to break blocks
ModPE.setHoe(id,texture,textureData,name,maxDamage)
Block.setType(id,type)
1-wood
2-dirt
3-stone
sorry for bad English

Why are you stealing my ideas?

Block.setType -> the Material pointer when constructing a new block
I'll look into the rest.

@sero583 That was never my intention
but if this was your first idea would be as implementing it
sorry for bad English


Bump to django-pandas 0.6.6.

@cshaley or @sannykr
Could you bump the releases for this feedstock? The most recent version on conda-forge (v0.6.1) is broken for Django>=4.0 (see here for example bug)
It looks like a bot has made some pull-request for this, but they haven't been looked at:
https://github.com/conda-forge/django-pandas-feedstock/pull/7
https://github.com/conda-forge/django-pandas-feedstock/pull/6
https://github.com/conda-forge/django-pandas-feedstock/pull/5
https://github.com/conda-forge/django-pandas-feedstock/pull/4

I'd be a willing maintainer for this package as well. Feel free to ignore if you want to limit who's on the maintainer list.
@conda-forge-admin, please add user @jacksund


Feature/apply standard js before commit

This is included in https://github.com/blueinkhq/blueink-client-js/pull/22


Notebooks: Internal Document Links Not Functional

Azure Data Studio Version: 1.13.1

CPUs
Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (4 x 2808)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwareoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_deferred_display_list: disabled_offskia_renderer: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (6.68GB free)

Process Argv

Screen Reader
no

VM
0%

Extension
Author (truncated)
Version

powershell
ms-
2019.11.0

whoisactive
Mic
0.1.2

sql-search
Red
0.3.4

Steps to Reproduce:

Create a internal document anchor
In a different cell create a link to the anchor [link](#regrets)
clicking the created link does not navigate to the document anchor but instead opens a second tab called workbench.html with the following content:

<!DOCTYPE html>

		<meta charset="utf-8" />

		<meta http-equiv="Content-Security-Policy" content="default-src 'none'; img-src 'self' https: data: blob: vscode-remote-resource:; media-src 'none'; frame-src 'self' https://*.vscode-webview-test.com; object-src 'self'; script-src 'self' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; connect-src 'self' https:; font-src 'self' https: vscode-remote-resource:;">

What kind of document are you trying to do this in? notebook, markdown? etc.

Apologies: in a Notebook.

The following table shows what is supported by Jupyter in terms of linking to document parts or Heading.

Markdown syntax for linking to a section in   notebook
Markdown syntax for the section that it will jump   to

[this link works   using "a id"](#cream)
CREAM!   or   CREAM!

[this link works   using "a name"](#ice)
ICE!   or   ICE!

[this link works   for Headings](#Introduction)
# Introduction

[this link works   for Multi-word Headings](#Ice-Cream)
# Ice Cream

[this link works   for Heading Level 2](#My-chocolate-Ice-Cream)
## My chocolate   Ice Cream

[Duplicated   Heading will always goes to the first one](#My-chocolate-Ice-Cream) `
## My chocolate   Ice Cream ## My chocolate   Ice Cream

File to repro:
Anchors.zip
``

I was just trying on my Mac, and am trying to get a full picture of what works today 😄:

Markdown syntax for linking to a section in notebook
Markdown syntax for the section that it will jump to
Works Today?

this link works using "a id"
CREAM! or CREAM!
Yes

this link works using "a name"
ICE! or ICE!
No

this link works for Headings
# Introduction
Yes

this link works for Multi-word Headings
# Ice Cream
Yes

this link works for Heading Level 2
## My chocolate Ice Cream
Yes

Duplicated Heading will always goes to the first one `
## My chocolate Ice Cream## My chocolate Ice Cream
No

I'll update this when we've added more support

@chlafreniere On my Windows, I still get workbench.html as reported at the beginning of this issue for both Insiders and standard build.
Version: 1.16.0-insider (user setup)
Commit: 9f9c65591d58c2999a72268e38e176f802fa184d
Date: 2020-03-09T05:48:25.421Z
VS Code: 1.42.0
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Version: 1.15.1 (user setup)
Commit: 83544eba2504f564d785534cc780d2073feec2cc
Date: 2020-02-15T05:03:16.545Z
VS Code: 1.42.0
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363

Moving to April for the other relative document links. Will also remove the Approved label to prevent confusion 😄

@barbaravaldez - it seems that if the reference/link and the linked item are on the same cell, and the linked item is at the bottom of the text cell and ADS window is short, clicking on the item seems to not work well. Can you please help investigate?


Prepare to define success metrics

Description:
Work with program area to determine what success looks like for this project and how we hope to achieve and measure that success.
Acceptance Criteria:

[ ] Connect with Lindsay to discuss success metrics
[ ] Review initial work/thought that went into CIF KPIs
[ ] Define project goals
[ ] Define what success means for the project
[ ] Establish clear priorities & nice-to-haves
[ ] Set up session with program area to discuss success and determine metrics

Notes:

We can probably leverage some of the initial work/thought that went into CIF in terms of how we want to organize and achieve success. We can start by identifying our big goals/key objectives and then determine KPIs that will help measure our success.

I think as a starter, we could look into the objectives outlined in the project charter and determine KPIs/metrics that would help measure those objectives.

Idea from Matthieu:

Gather thoughts from stakeholders before and after project to see if we've improved.
Evidence that a new system is needed (surveys)

Idea from Mike: How has exposure changed?

@jaimiebutton, Would like to work with you on this ticket

https://bcgov.sharepoint.com/:p:/t/00608-ScrumTeam/EQ-u576ro8BEqgrahI5IZoEBUTBVmUzfwkLGlftsYBrpEQ

Here are some more ideas for metrics:

At least x interviews per sprint
Complete theme analysis for at least x interviews done in a sprint
Review x reports/resources (desk work) per sprint
At least x ministries involved in research
At least x indigenous organizations consulted
Final deliverable delivered
Reach operators from x different industries
Project delivered on time
Met goals per sprint

Great, I have added these to the pptx.

Critical Success Factors from the Project Charter:

Team resources and co-location
User-centered design principles
Agile / scrum framework with a focus on user-centric service design
Realistic schedule agreed upon by the project team
Clear objectives and goals
Ongoing communication and engagement with Stakeholders, Project Team, and users
Time commitment from all stakeholders

Note: not completed during initial research and discovery phase. Removed from Project Planning EPIC to capture in potential future work.


OpenGL debug labels not getting displayed.

When running my application and setting object labels using  glObjectLabel, the object labels do not displayed in the respective pipeline state view. Is there something I"m missing to get this to work?

Which object types are you naming? The objects that should get names picked up for them are renderbuffers, textures, buffers, program pipelines, programs, and shaders.
Testing just now on a sample, it seems like nvidia's driver is barfing when trying to name buffer objects, even though everything looks valid to me. I'll need to check on AMD but I think it's just wrong. It worked fine for me on a texture and programs/shaders/etc.
On replay I can store object names in my own data structures rather than storing them in the driver, which also means you don't need KHR_debug on replay.

I'm naming: vertex, index, render buffers, frame buffer objects and textures.
Was the Nvidia driver complaining when you try to label an object prior to binding? If so, the AMD driver will do the same thing on Core Contex.

Looks like that's the case - I was using a sample program that added labels, and it was indeed calling glObjectLabel right after glGenBuffers.
It would still be nice to make it work even in spite of that, since I can just apply the names myself. But if that isn't the problem you're running into then it seems like everything works for me. Apart from FBOs that aren't displayed directly in the UI, so there'd be no place to name them anyway.
Can you provide any repro details? Either the program or a frame capture?

The program has too many dependencies to package up right now...so I'll just submit the capture.
labeltest.zip

Right, it's definitely some issue with storing the names in the driver, other than an unrelated shader issue the capture opens fine for me an buffers & textures are named:

(the weird misalignment on the CLODTerrainSMTexture_3_00 is because there's a \n in the name - I suspect that's not deliberate).
I think it's clear the solution is to store the names myself and not rely on the driver implementation at all, that should fix all of this. I'll do that today.

I forgot to mention that I was running the latest stable version 0.32, and I'm not seeing what you are seeing and the other way around too. Are you running the test with the nightly build or the latest stable? Thanks for looking into the issue.
Also I'll remove the extra newline char from the name .

I tried on v0.32 as well as recent code, it seemed to behave the same. I've got a fix I'll push up later today that you can check out in the next nightly.

...thanks.

That commit changes it to store the object names internally instead of also using KHR_debug for naming on replay. It worked for me (e.g. it let me use names that were applied before binding), but let me know how you get on with the next nightly build.

Just got a chance to test with RenderDoc_2017_02_15_a70bcb8a_64 nightly release and the object labels are now showing up correctly. Thanks!!!!


Unused validation repeats value in v1-finetune.yaml

The code for personalized.py only uses the repeats setting for the training set. Seems like the extra repeats setting under validation is a copy-paste oversight.
# configs/stable-diffusion/v1-finetune.yaml

validation:
  target: ldm.data.personalized.PersonalizedBase
  params:
    size: 512
    set: val
    per_image_tokens: false
    repeats: 10  # <--- unused?

Speaking of which, what is the rationale for going over the dataset multiple times in an epoch? Does it improve training accuracy somehow or is it just a way to avoid running the validation test too often (10:1 ratio instead of 1:1)?

On the topic of repeats, I wasn't sure if
data = instantiate_from_config(config.data)
Should be repeated twice in a row in https://github.com/rinongal/textual_inversion/blob/main/main.py#L749

The repeats are used in both cases. They are a dirty hack to ensure that pytorch-lightning doesn't explode if you use a very small (1-2 image) dataset where your batch size is larger than the number of available images.
Since we're anyhow counting training steps and not epochs, and since the lengthy part of the validation step is independent of this value (the image outputs part), it shouldn't have much of an impact on your training times.
If you're using a very large training set you can lower the repeats value.
@CodeExplode That's a bug. I'll fix it.

If we're trying 300+ training images, would a repeat of 1 seem reasonable?


how does updating vault work this way?

Thank for the helpful module, I was wondering how would you update/upgrade vault in this model without loosing data and interrupting the service?

Hi @medyagh
Thanks for the question. The data is stored in GCS, so you can safely upgrade the Vault version (change the Terraform variable) and then run terraform plan and terraform apply. This will create a new instance group manager with the newer Vault version, then delete the old instance group manager.

would this not destroy the bucket on every deployment?
https://github.com/priyeshgpatel/terraform-google-vault/blob/86b003d9b6992e59e060281cc62709b2ccabf7de/examples/vault-on-gce/main.tf#L56


Change the input/output for barcodes

Although it will break the compatibility with previous versions (although they are pre-releases), I would like to output the barcodes in the read name when several barcodes with a separator between them (like that, they could be retrieved separately to test other approaches.
Some helpers are already implemented on f6803ebf444da7adb11dc0bef82b8fe648f6aa7d

The barcode input file should have a new formatting to include the library for each sample in a column (mostly for BamBarcodeDetector)

Implemented in commit a86af6f629f3d8bf3b0629521b0256508e29aaa0

The first suggestion is not implemented, only the different input file.

Added separator in read name behavior, but important TODO (bug) in BarcodeOptions line 166 (5fef1ea). It should be fix.

Implemented and tested in commit 0f45c3665254be0a45f2aac53b357dc3ac3597d8. The bug is solved by changing the *BarcodeDetector classes instead of the BarcodeOption to retrieve the combined dictionary if I will needed someday.


[raudio] Rewritten ExportWaveAsCode() file saving to be more like rtextures ExportImageAsCode()

The current ExportWaveAsCode() has some various bugs/inconsistencies:
The data array name will list the entire path to the file. I don't know if ':', '/', and '\' are valid symbols in C var names but I made it so only the file name without its path and extension are listed. Also, note the missing file names before the wave data information preprocessor defines, and the unusual data array var name casing.
Before:

After:

@RadsammyT Thanks for the review! :)


Incoherent result

When comparing 2 lists for example [1,1,1,1] and [1,1,1,1] the expected kendall tau result as far as i know should be 1 however when running stats.kendalltau the result is nan.

x and y in a 2-d diagram is just a point, the slope of a correlation is not determined.
>>> np.corrcoef(np.ones(5), np.ones(5))
array([[ nan,  nan],
       [ nan,  nan]])

same should be true for other correlation/association measures like kendalltay


workspace: uefi (main library) is in a dedicated directory now

This implements the ideas discussed in #564.
Checklist

[ ] Sensible git history (for example, squash "typo" or "fix" commits). See the Rewriting History guide for help.
[ ] Update the changelog (if necessary)

I do not understand why https://github.com/rust-osdev/uefi-rs/actions/runs/3455556833/jobs/5767663192 fails. I'm seeking your advice @nicholasbishop

I do not understand why https://github.com/rust-osdev/uefi-rs/actions/runs/3455556833/jobs/5767663192 fails. I'm seeking your advice @nicholasbishop @GabrielMajeri

Add resolver = 2 to the [workspace] section as described in https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions. That should resolve the error since the alloc feature won't be enabled for that test.

I do not understand why it builds in the CI but no longer locally..
   Checking uefi-services v0.15.0 (/home/pschuster/dev/other/uefi-rs/uefi-services)
    Checking uefi-test-runner v0.2.0 (/home/pschuster/dev/other/uefi-rs/uefi-test-runner)
    Checking uefi_app v0.1.0 (/home/pschuster/dev/other/uefi-rs/template)
error: language item required, but not found: `eh_personality`
  |
  = note: this can occur when a binary crate with `#![no_std]` is compiled for a target where `eh_personality` is defined in the standard library
  = help: you may be able to compile for a target that doesn't need `eh_personality`, specify a target with `--target` or in `.cargo/config`

error: could not compile `uefi_app` due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `uefi-test-runner` due to previous error

Any idea? cargo clean also doesn't help. I tested multiple nightly versions..

Are you running cargo check? That's not something the CI runs. Since there's no longer a top-level package it's now checking the whole workspace instead of of just the uefi package. This was already broken before your change, you just would have had to run cargo check --workspace to see the error. I think it's fine for it to remain broken for this PR, we could look at fixing that command separately.

Very cool! I'm glad we could merge this.


Model.find() with empty argument has an unexpected return

await Model.find(/*null or undefined*/) is returning the same as await Model.first()
So when one writes await Model.find(req.params.id) on Express with an empty id, it will inadvertently show or edit the wrong object.
Maybe it's best to return undefined, just like when finding by a primary key value absent from DB. Like if the query were select * from model where id is null limit 1.

Wow, that totally got unnoticed for a while!
Thanks for finding this bug. I'll fix it, give me a moment.

fixed with version 2.8.5
Thanks @arthurfranca


lagom / executor / driver refactor

Refactor the experiment function, executors and drivers.
This PR seeks to disentangle hyperparameter optimization, ablation studies and distributed training code. With the addition of more features to Maggy the code becomes confusing if it is not split into distinct units. As a first step, the lagom function and associated functionality was rewritten. Since the implications of changing the lagom function concern the whole module, the changes are substantial. In order to make changes retraceable, I give a short summary of each file with the respective changes. It will be easiest to check the files of the PR in the order they are given in this summary.
Disentangling the lagom function:

maggy/experiment.py: Experiment now acts as a simple wrapper around the different lagom functionalities. It sets up basic info such as the IDs and still contains the error handling. Now takes a config object instead of the previous parameters since some keywords make no sense in the distributed setting, but are necessary for optimization.
maggy/experiment_config.py: The config classes for lagom.
maggy/core/lagom/: Contains lagom_optimization.py, lagom_ablation.py and lagom_distributed.py. These are the target functions for the dispatcher in experiment.py. Splitting the code introduced some redundancy, but I'd rather have slightly similar scripts than a large, entangled single script. Might be able to reduce redundancies further in future versions.
maggy/distributed/: Since experiment now dispatches for all modes, the special treatment of distributed is no longer necessary and the folder was deleted.
maggy/core/executors/Executor.py: The Executor class previously acted as a dispatcher for the kind of monkey-patching that was to be performed on the training function. Since dispatching has been delegated to experiment.py, the Executor class is no longer necessary.
maggy/core/executors/dist_executor.py: Adaption to the use of EnvSing() introduced by #76 and minor changes.
maggy/core/executors/trial_executor.py: Minor changes to keep consistency with dist_executor.py.

Refactoring the drivers

maggy/core/experiment_driver/Driver.py: The base class driver previously contained all the message digestion logic for hyperparameter training as well as several hp tuning specific functions. The new driver instead lets child classes register callbacks for the message types they want to support and starts this general message digestion thread. Also switched to config based initialization instead of keyword arguments.
maggy/core/experiment_driver/OptimizationDriver.py: Moved most of the message digestion logic into optimization driver. Now defines and registers a callback for each message type for the digestion thread. Also moved several functions specific to hp tuning to the OptimizationDriver. Switched to config initialization.
maggy/core/experiment_driver/AblationDriver.py: Switched to config initialization. Simplified initialization logic and switched to config.
maggy/core/experiment_driver/DistributedDriver.py: Removed all code that was necessary to maintain compatibility with the previous version of the base driver. Adapted callback schema and config based initialization.

Miscellaneous changes

maggy/core/rpc.py: Linting changes to conform with global variable name style.
maggy/util.py: Added two functions to keep hops out of maggy dependencies. Fixed a bug from #88 .
examples/notebooks: Adapted notebooks to new lagom syntax.

Known issues
Ablation tests are still ongoing, so far there seems to be an issue with the heartbeat.

It looks good to me, I tried it with tensorflow in my vm and works.

Why were there still calls to hopsutils and experiment_utils in the code? I converted those calls to EnvSing, pretty sure..

It was in the first commit then you change them in the next commit. I didn't see it at the beginning but then I saw it and marked the comments as 'resolved'

Gridsearch is tested and should work.


SHOW INDEX FROM executed on PostgoreSQL database

(and SQLSTATE[42601]: Syntax error)

Can you provide more information please.
Post the statement?

We have the same error here, basic when we try to export a PostgreSQL database we have same kind of syntax error.

I added update v2.0.3
This has an update that should fix that issue.
Regards,
Jon

Testing this version 2.0.3 following this previous error, I had the following message:

Thanks for the update Alex.
I will setup a PostgoreSQL database and do further testing.


Update with content purpose supergroup and subgroup

Update the schemas with content_purpose_supergroup and content_purpose_subgroup. Deprecate content_purpose_document_supertype.

@fmlharrison @vanitabarrett I think the examples need to be updated as well.

@leenagupte Spoken to Steve - I don't think the examples need to be updated now, but perhaps as a  later separate PR when it comes to adding some test coverage for the supergroups/subgroups?

@vanitabarrett sounds good.


Detect and handle changes in etcd info

The connection and cert info for etcd can change and needs to trigger the service config being updated and the service restarted.

LGTM. Does this need testing?

Actually, one thing I just noticed, and am unsure about, is how calico-kube-controllers handles the cert changing (see here). Hopefully, it will just enter a crash loop until the new cert is written, at which point it should recover on its own.
Will need to check for that in testing, I think.

Fixed calico-kube-controllers not restarting when it should.
Tested as described in https://github.com/charmed-kubernetes/charm-kubernetes-master/pull/34#issuecomment-510186591
Ready for review.


fix: add "submitNewOrderList" method and related types

Summary

Add submitNewOrderList() because New OCO is deprecated on Binance API.
Make sumbitNewOrder() and replaceOrder() generic to have correct report type for the response.
Add missing types of workingTime, selfTradePreventionMode and transactTime.
Add missing fields W and V to the executionReport.
Add the OrderResponse type for convenience.
Add generic OrderResponseTypeFor<T> for a better developer experience. Please take a look at the example below.
Add typing for "OCO" methods having any.
Add baseUrl to the WSClientConfigurableOptions, so it can be used to subscribe to SpotUserDataStream on Testnet. Closes #414
Detach types: CancelRestrictions, CancelReplaceMode
Prevent repeated inline use of SelfTradePreventionMode

Example
Thanks to the new generic type, the new submitNewOrderList method returns a response with the exact TypeScript type based on the newOrderRespType parameter. If newOrderRespType is not provided, it defaults to the minimum ACK, not to mislead the developer.
// See https://binance-docs.github.io/apidocs/spot/en/#new-order-list-oco-trade

const responseA = await client.submitNewOrderList({ ...args, newOrderRespType: "FULL" });
const executedQtyA = responseA[0].executedQty; // responseA has correct type of "OrderResponseFull"

// TypeScript will warn the wrong type for the below code
const responseB = await client.submitNewOrderList({ ...args, newOrderRespType: "ACK" });
const executedQtyB = responseB[0].executedQty; // TYPING ERROR: responseB is type of "OrderResponseACK"

const responseC = await client.submitNewOrderList({ ...args }); // Defaults to "OrderResponseACK"

const responseA = await client.submitNewOrder({ ...args, type: "MARKET" }); // FULL
const responseB = await client.submitNewOrder({ ...args, type: "MARKET", newOrderRespType: "ACK" }); // ACK

const responseC = await client.submitNewOrder({ ...args, type: "STOP_LOSS" }); // ACK
const responseD = await client.submitNewOrder({ ...args, type: "STOP_LOSS", newOrderRespType: "FULL" }); // FULL

NOTE: I could have divided the features into multiple PRs, but since some of the changes modified the same files, I didn't want to mess with Git conflicts, so I divided them into multiple commits.

@tiagosiebler, I will surely increase the version number.
I will try to find a way to implement the generic type to the sumbitNewOrder(). It is tricky.

MARKET and LIMIT order types default to FULL, all other orders default to ACK.

@tiagosiebler. I also made sumbitNewOrder() and replaceOrder() generic.
const responseA = await client.submitNewOrder({ ...args, type: "MARKET" }); // FULL
const responseB = await client.submitNewOrder({ ...args, type: "MARKET", newOrderRespType: "ACK" }); // ACK

const responseC = await client.submitNewOrder({ ...args, type: "STOP_LOSS" }); // ACK
const responseD = await client.submitNewOrder({ ...args, type: "STOP_LOSS", newOrderRespType: "FULL" }); // FULL

@tiagosiebler, I'm updating the first message in this PR when I update the PR, so you can use it for documentation purposes when you merge it.

@tiagosiebler, could you please review the PR? It's getting bigger. I want to continue adding further fixes in separate PRs, but they may depend on this PR.

@tiagosiebler, could you please review the PR? It's getting bigger. I want to continue adding further fixes in separate PRs, but they may depend on this PR.

Hey, I will need some time to review (currently travelling). Will review it soon. In the meantime, I suggest making another branch in your fork based on the branch you're currently working on. This way you're building on top of this PR without directly adding more commits to this PR/branch.

Hey, I will need some time to review (currently travelling). Will review it soon.

I wish you a nice trip. FYI, I'm using the version with PR applied in a small personal project, no problem so far.

Amazing work, looks great to me! Thanks for all the time you spent in improving this!

Happy to contribute, and thank you for publishing this great library.


[OL3.0.0] dynamic-data with a png icon

Replacing  the circle Style in the dynamic-data sample  by a iconStyle (see code below)
doesn't work.
var iconStyle = new ol.style.Style({
  image: new ol.style.Icon(/** @type {olx.style.IconOptions} */ ({
    anchor: [0.5, 46],
    anchorXUnits: 'fraction',
    anchorYUnits: 'pixels',
    opacity: 0.75,
    src: 'my.png'
  }))
});

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

#5777


Accessing globals in macros (again)

The solution of passing a _context was a bit overkill as it passes too much data. It doesn't just pass globals, it's passing in local variables. I'm defining globals as the set of key/value pairs returned by the getGlobalVariables method overridden on the class AbstractExtension. These are the true global variables.
    @Override
    public Map<String, Object> getGlobalVariables() {
        final Map<String, Object> globals = new HashMap<>();
        globals.put("DATE_TIME_FULL", DateFormat.FULL);
        globals.put("DATE_TIME_LONG", DateFormat.LONG);
        globals.put("DATE_TIME_MEDIUM", DateFormat.MEDIUM);
        globals.put("DATE_TIME_SHORT", DateFormat.SHORT);
        globals.put("DATE_TIME_NONE", -1);
        return globals;
    }

In that same AbstractExtension class I'm providing a filter, which I expect to use those globals with.
    @Override
    public Map<String, Filter> getFilters() {
        final Map<String, Filter> filters = new HashMap<>();
        filters.put("dateTime", new DateTimeFilter());
        return filters;
    }

I encounter the classical globals/macros issue when I trey to wrap my filter into a macro, and within that macro use any specified global. I only want transparent and easy access to the TRUE globals, instead, I have to munge up with a _context parameter...
{% macro printDate(timezone, timestamp, _context) %}{{ timestamp ? (timestamp | dateTime(timezone, _context.DATE_TIME_LONG, _context.DATE_TIME_NONE)) : "-" }}{% endmacro %}

versus
{% macro printDate(timezone, timestamp) %}{{ timestamp ? (timestamp | dateTime(timezone, DATE_TIME_LONG, DATE_TIME_NONE)) : "-" }}{% endmacro %}

Requested fix: please make getGlobalVariables truly global without requiring usage of _context.

Sounds like a good idea

I've opened a pull request for this.

I've opened a pull request for this.


removing handlers

Thank you for creating this library! I have a suggestion to enhance its functionality by allowing handlers to be removed.
The reason for this proposal is to address issues encountered when using handlers in a persistent manner within durable objects. Currently, it seems there's no way to remove listeners, which necessitates reinstantiating the client. This can lead to memory leaks and corrupted handlers.
Here are a few potential solutions, each with its own advantages and disadvantages:

Change handler arrays to protected:

Remove the private enforcement on the SlackApp handler arrays and change them to protected.
This would enable users to implement the removal of listeners at their discretion.
It wouldn’t affect the library's runtime and would maintain backward compatibility with existing users.

Use WeakRefs in the handler arrays:

Implement WeakRefs inside the arrays and validate the references before calling them.
This approach allows the garbage collector to manage memory efficiently, preventing leaks.
Although this requires a significant amount of code changes, it maintains backward compatibility and keeps the private attributes intact.

Add methods to facilitate handler removal:

Introduce new methods in the library specifically for removing handlers.
While this would require additional code changes and testing, it would also increase the library’s size.

By implementing one of these solutions, the library can better handle persistent use cases, preventing memory issues and enhancing overall stability.

Hi @gabewillen, thanks for the suggestion! I still don't fully understand why you think this is beneficial. Let me ask a few questions:

when using handlers in a persistent manner within durable objects

What is an example of a platform or scenario for this? More specifically, I'd like to understand what "durable objects" are.

which necessitates reinstantiating the client

What do you mean by "client" in this context?
It's indeed feasible to enable developers to access the array, but specifying the handler to remove could be complicated as they don't have easy-to-access IDs. Can you share a pseudocode demonstrating how your desired use case looks?

Thank you for your prompt response. Our situation is quite unique. Ideally, we would utilize a web application, but due to time constraints and our frontend team being occupied, we opted to develop a Slack app instead. In retrospect, I'm not entirely convinced it was the quicker option 😅.

when using handlers in a persistent manner within durable objects

What is an example of a platform or scenario for this?

Durable objects refer to a feature provided by Cloudflare that offers persistent, transactional storage. You can find more detailed information here: Cloudflare Durable Objects.
We created an evaluation app for RLHF, which is used by our team members to grade responses directly in Slack. Although there are numerous other methods we could have employed to achieve similar functionality, the durable objects have been adequate given our tight deadlines and the typical startup urgency for rapid development.

which necessitates reinstantiating the client

What do you mean by "client" in this context?

case involves our middleware, which uses your libraries internal authentication but also connects the Slack user to our internal database. With the use of durable objects, this connection process only needs to happen once. Although we could exit the middleware handler after the user lookup with a simple if-statement, the function would still be invoked, thereby consuming a small amount of computing resources unnecessarily. Ideally, we would remove this listener after the user is identified. Another example is the "app_home_opened" callback, which is used to initially load the view when a user opens the home tab. After this initial interaction, the handler is no longer needed due to subsequent user interactions.

It's indeed feasible to enable developers to access the array, but specifying the handler to remove could be complicated as they don't have easy-to-access IDs. Can you share a pseudocode demonstrating how your desired use case looks?

Given our specific requirements and the numerous arrays that store these handlers, I believe altering the API surface might not be the most practical solution. That's why I proposed simply changing the access level of these properties to protected. This adjustment should sufficiently meet our needs and anyone else needing a persistent instance of the app, without necessitating significant changes to the API structure.

Thanks for sharing the details. For your needs, I would suggest adding a simple if/else statement to the SlackApp initialization process as shown below:
export default {
  async fetch(
    request: Request,
    env: SlackEdgeAppEnv,
    ctx: ExecutionContext
  ): Promise<Response> {
    const app = new SlackApp({ env });
    if (!areDurableObjectsReady()) {
      app.use(durableObjectRelatedMiddleware);
    }
    return await app.run(request, ctx);
  },
};

When it comes to the "app_home_opened" event handler, the handler is still necessary even after a user gets their view. Every time a user accesses the view, your app is responsible for handling the event. If you don't want to refresh the view once it's available, you can simply do nothing in response to the event delivery.
Either way, I'd like to avoid exposing the internal arrays for this reason. The types/names of the arrays could be changed in the future (due to refactoring/Slack platform's breaking changes). It'd be appreciated if you could understand this.
I hope this makes sense to you, and the above suggestion is helpful. Is there anything else to discuss here?

Forgot to mention this: If I understand correctly, an edge function is stateless in general, though there may be runtime initialization cache. Thus, initializing SlackApp for each request should be inevitable.

Thanks for sharing the details. For your needs, I would suggest adding a simple if/else statement to the SlackApp initialization process as shown below:
export default {
  async fetch(
    request: Request,
    env: SlackEdgeAppEnv,
    ctx: ExecutionContext
  ): Promise<Response> {
    const app = new SlackApp({ env });
    if (!areDurableObjectsReady()) {
      app.use(durableObjectRelatedMiddleware);
    }
    return await app.run(request, ctx);
  },
};

When it comes to the "app_home_opened" event handler, the handler is still necessary even after a user gets their view. Every time a user accesses the view, your app is responsible for handling the event. If you don't want to refresh the view once it's available, you can simply do nothing in response to the event delivery.
Either way, I'd like to avoid exposing the internal arrays for this reason. The types/names of the arrays could be changed in the future (due to refactoring/Slack platform's breaking changes). It'd be appreciated if you could understand this.
I hope this makes sense to you, and the above suggestion is helpful. Is there anything else to discuss here?

Absolutely thanks again for hearing me out.

Forgot to mention this: If I understand correctly, an edge function is stateless in general, though there may be runtime
initialization cache. Thus, initializing SlackApp for each request should be inevitable.

While this is true for workers and serverless in general. Durable objects are stateful and thus don't succumb to the same initialization processes. In essence you can create a durable id from a users slack id and they have their own globally available stateful instance to which every request can be routed too.

Durable objects are stateful and thus don't succumb to the same initialization processes. In essence you can create a durable id from a users slack id and they have their own globally available stateful instance to which every request can be routed too.

Yes, the DO data is indeed stateful, but I don't understand the connection between the data and framework code change. Usually, developers look up the data within handler code. Thus, registering handlers is still necessary, and you can dispatch an event with consideration of the DA data within the functions.
The whole handlers can be omitted for some scenarios. As I suggested above, the proper way to do so is to have if/else statements during the SlackApp initialization. This means you have to have your own request payload parser to determine whether you should register a handler. This requires extra work on your side. I'm not sure if this is what you would like to have.
If you want to continue this discussion further, could you share a pseudo code demonstrating your ideal goal? Otherwise, is it okay to close this issue?

Also, I believe that registering handlers itself never costs a lot in terms of resource consumption (in comparison with others like DA data lookup etc.). But if such a small cost is critical for your use case, please go ahead with if/else statements during the initialization. You should be able to optimize the cost by doing so.


App is continuously flickering when app is open but phone kept idle for some duration

Describe the bug
App is continuously flickering when app is open but phone kept idle for some duration
To Reproduce

Open mobile app
Be in home page
Click on power button to turn off the phone while app is still open.
Keep phone idle for sometime ( 15- 20 minutes max)
Unlock the Android phone .

Current behavior
Mobile app flickers continuously.
Expected behavior
Without any flickers app should work in correct flow
Screenshots
https://user-images.githubusercontent.com/102220709/190657406-a5bd109a-a3b6-4224-8ff8-5436c494f3fc.mp4
Device: Android (One plus Nord 2)
OS: V11.3
Model: DN2101
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa5.mosip.net
Additional context
Env: qa5.mosip.net

After discussing with @santhoshsunder and @Anushree09-N, this issue may replicate on the mobiles which include the option "Only this time" while giving permission regarding location asked by App(Image1). The mobiles which I have (not in 1 plus Nord2), on those they were not showing that option(Image 2).
Image 1.

Image 2.

@Anil-kumar-Majji I have observed this issue on Samsung galaxy A03 Core with OS version: Android 11 as well and by increasing the idle time by 1 to 2 hr would help us to replicate the issue and also this is quite inconsistent. This is not device specific issue
CC @rakhimosip

Able to replicate the issue, the flow to replicate the issue is captured in below video:
https://user-images.githubusercontent.com/79500509/209144017-2854eff6-aecc-4d72-bf6b-c00582f4f3d5.mov
Device : PIXEL 6
OS: Android 13
MOSIP Version: <IP_ADDRESS>
MOSIP server: [qa5.mosip.net]
Device : Galaxy A03 Core
OS: Android 11
MOSIP Version: <IP_ADDRESS>
MOSIP server: [qa5.mosip.net]
Seen this issue on above devices.
CC @rakhimosip @Anil-kumar-Majji

Since the functionality is not getting impacted and the user will be able to continue the flow of actions, changing the severity to Minor. (ui issue).

verified as fixed in the build with commit id in the below screenshot.
https://drive.google.com/file/d/15uWjasH2tRj0qCau8Ljj8YFEoSXi6mfd/view?usp=drivesdk


Bug: Rule not applying to last table entry

.taplo.toml:
[formatting]
column_width = 100
indent_string = '	'
reorder_keys = true

# I don't want the package field or individual dependency tables to be reordered.
# The list of dependencies *should* be ordered, however.
[[rule]]
formatting = { reorder_keys = false }
include = ["**/Cargo.toml"]
keys = ["package", "dependencies.*"]

Cargo.toml after using taplo:
[package]
name = "twilight"
version = "0.0.0"
publish = false
edition = "2021"

[dependencies]
paste = "1.0.7"

[dependencies.twilight-cache-inmemory]
version = "0.11.0"
features = ["permission-calculator"]
default-features = false

[dependencies.twilight-gateway]
version = "0.11.0"
features = ["native", "zlib-stock"]
default-features = false

[dependencies.twilight-http]
version = "0.11.0"
features = ["decompression"]
default-features = false

[dependencies.twilight-model]
version = "0.11.0"
features = []
default-features = false

[dependencies.twilight-standby]
version = "0.11.0"
features = []
default-features = false

# Notice how this one still gets reordered.
# You could switch any dependency to be here and it would get reordered too.
[dependencies.twilight-util]
default-features = false
features = ["builder", "link", "snowflake"]
version = "0.11.0"

Does this happen with the newest CLI (^0.6.*), or are you using the vscode extension?

Seems to work correctly for the CLI for me. Should be fixed in the next version of the extension as well.

Yes, I'm using the extension. I'm so sorry for forgetting to mention that.
Thank you!

In that case this should be fixed with the next version, unfortunately I cannot say any ETA on that, sorry.

New versions are out on all platforms, so this should be fixed.


Stack Permutation code is added

You are given two arrays A and B of unique elements of size N. Check if one array is a stack permutation of the other array or not.
Stack permutation means that one array can be created from another array using a stack and stack operations.
Example 1:
Input:
N = 3
A = {1,2,3}
B = {2,1,3}
Output:
1
Explanation:

push 1 from A to stack
push 2 from A to stack
pop 2 from stack to B
pop 1 from stack to B
push 3 from A to stack
pop 3 from stack to B

Please Merge it.

Please merge it.


DO NOT MERGE Use Swift 3.2

Considering master is already on 4.0 this is a temporary branch to use for Swift 3.2 support.

Closing now that Swift 4.0 is out of beta.


Factory Unification

Motivation
Mirage's Model is hard to teach because it falls into an uncanny valley of seeming like the same thing as DS.Model. It doesn't do much other than declare that a type exists and that it has certain associations.
Proposal
Factory makes a better foundational primitive for Mirage. There's no reason we can't annotate relationships on factories instead of on models, and drop the concept of Model.
On the original motivation for Model
https://github.com/samselikoff/ember-cli-mirage/issues/69 lays out the original thinking. I think all the objections against declaring associations within factories can be overcome.

...but then, users would need to ensure all their relationship metadata is in their factories. What if this doesn't match up with their business requirements regarding what makes their models valid? For example, what if a contact didn't need an address to be valid, and so the factory didn't have the association in its definition?

This is a circular argument about the API of Factory. There's no reason we can't allow Factory to declare associations that don't have default implementations. For example,
address: hasOne()

can declare an association without providing any default implementation, whereas
address: hasOne(function(n, server) {
  return server.create('address');
})

can both declare the association and provide a default value. This also eliminates the need to imperatively create related records in afterCreate.
On Foreign Keys
Several discussions about associations have unnecessarily entangled the question of foreign keys.
Foreign keys are an implementation detail. Consider that JSON:API deliberately hides them within the server's implementation. A spec-compliant JSON:API server is expected to be able to work with no publicly-visible foreign keys at all.
Mirage has the luxury of being an in-memory data store, so indirection via keys is not necessary. Relationships can point directly at the objects themselves.
When users want to expose a property that acts as a foreign key to a relationship, that can be done directly:
  get addressId() {
    if (this.address) {
      return this.address.id;
    }
  }
  set addressId(id) {
    this.address = server.addresses.find(id);
  }

This pattern can readily be packaged up as a macro since it is a useful common case:
  addressId: foreignKeyFor('address', /* { remoteKey: 'id' } */),

On Fixtures
Mirage supports fixtures as a parallel world apart from using factories at all. One may object to making factories the foundational primitive since they seem extraneous when using fixtures.
But I think factories should actually run anyway when using fixtures. The contents of the fixture can be treated as inputs to the factory instead of being raw, fully-specified records. This is how I actually use fixtures in practice, because otherwise the fixture files are forced to be more fragile and verbose.
For example, server.loadFixtures('articles') is conceptually shorthand for
import articlesFixtures from 'mirage/fixtures/articles';
articlesFixtures.forEach(a => server.create('article', a));

Thanks for taking the time to write this up and share your thoughts!
This comes at a good time as I am reworking parts of the ORM, and was going to publish some small breaking changes in 0.3. It could work out that we abstract away Model from Mirage's public interface either before 0.3 or v1.0.

Conceptually I liked the pattern of factory properties being "things you get when creating an object from this factory." Factories like this seem like they could be hard to parse
// factories/post.js

Mirage.Factory.extend({

  user: hasOne(function(n, server) {
    return server.create('address');
  }),

  comments: hasMany(),

  title: 'Foo',

  publishedAt: '2016-01-01'

})

(in this case, server.create('post') would give you an associated user but no comments), but I could be hand-wringing over nothing.
There is also an open PR for an association helper that I expect we'll merge soon, which would address the point about needing afterCreate to make & wire up standard associations.
I wonder if we could have a "declaration" section for factories, as a clear place where relationship metadata is encoded:
Mirage.Factory.extend({

  _schema: {
    user: hasOne(),
    comments: hasMany()
  }

})

Is there a decorators solution here?
Mirage.Factory.extend({

  @hasOne user
  @hasMany comments

  user: association(),

  title: 'Foo',

  publishedAt: '2016-01-01'
})

Ultimately, I agree that it might not be worth keeping both concepts anymore. The original motivation was to have one place where your schema is defined (rails AR, schema.rb) and one place where fake data is managed/produced (factory_girl). It's clearly caused lots of confusion so it's worth discussing.
Another point, if we dropped Models from the public interface, we'd still need schema.users.create(). Would it be more confusing to explain what this is doing without ever having introduced the concept of the model? Would we add an API to factories/server.create to "make an empty object of type X"?

Also, once the ORM supports all the relationship types ED does, I want Mirage to autoread ED's schema. This could alleviate some of the confusion.

I like the decorators idea. It's also possible to use named exports alongside the factory class:
export const schema = {
  user: hasOne(),
  comments: hasMany()
};
export default Factory.extend({...});

Re-reading this now here are my thoughts:

Having Mirage automatically read Ember Data models and generate its own models at runtime should address a lot of the confusion
Requiring factories for each model would be a breaking API change
We may eventually add default values to Models (different from factory values), if these were on the same object it could be more confusing
The roles for models and factories are borrowed from backend systems, which does provide some point of comparison for folks familiar with those systems. Also, we don't have to invent our own abstractions, we're borrowing well-worn patterns

For these reasons I think I'm going to close this for now. I like your fixtures idea, I am open to adding that to the API. The foreign keys in 0-3 ended up being different from your proposal, I had some issues with an in-memory graph but can't recall them now.
If you (or anyone) has more thoughts here that will turn into actionable items, I'm more than happy to reopen this so we can discuss. Thanks again!


Improper use of Getx detected

Hi, I'm having a strange issue with GetX on an application that I'm developing. I'm using a controller to keep track of the internet connection of the device, everything works fine, but in one button I'm trying to change the behavior of the onPressed function based on that status, but it gives me the error of improper use of a GetX has been detected. But if I do a hot reload the error disappears and the button shows just fine and the behavior of the function gets changed. If I restart the application the error comes back and goes away with another hot reload. Bellow is a piece of my code:
Container(                   height: 80.0,                   child: Padding(                     padding: EdgeInsets.all(8.0),                     child: Row(                       mainAxisAlignment: MainAxisAlignment.end,                       children: [                         GetX<ConnectionController>(                           builder: (conn) => RaisedButton(                             onPressed: () async {                               if (conn.connectionStatus.value ==                                   DataConnectionStatus.connected) {                                 SnackBar snack = await c.save();                                 Scaffold.of(context).showSnackBar(snack);                               } else {                                 SnackBar msg = SnackBar(                                   content: conn.disconnectedSnack.content,                                   duration: Duration(seconds: 10),                                   action: SnackBarAction(                                     label: 'Salvar Offline',                                     onPressed: () async {                                       SnackBar snack = await c.save(offline: true);                                       Scaffold.of(context).showSnackBar(snack);                                     },                                   ),                                 );                                 Scaffold.of(context).showSnackBar(msg);                               }                             },                             child: Text(                               'Salvar',                               style: TextStyle(color: Colors.white),                             ),                             color: Color(0xFF00b3c9),                           ),                         ),                         FlatButton(                           child: Text('Cancelar'),                           onPressed: () {},                         ),                       ],                     ),                   ),                 )
Note that this variable c is another controller that I have instantiated in the widget, I don't know if that can cause trouble, I've searched other similar questions and even some issues here on GitHub, but couldn't figure it out. Sorry if this isn't the best place to look for help but as I'm not sure if it's a bug I'm opening this issue.

There is no need to use a GetX in the View, as it will not be changed if the observable is changed. In onPressed, before if, do this:
final ConnectionController conn = Get.find<ConnectionController>();

Oh I see, it worked like a charm! I didn't get that it's only meant to be used when something on the view is changed. Anyways, thank you very much for the response, congrats for the awesome package.


Unbundle hexy and use the npm package

I'm not sure why hexy is bundled as the history is lost. Feel free to close it if there was a good reason for the bundling.

the reason might be that I started using hexy before npm even exist (thanks, @mscdex ! )


left margin of options function provided by css3colors should be more versatile

Currently (as of this commit), it is just assumed to be a string (of whitespace hopefully).
Let's allow it to be a number of spaces as well, and do some sanity checks, and have a default value.

Let's assume default indent to be no indentation, and allow strings or small positive integers, say maxed out at 40.


Offset popup from viewport to emphasize separation from app

@zone117x suggests we pop up the Blockstack App during authentication in a way that's offset from the viewport so the user doesn't get the perception that the popup is just part of the app, which could lead them to feel comfortable later entering their Secret Key directly into apps.
This could apply to both the extension and non-extension version of the Blockstack App popup.
Offset example from 1Password:

So, what is your recommendation for how much 'offset' it should be? All the way on the right (I think Metamask does)?

Yea I think we can use MetaMask as guidance here


Changing timer plugin colors for status bar

When farming patches are growing, the green on green status bar is only like 2 shades different creating an eye sore. Thus causing the actual timer bars to be essentially not used. From talking, most people just search for the "Done at 1:45 PM" text to check crops and just ignore the status bars unless it's red.
It would be handy to make the background default bar like a light-medium gray and then have the red for dead, green for growing, etc on top of gray.
Optional: Upon being fully grown, have a yellow border around the green?

duplicate of #8262


authorization fails when cargo publish is used

Description
I want to publish a crate to the gitea package registry
cargo publish --registry gitea which returns
failed to get a 200 OK response, got 401
  headers:
        HTTP/1.1 401 Unauthorized
        Content-Type: text/plain; charset=utf-8
        X-Content-Type-Options: nosniff
        Date: Thu, 28 Sep 2023 10:23:41 GMT
        Content-Length: 17

  body:
  authGroup.Verify

A token is used with complete access and it is defined in credentials.toml.
The repository  _cargo_index is existing and has config.json with dl and api as entries
What kept me wondering is when I do not have a credentials.toml for a token is asked.
And I should go http://{url}/api/packages/{USER}/cargo/me which returns always 404.
This process of following an url to get access to a token is not explained in the docs.
Thats why i created my own token with full access without success.
Gitea Version
1.20.4
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
2.40.1
Operating System
Win 11
How are you running Gitea?
Running in Docker
Database
SQLite

Does the config.json in the index repository contain a auth-required: true field? If not you need to recreate that file from Settings > Packages > Initialize Index. The visibility change of an owner is sadly not synced into the config.
To avoid this, you can use the sparse http index for cargo which does not use the index repository.

After Initializing  the config.json is still not containing auth-required: true.
The owner of the repositroy is Owner to which I belong.
I have 2FA activated so I need to use anyway all the time a token.
I am a bit confused. There are two different authorizations? The usual one to get access to Gitea and then a different one publishing a crate or why there need to be auth-required: true? I thought I just need to have access to the repository and then by using cargo publish --registry gitea this will make the corresponding commit to the index.
my config.toml:
[registry]
default = "gitea"

[registries.gitea]
index = "http://<URL>/<ORGANIZATION>/_cargo-index.git"

[net]
git-fetch-with-cli = true

I created an extra folder .cargo in the root of the repositry and placed config.toml inside, which is fine (acc. to https://doc.rust-lang.org/cargo/reference/registries.html but not acc. to https://docs.gitea.com/usage/packages/cargo), but I also placed the .credentials.toml inside and published with --allow-dirty because the credential file was of course not checked in. Instead the .credentials.toml should be place in the home directory as stated in both documentations.


feat: add confirmation dialog to clear tasks

this adds a better dialog to clear tasks

Before
After

hey! i really enjoy how you made a dialog box with looks in mind. the regular window.confirm design annoys me a bit! however:

i am a fan of using the Web APIs for user familiarity and accessibility. it is something that people understand, and just works.
my concern is that your implementation doesn't cover <1024px, where the new dialog breaks. that is the tradeoff for not using Web APIs - we have to go the extra-mile to assure it works!

due to the presented points, this PR will not be approved and we will remain with the current implementation.
thanks for contributing and hope to work with you in another issue soon :)


WIP: travis-ci: run stbcheck utility

You have two options which are described on the above policy.
Could you please choose either option 1 or 2, and specify it clearly on the reply?

one

PRELIMINARY DECLARATION FOR FUTURE SWITCH TO A NON-GPL LICENSE
I hereby agree in advance that my work will be licensed automatically under the Apache License or a similar BSD/MIT-like open-source license in case the SoftEther VPN Project adopts such a license in future.

it is not ready to merge
I'm going to cleanup travis-ci build as well as fix missing strings

ready to review and merge
I decided to do travis-ci refactoring in later PRs


Clarify which ASR rules generate alerts and which ones don't - and whether this is configurable

The Notifications and Alerts section (https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/attack-surface-reduction?view=o365-worldwide#notifications-and-alerts) vaguely indicates that some ASR rules trigger alerts and others don't ("when certain attack surface reduction rules are triggered, alerts are generated").
It'd be helpful if this was more specific. Which ASR rules trigger alerts? Which ones do not? Is there anything that can be configured to make them generate an alert?

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

ID: 96cedf2c-e6fa-bbfb-61f0-ab4bcaae1479
Version Independent ID: 45ca9ffb-55e9-7721-3433-017a513a59be
Content: Use attack surface reduction rules to prevent malware infection
Content Source: microsoft-365/security/defender-endpoint/attack-surface-reduction.md
Product: m365-security
Technology: mde
GitHub Login: @denisebmsft
Microsoft Alias: deniseb

@denisebmsft Please help us in resolving this issue. Thanks

@denisebmsft Gentle reminder.

Opened task 5351236

My colleague is still working on this. He is waiting on some needed information.

In progress - a few issues still to be resolved.

Fixed, but will add additional details when provided by the product team.
See: https://docs.microsoft.com/microsoft-365/security/defender-endpoint/attack-surface-reduction-rules-reference?view=o365-worldwide#per-rule-alert-and-notification-details


[feature request] user management

Administrator can add devices on behalf of ordinary users.
Ordinary users that can not add / delete devices (or 3rd type of user account that have only view privileges)

@hackerunet  could you please give me the link to view the php frontend source code of traccar so that i can get some idea to make my front end with PHP? I am working on that..

If you need traccar source code get.into traccar.org and check in the web
app, my front end is not traccar front end is mine and was made from
scratch. Traccar doesnt have a php based frontend as far as i know.
El 04/02/2016 05:44, "tufanbhattarai"<EMAIL_ADDRESS>escribió:

@hackerunet https://github.com/hackerunet could you please give me the
link to view the php frontend source code of traccar so that i can get some
idea to make my front end with PHP? I am working on that..
—
Reply to this email directly or view it on GitHub
https://github.com/tananaev/traccar/issues/492#issuecomment-179749558.

User and device management is available in recent versions of Traccar server.


Cannot read property 'removeChild' of null at MarkerLabel_.onRemove

https://github.com/tomchentw/react-google-maps/issues/774
also pay attention to this
https://cdn.rawgit.com/googlemaps/v3-utility-library/master/markerwithlabel/src/markerwithlabel.js
MarkerLabel_.prototype.onRemove
it defer from the one that used in this library

i've made a fix

@egdbear Your fix works in a regular browser if you do these changes:

Remove lines 596-598
Remove lines 51-57
Replace gMapsApi with google.maps

@ismael-miguel Thanks man. I really appreciate. Are you interested in job offer?

@egdbear thanks for your solution!
I added the line
if (!this.labelDiv_.parentNode) return
after
MarkerLabel_.prototype.onRemove = function () {
var i; ....
And it worked again 👍

https://github.com/jesstelford/node-MarkerWithLabel/pull/15/commits/7b963ccc815e0229f4d7ad05ff45fe4be0984f33

Can anyone confirm if this is fixed in v2.0.2?

It Does!
Thanks @jesstelford


Make _pages getter public

What feature would you like to see?
I would like to have access to pages.
Please tell us the problem you are running into that led to you wanting a new feature.
I cant see total of pages in the stack to see that its a last page.

This is a great suggestion and added in https://github.com/woltapp/wolt_modal_sheet/pull/299
Exposing the page list, and also exposing helper getters to detect if the current page is first/last really improved the example playground app. You can see yourself in this PR diff: https://github.com/woltapp/wolt_modal_sheet/pull/299

Released https://pub.dev/packages/wolt_modal_sheet/changelog @Albertbol


Chain parameters should not be computed in an init function

E.g. genesis block ID, which depends on other variables in the genesis block. Therefore a custom chain currently needs to copy this entire function to duplicate the logic

Closed in d8aef1862794e6e5f6ba6fea70d07817a2caf47a


⚠ Bofrost.at has degraded performance

In 8f39687, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1921 ms

Resolved: Bofrost.at performance has improved in b3d5e00 after 13 minutes.


Fixed failing build when socket.h adds flexible arrays to end of structures

Fixes #116

I rebuilt and ran the test_socket program, which ran successfully.  Are there any other tests which I should run while we wait for the CI?

No, that's good enough. Thanks!

Aitäh :)

I lived in Tallinn for a couple of years.  Next time I visit, it might be interesting for me to visit Zubax and see Télega / UAVCAN in action, if you have some interesting demonstrations of the techologies available.

Sure, just drop me a line next time you're visiting these parts!


Where should ROS packages be located on OpenEmbedded images?

Should ROS packages be located under /opt/ros/<ROS_DISTRO> or folded into the rest of the OS under /usr? The current meta-ros implementation for crystal and dashing on [thud-draft] does the latter, but choosing the former would seem to guarantee that ROS 1 packages can be added to ROS 2 distros plus they would be where existing ROS users expect to find them. However, it would be, in some sense, a breaking change and would violate the Filesystem Hierarchy Standard because ROS is not an add-on, but fundamental to the operation of the image. In spite of this, we favor /opt/ros/<ROS_DISTRO>. We would like feedback from the ROS community on this, especially from the current users of meta-ros, who would be impacted by the change. Please add your thoughts by 2019-08-30.

/opt/ros/<ROS_DISTRO> seems to be a reasonable choice.

Also OSRF has registered ros with LANANA as a provider to be FHS compatible.

I finally found why this is so. The last sentence of 3.13.2. under http://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch03s13.html states:

Distributions may install and otherwise manage software in /opt under an appropriately registered subdirectory.

So the decision is change where the ROS packages are located to be under /opt/ros/<ROS_DISTRO>. This will be done as part of the implementation of meta-ros layer version 3 -- see Milestone 8.


Use new multiline output handler

Drops hacky URL encoding and begins using GitHubs new output facility for multi line outputs.
Would be good to test somewhere.
Closes #13

Tested, seems to work.


Support ztsd compression as Content-Encoding

Introduces the ability for a registry to serve content with brotli, zstd, gzip or deflate compression using Content-Encoding mechanism.
A quick comparison on compression efficiency, applied to ubuntu top layer:
17953716 data.br
25861247 data.zstd
28382489 data.gz
71763456 raw

Taking over/reviving #3784, since @ndeloof is no longer working on this. I added some tests, and dropped brotli as per some discussion on the previous PR.

cc @thaJeztah

Codecov Report
Patch coverage: 64.00% and project coverage change: -1.00 :warning:

Comparison is base (08f7a47) 56.79% compared to head (1d9a453) 55.79%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3900      +/-   ##
==========================================
- Coverage   56.79%   55.79%   -1.00%
==========================================
  Files         106      108       +2
  Lines       10676    10937     +261
==========================================
+ Hits         6063     6102      +39
- Misses       3939     4149     +210
- Partials      674      686      +12

Impacted Files
Coverage Δ

registry/client/transport/http_reader.go
22.54% <64.00%> (ø)

... and 2 files with indirect coverage changes

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

👍🏻 looking forward to this feature!

@laurazard @thaJeztah Any progress on this?

I think this one was ready for review, but I (personally) didn't get round to do another review of it (definitely feel free to review though!)
For the "klauspost/compress" dependency; yes, I think it's safe to update it to a newer version (but from my perspective not a "blocker" for this PR; we can continue updating it either as part of this PR or as follow-ups); should be easy to update though 👍

For completenes; I should mention that this PR is NOT to support image that use zstd as compression. The OCI spec defines compression as part of the image's definition (which, in hindsight, is a bit of a pain). Image that use layers with zstd compression are already supported by various runtimes (and don't require this change). I should note that images with mixed compressions are not well-defined in the OCI specification, and have various compatibility issues; see

https://github.com/opencontainers/image-spec/issues/803

This PR allows images to be distributed with zstd transport compression. That's something currently not supported by any registry (to my knowledge), but is an approach we've been exploring (as a PoC). That feature would also the image themselves to use uncompressed layers, but compression to be applied during transport (push/pull).
There are some (non-insignificant) challenges still to be resolved for that (one of them is that clients not supporting transport-level compression would push/pull a LOT more data as they would be moving uncompressed layers over the wire.

I bumped klauspost/compress (cc @milosgajdos @thaJeztah)


erlang_27: 27.0 -> 27.0.1

Description of changes
Erlang 27.0.1 was released: https://erlangforums.com/t/patch-package-otp-27-0-1-released/3824. I was hopeful that we could remove some of the glue code for ex_doc with this release but we can't yet due to an issue reported on Linux (see revert here: https://github.com/NixOS/nixpkgs/pull/327631).
Please wait for ofborg to finish builds on OSX and Linux.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

The failed check runs locally.
➤ ./maintainers/scripts/check-by-name.sh master https://github.com/NixOS/nixpkgs.git
these 4 paths will be fetched (0.28 MiB download, 1.03 MiB unpacked):
  /nix/store/3sc0yv0bnhrlrnqasa5hbvdkn8zzc5dn-jq-1.6-dev
  /nix/store/8s18shh6aglz9w2zzrkwr7bgbc2g1nnv-jq-1.6-bin
  /nix/store/bfwvq5438hw2ycfnl8xyhljhn97klw4f-oniguruma-6.9.8-lib
  /nix/store/ngydafwn5kil236z3fp2anyxdq7wkf8p-jq-1.6-lib
copying path '/nix/store/bfwvq5438hw2ycfnl8xyhljhn97klw4f-oniguruma-6.9.8-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/ngydafwn5kil236z3fp2anyxdq7wkf8p-jq-1.6-lib' from 'https://cache.nixos.org'...
copying path '/nix/store/8s18shh6aglz9w2zzrkwr7bgbc2g1nnv-jq-1.6-bin' from 'https://cache.nixos.org'...
copying path '/nix/store/3sc0yv0bnhrlrnqasa5hbvdkn8zzc5dn-jq-1.6-dev' from 'https://cache.nixos.org'...
 Done
Fetching base branch master to compare against.. c755861181b982b522aed4eaabeeb4fdd9377a1b
Creating Git worktree for the base branch in /run/user/1000/tmp.vzLzMjtPGG/base.. Done
Merging base branch into the HEAD commit in /run/user/1000/tmp.vzLzMjtPGG/merged.. 2a299042de22d3aa2196238c72a94a0b0bc62a7a
Reading pinned nixpkgs-check-by-name version from pinned-version.txt.. 0.1.1
Building tool.. these 3 derivations will be built:

...truncated

/nix/store/nisq2b8js8fx86f0j2jrrk1iywd3m453-nixpkgs-check-by-name-0.1.1
Running nixpkgs-check-by-name..
Validated successfully
Cleaning up.. Done

The pkgs/by-name check failure was a problem on master, a rebase should fix it :)
And the reason it works locally is because the failure depends on the Nix version. This will be improved in the future


Document the added lit substitution swift_src_root

%swift_src_root: absolute path to the directory where the Swift source code is stored.
The substitution was introduced in #8641, I have used it again in #9999, I guess it makes sense to properly document it, too...

...and I wanted to claim the magic PR number 😁

@swift-ci Please smoke test and merge