text:
ADR: Enhancement to the KeyAccessServer table to support key rotations

Enhance Key Access Server table to support key rotations
Context and Problem Statement
The Key Access Server policy store supports a single key and many key access grants. The original design assumed that only a single key would be held at a given time and if a rotation was needed the key access server's public key would be replaced with a new on.
It appears that this may not be a good long term strategy and some enhancement is needed to track the key rotations for remote KAS (whether considered part of the platform or external to the platform).
Decision Drivers

Support key rotations
Ensure strict values

Considered Options

Store multiple keys within the public_key jsonb typed column
Create an auxiliary table to store the keys with a many:1 relationship with the KeyAccessServer table

Decision Outcome
Chosen option: "{title of option}"

Store multiple keys within the public_key jsonb typed column

🟢 Existing table structure and no migration needed
🔴 With JSONB the data does not have a schema to conform to and data structure migrations are hard
🔴 No indication from a high-level which key is primary without decoding the JSONB
🔴 Row needs to be updated "frequently" to capture key rotations and identify the current key
🔴 After many key rotations the resulting data is quite large and filtering needs to be added to the service code

Create an auxiliary table to store the keys
erDiagram

    KeyAccessServer ||--|| KeyAccessServerKey: "has current key"
    KeyAccessServerKey }|--|| KeyAccessServer: "belongs to"

    XKeyAccessGrant }|--|| KeyAccessServer: "has many"
	X ||--|| XKeyAccessGrant: "has one"

    X {
        uuid         id                      PK
    }

    XKeyAccessGrant {
        uuid  X_id FK
        uuid  key_access_server_id FK
    }

	%% moving public_key out
    KeyAccessServer {
        uuid       id                PK
		text       name
        text       uri               UK
        uuid       current_key_id    FK
        jsonb      metadata
		created_on date
		updated_on date
    }

    KeyAccessServerKey {
        uuid       id
        uuid       key_access_server_id  FK
        jsonb      public_key
        jsonb      metadata
		created_on date
		updated_on date
    }

🟢 Schema enforced solution to multiple keys
🟢 Ensure future migrations are simpler (not-NoSQL)
🟡 Requires an auto migration to move public keys
🔴 If public key json has many keys, a manual migration is required

References

@jrschumacher is this statement accurate given your proposed schema?
"During a key rotation, a new key (row) is added to the KeyAccessServerKey table and the current_key (on one or multiple) KAS is updated to that new key. The old keys will persist within policy (un-utilized as non-current) and are not deleted upon rotation."

That is my assumption. If we don't need to persist the keys then we really don't need a separate table.
It's also worth discussing how this would work for KASes managed by the platform and KASes managed remotely.

@jrschumacher How will this work with RSA and ECC as a KAS might have P256, P384, etc..... If a KAS can only have 1 current key at a time.
Also what format are we expecting to be stored in the public_key row? It would be nice if we took this time to standardize that format or build it in a such a way to support JWK, ANS.1/DER or PEM.

@jrschumacher I modified the ERD a little to add a composite unique key on the KeyAccessServerKeys table of UNIQUE(key_access_server_id, algorithm) and moved the relationship so Grants now has a many to one relationship to Keys
This will restrict a KAS to 1 key per algorithm going forward. So an admin can't define two RSA:4096 keys to the same KAS. It also allows the flexibility of letting the KAS manage multiple keys like ML-KEM, P-256, RSA, etc...
erDiagram

    %% KeyAccessServer ||--|| KeyAccessServerKey: "has current key"
    KeyAccessServerKey }|--|| KeyAccessServer: "belongs to"

    XKeyAccessGrant }|--|| KeyAccessServerKey: "has many"
	X ||--|| XKeyAccessGrant: "has one"

    X {
        uuid         id                      PK
    }

    XKeyAccessGrant {
        uuid  X_id FK
        uuid  key_access_server_id FK
    }

	%% moving public_key out
    KeyAccessServer {
        uuid       id                PK
		text       name
        text       uri               UK
        %% uuid       current_key_id    FK
        jsonb      metadata
		created_on date
		updated_on date
    }

    KeyAccessServerKey {
        uuid       id
        uuid       key_access_server_id  FK
        uuid       key_id
        vchar      algorithm
        jsonb      public_key "ASN.1, PEM, JWK"
        jsonb      metadata
		date       created_on
		date       updated_on
        compIdx    comp_key UK "key_access_server_id + algorithm"
    }

Looks great. I'm going to copy and update the main description.

So today KAS Grants relate registered Key Access Servers to Attributes (namespaces, definitions, values). It looks like this diagram would relate grants from keys to attributes. Is this an accurate change, or should the diagram point a KAS -> 1+ keys, and a KAS -> 1+ grants and 1 grant -> 1 value?

So today KAS Grants relate registered Key Access Servers to Attributes (namespaces, definitions, values). It looks like this diagram would relate grants from keys to attributes. Is this an accurate change, or should the diagram point a KAS -> 1+ keys, and a KAS -> 1+ grants and 1 grant -> 1 value?

I did flip it around because keys are what should be associated with a namespace, attribute, or value. A KAS can have multiple keys, with a constraint of 1 key per algorithm.
In theory, an admin could assign a set of keys belonging to one KAS to an attribute value, where you’d get an OR split between RSA, and ECC, for example.
Let me know if this makes sense.

authors: jakedoublev jrschumacher strantalis

repo: opentdf/platform


text:
Normalise author & publication data where possible

I've noticed that the data we have is a bit unpredictable in terms of formatting and structure. A few examples from the searches I keep running:

Note here that the darker text indicates the author, and the lighter text indicates the publication information. Because of the slightly messy data, it's not always apparent that this is the structure here.
A few things I notice:

Spacing and punctuation is unpredictable and unexpected (spaces around colons, no spaces after commas, trailing commas, open braces that don't close, spacing around parentheses, square braces vs parentheses, etc)
Multiple authors are attributed oddly (Wahl, Jan,Tomes, Margot)
Authors sometimes have dates inserted (Phillips, Vernon Sirvilian, 1871-) or needless metadata (Broughton, Oliver M., author.)
Metadata repeated needlessly (Edinburgh (Scotland ), Edinburgh , Edinburgh, Edinburgh (Scotland, Scottish burgh records society Printed for the lordprovost, magistrates andcouncil 1899)

These are all relatively minor issues, but they do make the metadata harder to parse. Are there ways that we could normalise this data? Given that we don't have full control over the data as it comes in, I'm thinking we'd need to build something of a "translation" layer on top of the existing data, so we can parse it a bit prior to outputting it. The trick, of course, is to ensure that we aren't over-correcting the problem and we're only improving the readability of the text—some of these issues might be easier to fix than others.

If we're set on trying to do this algorithmically, first steps would be to start collecting some larger subsets of data that we can try and experiment with - I have a definite fear that any algorithmic approach will end up overzealous though.

Whilst its good to keep an eye on this, I think it isn't an easy one to solve.  In a sense, it's a worldwide library problem.  We all work to standards, but interpret them differently!  The joy(!) of aggregating data from so many varied sources is that the data will naturally not match cleanly like this.  This is one of the reasons for trying to keep to quite a sinmple set of core fields which are hard to misinterpret and should translate well between countries / languages / material types: e.g. title and creator.
Having said that... I think one of the (many) benefits this site could bring, is that as the aggregation of data grows, it becomes a richer source that can be used  for different purposes, such as cleaning or tidying up data.

So me and Sarah discussed this a while back actually, I had suggested what might be quite nice is if we supported crowdsourcing data correction. We can't easily correct data algorithmically but we can probably identify data we don't understand - if we were to have a separate page where users could work through that and correct it in such a way that (provided enough people agree this is the correct interpretation) it got written back to the database that would be... an interesting project in itself. :smile:

Also what we would ideally want is for the corrections to also be sent back to the source library for them to include in their catalogues, so the next time we get a data feed, the corrected data isn't overwritten.

source: gharchive/issue

authors: brizee sarahmonster stuartlewis

repo: opentexts/opentexts

license: MIT

license_type: permissive

license_source: github-api


text:
[openwrt] Enable OTBR_NAT64 and INFRA_IF by default and add UCI config.

This commit enables OTBR_NAT64 and INFRA_IF by default, making NAT64 functionality available out-of-the-box on the OpenWrt platform.
At the same time, the RCP serial port configuration is added to the UCI configuration file to make the runtime modifications clearer and to avoid the errors that are easily caused by directly modifying the init.d configuration.

The CI/CD passed automatically again without making changes. I guess we need to improve the number of concurrencies in CI/CI to make it a single step test?
In any case, can someone merge it in? @bukepo @xuyirio thanks.

LGTM.
One thing to note: querying an AIL NAT64 prefix is currently disabled for OpenWRT (PR).

According to the description of openwrt/pull/11559, libanl is already included in the musl c library, so we can turn this option on.
Do I need to also submit a modification to CMakeLists.txt#L153 PR?

LGTM.
One thing to note: querying an AIL NAT64 prefix is currently disabled for OpenWRT (PR).

According to the description of openwrt/pull/11559, libanl is already included in the musl c library, so we can turn this option on.
Do I need to also submit a modification to CMakeLists.txt#L153 PR?

Good to know! Yes, please remove the NOT OT_TARGET_OPENWRT condition and verify the tests are passing.

source: gharchive/pull-request

authors: ihidchaos xuyirio

repo: openthread/ot-br-posix

license_source: bigquery


text:
Fixes docker run command to allow host receiving RA packets.

This bring small changes for the docker run command to allow the computer (and other devices in the network) to have access to the RA packets.
This a result from this issue: https://github.com/openthread/ot-br-posix/issues/1789

Note: Already signed the CLA.

@saramonteiro , any plans to move this PR forward?

authors: jwhui saramonteiro

repo: openthread/ot-docs


text:
[CLI] The CLI device built with default options goes to dead loop when thread is started

The CLI device will be trapped in a dead loop when thread is started on the nrf52840 CLI device:
> ifconfig up
Done
> thread start
Done
> # hang

git commit: https://github.com/openthread/ot-nrf528xx/commit/993dc42f87cb905014593f417384eca33d2c6e6c
backtrace:
Program received signal SIGTRAP, Trace/breakpoint trap.
tx_terminate () at ../third_party/NordicSemiconductor/drivers/radio/nrf_802154_core.c:1181
1181	            while (!nrf_timer_event_check(NRF_802154_TIMER_INSTANCE, NRF_TIMER_EVENT_COMPARE0))
(gdb) bt
#0  tx_terminate () at ../third_party/NordicSemiconductor/drivers/radio/nrf_802154_core.c:1181
#1  0x00054b44 in current_operation_terminate (term_lvl=term_lvl@entry=1 '\001',
    req_orig=req_orig@entry=REQ_ORIG_ACK_TIMEOUT, notify=notify@entry=false)
    at ../third_party/NordicSemiconductor/drivers/radio/nrf_802154_core.c:1400
#2  0x000558ee in nrf_802154_core_receive (term_lvl=<optimized out>, req_orig=<optimized out>,
    notify_function=notify_function@entry=0x53911 <notify_tx_error>, notify_abort=<optimized out>)
    at ../third_party/NordicSemiconductor/drivers/radio/nrf_802154_core.c:2961
#3  0x00052a4e in nrf_802154_request_receive (term_lvl=term_lvl@entry=1 '\001',
    req_orig=req_orig@entry=REQ_ORIG_ACK_TIMEOUT, notify_function=notify_function@entry=0x53911 <notify_tx_error>,
    notify_abort=notify_abort@entry=false)
    at ../third_party/NordicSemiconductor/drivers/radio/nrf_802154_request_direct.c:67
#4  0x0005397a in timeout_timer_fired (p_context=<optimized out>)
    at ../third_party/NordicSemiconductor/drivers/radio/mac_features/nrf_802154_precise_ack_timeout.c:75
#5  0x00052968 in nrf_802154_lp_timer_fired ()
    at ../third_party/NordicSemiconductor/drivers/radio/timer_scheduler/nrf_802154_timer_sched.c:465
#6  0x0000822c in HandleCompareMatch (aIndex=aIndex@entry=k802154Timer, aSkipCheck=aSkipCheck@entry=false)
    at ../src/src/alarm.c:319
#7  0x00008856 in RTC2_IRQHandler () at ../src/src/alarm.c:686
#8  <signal handler called>
#9  nrf5RadioProcess (aInstance=aInstance@entry=0x20001388 <ot::gInstanceRaw>) at ../src/src/radio.c:831
#10 0x00007df8 in otSysProcessDrivers (aInstance=aInstance@entry=0x20001388 <ot::gInstanceRaw>)
    at ../src/src/system.c:141
#11 0x00000620 in main (argc=0, argv=0x0 <__isr_vector>) at ../openthread/examples/apps/cli/main.c:123
(gdb)

Steps to reproduce:

build and flash the nrf52840 CLI device by following https://github.com/openthread/ot-nrf528xx/blob/main/src/nrf52840/README.md
start GDB debugging by following https://devzone.nordicsemi.com/nordic/nrf-connect-sdk-guides/b/getting-started/posts/using-gdb-with-nordic-devices
start thread on the CLI device with ifconfig up and thread start commands.

@LuDuda Could you help take a look?


text:
🐛 [Bug]: opentiny pro vur-router meta: hideInMenu: tree, the menuItem in side menu

Version
"@opentiny/vue": "^3.6.8",
Vue Version
"vue": "^3.2.31",
Link to minimal reproduction
export default {
  path: 'list',
  name: 'List',
  id: 'List',
  label: 'List',
  component: () => import('@/views/list/index.vue'),
  meta: {
    locale: 'menu.list',
    requiresAuth: true,
    order: 2,
    hideInMenu: true
    // roles: [RoleType.admin, RoleType.user],
  },
  children: [
    {
      path: 'table', // The midline path complies with SEO specifications
      name: 'Table',
      id: 'Table',
      label: 'Table',
      component: () => import('@/views/list/search-table/index.vue'),
      meta: {
        locale: 'menu.list.searchTable',
        requiresAuth: true,
        // roles: [RoleType.admin, RoleType.user],
      },
    },
  ],
};

Step to reproduce
list菜单中设置了hideInMenu: true,结果依然在左侧菜单中
What is expected
No response
What is actually happening
No response
Any additional comments (optional)
No response

@hello-yezi 可否帮忙看下这个问题

authors: kagol labike

repo: opentiny/tiny-vue


text:
🛑 [CN] OpenUPM Website Packages is down

In cfff11b, [CN] OpenUPM Website Packages (https://openupm.cn/packages/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website Packages is back up in 097f170.

repo: openupm/upptime-openupmcn


text:
🛑 [CN] OpenUPM API /packages/extra is down

In f9c550f, [CN] OpenUPM API /packages/extra (https://api.openupm.cn/packages/extra) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM API /packages/extra is back up in 6e3f8a0.


text:
🛑 [CN] OpenUPM Website is down

In 6181b8e, [CN] OpenUPM Website (https://openupm.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website is back up in 27ab4c2 after 20 minutes.


text:
🛑 [Global] Unity Registry /package-name is down

In a167102, [Global] Unity Registry /package-name (https://packages.unity.com/com.unity.addressables) was down:

HTTP code: 500
Response time: 579 ms

Resolved: [Global] Unity Registry /package-name is back up in f1e26a4.

repo: openupm/upptime


text:
🛑 [CN] OpenUPM Website is down

In d155dc7, [CN] OpenUPM Website (https://openupm.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [CN] OpenUPM Website is back up in 2a86c5e.


text:
[Bug]: Some data used for both train and test when using folder dataset format with random seed

Describe the bug
I'm using Anomalib for anomaly detection.
My custom dataset is very small size and it is not split to train/validation(test).
So, I split data with anomalib/data/utils/split.py "split_normal_images_in_train_set" function.
But, after create self.train_data & self.test_data at anomalib/data/folder.py,
Some data exists in self.train_data and self.test_data.
I think the data used for training is used again for validation when seed=0(random seed) condition.
Because self.train_data and self.test_data is created independently.
self.train_data
https://github.com/openvinotoolkit/anomalib/blob/main/anomalib/data/folder.py#L483
self.test_data
https://github.com/openvinotoolkit/anomalib/blob/main/anomalib/data/folder.py#L512
Check this issue please.
Dataset
Folder
Model
PatchCore
Steps to reproduce the behavior

Install Anomalib
Prepare dataset for folder format (recommend to small size dataset)
Create config file for folder format
Debuging \anomalib\anomalib\data\folder.py
Compare self.train_data and self.test_data

OS information
OS information:

Ubuntu 20.04
Python version: [e.g. 3.8.10]
Anomalib version:0.3.3
PyTorch version: 1.11.0
CUDA/cuDNN version: 11.4
GPU models and configuration: GeForce RTX 2080
Any other relevant information: I'm using a custom dataset

Expected behavior
I want to know about this issue is real bug or my mistake.
If this issue is a bug, please share the fix plan.
Screenshots
No response
Pip/GitHub
GitHub
What version/branch did you use?
Anomalib version:0.3.3
Configuration YAML
dataset:
  name: private_data
  format: folder
  path: /private_data
  task: segmentation
  category: bottle
  image_size: 224
  train_batch_size: 32
  test_batch_size: 32
  num_workers: 8
  transform_config:
    train: null
    val: null
  create_validation_set: false
  tiling:
    apply: false
    tile_size: null
    stride: null
    remove_border_count: 0
    use_random_tiling: False
    random_tile_count: 16

model:
  name: patchcore
  backbone: resnet18
  pre_trained: true
  layers:
    - layer2
    - layer3
  coreset_sampling_ratio: 0.1
  num_neighbors: 9
  normalization_method: min_max # options: [null, min_max, cdf]

metrics:
  image:
    - F1Score
    - AUROC
  pixel:
    - F1Score
    - AUROC
  threshold:
    method: adaptive #options: [adaptive, manual]
    manual_image: null
    manual_pixel: null

visualization:
  show_images: False # show images on the screen
  save_images: True # save images to the file system
  log_images: True # log images to the available loggers (if any)
  image_save_path: null # path to which images will be saved
  mode: full # options: ["full", "simple"]

project:
  seed: 0
  path: ./results

logging:
  logger: [] # options: [comet, tensorboard, wandb, csv] or combinations.
  log_graph: false # Logs the model graph to respective logger.

optimization:
  export_mode: null # options: onnx, openvino

# PL Trainer Args. Don't add extra parameter here.
trainer:
  accelerator: auto # <"cpu", "gpu", "tpu", "ipu", "hpu", "auto">
  accumulate_grad_batches: 1
  amp_backend: native
  auto_lr_find: false
  auto_scale_batch_size: false
  auto_select_gpus: false
  benchmark: false
  check_val_every_n_epoch: 1 # Don't validate before extracting features.
  default_root_dir: null
  detect_anomaly: false
  deterministic: false
  devices: 1
  enable_checkpointing: true
  enable_model_summary: true
  enable_progress_bar: true
  fast_dev_run: false
  gpus: null # Set automatically
  gradient_clip_val: 0
  ipus: null
  limit_predict_batches: 1.0
  limit_test_batches: 1.0
  limit_train_batches: 1.0
  limit_val_batches: 1.0
  log_every_n_steps: 50
  log_gpu_memory: null
  max_epochs: 1
  max_steps: -1
  max_time: null
  min_epochs: null
  min_steps: null
  move_metrics_to_cpu: false
  multiple_trainloader_mode: max_size_cycle
  num_nodes: 1
  num_processes: null
  num_sanity_val_steps: 0
  overfit_batches: 0.0
  plugins: null
  precision: 32
  profiler: null
  reload_dataloaders_every_n_epochs: 0
  replace_sampler_ddp: true
  strategy: null
  sync_batchnorm: false
  tpu_cores: null
  track_grad_norm: -1
  val_check_interval: 1.0 # Don't validate before extracting features.

Logs
Don't need logs for this issue.

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, this was a reported bug in version 0.3.3, which was fixed in v0.3.4. Upgrading your installation of Anomalib to v0.3.4 or higher should resolve your issue.
I'm closing this issue as a duplicate but feel free to re-open if your problems persist after upgrading.

Thank you @djdameln
I'll upgrade my Anomalib version.

authors: djdameln yesjuhyeong

repo: openvinotoolkit/anomalib


text:
Update section "Creating an annotation task" in User Guide

Motivation and context

Resolved #3164
This PR add section "task details"  for reduce section "creating an annotation task"
Fix pointers on image131_detrac.jpg
How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[x] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

@TOsmanov , could you please fix linter errors?

@TOsmanov , could you please resolve conflicts? Roman fixed a lot of spell errors.

authors: TOsmanov nmanovic

repo: openvinotoolkit/cvat


text:
Include Parameters and Annotations when Copying an Action

When copying an action ensure that parameters and annotations are also copied

Closes https://github.com/openwhisk/openwhisk/issues/418

PG2 824

@rabbah, any comments on this one?

I'm having second thoughts about this - may be a good one to take on the dev list.
The reason: we don't make it possible to delete a parameter from the CLI.

@rabbah I think this is good thing to add to the CLI, be able to copy all the metadata.
The reason: we don't make it possible to delete a parameter from the CLI.
What's the concern here about deleting a parameter?
Merging this PR doesn't block us from offering a way to delete a single parameter in future update of CLI.

PG2 1029

authors: csantanapr dubeejw rabbah

repo: openwhisk/openwhisk


text:
[EPIC][CPU] Generate efficient vectorized pack op for non-f32 types.

This is the EPIC that collects pack optimization work. We should generate vectorized code (without stack allocation) after finishing below tasks.
### Tasks
- [ ] https://github.com/openxla/iree/issues/15600
- [ ] https://github.com/openxla/iree/pull/16213
- [ ] https://github.com/openxla/iree/issues/16313
- [ ] https://github.com/openxla/iree/issues/15441
- [ ] https://github.com/openxla/iree/issues/16071
- [ ] Deprecate DecomposePackUnPackOps pass

cc @dcaballe @bjacob @Max191 @MaheshRavishankar This collects the issues I've seen for pack op codegen. The LHS and RHS have different issues. Some of the prototype and ideas are updated in the child issues.

I still have some doubts about using direct vectorization here but I'm ok to move forward with it. We should also work on efficient pack/unpack support for targets without masking support (e.g., Neon). Currently, I'm seeing if/else statements/scalar code for it.

I still have some doubts about using direct vectorization here but I'm ok to move forward with it.

I think we are penalized by the current flow esp for pack_with_padding fusion cases. I need it, so I can evaluate how far we can push. Hopefully it will benefit all the CPUs.

We should also work on efficient pack/unpack support for targets without masking support

It would be more efficient because you don't need to go with stack allocation. We might get some penalty on shape_cast lowering, but it is a better state to me. Let's see.
I'm not going to "flip it anyway", but it unblocks me to prototype more things. We might get diverge for different CPUs, but it open a new path for us. Let's see what we can do better here. :)

authors: dcaballe hanhanW

repo: openxla/iree


text:
Verify window_reversal in ConvolutionOp

The window_reversal attribute does not have any verification check.
This should be a 1-D tensor such that size(window_reversal) == number of spatial dims.

The check on the StableHLO side will be addressed in https://github.com/openxla/stablehlo/pull/441

@sdasgup3 can we close this?

I think so given that both the action items are addressed.

repo: openxla/stablehlo


text:
[BUG] container images have no versions. Only latest

Please release and tag old container images that are stored at ghcr.io - at least 1.3.4

@siredmar sorry to reply late, now OpenYurt v1.4.0 has been released, pleas enjoy it.

authors: rambohe-ch siredmar

repo: openyurtio/openyurt


text:
Brave erased the browsing history without any user interaction

Hello, I would like to report a bug.
When I open the Brave "History" section, it only shows me the last 10 days browsing history.
I do not remember having cleared my history manually. I'm very frustrated as I was looking for a website I found a month ago.
Do you guys have the same problem?
I'm running 0.22.669 version on Windows 10.

I believe this is the project you are looking for: https://github.com/brave

authors: devinsba eTorAken

repo: openzipkin/brave


text:
Adds basic infrastructure for RPC request sampling

This adds an abstraction layer for RPC, based on non-deprecated code in
brave-instrumentation-http. It will be a work in progress until at least
Dubbo and gRPC are integrated (ideally also Armeria even though in
another repo.
This is limited to sampling logic to make it easy to integrate and also
as that's the more in-demand functionality. Most notably, we only need
two properties: RPC service and method, to satisfy the first use cases
of RPC sampling.
Ex. Here's a sampler that traces 100 "GetUserToken" requests per second. This
doesn't start new traces for requests to the health check service. Other
requests will use a global rate provided by the tracing component.
import static brave.rpc.RpcRequestMatchers.*;

rpcTracing = rpcTracingBuilder.serverSampler(RpcRuleSampler.newBuilder()
  .putRule(serviceEquals("grpc.health.v1.Health"), Sampler.NEVER_SAMPLE)
  .putRule(methodEquals("GetUserToken"), RateLimitingSampler.create(100))
  .build()).build();

grpcTracing = GrpcTracing.create(rpcTracing);

Thanks @trustin for helping me think through namings and such

added gRPC impl

@anuraaga PTAL again at grpc as I'm switching to dubbo meanwhile. thanks for the review!

@anuraaga yeah the idea is to do parsing and agreed it is more straightforward in google grpc which hides the transport. Due to issues like you mentioned, I wanted to keep the simple part (sampling) separate.. this keeps the latter change concentrated on these bits (including if http request should have a nullable getter for rpcRequest or not)

suprisingly I didn't mention this earlier, but #999 will be rebased over this, and has scope for parsing etc.

so one thing I will clear up in the text is that the method name is not required to be different than the java method. There are java based RPC, of course, like Dubbo. It is just preferred to use IDL when something is backed by IDL. We cannot enforce that there is always going to be IDL in other words.

I added apache dubbo. Last thing is to convert that code to alibaba dubbo

Thanks for the help!


text:
Quickstart add basic REST service

Also some extensive test revamping.

Git got messed up, putting up a new PR

repo: openziti/ziti


text:
Fix of quay operator for upstream community operators container version

Fixed issue with incorrect version of the container image for quay for version 1.0.2
New Submissions

[ ] Does your operator have nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?
[ ] Have you tested your Operator with all Custom Resource Definitions?
[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--

@sabre1041, please consider bumping the version by replaces in your CSV.

repo: operator-framework/community-operators


text:
Operator removed all the labels and annotations added to operator service

Bug Report
I am trying to add labels to the service exposed by the operator. The operator removes labels and annotations from service. We are trying to create a service mesh that would require marking all services with a project and team label.
What did you do?
Tried creating service through yaml file.
--- apiVersion: v1 kind: Service metadata:   labels:     name: xyz-operator     project: xyz-operator     role: operator     team: foundation   name: xyz-operator   namespace: fdn-analytics spec:   ports:     - name: metrics       port: 8383       protocol: TCP       targetPort: 8383   selector:     name: xyz-operator     project: xyz-operator     role: operator   sessionAffinity: None   type: ClusterIP
What did you expect to see?
Service used by the operator to use the labels added.
What did you see instead? Under which circumstances?
The labels were removed when the operator started to init the service
Environment

operator-sdk version:
v0.7.0+git

go version:
1.12.12

Kubernetes version information:
v1.16.3

Kubernetes cluster kind:

Are you writing your operator in ansible, helm, or go?
go

Possible Solution
https://github.com/operator-framework/operator-sdk/blob/master/pkg/metrics/metrics.go#L84
copy labels here as well.

Hi @swapnil-zendesk,
If you are writing your operator in Go then, I'd like to say that you need to add the labels in the code that gen the resources. See in the Memcached sample here the labels added in the Service.
Also, I'd like to say that the go version 1.12.12 is not compatible with the SDK version v0.7.0+git and recommend you use the latest ones which are currently: 1.13+ for go and 0.13 for SDK.
I'd like also to share and recommend to you check the article Getting started with Golang Operators by using Operator SDK
I believe that the above information sorted out your question. Please, let us know if we can close this one.

Hello @camilamacedo86 ,
Thank you for replying.
It might be confusing but the service I am referring to is the one operator used to communicate with other service/ pods.
`swapnil@jumpbox2:~$ kubectl get all -n namespace
NAME                                          READY   STATUS    RESTARTS   AGE
pod/xyz-operator-74b9c548c4-dqtlq   1/1     Running   0          42m
NAME                             TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)    AGE
service/xyz-operator   ClusterIP   XX.XX.XX.XX           8383/TCP   109m
NAME                                     READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/xyz-operator   1/1     1            1           109m
NAME                                                DESIRED   CURRENT   READY   AGE
replicaset.apps/xyz-operator-74b9c548c4   1         1         1       42m
replicaset.apps/xyz-operator-c5755db87    0         0         0       62m`
service/xyz-operator (is missing labels), which is created by the operator framework to expose metrics.

Hi @swapnil-zendesk,
The only services that are created by default in the scaffold, I mean, that the developer did not implemented on it are to allow to expose the operator metrics. See here the Memcached sample.
Example
NAME                                 TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)             AGE
service/example-memcached            ClusterIP   10.108.124.47   <none>        11211/TCP           63s
service/memcached-operator-metrics   ClusterIP   10.108.67.82    <none>        8383/TCP,8686/TCP   66s

They are implemented in the main.go here. See here the implementation of the func CreateMetricsService. And here the labels added.
So, if you would like to update their labels it needs to be done programmatically. You can change the default implementation for your own. However, could you let us know why it is important to you change its labels? I mean, could you let us know what is the scenario/business requirement and what you are trying to solve?

Hi @camilamacedo86,
Thanks for the response and suggestions.
In order to do this programmatically, we would have to fork the repository and maintain our own library. We would like to avoid that if possible. So the business reason for this is because we are enforced by our DevOps team to have the labels defined at creation time. This is for ease of managing numerous pods that we have at Zendesk.
Would it possible for this to be a feature request for the metrics service to inherit the labels from the implemented service(xyz-operator)?
Thanks!

Hi @swapnil-zendesk,
Following some comments inline.

In order to do this programmatically, we would have to fork the repository and maintain our own library.
No. You can do the implementation of the ServiceMonitor in your own project.

Would it possible for this to be a feature request for the metrics service to inherit the labels from the implemented service(xyz-operator)?

Could you please open a new issue with the RFE?
Please, let us know why it is important for you to be able to define the labels on it. What problem/need you will solve with. Also, please add the link for this one as a reference.
In this way, since is your questions are sorted out I am closing this one.
Thank you for your collaboration with.

repo: operator-framework/operator-sdk


text:
operator-sdk should use updated ubi base image

In the recent releases of operator-sdk, v1.6.1 and v1.5.1, there are three high level vulnerabilities according to quay https://quay.io/repository/operator-framework/helm-operator/manifest/sha256:3f557aa662ce3af3693d7bea42b41a7339857d6c7abaeec3bbe9f1a89f63f15f?tab=vulnerabilities.
Most likely because the image is relying on an older ubi8 image https://github.com/operator-framework/operator-sdk/blob/master/images/operator-sdk/Dockerfile#L20. The latest ubi8-minimal is 8.3-298

Closed by #4766

authors: bitscuit estroz


text:
pkg/metrics: CreateMetricsService should return latest service

Description of the change:
createOrUpdateService should return latest service not the existing service.
log should use the INFO level log as like “Metrics Service object created”.
Motivation for the change:
CreateMetricsService should return latest service, so createOrUpdateService should return latest service not the existing service.
log should use the INFO level log as like “Metrics Service object created”.

Not sure why the Travis job failed. Maybe it's unstable?

/ok-to-test

authors: Gallardot jmrodri


text:
bundle webhook: enforce spec immutability

Signed-off-by: Joe Lanford joe.lanford@gmail.com

With just this change, it's possible to cause the Bundle controller to permanently fail for a particular Bundle by deleting the underlying unpack pod. When the pod is deleted, the Bundle controller will notice, create a new unpack pod, and then attempt to set the Bundle phase back to Pending. This will fail because the Bundle is in the Unpacked phase.

We're fine with users/controllers updating any labels/annotations

Actually I wonder whether this is behavior we'd allow if we're moving towards an embedded Bundle model?

Alright I updated this PR to only enforce spec immutability. That means there is still a possibility of a BI pivoting without a change to the Bundle. That could be accomplished by:

Using an image tag, a git branch, or a git tag in the Bundle source
Moving the image tag to a new digest, pushing changes to a git branch, or deleting and re-pushing a git tag on a different commit
Doing something to cause the unpack pod to be re-created (e.g. deleting the unpack pod)

If a user performs these steps, the new content from step 2 will be unpacked as a result of step 3, and the BI will notice, causing its pivot logic to execute.
IMO, this isn't a whole lot different than the pod example where one of the pod's container images uses and tag, the tag is moved to a different digest, and then at some unknown point in the future the existing pod gets rescheduled on a different node, and that node pulls the new image at the new digest and runs something different without you explicitly asking for it.

Actually I wonder whether this is behavior we'd allow if we're moving towards an embedded Bundle model?

Something to think about here, but in general I don't think those should be immutable. The BI controller may want to reconcile the labels/annotations for the Bundles it controls though. But I think that's separate from general immutability.

authors: joelanford timflannagan

repo: operator-framework/rukpak


text:
[Request] Add option to list models starting from certain date

Based on what i've seen from the implementation this should be possible using root_prefix + isoformat_date fragment and leverage s3, and azureblob search by prefix capability.

Awesome idea! I'd welcome a PR if you're up for it 😄
The only complexity I see is that get_model_versions_path, which is used to list all of the models with a given state, does not currently use the date in its prefix.
So the quickest implementation (which would be the slowest to run) would be to filter results after they are loaded. TO be able to use storage prefix filtering, we'd need to either change how we list models (perhaps to not use the versions/ directory anymore?) or start storing version files with a date prefix.

repo: operatorai/modelstore


text:
Update 01_convection.ipynb

Fixed tiny typos

Codecov Report

Merging #682 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #682      +/-   ##
==========================================
- Coverage   87.32%   87.31%   -0.02%
==========================================
  Files          93       93
  Lines        9278     9278
  Branches     1855     1855
==========================================
- Hits         8102     8101       -1
  Misses        950      950
- Partials      226      227       +1

Impacted Files
Coverage Δ

devito/__init__.py
86.81% <0%> (-1.1%)
:arrow_down:

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 be446fd...ddea1d2. Read the comment docs.

thanks, merged.

authors: FabioLuporini codecov-io georgebisbas

repo: opesci/devito

license: mit


text:
Quick guide

@ggorman
/cygdrive/c/Users/mathias/Desktop/Research/LondonSympy/Inversion/inversion/src/opesci_segy.c:
In function ‘unpack_float’:
/cygdrive/c/Users/mathias/Desktop/Research/LondonSympy/Inversion/inversion/src/opesci_segy.c:104:9: error: ‘for’ loop initial declarations are only allowed in C99 mode
for(int i=0;i<4;i++)
^
/cygdrive/c/Users/mathias/Desktop/Research/LondonSympy/Inversion/inversion/src/opesci_segy.c:104:9: note: use option -std=c99 or -std=gnu99 to compile your code
CMakeFiles/opesci.dir/build.make:80: recipe for target 'CMakeFiles/opesci.dir/src/opesci_segy.c.o' failed
make[2]: *** [CMakeFiles/opesci.dir/src/opesci_segy.c.o] Error 1
CMakeFiles/Makefile2:931: recipe for target 'CMakeFiles/opesci.dir/all' failed
make[1]: *** [CMakeFiles/opesci.dir/all] Error 2
Makefile:126: recipe for target 'all' failed
make: *** [all] Error 2

@ggorman
fixed

repo: opesci/inversion


text:
IPSec Status is not shown directly

After a while the IPSec Status is not shown correctly. Neither on the dashboard then on the status page
The Tunnel itself seems to work normally.
after restarting the whole ipsec service the Status is shown correctly

@andreasvel if you have new information, append new findings to the existing issue https://github.com/opnsense/core/issues/634 instead of opening a new issue again, like https://github.com/opnsense/core/issues/777

authors: AdSchellevis andreasvel

repo: opnsense/core


text:
It would be nice to add some popular DNS over TLS (DoT) resolvers with simple checkboxes

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is including your motivation for the request,
i.e. "For the purpose of [...] I am missing a solution that will [...]."
It would be great if you could enable DNS over TLS (and maybe DNS over HTTPS at some point) to popular public resolvers with simple checkboxes. That would avoid typos and silly mistakes that will happen every now and then while copy&pasting many ip addresses and domain names from the internet/etc.
Describe the solution you like
A clear and concise description of what you want to happen.
(e.g. I would like an input field in the /ui/firewall/alias which would add .... to ....)
For example Pi-hole has a pretty decent UI to enable popular DNS (although not over TLS) options. You just check if you want to use Google, Cloudflare, etc., and it just works. Maybe even simplify from that Pi-hole example and just have one checkbox per service and automatically add all IPv4 and IPv6 addresses depending if the protocols were supported via WAN. Maybe there's no harm in adding IPv6 forwarders even without IPv6 on WAN interface, but Opnsense is still pretty new to me so I'm not sure about that.
Checking Cloudflare, Google, and Quad9 would add something like the following to unbound configuration.
forward-zone:
    name: "."
    forward-tls-upstream: yes

    ## Cloudflare
    forward-addr: 1.1.1.1@853#cloudflare-dns.com
    forward-addr: 1.0.0.1@853#cloudflare-dns.com
    forward-addr: 2606:4700:4700::1111@853#cloudflare-dns.com
    forward-addr: 2606:4700:4700::1001@853#cloudflare-dns.com

    ## Google
    forward-addr: 8.8.8.8@853#dns.google
    forward-addr: 8.8.4.4@853#dns.google
    forward-addr: 2001:4860:4860::8888@853#dns.google
    forward-addr: 2001:4860:4860::8844@853#dns.google

    ## Quad9
    forward-addr: 9.9.9.9@853#dns.quad9.net
    forward-addr: 149.112.112.112@853#dns.quad9.net
    forward-addr: 2620:fe::fe@853#dns.quad9.net
    forward-addr: 2620:fe::9@853#dns.quad9.net

Describe alternatives you considered
A clear and concise description of any alternative solutions or features you considered.
Additional context
Add any other context or screenshots about the feature request here or links to relevant forum thread or similar
Pi-hole UX is pretty good, but I think it could be even more simplified. Just one checkbox per popular DNS resolver.

I don't expect we will preconfigure external dns's, the amount of maintenance and the concept of "popular" will be impossible to maintain (see the whole dyndns discussions for example). Adding a paragraph to the documentation would likely me more than enough and is easy to contribute to (https://github.com/opnsense/docs)

I created a small pull request for DNS over TLS documentation. https://github.com/opnsense/docs/pull/390
I would still say that popularity isn't that hard to define. For example couple of billion Android devices try use 8.8.8.8 over TLS. And 1.1.1.1 mobile app has been installed something like a hundred million times. :)

This went in with https://github.com/opnsense/docs/commit/86e313f1f8bde2f56f43dc16f4d77eb7c08633d6, merged with https://github.com/opnsense/docs/pull/390

authors: AdSchellevis oittaa swhite2


text:
Cloning an firewall schedule doesn't do anything

Hi,
I just realized that when you clone a "firewall schedule" the webinterface is just reset, the menu on left is folded close (the firewall section was previously open, as I have clicked on "Schedules") and nothing else happens, ie no duplicate schedule is created.
It doesn't matter whether you clone schedules which are in use or not.
I am on
OPNsense 16.1.13-amd64
Intel(R) Atom(TM) CPU D425 @ 1.80GHz
2 CPUs: 1 package(s) x 1 core(s) x 2 HTT threads
and it says no updates are outstanding.
Cheers
Tom

Hi Tom,
Nice catch, will be fixed in 16.1.14, thank you :)
Cheers,
Franco


text:
net/frr and security/tor: remove session close from search action

see https://github.com/opnsense/core/commit/b739c49892a3dc52029f863f20e0975dde476388
Now everything should be fine here.

hrm,sorry, I ran the style update a few minutes ago and that clashes in bgp

was just removing some git marks and restore the indent.

authors: fabianfrz fichtner

repo: opnsense/plugins


text:
Auto-update the app

Context
Currently user is completely responsible for Opossum app update - check for new releases on gitHub, manually download and install.
Goal
Would be nice to add this functionality to the app.
Ideas

Just check for updates and notify user about a new release every time starting the app. Might add a menu item "check for updates" or something similar.
(Probably later) Check for updates and automatically install it (after a user agreement)

This was fixed by #1529

authors: benedikt-richter vasily-pozdnyakov

repo: opossum-tool/OpossumUI


text:
failure with Chef 12

Maybe there is a more elegant way to resolve this?! But this does the job.
Also updated specs to chefspec 4.

:+1:

authors: armiller dennisklein

repo: opscode-cookbooks/rsync


text:
feat: Added cookie based user id memorization to support sticky bucketing

Summary

Added a Random 6 digit User Id Generator.
Storage and retrieval of user id from cookie.
Added Changelog file to track changes across versions.
Updated Readme

@opti-jnguyen Thanks for the review. I thought about doing custom implementation for cookie parsing but then realized that the package has a very low foot print, somewhere under 1.5kB addition to the final bundle. Then i went ahead and replaced our custom id generation function with uuid. both cookie and uuid add total of 2.7 KB to the bundle size. Our custom implementation would also add at least 70% of that. Based on this, i believe it makes sense to user tried and tested standard packages instead of custom implementation. The uuid takes a little longer to generate but its 0.3 ms on the top side which is not bad. What do you think?

@opti-jnguyen Thanks for the review. I thought about doing custom implementation for cookie parsing but then realized that the package has a very low foot print, somewhere under 1.5kB addition to the final bundle. Then i went ahead and replaced our custom id generation function with uuid. both cookie and uuid add total of 2.7 KB to the bundle size which is almost nothing. Our custom implementation would also add at least 70% of that. Based on this, i believe it makes sense to use tried and tested standard packages instead of custom implementation. The uuid takes a little longer to generate but its 0.3 ms on the top side which is not bad. What do you think?

@zashraf1985 - makes sense, I don't think the overhead is bad. If we are okay with the cons of risk and slightly bumping up the footprint for the pros of having effective, up-to-date 3rd party libraries then we should go ahead and just use both cookie and uuid.

repo: optimizely/cloudflare-worker-template


text:
(fix): update the forwarder to use a thread

Summary

Update the event forwarder to use a thread instead of using the main thread.

Test plan

update tests

Coverage decreased (-0.09%) to 99.446% when pulling c64154e732864703384ecd9ab1b0658f629bad2c on updateEPForwarder into 86a7aae9340811b1d4031d3db51dcec8d360aae6 on master.

Coverage decreased (-0.09%) to 99.446% when pulling c64154e732864703384ecd9ab1b0658f629bad2c on updateEPForwarder into 86a7aae9340811b1d4031d3db51dcec8d360aae6 on master.

Closing due to inactivity. Please re-open if needed.

repo: optimizely/ruby-sdk


text:
Python live lab

WMS ID = 440
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[x] All filenames are lower case (including folders, images, files, etc.)
[x] Filenames are descriptive
[x] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[x] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[x] Image references in markdown contain an alternate text

@hope-fisher

repo: oracle-livelabs/developer


text:
Remove provider.tf to make this project a reusable module from the registry

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version and Provider Version

Affected Resource(s)

Terraform Configuration Files

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file.
# Please remove any sensitive information from configuration files before sharing them.

Debug Output

Panic Output

Expected Behavior

Actual Behavior

Steps to Reproduce

terraform apply

Important Factoids

References

Review https://github.com/oracle-terraform-modules/terraform-oci-oke/pull/137 for the fix.

Hi,
Thanks for your contribution. Please also update the docs for the following scenarios in the quickstart page:

Users are cloning this repo instead of using the published module. This means they'll need to add the provider.tf themselves. The provider will need to be as it is currently defined.
Users are using the published module from the registry. Please document how they should then use the module, including defining the provider and passing the various parameters etc.

Done in #139

authors: hyder sauraahu


text:
Does Coherence work on ARM architecture?

Type of question
Coherence CPU architecture support
Question
Does Coherence work on ARM architecture (like the AWS Graviton2) or only with X86?

Coherence is pure Java, so it works on anything Java works on, including ARM.
That said, we did notice some issues in our nightly ARM builds with Java 8, but Java 11 ARM builds work fine, so I'd strongly suggest using Java 11 or later.

authors: aseovic javafanboy

repo: oracle/coherence


text:
WLS 12.2.1.2 cannot make connect() to admin jvm during container build for online wlst

Hi, I'm attempting to execute some online configurations via wlst and when trying to connect to the admin jvm the connect() fails with "java.net.ConnectException: Connection refused (Connection refused); No available router to destination.". The admin jvm is started successfully during the container build. The connect() attempt is to the t3s admin port. As a troubleshooting step, I manually stop the container build after starting up the admin jvm. I then run the container, start the admin jvm and manually excute the connect() and can successfully execute the online configuration. Has anyone else run cross this condition?

@ackwdw123 How do you manually stop container build?  From where are you executing the connect?

===Docker contianer build that fails at t3s connect()

Install JDK , Install WLS Binary

Copy jks, offline py, online py, start script (simple shell script that executes startWebLogic.sh, sends process to background, redirects the output to log)

Execute offline wlst : ${ORACLE_HOME}/oracle_common/common/bin/wlst.sh -skipWLSModuleScanning ${DOMAIN_CREATE_SCRIPT} -p ${DOMAIN_CREATE_PROPERTY_FILE}

Start Admin JVM

Connect to Admin JVM
Admin JVM starts successfully
wlst connect() fails

Execute online wlst  : ${ORACLE_HOME}/oracle_common/common/bin/wlst.sh -skipWLSModuleScanning ${DOMAIN_CREATE_ONLINE_CONFIG_SCRIPT} -p ${DOMAIN_CREATE_PROPERTY_FILE}

===Manual Verification of successful connect()

Install JDK , Install WLS Binary

Copy jks, offline py, online py, start script (simple shell script that executes startWebLogic.sh, sends process to background, redirects the output to log)

Execute offline wlst : ${ORACLE_HOME}/oracle_common/common/bin/wlst.sh -skipWLSModuleScanning ${DOMAIN_CREATE_SCRIPT} -p ${DOMAIN_CREATE_PROPERTY_FILE}

Start Admin JVM

End Docker build
Run docker container
Start Admin JVM
Connect to Admin JVM - connect('user','pwd','t3s://fqdn.hostname.com:port')
Execute online wlst : ${ORACLE_HOME}/oracle_common/common/bin/wlst.sh -skipWLSModuleScanning ${DOMAIN_CREATE_ONLINE_CONFIG_SCRIPT} -p ${DOMAIN_CREATE_PROPERTY_FILE}

@ackwdw123 you can not start the JVM at docker build time, that is not how Docker build process works.  What you need to do is when you run the container, start the Admin Server in the background and then call a script that verifies that the Admin Server is up and invokes the WLST online script.
I will try to submit a sample to do this.

Thank you for the follow up, I didn't have any success executing an online script with one build. I have been able to execute an online script using the following steps:

./dockerJDK-WLS-12.2.1.2-Binary.sh
./dockerJDK-WLS-12.2.1.2-Domain.sh
docker run -h hostname -p 20000:20000 -ti rhelv7-wls-domain bash
./start-adm.sh
Manually execute the online scripting.
Manually commit container changes
https://`hostname`:20000/console

Please post your Dockerfile

@ackwdw123 Do you mind sharing your Dockerfile so that we try to reproduce and advice you.

@ackwdw123 take a look at #392 for an example how to do WLST online at domain image build.  You can follow the same steps to do your WLST online configuration.

authors: ackwdw123 brunoborges mriccell

repo: oracle/docker-images


text:
weblogic-kubernetes-operator started managed servers with coherence enabled does not form a cluster.

When weblogic kubernetes operators starts managed servers, it creates kubernetes service object with service type=ClusterIP that causes the incorrect WKA list as shown below causes multiple coherence enabled managed servers(CacheTier) NOT to form a cluster.
WellKnownAddressList(
10.106.99.26
10.244.1.3
)
MasterMemberSet(
ThisMember=Member(Id=1, Timestamp=2018-06-19 18:22:54.308, Address=10.244.1.3:58536, MachineId=30238, Location=machine:wdtdomain-managed-server1,process:5
00,member:managed-server1, Role=CacheTier)
OldestMember=Member(Id=1, Timestamp=2018-06-19 18:22:54.308, Address=10.244.1.3:58536, MachineId=30238, Location=machine:wdtdomain-managed-server1,process
:500,member:managed-server1, Role=CacheTier)
ActualMemberSet=MemberSet(Size=1
Member(Id=1, Timestamp=2018-06-19 18:22:54.308, Address=10.244.1.3:58536, MachineId=30238, Location=machine:wdtdomain-managed-server1,process:500,member
:managed-server1, Role=CacheTier)
)
MemberId|ServiceJoined|MemberState|Version
1|2018-06-19 18:22:54.308|JOINED|12.2.1.3.0
RecycleMillis=1200000
RecycleSet=MemberSet(Size=0
)
)
Here, 10.244.1.3 is the Pod IP of the managed-server1, while 10.106.99.26 is the service IP of managed-server2 rather than actual pod IP of managed-server2, causing the mananged-server1 and managed-server2 not to form a cluster.
Not sure weblogic-kubernetes-operator provides the way to create headless service object for managed server as for coherence cluster to be well formed on kubernetes, Headless Service object needs to be created.
Plese see below kubernetes doc for headless service.
https://kubernetes.io/docs/concepts/services-networking/service/#headless-services
As per the above kubernetes doc, headless-service can be used when no load-balancing is required among the pod instances with selectors. I can only see single instance of each managed server running on kubernetes. And do not expect operator will be running multiple pods of a single managed-server(e.g managed-server1), so I do think a service object with type=ClusterIP needed for a managed server running on kubernetes.
So weblogic-kubernetes-operator must provide a way or an option for managed server to be created with headless service or create headless service by default for each managed server instance so that servers involving in caching tier can form the cluster when running on kubernetes.

Realized issue filed with wrong username. Closing this one..

repo: oracle/weblogic-kubernetes-operator


text:
change samples directory

Change from /samples/simple to /samples. Remove unused /samples/production directory.

@rosemarymarano There were additional /simple usages outside of hugo that also needed fix-up. I've taken the liberty of pushing a commit that updates them - please double-check the commit diff.

When this goes through, I'll notify the Oracle Fusion Middleware on Kubernetes team and maybe Ed Burns/Galia Cheng also.

authors: rosemarymarano tbarnes-us


text:
enable BRB for clients that don't support resume

I tried to do this for #518 but decided it was scope creep.
Goal: BRB should work seamlessly for clients that only reattach, without using the RESUME command.

Failed resume that results in a reattach means that the resume token assigned during registration is invalid (instead, the resume token of the original client is still valid). All subsequent chained resumes will fail.
This is fine, but maybe we should keep the timestamp of the failed resume around and use it for history autoreplay?

I've thought about this more and I no longer want to implement it.
The robust solution is for clients to implement CHATHISTORY and msgid-based deduplication so they can request the history they need --- not for the server to work harder at tracking how much they missed.

repo: oragono/oragono


text:
tabs for different views on the same image

Currently, ufp, utk, and, if available, PSP views are on different pages.
Instead, we can just leverage the Layout component and display tabs to switch between main views.
Out of scope for now: memoizing and state handling

This has been roughly achieved now based on indui.

repo: orangecms/utk-web


text:
image pulling does not validate digests

When pulling an image by digest, I would expect the library to verify that the digest of the returned resource matches the requested digest.
For testing purposes, I set up a registry that returns the same image for any requested digest:
$ curl -s https://evil-registry.rudy.family/v2/busybox/manifests/sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef | sha256sum
d319b0e3e1745e504544e931cde012fc5470eba649acc8a7b3607402942e5db7  -

Docker rejects to pull this image:
$ docker pull evil-registry.rudy.family/busybox@sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
evil-registry.rudy.family/busybox@sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef: Pulling from busybox
manifest verification failed for digest sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef

Pulling with oci-distribution does not fail, and returns the bogus hash to the user:
let arg = "evil-registry.rudy.family/busybox@sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef"
let image: Reference = arg.parse().unwrap();
let client = Client::default();
let auth = &oci_distribution::secrets::RegistryAuth::Anonymous;
let accepted_media_types = vec!["application/vnd.docker.image.rootfs.diff.tar.gzip"];

let (_m, d) = client.pull_manifest(&image, auth).await.unwrap();
println!("pull_manifest({}) -> {}", arg, d);

let data = client.pull(&image, auth, accepted_media_types).await.unwrap();
println!("pull({}) -> {:?}", arg, data.digest);

pull_manifest(evil-registry.rudy.family/busybox@sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef) -> sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef
pull(evil-registry.rudy.family/busybox@sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef) -> Some("sha256:deadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeefdeadbeef")

The spec says this regarding content verification:

Most clients MAY ignore the [Docker-Content-Digest header], but if it is used, the client MUST verify the value against the uploaded blob data.

The full reproducer is available at https://github.com/burgerdev/evil-registry/.

Thanks for filing this @burgerdev. It looks like the spec also says the same thing about blobs as well as the manifest itself. So we should check for the presence of the header and then validate whatever comes back (manifest or blob) with that digest.

Yes, and I think it should be two checks:

Does the Docker-Content-Digest match the returned body?
Does the requested digest match the actual digest?

For (2), the spec is a bit vague around canonical digests. However, I'd argue that pulling an explicitly pinned image should fail if the requested digest is not available, and that it's a registry error if blobs mentioned in a manifest are not available under their digests.

So basically the desired logic is "if my reference contains a digest rather than a version, then validate that the returned content matches that digest"

Fyi, I proposed a clarification for the distribution spec in https://github.com/opencontainers/distribution-spec/issues/549.

Thanks for doing that. Looks like there is some decent support for it there, so I'm glad we're implementing it here

repo: oras-project/rust-oci-client


text:
Introduce React FullPage for homepage scroll effect

Overview
This PR adds a new library: react-fullpage that allows us to achieve an "on-scroll" vertical slide behavior for the site's homepage
Demo
https://www.loom.com/share/ec68603f20c349e8b49aa6c8316b6740#63
Work to do

[ ] Share preview with team and get feedback
[ ] Ensure all mobile queries and breakpoints work
[ ] Ensure slide images are loaded before entering view (no flickering)
[ ] Determine if we'll buy commercial license
[ ] Clean up committed code

@alexlsalt Is this still something we're looking to bring in?

authors: alexlsalt dzello

repo: orbit-love/orbit-model


text:
Remove uberjar dependency

Fixes #269

@JoeHegarty lgtm, we should check the sample project after this change (ensure it has it's own slf4j logger eg. log4j2).

@gustavonalle thanks!

authors: gustavonalle johnou

repo: orbit/orbit


text:
Release notes for 0.20.0

This PR will update CHANGELOG to contain description of the changes since 0.19.0. This PR is required to release 0.20.0.
This is still work in progress!

Hey team! @shamb0t are there breaking changes coming in this release with respect to data structures / formats?

Hey @Schwartz10! :wave:  There will be breaking changes to the API but the new release will still be able to read old data structures and should be backwards compatible w.r.t. old OrbitDB addresses . The shape of new entries will change to include an identity and cid field and will have their version incremented to 1.
Does that answer your question?

What's blocking this?

Hey @fazo96 thanks for stopping by! No blockers but an issue was discovered and fixed in orbit-db-keystore, that meant a bit more work needed to be done to ensure old data-structures could still be read with the new keystore. Once all the keystore PRs https://github.com/orbitdb/orbit-db-keystore/pull/15, https://github.com/orbitdb/orbit-db-identity-provider/pull/23, https://github.com/orbitdb/ipfs-log/pull/238, are merged we should be ready for this and release. Almost there! :)

@shamb0t @aphelionz I believe this still needs to be merged (and updated before?) for 0.20.0 release.

(and rebase before merging)

This looks good to me and ready to merge 👍

Good catch @shamb0t! 👍 LGTM.

repo: orbitdb/orbit-db


text:
JSONAPISource does not set Content-Type for POST just after a GET

Hello,
when the JSONAPISource does a GET, and then a POST (with body), the header "Content-Type" is not set.
This bug was introduced recently, I believe it's because deepMerge as used here:
https://github.com/orbitjs/orbit/blob/7da202aa4ef074be9d4a13b41d731e76f154078c/packages/%40orbit/jsonapi/src/jsonapi-source.ts#L206
actually does not make a copy of the default settings, in this branch of the code inside deepMerge:
https://github.com/orbitjs/orbit/blob/a99942370e9c63502b75d0aa1484dbc78a097357/packages/%40orbit/utils/src/objects.ts#L187
so the delete on Content-Type is done permanently to the default settings object:
https://github.com/orbitjs/orbit/blob/7da202aa4ef074be9d4a13b41d731e76f154078c/packages/%40orbit/jsonapi/src/jsonapi-source.ts#L215
and it never comes back, even for POST with body

@belluzj thanks for digging into this. I'll fix up the deepMerge implementation soon.

A fix has been published in v0.15.19 of @orbit/utils and @orbit/jsonapi.
Thanks again for reporting @belluzj!

Thanks for your extreme reactivity! The problem I had is indeed fixed in the new version.

authors: belluzj dgeb

repo: orbitjs/orbit


text:
Wrong information MEMO on API results

Hi
The API is getting the memo information wrong like this:
https://api.stellar.expert/api/explorer/public/payments?account=GDDTZNNH7BXXWVKVM4VMYDIYGHJ7SWEB3QQ3IJPIVHCSNTL7A7GDITRG&limit=200&order=desc
{"id":"141580534601093121","paging_token":"141580534601093121","optype":1,"memo":14427229,"ledger":32964287,"tx_id":"141580534601093120","ts":"2020-12-07T12:42:57.000Z","from":"GDQ54YQUAWJAOBLZ6T3LPPHPJXPZ3WOBAP746J6STOGFPJ3E6SVVETVZ","to":"GDDTZNNH7BXXWVKVM4VMYDIYGHJ7SWEB3QQ3IJPIVHCSNTL7A7GDITRG","asset":"TREEP-GAVBWV24PZ6POVQGQO5UEWGO3TO7ERYXRFFI6V5VH3BMTPDZOHVOFA3G-2","amount":"10000","source_asset":"TREEP-GAVBWV24PZ6POVQGQO5UEWGO3TO7ERYXRFFI6V5VH3BMTPDZOHVOFA3G-2","source_amount":"10000"}
And the graphic interface the memo is ok
https://stellar.expert/explorer/public/tx/141580534601093120#141580534601093121

Fixed.
Sorry. Don't know how this happened. We really tested this like 5 days ago.

I want to say thank you for fast fix!

authors: RASTecnoTI orbitlens

repo: orbitlens/stellar-expert-explorer


text:
Settings/Preferences "General" > "d/l updates" checkbox doesn't stick

Describe the bug
Checking the Automatically download updates checkbox doesn't stick when navigating preferences.
To Reproduce

Open Preferences (Settings)
See that Automatically download updates is unchecked
Check Automatically download updates
Click on another tab (e.g., System)
Click back to General tab

Expected behavior
Automatically download updates stays checked.
Actual behavior
Automatically download updates is unchecked.
Note: checking Automatically download updates, then closing the window, then reopening it shows it remaining checked. However, clicking over to another tab (e.g., System) unchecks the setting again.
Other
I also noticed "glitchiness" when initially using the Settings dialog: couldn't change tabs until I closed and reopened the dialog. Am unable to recreate this issue reliably, though.
Orb Report
OrbStack info:
  Version: 0.13.0 (130000)
  Commit: ba57f21d6c60d45e0469196f4a67c79ec9911eea (v0.13.0)

System info:
  macOS: 12.6.7 (21G651)
  CPU: amd64, 16 cores
  CPU model: Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz

Additional context
I didn't include logs since this is (purely?) a GUI issue and didn't see anything relevant. Can still provide if needed.

Fixed for the next version. Thanks for reporting! Seems like this bug is specific to macOS 12.
The tab switching issue sounds like a SwiftUI bug in macOS 12 that we may not be able to do much about, unfortunately.
Just curious: is there a specific reason you haven't updated to macOS 13? (helpful to know for version distribution/support purposes)

specific reason you haven't updated to macOS 13

Yeah, there's music software I use that doesn't work well with 13 (yet?). I'll probably upgrade to 13 when Sonoma (14) is released, though.

repo: orbstack/orbstack


text:
Sample Generation Refinement

Due to some default library version conflicts (between librosa and fastai_audio), we needed to find a stable combination -- now updated in requirements.txt file (read by training notebooks).

Added script to sample generation notebook to clear out empty *.wav files. The model training notebook, 2_FastAI_StarterScript.ipynb, assumes that all *.wav files are non-empty. I had to manually delete these files to unblock training.

Cleared notebook output/metadata from checkin to keep future additions small and readable

@bnestor
Regarding Point 1: I'll test and update. Nice callout
Regarding Point 2: I'll provide the directory structure in a zipfile of data for quick start. I'll create / track an issue regarding all of the hardcoded paths. Existence of these file paths should be passed in as args and validated at beginning of script or script should gracefully fail.

repo: orcasound/aifororcas-livesystem


text:
Placeholder does not work with dropdown_input and remove_button plugins

Placeholder does not work with dropdown_input and remove_button plugins
My code:
document.querySelectorAll('.filter__select').forEach(element => {
new TomSelect(element, {
plugins: ['remove_button','dropdown_input'],
sortField: 'text',
});
});

Fixed with that last commit. Thanks Ivan!

Thank you, very cool plugin !

authors: IvanBoichuck oyejorge

repo: orchidjs/tom-select


text:
404 dashboard not found

Expected Behavior
show the dashboard page
Actual Behavior
laravel 404 , page not found (in localhost/dashboard)
Steps to Reproduce the Problem
1.php artisan serve
2.login into localhost/dashboard
3. face the error
Specifications

ORCHID Version:^3.0
Laravel Version:^5.7
PHP Version:7.1.3
Database Version:sqlite3

Other Notes
no change in routes , just php artisan orchid:install

Do you see routes?
php artisan route:list

Please pay attention to the parameters:
DASHBOARD_DOMAIN=localhost
DASHBOARD_PREFIX=dashboard

They determine where the panel will be located.
How do you start the server? Possible settings .env not applied

I am able to login successfully. But after login, the page redirects to https://admin.test.test/dashboard and shows 404.

@mathewparet
This is possible, provided that the user under whom you want to log in does not have the right to access.
The command to create a user with maximum permission (for the moment)
artisan make:admin

I created the used with artisan make:admin only
On Thu, 7 Feb, 2019, 5:41 PM Alexandr Chernyaev, notifications@github.com
wrote:

@mathewparet https://github.com/mathewparet
This is possible, provided that the user under whom you want to log in
does not have the right to access.
The command to create a user with maximum permission (for the moment)
artisan make:admin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/orchidsoftware/platform/issues/723#issuecomment-461394794,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACRg6tZlijamS6OzO3KYFI710xVVnEYiks5vLBf7gaJpZM4YfzaL
.

--
Best Regards,
Mathew Paret

@mathewparet  Well, could you indicate your versions.
As for 404 errors, you see the page of the laravel or the page of the orchid (They are visually different).
Also please check that the session is being written and you have the necessary permissions on the directories.

The 404 error I get is from Laravel, not Orchid
Also, all permissions seem right and session files are successfully being written into.
I am using Laravel Framework 5.7.25

You can show the output of the following commands:
php artisan route:list

and
php artisan tinker
>>> config('platform.domain');
>>> config('platform.prefix');

php artisan route:list

gMac:test mathewparet$ php artisan route:list
+-----------+----------------------------------------+--------------------------------------------------------------------+-----------------------------------------+------------------------------------------------------------------------------------+----------------------+
| Domain    | Method                                 | URI                                                                | Name                                    | Action                                                                             | Middleware           |
+-----------+----------------------------------------+--------------------------------------------------------------------+-----------------------------------------+------------------------------------------------------------------------------------+----------------------+
|           | GET|HEAD                               | /                                                                  |                                         | Closure                                                                            | web                  |
|           | GET|HEAD                               | api/user                                                           |                                         | Closure                                                                            | api,auth:api         |
| test.test | GET|HEAD                               | dashboard                                                          | platform.index                          | Closure                                                                            | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/announcement/{method?}/{argument?}                       | platform.systems.announcement           | Orchid\Platform\Http\Screens\AnnouncementScreen@handle                             | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/backups/{method?}/{argument?}                            | platform.systems.backups                | Orchid\Platform\Http\Screens\BackupScreen@handle                                   | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/bulldozer/{model?}/{method?}/{argument?}                 | platform.bulldozer.index                | Orchid\Bulldozer\Http\Screens\BootModelScreen@handle                               | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/category/create/{method?}/{argument?}                    | platform.systems.category.create        | App\Orchid\Screens\Category\CategoryEditScreen@handle                              | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/category/{category}/edit/{method?}/{argument?}           | platform.systems.category.edit          | App\Orchid\Screens\Category\CategoryEditScreen@handle                              | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/category/{method?}/{argument?}                           | platform.systems.category               | App\Orchid\Screens\Category\CategoryListScreen@handle                              | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/comments/create/{method?}/{argument?}                    | platform.systems.comments.create        | App\Orchid\Screens\Comment\CommentEditScreen@handle                                | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/comments/{comments}/edit/{method?}/{argument?}           | platform.systems.comments.edit          | App\Orchid\Screens\Comment\CommentEditScreen@handle                                | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/comments/{method?}/{argument?}                           | platform.systems.comments               | App\Orchid\Screens\Comment\CommentListScreen@handle                                | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/example/{method?}/{argument?}                            | platform.example                        | App\Orchid\Screens\ExampleScreen@handle                                            | web,platform         |
| test.test | GET|HEAD                               | dashboard/login                                                    | platform.login                          | Orchid\Platform\Http\Controllers\Auth\LoginController@showLoginForm                | web,guest            |
| test.test | POST                                   | dashboard/login                                                    | platform.login.auth                     | Orchid\Platform\Http\Controllers\Auth\LoginController@login                        | web,guest            |
| test.test | POST                                   | dashboard/logout                                                   | platform.logout                         | Orchid\Platform\Http\Controllers\Auth\LoginController@logout                       | web                  |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/main/{method?}/{argument?}                               | platform.main                           | App\Orchid\Screens\PlatformScreen@handle                                           | web,platform         |
| test.test | POST                                   | dashboard/password/email                                           | platform.password.email                 | Orchid\Platform\Http\Controllers\Auth\ForgotPasswordController@sendResetLinkEmail  | web,guest            |
| test.test | GET|HEAD                               | dashboard/password/reset                                           | platform.password.request               | Orchid\Platform\Http\Controllers\Auth\ForgotPasswordController@showLinkRequestForm | web,guest            |
| test.test | POST                                   | dashboard/password/reset                                           |                                         | Orchid\Platform\Http\Controllers\Auth\ResetPasswordController@reset                | web,guest            |
| test.test | GET|HEAD                               | dashboard/password/reset/{token}                                   | platform.password.reset                 | Orchid\Platform\Http\Controllers\Auth\ResetPasswordController@showResetForm        | web,guest            |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/press/entities/{type}/create/{method?}/{argument?}       | platform.entities.type.create           | Orchid\Press\Http\Screens\EntityEditScreen@handle                                  | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/press/entities/{type}/{method?}/{argument?}              | platform.entities.type                  | Orchid\Press\Http\Screens\EntityListScreen@handle                                  | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/press/entities/{type}/{page?}/page/{method?}/{argument?} | platform.entities.type.page             | Orchid\Press\Http\Screens\EntityEditScreen@handle                                  | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/press/entities/{type}/{post?}/edit/{method?}/{argument?} | platform.entities.type.edit             | Orchid\Press\Http\Screens\EntityEditScreen@handle                                  | web,platform         |
| test.test | POST                                   | dashboard/press/media/delete_file_folder                           | platform.systems.media.deleteFileFolder | Orchid\Press\Http\Controllers\MediaController@deleteFileFolder                     | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/directories                                  | platform.systems.media.getAllDirs       | Orchid\Press\Http\Controllers\MediaController@getAllDirs                           | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/files                                        | platform.systems.media.files            | Orchid\Press\Http\Controllers\MediaController@files                                | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/move_file                                    | platform.systems.media.moveFile         | Orchid\Press\Http\Controllers\MediaController@moveFile                             | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/new_folder                                   | platform.systems.media.newFolder        | Orchid\Press\Http\Controllers\MediaController@newFolder                            | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/remove                                       | platform.systems.media.remove           | Orchid\Press\Http\Controllers\MediaController@remove                               | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/rename_file                                  | platform.systems.media.renameFile       | Orchid\Press\Http\Controllers\MediaController@renameFile                           | web,platform,Closure |
| test.test | POST                                   | dashboard/press/media/upload                                       | platform.systems.media.upload           | Orchid\Press\Http\Controllers\MediaController@upload                               | web,platform,Closure |
| test.test | GET|HEAD                               | dashboard/press/media/{parameters?}                                | platform.systems.media.index            | Orchid\Press\Http\Controllers\MediaController@index                                | web,platform,Closure |
| test.test | GET|HEAD                               | dashboard/press/menu                                               | platform.systems.menu.index             | Orchid\Press\Http\Controllers\MenuController@index                                 | web,platform,Closure |
| test.test | GET|HEAD                               | dashboard/press/menu/create                                        | platform.systems.menu.create            | Orchid\Press\Http\Controllers\MenuController@create                                | web,platform,Closure |
| test.test | DELETE                                 | dashboard/press/menu/{menu}                                        | platform.systems.menu.destroy           | Orchid\Press\Http\Controllers\MenuController@destroy                               | web,platform,Closure |
| test.test | PUT|PATCH                              | dashboard/press/menu/{menu}                                        | platform.systems.menu.update            | Orchid\Press\Http\Controllers\MenuController@update                                | web,platform,Closure |
| test.test | GET|HEAD                               | dashboard/press/menu/{menu}                                        | platform.systems.menu.show              | Orchid\Press\Http\Controllers\MenuController@show                                  | web,platform,Closure |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/roles/create/{method?}/{argument?}                       | platform.systems.roles.create           | App\Orchid\Screens\Role\RoleEditScreen@handle                                      | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/roles/{method?}/{argument?}                              | platform.systems.roles                  | App\Orchid\Screens\Role\RoleListScreen@handle                                      | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/roles/{roles}/edit/{method?}/{argument?}                 | platform.systems.roles.edit             | App\Orchid\Screens\Role\RoleEditScreen@handle                                      | web,platform         |
| test.test | POST                                   | dashboard/search/{query}                                           | platform.search                         | Orchid\Platform\Http\Controllers\Systems\SearchController@index                    | web,platform         |
| test.test | GET|HEAD                               | dashboard/systems                                                  | platform.systems.index                  | Orchid\Platform\Http\Controllers\Systems\SystemController@index                    | web,platform,Closure |
| test.test | GET|HEAD                               | dashboard/systems/cache                                            | platform.systems.cache                  | Orchid\Platform\Http\Controllers\Systems\CacheController@store                     | web,platform         |
| test.test | POST                                   | dashboard/systems/files                                            | platform.systems.files.upload           | Orchid\Platform\Http\Controllers\Systems\AttachmentController@upload               | web,platform,Closure |
| test.test | POST                                   | dashboard/systems/files/get                                        | platform.systems.files.getFilesByIds    | Closure                                                                            | web,platform         |
| test.test | PUT                                    | dashboard/systems/files/post/{id}                                  | platform.systems.files.update           | Orchid\Platform\Http\Controllers\Systems\AttachmentController@update               | web,platform,Closure |
| test.test | POST                                   | dashboard/systems/files/sort                                       | platform.systems.files.sort             | Orchid\Platform\Http\Controllers\Systems\AttachmentController@sort                 | web,platform,Closure |
| test.test | DELETE                                 | dashboard/systems/files/{id}                                       | platform.systems.files.destroy          | Orchid\Platform\Http\Controllers\Systems\AttachmentController@destroy              | web,platform,Closure |
| test.test | POST                                   | dashboard/systems/notification/read                                | platform.notification.read              | Orchid\Platform\Http\Controllers\Systems\NotificationController@markAllAsRead      | web,platform         |
| test.test | POST                                   | dashboard/systems/notification/remove                              | platform.notification.remove            | Orchid\Platform\Http\Controllers\Systems\NotificationController@remove             | web,platform         |
| test.test | GET|HEAD                               | dashboard/systems/tags/{tags?}                                     | platform.systems.tag.search             | Orchid\Platform\Http\Controllers\Systems\TagsController@show                       | web,platform         |
| test.test | POST                                   | dashboard/systems/widget/{widget}/{key?}                           | platform.systems.widget                 | Orchid\Platform\Http\Controllers\Systems\WidgetController@index                    | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/users/{method?}/{argument?}                              | platform.systems.users                  | App\Orchid\Screens\User\UserListScreen@handle                                      | web,platform         |
| test.test | GET|HEAD|POST|PUT|PATCH|DELETE|OPTIONS | dashboard/users/{users}/edit/{method?}/{argument?}                 | platform.systems.users.edit             | App\Orchid\Screens\User\UserEditScreen@handle                                      | web,platform         |
| test.test | GET|HEAD                               | dashboard/{fallbackPlaceholder}                                    |                                         | Closure                                                                            | web,platform         |
+-----------+----------------------------------------+--------------------------------------------------------------------+-----------------------------------------+------------------------------------------------------------------------------------+----------------------+

Tinker:
gMac:test mathewparet$ php artisan tinker
Psy Shell v0.9.9 (PHP 7.3.1 — cli) by Justin Hileman
>>> config('platform.domain')
=> "test.test"
>>> config('platform.prefix')
=> "dashboard"
>>> exit
Exit:  Goodbye
gMac:test mathewparet

@mathewparet
Your domains do not match, you refer to: https://admin.test.test/dashboard , but the parameters indicate otherwise. bring them to one form.

That's because I re-installed it in an effort to try fix it and when I reinstalled I setup the url as test.test
Now I refer to https://test.test/dashboard
It asks me to login and after that I fall back to Laravel 404

@mathewparet
Good, but I am still convinced that the problem is due to the environment.
Could you just create a simple authorization using the command make:auth and tell if it works?

So I'll just do make:auth?
Since the user tables are quite similar (you only have extra fields), I
believe I do not need to run the user table migration. Correct?
On Fri, 8 Feb, 2019, 12:34 AM Alexandr Chernyaev, notifications@github.com
wrote:

@mathewparet https://github.com/mathewparet
Good, but I am still convinced that the problem is due to the environment.
Could you just create a simple authorization using the command make:auth
and tell if it works?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/orchidsoftware/platform/issues/723#issuecomment-461555210,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACRg6srp0OxEzFSamotR5Z-C9dN-TTToks5vLHivgaJpZM4YfzaL
.

--
Best Regards,
Mathew Paret

I ran php artisan make:auth and then tried test.test/dashboard/login (the old orchid login page came up). Then I went to test.test/login to use the laravel inbuild login. After login it went back to inbuilt /home page. But then when I go it /dashboard again it shows 404

excellent, it gives me a lot of information to identify the problem, but could you dump the user:
php artisan tinker:
dd (App \ User :: find (1)):
Most likely the user model was not inherited

gMac:test mathewparet$ php artisan tinker
Psy Shell v0.9.9 (PHP 7.3.1 — cli) by Justin Hileman
>>> dd(App\User::find(1))
App\User {#3225
  #fillable: array:3 [
    0 => "name"
    1 => "email"
    2 => "password"
  ]
  #hidden: array:2 [
    0 => "password"
    1 => "remember_token"
  ]
  #casts: array:1 [
    "email_verified_at" => "datetime"
  ]
  #table: "users"
  #allowedFilters: array:4 [
    0 => "id"
    1 => "name"
    2 => "email"
    3 => "permissions"
  ]
  #allowedSorts: array:3 [
    0 => "id"
    1 => "name"
    2 => "email"
  ]
  #connection: "mysql"
  #primaryKey: "id"
  #keyType: "int"
  +incrementing: true
  #with: []
  #withCount: []
  #perPage: 15
  +exists: true
  +wasRecentlyCreated: false
  #attributes: array:10 [
    "id" => 1
    "name" => "Mathew Paret"
    "email" => "mathewparet@gmail.com"
    "email_verified_at" => null
    "password" => "$2y$10$XQzD/9NSR3qzhC73gmCDieKGnzrNvBsNj3apwJG1NgaNhw.muByzy"
    "remember_token" => null
    "created_at" => "2019-02-07 16:08:00"
    "updated_at" => "2019-02-08 04:31:52"
    "last_login" => "2019-02-08 04:31:52"
    "permissions" => "{"platform.index": true, "platform.systems": true, "platform.bulldozer": true, "platform.systems.menu": true, "platform.systems.cache": true, "platform.systems.index": true, "platform.systems.media": true, "platform.systems.roles": true, "platform.systems.users": true, "platform.systems.backups": true, "platform.systems.category": true, "platform.systems.comments": true, "platform.systems.attachment": true, "platform.systems.announcement": true, "platform.entities.type.example-page": true, "platform.entities.type.example-post": true}"
  ]
  #original: array:10 [
    "id" => 1
    "name" => "Mathew Paret"
    "email" => "mathewparet@gmail.com"
    "email_verified_at" => null
    "password" => "$2y$10$XQzD/9NSR3qzhC73gmCDieKGnzrNvBsNj3apwJG1NgaNhw.muByzy"
    "remember_token" => null
    "created_at" => "2019-02-07 16:08:00"
    "updated_at" => "2019-02-08 04:31:52"
    "last_login" => "2019-02-08 04:31:52"
    "permissions" => "{"platform.index": true, "platform.systems": true, "platform.bulldozer": true, "platform.systems.menu": true, "platform.systems.cache": true, "platform.systems.index": true, "platform.systems.media": true, "platform.systems.roles": true, "platform.systems.users": true, "platform.systems.backups": true, "platform.systems.category": true, "platform.systems.comments": true, "platform.systems.attachment": true, "platform.systems.announcement": true, "platform.entities.type.example-page": true, "platform.entities.type.example-post": true}"
  ]
  #changes: []
  #dates: []
  #dateFormat: null
  #appends: []
  #dispatchesEvents: []
  #observables: []
  #relations: []
  #touches: []
  +timestamps: true
  #visible: []
  #guarded: array:1 [
    0 => "*"
  ]
  #rememberTokenName: "remember_token"
  -cachePermissions: null
  +jsonColumnName: "content"
}
gMac:test mathewparet$

Yes, everything is likely that way, laravel recently brought changes to his delivery: https://github.com/laravel/laravel/blob/master/app/User.php
but the installer did not find what to replace
https://github.com/orchidsoftware/platform/blob/master/src/Platform/Commands/InstallCommand.php
Inherit your model from the orchid model and everything will be fine, but I will try to update the installer so that no one will encounter the same problem.

Looks like it is already inherited Orchid's model. I found this in App\User.php
namespace App;

use Illuminate\Notifications\Notifiable;
use Illuminate\Contracts\Auth\MustVerifyEmail;
use Orchid\Platform\Models\User as Authenticatable;

class User extends Authenticatable
{

What does your user return?
php artisan tinker:
$user->hasAccess(“platform.index“)

gMac:test mathewparet$ php artisan tinker
Psy Shell v0.9.9 (PHP 7.3.1 — cli) by Justin Hileman
>>> $user = App\User::find(1);
=> App\User {#3225
     id: 1,
     name: "Mathew Paret",
     email: "mathewparet@gmail.com",
     email_verified_at: null,
     created_at: "2019-02-07 16:08:00",
     updated_at: "2019-02-08 04:31:52",
     last_login: "2019-02-08 04:31:52",
     permissions: "{"platform.index": true, "platform.systems": true, "platform.bulldozer": true, "platform.systems.menu": true, "platform.systems.cache": true, "platform.systems.index": true, "platform.systems.media": true, "platform.systems.roles": true, "platform.systems.users": true, "platform.systems.backups": true, "platform.systems.category": true, "platform.systems.comments": true, "platform.systems.attachment": true, "platform.systems.announcement": true, "platform.entities.type.example-page": true, "platform.entities.type.example-post": true}",
   }
>>> $user->hasAccess("platform.index");
=> false
>>> exit
Exit:  Goodbye
gMac:test mathewparet$

This is very strange, as you see in the user rights the specified value goes as true.
I still think that this is because of the update of the model of the User, and more precisely because of this line:
    /**
     * The attributes that should be cast to native types.
     *
     * @var array
     */
    protected $casts = [
        'email_verified_at' => 'datetime',
    ];

Because it replaces the base value:
    /**
     * @var array
     */
    protected $casts = [
        'permissions' => 'array',
    ];

Please add it now manually to your model.

And it worked! Ta-da.
Thank you :)

Run :
php artisan route:clear

authors: jonatemps mathewparet shinya-dono tabuna

repo: orchidsoftware/platform