Convert patient address information

Describe the bug
Add capability to find and convert the following patient address information

Patient.address / PID-11
Patient.address.district / PID-12. (Also known as Country code)

This was broken off from work item #94
To Reproduce
Create a sample HL7V2.6 patient PID segment with aforementioned patient information.
Expected behavior
Patient information should be detected and added to corresponding fields in HL7 FHIR resources.
Examples:
Patient Address:  This should handle a complete Extended Address XAD content  (should allow for multiple)
{
  "resourceType": "Patient",
  "id": "address",
  "address": [
    {
      "use": "home",
      "type": "both",
      "text": "534 Erewhon St PeasantVille, Rainbow, Vic  3999",
      "line": [
        "534 Erewhon St"
      ],
      "city": "PleasantVille",
      "district": "Rainbow",    <<< comes from PID.12
      "state": "Vic",
      "postalCode": "3999",
      "period": {
        "start": "1974-12-25"
      }
    }
  ],

District / Country code
From HL7V2.6, it is four characters of local definition.
Inserted into .address as shown above
Screenshots
N/A
Desktop (please complete the following information):

OS:  Mac OS
Version Big Sur

Additional context
Use and Type Mappings
V2.6 Address and FHIR Address do not have clean 1:1 mappings for Type -> Use / Type.  This is the design for meaningful mappings.
V2.6 Address is an XAD data type.  https://hl7-definition.caristix.com/v2/HL7v2.6/DataTypes/XAD XAD is used for both Patients and Organizations, so we want to use the same mapping.
XAD has multiple special fields to get information from:

XAD.7 has a list of address types https://hl7-definition.caristix.com/v2/HL7v2.6/Tables/0190
XAD.16 - Temporary Indicator	(v2.6)
XAD.17 - Bad Address Indicator (v2.6)
XAD.18 - Address Usage (v2.6)

FHIR org has an V2 to FHIR mapping for address, but it does not account for the new fields (XAD.16/17/18) added in v2.6
FHIR Address reference: https://www.hl7.org/fhir/datatypes.html#Address
"use" and "type" are OPTIONAL, but are not extendable.

FHIR Use Code
Display
Definition

home
Home
A communication address at a home.

work
Work
An office address. First choice for business related contacts during business hours.

temp
Temporary
A temporary address. The period can provide more detailed information.

old
Old / Incorrect
This address is no longer in use (or was never correct but retained for records).

billing
Billing
An address to be used to send bills, invoices, receipts etc.

FHIR Type Code
Display
Definition

postal
Postal
Mailing addresses - PO Boxes and care-of addresses.

physical
Physical
A physical address that can be visited.

both
Postal & Physical
An address that is both physical and postal.

XAD Mapping Summary for FHIR Type
FHIR Type Code is mapped from XAD.18 table 0617
If XAD.18 is not present, but XAD.7 is "M" or "SH", XAD.7 will be used.  If no conditions are satisfied, Type will remain empty.

XAD Type Code
Definition
FHIR Type

XAD.18 "M" : Mailing
Identifies an address for mail correspondence from a healthcare provider as stipulated by the subject. For example, under the tenets of certain privacy regulations, it is exclusive to the patient and is typically maintained at the encounter or visit level versus the person level as it only has relevance to the specifics of a given encounter.  This is an exception category of address in that the patient has stipulated that they want all correspondence relevant to a given encounter sent to this address in lieu of any other address on file.  Providers are required to accommodate such requests under HIPAA promulgated regulation.  Note that mailing and legal address may be mutually exclusive as defined below.
"postal"

XAD.18 "V": Visit
Identifies an address at which the individual is physically located and may be visited.
"physical"

XAD.7 "M" : Mailing
Retained for backward compatibility only as of v2.6. Refer to XAD.18, which takes priority.
"postal"

XAD.7 "SH" : Shipping Address
XAD.18 value takes priority.
"physical"

XAD.18 "C" : Classification
Identifies an address used for the purpose of demographic classification or searching.  Such addresses frequently contain insufficient information to be used as mailing or visit addresses.  For example, they may only indicate country and postal code, without providing a street address.
Not supported

XAD Mapping Summary for FHIR Use

XAD Field, Code & Value
XAD Description
FHIR Use

XAD.16 (Temp) "Y"
Temporary indicator
"temp"

XAD.17 (Bad) "Y"
Bad address
"old"

XAD.7 "B" : Firm/Business
Refers to an address specific to an organization, such as an insurance company or employer, versus an individual’s work location or place of employment. It would be specific to a firm or organization that has some sort of business relationship with the subject
"work"

XAD.7 "BA" : Bad address
Retained for backward compatibility only as of v2.6. Refer to XAD.17
"old"

XAD.7 "BDL" : Birth delivery location (address where birth occurred)
Refers to the address where birth occurred.
Not supported

XAD.7 "BI" : Billing Address
May also be used for the validation/authorization of credit cards
"billing"

XAD.7 "BR" : Residence at birth (home address at time of birth)
Refers to the home address at time of birth.
Not supported

XAD.7 "C" : Current Or Temporary
Retained for backward compatibility only as of v2.6. Refer to XAD.16.  XAD.16 (Y/N) takes priority.
If XAD.16 is empty and XAD.7=="C" then "temp"

XAD.7 "F" : Country Of Origin

Not supported

XAD.7 "H" : Home
Refers to a residence or domicile, literally the place where the subject resides the majority of the time. Generally speaking most people will have a home address and it will represent their primary address. Home address is mutually exclusive of permanent address.
"home"

XAD.7 "L" : Legal Address
Refers to a special case address specific to the status of a subject or legal action involving the subject. For example, prisoners being treated at a healthcare facility, etc.
Not supported

XAD.7 "M" : Mailing
Retained for backward compatibility only as of v2.6. Refer to XAD.18
not a use; this is a Type.  See Type mapping table

XAD.7 "N" : Birth (nee) (birth address, not otherwise specified)
Refers to the birth address, not otherwise specified
Not supported

XAD.7 "O" : Office/Business
Refers to a work address specific to the subject.
"work"

XAD.7 "P" : Permanent
Refers to a place where the residents know the subject and where correspondence addressed to the subject will eventually reach the subject regardless of their physical location. A permanent address generally reflects a tax jurisdiction.  Members of the military, flight attendants, and executives on rotational assignments are examples of those who typically maintain a permanent address. Although mutually exclusive of home address, in some instances, such as the executives mentioned above, it may be synonymous.  In such cases upon return from assignment this address would revert to the home address.
Not supported

XAD.7 "RH" : Registry home.
Refers to the information system, typically managed by a public health agency that stores patient information such as immunization histories or cancer data, regardless of where the patient obtains services
Not supported

XAD.7 "S" : Service Location
Refers to the location in which service is rendered. This would be used if reimbursement is based on the location of the service (to take into account the cost of those services).
Not supported

XAD.7 "SH" : Shipping Address

not a use; this is a Type.  See Type mapping table

XAD.7 "V" : Vacation

Not supported

XAD Address Mapping for FHIR Period

XAD Field
Description
FHIR field . subfield

XAD.12
Address Validity Range
Address.period

XAD.13
Effective Date
Address.period.start

XAD.14
Expiration Date
Address.period.end

In Release 1.0.8


Fix incorrect construction of magic command azure.quotas

Quotas command was constructed using an incorrect name.
Updating to the intended name.

It looks like the API documentation comment at L17 may also be good to update, but otherwise LGTM.

Thanks for the catch, @cgranade . To avoid delaying the pending PR we have tonight, I'll leave as is, but I'll correct the comment in the next few days.

It looks like the API documentation comment at L17 may also be good to update, but otherwise LGTM.

Thanks for the catch, @cgranade . To avoid delaying the pending PR we have tonight, I'll leave as is, but I'll correct the comment in the next few days.

/azp run

/azp run

Force merging to restore build.

Force merging to restore build.


Emmet Abbrevation html:5 for pug doesn't produce doctype shortcut

I don't know if this is the right repo,
but when I open a pug-file and use html:5 emmet,
it produces <!DOCTYPE html> in the first line instead of using the pug's doctype shortcut

html:5 does the same expansion on emmet.io. You should open an upstream issue at https://github.com/emmetio/emmet.


Support TRACE methods in router_check tool

Currently, the router_check tool only supports GET, PUT, and POST methods according to the documentation https://www.envoyproxy.io/docs/envoy/latest/configuration/operations/tools/router_check (in the method section).
I am looking to create some tests that ensure envoy denies TRACE methods for my route, but can't do so because of this limitation. Would it be a difficult problem to support all methods (or at least TRACE) in the router_check tool?
Description:

Describe the desired behavior, what scenario it enables and how it
would be used.

[optional Relevant Links:]

Any extra documentation required to understand the issue.

I tested with router_check tool with config as below:
route config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                  headers:
                    - name: ":method"
                      string_match:
                        exact: "TRACE"
                        ignore_case: true
                route:
                  cluster: my_cluster

The test is
tests:
- test_name: Cluster_name_test
  input:
    authority: <IP_ADDRESS>:13333
    path: /
    method: TRACE
  validate:
    cluster_name: my_cluster

It seems the TRACE method works.
bazel-bin/test/tools/router_check/router_check_tool --config-path ./config.yaml -t ./test.yaml -d
Cluster_name_test
Current route coverage: 100%

It should be the doc issue.

Confirmed that I can also use TRACE. I'll leave this issue open so that the docs can be fixed.


CollisionPolygon2D Issues

Windows 7 Godot 2.1/2.2
CollisionPolygon2D/set_polygon() does nothing
Steps to reproduce:
1-Get the polygon:
col = get_polygon()
2-Change the CollisionPolygon2D's shapes :
col[1].y=-80
3- set the polygon:
set_polygon(col)
Link to minimal example project (optional but very welcome):
https://drive.google.com/open?id=0B3mjAjcuXnKqVjFPanUycHhiaXc

when you turn on visible collision shapes, you can see the changed polygon, but the collision detect the old polyong instead the new one
http://gph.is/2iqruwX

I can reproduce this using AnimationPlayer

@0nepixel  @williamd1k0  Its not bug. 2Dpolygon help create collision shape, but it not shape itself. You should use this...

thanks

@0nepixel you won't see the new shape in "debug" unless you add it to a collisionshape/polygon (confusing, I know) or draw it yourself (with _draw)

you don't see the problem xD, the shape changes in the collision only

@0nepixel  Here, but after download close this Issue, because its not forum :З
https://cloud.mail.ru/public/Jip6/NgBAwYVWY

You are using the animationplayer in fixed mode, right?

@sezit thanks bro :) :+1:

@bojidar-bg I tested AnimationPlayer using idle and fixed mode (same result).

I'm pretty sure this is by design. The "visible collision shapes" I believe only show the shapes made in the editor, not the shapes inside of the CollisionObject2D's. So, if you update the shape in CollisionObject2D the collisions you'll see won't match up unless you update the CollisionPolygon2D which is basically only useful as an editor class.
Again, don't think this is a bug, this is just by design.

This seems to be related to #4260

This is indeed the normal behaviour. It might be made a bit more user-friendly in 3.0, but this is already tracked in various other issues so closing this one.


Clear image cache

Hi. If I change any photo and show this with glide, I see old image until manually delete cache file.
Here is issue https://github.com/thephpleague/glide/issues/7 about this, and method deleteCache now in library code.
I think, if You update a league/glide version in composer.json, and all will work out the box. Or, may be, such method already exists, and I do not know about this?
P.S. Thank You for great extension, and sorry my terrible English :)

Glad you like! And yes, this feature has been built and will be available as soon as I release version 1.0, which is really any day now
Lets wait for 1.0 release and i'll update version constraint

Ok, fine :)


Blob IAM support apparently invalid

While writing system tests for the requester_pays feature, I triggered the following:
Traceback (most recent call last):
  File "/home/tseaver/projects/agendaless/Google/src/google-cloud-python/storage/tests/system.py", line 372, in test_blob_acl_iam_w_user_project
    blob.set_iam_policy(policy)
  File "/home/tseaver/projects/agendaless/Google/src/google-cloud-python/storage/google/cloud/storage/blob.py", line 1148, in set_iam_policy
    _target_object=None)
  File "/home/tseaver/projects/agendaless/Google/src/google-cloud-python/storage/.nox/sys-3-6/lib/python3.6/site-packages/google/cloud/_http.py", line 293, in api_request
    raise exceptions.from_http_response(response)
google.api.core.exceptions.BadRequest: 400 PUT https://www.googleapis.com/storage/v1/b/new_1506705016579/o/SmallFile/iam?userProject=citric-celerity-697: roles/storage.objectViewer is not a valid role for projects/_/buckets/new_1506705016579/objects/SmallFile#0.

Note that the earlier call to Blob.get_iam_policy does succeed, returning:
(Pdb) pp policy.to_api_repr()
{'bindings': [{'members': ['projectEditor:some-project-742',
                           'projectOwner:some-project-742',
<EMAIL_ADDRESS>               'role': 'roles/storage.legacyObjectOwner'},
              {'members': ['projectViewer:some-project-742'],
               'role': 'roles/storage.legacyObjectReader'},
              {'members': ['allUsers'], 'role': 'roles/storage.objectViewer'}],
 'etag': 'CAM='}

We don't have existing system tests for Blob.set_iam_policy, but the Storage IAM docs don't define any IAM operations for blobs, only for buckets and projects.  Indeed, they say:

To learn about controlling access to individual objects in your buckets, see Access Control Lists.

The API documentation for Objects also doesn't (any longer?) show getIamPolicy, setIamPolicy, or testIamPermissions.
@lukesneeringer can you loop somebody in to clarify?

@frankyn confirmed to me offline:

There is no Object level IAM only Object Level ACL.

It turns out that Blob.set_iam_policy can only assign the following "legacy" roles:

roles/storage.legacyObjectReader
roles/storage.legacyObjectOwner

IAM object-level methods should not be deprecated. We should document how to use these methods to assign legacy roles instead.

@frankyn ISTM that the back-end docs need to be updated correspondingly (and first, so that we track them without guesswork).

Good point. I'm working on resolving this in Storage docs. I'll update this post.

@frankyn I still don't see API documentation for objects.getIamPermissions et. al.

Will update soon. I need to sync with a few stakeholders on the GCS team before continuing there exist additional open questions before introducing the docs back into the world. Setting up meeting for mid-next week given some are OOO. I will have a better update then. Thank you for patience.

Sent a document for GCS team review to determine consensus for what to do here.

@frankyn ping?

Hey @tseaver, responding through hangouts.


Ensure synthetic function names conform to naming requirements

Pull Request check-list
Please make sure to review and check all of these items:

[x] Does npm test pass with this change (including linting)?
[ ] Is the new or changed code fully tested?
[ ] Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.
Description of change
The "restore-asking" function name is not valid and was causing co-redis (by way of its usage of thenify) to throw because thenify uses the function name to rewrite async functions with promises.
This PR will change the name of the "restore-asking" function to "restore_asking", which is valid.
This sanitation is a bit stricter than necessary, since it also sanitizes valid unicode characters, but it covers this module's potential use cases just fine.

@danmactough Thanks a lot!

my pleasure 😸 @BridgeAR


Enable auto subtitles on the video depending on the website's language

When watching the video, the correct subtitles will be displayed according to the site's language

See #85


Update introduction.md

Add tutorial on recursion in JavaScript
This commit introduces a comprehensive tutorial on recursion in JavaScript. The tutorial provides easy-to-understand examples and explanations for beginners, covering the fundamental concepts of recursion, including base cases, recursive cases, and the pros and cons of using recursion.
The tutorial includes two illustrative examples: a countdown function and the calculation of the factorial of a number. Each example is accompanied by detailed explanations, making it accessible for those new to the concept of recursion.
The markdown file is well-formatted for clarity and readability, following the style of existing documentation in the repository.
Contributors:  Zynthatrix

Some changes please:

copy the contents of introduction.md into about.md
copy the contents of introduction.md into exercises/concept/pizza-order/.docs/introduction.md
markdown style: one sentence per line -- https://exercism.org/docs/building/markdown/markdown#h-layout


Run Error - swissprot database

Hi,
I'm trying to run zdb, but I get this error:
(zdb) moshea@shannon:/mnt/LargeStorageNoBackup/Datasets/Moshea/Databases/zdb$ zdb run --input=../zdb_table.csv
Starting the analysis pipeline
N E X T F L O W   ~  version 24.04.3
Launching /home/moshea/miniconda/envs/zdb/share/zdb-1.3.1/annotation_pipeline.nf [clever_lavoisier] DSL2 - revision: 067a6b5acf
wrong type for swissprot_db zdb_ref/uniprot/swissprot/
ERROR ~ assert(false)
-- Check script '/home/moshea/miniconda/envs/zdb/share/zdb-1.3.1/annotation_pipeline.nf' at line: 48 or see '.nextflow.log' file for more details
Could not finish the analysis
Try to rerun the same command with the --resume flag set to rerun the analysis
I haven't found any instruction as to where to run the tool or how to tell it where the databases are, is that the problem?

Yes, I ran zdb setup:
(zdb) moshea@shannon:/mnt/LargeStorageNoBackup/Datasets/Moshea/Databases/zdb/uniprot/swissprot$ ls -lht
total 580M
-rw-rw-r-- 1 moshea moshea 106M Jul 24 14:31 swissprot.fasta.phr
-rw-rw-r-- 1 moshea moshea 4.4M Jul 24 14:31 swissprot.fasta.pin
-rw-rw-r-- 1 moshea moshea 198M Jul 24 14:31 swissprot.fasta.psq
-rw-rw-r-- 1 moshea moshea 272M Jul 24 14:30 swissprot.fasta
-rw-rw-r-- 1 moshea moshea 1.1K Jul 24 14:30 relnotes.txt
This is what I get when trying to run:
(zdb) moshea@shannon:/mnt/LargeStorageNoBackup/Datasets/Moshea/Databases$ zdb run --input=zdb_table.csv --ko --cog --pfam --ref_dir=/mnt/LargeStorageNoBackup/Datasets/Moshea/Databases/zdb/ --conda
Starting the analysis pipeline
N E X T F L O W   ~  version 24.04.3
Launching /home/moshea/miniconda/envs/zdb/share/zdb-1.3.1/annotation_pipeline.nf [voluminous_dalembert] DSL2 - revision: 067a6b5acf
wrong type for swissprot_db /mnt/LargeStorageNoBackup/Datasets/Moshea/Databases/zdb/uniprot/swissprot/
ERROR ~ assert(false)
-- Check script '/home/moshea/miniconda/envs/zdb/share/zdb-1.3.1/annotation_pipeline.nf' at line: 48 or see '.nextflow.log' file for more details
Could not finish the analysis
Try to rerun the same command with the --resume flag set to rerun the analysis

Unfortunately I could reproduce the issue, seems the conda release is broken somehow. Will take a look tomorrow and keep you posted. If you're in a hurry you can install from source, which will work.

It was an issue with newer releases of nextflow and will be fixed with https://github.com/metagenlab/zDB/pull/120. I'll launch the release process to bioconda this afternoon.

Ok, thanks!

Ok release is out, so you can update your conda environment and things should work.
I noted that one of the conda environments does not seem to build anymore, so run zdb without the --conda option and everything should be fine. If you absolutely have to use --conda, you will have to apply this change to your zdb (somwhere like  ~/bin/miniconda3/envs/zdb/share/zdb-1.3.2/conda/checkm.yaml).

Hi,
I've managed to get close to the end of the pipeline using singularity, but it crashed on this error:
INFO:    Converting SIF file to temporary sandbox...
Loading gbks
Loading groups
Loading seq hashes
Loading orthofinder results
Loading alignments
Loading checkm results
Traceback (most recent call last):
File "/mnt/scratch/work/e7/99c142f9724da8c63d6f99f3cc40f3/.command.sh", line 26, in
setup_chlamdb.load_genomes_info(kwargs, gbk_list, "checkm_results.tab", "marvelous_elion")
File "/mnt/scratch/zDB/bin/setup_chlamdb.py", line 466, in load_genomes_info
taxon_id = hsh_filename_to_taxid[row["Bin Id"]]
KeyError: nan
INFO:    Cleaning up image...

At first glance that seems like an issue in your input files, with checkm having nan as "Bin ID" for some genomes. This is supposed to be the unique identifier of the genome, so that won't work. Maybe try to have a look at the checkm outputs?

I'll close this issue, as the issue initially reported is fixed. If you still have an issue with your input, you can open another issue for that and I can try to help you figure out the issue with your input files.


please use musl-libc for static builds to avoid glibc bug

Hello,
There is a glibc bug which is affecting the current skopeo builds from this repository. More details can be found in this blog post.
We (kubespray project maintainers) want to use skopeo as part of kubespray when deploying with cri-o and would like to use a distribution independent release that can be aligned between our various supported distributions (see https://kubespray.io/#/docs/ci) but we hit the issue described above. When running the binary releases from this repository and trying to do a skopeo copy we get the following error:
INFO[0000] Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled
Getting image source signatures
Copying blob 5f70bf18a086 skipped: already exists
Copying blob 9be70a1d2594 done
Copying blob 727c7d3892e3 done
Copying blob 81af2f2a6fbd done
Copying blob 2668dcc90be0 done
Copying blob cf03e0d52918 done
FATA[0002] writing blob: adding layer with blob "sha256:727c7d3892e387293604ea704f8645b0ee377cfd35a2891aca1a88b57a811d5d": processing tar file(fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0xe5 pc=0x7f3ad7421bd0]

runtime stack:
runtime.throw(0xf80091, 0x2a)
        /usr/local/go/src/runtime/panic.go:1117 +0x74
runtime.sigpanic()
        /usr/local/go/src/runtime/signal_unix.go:718 +0x305

goroutine 1 [syscall, locked to thread]:
runtime.cgocall(0xeab650, 0xc00061fb18, 0xc0000122e0)
        /usr/local/go/src/runtime/cgocall.go:154 +0x5d fp=0xc00061fae8 sp=0xc00061fab0 pc=0x40573d
os/user._Cfunc_mygetpwuid_r(0x0, 0xc0003ed710, 0x1b71070, 0x400, 0xc0000122e0, 0x7f3a00000000)
        _cgo_gotypes.go:172 +0x4a fp=0xc00061fb18 sp=0xc00061fae8 pc=0x7bc7aa
os/user.lookupUnixUid.func1.1(0x0, 0xc0003ed710, 0xc000193d20, 0xc0000122e0, 0xc00061fbb8)
        /usr/local/go/src/os/user/cgo_lookup_unix.go:103 +0xd2 fp=0xc00061fb68 sp=0xc00061fb18 pc=0x7be052
os/user.lookupUnixUid.func1(0x121f3a0)
        /usr/local/go/src/os/user/cgo_lookup_unix.go:103 +0x47 fp=0xc00061fba0 sp=0xc00061fb68 pc=0x7be0c7
os/user.retryWithBuffer(0xc000193d20, 0xc00061fc78, 0x0, 0xc00061fdb0)
        /usr/local/go/src/os/user/cgo_lookup_unix.go:247 +0x42 fp=0xc00061fbf8 sp=0xc00061fba0 pc=0x7bdc42
os/user.lookupUnixUid(0x0, 0x0, 0x0, 0x0)
        /usr/local/go/src/os/user/cgo_lookup_unix.go:96 +0x132 fp=0xc00061fcc0 sp=0xc00061fbf8 pc=0x7bd032
os/user.current(0xc0001ec000, 0x1000, 0x1000)
        /usr/local/go/src/os/user/cgo_lookup_unix.go:49 +0x4b fp=0xc00061fd00 sp=0xc00061fcc0 pc=0x7bca6b
os/user.Current.func1()
        /usr/local/go/src/os/user/lookup.go:15 +0x25 fp=0xc00061fd28 sp=0xc00061fd00 pc=0x7bdd65
sync.(*Once).doSlow(0x198b820, 0x13170f8)
        /usr/local/go/src/sync/once.go:68 +0xee fp=0xc00061fd78 sp=0xc00061fd28 pc=0x488eae
sync.(*Once).Do(...)
        /usr/local/go/src/sync/once.go:59
os/user.Current(0xffffffffffffffff, 0xc00061fde8, 0xb917e6)
        /usr/local/go/src/os/user/lookup.go:15 +0x105 fp=0xc00061fda8 sp=0xc00061fd78 pc=0x7bc125
os/user.Lookup(0xf5633a, 0x7, 0xc000096270, 0x0, 0x0)
        /usr/local/go/src/os/user/lookup.go:33 +0x28 fp=0xc00061fdf8 sp=0xc00061fda8 pc=0x7bc168
github.com/containers/storage/pkg/chrootarchive.chroot(0x7ffe562b177d, 0x69, 0x0, 0x0)
        /build/vendor/github.com/containers/storage/pkg/chrootarchive/chroot_linux.go:30 +0xb8 fp=0xc00061fed8 sp=0xc00061fdf8 pc=0xdbbd38
github.com/containers/storage/pkg/chrootarchive.untar()
        /build/vendor/github.com/containers/storage/pkg/chrootarchive/archive_unix.go:46 +0x185 fp=0xc00061ff38 sp=0xc00061fed8 pc=0xdbafa5
github.com/containers/storage/pkg/reexec.Init(...)
        /build/vendor/github.com/containers/storage/pkg/reexec/reexec.go:30
main.main()
        /build/cmd/skopeo/main.go:128 +0xf6 fp=0xc00061ff88 sp=0xc00061ff38 pc=0xe95416
runtime.main()
        /usr/local/go/src/runtime/proc.go:225 +0x263 fp=0xc00061ffe0 sp=0xc00061ff88 pc=0x43ba03
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1371 +0x1 fp=0xc00061ffe8 sp=0xc00061ffe0 pc=0x4700a1
): exit status 2

We get this when the destination is a cri-o container engine. When we build skopeo in an alpine linux golang container everything works fine and the image is properly uploaded.
As a proof of concept please see https://github.com/simplekube-ro/skopeo-binary.
As far as I can tell this is as close as we can get to an upstream binary release and would be glad to open a PR to switch the builder  image like in my PoC build.

Thanks for the heads up, and the pr contribution. Please merge it over.

@lework the PR is open if you have the time to take a look and merge it would be great.
Would you be OK with the kubespray project using the binary artefacts from your repo for our cri-o deployment option given that the upstream skopeo project does not publish official binary builds?

@cristicalin ok


snap: switch to base core20

This happens to fix missing icons in CoqIDE

Does the "core" selection has an effect on which versions of Ubuntu the snap runs?
In one of your commits on the mathcomp school I have seen an explicit request for adwaita - can you leave a few words on the different methods? Should we maybe do both (switch core +gtk and explicitly request adwaita?)

Adding the package explicitly did have no effect. My guess is that the package is already in the core or in the extension, so it is not added to the image.
I could not find any info on there requirements implied by the choice of the base. In some sense I think it is orthogonal, it a file system image, you can run core20 on a fedora. There might be some nasty dependency on gnome on system stuff, but I checked and gnome-3-38 works on ubuntu 16.04, so I guess we are safe:
https://snapcraft.io/install/gnome-3-38-2004/ubuntu
I sincerely don't know why this fixes the problem. So please double test it on your side.
I'm wondering if we can do something like https://unix.stackexchange.com/questions/365268/how-do-i-take-a-screen-shot-of-my-xvfb-buffer and upload the screenshot as an artifact of the smoke test job.

I see, thanks! I am btw. quite sure that it did work fine on my computer (running Ubuntu 20.04 LTS) when I last tested it, but I am not sure if I tested it via the alias or via putting the executable into the path, probably the latter.

But of course the snap should provide adwaita, and this is what should be picked up by CoqIDE.

I guess from a snap point of view it is a hack / stretch, but I actually prefer to put the snap image bin folder into my path and call the commands this way - with the patched I did to ocamlfind this works fine (as far as I tested it).
But indeed I should also test the aliases.
I am unsure what to recommend to users. Did you try mapping the bin folder into your PATH?

I meant looking into /snap/xx. For running coqide going via the snap link works reasonably well. I am not so sure about console usage of the coq ecosystem.

@gares : I restarted the snap job since it failed CI - if it fails again we need to look into it.

@gares : it failed again in the same way. So I there seem to be interactions between the snap base version and the host OS version. But strangely it is also Ubuntu 20 (20.04 LTS)
Any thought what I can do about this? I can't merge it if it kills CI.

I did not see the failure because it is in a plugin I did not build.
It just seems one needs to install libstdc++SOMETHING-dev (eg SOMETHING=-10). Maybe it used to be there in the old image but not in the new one.

if I'm right, then it should be a depext of the plugin linking with z3 I guess

It worked (I did kill the other jobs)

I was wrong, the library is there... (ABI version 6). So I don't get why it is not found...

I will do some local tests today or tomorrow.

Apparently on my Ubuntu stdc++6 is there for compat reasons, but you can't link against it, that is the .so symlink is only available from ABI 7 to 10:
libstdc++-10-dev: /usr/lib/gcc/x86_64-linux-gnu/10/libstdc++.so
libstdc++-7-dev: /usr/lib/gcc/x86_64-linux-gnu/7/libstdc++.so
libstdc++-8-dev: /usr/lib/gcc/x86_64-linux-gnu/8/libstdc++.so
libstdc++-9-dev: /usr/lib/gcc/x86_64-linux-gnu/9/libstdc++.so

I've pushed a commit with 7

@gares : can you please rebase this PR to main latest?

Hmm - still does not pass. I guess I should have a look with local builds.

Z3

Closing since we no longer support snap (for the time being).


Problem getting started with indexeddb codelab

After running the server, when I open the browser I have the following error.

Hi, sorry you're having trouble. Do you have any more information? Perhaps you could share the commands you are running and/or your command line output? Or what step you're on and if you've made code changes

Hello @DavidScales, thank you for the response.

I will attach the screenshots of the commands I am running and command line output.
I am at step 2 Get Set Up. I did not change any code.

Thanks @anushagadepalli, I'm not able to reproduce the issue. But it looks like from your command logs that the server installs and runs successfully, and you are in the correct directory. So the issue could be on the browser end.
Can you try starting the server again, and this time open localhost in an incognito window (or private window). If you're using Chrome, try clearing the caches and uninstalling previous service workers (Dev Tools > Application tab > Clear storage panel > Clear site data button) and then refreshing.
Often when I am working with service workers on localhost, old service workers from previous work remain in the browser and can mess up requests. Let me know if that fixes it.

Hello @DavidScales, thank you for your suggestion. I found the issue.
The application is available on http://<IP_ADDRESS>:8080/index.html as opposed to http://<IP_ADDRESS>:8080. Some background on my dev environment: I use a Windows OS, so may be the server cannot serve the app or could not access index.html? Any leads would be helpful. Thank you in advance.

Oh I see. I'm not sure why that is happening. But it's fine to use http://<IP_ADDRESS>:8080/index.html. Ideally http://<IP_ADDRESS>:8080, http://<IP_ADDRESS>:8080/, and http://<IP_ADDRESS>:8080/index.html should be requested the same from your browser, and should be returned the same from a server. But you're fine to continue the labs using whichever works on your system. Let me know if you have more questions! Best of luck


add .gitignore to templates

Add .gitignore to each template so each MF app would have its own independent .gitignore file that suits the MF app

I'm working on this issue and creating a PR for this soon

Found the source of the bug!🎉
Looking into the installed package at the global node_modules directory, the create-mf-app node_module at C:\Users\{user}\AppData\Roaming\npm\node_modules\create-mf-app doesn't seem to have the .gitignore files in the templates.
This is apparently a known issue with npm and will need a fix on our level, ill submit a PR request soon hopefully :)
I'll work on a solution where for each app at the end it will rename the file from gitignore to .gitignore since this seems to be the common solution in the issue thread. If you think of other more elegant solutions I would love to discuss them.

Thanks, @JonathanDagan, I just pushed a repository with node_modules because I didn't notice .gitignore was missing!
@jherr looking forward to get this one merged!

✅Bug Fixed!🎉
#8 has been merged so I'm closing this issue :)


Status = WaitingForActivation

I tried the library and it's not even trying to send the email. The result from client.SendMail(emailMessage) is always: Status = WaitingForActivation. I already enabled the "Internet (client)" capability in the manifest file, but it's still not working. Am I missing something?

This is usually occurring when you are calling an awaitable method without the await keyword.
You should call the SendMail method as follows:
await client.SendMailAsync(emailMessage);

This will cause a WaitingForActivation message:
client.SendMailAsync(emailMessage);


[release-1.22] Pin appVersion to v1.22.0

What this PR does / why we need it:
This PR pins appVersion of Charts to 1.22
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

Taken care by https://github.com/kubernetes/cloud-provider-openstack/pull/1626/files
closing this.
/close


Add morcus.net

https://morcus.net/dicts , a collection of digital tools for Latin learners.
From my browser, I see 171.86 kB transferred (525.60 kB total).

Welcome to the 250kB Club! Your sub page will be https://250kb.club/morcus-net


[Vault] Aura OHM-DAI

API PR: https://github.com/beefyfinance/beefy-api/pull/1100
I had to add OHM token into API's address-book package so rn I'm not sure if it's not necessary to build & publish the package (as blockchain-addressbook) once the API pull request is merged?
Aura OHM-DAI contracts:
vault: 0x17dEc2AF8018f2F940D34787399eA123Ff292963
strat: 0x244720cB77215fF57e34d613C0F4AA2f48Cb13c6

Nice work!


[FALSE-POSITIVE]

Our website https://gowc.us/ is listed as phishing and fraud with you could you reclassify us now that we have resolved the issue

Please remove gowc.us from your list


CyBQM QOL

Includes several QOL changes:

Restructure the way cyBQM tests are organized (includes the content from #571)
Change the way cyBQMs are constructed
Change the to_coo method to match the legacy to_numpy_vectors method.

Codecov Report

Merging #574 into dev will increase coverage by 0.16%.
The diff coverage is 81.04%.

@@           Coverage Diff            @@
##            dev     #574      +/-   ##
========================================
+ Coverage    91%   91.17%   +0.16%
========================================
  Files        57       57
  Lines      4281     4306      +25
========================================
+ Hits       3896     3926      +30
+ Misses      385      380       -5

Impacted Files
Coverage Δ

dimod/bqm/__init__.py
100% <100%> (ø)
:arrow_up:

dimod/core/bqm.py
79.59% <65.82%> (-6.4%)
:arrow_down:

dimod/bqm/adjdictbqm.py
94.6% <97.18%> (+1.67%)
:arrow_up:

dimod/serialization/fileview.py
85.86% <0%> (+16.19%)
:arrow_up:

Continue to review full report at Codecov.

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


Clicking on a tx in the address page on testnet redirects back to mainnet

Describe the bug
Clicking on a tx in the address page on testnet redirects back to mainnet
To Reproduce
Steps to reproduce the behavior:

Go to any address page on testnet
Click on any tx in the list
page redirects to mainnet and user has to pick testnet again from navbar network menu

Expected behavior
explorer should stay on testnet
Screenshots

Desktop (please complete the following information):
macOS, brave browser
Additional context
I think it's due to the tx link being https://explorer.stacks.co/txid/0x7144702f8a38305236f9fa6c774b88d81e583316d5ceef36e1319dcb41f4f3fa?chain=https%3A%2F%2Fstacks-node-api.testnet.stacks.co
normally tx link should end with ?chain=testnet but since it's incorrect for some reason it falls back to mainnet as default network.
imo need to find out when this bug was introduced that adds the chain=api address and revert it.

I can reproduce this on any list item on testnet, not only txid

:tada: This issue has been resolved in version 1.36.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[FEATURE] Add marker for top-level functions in Kotlin

First of all thanks for this awesome plugin!
When developing Jetpack Compose, you work with a lot of (top-level) functions in a Kotlin file.
@Composable
fun MyScreen() {
  MyWidget()
}

@Composable
private fun MyWidget() {
}

It would be nice if functions (both public and private) can also be displayed as markers.

Thank you, i will consider it


PUT issues

when i try :
curl -i -X PUT http://localhost/phalcon-rest-master/users/2
I get result:
Status : 401 Unauthorized
{
"status": "ERROR",
"data": "Access is not authorized"
}
what i should do for this issue?

You cand PUT to http://localhost/phalcon-rest-master/users/2 you should PUT to http://localhost/phalcon-rest-master/users


Check for user and password also in DAV blobstores

According to the list in https://github.com/cloudfoundry/bosh/blob/f91fce17854855fb242e8cc24f1d777703f24260/blobstore_client/lib/blobstore_client/client.rb#L4 DAV is a valid option for a blobstore client

merged with commit https://github.com/cloudfoundry/bosh/commit/5a1a8dfc33543f95c59583b4226e454163575b1c


Nice work, grats

I'm using your configuration with lit-element :3
Thank you

Whoa, thank you 🙂😌
It will be great if you share a link to your repo, so i could watch how it going!
I'm going to update readme and update a guide how it works. Hope it helps people to understand whats going inside


fix(deps): update prisma monorepo to v4.5.0

😭

Not exactly the outcome I was aiming for, but hey, at least I got the information I needed 😄

This looks like it's correct, no?


Fix qualified variable look-ups

When Puppet runs, a lot of warnings are returned via stdout to the user:
Warning: Scope(Class[Rcs]): Could not look up qualified variable 'rcs::params::tmptime'; class rcs::params has not been evaluated
Warning: Scope(Class[Rcs]): Could not look up qualified variable 'rcs::params::sulogin'; class rcs::params has not been evaluated
Warning: Scope(Class[Rcs]): Could not look up qualified variable 'rcs::params::delaylogin'; class rcs::params has not been evaluated
Warning: Scope(Class[Rcs]): Could not look up qualified variable 'rcs::params::utc'; class rcs::params has not been evaluated
Warning: Scope(Class[Rcs]): Could not look up qualified variable 'rcs::params::verbose'; class rcs::params has not been evaluated
Warning: Scope(Class[Rcs]): Could not look up qualified variable 'rcs::params::fsckfix'; class rcs::params has not been evaluated

This is not ideal. Work out what's going on, and hopefully fix the issue. (Hint: it's possibly due to resource ordering.)

I wonder if this is because the variables have a value which requires params be evaluated first. Moving the variables out, or somehow stopping them require a value of the params manifest, might fix this.
Still thinking.


[Bug] [Mater] The process always runs when the process contains subprocess and params deliver

close #14855

Codecov Report

:exclamation: No coverage uploaded for pull request base (3.1.9-prepare@146f46d). Click here to learn what that means.
 Consider uploading reports for the commit af127eb to get more accurate results

@@               Coverage Diff                @@
##             3.1.9-prepare   #14856   +/-   ##
================================================
  Coverage                 ?   38.22%
  Complexity               ?     3986
================================================
  Files                    ?     1000
  Lines                    ?    36924
  Branches                 ?     4264
================================================
  Hits                     ?    14115
  Misses                   ?    21192
  Partials                 ?     1617

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


manage shellcheck warnings

Thank you for developing this script. You may want to use shellcheck to maintain code quality and to detect some bugs automatically.
The first step would be fixing the existing warnings:
mgitstatus:186:30: note: Use find instead of ls to better handle non-alphanumeric filenames. [SC2012]
mgitstatus:188:24: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:202:24: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:211:20: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:280:38: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:281:38: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:282:42: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:304:44: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:309:44: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:314:44: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:319:44: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:324:44: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:329:44: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:335:71: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]
mgitstatus:341:24: note: Don't use variables in the printf format string. Use printf '..%s..' "$foo". [SC2059]

The second step would be running shellcheck from a CI system for every commit and pull request. One possible way to do it would be using Cirrus CI, you can model the configuration after this example. Unfortunately, Cirrus CI does not support e-mail notifications, but the service is still free (up to a monthly limit) for open source software projects.

Hey Denis!
Thank you for pointing this out. Multi-git-status already uses Shellcheck. There's a [test rule](https://github.com/fboender/multi-git-status/blob/d943f040d6ba5fdae960a7aeceffda0231904637/Makefile#L15) in the Makefile that executes it.
The problems found by Shellcheck that you listed are known, but have reasons for why they're still being used. See above link for excludes and their reasoning.
make test is called in a git pre-commit hook locally in my repo, so that it runs automatically before I commit.


Propagate shadow worker start error

What changed?
Return error when shadow worker failed to start

Why?
Bug fix

How did you test it?
Unit test.

Potential risks
N/A

Pull Request Test Coverage Report for Build 11abe7ba-03d4-4cfd-8af3-f6d49f2ad435

0 of 0   changed or added relevant lines in 0 files are covered.
20 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 75.663%

Files with Coverage Reduction
New Missed Lines
%

internal/internal_worker.go
20
84.65%

Totals

Change from base Build f926739c-1f26-4225-8b55-dd8cd87588e1:
0.1%

Covered Lines:
10129

Relevant Lines:
13387

💛  - Coveralls


QF-4536-Add Teams Endpoints to manage teams

New endpoints have been created for managing both teams and member under organization for CRUD actions

Can you please rebase on the latest master and squash all the changes in a single commit?
Please add typing on all the methods that you add in this PR, except the tests.
Also, unfortunately I see some of our verbal conversation feedback was not addressed.

Do you want to add typing also in variables or is it overkill?
for example email_or_username: str = data.get("member", "")

Please add typing on all the methods that you add in this PR, except the tests.

Do you want to add typing also in variables or is it overkill?
for example email_or_username: str = data.get("member", "")

Add typing only when the type cannot be guessed by the type checker. In the case you mentioned, the typechecker has no way to get what is the type at key "member", so it will be Any.
But if you have:
def foo() -> int: ...
bar = foo()

There is no need to set the type of bar, as we already set that foo is always returning an int.

Task linked: QF-4536 Add API endpoint to manage teams


How is this related to Anti-Spoofing?

@cleardusk I'm a noob, please help me with this question: How can I use this code to perform spoof face dataset synthesis as mentioned in your paper: https://arxiv.org/pdf/1901.00488v2.pdf
I've looked through the repo and see that the main features are Face alignment, Face reconstruction, 3D pose estimation, Depth image estimation and PNCC & PAF features; and also the code. I didn't know what part is for spoof face dataset synthesis. Please explain this to me.

Sorry for that, this repo is not for that paper Improving Face Anti-Spoofing by 3D Virtual Synthesis. The code of that paper is not released.


Proposal: Fail or warn when comparison arg widths do not allow both occurrences

There is class of errors where comparison operators are working on values where the number
of bits precludes either a negative or positive result from occurring.
The classic example is
val reg = RegInit(0.U)  // this is a bug that allocates only 1 bit for the register
reg := reg + 1.U
when(reg > 4) {
   // This code cannot be reached because reg cannot be bigger than 1
  ???
}
There should be some way that a firrtl pass (possibly part of DCE or Constant Propagation) could detect this situation.
While there are concerns that parameterizations could create these situations that still result in desired behavior.  But I suspect there is a more correct way of writing the code based on parameters that would not have the mismatched bits in comparisons.

I'm going to close this to ensure any conversation is in the same place: https://github.com/freechipsproject/chisel3/issues/697


Lua print function replcament issue...

Unable to convert correctly from bool to string, int to string, float to string, and double to string.
If you know a way to do that, thanks by advance.

EDIT : Rectifivation ints prints correctly when they are not NIL...
The problem with the Color method was the R, G, B and A being NULL instead of a number.
So the real problem of print is that it print nothing instead of 'null' or 'nil', and it's not able to print bool values.

Fixed in latest commit !


Use arrow functions in callbacks

Modernizing our Messaging example. Developers don't use function declarations in callbacks anymore.

thanks!


Outdated "v4.1 ideas" milestone

I see you use Projects rather than Milestones. So, please remove "v4.1 ideas" milestone. It might be confusing.

Done!


deploy/helm: add option to create PodSecurityPolicy

Description
Creating the PodSecurityPolicy is disabled by default. This can be
overridden in values.yaml or on the command line.
Example:
helm template deploy/helm/eunomia-operator/ \
  --set eunomia.operator.image.tag=dev \
  --set eunomia.operator.podSecurityPolicy.enabled=true \
  --set eunomia.operator.image.pullPolicy=Never | kubectl apply -f -

Fixes #383
Type of change

New feature (non-breaking change which adds functionality)

Checklist

[ ] Unit tests and e2e tests updated
[ ] Documentation updated

Looks good, can we just add a snippet in the documentation that it is supported and can be enabled through the helm chart?

@vinny-sabatini fixed in commit f87653d76a88edff90f4b808f62b1331584d9acd.


[stable/sentry] Missing documentation for user.password

Describe the bug
The documentation is missing a callout and description for the user.password setting.
Version of Helm and Kubernetes:
N/A
Which chart:
stable/sentry v3.1.5
What happened:
N/A
What you expected to happen:
Document the use of setting your own Admin password via user.password value.
How to reproduce it (as minimally and precisely as possible):
N/A
Anything else we need to know:

Go away stale bot

Also searching for this.


Add option for providing script to check that any version file was updated

Generally, when a new release is created, some kind of version file is modified to update the version number, e.g. __version__ = 1.2.3 in a Python module's __init__.py file.
An option for users to provide their own script to check that the to-be-created tag matches their application's version would be useful. For example, for a Python module called my_module:
$ python3 -c "import my_module; assert my_module.__version__ == '1.2.3'"

If that check fails, the action should fail. The version string to compare against should be the match for the version_regex, before prepending the version_tag_prefix.
The option could have a default value of "" which would simply skip the check.

Closed via #111

Example: https://github.com/christophebedard/tag-version-commit/commit/d902eff84c4b99ff6c7d8b420f91c9e8bfa29f83
The commit is titled "1.0.4" but the commit didn't update the version in the package.json file, which is what the version_assertion_command checks in both tag/tag and test/test-action jobs, so they fail:

https://github.com/christophebedard/tag-version-commit/runs/1045652656
https://github.com/christophebedard/tag-version-commit/runs/1045652680

I then updated the package.json file so that the version matches and all actions/jobs pass: https://github.com/christophebedard/tag-version-commit/commit/0a1cbb14707ecf36d16aeb2241d4d8cf80e8f773


Parse a state action string like a shell

Fixes #5
We cannot simply split it by space because the address of resource can contain spaces.
We should parse it like a shell with go-shellwords.

Given the following configuration:
terraform {
  required_version = "0.13.5"

  required_providers {
    docker = {
      source  = "terraform-providers/docker"
      version = "2.7.2"
    }
  }
}

resource "docker_image" "nginx" {
  name         = "nginx:latest"
  keep_locally = false
}

# resource "docker_container" "nginx" {
#   image = docker_image.nginx.latest
#   name  = "example"
# }

resource "docker_container" "nginx" {
  for_each = {
    "This is an example" = "example"
  }

  image = docker_image.nginx.latest
  name  = each.value
}

A migration file is the following. Note that we need to escape double-quote ( \" ). It's a HCL limitation.
migration "state" "test" {
  dir = "tmp/test5"
  actions = [
    "mv docker_container.nginx 'docker_container.nginx[\"This is an example\"]'",
  ]
}

Run the tfmigrate plan command:
[tfmigrate@fix-iss-5|✔]$ TFMIGRATE_LOG=DEBUG bin/tfmigrate plan tmp/test5/state_mv.hcl
2020/11/05 22:11:51 [DEBUG] [main] start: bin/tfmigrate plan tmp/test5/state_mv.hcl
2020/11/05 22:11:51 [DEBUG] [main] tfmigrate version: 0.1.0
2020/11/05 22:11:51 [DEBUG] [command] option: &tfmigrate.MigratorOption{ExecPath:""}
2020/11/05 22:11:51 [INFO] [command] read migration file: tmp/test5/state_mv.hcl
2020/11/05 22:11:51 [DEBUG] [command] parse migration file: "migration \"state\" \"test\" {\n  dir = \"tmp/test5\"\n  actions = [\n    \"mv docker_container.nginx 'docker_container.nginx[\"This is an example\"]'\",\n  ]\n}\n"
failed to decode migration file: tmp/test5/state_mv.hcl, err: tmp/test5/state_mv.hcl:4,57-61: Missing item separator; Expected a comma to mark the beginning of the next item.
[tfmigrate@fix-iss-5|✔]$ TFMIGRATE_LOG=DEBUG bin/tfmigrate plan tmp/test5/state_mv.hcl
2020/11/05 22:12:13 [DEBUG] [main] start: bin/tfmigrate plan tmp/test5/state_mv.hcl
2020/11/05 22:12:13 [DEBUG] [main] tfmigrate version: 0.1.0
2020/11/05 22:12:13 [DEBUG] [command] option: &tfmigrate.MigratorOption{ExecPath:""}
2020/11/05 22:12:13 [INFO] [command] read migration file: tmp/test5/state_mv.hcl
2020/11/05 22:12:13 [DEBUG] [command] parse migration file: "migration \"state\" \"test\" {\n  dir = \"tmp/test5\"\n  actions = [\n    \"mv docker_container.nginx 'docker_container.nginx[\\\"This is an example\\\"]'\",\n  ]\n}\n"
2020/11/05 22:12:13 [INFO] [command] new migrator: &config.StateMigratorConfig{Dir:"tmp/test5", Actions:[]string{"mv docker_container.nginx 'docker_container.nginx[\"This is an example\"]'"}}
2020/11/05 22:12:13 [INFO] [migrator] start state migrator plan
2020/11/05 22:12:14 [DEBUG] [executor@tmp/test5]$ terraform version
2020/11/05 22:12:14 [INFO] [migrator@tmp/test5] terraform version: 0.13.5
2020/11/05 22:12:14 [INFO] [migrator@tmp/test5] initialize work dir
2020/11/05 22:12:15 [DEBUG] [executor@tmp/test5]$ terraform init -input=false -no-color
2020/11/05 22:12:15 [INFO] [migrator@tmp/test5] get the current remote state
2020/11/05 22:12:16 [DEBUG] [executor@tmp/test5]$ terraform state pull
2020/11/05 22:12:16 [INFO] [migrator@tmp/test5] override backend to local
2020/11/05 22:12:16 [INFO] [executor@tmp/test5] create an override file
2020/11/05 22:12:16 [INFO] [executor@tmp/test5] switch backend to local
2020/11/05 22:12:17 [DEBUG] [executor@tmp/test5]$ terraform init -input=false -no-color -reconfigure
2020/11/05 22:12:17 [INFO] [migrator@tmp/test5] compute a new state
2020/11/05 22:12:17 [DEBUG] [executor@tmp/test5]$ terraform state mv -state=/var/folders/zh/37j0y_pn2pzc295c19rpw2tw0000gp/T/tmp756235542 -backup=/dev/null docker_container.nginx docker_container.nginx["This is an example"]
2020/11/05 22:12:17 [INFO] [migrator@tmp/test5] check diffs
2020/11/05 22:12:19 [DEBUG] [executor@tmp/test5]$ terraform plan -state=/var/folders/zh/37j0y_pn2pzc295c19rpw2tw0000gp/T/tmp877907325 -out=/var/folders/zh/37j0y_pn2pzc295c19rpw2tw0000gp/T/tfplan340595896 -input=false -no-color -detailed-exitcode
2020/11/05 22:12:19 [INFO] [executor@tmp/test5] remove the override file
2020/11/05 22:12:19 [INFO] [executor@tmp/test5] switch back to remote
2020/11/05 22:12:19 [DEBUG] [executor@tmp/test5]$ terraform init -input=false -no-color -reconfigure
2020/11/05 22:12:19 [INFO] [migrator] state migrator plan success!

Looks good to me.


Add Xcode 11.3 beta

Tool information

Tool name:
Add or update?
Desired version: 11.3 beta
Approximate size: ~9GB
If this is an add request:

Brief description of tool: most recent version of Xcode
URL for tool's homepage: https://developer.apple.com

Virtual environments affected

[x] macOS 10.15
[ ] Ubuntu 16.04 LTS
[ ] Ubuntu 18.04 LTS
[ ] Windows Server 2016 R2
[ ] Windows Server 2019

Can this tool be installed during the build?
Sort of—via xcode-install. It takes a while.
Are you willing to submit a PR?
Sure?
Notes
Xcode 11.3 fixes a major bug in the Swift toolchain that breaks apps built with Xcode 11.2.x using Swift packages.

This is currently rolling out (and may have already reached your account). Docs updates will follow.


Unable to add the plugin to an Android project!

I was trying to use this plugin in an Android app and facing this issue:

I can see that this plugin is released on:
https://plugins.gradle.org/m2/ai/clarity/codeartifact/ai.clarity.codeartifact.gradle.plugin/
but I am not sure if Android Gradle uses the same repo!
any suggestion on how to fix it?

Hi @mohsenoid, sadly I'm not an Android developer, but the plugin is released in the official gradle central plugin repositories.
Exactly here: https://plugins.gradle.org/plugin/ai.clarity.codeartifact
Can you share your build.gradle file?

Thanks for the reply, it isn't a special setup. I even tried it with a new Android project and it didn't work.
Looks like the Gradle in Android projects uses another repo to pull plugins or somehow ignores this one.
Feel free to close this issue, cause we switch to GitHub Packages instead of AWS CodeArtifact, cause it doesn't neet generating token OTG.

Thanks


Add button for editing a context pack

We should have a button for editing a context pack

We will close this issue since this feature is not included in the stories list we sold.


Execute async option

Summary

This is a simple change to the existing task to support the Snowflake get/put command.
Snowflake get/put commands don't work when using the Snowflake async_execute method.
NB. This is my first PR - please be kind :)
Apologies ... I'm not sure how to complete the CHANGELOG.md
Relevant Issue(s)

Add a task to run PUT file commands; closes #8
Checklist

[ ] Summarized PR's changes in CHANGELOG.md

I think this closes https://github.com/PrefectHQ/prefect-snowflake/issues/8

Yes, I did consider that. I'll update to add the new task.


Bumps

includes all dependant issues

@tomlovesgithub I ran npm i and npm run serve and there was an error in my terminal. I am not sure if it only happens on my laptop (Mac M1).

I encountered the same issue (I'm using Mac M1), I delete node_mudules and npm install again, then npm run serve can work.


First approach to export to PDF using QuestPDF

First approach to export to PDF using QuestPDF.
Created PDFService similar to existing ExcelService and added an "Export to PDF" button on eCommerce->Products page.
Rough fit columns calculation.
Numbers and text alignment.

cool! thank you very much.


[Storage] Fix issue #12291: az storage blob generate-sas does not properly encode --full-uri

Description

Fix issue #12291
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Storage

/azp run


Use JS scripts instead of Makefile

Issue: https://github.com/exercism/javascript/issues/646

No make dependency anymore!

Uses shelljs for all shell commands. So everything is unix-like without depending on OS commands! shelljs gets removed while syncing to exercise dirs and while performing checksum.

Travis job now uses these JS scripts instead.

Next step is to streamline process, change all the docs, add contributing doc and delete Makefile.

Fixed all review comments apart from those two (left unresolved). Let me know your thoughts & I can convert to ES syntax and use babel-cli.

Let's just get this merged. We can edit later.


acbuild run with systemd-208 fails

systemd v208 on CentOS 7.  acbuild run fails because this version of systemd-nspawn doesn't support the -q/--quiet option.

That's definitely an issue. I just made a PR that should fix this (https://github.com/appc/acbuild/pull/141), would you be willing to take it for a spin and make sure that this is fixed on your end?

@dgonyeo different error, now. :-)
systemd-nspawn: unrecognized option '--register=no'

It appears --register was also added in v209.

So, removing --register does allow acbuild run.  Assuming the behavior in v208 is to register the container with machined, I don't know what the impact of that is.

@blalor registration isn't really anything important, https://github.com/appc/acbuild/pull/135 removed registration, but it needs to check for the systemd version to ensure that flag is valid to fix this issue.
I wonder if using nspawn is more effort to maintain than it's worth. Perhaps a pure go implementation for execution would make more sense (something like libcontainer with minimal options perhaps?). Or even running rkt (which I believe bundles systemd).

I'd prefer to just get around to https://github.com/appc/acbuild/issues/13, which pretty much addresses this (just with more work than dropping nspawn completely).

Just updated the PR for this issue to also not pass --register for when systemd < 209.


Remove modin-hdk package

https://github.com/modin-project/modin/commit/685f7badf9ff9fbef9ce44f425c672539a699b5f

Closed in #148.


Attendance rate

fills the content for those two green boxes in home page of an org. Please hook to the front end and let's see if it does the work or if you have any feedback to update the logic let me know. thanks


Fix bug where picture wasn't being set in PostData or FacebookLink Fixes #203

Fix 2 bugs related to submitting an override picture as part of a feed link. One in PostData where the constructor param "picture" wasn't being used. And one in FeedTemplate where FacebookLink.getPicture wasn't being added to query params. Fixes #203

@trwalzer Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@trwalzer Thank you for signing the Contributor License Agreement!


[USE] List of invalid character sequences is incomplete

The list of invalid character sequences, which the USE documentation describes as “a complete listing of prohibited sequences documented in TUS version 12.1”, is not in fact complete. For Devanagari, it includes the sequences labeled “Do Not Use” of table 12.1, but lacks the sequences labeled in the same way in tables 12.2 and 12.3.
It can be argued that these tables don’t need to be explicitly handled in the USE because their invalid character sequences would already be detected as invalid by not matching any of the regular expressions for well-formed clusters. Stating this in the documentation would be better than claiming “a complete listing”.

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

ID: 194a6d3c-4137-46e9-3a4b-44b990200986
Version Independent ID: a0c8e788-5228-aa28-670e-3ba1ac3faecd
Content: Creating and supporting OpenType fonts for the Universal Shaping Engine - Typography
Content Source: typographydocs/script-development/use.md
Product: typography

Fix in progress.

Fixed


Post cleanup

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@69f866a). Click here to learn what that means.
The diff coverage is 33.3%.

@@            Coverage Diff            @@
##             master      #65   +/-   ##
=========================================
  Coverage          ?   32.74%
=========================================
  Files             ?       59
  Lines             ?    27586
  Branches          ?        0
=========================================
  Hits              ?     9034
  Misses            ?    17576
  Partials          ?      976

Impacted Files
Coverage Δ

internal/pkg/table/policy.go
35.29% <ø> (ø)

internal/pkg/zebra/zapi_linux.go
0% <ø> (ø)

internal/pkg/zebra/route_type_string.go
0% <ø> (ø)

pkg/packet/rtr/rtr.go
93.33% <ø> (ø)

pkg/packet/mrt/mrt.go
54.2% <ø> (ø)

pkg/server/zclient.go
13.87% <ø> (ø)

internal/pkg/zebra/ptm_status_string.go
0% <ø> (ø)

internal/pkg/table/adj.go
53.33% <ø> (ø)

cmd/gobgp/cmd/rpki.go
10.52% <ø> (ø)

internal/pkg/table/message.go
88.27% <ø> (ø)

... and 49 more

Continue to review full report at Codecov.

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


Faulty testcases that should be added back in awhile

All the testcases are in #219
To check if the testcases can be added back. @ntwbruce you might wanna merge master to this branch of yours whenever we make a major change and push it to check 😅

👌


log print log when offer_failed in internal service

Proposed changes
Print log when offer_failed in internal service
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Support multi ip

Motivation:
Support multi ip
Modification:
allow user set ip range and bind enterface network to make virtual host and bound host change.
Result:
Fixes https://github.com/alipay/sofa-rpc-boot-projects/issues/42

Codecov Report

Merging #43 into master will increase coverage by 0.41%.
The diff coverage is 65.41%.

@@            Coverage Diff             @@
##           master      #43      +/-   ##
==========================================
+ Coverage   59.19%   59.61%   +0.41%
==========================================
  Files          45       46       +1
  Lines        1272     1399     +127
  Branches      210      230      +20
==========================================
+ Hits          753      834      +81
- Misses        396      428      +32
- Partials      123      137      +14

Impacted Files
Coverage Δ

...m/alipay/sofa/rpc/boot/container/SpringBridge.java
66.66% <0%> (-8.34%)
:arrow_down:

...sofa/rpc/boot/container/ServerConfigContainer.java
87.94% <100%> (+1.87%)
:arrow_up:

...ay/sofa/rpc/boot/SofaBootRpcAutoConfiguration.java
100% <100%> (ø)
:arrow_up:

...lipay/sofa/rpc/boot/common/NetworkAddressUtil.java
54.65% <54.65%> (ø)

...ay/sofa/rpc/boot/config/SofaBootRpcProperties.java
66.43% <70%> (+0.57%)
:arrow_up:

Continue to review full report at Codecov.

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


Update VersionInfo.in

PRODUCT_ICON typo

Thanks for fixing!

Thanks for providing the files!
2016-05-18 9:25 GMT+02:00 Aleksei<EMAIL_ADDRESS>
Thanks for fixing!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/halex2005/CMakeHelpers/pull/2#issuecomment-219947126


No rank for bytes vector: [33

Hi, I just had feedback from my users that they are experiencing this error:
[ error ] [0]No rank for bytes vector: [33][src/Vocab/Vocab.php:120]
Since this is a problem found by a user who did not save the original text, I don't know exactly what text is causing this problem, I'm very sorry.
I looked at the source code and it should be this code that is causing the error to be reported:
return $this->tokenToRankMap[EncodeUtil::fromBytes($bytes)] ???? throw new OutOfBoundsException(sprintf(
'No rank for bytes vector: [%s]',
implode(', ', $bytes), the
I'm wondering if there is any way to return a default value or not let it report an error when it encounters an error like this?
Thank you.

I'm wondering if there is any way to return a default value or not let it report an error when it encounters an error like this?

You can use Vocab::tryGetRank() method instead of Vocab::getRank from user code, to avoid throw an exception.
In context Encoder::encode() we cannot ignore such errors. Since this can lead to an unpredictable result (it will be impossible to decode tokens back to a text).
The reason for the error may be:

a logical error in the code
broken *.tiktoken file

Please submit a stack trace, used encoding and the input text to encode when the error occurs again.


Free statements/results

Thanks for the awesome library! I do have a question and concern since I am trying to use it. Assuming that I want to keep the connection with MySQL opened to perform continuous work (multi-threaded), how do you free results?
At the moment all I can see is .close() and .close_statement(), but there is no implementation like .free() or .free_results().
Please advise.

The results destructor does the work. You don't need to do anything on your side to free a results object.
The reason why prepared statements need a special close_statement function is because statements are really handles to server-side objects. close_statement sends a message to the server instructing to deallocate the server-side object. This is an operation that may block and fail, so running it from a destructor is nor adequate.

TL;DR: results memory freeing happens automatically as part of its destructor.

That sounds great, so action needed from the user; just do your queries. Thanks!

Yep, no action needed unless you're preparing statements dynamically, in which case close_statement is needed.
I'm gonna close this issue. Should you have more questions, please feel free to ask!


Documentation: haskell-modules readme

Description of changes
Relative symbolic link to haskell-modules/HACKING.md.
This displays HACKING.md as README.md in the GitHub UI, making it slightly more visible.
There is only one Markdown file in the haskell-modules directory, HACKING.md.
This GitHub feature is documented here: https://stackoverflow.com/a/49981731/1007926
Thanks
Things done
Viewed in GitHub UI:
https://github.com/peterbecich/nixpkgs/tree/9ed2159a0c065ba218a5fd80177f6eec325b8903/pkgs/development/haskell-modules#readme

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

I don't necessarily feel strongly either way, but I think the original argument for not naming it README.md is that we don't want it to be that visible.
The file is mostly for the members of the NixOS/haskell team, not for end users or contributors (who should ideally be able to find all the information they need in the Nixpkgs Manual).


Type guard for workspaceFolders

See #1
https://github.com/zuhanit/epscript-language-server/blob/9389c9593daefbf62be82db3fb5a93fba6830ed0/server/src/analyzer.ts#L41-L72

Not becuase of server, client issue. workspaceFolders can be undefined if no folders open.
https://github.com/zuhanit/epscript-language-server/blob/8b2f36733d97feedebf3884d664ca655399c1a1e/client/src/extension.ts#L66-L72

Fixed in https://github.com/zuhanit/epscript-language-server/commit/af2ac9be020306201dee337c3d1e74d7d8fb7bea. But I don't know how synchronize between server and client when workspace is null, and file is null.

But it runs when file saved(exist).

Fixed in af2ac9b. But I don't know how synchronize between server and client when workspace is null, and file is null.

But it runs when file saved(exist).

Fixed in #9


What are the rate limits?

Are there rate limits on this REST API? If so these should be documented.

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

ID: 35805a0b-697a-884e-0025-2526307bbc96
Version Independent ID: d70061ab-e979-5924-a89d-19de56fe1cb4
Content: Using Azure Blockchain Workbench REST API
Content Source: articles/blockchain/workbench/use-api.md
Service: azure-blockchain
GitHub Login: @PatAltimore
Microsoft Alias: patricka

@brandonh-msft Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

Hi @brandonh-msft,
The REST API endpoint is exposed for each deployment using Azure App Service.  For recommendations on how you can you can scale up to mitigate slow API responses, see https://github.com/Azure-Samples/blockchain/blob/master/blockchain-workbench/faq/performance.md.
Thanks,
Pat

#please-close


Revert "Add participants subtitle to README.md"

Oops, I merged but realized there is a typo in Participants: its says instead partipants

This is a good question. What is considered best practice? In this case it is a very small change that I would have to make to revert the typo, so fixing it with another PR would make sense. But if I would have merged a more complicated PR by error it would be easier to just revert the merge right?

Alright have just noticed the typo too.

Not sure what is considered a good practice. But in pandas, probably half of the PRs I opened had something that had to be changed, and in all the cases we applied the fix in a follow up, and never reverted.
I'd say reverting is only used when you break something, and the fix is not obvious or fast. If we introduce a bug in pandas in a PR, and what to fix requires discussion, or we're even unsure that the PR was a good idea, then we'd revert. Otherwise we just fix the problem and move forward.
Probably worth mentioning that in pandas and open source in general there is a 0 blame policy. We always focus on the solutions, and not on the problem. At least in a personal level, we may discuss about the problem if it's because we don't have enough tests, they're not running properly... So we can also focus on the solution to the root cause of the problem.


chore(deps): bump https://github.com/jenkins-x/jx-cli to 3.0.406

Update jenkins-x/jx-cli to 3.0.406
Command run was ./promote/main

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign abayer
You can assign the PR to them by writing /assign @abayer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rawlingsj
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [rawlingsj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update changeset-release.yml

This pull request includes a small change to the .github/workflows/changeset-release.yml file. The change involves setting up the setupGitUser parameter to false in the changesets job.  This should allow the GitHub action to inherit the user details from the PAT

.github/workflows/changeset-release.yml: Added setupGitUser: false to the changesets job configuration.

Thank you for submitting your Pull Request, the following links will become available for preview shortly:

StudioCMS Landing Page

StudioCMS Documentation

StudioCMS Demo (node-playground) (Also deployed with package changes)

StudioCMS Ui Demo (ui-playground)

Is this inheriting the token from STUDIOCMS_SERVICE_TOKEN?  I am trying to do something similar and the action seems to not be inheriting the user.

Is this inheriting the token from STUDIOCMS_SERVICE_TOKEN? I am trying to do something similar and the action seems to not be inheriting the user.

this is the default action prop.  i just set it to false to ensure it would use the PAT instead of the GITHUB_TOKEN


Desktop toggle requirements btn + unlock semester grid

Summary
This pull request adds a button to the navbar on desktop that allows for toggling the display of the requirements pane as to provide more potential visual space for the semester view.  I just really wanted to see more semesters on my screen lol
The diff also converts SemesterView to CSS grid (from flexbox) for listing the semester cards. The old implementation using flexbox had 2 columns hardcoded in (4 for compact mode). Using grid, we can have variable number of columns. allowing us to take advantage of the extra space with the requirements pane hidden.
Finally, this diff converts the desktop navbar style position from fixed to sticky. A fixed position means that no space is created for the element in the document. The position of requirements bar was implemented with a hacky margin-left: 4.5rem, which is not needed with the sticky positioning, which does create space for the element. This also allows the sidebar to not overlap the semester view when the requirements bar is hidden.
The mobile styling doesn't require changes since it sits on the top of the screen, not the side, where overlapping is acceptable behavior.

[x] add button in navbar to toggle requirements bar
[x] show requirements on page load for desktop, but hide by default on page load for mobile/tablet
[x] convert semesterview card layout from flexbox to css grid
[x] use position: sticky for sidebar (desktop navbar only)

Remaining TODOs:
Currently the icon for the button is just an existing hamburger svg, but we can definitely come up with something better that communicates its purpose more effective.
The button is currently located in the lower end of the nav bar right above the logout button. This location may not be ideal, for example allowing for accidental clicks on the logout button. We may want to relocate this button if that is the case.
Also there is a bug where the button stays blue after being clicked, only returning to gray once you click somewhere else. This is demonstrated in the Toggling GIF. This issue should/will be addressed along with an actual icon.

[ ] finalize location of button in navbar
[ ] finalize button icon
[x] fix button icon focus bug

Test Plan
Toggling (updated design, images below don't reflect this toggle btn change)

Default view on ultrawide (21:9) screen

CSS Grid implementation shows 3 columns in compact mode at 1400px - 13" laptop (referenced in #569)

Notes
If the requirements bar is set to be shown on desktop and the device switches to mobile while on the same page, the requirements page will be shown rather than the semester vue. This is because both desktop/mobile share the same state variable (idk what it's called in Vue) in Dashboard.vue for showing/hiding the requirements bar/page (namely isOpeningRequirements).
If we don't want this behavior we'll just have to separate them into different state variables, though this situation is extremely rare imo
Also this is behind a feature flag, call GK.enableToggleRequirementsBarBtn() in the console to enable.

Bottom bar is not looking so hot :,(

Left nav bar + bottom bar + scroll lockup should all be fixed now


Allow customisation of git tag

Describe Request:
This Orb currently requires the git tag pushed to be e.g. v1.2.3.
At times an Orb will be developed in a repository along side other code.
In those cases demanding a git tag format to be vx.y.z is not sufficient. It would be better to allow a prefix to the tag.
As a result the tag could be circle-orb-v1.2.3 and circle-orb-2-v1.2.3.
As a result one could publish multiple Orbs from one repository as well as a repository in which the current tag is already in use.

Hello @tdeekens
While the git tag could match this pattern, the version of the orb itself could not.
https://circleci.com/docs/orb-concepts#semantic-versioning
Each individual orb can only publish as X.Y.Z and each version is immutable. With this fact, would being able to customize the got tag with a prefix still be preferable if the orb itself can not?

Hi,
thanks for getting back!
Yes, I am aware that each production published Orb is immutable and has to follow regular semantic version.
Even in this case it would still be preferable to prefix the git tag triggering a publish while the released Orb's version omits the prefix.
There are two scenarios I can see this being beneficial:

The Orb living in a repository in which a regular xx.y.z tag scheme is already used by something else
An Orb lives inside a repository with other (often private Orbs) needing to be published in different versions increments

In both cases the prefix would solve the issues one otherwise faces.

Hi all,
I'm facing the same issue as described by @tdeekens, with multiple orbs living in the same repo. imho, the version pattern could still be checked (as it is now) but allowing us to pass the version as parameter would be awesome. You could still default to CIRCLE_TAG anyways.
It would greatly improve the flexibility and wouldn't hurt whoever uses it right now.

Personally, I prefer option (2) because of separation of concerns. If the job is to publish, it shouldn't (imho) care what's your naming convention.

I took the initiative and sent a draft PR with a suggestion to illustrate. Sorry if there's something incorrect - I was aiming just at sharing my way of thinking.

Did you find any workaround @tdeekens ?

No, I didn't. I don't think there is. The only work around I could think of is building my own orb-tools which suits my needs exactly. However, I still think this is a valid use case for the Orb and would help others if it was supported.

Hey all, I think i could be misunderstanding.
@tdeekens the tag is not decided by the orb, it id decided by the config file, are you not able to modify the tag regex string in the deploy job?

@KyleTryon thanks for getting back. Trying to follow along your question. I can configure the git tag RegExp on "my" job triggering orb-tools to publish. Still orb-tools requires then requires the git tag to follow this format. So If I'd configure my job to trigger on say my-orb-name-v1.2.3 to publish via orb-tools then orb-tools would fail the the CIRCLE_TAG doesn't match the required format by orb-tools.

I already opened an issue for a different (but related) issue: #172.
I would like to have the ability to specify a custom development version.
This used to be possible with the old orb version, but isn't anymore. See #172 for the reasoning why.

Alright folks I think I have a possible solution that should satisfy everyone. We will allow users to supply custom regex strings and we will grep out the version from the matched tag strings. I will follow up shortly with a PR


Adina/where command

To test:
The command is /where "user"- it should list the user and the rooms its in. There was a bit of a delay before it popped up in the room itself.

Testing Results:

[x] Testing command with no argument
"/where" -> "Who do you want to locate?"

[x] Testing command with invalid user
"/where RandomUser" -> "Unable to find RandomUser"

[ ] Testing command with my current logged in username
"/where Kevin" -> "Kevin (Currently null) is in the follow rooms: testRoom"

Do we know why the current user is null and why this is printing?

@KSLHacks that's so weird, it's not saying the user's null it's printing whether users active or afk. In Jabbr20 it prints "adinas (Currently Active) is in the following rooms:". If you look at the user isafk value it should be set to false because UpdateActivity() keeps setting it to false.

@KSLHacks Update: So it looks like regardless of what the status is for the user, it's always getting passed in as null by the hub into chat.js. I hardcoded the value as Active for now so something displays for now- but I think this might be a SignalR problem.

Go ahead and create a new issue to track this item with all the details re the failing case above and the force-active coe you had to do. Once you do, merge this and close/delete branch.


Learnings from NNI

As our project is similar to NNI by Microsoft, I thought it might be good to study how they're doing things, compare it how we're doing things, and derive some learnings.
How model's hyperparameter search space is defined

NNI calls a set of knobs "Configuration", the knob config "Search Space"
In NNI, "Search Space" is defined as JSON on separate file
In Rafiki, Knob Config is defined in Python with typed "Knob" classes as part of the model code
My opinion:

Rename "knob config" -> "knob space" for clarity?
More flexible & powerful to configure dynamically with Python
Edits to search space are simpler if written in Python alongside model code in the same file
Submitting a separate configuration file can be more troublesome
Using JSON is more convenient if hyperparameter search space is to be tweaked often, independently of model code

How model developers configure the AutoML algorithm

In NNI, model developers need to configure an "Experiment" in a YAML file

Choice of configuration: which "Tuner" to use, configuration for that chosen tuner, max no. of trials, max training duration, no. of GPUs, platform to train (e.g. local machine, Kubernetes)
A single model is trained for each experiment

In NNI, pointers to datasets are hard-coded in model code, and there's no concept of "task"
In Rafiki, application developers configure a train job by simply submitting a task, a budget, datasets and maybe model IDs in Python

Rafiki matches task to a set of models, and trains these multiple models concurrently
Rafiki manages provisioning of training platform & GPUs
Rafiki automatically selects & configures which advisor to use based on hyperparameter search space

Due to differences between designs of Rafiki and NNI:

In Rafiki, a non-expert application developer initiates training instead of a model developer, so configuring training should be non-technical and, as much as possible, abstract away complexity of model selection & tuning configuration
Rafiki is designed to be more end-to-end, as a ML-as-a-service

My opinion:

As with NNI, should model developers in Rafiki be able to optionally configure how their models are tuned e.g. which advisor to use, configuration of advisor?

Allows model developers to select more appropriate / empirically better AutoML algorithms for their models, but more burden on them
Maybe with another static class method

Current abstraction & definition of budget in Rafiki is appropriate

How the model interfaces with the AutoML system

In NNI, AutoML system calls upon model code by simply running main Python file (i.e. triggers main method). Supports a directory of Python files
In Rafiki, system calls upon model code by importing a given class from a single Python file, then appropriately running methods on instances of that class
In NNI, model code calls upon AutoML system by importing nni module and calling e.g. nni.get_next_parameter() to get hyperparameters for trial, nni.report_final_result(metrics) to pass final metrics of a trial that is interpreted by the tuner
In Rafiki, model code imports utils module and calls e.g. utils.dataset..., utils.logger... for helper/logging methods. Return values to e.g. evaluate(dataset) pass final score back to system
My opinion:

NNI's interface maximises portability of existing model code - no need to rewrite into a class definition like in Rafiki
NNI's interface more loosely couples model code & AutoML system
But Rafiki's well-defined model class gives more flexibility/power to tuning algorithms (e.g. better control flow), and is more appropriate for our design

Unlike NNI, Rafiki needs to support predictions, loading & saving of model parameters

Consider documenting on how to port existing model code to Rafiki, or brainstorm on tweaking API to improve portability?

How the AutoML system configures the model's training behaviour

NNI configures model's training behaviour just through hyperparameters and its framework for early stopping with the concept of an "Assessor"

Model code can optionally call nni.report_intermediate_result(metrics) that is interpreted by the assessor, which kills the trial when the intermediate results are poor
No explicit support and extension for other ways to configure model's training behaviour other than early stopping e.g. loading of shared parameters, using a downscaled model

In Rafiki, we're thinking of configuring a model's training behaviour with PolicyKnob(policy_name) as part of model's knobs, so that model code can switch between different "modes" (e.g. early stop VS don't early stop)

My opinion: this can support more advanced tuning strategies e.g. we can introduce more policies in the future without changing Rafiki's code

How the AutoML system supports architecture tuning

NNI only currently supports GA-based architecture tuning, where the model code & tuner depend on a custom graph abstraction & architecture space definition as the "Search Space"

Which may not be general/flexible enough

As in previous section, NNI won't be able formally support an implementation of ENAS as the tuner needs to tell the model code to load shared parameters and switch between "train for 1 epoch" & "just evaluate on a subset of the validation dataset"

For Rafiki, we're thinking of representing architecture as an array of categorical values

More general (up to model developer to define encoding), but low-level and less "informative" for the architecture tuning algorithm
E.g.

    l0 = KnobValue(0) # Input layer as input connection
    l1 = KnobValue(1) # Layer 1 as input connection
    l2 = KnobValue(2) # Layer 2 as input connection
    ops = [KnobValue('conv3x3'), KnobValue('conv5x5'), KnobValue('avg_pool'), KnobValue('max_pool')]
    arch_knob = ArchKnob([
        [l0], ops, [l0], ops,                   # To form layer 1, choose input 1, op on input 1, input 2, op on input 2, then combine post-op inputs as preferred
        [l0, l1], ops, [l0, l1], ops,           # To form layer 2, ...
        [l0, l1, l2], ops, [l0, l1, l2], ops,   # To form layer 3, ...
    ])

Thanks for the comparison. I list some comments (not in order)

search space. NNI has another way of defining the search space, which uses annotation. It moves the hyper-parameter definition closer to the use place. The python code can run with and without hyper-parameter tuning.
by making NNI a library, it would be easier for local development and debugging. The running flow is controlled by model developers. Rafiki provides a platform for hyper-parameter search. Rafiki controls the flow. Like map-reduce, the system controls the flow and the developers fill in the code of map and reduce.
it would be good to decouple a system into modular components. We will have resource management, filesystem or datastore, hyper-parameter tuning, inference queueing, etc.
we may not be able to unify the architecture tuning algorithms and hyper-parameter tuning algorithms. E.g., it is difficult to even unify ENAS and DART algorithms..
mlflow and kubeflow are two other projects with the hyper-parameter tuning feature.


Backstage - Silent Authentication with webchat

Is it an issue related to Adaptive Cards?
No
Is this an accessibility issue?
No
What version of Web Chat are you using?
Latest production
Which distribution are you using Web Chat from?
Bundle (webchat.js)
Which hosting environment does this issue primarily affect?
Web apps
Which browsers and platforms do the issue happened?
No response
Which area does this issue affect?
Others or unrelated
What is the public URL for the website?
No response
Please describe the bug
Hi Team
I have created an azure bot and integrated a PVA skill (enabled authentication).
I wanted to include this above azure bot using the below components in backstage (web app) (https://backstage.io/)
import {ReactWebChat, createDirectLine, createStore} from 'botframework-webchat';
import {useMsal } from '@azure/msal-react';
import { PublicClientApplication } from "@azure/msal-browser";

Now, after integrating in backstage, once user logs in to backstage (web app), I want to do acquireTokenSilent with the request and ensure user is already logged in to azure bot instead of showing sign in button in azure bot.
This above implementation works fine if the parent web app uses msal implementation of authentication.
But, looks like backstage web app uses Azure OAuth for authentication.
more info
https://backstage.io/docs/auth/microsoft/provider (The Backstage core-plugin-api package comes with a Microsoft authentication provider that can authenticate users using Azure OAuth.)

So, right now if i create a new PublicClientApplication instance and pass the details to method
acquireTokenSilent(requestObj)
This throws below error.
ClientConfigurationError: authority_mismatch: Authority mismatch error. Authority provided in login request or PublicClientApplication config does not match the environment of the provided account. Please use a matching account or make an interactive request to login to this authority.
at ClientConfigurationError.AuthError [as constructor] (AuthError.js:31:1)
at ClientConfigurationError.ClientAuthError [as constructor] (ClientAuthError.js:224:1)
at new ClientConfigurationError (ClientConfigurationError.js:117:1)
at ClientConfigurationError.createAuthorityMismatchError (ClientConfigurationError.js:264:1)
at SilentCacheClient.eval (BaseInteractionClient.js:146:1)
at step (_tslib.js:87:1)
at Object.eval [as next] (_tslib.js:68:1)
at fulfilled (_tslib.js:58:1)
Let me know how we can do acquireTokenSilent method call if the parent webapp is using the azure oauth for user login?
Thank you!
Do you see any errors in console log?
ClientConfigurationError: authority_mismatch: Authority mismatch error. Authority provided in login request or PublicClientApplication config does not match the environment of the provided account. Please use a matching account or make an interactive request to login to this authority.
    at ClientConfigurationError.AuthError [as constructor] (AuthError.js:31:1)
    at ClientConfigurationError.ClientAuthError [as constructor] (ClientAuthError.js:224:1)
    at new ClientConfigurationError (ClientConfigurationError.js:117:1)
    at ClientConfigurationError.createAuthorityMismatchError (ClientConfigurationError.js:264:1)
    at SilentCacheClient.eval (BaseInteractionClient.js:146:1)
    at step (_tslib.js:87:1)
    at Object.eval [as next] (_tslib.js:68:1)
    at fulfilled (_tslib.js:58:1)

How to reproduce the issue?
Follow the steps in the bug description
What do you expect?
how we can do acquireTokenSilent method call if the parent webapp is using the azure oauth for user login?
Is there any other way of acquiring silent token of the bot ?
What actually happened?
Hi Team
I have created an azure bot and integrated a PVA skill (enabled authentication).
I wanted to include this above azure bot using the below components in backstage (web app) (https://backstage.io/)
import {ReactWebChat, createDirectLine, createStore} from 'botframework-webchat';
import {useMsal } from '@azure/msal-react';
import { PublicClientApplication } from "@azure/msal-browser";

Now, after integrating in backstage, once user logs in to backstage (web app), I want to do acquireTokenSilent with the request and ensure user is already logged in to azure bot instead of showing sign in button in azure bot.
This above implementation works fine if the parent web app uses msal implementation of authentication.
But, looks like backstage web app uses Azure OAuth for authentication.
more info
https://backstage.io/docs/auth/microsoft/provider (The Backstage core-plugin-api package comes with a Microsoft authentication provider that can authenticate users using Azure OAuth.)

So, right now if i create a new PublicClientApplication instance and pass the details to method
acquireTokenSilent(requestObj)
This throws below error.
ClientConfigurationError: authority_mismatch: Authority mismatch error. Authority provided in login request or PublicClientApplication config does not match the environment of the provided account. Please use a matching account or make an interactive request to login to this authority.
at ClientConfigurationError.AuthError [as constructor] (AuthError.js:31:1)
at ClientConfigurationError.ClientAuthError [as constructor] (ClientAuthError.js:224:1)
at new ClientConfigurationError (ClientConfigurationError.js:117:1)
at ClientConfigurationError.createAuthorityMismatchError (ClientConfigurationError.js:264:1)
at SilentCacheClient.eval (BaseInteractionClient.js:146:1)
at step (_tslib.js:87:1)
at Object.eval [as next] (_tslib.js:68:1)
at fulfilled (_tslib.js:58:1)
Let me know how we can do acquireTokenSilent method call if the parent webapp is using the azure oauth for user login?
Thank you!
Do you have any screenshots or recordings to repro the issue?
No response
Adaptive Card JSON
No response
Additional context
No response

@stevkan any update on this?

@nkydrwr - Thank you for your patience.
Out of curiosity, as the Web Chat sample 07.advanced-web-chat-apps/e.sso-on-behalf-of-authentication references using msal, does this offer any helpful insights?

@stevkan I want to see if there is a solution for sso (on behalf authentication) if the web app is using azure auth (with no msal implementation)

Unfortunately, no, there is no solution available. The sample linked above, as well as others in the containing folder, are the only SSO solutions we have.
I'll mark this as a feature request for consideration in a future release.


Add ability to create ArgumentCompleters which are dependant on other parameters

Summary of the new feature/enhancement
Add ability to pass PSBuildParameters into the class and script you supply to https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.argumentcompleterattribute?view=powershellsdk-1.1.0
Proposed technical implementation details (optional)
This would allow argument completion where it is not reasonably possible without knowing the value of other options.
The best example I can think of is the Azure VM Image parameters.
Location -> Publisher -> Offer -> SKUs -> Image
My the time you get to Offer, if you don't know Publisher and Location, the list is would take way to long to retrieve.

This already exists for the described scenario