mseccfg/mseccnf clarification (4.6)

Section 4.6 talks about mseccfg and also mseccnf, which is a CSR at address 0x390. can you please clarify:

Are these the same thing?
Is the CSR are 0x390 only present if Zkr is implemented?
Is there any documentation of the remaining bits in mseccnf? I can't find any other details about it.

Thanks.

Hi @JamesKenneyImperas
Yes, this is a typo, it should have read mseccfg.
The mseccfg register is defined / owned by the TEE task group. They let us have a single bit in it because it seemed like a logical place to put the SKES bit. I realise now the spec could do with expanding on what this register is and when it exists. Something like the following:

mseccfg exists if Zkr is implemented, or if any of the "additional functionalities from the TEE group" (I'll describe these better later) are implemented. If Zkr is not implemented, the SKES bit must be hardwired to zero. If Zkr is implemented and "the TEE functionality" is not implemented, all bits other than SKES must be hardwired to zero, or otherwise set according to the TEE specifications for a not implemented feature.

Would this have answered your above question? Baring exactly what the other bits do?
Cheers,
Ben

Hi Ben,
Yes, that would have helped. Thanks!

Great, I'll add that in for the next release.

We switched mseccfg address to 0x747 as requested by Opcode and Consistency review.


Django 1.7 : ImportError cannot import name get_verbose_name

rollyourown/seo/options.py", line 4, in
from django.db.models.options import get_verbose_name
this error is occurred due to some changes in django 1.7
get_verbose_name function is changed from db.models.options.get_verbose_name to utils.text.camel_case_to_spaces
Solution
comment this line
from django.db.models.options import get_verbose_name
Add this line
from django.utils.text import camel_case_to_spaces as get_verbose_name

Thanks


Creating a new map with an URL that retrieves more than one file should add all layers to the map and not to different maps

Like an osm export

uhmm, this is a non-trivial change, the whole platform works by adding stuff as tables, not layers inside a single table. Are we sure we want to attack this? /cc @javisantana
BTW, OSM imports also create multiple tables:

Is a map, with the tables. Not layers in a table
On Jul 20, 2015 9:09 AM, "Kartones"<EMAIL_ADDRESS>wrote:

uhmm, this is a non-trivial change, the whole platform works by adding
stuff as tables, not layers inside a single table. Are we sure we want to
attack this? /cc @javisantana https://github.com/javisantana
BTW, OSM imports also create multiple tables:
[image: image]
https://cloud.githubusercontent.com/assets/2085449/8771227/eaad6c72-2ebe-11e5-972b-4b916779b6e0.png
—
Reply to this email directly or view it on GitHub
https://github.com/CartoDB/cartodb/issues/4556#issuecomment-122783041.

this needs to be designed internally, not an easy change

If is only for the map I can reuse stuff I've done for Instagram import (the "after import decorator") but it requires a few changes, is still not trivial.
For example we're currently not creating a map if import generates N tables (and I think this logic is handled frontend-side). Also only doing this on url-based imports but not the rest (e.g. why not ArcGIS? Why not an OSM or KML import?) is going to be weird, no?
Can be done as a "test", but if we then left applying this to other sources/formats until later it will behave differently depending on the import source.
Anyway, I'm glad to improve the Importer, just warning that is a quick change so we all have it into account and plan accordingly

No quick changes, we need a clear strategy here on what the importer creates (tables, layers and styles) based on imported files. This is a full feature and needs a wiki page
Think that with pecan we already started to analyze datasets to create wizards that match the dataset, that should be part of the import process.

Yep, no problem on creating a wiki page.


Error in vercel deploy: TypeError: Cannot read properties of undefined (reading 'v2_meta')

What version of Remix are you using?
1.6.7
Steps to Reproduce
clone repository by ssh: git clone git@github.com:Lucas-Eduardo-Goncalves/pac.app.git
then add this repository to vercel, and try.
Expected Behavior
My site should work normally. On localhost I can't find it works normally.
Actual Behavior
I find the error message: TypeError: Cannot read properties of undefined (reading 'v2_meta')

Same error for me in 1.8.0. Wasn't a case with 1.7.2

Can you both provide a gist of you package.lock file?

Can you add future: {} in your remix.config.js and see if the issue goes away?

Had the same problem but adding future: {} solved the problem

@machour Adding future doesn't fix, also broken in local for me

Seem you are missing edit the remix config while you want to deploy to Vercel.
In remix.config.js
/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
  serverBuildTarget: "vercel",
  // When running locally in development mode, we use the built in remix
  // server. This does not understand the vercel lambda module format,
  // so we default back to the standard build output.
  server: process.env.NODE_ENV === "development" ? undefined : "./server.js",
  ignoredRouteFiles: ["**/.*"],
  // appDirectory: "app",
  // assetsBuildDirectory: "public/build",
  // serverBuildPath: "api/index.js",
  // publicPath: "/build/",
};

Create new server.js file at your root folder (the same level of remix.config.js)
import { createRequestHandler } from "@remix-run/vercel";
import * as build from "@remix-run/dev/server-build";

export default createRequestHandler({ build, mode: process.env.NODE_ENV });

Having the same problem, but adding future: {} does not solve the issue. I already have a server.js file as described by @ThanhPhat1080.

@sjwinther are all your remix deps on 1.8.0? Can you share a gist of your package.json depedencies & devDependencies sections?

@machour Yup! Here you go: https://gist.github.com/sjwinther/643603e3c40273614f05855ff2ce90db

@sjwinther just to confirm, you're seeing Cannot read properties of undefined (reading 'v2_meta') even tho you added future: {} to your remix.config.js file? (Please update the gist with its contents 🙏)

Looks like I got it resolved now, although it was pretty difficult to figure out from the error. I was returning { rel: "icon", href: "/favicon.png", type: "image/png" } in one of the Link functions and for some reason Remix didn't like that? I was getting this error as well, which was also resolved when I removed the favicon.png link:
{
  data: 'No route matches URL "/favicon.ico"',
  status: 404,
  statusText: 'Not Found'
}
No routes matched location "/favicon.ico"

Seem you are missing edit the remix config while you want to deploy to Vercel. In remix.config.js
/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
  serverBuildTarget: "vercel",
  // When running locally in development mode, we use the built in remix
  // server. This does not understand the vercel lambda module format,
  // so we default back to the standard build output.
  server: process.env.NODE_ENV === "development" ? undefined : "./server.js",
  ignoredRouteFiles: ["**/.*"],
  // appDirectory: "app",
  // assetsBuildDirectory: "public/build",
  // serverBuildPath: "api/index.js",
  // publicPath: "/build/",
};

Create new server.js file at your root folder (the same level of remix.config.js)
import { createRequestHandler } from "@remix-run/vercel";
import * as build from "@remix-run/dev/server-build";

export default createRequestHandler({ build, mode: process.env.NODE_ENV });

This solution worked for me, in addition to adding the property future: {}. Besides I have installed @remix-run/vercel and @vercel/node according to @sjwinther 's gist.

I'm also running into this issue with
		"@remix-run/node": "^1.7.2",
		"@remix-run/react": "^1.7.2",
		"@remix-run/serve": "^1.7.2",

Fixed it by ensuring every remix package was up to date:
		"@remix-run/node": "^1.8.0",
		"@remix-run/react": "^1.8.0",
		"@remix-run/serve": "^1.8.0",
		"@remix-run/dev": "^1.8.0",
		"@remix-run/eslint-config": "^1.8.0",

AND including future in remix.config.js

I was able to figure out the answer, to make it work I updated the packages to version 1.8.0 and also added the @remix/vercel package.

Closing in favor of https://github.com/vercel/vercel/issues/9010

AFAICT this should only be an issue if @remix/vercel is not explicitly installed. Adding future: {} to your config shouldn't make a difference if you do (and if it does cause an issue, it may be duplicate copies of the dev or server-runtime packages installed as a side effect of Vercel automatically installing the outdated version.

I should mention this error happened to me in the self hosted version, but not all remix dependencies were up to date so it makes sense

I had the issue locally too (in prod I use fly.io)

We have reported the issue to vercel and provided a fix for it there.
If you have an unrelated problem, please create a new issue.


hooks should be deleted in reversed order

Scenario:

pre-install helm hook as job needs additional configmap
configmap is not part of release, it is only needed by hook
configmap is also marked as hook, and assigned lower hook-weight so that it is installed before the job needs it
both job and configmap are marked for deletion on hook-succeeded
job completes succesfully
helm deletes both configmap and job in the same order as it executed them

Configmap is deleted while the job that needs it still exists (although the "need" is only declarative since job is already completed).
This produces FailedMount warnings in k8s events.
Output of helm version:
version.BuildInfo{Version:"v3.10.0", GitCommit:"ce66412a723e4d89555dc67217607c6579ffcb21", GitTreeState:"clean", GoVersion:"go1.18.6"}

Makes sense to me.

This is still an issue.

not stale

still relevant

Still relevant.

Not stale.

This is even more important as we can't use helm test with a pod (with restartPolicy: never) and a pvc now  which requires the pod to get deleted releasing the volume claim before the pvc can be cleaned up.
#11387 introduced the timeout that now waits for our PVC to get removed before cleaning up the completed POD.#12758

not stale

The proposal makes a lot of sense to me since I had to set hooks as "helm.sh/hook-delete-policy": before-hook-creation #,hook-succeeded (commented hook-succeeded) because a ConfigMap/Secret used by a hook was deleted before a Job/Pod hook was executed.
A complementary idea would be a new annotation (e.g. "helm.sh/hook-delete-group") to allow grouping hooks working as a whole.

not stale


Client Allocation Request for: asd

Client Allocation Questions
Core Information

Name: asd
Website / Social Media: asd, (asd, asd)
Region: Africa
DataCap Requested: 224 GiB
Addresses to be Notarized: asd
Notary Requested: Irene Young

This user’s identity has been verified through filplus.storage


Trim repo to only include stac-fastapi.pgstac package code

Updates the repo to only include code for the stac-fastapi.pgstac backend.
This PR tries to keep the number of changes to a minimum and focus on creating a working stac-fastapi.pgstac package. Other changes related to code cleanup, testing, etc. can be tackled in future PRs.
Notable Changes:

[x] Move setup.py and setup.cfg files to the project root
[x] Move stac-fastapi.pgstac source code from stac_fastapi/pgstac/stac_fastapi/pgstac to stac_fastapi/pgstac.
[x] Pin stac-fastapi.* dependencies to GitHub commits
This was necessary because there are changes to stac-fastapi.types that are not part of the most recent release. Going forward, we can pin these dependencies to specific releases.
[x] Add test dependencies that were previously installed into the Docker image as part of another stac-fastapi.* package.
[x] Update Makefile targets and Docker Compose services
This also included renaming some of the targets and services to remove the -pgstac suffix. This wasn't strictly necessary to get things to run, but those suffixes no longer seemed necessary
[x] Update GitHub Actions
[x] Update scripts/publish
[ ] Update docs to be specific to stac-fastapi.pgstac
[ ] Update main README to be specific to stac-fastapi.pgstac

PR Checklist:

[x] Code is formatted and linted (run pre-commit run --all-files)
[x] Tests pass (run make test)
[ ] Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
[ ] Changes are added to the CHANGELOG.

[ ] Changes are added to the CHANGELOG.

@geospatial-jeff Do you have a preference for how we handle transitioning the CHANGELOG? Since the versioning of this package is going to continue from the existing version (v2.3.0) my thought was that we should:

Preserve the current CHANGELOG
This should include the upcoming v2.4.0 release prior to officially breaking apart the repo, which means I'll probably need to rebase onto stac-fastapi@master again to include that.
Immediately release v2.5.0
This will allows us to pin this package to stac-fastapi>=v2.4.0 and remove the GitHub dependencies mentioned in the description. It will also let people know that versioning of this package may begin to diverge from the other stac-fastapi.* packages.
Proceed with normal version updates after that.

Do you have a preference for how we handle transitioning the CHANGELOG?

I don't have a strong preference.  One of the biggest upsides IMO of splitting backends out of stac-fastapi is those backends can be versioned/released separately.  I agree that historical changes from the existing CHANGELOG should be preserved but outside of that requirement I don't have a strong preference.
Immediately releasing v2.5.0 makes sense to me but I think we may want to hide behind an alpha/beta release until everything is finalized.

@duckontheweb Can you please post the github commands you ran to maintain history?  I'd like to use the same commands for the sqlalchemy backend.

@duckontheweb Can you please post the github commands you ran to maintain history? I'd like to use the same commands for the sqlalchemy backend.

Sure thing.
$ mkdir stac-fastapi-pgstac
$ cd stac-fastapi-pgstac
$ git init
$ git remote add stac-fastapi https://github.com/stac-utils/stac-fastapi.git
$ git fetch
$ git reset --hard stac-fastapi/master
$ git remote remove stac-fastapi
$ git remote add origin https://github.com/stac-utils/stac-fastapi-pgstac.git
$ git push --set-upstream origin main --force

Update docs to be specific to stac-fastapi.pgstac

@geospatial-jeff I ended up simplifying the API section of the mkdocs.yml config to just point to the index.md file for each of the following sub-packages:

stac_fastapi.pgstac
stac_fastapi.api
stac_fastapi.types
stac_fastapi.extensions

Since those index pages provide their own links to the individual module pages we can still navigate to all of the auto-documented API code, but without having to constantly update the list of pages in the config. Part of the reasoning for this, was that I noticed that there were still nav links to stac_fastapi.server, which no longer exists. I don't know if this is what we want as a permanent solution, but this seems like a good starting point and maybe we can open issue to revamp the docs more thoroughly.

Opened stac-utils/stac-fastapi#450 to remove the backend packages from that repo. We should wait for that PR to be merged and released, then update this PR to install the core packages from the new release.

Closing as OBE (https://github.com/stac-utils/stac-fastapi/discussions/517).


[1.12] Bump Mesos to nightly 1.7.x 40ea2b5

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Changelog:
https://github.com/apache/mesos/compare/4a2949cb075ab02086fd9e3065bcab83855bf9cc...40ea2b571b62dc90bacb80b4977b30da6c73a48f

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review


where can I find demoVideo part in cityscapes？

https://www.cityscapes-dataset.com/downloads/
I believe you should be looking at leftImg8bit_demoVideo.zip (6.6GB) file.


Cypress timeouts and waiting functions revision for basic functionalities

Replace the wait functions after search with xhr requests timeouts (wait for xhr request to finish and then move onto the next phase). (Research how this can be implemented so we can bring down the wait functions to zero)

Done:
https://github.com/cortezaproject/corteza-e2e-cypress/commit/1449eb5d69410d64c530a28f8f07f9a040d5b261
https://github.com/cortezaproject/corteza-e2e-cypress/commit/3d01f946d9d4e9cfc0138b5fa2b97a423c0ed701


profiling notices in Xcode7

Installed the plugin through Alcatraz
I'm running Xcode7 beta 4
And when I'm building any project (through either xcode, xctool or xcodebuild) I get a bunch of these messages:
profiling: /Users/xxx/Library/Developer/Xcode/DerivedData/MHImportBuster-esjnphrkxbkayucmuszdhqdopppi/Build/Intermediates/MHImportBuster.build/Debug/MHImportBuster.build/Objects-normal/x86_64/MHHeaderCache.gcda: cannot merge previous GCDA file: corrupt arc tag (0x00000004)
profiling: /Users/xxx/Library/Developer/Xcode/DerivedData/MHImportBuster-esjnphrkxbkayucmuszdhqdopppi/Build/Intermediates/MHImportBuster.build/Debug/MHImportBuster.build/Objects-normal/x86_64/NSMutableIndexSet+NSArray.gcda: cannot merge previous run count: corrupt object tag (0x01000000)

Only disabling the plugin would resolve it

Hey @basvankuijck thanks for reporting... I'll take a look if same thing happens on my mac.

Thanks!
They're just simple notices, so the build still succeeds. But my terminal is cluttered with these lines.
Sidenote: Thanks for plugin contribution, it really saves me a lot af scrolling ;)

Thanks man appreciate it :) I'll look into it anyway, it sounds like a nuisance.

I've fixed this issue by ignoring .gcda and .gcno files.
https://github.com/ClementPadovani/Peckham/commit/35d26b77e08b84a0480d8813e22f49191539dcd4

@markohlebar You can now close this issue.

@ClementPadovani cheers!


Lucene Source Operator Implementation

@chenlica @jesmaelnezhad @JavierJia .. Please review the code related to lucene source operator implementation.
Thanks,
Sandeep

By mistake I created this branch(luceneSrcOp) taking "lucenedemo" branch as the base, instead of "master" branch. Merging this pull request into master will also merge lucenedemo branch into master. But, I hope it is ok, since lucene demo code is in textdb-sandbox project.

It should be OK.  Let's have a F2F discussion about this pull request.  I will send a separate email.

Just took a glance at it. Looks good. Could you reformat the code before submit? Otherwise, it seems every line get updated.

Per our discussion, it may be better to decline this PR and create two separate PRs, one for the Scan operator, and one for the Lucene Hotel example.

Created another pull request which has the changes related to this pull request..

Please delete this branch.


feat: add tricky-challenges tool

Checklist:

[X] I have read freeCodeCamp's contribution guidelines.
[X] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Now that we have a standardised format for the titles in "Ask for Help" generated forum posts...
I threw together a quick tool that grabs the last 100 topics from our forum, checks if they look like an "Ask for Help" post, and counts the number of topics each block-step pair has.
This should allow us to identify which particular challenges our campers are getting stuck on, which tells us that a challenge might need to be rewritten or broken down.

Example output
[
  [ 'Learn HTML by Building a Cat Photo App-Step 12', 8 ],
  [ 'Learn HTML by Building a Cat Photo App-Step 6', 5 ],
  [ 'Learn HTML Forms by Building a Registration Form-Step 15', 3 ],
  [ 'Learn HTML by Building a Cat Photo App-Step 4', 3 ],
  [ 'Tribute Page-Build a Tribute Page', 2 ],
  [
    'Learn CSS Colors by Building a Set of Colored Markers-Step 49',
    2
  ],
  [ 'Learn HTML by Building a Cat Photo App-Step 13', 2 ],
  [ 'Learn HTML by Building a Cat Photo App-Step 14', 2 ],
  [
    'Technical Documentation Page-Build a Technical Documentation Page',
    2
  ],
  [ 'Learn HTML by Building a Cat Photo App-Step 46', 2 ],
  [ 'Learn HTML by Building a Cat Photo App-Step 2', 1 ],
  [
    'Learn Intermediate CSS by Building a Picasso Painting-Step 59',
    1
  ],
  [
    'Learn CSS Colors by Building a Set of Colored Markers-Step 78',
    1
  ],
  [ 'Learn CSS Transforms by Building a Penguin-Step 63', 1 ],
  [ 'Learn HTML by Building a Cat Photo App-Step 68 Help', 1 ],
  [ 'Learn CSS Grid by Building a Magazine-Step 21', 1 ],
  [
    'Basic Node and Express-Implement a Root-Level Request Logger Middleware',
    1
  ],
  [ 'Learn HTML by Building a Cat Photo App-Step 60', 1 ],
  [ 'Learn HTML Forms by Building a Registration Form-Step 36', 1 ],
  [ 'Learn HTML Forms by Building a Registration Form-Step 30', 1 ],
  [ 'Learn Accessibility by Building a Quiz-Step 43', 1 ],
  [ 'Learn Basic CSS by Building a Cafe Menu-Step 34', 1 ],
  [ 'Basic JavaScript-Record Collection', 1 ],
  [ 'Learn Basic CSS by Building a Cafe Menu-Step 13', 1 ],
  [ 'Learn Typography by Building a Nutrition Label-Step 61', 1 ],
  [ 'Basic JavaScript-Testing Objects for Properties', 1 ],
  [ 'Learn HTML by Building a Cat Photo App-Step 63', 1 ]
]

I pushed an update to this. Now you can run npm start with a posts= and block= parameter to specify the results you want to see.

@naomi-lgbt I do not have privileges to merge this PR.


[BUG] When using the warhammer theme, short notes are too small for the text

Describe the bug
The text of short notes is hard to read when using the warhammer fantasy theme.

To Reproduce
Steps to reproduce the behavior:

Use the Warhammer theme.
Create a new note and write a short phrase.
Save and close the editor.
Open the note to read it (via the calendar).
See error

Foundry Information

Foundry Version: [v10]
Game System: [Warhammer fantasy 4e]
Simple Calendar Version: [eg 2.1.27]
Simple Calendar Configuration: Warhammer fantasy theme

Browser (please complete the following information):

Foundry.

Thanks for this mod. We use it a lot :)

This issue should be fixed in version 2.1.40 of Simple Calendar


Contract Apps: errors handling

We need to add at least some minimal errors handling & displaying for all apps. Add at least div wit the red text & reconnect after 10 seconds. For now for example if you try to run contract apps on master you would get the following:

App is unable to check the contract id (empty cid list is returned) and it just silently dies.
This is not the only case. When app is loaded and something bad happens need to display error div as well.

Make  text in the center, and change "id" to " cid" for Vault

Please also check that errors are correctly handled when tx_send + small fee/not enough BEAM is handled (and errors from other requests)

checked


[Feature] Test sample RayCluster YAMLs to catch invalid or out of date ones

Why are these changes needed?
Use #605 to test sample RayCluster YAMLs. This PR found:

Invalid YAML: #675
Outdated YAML: ray-cluster.getting-started.yaml
Bug: #679

Related issue number
Closes #642

Checks

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

[x] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

cd tests/framework
python3 test_sample_raycluster_yamls.py 2>&1 | tee log

Will lgtm once you get the new test to pass consistently.

@DmitriGekhtman There are 4 tests hit the CPU constraint ("a standard Linux runner has 2-core CPU (x86_64), 7GB of RAM, and 14GB of SSD space.") of GitHub Actions as we discussed in the Design: KubeRay E2E Configuration tests.
I used os.system(f'kubectl describe pods -n={self.namespace}') to gather more information when RayClusterAddCREvent fails to converge. You can search "Insufficient cpu" in CI result.
Events:
  Type     Reason            Age               From               Message
  ----     ------            ----              ----               -------
  Warning  FailedScheduling  8s (x3 over 92s)  default-scheduler  0/1 nodes are available: 1 Insufficient cpu.

Ok, it seems that to automate test execution, we will have to run these tests in the Ray CI.
Here's a proposed sequence of actions.
For this PR, make sure the tests are passing manually when you run them.
After merging this PR, the main priority is manual release testing:
The Ray 2.1.0 release is in progress and a more-or-less final rayproject/ray:2.1.0 image is available.
Run the tests with the 2.1.0 images manually and make sure they pass.
(It is possible that some minor commits will be picked in and the image will be modified before release... just ignore that for now. Or if you like repeat the tests when the Ray team is approaching the final 2.1.0 release -- should be within the next few days; you can check the relevant Anyscale-internal slack channel for details.)
Prior to the KubeRay 0.4.0 release, run the tests manually again with a KubeRay 0.4.0 candidate and Ray 2.1.0.
The next priority is establishing automated pipelines for running these tests in the Ray CI. It's important to track this and do it eventually, but it's fine if we don't put a deadline on it right now.

If there's a way to fit some subset of the test into CI, perhaps with modifications to the configs, that would also be good.

If there's a way to fit some subset of the test into CI, perhaps with modifications to the configs, that would also be good.

This PR runs 3 tests on KubeRay CI, and I will open issue #695 to track the progress of running tests on Ray CI.
Although each standard Linux runner has 2 cores, I always failed to schedule Pods when CPU usage is higher than 800m (0.8 CPU). Maybe there are some CPU fragmentation problems.

Thanks, just wondering if this would've caught the bug fixed by https://github.com/ray-project/kuberay/pull/501?

Probably not in its current form, but it wouldn't be too hard to extend the framework to validate log volume mounts.


Target .NET Standard 2.0

Part of aspnet/Home#2045.

⌚ on https://github.com/aspnet/EventNotification/pull/70 to go through first.


kick++ Technique.

Can someone please explain what led to the use of this seeming hack? I am finding the data binding in Polymer quite frustrating when it seems things like this are necessary. Even using the proper Polymer array mutation methods don't seem to actually fire the correct events.

I had problems getting the data binding in polymer to work well with lists, in particular when you have computed properties that depend on a list property. Using the polymer array mutation didn't seem to trigger the computed properties to be recomputed. By making the computed property also depend on the primitive-valued kick property and bumping its value, I could get the computed properties to update. It is indeed a hack to get around problems in the data binding implementation. I don't know the best way to fix this; it's possible that computed properties work right in newer versions of polymer and the hack can just be removed. It's also possible that this could be restructured to not rely on computed properties to pass info to the template and then again this hack would not be necessary. And finally, we might be able to ditch polymer templates and use something like react which doesn't use data binding but instead relies on explicit rerendering. I'd be open to any of these.

We can close this now, right?

I left it open because I wanted to write some brief documentation on how the data binding works, but who knows when I'll get around to it. For now I'll just link to the relevant docs I found, and we'll close this up.
https://www.polymer-project.org/1.0/docs/devguide/data-binding#array-binding


[master] Upgrade to latest dependencies

Cron. -knative-prow-robot
/cc knative/serving-writers knative/eventing-writers
/assign knative/serving-writers knative/eventing-writers
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/hack 4ed1ecb...4422dca:
  > 4422dca Set GOBIN in codegen-library.sh (# 44)
  > d946d25 Revert "Add hermetic go mod aware handling to run_go_tool (# 38)" (# 39)
  > ea9c9a0 Add hermetic go mod aware handling to run_go_tool (# 38)

/retest
/lgtm
/approve

/retest
/lgtm
/approve


Fixed model cleanup after training in low_memory mode

Issue #, if available:
Could be related to https://github.com/awslabs/autogluon/issues/168
Description of changes:
Models are not cleaned up after training in low-memory mode because models collection holds reference to the object.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Great defect find and fix! This defect appears to primarily impact non-bagging setting, but can also have a fairly massive impact on large multiclass classification datasets due to the large OOF predictions being held in the stacker/bag ensemble models that are still present in memory. This should help with OOM errors substantially!

Merging as changes do not impact the CI failure.


Support ng-packagr

It would be great if this package also augmented ngPackagr when it became available

https://github.com/ng-packagr/ng-packagr/issues/1471

Hi,
I tried to customize colors, but it doesnt work
`const colors = require("./node_modules/tailwindcss/colors");
module.exports = {
purge: [
"./src//*.html",
"./src//.ts",
"./src/**/.css",
"./src/**/*.scss",
],
darkMode: false, // or 'media' or 'class'
theme: {
extend: {
teal: colors.teal,
orange: colors.orange,
},
},
variants: {
extend: {},
},
plugins: [
require("@tailwindcss/aspect-ratio"),
require("@tailwindcss/forms"),
require("@tailwindcss/line-clamp"),
require("@tailwindcss/typography"),
],
};
`
VSCode complanes on all requre stataments:
Could not find a declaration file for module '@tailwindcss/aspect-ratio'. <EMAIL_ADDRESS>implicitly has an 'any' type.   Try npm i --save-dev @types/tailwindcss__aspect-ratioif it exists or add a new declaration (.d.ts) file containingdeclare module '@tailwindcss/aspect-ratio';ts(7016)
Please help.
regards
Laura


Allow outputing enums as string values

Hi,
I'm looking at this as an option to output our DTOs and service models to typescript, and one thing I've noticed is that enums are rendered as integers.
I've spiked an option to output as strings, with a simple test.
Would this be a valid contribution? Or is there another way to acomplish this?
I'm hardcoding "" instead of '', not sure if that's valid.
Thanks

Also, added support for IEnumerable<> and IDictionary<,>, which map to Array and Record

Thanks for the great contribution 💯

Published 1.3.13 to NuGet.


config: Deprecate build.spec.additionalTrustedCA

AdditionalTrustedCAs referenced in build.config.openshift.io/cluster were never used in OpenShift 4.1.
Mark existing field as deprecated and schedule for future removal.

/assign @bparees
fyi @bmcelvee @openshift/openshift-team-developer-experience

/close
Deprecated in #406


spacy.en.English() gets hanged

Hi! Congratulations on the awesome work! :)
I am trying to run spacy using spacy.en.English(). But it gets stuck there. Does not move forward. I am using ubuntu 15. Please help me out.

Hmm. Two thoughts:

How much memory do you have available? It needs up to 4gb
How long did you wait? It needs 1-2 minutes to load

Oh okay! memory is not an issue. It takes around 2-3 minutes. I guess its okay then. But still, any suggestions on making it run quicker?

I'm working on a neural network model that should take much less memory.
You can do set the parser=False flag, to avoid loading the parser model. This will make it load much faster, but doesn't let you use a lot of the functionality.

@honnibal how much less memory are we talking? Currently the model takes around 1.1 GB of memory on my end, which makes it impossible to host on a small cloud worker, but if it can be reduced along with the load time, that would really be awesome.
Any ETA on when the neural network model hits a release?

I've been doing nothing else for about 4 or 5 weeks now, which is why I've been a bit quiet :). I thought I'd get this done much quicker, but I took a detour to understand the latest papers.
I've got the NN implemented and it's passing basic tests, and doing what it should on binary text classification. I'm currently doing the POS tagging experiments. There seem to be some bugs in this part. I hope to have the tagger performing decently tonight, and maybe the parser doing useful things by the end of the week.
It's hard to say, though. Maybe there'll be some hold-ups. I'd be surprised if the NN model requires more than 500mb of memory. I think we might even be able to get it under 200mb.

It's all custom. Current messy state here: https://github.com/honnibal/thinc/blob/tmp_nn2/thinc/nn.pxd
The batch normalization stuff isn't working yet, and there's a fair bit of code duplication while I've been playing around. I expect the version that gets linked to spaCy in the end will be about 500 lines. Everything's implemented as a staticmethod, because I liked namespacing them that way. They then become inlined to work around a limitation in Cython that I really should report.
So, why not Theano/Tensor Flow/Caffe etc? It's not just NIH, I promise :). There are a few things about our problem that make these libraries a poor fit.
The main difference is that the parser can't batch up problems and send them to a library. The parser is a push-down automaton, and the model has to determine which action to take next. The the parser has to get that action, and perform it. Then we can extract features from the state and advance. The loop looks like this:
state = ParseState(sentence, tags)
while not state.is_final():
    valid_actions = transition_system.check_valid(state)
    features = extract_features(state)
    scores = model.predict(features)
    action = arg_max_if_true(scores, is_valid)
    transition_system.apply(action, state)

The other consideration is that I really don't want to give up my hash tables. NLP problems are very sparse, so modelling everything as a dense matrix doesn't work so well.
So, I wanted to achieve the following:

The ML functions must not require the GIL. This way, we can finally properly multi-thread spaCy.
No system dependencies, e.g. depending on Eigen, Boost, Caffe etc is unacceptable. We're really serious about making spaCy's installation bullet-proof (next release is a massive advance on that). We can't achieve that if we rely on system libraries.
 During training, it should just grow the hash table.
I want to be able to define group L1 penalties flexibly, to e.g. prefer models that don't fine-tune many word embeddings. This will allow us to re-use the same embeddings between tasks.
I want to be able to look over the code and understand it. We don't need so many abstractions, because we don't need to create some sort of "pluggable architecture". We can grow out the abstractions in time if we want. But for now the best way to ensure future changes can be integrated easily is to keep the code short and direct. If the library is <1,000 lines, integrating the next paper to be released can't be much work.

Note that I'm making a conscious trade-off here: at this point I'm not looking to support any other users of this code, other than spaCy, with this library. That buys a lot of freedom.

@honnibal Thanks for your response and appreciate the time that you put into responding to my question.
I plan to look into your implementation of hash tables and the current nn file above you highlighted.


allow [$:] as prefix and plain ? for prepared statements

This allows handling of the $-prefix (postgresql and sequelize bind), :-previx (PHP PDO and sequelize replace) and single ? (most DBS for prepared steatement.
But this PR allows this placeholder on more positions than the underlaying databases, so its for people who need preapared-statement support and know what they do. I am not shure if this should go into master. Anyway it works for me and is out for now.
By the way some trailing whitespace are stripped, so use git diff -w

hi @oger000 , thanks for the pr and sorry for the late reply.
There are two things need to be discussed:

need support ? and ?? follows: https://github.com/mysqljs/mysql and https://github.com/go-sql-driver/mysql
i think placeholder should not be a Identifier in AST, or at least have a flag to label it out.


update "applies to" section

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8006

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @e0i, for your information
Thank you


Update citation

Update the citation on the readme to reference the final paper instead of the preprint.

It looks as if the link has remained the same when referencing the final paper, so I just removed the preprint text.


ORT analyzer keeps scanning node_modules files

I am trying to run a scan against the Ant Design framework, but running into a couple issues.
The analyzer says it will only exclude the .git file even though node_modules is hard-coded to be ignored in the Package.kt file and even though the .ort.yml file in the ant-design repo is configured to exclude it.

The analyzer looks to be parsing files in the node_modules folder and in the end results in an error because of packages that share the same id:

The analyzer looks to be parsing files in the node_modules folder

That expected. Any existing / committed node_modules directory is "ignored" / temporarily stashed away, but just to recreate a node_modules directory (implicitly, by running npm install) whose contents are then parsed. This is to ensure the node_modules contents are always up to date.
Also, excluding paths does not mean they don't get analyzer. By default they will only show up marked as excluded in reports. If you really want to skip / ignore excluded paths, you need to pass -P ort.analyzer.skipExcluded=true to the analyzer.

in the end results in an error because of packages that share the same id:

Yes, that's a know issue with some projects, and https://github.com/oss-review-toolkit/ort/pull/6533 proposes a solution (but needs more work).


Added Linked List [Python]

Fixes #374
By submitting this pull request I confirm I've read and complied with the below declarations.

[x] I have read the Contribution guidelines and I am confident that my PR reflects them.
[x] I have followed the coding guidelines for this project.
[x] My code follows the skeleton code structure.
[x] This pull request has a descriptive title. For example, Added {Algorithm/DS name} [{Language}], not Update README.md or Added new code.
[x] This pull request will be closed if I fail to update it even once in a continuous time span of 7 days.

@Monal5031 Review.

@Monal5031 Changes are done take a look


Reorganize ingest_metadata field

This work needs to be done In conjunction with the work in Entity API #748
The Dataset.ingest_metadata field will be reorganized to accommodate:

Easier access to metadata for searching
Adding fields to accommodate the Workflow Tracking effort
Adding the Dataset.calculated_metadata field to allow storage of calculated/derived metadata

This work is specified in the ingest_metadata field reorganization document
From the above document a summary of the changes that need to be made are:

MOVE:

Dataset.metadata.metadata → Dataset.metadata
Dataset.metadata.files → Dataset.files

RENAME (Elasticsearch/Search API only):

Dataset.metadata → Dataset.ingest_metadata (Elasticsearch/Search API only)

DELETE:

Dataset.metadata.thumbnail_file_abs_path
Dataset.metadata.extra_metadata

ADD:

Dataset.ingest_metadata.workflow_description (as String/Text)
Dataset.ingest_metadata.workflow_version (as String/Text)
Dataset.calculated_metadata (as JSON text)

@kburke The Harvard team noted that they'll also need to update some of the mapped fields during portal index translation. So once you have the changes ready, I'll ask them to take care the portal pieces under https://github.com/hubmapconsortium/search-api/tree/main/src/hubmap_translation/addl_index_transformations/portal


feat: implement rules config field

This implements the top level rules configuration field. It lets you specify transport rules for non-js modules. For example, you can specify *.md files to be included as a text file with -
[[rules]]
{type = "Text", globs = ["**/*.md"]}

We also include a default ruleset -
  { type: "Text", globs: ["**/*.txt", "**/*.html", "**/*.pem"] },
  { type: "Data", globs: ["**/*.bin"] },
  { type: "CompiledWasm", globs: ["**/*.wasm"] },

More info at https://developers.cloudflare.com/workers/cli-wrangler/configuration/#build.
Known issues -

non-wasm module types do not work in --local mode
Data type does not work in service worker format, in either mode

Why didn't the changeset bot drop a comment here? 🤔 I'll investigate later, unless someone else has an idea


Class blade.compiler does not exist

Hi,
when using command : "composer update", the package causes the following error :
> php artisan clear-compiled

  [ReflectionException]
  Class blade.compiler does not exist

Ok. Just saw the "pull request" to solve this issue.


fix: ISSUE-6 - allow to not setting the keys of a table

Codecov Report

Merging #7 (e7fadb8) into main (d9914df) will not change coverage.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##                main        #7   +/-   ##
===========================================
  Coverage     100.00%   100.00%
+ Complexity        65        64    -1
===========================================
  Files              3         3
  Lines            154       154
===========================================
  Hits             154       154

Impacted Files
Coverage Δ

src/MysqlParser/Processor/CloudSpanner.php
100.00% <ø> (ø)

src/MysqlParser/Parser.php
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


[CIS] Modify the report format for new requirements

Modify the summarizing logic to record all results, including pass, skipped, not just failures
Change the results structure to include, fail, pass and skip section - 1

Verified on master-head latest.

Report on the API summarizes the results.
It gives the total checks, passed/failed/mixed state.
The details of different tests, with the status is also available in the result.
The details on which node the test has to be run is available.
The details about which nodes the test has failed in case the state of the test is "mixed" is available on the report

.


⚠ PrivateHD has degraded performance

In de05f4e, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2457 ms

Resolved: PrivateHD performance has improved in efea7aa.


TCP control fuzzing and bugfixes

Added:

Fuzz test for ControlBlock segment generation and acceptance, both incoming and outgoing.
Added StringExchange package level function
Created seqs.go to store common logic and types
Added Fuzz test for stacks.TCPConn type, closing the testing loop for communications between client and server with packet length randomness.
Add bugfixes for zero window size control flow.
Now correctly calculates outgoing packet length maximum basing itself on UNA, NXT and Window size

Tested with cyw43439, http-server example and seems to work perfectly.


[DNM] Patch cos for NVME drive fix

Directly patch cos command for fixing https://github.com/harvester/harvester/issues/1627 in case we can't get the backported cos-installer 0.21.2 in time.
See cOS PR https://github.com/rancher-sandbox/cOS-toolkit/pull/937

installer 0.21.2 It's published.


[BUG] Compromised credentials

What version of the bids app were you using?
No response
Describe your problem in detail.
CircleCI has alerted everyone to cycle credentials stored in their environment variables: https://circleci.com/blog/january-4-2023-security-alert/
This project has what I suspect are @Lestropie's docker credentials in its environment variables.
What command did you run?
No response
Describe what you expected.
No response

Thanks for the heads-up.
Rotated the GitHub OAuth tokens, even though apparently CircleCI has done so for all users at their end.
My DockerHub password has been modified.
(Tags currently aren't automatically resulting in Docker image pushes because I've not invested the effort in getting the CI up to date; but the credentials needed to be cycled nevertheless)


Better log display

Q
A

Bug fix?
no

New feature?
no

BC breaks?
no

Deprecations?
no

Related tickets

Documentation

License
MIT

As the logger inlines HTTP request / response, it's really more readable
if the message use many lines by default.

what is the visual impact of this? does it not waste too much space in the collapsed view of the request list? if you think its good there, i am all for doing it, seems the way one usually reads HTTP, with newlines to separate parts

@dbu It is really really cleaner ;)
With bin/console server:log -vvv --format="%datetime% %start_tag%%level_name%%end_tag% <comment>[%channel%]</> %message%\n" (I don't want to see extra & context, it already in the log message):
before:

after:

indeed. thanks a lot!

Thank you for the images!


Fixes typo in "Inconsistency" error message

Noticed this in a screenshot on #660.

Thanks. This error totally deserves a better message (and handling) in the future tho.


Having JsxPdf component import issues

When creating reports using jsxPdf I can't import components from different files. If I do try, then I get the error JsxPdf is not defined
If I have the component in the same file then it works fine.

We decided to not use jsxpdf.


Update checkboxes.js

Hi @pucci2017, sorry for the confusion but you don't need to send pull requests to the repo. The challenges are for you to do in your personal time, but there is no checking or code review.


[SPARK-35363][SQL][FOLLOWUP] Use fresh name for findNextJoinRows instead of hardcoding it

What changes were proposed in this pull request?

This is a followup from discussion in https://github.com/apache/spark/pull/32495#discussion_r632283178 . The hardcoded function name findNextJoinRows is not a real problem now as we always do code generation for SMJ's children separately. But this change is to make it future proof in case this assumption changed in the future.
Why are the changes needed?

Fix the potential reliability issue.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Existing unit tests.

cc @cloud-fan, thanks.

Test build #138546 has started for PR 32548 at commit 5a718fc.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43072/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43072/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43072/

The failed test seems not relevant here, restarted test - https://github.com/c21/spark/actions/runs/841165886 .

Test build #138546 has finished for PR 32548 at commit 5a718fc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138546/

Thank you @dongjoon-hyun and @cloud-fan for review!


Plans for JuMP 0.19 interop?

Hey @joehuchette. I was just wondering what your plans are for supporting JuMP 0.19. I guess there are (at least) two possible avenues:

full rewrite using MOI. SCIP went this route.
wrap the existing MPB interface, similar to AmplNLWriter.

Any thoughts?

I was planning to bite the bullet and update to MOI: the surface area of the package isn't too large, and it mostly uses the nonlinear interface which is largely unchanged. This is one of the projects I was hoping to tackle at the JuMP-dev workshop this week :)

Wow, that would be awesome, thank you!

@joehuchette
If this issue is still open after Christmas, I would be willing to contribute to the merge.

I feel #31 is probably about 80 - 90% of the way to full functionality. What's missing is handling of NLPBlocks, but that hasn't changed much from MathProgBase so it shouldn't be that difficult to reimplement. I just didn't do it because I didn't personally need it and my time is limited right now.

Hello guys!
The tests gear.jl and minlp.jl are not running on my computer.. it says
" ... Attribute MathOptInterface.NLPBlock() is not supported by the model."
Somebody knows how to make it work?
Tks.

The newest version of BARON.jl only supports quadratically constrained problems (for now). It was partially updated for the new communication layer used by JuMP (MathOptInterface). I'm planning to get around to finishing the job in the coming weeks.


Geolocation.GetLocationAsync from MainPage, Main?

I would like to find the users' current location during execution of Events and also 'Xamarin Form Code Behind C#'.
My code works fine when calling Geolocation.GetLocationAsync from an Event (like a Button being pressed)  but I cannot get the async await to work on MainPage Main method. Can you please help me understand how to make this happen?
[Enter feedback here]

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

ID: 3e4b7142-58e2-221e-d4fd-83808c298d89
Version Independent ID: 24c69ad9-44c2-a89d-608c-ffc9946fb411
Content: Geolocation Class (Xamarin.Essentials)
Content Source: docs/en/Xamarin.Essentials/Geolocation.xml
Product: xamarin
Technology: xamarin-essentials
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Hi @stewa11
Unfortunately we cannot respond to support questions here. The recommended place to seek help is the Xamarin.Essentials channel on Microsoft Q&A.

Hi @stewa11
Unfortunately we cannot respond to support questions here. The recommended place to seek help is the Xamarin.Essentials channel on Microsoft Q&A.


Cannot find information about the Chemistry department

The Chemistry department webpage should come up first, but the three pages references (not sure why the 2nd and 3rd have no names) were far from relevant.

Same thing for physics, doesn't search for departmental webpages.

It really has a lot of difficulty finding specific information on individual departments, which leads me to suspect that the weights of the departmental webpages are too small for some reason.

This is an interesting one - I cannot get the retriever to return specific information about the chemistry department office, and I think it's because the information is listed on the front page, but there is no context on the page that indicates this is an office location, it's just in a side bar, and I think users are supposed to intuit that that location is the office - semantically, it's not linking.  I will think about ways to handle this in the search.

@martilar  might be a good one for you to noodle on as well.  If you go into the search index and query for the office location, nothing is returned. If you go to the website directly, you can see the office listed on the main site for the chemistry department.

it is actually more than the front office. For example, this query should definitely be answered by looking at the faculty page or the facutly research pages from the physics department, but the chatBot returned three pages from the college. I've tried a number of questions and never got any page to show up from the physics department website.

thank you for the additional context Chen

PS -- i also created a but for the duplicate citations, that should not be happening

PS -- i also created a but for the duplicate citations, that should not be happening

Those are actually three different pages, two are about funding, and one is the entrance page. They just have the same name.

noted

renaming: Search Relevancy.

It is generating the right response, but the first round didn't return the relevant webpage, and the second round it returned the relevant webpage, but the page is info2.txt, and info1.txt is not relevant.


[cleanup] Remove unused test

The feature flag for this test was never enabled, meaning that this test was never executed.
(I hold no opinion on whether this test is useful or not... if it is maybe someone wants to do the opposite and get it running)

This test has been here forever -- looks like you added it way back in #933.
I think we do still want to test that the hostname check happens correctly, but I think it's a function of the channel creds to do this.  I think we primarily want to test this for SslCreds and TlsCreds -- we know it won't work for (e.g.) insecure creds.
@ZhenLian, do we already have some separate test for this functionality for TlsCreds and SslCreds?  If so, we can go ahead with removing this duplicate test; if not, we should restructure this to work for TlsCreds and SslCreds and make sure it runs.

Any word on this?

We have TlsCreds test for this(https://github.com/grpc/grpc/blob/2badafbc4d246d5165546a61eeb36aa017987d30/test/cpp/security/tls_certificate_verifier_test.cc#L117), but I didn't find anything for SslCreds.
This seems to be core tests. The similar behavior should already be covered in https://github.com/grpc/grpc/blob/2badafbc4d246d5165546a61eeb36aa017987d30/test/core/security/grpc_tls_certificate_verifier_test.cc#L132-L174. I am fine to remove this, especially under the situation where it was never run before.

CC @erm-g on this as well

@ZhenLian I don't think the tests that directly test the hostname verifier are a replacement for this.  This is an end-to-end test that shows that when actually creating a gRPC channel, we will fail the connection if the hostname verification does not fail.  I think we still need that test to make sure that this is actually working end-to-end.
Can you please make sure we have such an end-to-end test?

Sorry for the late reply. I guess what you wanted to say was "we will fail the connection if the hostname verification does fail"?
If that's the case, I agree that we don't have core e2e tests for that right now. All the tests are valid cases, and failure cases are not covered.
@erm-g we might want to add this test as well

So is the outcome here that someone is writing new tests and this currently unused code will remain unused? If so, let's remove it.
Or is the outcome that <> will be re-enabling this test as is and using it in the future? If so, let's close this.

Sorry for the delay...
I think the outcome here is that our team will write new tests, and this currently unused code will remain unused. Adding @erm-g to make proper calls on what we are going to do next...

So can we remove this?

6 months later and this test continues to take maintenance... let's remove it?

@erm-g Can you please assign someone to follow up on this?  Thanks!

b/276460206


Consider rename of OCDS API parameters version and index_version (or new param)

@kindly wrote:
When the version parameter is used for the OCDS API endpoint it makes sense for the core standard (e.g. latest).
When used for profiles the version parameter should be profiles/<profile_slug>/<branch>
and for infrastructure: infrastructure/<branch>
Calling this parameter version could be considered confusing and its usage needs to not contain the start or end /
Originally reported at https://github.com/OpenDataServices/standard-search/issues/10

This parameter no longer exists in #8


Define singleton method on MiqServer before attempting to stub it

With strict partial validation enabled you will see the following error when running the MiqQueue specs:
Failure/Error: allow(MiqServer).to receive(:setup_data_directory).and_raise(ex)
       MiqServer(id: integer, guid: string, status: string, started_on: datetime, stopped_on: datetime, pid: integer, build: string, percent_memory: float, percent_cpu: float, cpu_time: float, name: string, last_heartbeat: datetime, os_priority: integer, is_master: boolean, logo: binary, version: string, zone_id: integer, upgrade_status: string, upgrade_message: string, memory_usage: decimal, memory_size: decimal, hostname: string, ipaddress: string, drb_uri: string, mac_address: string, vm_id: integer, has_active_userinterface: boolean, has_active_webservices: boolean, sql_spid: integer, rh_registered: boolean, rh_subscribed: boolean, last_update_check: string, updates_available: boolean, log_file_depot_id: integer, proportional_set_size: decimal, has_active_remote_console: boolean, system_memory_free: decimal, system_memory_used: decimal, system_swap_free: decimal, system_swap_used: decimal, has_active_cockpit_ws: boolean, unique_set_size: decimal, has_vix_disk_lib: boolean, href_slug: string, region_number: integer, region_description: string, zone_description: string) does not implement: setup_data_directory

The problem is that there is no MiqServer.setup_data_directory method, so I created an empty definition. With this in place the specs pass.

@miq-bot add_label test, refactoring

I'm guessing the failure is unrelated.

Looks like a sporadic failure, I restarted that test

@agrare Thanks, green now. :)


Fail to add / edit short name in column dictionary

Description

Add/ edit Short Column Name in column dictionary
Related Issue :

MT-58
How Has This Been Tested?

Metadata -> column dictionary -> create new column dictionary

Add column dictionary with short colum name ->
Go to column dictionary detail -> check if you can see the short column name -> Try editing short column name
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project. it will be added soon
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document. it will be added soon
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Additional Context

run build
deploy to 5

@kyungtaak 서버에서 값이 오는데 안나온다는 말씀이신가요 ?


Committing adding challenge 1 solution to the branch

Committing the merge of challenge 1 to forked repository

f

Challenge 1 code ready to be submitted to the main branch when ready


Write records to Kinesis in a batch

This fixes problem with Kinesis Tee performance. See #31.
Additionally specs are updated to work with awscala 0.5.9.

Thanks, I'll have a look tomorrow :+1:

Thanks!

@kazjote has signed the Individual Contributor License Agreement. Thanks so much

@BenFradet I can. However, I am not sure if it is really Iglu schema. According to https://github.com/snowplow/iglu/blob/master/README.md

Iglu is a machine-readable, open-source schema repository for [JSON Schema] json-schema

but avro schema is not json-schema (however somehow similar). As far as I can see, there are at least differences in types (for example: "record", "int", "number"). I am not sure if anybody can use it with any json-schema validator. For example, it fails with this one: https://www.jsonschemavalidator.net/
Let me know if you still want to have avro schema in Iglu Central. If you do, I will create a PR.

We have avro schemas in iglu central too like the one for 1-0-0: https://github.com/snowplow/iglu-central/tree/master/schemas/com.snowplowanalytics.kinesistee.config/Configuration/avro

@BenFradet: Kacpers contributions should be covered by the LiveIntent corporate CLA.

@kazjote has signed the Software Grant and Corporate Contributor License Agreement. Thanks so much

@BenFradet Any chance to have this PR accepted and released?

hey @christoph-buente , we're not maintaining this project anymore. I'll ask for it to be archived.

Interesting, what are the proposed ways to filter streams for example for missing data or spider/bot traffic?

From: Ben Fradet<EMAIL_ADDRESS>Sent: Thursday, June 20, 2019 8:14:41 AM
To: snowplow/kinesis-tee
Cc: Christoph Bünte; Mention
Subject: Re: [snowplow/kinesis-tee] Write records to Kinesis in a batch (#32)
hey @christoph-buentehttps://github.com/christoph-buente , we're not maintaining this project anymore. I'll ask for it to be archived.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/snowplow/kinesis-tee/pull/32?email_source=notifications&email_token=AAAJBBTBUG5IOUMCD2XYGNLP3MN5DA5CNFSM4D7X4THKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYEMGFQ#issuecomment-503890710, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAAJBBTTGUMFKK5RFZVNPHTP3MN5DANCNFSM4D7X4THA.


Button receives dotted outline on focus in Firefox

Expected Behavior
Button should not get dotted outline in Firefox.
Actual Behavior
Button gets dotted outline in Firefox. Applies to all buttons, not just CTA.

Steps to Reproduce

Go to https://opensource.adobe.com/spectrum-css/2.13.0/docs/#button---cta
Tab to a button.
See dotted outline.

Browser name/version/os (ie Chrome Version 62.0.3202.94 (Official Build) (64-bit) MacOS)
Firefox
Spectrum-CSS version
2.13.0

Duplicates #161


Page Generation Fails on Certain Pages with 502 error

When generating the pages using npm run build pages time out after 2 attempts. This happens even after reattempting to build.
Page ID that errors: af74a514d795499193b3487b200ebb39

I also have this bug but every time when I build, one or two random pages will have this error.
Error occurred prerendering page "/troi". Read more: https://nextjs.org/docs/messages/prerender-error
HTTPError: Response code 502 (Bad Gateway)
    at Request.<anonymous> (C:\Users\jch\Desktop\nextjs-notion-starter-kit\node_modules\notion-client\node_modules\got\dist\source\as-promise\index.js:117:42)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

@transitive-bullshit Could you help figure out what could be the issue here? The fact that it's random pages getting this error is not really debuggable.. thanks!


[silgenpattern] Perform a copy if we have a borrowed cast operand, before we store it.

[silgenpattern] Perform a copy if we have a borrowed cast operand, before we store it.
Sometimes in SILGenPattern, we need use an indirect cast on object that does
not require re-abstraction as an optimization. A notable case where this happens
are various casts related to NSError. In such a case, if we have a borrowed cast
operand, perform a copy before the store to preserve semantic sil invariants.
rdar://31880847

@swift-ci smoke test and merge


Popups fail when clustered

Given these elements:
          <l-marker-cluster-group>
            <l-marker
              v-for="ms of mapStats"
              :key="ms"
              :lat-lng="ms.lalo"
            >
              <l-popup>hi</l-popup>
            </l-marker>
          </l-marker-cluster-group>

When enclosed by the cluster tag the popups fail to work although an @click with a console.log on each marker still works.   The markers are clickable but for some reason the popup isn't triggering.
Thanks in advance for any help!

Can you spin up a minimal test environment which shows the problem?

@mwolfeu Had you time to create a demo where I can have a look into it?
Without a demo it is hard for me to reproduce, because I don't know how your current setup look like.
E.g. It might be a problem that you assigning the ms object in your example code above as a key, but this is just a guess.

Unfortunately I can't seem to replicate it.
Essentially mapStats is a computed variable which looks like:
{
    "lalo": [
        40.45661544054639,
        -74.00244397323672
    ],
    "icon": 4,
    "html": "\n            Name: My Pi
\n            Model:  RPi 5
\n               Country: US
\n            State/Region: New York
\n            Address: Street18"
}

When using the computed variable things fail as described.  When I console.log it, take that output and assign it to a variable manually, it works!
By adding an @click to each marker, I can see print data for the problem markers and it all looks fine.
The marker is there, the data is there, but the html elements for the popup never get generated when I click it.
If you have any ideas regarding different things I could try, I'd be grateful.

This looks more like you loosing some stuff, like the reactivity, on some point. Unfortunately it is kind of hard do diagnose the problem without having a look into the component by myself. Maybe try to copy the component into a demo as it is and just try to mock the provided data around the component itself. If this still doesn't show the same error as you experience locally, I would suggest you to remove bit by bit from the component till it works and try to readd the stuff again afterwards to get closer to the issue.
Overall it doesn't look like a problem of the library itself to me.

Fixed.
I'm still not clear why the problem manifested the way it did. But I'm pretty sure the problem was that I was I was using an initially empty "filter" object for filtering map data.  The object would contain properties like country:"DE" but only after the user selected them from the ui.
I just learned Vue cannot detect property addition or deletion, only changes to existing properties. So, filling out the filter object with starting values (even if those values were null) fixed everything.


Clarity on Speech to Text Customization using the SDK.

I don't understand why the SDK is flagged as "No" on the customization row for Speech to Text on the table on this page, so I wanted to clarify my understanding. You can definitely use the SDK to use custom models in Speech to Text,

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

ID: 4e54515b-dff7-4345-7e85-146692a33701
Version Independent ID: 12f4adf9-3ebe-5d1e-a6aa-bc254bea8eb3
Content: What are the Azure Speech Services? - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/overview.md
Service: cognitive-services
Sub-service: speech-service
GitHub Login: @erhopf
Microsoft Alias: erhopf

@JamesearlThanks for your question. We are checking on this and will respond to you soon.

@JamesEarle + @SumanthMarigowda-MSFT - While the SDK does allow you to use an already created custom models, you cannot use the SDK to create/train/deploy custom models. For the latter, you'll need to use the REST APIs: https://westus.cris.ai/swagger/ui/index

@erhopf Thanks, that is consistent with my understanding but I don't feel like the differentation is made clear in this documentation. Perhaps distinguishing between custom model usage (SDK) and custom model management (REST) would help here.

@JamesEarle - Agreed. We'll look into an update that clears this up.

#please-close
We have a work item to update this. Thanks again @JamesEarle.

@JamesEarle
We will now proceed to close this thread. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.


Unhandled rejection RangeError: Maximum call stack size exceeded

Hi,
I'm experiencing some problems using your library (version 0.0.5). I use it in order to define visibility scope in various sequelize entities, for example:
cache: {
			type: DataTypes.TEXT,
			roles: {
				self: true
			}
		}

Sometimes, after an undefined number of call (a lot), I can't realize when exactly, a get this error:
Unhandled rejection RangeError: Maximum call stack size exceeded
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)
    at target.Instance.get (/var/app/current/node_modules/ssacl-attribute-roles/lib/index.js:52:23)

can you help me?

I'm afraid i haven't encountered this error before.
Anyway you can show me some code that reproduces this to some kind of certainty?

Hmm, are you calling ssaclAttributeRoles(sequelize|models) multiple times in your code over time? Looks like the code keeps calling itself whcih should only happen if the init code is called multiple times.

Yes, I noticed that I call it twice, I tried to fix and now I'm testing

Must be calling it more than twice, you must be calling it continously. Would be great to implement a check for this.

Ok, i fixed it.

I'm reopening to remind myself to throw an error if init'ed twice.


Syncronize option don't appear on Brave browser

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
On Brave browser the syncronize feature don't appear.
To Reproduce
Steps to reproduce the behavior:

Go to 'File' tab

Expected behavior
The synchronize feature should appear.
Screenshots

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 14.9.4

Desktop (please complete the following information):

OS: Windows 10 x64
Browser: Brave Version 1.27.111 Chromium 92.0.4515.131

We don't test Brave, a user needs to debug this.


Huion GT-185

Hardware: Inspiron 7577
Operating System: Xubuntu 18.04.1 x86_64
Console output:
Reading configuration. . . Done!
Preparing driver. . . Done!
--------------------------------------------------------------------------------
    |                Product: Tablet Monitor
 64 |        Params block #1: ??????
    |                          Max X: 64400
    |                          Max Y: 36240
    |                   Max pressure: 2047
    |                     Resolution: 4000
    |
 79 |         Internal model:
 7b |         Buttons status: HK On
 c8 |        Params block #2: ????????
    |                          Max X: 64400
    |                          Max Y: 36240
    |                   Max pressure: 2047
    |                     Resolution: 4000
    |
 c9 |      Unknown string #1: HUION_M163_161017
 ca |  Internal manufacturer: HUION Animation Technology Co.,ltd
--------------------------------------------------------------------------------
Setting up driver. . . Done!
	Tablet model name     GT-221 PRO
	Buttons               ENABLED (10)
	Scrollbar             ENABLED (1)
	Desktop notifications ENABLED
	Multi Monitor Setup   disabled

Huion Kamvas driver should now be running

% Main Menu %
button 0 = [menu_krita]
button 1 = [menu_gimp]
button 2 = [menu_darktable]
button 3 =
button 4 =
button 5 =
button 6 =
button 7 =
button 8 = key Return
button 9 = key Escape
Traceback (most recent call last):
  File "./huion-tablet-driver.py", line 476, in <module>
    main.run()
  File "./huion-tablet-driver.py", line 32, in run
    main_loop()
  File "./huion-tablet-driver.py", line 268, in main_loop
    X = (data[8] << 16) + (data[3] << 8) + data[2]
IndexError: array index out of range

Only monitors are the laptop display and the Huion.

Some more info as I try to get it working:
Primary screen:
eDP-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 345mm x 194mm
Huion screen:
HDMI-1-4 connected 1366x768+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
The error at the bottom appears after I try to use the pen, but then on subsequent attempts to run the script it repeats the error until I modify the config, then it's back to waiting for me to try to use the pen.
As for the config, here are some changes I made:
[laptop_seperate]
# Laptop builtin and Huion tablet, separate views

# screen sizes
laptop_width = 3840
laptop_height = 2160
tablet_width = 1366
tablet_height = 768

# quick maths
total_screen_width = ${laptop_width} + ${tablet_width}
total_screen_height = ${laptop_height}
tablet_offset_x = ${laptop_width}
tablet_offset_y = 0

# output types
laptop_output = eDP-1
tablet_output = HDMI-1-4

# xrandr parameters
xrandr_laptop_output = --output ${laptop_output} --mode ${laptop_width}x${laptop_height} --pos 0x0 --rotate normal
xrandr_tablet_output = --output ${tablet_output} --mode ${tablet_width}x${tablet_height} --pos ${laptop_width}x0 --rotate normal
xrandr_args = ${xrandr_laptop_output} ${xrandr_tablet_output}

[tablet_gt185]
model_name    = GT-185
screen_width  = 1366
screen_height = 768
pen_max_x     = 64400
pen_max_y     = 36240
pen_max_z     = 2047
resolution    = 4000
buttons       = 8
scrollbar     = 0
screen        = true

I also find that the tablet is still mirroring a portion of my laptop's screen even with the script running.

I just realized that the xrandr part was not working because I forgot to enable it at the top of the config. So one problem solved.

So I've been doing a bit of digging, it seems that in the main_loop() you are expecting data to have 8 items but my tablet is only returning 7.
Here's the values I gathered from my bodge of a debug:

Always 7
Changes depending on what is happening, seems to match the other tablets.

Default: 128
Touch: 129
Pen Button 1: 130
Pen Button 2: 132
Tablet Buttons: 224 (and sticks until touch or pen button)

I think this is distance the pen is from tablet but the numbers are funky, it goes past 255 and wraps as you get close
X value. Leftmost is 0, Rightmost is 255
Seems similar to #2 but I can't tell, the numbers change too fast for me
Y value. Topmost is 0, Bottommost is 141
Pressure sensitivity, 0 is min, 255 is max
Pressure sensitivity, 0 is min, 7 is max

I haven't tried going through the code to rematch it up yet.

I have got it working to a level I am good with and uploaded it to a new repo if you are interested in viewing:  531d55d

Thank you very much, this is very valuable information.
I'll have to investigate this carefully. Not having a table like this to make tests makes things harder...

I noticed in commit 1319c14, you added the tablet to the config file, however without changes to the driver script, it won't work properly.

Hi @JulianWebb thanks for keeping in touch.
Yes, it won't work, but I need to understand the issue much better, before commiting those kind of changes. There are more tables that don't work and I'd like to support all the cases, without causing current working ones to fail.
I've just updated the script adding a new debug mode to get better debugging information.
Could you please try the new version after changing debug_mode = true in the config file, and paste back some of the lines that appear when you use the pen, like the following?:
data[12] = array('B', [8, 128, 17, 88, 33, 145, 0, 0, 0, 0, 0, 0])
{'TYPE': 128, 'X': '[8]<<16+[3]<<8+[2]=22545', 'Y': '[5]<<8+[4]=37153', 'PRESS': '[7]<<8+[6]=0'}
data[12] = array('B', [8, 129, 26, 88, 184, 145, 250, 1, 0, 0, 0, 0])
{'TYPE': 129, 'X': '[8]<<16+[3]<<8+[2]=22554', 'Y': '[5]<<8+[4]=37304', 'PRESS': '[7]<<8+[6]=506'}
data[12] = array('B', [8, 129, 21, 88, 54, 146, 123, 6, 0, 0, 0, 0])
{'TYPE': 129, 'X': '[8]<<16+[3]<<8+[2]=22549', 'Y': '[5]<<8+[4]=37430', 'PRESS': '[7]<<8+[6]=1659'}
data[12] = array('B', [8, 129, 6, 88, 135, 146, 192, 10, 0, 0, 0, 0])
{'TYPE': 129, 'X': '[8]<<16+[3]<<8+[2]=22534', 'Y': '[5]<<8+[4]=37511', 'PRESS': '[7]<<8+[6]=2752'}

I will try the debug mode when I get access to my tablet later today.

Great. I look forward to it because I can't wrap my mind around the changes you did.
Originally the X coordinate is composed from 3 data points: data[8]*65536 + data[3]*256 + data[2]
But you changed it to: int(data[3]/255)*64400 which I don't know how it can give any meaningful coordinate representation, because if you are receiving X from data[3], by dividing between 255 and loosing the decimal part you are effectively ignoring its value completely, because the data points can't be higher than 255, at least in my tablet. So the result should be always 0.

So I got a similar error to what I originally got when I first opened this issue.
Finding USB device. . . Done!
Reading configuration. . . Done!
Preparing driver. . . Done!
--------------------------------------------------------------------------------
    |                Product: Tablet Monitor
 64 |        Params block #1: ??????
    |                          Max X: 64400
    |                          Max Y: 36240
    |                   Max pressure: 2047
    |                     Resolution: 4000
    |
 79 |         Internal model:
 7b |         Buttons status: HK On
 c8 |        Params block #2: ????????
    |                          Max X: 64400
    |                          Max Y: 36240
    |                   Max pressure: 2047
    |                     Resolution: 4000
    |
 c9 |       Firmware version: HUION_M163_161017
 ca |  Internal manufacturer: HUION Animation Technology Co.,ltd
--------------------------------------------------------------------------------
Setting up driver. . . Done!
        Tablet model name     GT-185
        Buttons               ENABLED (8)
        Scrollbar             disabled (0)
                 Reversed: (False)
        Desktop notifications ENABLED
        Multi Monitor Setup   disabled
        Calling xrandr        disabled

Huion Kamvas driver should now be running

% Main Menu %
button 0 = [menu_krita]
button 1 = [menu_gimp]
button 2 = [menu_darktable]
button 3 =
button 4 =
button 5 = [menu_vlc]
button 6 =
button 7 = key Escape
Traceback (most recent call last):
  File "./huion-tablet-driver.py", line 543, in <module>
    main.run()
  File "./huion-tablet-driver.py", line 32, in run
    main_loop()
  File "./huion-tablet-driver.py", line 322, in main_loop
    X = (data[8]<<16) + (data[3]<<8) + data[2]
IndexError: array index out of range

I think it's probably for the same reason, the data packets coming in from my tablet are different from what it is for the others.
As for what my code is doing, I honestly had to look at again to remember.
the int() encapsulates the entirety of (x_item / 255) * main.settings['pen_max_x'] so it's not losing the decimal before multiplying it, I think that was the main confusion there. I don't really know what the data packet looks like from your tablet, but I know it differs from what mine is outputting, so some tweaks had to be made.
Also I have no idea how the actual communication over USB part works, that's a mystery to me.

I see... Thanks. I'd love to see the received data in your case.
Could you please add the following code to your modified source, inside the main_loop() function, just before the is_touch = data[1] == 129 line? (should be line 236 in your fork ):
if not (data[1] == 128):
    print("data[{}] = {}".format(len(data), data))

Then run it, and briefly press the four tablet corners with the pen (top left, top right, bottom left, bottom right) and paste here the output that appears when you press it?

Now you can choose [tablet_debug] as your tablet, it should print the correct information every time you touch the screen, without giving any errors.
Let me know if you can try it and share the output


Unable to apply css to options or break options

https://stackblitz.com/edit/angular-wev3m8?file=src%2Fapp%2Fapp.component.ts
I am trying to break the line if the option label is too long.

how can I achieve that?

You could pass a custom class to that field through className:
{
  key: 'Select',
  type: 'select',
+ className: 'custom-select'
}

Then apply the desired style in your css files, in general native select has a limited styling support in browsers, so in case you want to have a full control of select options I would suggest to use ng-select.