Handles not aligned with selected area in Safari

When creating or selecting (when not in readOnly mode) an annotation in Safari, the handles are not aligned with the annotated region.

Just to confirm: does the offset between shape and handle shift when you zoom? (Offset should reach zero add you approach the highest zoom level.)

The offset does change when zooming but even at the max zoom level it is still there
https://user-images.githubusercontent.com/62853290/122820874-1d226a00-d2aa-11eb-979c-429368db2ae3.mp4

Ok, got some additional reports from friends testing this on Mac + did some digging. It's confirmed that this is because an unsupported feature in Safari. For the record:
https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/transform-origin
Two possible solutions to this are:

Go via CSS entirely (currently the transform is done via an SVG attribute - which is what Safari doesn't like)
Scale the handle radius rather than do a transform (might be a simpler solution)


Update powerbi-modeling-guidance-for-power-platform.md

The 80MB limit is removed from the Dataverse Connector now - the limit is changed to a maximum of 10 minutes to execute the query.

@davidiseminger
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


[3.0] Crash in audio engine when Godot closes

Tested on Godot 3.0 master 5e3fc7d06956dcda8b50cd4f028c83cf967f7223
Windows 10 64 bits, debug run from QtCreator
I created an empty project, but as soon as I open it, the project manager crashes. It looks like it tries to access buses[0] but the vector is in a somehow invalid state.
Then the editor opens background after I stop debugging.
It also crashes the same way when I close it.

I fixed this for Linux in #7833 I'll make a similar PR for win32


Dashboard Order Overview missing orders

Description
Orders between 0:00 and 1:59 are tracked as orders for the previous day.
Possible Solution
save timezone according to shop time (Europe/Berlin instead of UTC) OR request order stats with a proper offset to shop time.

Has been fixed in the last release. DateHistogram Association allows now a timezone argument


Links to Sierra API reference material don't work

https://github.com/search?q=org%3Awellcomecollection+https%3A%2F%2Ftechdocs.iii.com&type=code
Apart from the link to the top of the documentation: https://techdocs.iii.com/sierraapi/Content/titlePage.htm, none of the URLs returned by the search above resolve.

It looks like they've removed Reference/ and titlecased objects
e.g.
https://techdocs.iii.com/sierraapi/Content/zReference/objects/bibObjectDescription.htm
has become:
https://techdocs.iii.com/sierraapi/Content/zObjects/bibObjectDescription.htm


Support binary option for multipart/form-data type

Prerequisites

[X] I have written a descriptive issue title
[X] I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal
Hello! I'm using this module with @fastify/multipart. recently i found that when request type is multipart/form-data, it must be decoded with binary options like Buffer.from(data, 'binary') But, now it seems this module doesn't support binary options. So could i add binary option?
Motivation
When i send this request
curl --location --request POST 'http://localhost:3000/upload/templates' \
--form<EMAIL_ADDRESS>\
--form 'template="{}"' \
--form 'ratio="1"' \
--form 'categories=""'

lambda handler is (test with serverless-offline)
const ffy = require('fastify');
const fs = require('fs');
const fastify = ffy();

const opts = {
  attachFieldsToBody: true,
};

fastify.register(require('@fastify/multipart'), opts)

fastify.post('/upload/templates', async function (req, reply) {
  const data = await req.body;
  console.log(data);
  fs.writeFileSync('./image.png', data.thumbnail._buf);
  reply.send('done');
})

export const main = awsLambdaFastify(fastify);

buffer result must be
 thumbnail: {
    fieldname: 'thumbnail',
    filename: '24939410.png',
    encoding: '7bit',
    mimetype: 'image/png',
    file: FileStream {
      _readableState: [ReadableState],
      _events: [Object: null prototype],
      _eventsCount: 5,
      _maxListeners: undefined,
      bytesRead: 5062,
      truncated: false,
      _read: [Function (anonymous)],
      [Symbol(kCapture)]: false
    },
    fields: [Circular *1],
    _buf: <Buffer 89 50 4e 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 00 c8 00 00 00 c8 08 02 00 00 00 22 3a 39 c9 00 00 13 8d 49 44 41 54 78 9c ec dd 79 50 53 e7 fe ... 5012 more bytes>,
    toBuffer: [AsyncFunction: toBuffer]
  },

but actual result of this version is
thumbnail: {
    fieldname: 'thumbnail',
    filename: '24939410.png',
    encoding: '7bit',
    mimetype: 'image/png',
    file: FileStream {
      _readableState: [ReadableState],
      _events: [Object: null prototype],
      _eventsCount: 5,
      _maxListeners: undefined,
      bytesRead: 7603,
      truncated: false,
      _read: [Function (anonymous)],
      [Symbol(kCapture)]: false
    },
    fields: [Circular *1],
    _buf: <Buffer c2 89 50 4e 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 00 c3 88 00 00 00 c3 88 08 02 00 00 00 22 3a 39 c3 89 00 00 13 c2 8d 49 44 41 54 78 c2 9c c3 ... 7553 more bytes>,
    toBuffer: [AsyncFunction: toBuffer]
  },

Example
I think new option enforceBinaryOption should be added

property
description
default value

enforceBinaryOption

false

module.exports = () => {
    options.enforceBinaryOption = options.enforceBinaryOption ?? false
     ...

    //  multipart/form-data only works if encoding is binary
    // const payload = Buffer.from(event.body, 'binary')
    // const payload = Buffer.from(event.body, event.isBase64Encoded ? 'base64' : 'utf8')
   const payload = Buffer.from(event.body, options.enforceBinaryOption ?  'binary' :  (event.isBase64Encoded ? 'base64' : 'utf8'))
}

Why not using the binaryMimeTypes option?
What if you have other routes not needing binary?

btw: have you defined multipart/form-data as a binary media type for your API, like described here?
If so can you share how your lambda event looks like?

umm.. i tested with serverless-offline plugin and serveless config(serverless.ts) looks like
provider: {
    name: 'aws',
    runtime: 'nodejs14.x',
    lambdaHashingVersion: 20201221,
    stage: 'dev',
    region: 'ap-northeast-2',
    logRetentionInDays: 14,
    memorySize: 256,
    apiGateway: {
      binaryMediaTypes: ['multipart/form-data', 'image/*'],
      apiKeySourceType: 'HEADER',
      minimumCompressionSize: 5000,
    },
 ...
}

and this is lambda event
'create-template': {
      handler: 'src/functions/create-template/handler.main',
      events: [
        {
          http: {
            path: 'upload/templates',
            method: 'post',
            cors: corsPolicy,
            private: true,
          },
        },
      ],
    },

Would using the binaryMimeTypes option also work instead of introducing a new option? What if you have other routes not needing binary?

i already tried to solve this problem with binaryMimeType. but i can't still find reason why not working with binaryMimeType...

and this is lambda event

I mean the real aws lambda event that is passed in your lambda handle function...
something like:
exports.handler = async (event, context) => {
  console.log(JSON.stringify(event, null, 2))
  return proxy(event, context)
}

fyi: I just added some multipart tests.... seems to work: https://github.com/fastify/aws-lambda-fastify/commit/e274f7e63112670410aca0fb6ce200962d0c8536


Fix typos and grammar in the Readme

The Readme for the project had typos and grammar errors. This makes it look clumsy and not professional. I have fixed all such minor yet important lines.

I am working on this issue maintainers. I will raise a PR soon

I am working on this issue maintainers. I will raise a PR soon

yup thanx @vedanthv


Provide API's for accessing from any JS/TS Framework

schema.prisma.txt

for default tables only of course, any half competent coder will be able to use them as reference to build out from


(Web Components) Image not rendering for Content Block - Segmented on the Cloud example page

Description
Expected:
Images will render for Content Block - Segmented on the Cloud example page.
Actual:
Images not rendering for the Content Block - Segmented section in the Cloud example page.
Component(s) impacted
Content Block - Segmented
https://carbon-design-system.github.io/carbon-for-ibm-dotcom-web-components-test/next/cloud/index.html

Browser
Chrome, Safari, Firefox, Microsoft Edge
Carbon for IBM.com version
v1.32.0-rc.1
Severity
Severity 3 = The problem is visible or noticeable to users but does not impede the usability or functionality. Affects minor functionality, has a workaround.
Application/website
https://carbon-design-system.github.io/carbon-for-ibm-dotcom-web-components-test/next/
Package
@carbon/ibmdotcom-web-components
CodeSandbox example
https://carbon-design-system.github.io/carbon-for-ibm-dotcom-web-components-test/next/
Steps to reproduce the issue (if applicable)

Navigate to https://carbon-design-system.github.io/carbon-for-ibm-dotcom-web-components-test/next/cloud/index.html
Use the Table of Contents to navigate to the Content Block - Segmented section
Observe that images are not rendering

Release date (if applicable)
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

Hey team! Please add your planning poker estimate with ZenHub @annawen1 @ariellalgilmore @emyarod @IgnacioBecerra @kennylam

Consolidating Cloud example page to #8572


Refactor 22 lines occurring 2 times in client.go

I've selected for refactoring 22 lines of code which are duplicated in 1 file(s) (1, 2).  Addressing this will make our codebase more maintainable and improve Better Code Hub's Write Code Once guideline rating! 👍
Here's the gist of this guideline:

Definition 📖
Do not copy code.
Why❓
When code is copied, bugs need to be fixed in multiple places. This is both inefficient and a source of regression bugs.
How 🔧
Avoid duplication by never copy/pasting blocks of code and reduce duplication by extracting shared code, either to a new unit or introduce a superclass if the language permits.

You can find more info about this guideline in Building Maintainable Software. 📖

ℹ To know how many other refactoring candidates need addressing to get a guideline compliant, select some by clicking on the 🔲  next to them. The risk profile below the candidates signals (✅) when it's enough! 🏁

Good luck and happy coding! :shipit: :sparkles: :100:

I will give this a try! Please assign it to me.

@agarwalrounak please go ahead


Add TLS support for CTLog

Summary
This pull request introduces support for enabling TLS in communications with CTLog. By adding a new command-line flag --tls-ca-cert and implementing the necessary logic to handle CTLog certificates verification , this update enhances security.
Release Note

Feature: Added support for TLS in communication with the CTLog.
New Flag: --tls-ca-cert to specify the CA certificate file path for secure connections.
Behavior: If the --tls-ca-cert flag is not provided, the system will default to insecure connections.
Security: This update significantly enhances the security of data in transit by enabling TLS.

Resolves issue: https://github.com/sigstore/fulcio/issues/1717
Documentation

Hey @fghanmi, sorry for the delay! Is there anything from https://github.com/sigstore/rekor/pull/2164/ that we should pull into this PR so this is in sync? Other question, is there any place we can add minimal tests?

sigstore/rekor#2164
@haydentherapper,
I believe there is nothing to be added from sigstore/rekor#2164
Concerning the tests, I tried to run make up to docker-compose up, but the current configuration fails, I am not sure if I am running it wrong;
failed to load PEM certs file: open /etc/config/root.pem: permission denied

@fghanmi Hm, I didn't get such an error, I ran docker-compose build; docker-compose up.  Do you want to try again?

I had permissions issues on my host.. it's working fine now.

One more thing, I've noticed that ct_log server is not properly serving TLS when it's enabled. I've opened a small fix PR on certificate-transparency-go and when it's merged, I'll resume tests on this PR.

Sounds good, just ping this thread once you’ve tested it.

Sounds good, just ping this thread once you’ve tested it.

@haydentherapper, the update on certificate-transparency-go has been merged and I've tests the TLS communication between Fulcio and ct_server and it works fine now.
Inside Fulcio pod:
root@a899b97acafd:/go# curl  -v https://ct_server:6962/test --cacert /config/tls/ca.crt
*   Trying <IP_ADDRESS>:6962...
* Connected to ct_server (<IP_ADDRESS>) port 6962 (#0)
* ALPN: offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /config/tls/ca.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN: server accepted h2
* Server certificate:
*  subject: OU=Server; CN=*<EMAIL_ADDRESS>*  start date: Jul 30 18:59:47 2024 GMT
*  expire date: Sep 28 18:59:47 2024 GMT
*  subjectAltName: host "ct_server" matched cert's "ct_server"
*  issuer: CN=My CA
*  SSL certificate verify ok.
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /test]
* h2h3 [:scheme: https]
* h2h3 [:authority: ct_server:6962]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x557648bc0c80)
> GET /test HTTP/2
> Host: ct_server:6962
> user-agent: curl/7.88.1
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
< HTTP/2 404
< vary: Origin
< content-length: 0
< date: Tue, 30 Jul 2024 19:54:48 GMT
<
* Connection #0 to host ct_server left intact


PE-544, PE-563 commits

PE-544, 563 commits

PE-548,549,550 Mobile UI bugs Fix

> PE-548 - Mobile Web: Ownership transfer is hidden when applying for services
> PE-549- Mobile Web: Confirmation page UI changes
> PE-550- Mobile Web: Edit button on summary tab should be aligned with its section header


R_RISCV_CALL vs R_RISCV_CALL_PLT

call foo produces R_RISCV_CALL in -fno-pic mode and R_RISCV_CALL_PLT in -fpie/-fpic mode.
IMHO the distinction is not really useful. We can avoid R_RISCV_CALL and use R_RISCV_CALL_PLT everywhere (also in -fno-pic mode). If the target symbol is non-preemptable (local/hidden/not -shared/etc), the linker can omit PLT creation for R_RISCV_CALL_PLT. AFAICT, the only differences are these lines:
// binutils-gdb/bfd/elfnn-riscv.c
	case R_RISCV_CALL_PLT:
	  /* This symbol requires a procedure linkage table entry.  We
	     actually build the entry in adjust_dynamic_symbol,
	     because this might be a case of linking PIC code without
	     linking in any dynamic objects, in which case we don't
	     need to generate a procedure linkage table after all.  */

	  if (h != NULL)
	    {
	      h->needs_plt = 1;
	      h->plt.refcount += 1;
	    }
	  break;

	case R_RISCV_CALL:
	  /* Handle a call to an undefined weak function.  This won't be
	     relaxed, so we have to handle it here.  */
	  if (h != NULL && h->root.type == bfd_link_hash_undefweak
	      && h->plt.offset == MINUS_ONE)
	    {
	      /* We can use x0 as the base register.  */
	      bfd_vma insn = bfd_get_32 (input_bfd,
					 contents + rel->r_offset + 4);
	      insn &= ~(OP_MASK_RS1 << OP_SH_RS1);
	      bfd_put_32 (input_bfd, insn, contents + rel->r_offset + 4);
	      /* Set the relocation value so that we get 0 after the pc
		 relative adjustment.  */
	      relocation = sec_addr (input_section) + rel->r_offset;
	    }

I don't know much about BFD internals, but it appears the existence of a PLT in -fpie/-fpic code does not make differences. R_RISCV_CALL_PLT is not necessary to force the creation of a PLT if the symbol is non-preemptable.
In -fno-pic code, there may be a so-called "canonical PLT" (created due to an absolute/pc relative relocation to a function). However, its handling has nothing to do with the dichotomy of R_RISCV_CALL{,_PLT}.
I don't know what the weak-undef code does.
On x86_64, newer gas/llvm-mc (after r358652) produces R_X86_64_PLT32 for call foo and call foo@plt. R_X86_64_PLT32 can be optimized to R_X86_64_PC32 if the symbol is non-preemptable.
powerpc32 ELFv1 specifies R_PPC_LOCAL24PC R_PPC_REL24 and R_PPC_PLTREL24. powerpc64 ELFv2 just uses R_PPC64_REL24.

CALL is important for performance, as it supports bypassing the PLT when
the call is known to be local to the shared object.
On Tue, Jun 11, 2019 at 11:18 AM Fangrui Song<EMAIL_ADDRESS>wrote:

call foo produces R_RISCV_CALL in -fno-pic mode and R_RISCV_CALL_PLT in
-fpie/-fpic mode.
IMHO R_RISCV_CALL is not really useful. R_RISCV_CALL_PLT can also be used
in -fno-pic mode. If the target symbol is non-preemptable
(local/hidden/not -shared/etc), the linker can omit PLT creation for
R_RISCV_CALL_PLT. AFAICT, the only difference is the following code:
case R_RISCV_CALL:
/* Handle a call to an undefined weak function.  This won't be	     relaxed, so we have to handle it here.  /
if (h != NULL && h->root.type == bfd_link_hash_undefweak
&& h->plt.offset == MINUS_ONE)
{
/ We can use x0 as the base register.  /
bfd_vma insn = bfd_get_32 (input_bfd,
contents + rel->r_offset + 4);
insn &= ~(OP_MASK_RS1 << OP_SH_RS1);
bfd_put_32 (input_bfd, insn, contents + rel->r_offset + 4);
/ Set the relocation value so that we get 0 after the pc		 relative adjustment.  */
relocation = sec_addr (input_section) + rel->r_offset;
}
I'm not sure how these lines make a difference.
On x86_64, newer gas/llvm-mc (after r358652) produces R_X86_64_PLT32 for call
foo and call@plt. R_X86_64_PLT32 can be optimized to R_X86_64_PC32 if the
symbol is non-preemptable.
powerpc32 ELFv1 specifies R_PPC_LOCAL24PC R_PPC_REL24 and R_PPC_PLTREL24.
powerpc64 ELFv2 just uses R_PPC64_REL24.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/riscv/riscv-elf-psabi-doc/issues/98?email_source=notifications&email_token=AAH3XQS5NXB6KSLYSTYUM63PZ5UWRA5CNFSM4HW4HOIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GYYIKLA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH3XQSSY55BSEG6Z7OQCL3PZ5UWRANCNFSM4HW4HOIA
.

@aswaterman Such optimizations can be applied on R_RISCV_CALL_PLT, too (i386 x86-64 ppc{32,64} have similar optimizations). The preemptability is the property of the symbol, not the property of the relocation type. The evolution from powerpc ELFv1 to ELFv2 told me people did intend to assign such semantics to relocation types, but they found the semantics may be better handled on the symbol side.

call foo always gives R_RISCV_CALL; if you want R_RISCV_CALL_PLT you have to write call foo@plt.

I too see no justification for the distinction. It makes sense only on targets where there's a special ABI for calling into the PLT (typically, a register that must contain the GOT address, e.g. ebx on i386), in which case call points that aren't explicitly calling foo@PLT cannot be directed into a PLT thunk (a proper one - not an issue for the canonical non-PIC PLT thunk in a non-PIE main executable), and must be a link error (or a textrel) if the symbol is not locally defined.

@jrtc27 Sorry I made a mistake. I've changed the first sentence to use a C example instead.

I too see no justification for the distinction. It makes sense only on targets where there's a special ABI for calling into the PLT (typically, a register that must contain the GOT address, e.g. ebx on i386), in which case call points that aren't explicitly calling foo@PLT cannot be directed into a PLT thunk (a proper one - not an issue for the canonical non-PIC PLT thunk in a non-PIE main executable), and must be a link error (or a textrel) if the symbol is not locally defined.

Sometimes it's useful to ensure this specific call cannot be pre-empted. The FreeBSD libc at least makes use of this; you can work around the issue by defining a local symbol alias, but not distinguishing between call foo and call foo@plt would break this.

The RISC-V glibc port relies on the same property @jrtc27 mentioned.

Also I suppose a reason for the compiler not to emit call foo@plt with -fno-PIC is that it may have performed optimisations on the assumption that foo cannot be preempted, which is no longer true if you link it as a shared library (and that may well link just fine, especially if you used -fPIE and aren't using global non-static variables).

The undef weak check is to prevent relocation truncated errors when you call a weak function that does not get defined, and your code is compiled for an address above 0x80000000 on a 64-bit target.  For an undefined weak function, we need to make the target address 0.  But this is a pc-relative reloc, which has a 2GB range (medlow/medany) which means we can't actually reach 0 from any address above 0x80000000.  So we detect this case and rewrite the instruction and reloc to be x0 relative instead of pc-relative, and then we can resolve the reloc without error as address 0 is reachable from x0.  There are testcases for this in the ld testsuite, see for instance ld/testsuite/ld-riscv-elf/weakref*.
As a practical matter, since all linux code is compiled for a base address of 0, this only get triggered by embedded developers, so we only needed a fix for R_RISCV_CALL.

We can't drop support for R_RISCV_CALL as the ABI was fixed when we upstreamed glibc.
We could perhaps prefer R_RISCV_CALL_PLT and deprecate R_RISCV_CALL in future toolchains.  However, this isn't a bug fix, this is an enhancement.  As a practical matter, we only have one person supporting the entire toolchain, so there is no time available to do enhancement work like this.  There is only time available to fix stuff that is broken.  Perhaps at some point in the future we will have people available to look at issues like this.


Initial commit - New Sample - Numbered List Cards

Q
A

Bug fix?
no

New sample?
yes

Related issues?
N/A

What's in this Pull Request?
I have created a new JSON View Formatter sample that turns list items into numbered list cards. The numbering is done using @rowIndex JSON formatting value.
The sample includes two different JSON files: one where the numbering background uses a SharePoint theme color, and another that uses a custom image for the background.
Thanks for your contribution! Sharing is caring.

So cool cards🤩🤩🤩
Thanks again for the awesome sample @tvahk !


Implement Rorschach#setACL()

Implemented SetACLBuilder class and added Rorschach#setACL() method to instantiate builder.

Coverage decreased (-1.51%) to 98.49% when pulling c69b1b14d67e06aac901f62773c981a34c1ea512 on estliberitas:set-acl-implementation into 2c897b8bdb46fb192275cc30288f54c202adc6fc on slideme:master.

Coverage remained the same at 100.0% when pulling 806420c9f3650b504f291ceb616fca0ce0d4b85e on estliberitas:set-acl-implementation into 2c897b8bdb46fb192275cc30288f54c202adc6fc on slideme:master.

Coverage remained the same at 100.0% when pulling 806420c9f3650b504f291ceb616fca0ce0d4b85e on estliberitas:set-acl-implementation into 2c897b8bdb46fb192275cc30288f54c202adc6fc on slideme:master.

Closes #12


Dropped support for python 3.6, 3.7 and added support for python 3.12

Description

Dropped support for python 3.6, 3.7
Added support for python 3.12
Bumps aiohttp from >=3,<4 to >=3.9.2,<4
Bumps black to >=24.3.0

Issues Resolved
Closes #715
Closes #430
Closes #704
Closes #688
Closes #687
Closes #622
Closes #621
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Failing tests are unrelated to this PR.
Working on fixing generator to make it work with latest OpenSearch openapi specification


Cell selections are sticking to the view

Please see http://stackoverflow.com/questions/28547303/how-do-i-clear-a-collection-view-cells-view-layer-cache-during-animation
Removing this layout solves the problem. Please see the comments in there too and feel free to ask me any questions. Thanks!

It's best if you can provide a sample project.
I updated the following methods in CSLockedHeaderViewController.m, and the results are looking fine to me
- (UICollectionViewCell *)collectionView:(UICollectionView *)collectionView cellForItemAtIndexPath:(NSIndexPath *)indexPath {

    NSDictionary *obj = self.sections[indexPath.section];

    CSCell *cell = [collectionView dequeueReusableCellWithReuseIdentifier:@"cell"
                                                             forIndexPath:indexPath];

    cell.textLabel.text = [[obj allValues] firstObject];

    CALayer *layer = cell.textLabel.layer;
    layer.borderColor = [UIColor blackColor].CGColor;
    layer.borderWidth = 1;
    layer.cornerRadius = 10;

    return cell;
}

- (void)collectionView:(UICollectionView *)collectionView didSelectItemAtIndexPath:(NSIndexPath *)indexPath {

    CSCell *cell = (CSCell *)[collectionView cellForItemAtIndexPath:indexPath];

    CABasicAnimation *animation = [CABasicAnimation animationWithKeyPath:@"bounds"];

    animation.duration = 2.0;
    animation.toValue = [NSValue valueWithCGRect:CGRectMake(10, 10, 60, 60)];
    [cell.textLabel.layer addAnimation:animation forKey:@"transform"];
}

It's also good to try using CAAnimation instead of POP and see if that happens?


GKE cluster information is wrong.

Rancher versions:
rancher/server or rancher/rancher: 2.0.8 latest stable.
kubernetes (if applicable): v1.10.7-gke.2
Docker version: (docker version,docker info preferred)
17.3.2
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
GKE
I've just created new kubernetes cluster on GKE. Here are few errors I've noticed and i guess it should be reported here.
Issue 1.

Cluster CPU, RAM usage says n/a
Issue 2.

Node specific CPU, RAM shows wrong information. I've selected standard 1cpu, 3.75gb ram option when creating cluster and confirmed it in google compute engine page. However in rancher, it shows wrong.
0.9CPU , 2.6 GiB Ram?? What does it mean?

3.75gb is the raw size of the VM, a bunch of that is reserved by Google for k8s and the OS, so ~2.6gb is what's left as allocatable.  CPU works similarly.

Thanks for your report!
For issue 2, please check https://github.com/rancher/rancher/issues/15992#issuecomment-427687108
Close in favor of https://github.com/rancher/rancher/issues/15272 for issue 1.

Well that reserved amount is so unfortunate. Take a look here, if 1.15GB RAM and 0.10% of CPU is reserved, why is there still reserved amount there? As picture says:
0.6 of 2.6 GiB reserved
0.6 of 0.9 reserved

With kubectl describe node, you can find the Allocatable, Capacity and Allocated resources info.
The dashboard shows the sum(requested)/sum(allocatable) of each node in the cluster


Update README.md

Change the footer in the main README.md file from to 2021

git revert 2022 XYZ, Inc.


File status highlight stopped working with PhpStorm 10

Hey there, as per subject the file status highlight feature seems to have problem with PhpStorm 10, I recently updated and noticed that neither files nor folder are getting highlighted as expected. Anyone else experienced the problem or know how to solve it? Thanks a lot for your help.

@debo Thank you for reporting. Issue will be handled with #174
Please refer to it and try to apply my possible fix scenario to help me investigating this problem.


DPL-538 Replace BFormSelect with a new tailwind based select component

User story
As part of clean migration from bootstrap (DPL-483) , create a custom component to replace the bootstrap BFormSelect component
Who are the primary contacts for this story
Steve/Seena
Who is the nominated tester for UAT
e.g. John S (don't include surnames in public repos)
Acceptance criteria
To be considered successful the solution must allow:

[ ] A new traction-select component that uses tailwind styling
[ ] The new component should contain all existing functionalities of BFormSelect that are currently in use
[ ] Replace all existing BFormSelect references with new component
[ ] Remove BFormSelect from globally imported list

References
This story has a non-blocking relationship with:

#827

Closing as in done column


OCPBUGS-15737: Re-enable psa plugin

Upstream PSA changes were introduced in Kubernetes 1.25 (OpenShift 4.12). Downstream OLM has a plug-in that integrates with the security team's Cluster-Policy-Constroller that helps smooth out the transition and helps avoid stuck workloads for our customers. We had to disable the plug-in in 4.12. It's not ready to be re-enabled.

/test unit-olm

/override ci/prow/verify
this stage fails because there are changes to the staging directory. These changes affect downstream files only. ok to override.

/label cherry-pick-approved
/label qe-approved

/override verify
Changes here are in downstream only files in the staging (which normally is closed for changes outside of upstream commits). This is one of the rare cases where we need to make changes to downstream only behavior that must exist in the olm src tree in the staging directory.

/label backport-risk-assessed

/override ci/prow/verify

/jira-refresh

/jira refresh

/jira refresh

/jira refresh

/jira refresh


How is the latent image (64x64) used in tutorial?

Appreciate the author's great great work.
My question is about the latent image (compressed from 512x512 original image). In author's paper, it mentioned that ControlNet trained a new lite CNN to compress the original image(like depth map / seg map / edge map?) to latent image. Is that crucial when we training on a customed dataset? Because I don't  see any related information about training the lite CNN in the example shown in tutorial. Should we retrain a new CNN to obtain latent image on new dataset?

This is the model used for encoding new control information into latent space.
https://github.com/lllyasviel/ControlNet/blob/main/cldm/cldm.py#L146-L162
And this control information in the bigger ControlLDM.
https://github.com/lllyasviel/ControlNet/blob/main/cldm/cldm.py#L311
https://github.com/lllyasviel/ControlNet/blob/main/cldm/cldm.py#L333
https://github.com/lllyasviel/ControlNet/blob/main/cldm/cldm.py#L333
This lite CNN is trained during training.

thanks @xiankgx  for your detailed answer! That's super helpful for me.


The Objective-C example(Hello.m) run with command infer run -- clang -c Hello.m failed

I use the <infer-linux64-v0.13.1 release> version.
And run ./build-infer.sh and sudo make install in the Ubuntu 16.04.
The java, C, Android example run normally. However, when I run the Objective-C example I fails.
The error is shown as below.
ca@ca:/home/ca/Project/infer-linux64-v0.13.1/examples$ infer run -- clang -c Hello.m
Capturing in make/cc mode...
Hello.m:10:9: fatal error: 'Foundation/Foundation.h' file not found
#import <Foundation/Foundation.h>
^~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
Error: the following clang command did not run successfully:
'/usr/local/lib/infer/facebook-clang-plugins/clang/install/bin/clang'<EMAIL_ADDRESS>

For Objective-C analysis to run you need to have Xcode installed, it also only works in MacOS. You can try running clang -c Hello.m and checking that it succeeds first.

@dulmarod
first, i use clang -c Hello.m and it succeeds.
but, when i use  infer run -- clang -c Hello.m, I occured the same error.

And Which version of mac os infer support?

You said earlier you are using the <infer-linux64-v0.13.1 release> version. That may be the problem, iOS analysis is only supported in MacOS. We support XCode 9.2 version.

My mac :
infer v0.13.0
Mac 10.13.2 (17C88)
XCode 9.2
I think that maybe infer-v0.13.0/lib/infer/facebook-clang-plugins/clang cant not find the "Fundation.h" which is in the Xcode.

@cyw3 can you open a separate issue for your problem? Thanks.

Oh, I see there's already #842, nevermind.


Feature request: Support python control flow in custom_transforms functions

For fitting parameter values for ODEs a la the adjoint sensitivity method, we might want to override the gradient computation for the forward ODE solve. More concretely, we might have an integrator function odeint that takes in a gradient field f, initial state y0, and a sequence of times ts to be evaluated at.
One specific use case where supporting control-flow in custom_transforms will be useful is for the backward integration (which might involve adaptive solvers, hence non-trivial control-flow). Ideally, we would like to write code as follows
@custom_transforms
def odeint(y0, ts):
  pass  # Some procedure integrating the vector field `f`.

def vjp_y0(g, ans, y0, ts):
  pass # A while loop and some if statements used to determine integration step size.

defvjp(odeint, vjp_y0, None)

Does #1255 fix this?

Correct me if I'm wrong, but the custom vjp functions here still aren't using Python control-flow. I understand that there are workarounds using the lax-based control-flow, but it would be nice if could just write Python loops and if-statements.
This is perhaps not necessary for the ODE adjoint, and the example code doesn't seem that complicated. But it might present some overhead when the research we're trying to implement has more complicated control-flow.

Unsurprisingly, it seems that unless you want to use tf.function or graph-mode execution, writing a few Python if-statements and loops in the gradient function used for tf.custom_gradient doesn't cause any trouble for TF2.0.
Being able to do this in JAX would be quite helpful to a researcher where in many cases the goal is to test out ideas fast.

One option for using arbitrary control flow is to write new JAX primitives: https://jax.readthedocs.io/en/latest/notebooks/How_JAX_primitives_work.html

We’re working on this. The reason it isn’t as simple as it was for Autograd is that JAX used a new autodiff design in which we only have forward mode and derive reverse mode automatically (composing forward mode with other transformations). That confers several advantages, but a disadvantage is that since the system itself doesn’t work in terms of VJPs, supporting custom VJPs is tricky. (You can write custom JVPs, ie forward-mode rules, with arbitrary Python control flow now.)

#2026 finally landed and added support for Python control flow in custom derivative rules! (The API also changed, so take a look at the tutorial notebook.)

Thanks for consistently pushing this forward and the amazing work!


[DEBUG] Rhoaieng 5344

Issue link

What changes have been made

Verification steps

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

Changes merged, closing this debug PR


support eval scripting commands (poc)

We should discuss this one. I really hate the Lettuce API ...  not sure or not whether we should break from it but this is going to be very inconvenient for scala programmers to work with and not at all intuitive. That said, at least I got it working.

I used to refer to this other lib : https://github.com/profunktor/redis4cats/blob/6fcd86e62a42cf1a73f1cdc514b169c77cdb3472/modules/effects/src/main/scala/dev/profunktor/redis4cats/algebra/scripts.scala#L24 as they also had to go through many hoops to workaround the Lettuce API for some cases ...

I used to refer to this other lib : https://github.com/profunktor/redis4cats/blob/6fcd86e62a42cf1a73f1cdc514b169c77cdb3472/modules/effects/src/main/scala/dev/profunktor/redis4cats/algebra/scripts.scala#L24 as they also had to go through many hoops to workaround the Lettuce API for some cases ...

Yep. good hints in there. I made some changes that clean some of it up. Probably need a way to clean up the response types a little more but it is better than it was.

This should address issue #42


Calling LoadModel from .net core WebAPI throws SEHException

exception:
   at BlingFire.BlingFireUtils.LoadModel(Byte[] modelName)    at BlingFire.BlingFireUtils.LoadModel(String modelName) in C:\Users\vanac\.nuget\packages\blingfirenuget\0.1.4\contentFiles\cs\any\BlingFireUtils.cs:line 23
The same code was tested with unit tests and works perfectly. It only throws the exception when i send a request to a webAPI using the same component. (this behaviour is the same for running the api through IIS as well as running it directly.)
EDIT: code causing this issue:
public TextTokenizer()         {             _EncoderModel = BlingFireUtils.LoadModel("./bert_base_tok.bin");         }

Update: The fault was mine. when running in a webApi, the application runs in a workingdirectory different from where the assembly is located, which caused it to not find the file, but the exception didn't really tell me much. I consider this closed.

Update: The fault was mine. when running in a webApi, the application runs in a workingdirectory different from where the assembly is located, which caused it to not find the file, but the exception didn't really tell me much. I consider this closed.

There was a long lasting feature request, that API should not throw the exception and rather return an error code. My apologies it is still not done... if you want feel free to take on this task :-) though.

There was a long lasting feature request, that API should not throw the exception and rather return an error code. My apologies it is still not done... if you want feel free to take on this task :-) though.


We need to create some introductory materials for THs

Source
Internal discussion in Swarm team, 13th June 2024
Problem
Each TH should begin with a clear and brief explanation of what TH is

Current situation

there is no introductor y material to welcome people to TH and explain succinctly what it is

How we want the current situation to change:
We need material that quickly and clearly answers the following

What is Town Hall (TH)?
Who Facilitate in Town Halls?
Why do we have Town Halls?
Why do we like to join Town Halls?
What is After Town Hall (ATH)?
Why do we like to join After Town Halls?
Why do we have After Town Halls?
How to submit Town Hall agendas?
Where to submit questions for Town Hall?
How to help or question prepared After Town Halls?

Who are the stakeholders?

Any previous attempts to address this problem?

Questions and possible approaches:

What format should it be in? A script? A slide deck? Something else?
Who will create it?

Ideas:

Measure:

Initially put the above list on a Google doc open to comments.
We create - Nicodemus interested in editing - will share link in here
Deadline for comments is this day next week
Abe will attach a file with his own ideas on how it should go
Attractive to attend if you know that every time you do, you get to take part in taking part in the next tranche of questions about how we are going to refine it all. i.e. you are going to have the chance to vote on the next iteration. We need to design clear questions ahead of time and present them.
Feedback loop for people to raise issues. A pathway for people to submit issues that people will vote on - like a change log?. We ask people to also define what the voting options should be.
Present the info as slides
Nicodemus and marketing group happy to help us get the info out!
PipeDrive could help us get a grip on phases and cycles of development? No cos not opensource, but cvan we adapt it?

Created the Google Doc under Swarm Account: https://docs.google.com/document/d/1wheIDiU9zlVui2bdXfEq9Wip2_C-CiOfaENoBH6S2to/edit?usp=sharing

Slides are here https://docs.google.com/presentation/d/1RURCxhUYcfNtGjXe2G_N1VXJ53Zifj-Ib9IqRD3EFNg/edit?usp=sharing
They can now be adapted each week

Slides are here https://docs.google.com/presentation/d/1RURCxhUYcfNtGjXe2G_N1VXJ53Zifj-Ib9IqRD3EFNg/edit?usp=sharing
They can now be adapted each week

it seems we need to use Intersect Team created slide templates Next Month

Vani will re-do the slides using the Intersect template

here are the new slides using Intersect template - https://docs.google.com/presentation/d/12oZ7jSuTko34hvfxY4bzVO0ygmutxNTUPfjJ-Qq7mIg/edit?usp=sharing
this issue feels "fixed", at least for now

Yep we got no complaints this time.
The above template was copied to Swarm Drive and modified to fit the latest changes for the July 25th Town Hall
https://docs.google.com/presentation/d/1BEDX9XvaHdWeY-sy6Tq3BvcCzwlBzJnvt1-DbmIGE_k/edit?usp=sharing


Customise Homepage

Fixed #75

Added featured content support on Homepage in wagtail admin
Added banners support on Homepage wagtail admin
Made menu flat (no sub-navigation)
Set default to True for show in menus for sections and articles

Hey @dannyparsons

menu support included, you can create a new menu from Settings>Main Menu, just make sure the page you are adding is eligible to be shown in the menu by checking the promote tab. Levels for the menu could also be selected from menu settings.

featured content support included, you can add featured contents on homepage.

footer support included, you can create new snippet for footer from wagtail menu.

Thanks for this. This is looking good, a few points:

Can we set Show in menus to be checked by default for articles and sections? I can see this being confusing for CMS users when creating the menu and not knowing why an item doesn't appear.
In Settings > Main Menu > Settings, can you set the default to be 1. No Sub-navigation (flat) - this is what we want the sites to use.
The Featured Content works well. When I run it, it still shows all the articles first and then the featured content below. We only want the featured content to show now, not all the articles. Not sure if that's just for me?
Footers also display. Probably need a design and functionality discussion around these, but not for this PR

* banners included, with clickable images for internal and external pages
* made **Show in menus** default to checked
* made menu sub navigation to **flat**
* removed old articles from homepage

Thanks. Can you swap Banners and Featured Content sections in the CMS when editing the homepage? Banners appear above so it will be more logical for it to be above in the CMS as well.

unified migration files, so before pulling new code run the following commands
make ssh
cd /app/
python manage.py migrate home 0004

then you can pull new code and run new migrations

Looks good. Minor points:

Could you make the Banner image mandatory? It isn't in v1 but I think it needs to be otherwise there isn't anything to display
Could you add the help text on hover for the banner fields? (see below) Something like:
Banner image: Image to display as the banner
Link page: Optional page to which the banner will link to
External link: Optional external link which a banner will link to eg https://www.google.com

@dannyparsons addressed both points.

Thanks.
@istride raised some important points on use of banners https://github.com/unicef/iogt/issues/75#issuecomment-852264394 I think that needs to be talked through with him next.

@dannyparsons banner and footer are implemented as pages now, kindly check.

fixed migration files, so before pulling new code run the following commands
make ssh
cd /app/
python manage.py migrate home 0004

then you can pull new code and run new migrations

Thanks.
I was assuming that banners and footers would still be selected in a field from the homepage like the featured content. This would be desirable for the CMS editors. It would mean easier control over which banners are included and in what order. Banners could be created under a Banners Index Page (like in v1), instead of having to be children of the homepage. The same for footer. I think that would make it CMS editing clearer.

Hey @dannyparsons,
I have implemented Banner and Footer Index Pages (to hold all banners and footers respectively) and Banner and Footer for individual entity just like V1 and I have also added the ability to select banners for the home page just like featured content. One thing I want to confirm is that should selecting footer also be an option on home page?

fixed migration files, so before pulling new code run the following commands
make ssh
cd /app/
python manage.py migrate home 0004

then you can pull new code and run new migrations

Thanks. I like this implementation because:

Banners are defined in their own place (Banner Index Page) so don't clutter the site structure.
The selection of banners as a field on the homepage means the things that will appear on the homepage are defined in one place. Also Laurie mentioned that the ordering of banners on the Banner Index Page in v1 is quite confusing. Ordering them on the homepage field is a much nice interface.
Banners don't have to be put back into draft for them to be hidden (they are just removed from the homepage)
If we ever wanted to use banners on other pages we could easily do this.

Footers are maybe different because they don't just appear on the homepage they appear across the site. So conceptually they don't belong on the homepage. But it would be much better to have the ordering of them done through the page selection way instead of the Footer Index Page.
I think we need input from @istride before deciding.

@dannyparsons @istride reverted footer changes and currently, this PR contains featured content and banner.
Also fixed migration files, so before pulling new code run the following commands
make ssh
cd /app/
python manage.py migrate home 0004

then you can pull new code and run new migrations

@istride changes addressed.

Merged manually as I had to merge changes from develop and recreate the database migrations.


[1.11] Fix usage of ISTIO_MUTUAL with credentialName. (#36935)

Currently, if a user sets both of these, there is no validation or
warning. What ends up happening is the ISTIO_MUTUAL part is completely
ignored, and you get one way TLS using the credentialName configs.
This is highly unexpected and may lead to misconfigurations where users
expect mTLS to be used/enforce, but it is not.
This modifies the behavior to reject this in validation, and if are both
somehow set then the ISTIO_MUTUAL has precedence. This mirrors the
behavior for file-mounted cert references in the original PR 2.5 years
ago:
https://github.com/istio/istio/commit/fd80f5d11d0ad527d0c3de73f06aa0c2d4501c8e#diff-1488ede8a94d615faf5bbbd17f81fdb16b0409a3cc21ae6525a91991e55df34fR381.
Because this represents a backwards incompatible change, and there are
known users with this configuration, an opt-out flag is added. This PR
will be backported with settings:

master, 1.13 - new behavior by default
1.12, 1.11 - old behavior by default, but with a new warning

(cherry picked from commit b44595320593f4b3325070cb794bad01a04a326f)
Please provide a description of this PR:

/retest


Initial Python version

Implemented:

Automatic loading and caching of CRN daily data, ALEXI daily ET, and PRISM daily P data from their remote sources

note that ALEXI ET seems to be no longer available during current year (2023)

Multiple initial condition options, including based on CRN SM
Integration (applying P - ET using the stored slope weights to compute next day's SM)
Python packaging
Example plots
Development setup instructions
pre-commit checks

Not (yet?) implemented:

(re)creating the weights
using min/maxmoist to clip
(re)creating min/maxmoist for different time periods
using local ALEXI ET store

need this to some extent since less available

smn (the non-weighted version in the original code)

should do this, since the original code seems to consider sm - smn (the diff) a product as well

mm units option (instead of current m3 m-3)

Planning to merge this soon, so can address remaining with targeted issues and PRs.

@zmoon Thanks for all of your hard work

Definitely needed, and you get the credit for that!
On Fri, Mar 17, 2023, 10:21 AM Zachary Moon @.***>
wrote:

@drnimbusrain https://github.com/drnimbusrain reminded that the Python
package name should be swampy or swamppy...
—
Reply to this email directly, view it on GitHub
https://github.com/noaa-oar-arl/SWAMP/pull/1#issuecomment-1473918795,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGLFYNU4TLNUNBLJG672L53W4RXM5ANCNFSM6AAAAAAV22PVFY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@drnimbusrain can you merge this or give me access to do so?

@zmoon I have updated your permissions so you are now admin of this repository.  Go ahead and merge.


help: Update invite new user documentation.

Follow-up to #28819.
Notes:

The first commit fixes the Manage pending invitations documentation for invitations being part of the Users tab in the Organization settings overlay.
The second commit fixes the instructions that had been incorrectly changed in commit 1045e322fda3d. These instructions are from the gear menu and not from the Organization settings overlay.
The third commit updates the email invitation documentation for the new feature of getting a direct message notification when an email invitation is accepted.

Questions:

When looking at the instructions for generation a reusable invitation link, that we use "invite" and not "invitation" for a number of strings in the model. I wasn't sure if that was something we wanted to update or not.

Screenshots and screen captures:

Updated instructions for "Send email invitations"
Current documentation

Updated instructions for "Create reusable invitation link"
Current documentation

Updated instructions for "Manage pending invitations" with relative link
Current documentation

Updated instructions for "Manage pending invitations" without relative link
Current documentation

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

Oh, is this PR overlapping with #30761? @shubham-padia FYI

I'll start a design discussion on CZO about the strings that use "invite" as a noun/adjective question.

These changes look good to me!
https://github.com/zulip/zulip/pull/30761 is more complex, and will require some care before we can merge, so let's get this integrated.

When looking at the instructions for generation a reusable invitation link, that we use "invite" and not "invitation" for a number of strings in the model. I wasn't sure if that was something we wanted to update or not.

@laurynmm will start a #design discussion for visibility. @timabbott FYI

Looks great, merged, since my only comment was on a potential improvement to existing text that might be a good follow-up. Thanks @laurynmm!

CZO design discussion about "invite" strings: https://chat.zulip.org/#narrow/stream/101-design/topic/invite.20user.20modal.3A.20.22invite.22.20strings/near/1852702


error run engep_predict

Hi,
It seems that the newest version of propr (v5.0.1) doesn't have phis function anymore. So this will cause the error when I try to run engep_predict.
And also the two similarity measures "phi_s" and "rho_p" will somehow create NA value then fail to finish the analysis.
Could you please check the source code and fix this two bugs here?
Thanks a lot!

Hi,
Thank you for reaching out and bringing this issue to our attention. We appreciate your interest in the ENGEP package. Based on the error message and the details you provided, it seems like the problem might be related to an upgrade in the propr package (https://github.com/tpq/propr), affecting the propr::phi and propr::perb functions.
Here are some recommendations:

Sub-Reference Size: Ensure that the sub-reference size is adequately chosen, avoiding sizes that are too small (e.g., 10 cells and 50 cells), as the default maximum k value in kNN regression is set to 50.
Error Cause: The error is likely due to the recent upgrade in the propr package. We acknowledge this issue and plan to release an update for the ENGEP package to address it promptly.
Potential Solutions:

Install a previous version of the propr package (e.g., version ‘4.2.6’) until the ENGEP package is updated.
If installation issues persist, you can proceed by using the remaining eight similarity measures, excluding the two in the propr package, though this might result in a slight loss of accuracy.

engep_predict <- engep_predict(osmfish,ref_list,pre_genes,parallel=T,get_baes=T,get_weight=T,
                              simi_list = c("pearson", "spearman", "cosine", "jaccard", "weighted_rank",
                                            "manhattan", "canberra", "euclidean"))

Package Versions as a Reference:

sessionInfo()
R version 4.1.1 (2021-08-10)
Platform: x86_64-conda-linux-gnu (64-bit)
Running under: Ubuntu 18.04.5 LTS

Matrix products: default
BLAS/LAPACK: /home/zhangxf/anaconda3/envs/yangst/lib/libopenblasp-r0.3.18.so
locale:
[1] LC_CTYPE=en_US.UTF-8       LC_NUMERIC=C
[3] LC_TIME=en_US.UTF-8        LC_COLLATE=en_US.UTF-8
[5] LC_MONETARY=en_US.UTF-8    LC_MESSAGES=en_US.UTF-8
[7] LC_PAPER=en_US.UTF-8       LC_NAME=C
[9] LC_ADDRESS=C               LC_TELEPHONE=C
[11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base
other attached packages:
[1] Matrix_1.3-4 ENGEP_1.0
loaded via a namespace (and not attached):
[1] compiler_4.1.1  parallel_4.1.1  grid_4.1.1      lattice_0.20-45

library(propr)
packageVersion("propr")
[1] ‘4.2.6’

We appreciate your patience, and we're actively working on resolving this issue. Feel free to reach out if you have further questions or concerns.


Enhancements to Background, Map Data, Help panes

I've been working on these for a few days, so I'm going to just roll a few semi-related things into one PR.

[x] #4553
[x] #4570
[ ] #4546
[ ] #2211  😏

The .gif doesn't do this justice, but here's what I've been working on the past few days.  These sliders make it possible to improve any imagery. I'm pretty excited about it 😄
This feature uses CSS filters to close #2211, something that's been in the back of my mind for a while.  It will work well in Chrome and Firefox and some partial to full support in Safari, Edge, and not sure about IE11.

This spun off from an effort to slightly improve the usability of the side panes.  The sliders replace the old "brightness buttons", which were a bit confusing to people (they did not look like buttons) and could only do steps from 25%, 50%, 70%, 100%.

Talking of the background pane - is it possible to do something like in this image https://github.com/openstreetmap/iD/issues/3453#issuecomment-258199010 and hide all background > 20 years old in a "historic imagery" dropdown? Because the background list is now quite long for mappers in the UK.

Talking of the background pane - is it possible to do something like in this image #3453 (comment) and hide all background > 20 years old in a "historic imagery" dropdown? Because the background list is now quite long for mappers in the UK.

This is a really good idea.. I don't want to extend the scope of the PR right now but I do want to think about letting people customize the background imagery list.. e.g. add more / or remove the ones that they never want to see.   I'll reopen and add some comment to #3453


Authentication using OIDC

What is the URL of the document?
The URL to help identify the document.
https://awslabs.github.io/kubeflow-manifests/docs/deployment/vanilla/guide/#dex
Which section(s) is the issue in?
The sections(s) within the document that have issue in.
Dex
What needs fixing and describe the solution you'd like?
A clear and concise description of what the issue is.
Need guides/examples of setting up authentication with OIDC as alternative to Cognito for managing user authentication.
Additional context
Add any other context about the problem here.
Cognito is not supported in some AWS region like Milan, Cape Town, and Jakarta, but sometimes people have to run workload in specific region for regulatory/compliance reason.

Hi @rizadiawan, thanks for creating the issue. For your usecase, there are 2 ways to go about this:

If you plan to with set up a load balancer, you can directly configure the load balancer to authenticate using auth-idp-oidc annotation on Ingress or
dex connector for OIDC based iDP

I havent used either of this but have experience configuring Load balancer based authentication. Would you be interested in looking into this? We can guide you based on your idP. If you are okay with using Load balancer, following are the details you will need from your idP to configure it:

Issuer Endpoint
Authorization Endpoint
UserInfo Endpoint
Token Endpoint
ClientId and Client Secret for your App in idP

I am asking these information based on the following docs:

https://docs.aws.amazon.com/elasticloadbalancing/latest/application/listener-authenticate-users.html
https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/ingress/annotations/#auth-idp-oidc

I expect these information to be used on the ingress like:
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: istio-ingress
  annotations:
    alb.ingress.kubernetes.io/auth-type: oidc
    alb.ingress.kubernetes.io/auth-idp-oidc: '{"Issuer":"$(oidcIssuer)","AuthorizationEndpoint":"$(oidcAuthorizationEndpoint)","TokenEndpoint":"$(oidcTokenEndpoint)","UserInfoEndpoint":"$(oidcUserInfoEndpoint)","SecretName":"$(oidcSecretName)"}'
    alb.ingress.kubernetes.io/certificate-arn: $(certArn)
    alb.ingress.kubernetes.io/listen-ports: '[{"HTTPS":443}]'
    alb.ingress.kubernetes.io/auth-scope: 'email openid profile'
    alb.ingress.kubernetes.io/scheme: internet-facing
    kubernetes.io/ingress.class: alb
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: istio-ingressgateway
          servicePort: 80
        path: /*

oidcSecretName will be a K8s secret with the ClientId and Client Secret

Hi @surajkota, thanks for reply.
I've followed your guide above with an Auth0 app, and user is correctly presented with Auth0 login screen when opening the dashboard URL. However, upon entering correct credential, instead of logging in the user to the dashboard, the user is redirected back to local Dex login URL, for example: https://kubeflow.kubeflow.rizasaputra.com/dex/auth/local?req=q356x74qwzc7atv5fb234ecyh.
Only after entering local Dex credential the user is taken to dashboard.
For some additional context, this is what I do:

Set up an Auth0 app in a domain, and obtained these details:

Issuer Endpoint: https://kftest.jp.auth0.com/
Authorization Endpoint: https://kftest.jp.auth0.com/authorize
UserInfo Endpoint: https://kftest.jp.auth0.com/userinfo
Token Endpoint: https://kftest.jp.auth0.com/oauth/token
Client ID and client secret

Do some necessary setup:

Add permission to read secrets to Clusterrole aws-load-balancer-controller-role
Remove duplicate aws-load-balancer-controller service account definition from load balancer controller manifest as instructed here: https://docs.aws.amazon.com/eks/latest/userguide/aws-load-balancer-controller.html on point 5.b.ii in tab Kubernetes manifest

Register users on Auth0 and create corresponding profiles manually with same email https://github.com/rizadiawan/kubeflow-manifests/blob/oidc-auth/deployments/profile.yaml
Try login from main page: https://kubeflow.kubeflow.rizasaputra.com

Complete reference of my changes are on this commit: https://github.com/rizadiawan/kubeflow-manifests/commit/b2fb5d817640f8c96238909e51c6cb43306658d2
I've tried to also apply AWS Authservice like the Cognito deployment: kustomize build awsconfigs/common/aws-authservice/base | kubectl apply -f - but I still faced same problem.
Do I miss something?

Oh, I managed to get it works. Turns out the problem is because I mixed up instructions for doing vanilla deployment, manual LB deployment, and manual Cognito deployment. Later I'll try to open a PR for docs on authenticating with ALB + idP.
Thanks again for the guide :)

Awesome, this is great! Thanks for the POC
I will resolve the issue for now but feel free to open a new PR later


MWPW-151549: Modify blog playwright test for bacom

Modifies scripts created for opening docx and modifying on bacom-blog for use on bacom
Adds a step to utilize hlx sign in to ensure authentication

Resolves: MWPW-151549

Hi @JackySun9 and @Dli3 ,
I had to rebase, which is why there were some weird changes in the commits. Should all be good now. Please take another look! Thank you both for your help.


Guidebook content megaissue

This is a collection of various issues & tasks related to missing guidebook content or instances where guidebooks should get used but currently aren't. For missing guidebook functionality or bugs see #17163
Missing Guides

[x] Tesla needs a guidebook #23112
[ ] All antagonist roles should have a guidebook. Related to #28614

[x] #22918

[ ] Ghost role prototypes should have guidebook entries.
[ ] Combat needs a guidebook (#17530)
[ ] Job icons / huds need a guidebook (#18548)
[ ] All jobs should have a guidebook, in addition to the current department-level guidebooks. Related to #28614

[ ] Might need to add support for giving imbedded entities starting gear

[ ] Department guides should list associated jobs

Make more use of guidebooks

[ ] The rules window should probably be a guidebook #19763
[ ] The Ghost role UI should link to guidebooks. Related to #20192. Should work somewhat like #28614.
[ ] The character menu should probably use, link to, or be a guide entry of sorts.

[ ] Objectives should have guidebooks, or be some kind of guidebook control

I'd like to suggest the guidebook should do links better, like when you click a GuideEntityEmbed it should take you to that entity's guidebook page if it exists.
For instance, The Network Configurator has its own book page, so when I click the embed on the Engineering page it should take me to info about the network configurator

The rules window should probably be a guidebook

this one is definitely done

The 'food recipes' guidebook entry doesn't include '5u milk' as an ingredient in cake batter.
I'm not sure if this is the right place to report typos and information errors in currently existing entries (it does say 'megaissue', so it seems reasonable)

The 'food recipes' guidebook entry doesn't include '5u milk' as an ingredient in cake batter.
I'm not sure if this is the right place to report typos and information errors in currently existing entries (it does say 'megaissue', so it seems reasonable)

food recipes should use guidebook generator in the same way as reagents

Maybe an issue for new players: Leviathan doesn't show the Guidebook on start. It shows the rules instead.


Check properties - for iOS9 compatibilty

Check if properties exist for iOS 9 compatibility

<engine name="apple-ios" version=">=10.0.0" /> in the plugin.xml.
It means ios9 is not supported.


Clovis string is showing in CORE Architecture document.

Clovis string is showing in CORTX CORE Arch document.
Mero string is showing in Images.
I believe, we have to replace clovis with Motr.
https://github.com/Seagate/cortx/blob/main/doc/be/CORTX_CORE_ARCHITECTURE.rst

This is fixed by https://github.com/Seagate/cortx/pull/486


Mergeback/2.3.0

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

Project coverage is 100.00%. Comparing base (cc66e90) to head (8abdbb3).
Report is 4 commits behind head on develop.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##           develop       #48   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          117       116    -1
=========================================
- Hits           117       116    -1

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


Could not resolve all dependencies for configuration ':react-native-vector-icons:classpath'.

--- Delete everything above this line ---
Description
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApk'.
A problem occurred configuring project ':react-native-vector-icons'.
Could not resolve all dependencies for configuration ':react-native-vector-icons:classpath'.
Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
Required by:
ReactNativeSeed:react-native-vector-icons:unspecified

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 11.221 secs
Explain what you did, what you expected to happen, and what actually happens.
How to repeat issue and example
It causes while running react-native run-android
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApk'.
A problem occurred configuring project ':react-native-vector-icons'.
Could not resolve all dependencies for configuration ':react-native-vector-icons:classpath'.
Could not find any matches for com.android.tools.build:gradle:2.3.+ as no versions of com.android.tools.build:gradle are available.
Searched in the following locations:
https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
https://jcenter.bintray.com/com/android/tools/build/gradle/
Required by:
ReactNativeSeed:react-native-vector-icons:unspecified

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Your explanation here and source code or link
Solution
What needs to be done to address this issue? Ideally, provide a pull request with a fix.

Running into a similar situation, but specifically for react-native-image-picker.
Incremental java compilation is an incubating feature.

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugApk'.
   > A problem occurred configuring project ':react-native-image-picker'.
      > Could not resolve all dependencies for configuration ':react-native-image-picker:classpath'.
         > Could not find any matches for com.android.tools.build:gradle:2.2.+ as no versions of com.android.tools.build:gradle are available.
           Searched in the following locations:
               https://jcenter.bintray.com/com/android/tools/build/gradle/maven-metadata.xml
               https://jcenter.bintray.com/com/android/tools/build/gradle/

Solved it by adding to the bottom of android/build.gradle
subprojects {
    if (project.name.contains('react-native-image-picker')) {
        buildscript {
            repositories {
                jcenter()
                maven { url "https://dl.bintray.com/android/android-tools/" }
            }
        }
    }

    if (project.name.contains('react-native-vector-icons')) {
        buildscript {
            repositories {
                jcenter()
                maven { url "https://dl.bintray.com/android/android-tools/" }
            }
        }
    }
}

Thanks @rgpass for the fix. Could also combine this two libs together.
subprojects {
    if (project.name.contains("react-native-image-picker") || project.name.contains("react-native-vector-icons")) {
        buildscript {
            repositories {
                jcenter()
                maven {url "https://dl.bintray.com/android/android-tools/"}
            }
        }
    }
}

react-native-vector-icons is just update to the newest version ˆ6.1.0
https://github.com/oblador/react-native-vector-icons/releases
Waiting for the next release and bugfix of react-native-image-picker


ARTEMIS-1526 NullpointerException in ActiveMQServerControl.listConsumers()

race condition between listConsumers() and client closing a Session . Avoid NullPointerException and return empty strings for JSON attributes associated with that Session.

seems there were changed introduced yesterday -  I will need to pick these up retest & push again.

@pgfox you need to rebase this...


Unreachable code in transpiled JS

TypeScript Version:  2.1.5 / Current Playground Version
Code
TS Playground Link: https://goo.gl/u9Ar8w
enum Some { Enum = 1 }
class OtherClass { }

class DeclareAfterReturn extends OtherClass {

    constructor() {
        super();
        console.log(this.map[Some.Enum]);
    }

    map = {
        [Some.Enum]: {
            name: 'something'
        }
    };
}

Expected behavior:
No unreachable code
Actual behavior:
Unreachable variable declaration on line 26 in the Playground link above (the var _a after then return).  JSHint doesn't like this.  This changed somewhere between 2.0 and 2.1.5.

The declaration var _a is not a statement. it is a declaration. all declarations are hoisted to the top of their scope in JS. the tool that is reporting this error to you needs to be updated to be inline with the JS semantics, I suggest filing a bug there.

Duplicate of https://github.com/Microsoft/TypeScript/issues/13592


dotnet test should verify that testhost.exe and testhost.dll are the correct artifacts

Description
Today, I created a project called TestHost and put some tests in it. The idea is to write some arbitrary tests that a different test project would use in conjunction with dotnet test to test the output from a test logger that I'm writing. (example at https://github.com:fluffynuts/break-dotnet-test), but one can literally do dotnet new nunit -n TestHost.
However, I literally just spent the last hour or more trying to figure out why dotnet test in this folder produces:
  Determining projects to restore...
  Restored C:\tmp\TestHost\TestHost.csproj (in 160 ms).
  TestHost -> C:\tmp\TestHost\bin\Debug\net6.0\TestHost.dll
Test run for C:\tmp\TestHost\bin\Debug\net6.0\TestHost.dll (.NETCoreApp,Version=v6.0)
Microsoft (R) Test Execution Command Line Tool Version 17.2.0 (x64)
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Testhost process exited with error: . Please check the diagnostic logs for more information.

Test Run Aborted.

especially after enabling all diagnostic reporting (--verbosity:diagnostic --diag:test.log) and finding no error - in fact, test.log contains lines about how testhost.exe exited with code 0 and no error.
On a lark, I thought that perhaps the name was a problem, and found that renaming the .csproj (which changes the output file name - so I guess specifically setting an output binary path would have also worked) causes tests to run as expected.
Configuration

Which version of .NET is the code running on? net6.0
What OS and version, and for Linux, what distro? Windows 11 21H2
What is the architecture (x64, x86, ARM, ARM64)? x64
Do you know whether it is specific to that configuration? I'm guessing it's not 😅

Regression?
I imagine I'm probably the first unfortunate soul to have stumbled across this. I'd be surprised if it wasn't always this way.
Other information
since dotnet test is bringing in the testhost artifacts, I'm assuming it does so before building, and the build is simply wiping them out. So it would be a good idea to either:

verify that the testhost files haven't been changed before starting, or, simpler
clean before building & attempt to copy after building, and fail if those artifacts are already found

cc @nohwnd (there is no area-vstest label).

التحقق من وجود ملفات الاختبار وكذلك  التنظيف قبل عملية البناء

Thanks for the tag. Moved your issue here: https://github.com/microsoft/vstest/issues/3918

apologies, I wasn't quite sure where to raise the issue (:

@fluffynuts No apology needed. :)


EVS - Add Configuration To Output Events Upon Command Message vs. Function Call (GSFC DCR 22080)

The GSFC MMS FSW team ran into a problem when several events were being output by high priority tasks.
A recommended solution to this problem is to create a configuration for EVS to send a specified number of events at a specified periodic rate. Adding additional event filtering capabilities should to address this issue should also be looked into.

Imported from trac issue 97.  Created by sstrege on 2015-08-27T15:15:45, last modified: 2019-04-03T18:01:02

Trac comment by glimes on 2016-10-18 15:07:03:
Remove my name from many tickets (where it was applied by default), so others can tell that there are tickets that need some attention.

Trac comment by jhageman on 2019-04-01 12:33:48:
CCB - review path forward, recommend projects resolve their issues rather than complicating cFE

Trac comment by jhageman on 2019-04-03 18:01:02:
CCB 4/3/19 Discussion

Multiple solutions to this issue are available without complicating the community code base
Could have filtered offending issues, fixed the cause of the event, etc

Closing this ticket as wontfix, and added requirement enhancement ticket #305 to consider trade of complicating design.


Added a set of tests for 16x8.

This PR is an addition to the PR:
https://github.com/tensorflow/tensorflow/pull/36251
The command that I used to run them:
bazel run  //tensorflow/lite/testing:generate_examples -- /tmp --zip_to_output=conv_relu --toco=$(pwd)/bazel-bin/tensorflow/lite/toco/toco --jobs 48
This PR adds op_tests for the operators that are implemented for the quantization mode:
activations - int16, weights -int8.

fyi, the zip test starts to use the new mlir converter now.

@wwwind Can you please check @liufengdb's comments and keep us posted. Thanks!

This PR will be merged as a follow-up of this PR https://github.com/tensorflow/tensorflow/pull/36251

Hi @suharshs Could you please re-approve this PR ? I had to push a fix after CI checks.
Thanks!

Hi @suharshs I pushed a fix. Thanks!

Hi @rthadur I see that all checks are green now, could we please merge this PR ?
Is there something blocking it ? Thanks!

For some reason this test is not building and running properly internally. I am resolving the issues, and also trying to figure out why its not run in OSS TF.
I will try to resolve it to get the missing 16bit tflite testing infra submitted, and update with the details here.

Ok so I just got this PR merged with some additions to the testing infra.
In order to get the PR through i had to remove the leaky relu test and the conv with activation test. Could you add those tests in separate small PRs so that we can narrow down those failures and get those in as well.
Thanks!

Hi @suharshs Thank you! I will do.


Update request: souper -> latest (using LLVM 4.0)

Issue description
souper was recently updated to use LLVM 4.0, which is rather good news for my use cases.  Can we update our version to use this?
It also seems they now more strongly prefer their own KLEE fork so perhaps we should switch to using that as well?
@taktoa (maintainer)--LMK your thoughts and if you want to tackle it or want me to (I'd probably get to it this weekend).
Thanks!

I'm pretty busy these days but if you're interested in updating it feel free :+1:

Sure thing!
Although actually we'll need to actually add LLVM 4.0 first, forgot that wasn't in-tree yet :innocent:.
Maybe I'll give that a go as well :+1:
(cc #22630)


adding prometheus metrics server

Does not include any SFU stats yet, but includes the prometheus metrics server launching with the sfu node.

I originally added counters to the publish() and subscribe() etc stream control methods, but we should actually get these for free when we add go-grpc-prometheus

I am working to add some GetStats() exposure, but (I'm not an expert, I might be wrong) -- I didn't like how GetStats always returns an increasing number for most metrics; they typically are more interesting as instantaneous values -- this is taking me some time to implement as I am a golang novice, and I think it's best if I commit this simple branch now so we can begin to use metrics

For simplicity, I don't think we should introduce prometheus in this repo. ion reimplements cmd in at https://github.com/pion/ion/pull/309/files#diff-5b63bcde9120c2b022b48409414a664bR67 so perhaps it makes more sense there (once we merge the migration). We can add some generalized stats endpoints here, but how they are aggregated/displayed should be up to the consumer

I understand the instinct to maintain simplicity, and at first glance, I recognize that this seems to add little extra functionality beyond just consuming a TCP port.  My original goal was to include in this PR figures from PeerConnection.GetStats API, specifically metrics for bandwidth consumption (per connection, tagged with metadata) and UDP ports (one of our tightest resources, until the proposed PC changes are implemented). This needs to run by iterating all the PCs and accumulating the stats, which can only execute on the SFU.
I haven't finished my new CountRouterMetrics method yet, but in my feature/prometheus-advanced branch we count all the metrics in the rtc/webrtctransport.go file (by adding a CountMetrics(cycleSeconds int) method to the Transport interface). Just adding the server line in cmd on the ion repo will not suffice to expose these stats (and I also have a really hard time with the idea of having 2 "builds" of SFU, one from ion that includes metrics in the build and one from ion-sfu that does not, honestly I'd sooner scrap telemetry entirely than suggest that).
Telemetry we can get without introspecting GetStats API is limited to "per-container" aggregations; I think it's common for a piece of core infrastructure like SFU to expose a metrics endpoint to enable operational graphs like "bytes per second, by codec" or of open UDP ports (a scarce resource that is not typically exposed by cAdvisor). With the new proposed UDP port changes, you could make the argument this becomes less operationally critical.
Ultimately, I think we'll come back and add it some day, but this is A-OK and I fully own that the utility of "just exposing it" without the extra metrics isn't useful here - If you don't care to expose at least the metrics from go-grpc-prometheus like you showed me last night (I thought you were excited about that :) ) then we don't need this!

i for sure want the prometheus logging! just think it belongs in ion rather than here. since ion already reimplements cmd for sfu (to support service discovery). lets work on exposing the GetStats api. I'm happy to help with implementation


fix/improve get_number function

The while loop in the get_number function will be safer if checking for legal symbols in a variable name instead checking for a subset of illegal ones. For example, a closing bracket following a variable name, e.g., (a+b) would be regarded as part of the variable name.
https://github.com/IAEA-NDS/exfor-parserpy/blob/main/exfor_parserpy/utils/arithmetic_expr_parsing.py#L20

The functions in arithmetic_expr_parsing.py were rewritten from scratch, which should also solve this issue.


proposal: x/crypto: Not all parameters of the argon 2 specification are included in spec

The current interfaces are:
func IDKey(password, salt []byte, time, memory uint32, threads uint8, keyLen uint32) []byte
func Key(password, salt []byte, time, memory uint32, threads uint8, keyLen uint32) []byte
Parameters "Secret" and "Associated data" mentioned in the spec https://github.com/P-H-C/phc-winner-argon2/blob/master/argon2-specs.pdf are not listed in the above definition.
Parameter secret is meant for creating application specific hashes.
Parameter "Associated data" is meant for a hash calculated on session specific data. A password and salt should for some use cases return different hashes based on agreed session specific data: A date value (new keys each day?); user data; direction data; protocol data; classifications data; filenames, and whatever both ends of the session agree on.
How do we get those important parameters included?

Duplicate of #35481


Item Count doesn't update in offhand

If you have an incomplete stack of blocks in your offhand, then break some blocks and pick them up, the blocks do stack to your offhand, but the number doesn't update in your hotbar to reflect that.

Issue seems to be fixed in dev. Thank you!


Upgrade to MDC 0.21.0

Essentially take care of all breaking changes introduced since 0.19.0
Note that there are no breaking changes in 0.20.0 that affects react-mdc-web.

Remove the primary and accent properties on Button, since MDC
has removed that concept. Also removed all usages of primary
from the demo pages. Also update main.css to default raised button
color to match the demo's primary color.
Remove the plain property from Fab, since MDC has removed that concept.
Updated the snackbar demo to accommodate changes in button colors.

Note that after this, I am planning on upgrading to mdc-0.22, which has a few breaking changes.

Great, thank you


Why there are samples_with_missing_skeletons

I felt a little confused about the samples with missing skeletons. I tried to understand how you selected those samples like:

samples of all zeros (165 samples)
samples where some frames have no skeleton data (additional 65)

But I didn't manage to figure out how you ignore 302 samples in total. I was wondering if you could give some explanation about those ignored sample. Thank you :)

Which dataset are you talking about?

Sorry for the ambiguity. It's about NTU-RGB+D dataset.


Cant find check in button on source control explorer on Mac

Hi,  have successfully connected to my project on VSTS, created a workspace, mapped and downloaded the solutions, run the solution on the Mac, no problem on that.
But I can't seen to find a way to checkin my code updates, the way I`m used to do on VS for Windows.
I did find an option when you right click a single file on the source control explorer, to checkin that file, but where is all my changes located, and how do I checkin all modified files at once?

@jmatthiesen can you comment on this?

Hello! When using the TFVC extension your easiest way to check-in a file is to open a project in TFVC that uses that project, then you can use the Version Control menu to review changes and commit. Otherwise, the source control explorer doesn’t have an option for Check-in.


When first loading a directory with adv3Lite stored in source tree, the src/ dir is filled with .t3s and .t3o

Describe the bug
I've included adv3Lite in my project directory rather than using the standard location in /usr.  (I have my reasons.)  When I installed the extension and reloaded the project, my src/ directory filled with adv3Lite object and symbol files, and the final game file as well (.t3).
Note that my .t3m has options to store all object and symbol files in an obj/ directory, and writes the final .t3 to the root of the project.  (This is a hand-crafted make file, not one generated by any tools or templates.)
To Reproduce
The pertinent directories are:

adv3Lite/ - contains all the advLite .t, .h, and.tl
src/ - my game source code
obj/ - built by t3make

My .t3m:
-D LANGUAGE=english
-D MESSAGESTYLE=neu
-D INSTRUCTIONS_MENU
-lib system
-lib adv3Lite/adv3Lite
-source src/game.t

My t3make command line:
t3make -d  -we -FC -cs UTF-8 -Fy obj -Fo obj -f game.t3m -o game.t3

Log
Regarding the log: Because I was worried this was going to happen every time I opened VS Code, I deleted the .t3o and .t3s files and used VS Code's "Reload Developer Window" option.  Unfortunately, I lost the original log because of this.
Expected behavior
I would prefer it write the symbol and object files to the directory specified in my .t3m.  (I believe they already existed there when I started the extension, from a prior build.)
Desktop (please complete the following information):
Ubuntu Linux (Bionic).  VS Code 1.60.0.

Ok, I need to simplify the above.  I've removed adv3Lite from my project tree, restarted VS Code, and I'm still seeing the above behavior.

I see. Have you tried setting the -Fy obj flag in the makefile as well, if it is not specified I believe this behaviour is by design of how t3make works.

And the extension uses the makefile to produce preprocessed text, otherwise it won’t work. I need to consider what should happen in a case like this though... e.g warning or separate directory for the preprocessing to use...
Thanks for the report by the way!

Yes, that did it.  I've tried adding various options to the .t3m in the past and t3make complained.  I realized just now that the order of the options is important.  When I moved -Fy and -Fo up towards the beginning of the file, it all worked and everything clicked into place.
I'll let you decide if you want to close this ticket, or what further work is needed, if any.  I'm satisfied.
Thanks for the great tool!


Does not write..

I tried to do a simple example:
def write() do
client = CQEx.Client.new!
base = Q.new
|> Q.statement("INSERT INTO mydb.locations (user_id, date, unix_time, lat, long) values (?, ?, ?, ?, ?);")
|> Q.put(:user_id, 0)
|> Q.put(:date, '2016-5-12')
|> Q.put(:unix_time,<PHONE_NUMBER>)
|> Q.put(:lat, 3.23)
|> Q.put(:long, 3.4321)
end
but, nothing was written, is there anything I am missing?

sorry, I forgot to call Q.call!(client, base);


ninja: build stopped: subcommand failed.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/laekov/fastmoe.git
cd fastmoe
git checkout 4edeccd95a66d1f2d5eb7ec7a9e40a9f67e0e393
psudo() { sudo env PATH="$PATH" "$@"; }
psudo python setup.py install
Logs
FAILED: /home/protago/hanxue/fastmoe/build/temp.linux-x86_64-3.6/cuda/fmoe_cuda.o
c++ -MMD -MF /home/protago/hanxue/fastmoe/build/temp.linux-x86_64-3.6/cuda/fmoe_cuda.o.d -pthread -B /home/protago/miniconda3/envs/moe/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include -I/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/torch/csrc/api/include -I/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/TH -I/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/THC -I/usr/local/cuda-11.1/include -I/home/protago/miniconda3/envs/moe/include/python3.6m -c -c /home/protago/hanxue/fastmoe/cuda/fmoe_cuda.cpp -o /home/protago/hanxue/fastmoe/build/temp.linux-x86_64-3.6/cuda/fmoe_cuda.o -DFMOE_USE_NCCL -DUSE_C10D_NCCL -DTORCH_API_INCLUDE_EXTENSION_H -DTORCH_API_INCLUDE_EXTENSION_H '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_COMPILER_TYPE="_gcc"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_STDLIB="_libstdcpp"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' '-DPYBIND11_BUILD_ABI="_cxxabi1011"' -DTORCH_EXTENSION_NAME=fmoe_cuda -DTORCH_EXTENSION_NAME=fmoe_cuda -D_GLIBCXX_USE_CXX11_ABI=0 -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
In file included from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/ATen/Parallel.h:140,
from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/utils.h:3,
from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/nn/cloneable.h:5,
from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/nn.h:3,
from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/torch/csrc/api/include/torch/all.h:13,
from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/torch/extension.h:4,
from /home/protago/hanxue/fastmoe/cuda/fmoe_cuda.cpp:3:
/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/ATen/ParallelOpenMP.h:83: warning: ignoring #pragma omp parallel [-Wunknown-pragmas]
83 | #pragma omp parallel for if ((end - begin) >= grain_size)
|
In file included from /home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/c10d/ProcessGroupNCCL.hpp:10,
from /home/protago/hanxue/fastmoe/cuda/fmoe_cuda.cpp:7:
/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/include/c10d/NCCLUtils.hpp:9:10: fatal error: nccl.h: No such file or directory
9 | #include <nccl.h>
|          ^~~~~~~~
compilation terminated.
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1673, in _run_ninja_build
env=env)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/subprocess.py", line 438, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "setup.py", line 67, in
'build_ext': BuildExtension
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/init.py", line 153, in setup
return distutils.core.setup(**attrs)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/core.py", line 148, in setup
dist.run_commands()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/dist.py", line 955, in run_commands
self.run_command(cmd)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/install.py", line 67, in run
self.do_egg_install()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/install.py", line 109, in do_egg_install
self.run_command('bdist_egg')
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 164, in run
cmd = self.call_command('install_lib', warn_dir=0)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/bdist_egg.py", line 150, in call_command
self.run_command(cmdname)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/install_lib.py", line 11, in run
self.build()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/command/install_lib.py", line 107, in build
self.run_command('build_ext')
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/dist.py", line 974, in run_command
cmd_obj.run()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 79, in run
_build_ext.run(self)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/command/build_ext.py", line 339, in run
self.build_extensions()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 708, in build_extensions
build_ext.build_extensions(self)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/command/build_ext.py", line 448, in build_extensions
self._build_extensions_serial()
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/command/build_ext.py", line 473, in _build_extensions_serial
self.build_extension(ext)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/setuptools/command/build_ext.py", line 202, in build_extension
_build_ext.build_extension(self, ext)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/distutils/command/build_ext.py", line 533, in build_extension
depends=ext.depends)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 538, in unix_wrap_ninja_compile
with_cuda=with_cuda)
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1359, in _write_ninja_file_and_compile_objects
error_prefix='Error compiling objects for extension')
File "/home/protago/miniconda3/envs/moe/lib/python3.6/site-packages/torch/utils/cpp_extension.py", line 1683, in _run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error compiling objects for extension
Platform

Device: [NVIDIA Driver Version: 470.103.01]
CUDA version: [11.1]
NCCL version: [2.7.8]
PyTorch version: [1.8.0]

Even though I try psudo USE_NCCL=1 python setup.py install
still meet the same error

I solved the problem via install nccl again following here:
https://docs.nvidia.com/deeplearning/nccl/install-guide/index.html


add inline sourcemap support, it's useful to angular 2

postcss-loader?sourceMap=inline will output css and it's inline sourcemap. It's useful to angular 2's component styles.

Great work, thanks

I renames it to 3305c74 and add docs. Is it OK?

Ok!
please publish a new version as soon as possible ^_^

https://github.com/angular/angular/pull/10724
I've submitted a PR to angular team too, I hope angular will have perfect supporting for source map when it's released.

Sure, I will release it today (not at laptop right now, sorry)

Released in 0.10

@asnowwolf Can you please give a short explanation and example why you need inline sourcemaps for angular 😛 ? Is this still relevant from your side ?


[Turnstile] Add idempotency key documentation for Turnstile

We have recently introduced a support for idempotent POST requests for Turnstile's Siteverify. This PR adds documentation which would inform customers how to make use of this functionality.

would you mind also adding a note to the turnstile changelog?


JSon conversion fix

Fixed an issue where Media's MeanScore can be null which causes a retrieval to fail.
Sorry, there is no test for this one. If you want to check you can use [https://anilist.co/anime/107717/Kobayashisan-Chi-no-Maidragon-S/](Kobayashi-san Chi no Maidragon S), but cannot add as a test as once it gets a mean score the test will fail.

but cannot add as a test as once it gets a mean score the test will fail

The whole point of a test is to show when things aren't working right though?

Anyway thanks yeah :)


double-beep: Watch +1-888-885-7555

double-beep requests the watch of the watch_number +1-888-885-7555. See the MS search here and the Stack Exchange search here.

Approved by Makyen in Charcoal HQ


HC Cost Page Layouts and Record Type update

HC Cost object
Page layouts and Record Types

Reason for closing: When compared the Master Data sheet with the PR, I noticed extra fields on the layout.
Action: Please update the layouts based on the Master Data sheet and create a new feature branch with a different version.


fix response for get_queue_by_name on non existing queue

Fix problem where get_queue_by_name with non existing queue did not raise an AWS.SimpleQueueService.NonExistentQueue error but returned 404 only.

With this I can mock code like this
        try:
            queue = self.sqs_res.get_queue_by_name(QueueName=queueName)
        except ClientError as e:
            logger.warning("SQS Queue: %s doesn't exist, creating it.", queueName)
            if e.response['Error']['Code'] == 'AWS.SimpleQueueService.NonExistentQueue':
                queue = self.sqs_res.create_queue(QueueName=queueName)

Travis seems to indicate that the exception is not being raised.

@haad I'm closing this PR due to its age. Please reopen when you get a chance.


Added Dviih

I don't think that is required xd i just collaborated because i wanted to also Github already have the contributors tab

We don't have control over who counts as a contributor on GitHub and this PR wouldn't change anything.


Other strategies for scroll rig

Thank you for this example, it's really interesting to see this methodology.
In the article you mention there's lots of ways to build the decorative scroll rig. However, I'm struggling to come up with a way that decouples the content section heights from the screen height, so that sections can be driven by the amount of content within it and therefore removing the large gaps between sections, and creating uniform gaps between sections with different amounts of content within them.
Is there a method for achieving this? It seems challenging to do this as the position of a section would depend on the heights of preceding sections...

Hey Alex did you ever figure this out? Ive been experimenting as well but trying to use drei exclusively has run into some problems particularly with offset


Updated Setup.py to remove Pasteurize

Remove the following logic as Python 2 is being retired globally starting in 2020
from setuptools.command.build_py import build_py
:
:
class PasteurizeBuildCommand(build_py):
def run(self):
call(["pip", "install", "future"])
call(["pasteurize", "./pyramda"])
build_py.run(self)
:
:
cmdclass={
'build_py': PasteurizeBuildCommand
},

Coverage remained the same at 95.169% when pulling f5b4585cc21a7f8d8101691b6bc07e74b08dce20 on vgangaprasad:master into 85ab1c2f456085c9e31e3831459ee1a850ab559c on jackfirth:master.

For the Travis CI issues, I think dropping 3.3 from the CI config is the right way to go. Could you also add the newer versions? I think we want every version on this list except for 2.7.

Also, thank you so much for this pull request! It's something that's been bothering me for literal years.

CI is passing, so looks good to me 👍 Merging!