Add warning to "force", and write explanations of what the app is doing

I'm new to upriver.  I was clicking the "Pull" button and getting no feedback, so I selected "force".  I assumed if pushing this was going to lead to something irretrievably destructive, it would warn me.  Well, it didn't warn me.  There are also no instructions anywhere on what upriver actually does or is going to do - leading to a false sense of security.  Users are conditioned to an experience as follows: Apps tell you if they're going to do something irretrievably destructive.  They describe what's about to happen, and they give you a chance to back out.  In the absence of being warned, and in the absence of having anything described, the user is conditioned to assuming the action will be safe.
So, I've now lost all the changes I made to my fork, and its commit history.  If it wasn't for me happening to have a browser window open with the file (albeit in a form I have to redo some), I'd presumably have lost it completely.
Let's put this in perspective.  Upriver has one button, and one check box.  Neither are explained.  If you press the button with the checkbox enabled, upriver erases your work forever without warning you.  I believe this project is well-intentioned, and certainly would ostensibly provide a very useful service sorely lacking from the github web UI. Nevertheless, if I had a button that could erase Upriver in its current form from the internet entirely, and without warning you, well...

Hey! I'm sorry to hear that you might have lost data. If you can find any way to locate the sha1 hash of the commit (this article might assist), you can recover your work (although you'll have to open a Javascript console and use Upriver directly, the UI doesn't support that). You could find that hash by inspecting the page's HTML using DevTools if on the off chance you still had Upriver open.
You are very justified in wanting a more obnoxious warning, and I'll see what I can do. The checkbox does have a tooltip that explains it to some degree, but it's possibly not clear enough. I'm surprised that pressing the "Pull" button, didn't do anything, but the code in it's current form doesn't do  error-handling very well, and won't display any visual indication for a lot of errors (even as simple as the internet dropping out).

Thank you! The article helped me find the hash, but recovering didn't seem to work.  It's alright though  - I'd already fixed it.  I was just going through the article out of interest :)
Indeed, clicking the Pull button reported nothing back to me - so I assumed it hadn't done anything.  When enabling force however, clicking Pull came up with a dialogue with some JSON.

I'm assuming you were trying to rebase your fork with upstream, rather than just fast-forward your fork. The former is something I'd love to be able to do with Upriver (tracking issue #12), but it's significantly more complex and may not be possible with just the GitHub API. The main use-case I created Upriver for, is that I create a lot of small PRs as I notice small bugs/documentation issues in projects that I use, and often I can do this without having to clone locally with the GitHub web editor. This works once, but when I come back to the same project six months later, my fork is out-of-sync and the workaround for that is to delete and recreate the fork. With Upriver I can fast-forward my fork to match upstream, and "force" reset it if there are any conflicts.


implemented disallow-identifier-names

Related to https://github.com/jscs-dev/node-jscs/pull/943. I screwed the rebase :weary: Sorry

Coverage increased (+0.01%) to 98.64% when pulling 5ffbdd7f08612dbe2f93b5af22586fdb8afb7456 on alawatthe:identifier-names into ca77989defdee0320f92fb029ca61fa062ed0f35 on jscs-dev:master.

A test asserting case sensitivity would be great. In other words, there should be a test that shows that FOO does not result in an error.

Coverage increased (+0.01%) to 98.64% when pulling 24a4113d97dcdf07819afd16feb45fd8d01f36f9 on alawatthe:identifier-names into ca77989defdee0320f92fb029ca61fa062ed0f35 on jscs-dev:master.

@alawatthe Sorry this fell through the cracks. Great work here. Thanks for contributing. Landed!
I think this will be a popular rule.


Whether cli support IOS7?

Hi,
I' d like to ask about this: whether cli support IOS7?
I created an empty project, built, and made server by nginx,
I can browse correctly in relatively new version,
but blank in IOS7.1.1 (no log, no error, it seems like no .js files have been executed).

Hi,
I find the root causeis "ReferenceError: Can't find variable: Proxy".
How can I solve this problem?
Thanks!

Add a polyfill? See src/polyfills.ts.

you are right, but i use polyfill from https://github.com/GoogleChrome/proxy-polyfill.

According to the last comment, this has been solved. Closing this. If there is still an issue, please open a new issue and follow the template. Thanks.


Pusher suffix for internal devs

Details

Reads pusher suffix from local php config (in external sibling folder project)
Exposes it to .env so it's available in CONFIG.js

Part of bigger Offline First - Pusher Changes design doc.
The reason we need to start doing this is b/c in the near future Pusher will handle some API responses, and we don't want one response to take effect on multiple engineers' local environments. Hence we're appending a unique string (the pusher suffix) to the end of pusher channels to keep things from crossing over

original PR: https://github.com/Expensify/App/pull/8727

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/207393
Tests

[x] Verify that no errors appear in the JS console
[ ] Verify the suffix is exposed to webpack (web/mobile-web/desktop)

you can console.log it from src/CONFIG.js

[ ] Verify the suffix is exposed in metro/react-native (ios/android)
[ ] The suffix should fallback to empty string '' for production and staging builds
[ ] Inspect and see Pusher unit tests passing

Sample local dev output
[web-server]
[web-server] ><EMAIL_ADDRESS>web-server /Users/kidroca/Desktop/Freelance/Expensify.cash
[web-server] > scripts/dev.sh && webpack-dev-server --config config/webpack/webpack.dev.js
[web-server]
[web-proxy]
[web-proxy] ><EMAIL_ADDRESS>web-proxy /Users/kidroca/Desktop/Freelance/Expensify.cash
[web-proxy] > node web/proxy.js
[web-proxy]
[web-server] Using PUSHER_DEV_SUFFIX from ./config/_config.local.php
[web-server] Found suffix: 83894078fa2543c7b4c775b6645b514d
[web-server] Updating .env
...

PR Review Checklist

Contributor (PR Author) Checklist

[ ] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

PR Reviewer Checklist

[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

QA Steps

Verify production or staging are unaffected.
The changes here should apply only to local development. Sending/receiving reports and "user typing" events should be be working without regressions

[ ] Sending/Receiving messages still works
[ ] Adding/Removing users to policy still works
[ ] Removing users from policy from User B should reflect the changes for User A

Not sure how this exactly works but if User A and User B are part of the same policy and User B can remove users. When User B remove users this should be reflected for User A in real time. I think if you go to Setting -> Workspace -> Manage Members you should not see the removed members

Screenshots

Web

Mobile Web

Desktop

iOS

Android

cc @Beamanator

@Beamanator can you check whether this is the direction we want to go - add a value to .env so it can be reused by both metro and webpack bundlers

Some context
Reading  _config.local.php and adding PUSHER_DEV_SUFFIX only in webpack does not expose the variable to react-native ios/android, because they are bundled by metro
There's no easy way to update metro config to include and set a PUSHER_DEV_SUFFIX global variable, besides writing a custom plugin
The easiest thing to do to expose PUSHER_DEV_SUFFIX to both metro and webpack seems to be to add it to .env

I've reverted the refactoring work out of this PR since it's not essential to the feature - it seems raw concatenation is preferable in order to keep php and js channel names in sync
We can open a separate PR to refactor
✔ Ready for Review

I like the idea of doing the refactor in a separate PR to keep changes specific.
Can you also add the pusher suffix to the public-policyEditor channel name (in actions/Policy.js)? I didn't see that one since it was just added

Can you also add the pusher suffix to the public-policyEditor channel name (in actions/Policy.js)? I didn't see that one since it was just added recently

Sure, I thought it was intentionally left out
I'm not familiar with what the suffix is for, but the logic to expose it in webpack and metro
Maybe in the future the suffix can be fetched as a param after login?

Could you please add this comment & the suffix to the policyEditor channel? Then I think we're good to go

✔ Done & done

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Hey guys sorry but it seems I've forgotten to update file permissions for the new script
It should be flagged as executable

Heh, yeah. I just ran into that. Oops!

Thanks for fixing @kidroca ! 🙏

🚀 Cherry-picked to staging by @sketchydroide in version: 1.1.57-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @chiragsalian in version: 1.1.57-17 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


adding getters

Description
TODO: Include a detailed description of the changes in the body of the PR.
TODO: If relevant, provide a URL to updated Pattern Library documentation.
Testing Checklist

[x] Write unit tests for all new features.

Non-testing Checklist

[ ] Consider any documentation your change might need, and which users will be affected by this change.

Post-review

[ ] Squash commits into discrete sets of changes with descriptive commit messages.

Reviewers
TODO: In this section, tag specific reviewers you know will want to have a look at this PR. You can use the checklist below for organization:

[ ] @mention a reviewer here
[ ] @mention a reviewer here

Coverage decreased (-0.3%) to 93.068% when pulling 570d2b0f5d0fb4bf7f44212f7dc119bc3bf2ed52 on ekafeel/upgrade-edx-paging-collection into f8c07a983e0125bcab17b5e105b3f6710e37d8e3 on master.

Thanks for the contribution, @ehteshamkafeel!
I'd like to ask you to do a few things before I re-review:

Add some tests for your changes. You can read more about our testing requirements in the open edX contributing docs.
Please update the description of this PR to describe the changes you've made. Currently it appears to be the default PR template that we use. You can delete any non-relevant sections.

Thanks!

@dan-f yeah, I am actually writing tests. This PR isn't yet ready for a review yet that's why I didn't tag anyone. Thanks for your reviews though, makes perfect sense.

I see. Sorry to have interrupted your workflow! I thought I was tagged by you, but it looks like it was just @mention-bot doing its job :)

Coverage increased (+0.2%) to 93.52% when pulling 4f1de81abfde6b80a7b0538b82ee344f44dd692e on ekafeel/upgrade-edx-paging-collection into 789203b6912d17eeab4a8a752d2e7ce46f2bbf82 on master.

Coverage decreased (-0.2%) to 93.184% when pulling 2ed7132c535b4e69432de0a8a9bbccf3128d6371 on ekafeel/upgrade-edx-paging-collection into f8c07a983e0125bcab17b5e105b3f6710e37d8e3 on master.

👍  Looks good to me. Here are the steps to release the UI Toolkit:
https://openedx.atlassian.net/wiki/display/FEDX/UI+Toolkit+release+process

Coverage increased (+0.1%) to 93.483% when pulling 4087de4d9bf1b459b61f7046b0487b4084f92114 on ekafeel/upgrade-edx-paging-collection into 789203b6912d17eeab4a8a752d2e7ce46f2bbf82 on master.

@andy-armstrong @dan-f I have simplified my changes by removing the overridden parseState method in favor of more complete version of PageableCollection's parseState. I have overrridden two more query parameters values in the state object's declaration in PagingCollection.

Coverage increased (+0.2%) to 93.527% when pulling 7c26a96bec817af5e47839ae2a3dd41429f3f20c on ekafeel/upgrade-edx-paging-collection into 789203b6912d17eeab4a8a752d2e7ce46f2bbf82 on master.

Hi @ehteshamkafeel - thanks for your patience on my review.
While I really appreciate your contributing to the PagingCollection, I'm feeling that this change is not necessary; the requested behaviors are already implemented.
Backbone.paginator already has an API to set state through its constructor:
newCollection = new PagingCollection({
  results: [ ... ]
}, {
  state: {
    totalRecords: 10,
    currentPage: 2,
    totalPages: 3,
    pageSize: 4,
  },
  parse: true
});

Using this API will get the first part of your test to pass.
As for the second part, you call Backbone.collection.set() and Backbone.collection.reset() in order to set state values.  I would not expect this to work, since Backbone.paginator.PageableCollection does not override set. Furthermore, I'm not sure if we'd need such an API. Once instantiated, a collection should not mutate its own state. Since the collection represents a server's paginated API, the state should be parsed from server responses, not on-the-fly set manually on the client.
So, while I don't agree with the parseState changes (:-1:), the new getters get a :+1: from me!

@dan-f Have you seen the original implementation of parseState in backbone.paginator's PageableCollection. I don't know why we have overridden this method. If we don't override the method we get the expected behavior and we don't need these changes. So original parseState method does change state in set or reset if parse is set true. We only needed to customise the totalRecords and totalPages keys is queryParams to make it work.

@ehteshamkafeel I cannot recall why parseState was overridden, but I think it happened when I migrated this module from backbone paginator < 1.0 to ~2.0. If we can get away with removing it, great.

Coverage increased (+0.1%) to 93.483% when pulling 16626810f74294125b5dc0fbb0b19f713b40afdc on ekafeel/upgrade-edx-paging-collection into 789203b6912d17eeab4a8a752d2e7ce46f2bbf82 on master.

@dan-f I have removed the parseState method from PagingCollection and customised the queryParams for totalPages and totalRecords. I didn't remove the test and it's still passing. Please review.

@ehteshamkafeel could you outline your particular use case?

@dan-f yeah I can set state with constructor, but really now I don't know of any reason why this has to be like it is and what's wrong with this change.
Anyways I will discard these changes.

Nothing wrong with the changes, and please don't discard them! I'm just hoping to better understand the use case. I'm 👍  with the current changes, btw.

@dan-f Thanks for the thumbs up. Actually if we keep it as is then I will have to do a lot of refactoring in the edx-platoform. Thanks again!

@andy-armstrong you good with these changes?

Yep, looks great to me. 👍

Coverage increased (+0.1%) to 93.483% when pulling dc863281fe2d82a1c00752ccedb61fb568319d8d on ekafeel/upgrade-edx-paging-collection into 789203b6912d17eeab4a8a752d2e7ce46f2bbf82 on master.


Error when inserting TypeError: Cannot read properties of null (reading 'length')\n    at TableHandler.checkProperties

Which service(blob, file, queue, table) does this issue concern?
Table
Which version of the Azurite was used?
3.17.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
v.16.9.1
What problem was encountered?
After updating to the newest version (3.17.0), some of our integration tests started failing. The problem happens when we are inserting entities into a table. It looks like it is because some of the properties that we are inserting are 'null'
Steps to reproduce the issue?
If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: TableStorageContextMiddleware: RequestMethod=POST RequestURL=http://<IP_ADDRESS>/devstoreaccount1/testTable945584?$format=application%2Fjson%3Bodata%3Dminimalmetadata RequestHeaders:{"host":"<IP_ADDRESS>:10002","x-ms-version":"2019-02-02","dataserviceversion":"3.0","prefer":"return-no-content","accept":"application/json; odata=minimalmetadata","x-ms-client-request-id":"f4980e87-b413-4c91-a3d2-efa34ee4d72e","x-ms-return-client-request-id":"true","user-agent":"azsdk-net-Data.Tables/12.5.0 (.NET 6.0.2; Darwin 19.6.0 Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64)","x-ms-date":"Thu, 28 Apr 2022 13:16:50 GMT","authorization":"SharedKeyLite devstoreaccount1:pLFpauz4G4TsWFN5R877KI5zn51mqD9vAgnOlXbCEzk=","content-type":"application/json; odata=nometadata","content-length":"197"} ClientIP=<IP_ADDRESS> Protocol=http HTTPVersion=1.1
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d debug: tableStorageContextMiddleware: Dispatch pattern string: /testTable945584
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: tableStorageContextMiddleware: Account=devstoreaccount1 tableName=testTable945584
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d verbose: DispatchMiddleware: Dispatching request...
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: DispatchMiddleware: Operation=Table_InsertEntity
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d verbose: AuthenticationMiddlewareFactory:createAuthenticationMiddleware() Validating authentications.
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: TableSharedKeyLiteAuthenticator:validate() Start validation against account shared key authentication.
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: TableSharedKeyLiteAuthenticator:validate() [STRING TO SIGN]:"Thu, 28 Apr 2022 13:16:50 GMT\n/devstoreaccount1/devstoreaccount1/testTable945584"
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: TableSharedKeyLiteAuthenticator:validate() Calculated authentication header based on key1: SharedKeyLite devstoreaccount1:pLFpauz4G4TsWFN5R877KI5zn51mqD9vAgnOlXbCEzk=
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: TableSharedKeyLiteAuthenticator:validate() Signature 1 matched.
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d verbose: DeserializerMiddleware: Start deserializing...
2022-04-28T13:16:50.206Z e1cf5d57-fa43-419f-b58b-59888e23ad2d debug: deserialize(): Raw request body string is (removed all empty characters) {"LeverandorNummer":"1234","LeverandorNummer@odata.type":"Edm.Int64","Orgnummer":"1234","NummerserieType":"Leverandor","IsManuallyHandledInAgresso":null,"PartitionKey":"Leverandor","RowKey":"1234"}
2022-04-28T13:16:50.207Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: HandlerMiddleware: DeserializedParameters={"options":{"queryOptions":{"format":"application/json;odata=minimalmetadata"},"requestId":"f4980e87-b413-4c91-a3d2-efa34ee4d72e","dataServiceVersion":"3.0","responsePreference":"return-no-content","tableEntityProperties":{"LeverandorNummer":"1234","LeverandorNummer@odata.type":"Edm.Int64","Orgnummer":"1234","NummerserieType":"Leverandor","IsManuallyHandledInAgresso":null,"PartitionKey":"Leverandor","RowKey":"1234"}},"version":"2019-02-02","body":"ReadableStream"}
2022-04-28T13:16:50.207Z e1cf5d57-fa43-419f-b58b-59888e23ad2d error: ErrorMiddleware: Received an error, fill error information to HTTP response
2022-04-28T13:16:50.207Z e1cf5d57-fa43-419f-b58b-59888e23ad2d error: ErrorMiddleware: ErrorName=TypeError ErrorMessage=Cannot read properties of null (reading 'length') ErrorStack="TypeError: Cannot read properties of null (reading 'length')\n    at TableHandler.checkProperties (/usr/local/lib/node_modules/azurite/dist/src/table/handlers/TableHandler.js:601:52)\n    at TableHandler.insertEntity (/usr/local/lib/node_modules/azurite/dist/src/table/handlers/TableHandler.js:110:14)\n    at /usr/local/lib/node_modules/azurite/dist/src/table/generated/middleware/HandlerMiddlewareFactory.js:58:18\n    at /usr/local/lib/node_modules/azurite/dist/src/table/generated/ExpressMiddlewareFactory.js:77:63\n    at Layer.handle [as handle_request] (/usr/local/lib/node_modules/azurite/node_modules/express/lib/router/layer.js:95:5)\n    at trim_prefix (/usr/local/lib/node_modules/azurite/node_modules/express/lib/router/index.js:328:13)\n    at /usr/local/lib/node_modules/azurite/node_modules/express/lib/router/index.js:289:7\n    at Function.process_params (/usr/local/lib/node_modules/azurite/node_modules/express/lib/router/index.js:348:12)\n    at next (/usr/local/lib/node_modules/azurite/node_modules/express/lib/router/index.js:280:10)\n    at runMicrotasks (<anonymous>)"
2022-04-28T13:16:50.207Z e1cf5d57-fa43-419f-b58b-59888e23ad2d error: ErrorMiddleware: Set HTTP code: 500
2022-04-28T13:16:50.207Z e1cf5d57-fa43-419f-b58b-59888e23ad2d info: EndMiddleware: End response. TotalTimeInMS=1 StatusCode=500 StatusMessage=undefined Headers={"server":"Azurite-Table/3.17.0"}

Have you found a mitigation/solution?
Dont store nulls... But this is a breaking change for us

Appears to be a duplicate to my issue #1457

thanks, I am looking into this

Thanks for raising this.
I have added a regression test and updated the logic to handle null properties.
I shall try to fast track releasing this fix.

Thank you Edwin for the quick response and fix :)


Docker Build for production in Visual Studio Team Services

Hello.
How can I build a production docker image in Visual Studio Team Services with a Hosted Agent and the Docker task extention? This is what I get (from sample):
2017-08-01T21:51:14.7181020Z ##[section]Starting: Build Image
2017-08-01T21:51:14.7260790Z ==============================================================================
2017-08-01T21:51:14.7274380Z Task         : Docker
2017-08-01T21:51:14.7288640Z Description  : Build, push or run Docker images, or run a Docker command. Task can be used with Docker or Azure Container registry.
2017-08-01T21:51:14.7305650Z Version      : 0.2.4
2017-08-01T21:51:14.7319010Z Author       : Microsoft Corporation
2017-08-01T21:51:14.7332910Z Help         : More Information
2017-08-01T21:51:14.7346710Z ==============================================================================
2017-08-01T21:51:15.1765710Z dc5db21b-6c75-4bc9-a7be-29ba3b63ce8a exists true
2017-08-01T21:51:15.1994480Z [command]/usr/bin/docker login -u ******** -p ******** ********
2017-08-01T21:51:16.1734810Z Login Succeeded
2017-08-01T21:51:16.2035790Z [command]/usr/bin/docker build -f /opt/vsts/work/1/s/Image.Dockerfile -t ********/image -t ********/image:40 /opt/vsts/work/1/s
2017-08-01T21:51:16.2589470Z Sending build context to Docker daemon 557.1 kB
2017-08-01T21:51:16.2661970Z Sending build context to Docker daemon 1.114 MB
2017-08-01T21:51:16.2732880Z Sending build context to Docker daemon 1.671 MB
2017-08-01T21:51:16.2830400Z Sending build context to Docker daemon 2.228 MB
2017-08-01T21:51:16.2949460Z Sending build context to Docker daemon 2.785 MB
2017-08-01T21:51:16.2965860Z Sending build context to Docker daemon 3.296 MB
2017-08-01T21:51:16.2973540Z
2017-08-01T21:51:16.3183630Z Step 1 : FROM microsoft/dotnet AS build-env
2017-08-01T21:51:16.3245000Z Error parsing reference: "microsoft/dotnet AS build-env" is not a valid repository/tag
2017-08-01T21:51:16.3469150Z ##[error]Error parsing reference: "microsoft/dotnet AS build-env" is not a valid repository/tag
2017-08-01T21:51:16.3563210Z [command]/usr/bin/docker logout ********
2017-08-01T21:51:16.3577200Z Remove login credentials for ********
2017-08-01T21:51:16.3627120Z ##[error]/usr/bin/docker failed with return code: 1
2017-08-01T21:51:16.4357120Z ##[section]Finishing: Build Image

@pumaloso, It looks like the build agent you are using is running an older version of Docker.  The Error parsing reference: "microsoft/dotnet AS build-env" is not a valid repository/tag message is what you get when you try to use the multi-stage Docker build feature on an older version of Docker that doesn't support it.  You are either going to need to upgrade the version of Docker on your build agent or not use the multi-stage build feature.

Thanks for your reply! Somehow it got fixed when I changed the Hosted Agent, then changed it back to the Linux Hosted Agent.
Cheers!


Let's go for coffee?

Hi Lex, I'm not sure what I'm doing right now, so I'm just going to say it as is :) While watching your podcasts, I realized that I'm attracted to you. And I was wondering if you would be open to the idea of us meeting for coffee one day? :) In your character, I recognize many core life values that I cherish, and since I don't come across these too often, I decided to give it a chance and reach out, even though I feel very strange and nervous doing so.

Before we grab coffee Professor, I'd like to share that I've developed an RSS website dedicated to Lex Fridman. Being an ardent admirer of Lex Fridman, I built this website utilizing XML feeds sourced from his official podcast RSS on his website. I leveraged PHP for this project.
You can find the code here: Lex Fridman Podcast Website Github .
 If you have any suggestions, feature ideas, or want to report issues, please open an issue or submit a pull request @lexfridman
Best Regards,
Hashaam Zahid


It's impossible to open "Report an issue" or "Request api form" twice in a row

Reproduce on UAT and staging

Click on "report an issue" link in the footer -> close the pop-up on 'x'
Click on "report an issue" link in the footer again -> nothing happens -> bug
Click on "this form link" -> close the pop-up -> click on "report an issue" -> the pop-up appears ok

Note: The same issue is with "Request api form"

Verified on staging successfully


Add ware-freebsd worker

Woooot! That's very cool! I started to fix the first FreeBSD failure :-) https://github.com/python/cpython/pull/108964


🆙 Updates to demo and various packages

@stevejpurves this is maybe going to break thebe and jupyter outputs, we need to circle back to that, but I am going to merge it in and we can figure it out on the other side.


Stuck at unittest discovery.

Type: Bug
Behaviour
Expected vs. Actual
Expected: Testing discovery running fine and show the correct test entry at side bar.
Actual: Testing keep loading ，output of  Python shows that it stuck at unittest_discovry(or something). Then I run the command, it turns out that there are something wrong with home path:
(.env) PS C:\Users\11986\pycraft-game> .\.env\Scripts\python.exe ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\testing_tools\unittest_discovery.py ./test test_*.py
C:\Users\11986\AppData\Local\Programs\Python\Python311\python.exe: can't open file 'C:\\Users\\11986\\pycraft-game\\~\\.vscode\\extensions\\ms-python.python-2022.20.1\\pythonFiles\\testing_tools\\unittest_discovery.py': [Errno 2] No such file or directory

Steps to reproduce:

Install VSCode
Open the config syncing. (Everything works fine on another windows11 device).
Re-launch VSCode, then open Testing sidebar, configure a unittest setting, then the testing module
keeps loading and no response.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.11.1
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Pylance

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Experiment 'pythonSurveyNotification' is active
LSP Notebooks experiment is enabled
LSP Notebooks interactive window support is enabled
> conda info --json
> .\"~\.virtualenvs\pycraft-game-33blQzfa\Scripts\python.exe" ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
> ~\AppData\Local\Programs\Python\Python311\python.exe ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
[ERROR 2022-11-23 11:32:17.87]: Error: Command failed: c:\Users\11986\pycraft-game\"C:\Users\11986\.virtualenvs\pycraft-game-33blQzfa\Scripts\python.exe" c:\Users\11986\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py c:\Users\11986\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
�ļ�����Ŀ¼������������ȷ��

    at ChildProcess.exithandler (node:child_process:408:12)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Socket.<anonymous> (node:internal/child_process:451:11)
    at Socket.emit (node:events:526:28)
    at Pipe.<anonymous> (node:net:687:12) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'c:\\Users\\11986\\pycraft-game\\"C:\\Users\\11986\\.virtualenvs\\pycraft-game-33blQzfa\\Scripts\\python.exe" c:\\Users\\11986\\.vscode\\extensions\\ms-python.python-2022.20.1\\pythonFiles\\get_output_via_markers.py c:\\Users\\11986\\.vscode\\extensions\\ms-python.python-2022.20.1\\pythonFiles\\interpreterInfo.py'
}
> .\.env\Scripts\python.exe ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
> ~\.virtualenvs\pycraft-game-33blQzfa\Scripts\python.exe ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
> .\"~\.virtualenvs\pycraft-game-33blQzfa\Scripts\python.exe" ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
[ERROR 2022-11-23 11:32:19.118]: Error: Command failed: c:\Users\11986\pycraft-game\"C:\Users\11986\.virtualenvs\pycraft-game-33blQzfa\Scripts\python.exe" c:\Users\11986\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\get_output_via_markers.py c:\Users\11986\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\interpreterInfo.py
�ļ�����Ŀ¼������������ȷ��

    at ChildProcess.exithandler (node:child_process:408:12)
    at ChildProcess.emit (node:events:526:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  killed: false,
  code: 1,
  signal: null,
  cmd: 'c:\\Users\\11986\\pycraft-game\\"C:\\Users\\11986\\.virtualenvs\\pycraft-game-33blQzfa\\Scripts\\python.exe" c:\\Users\\11986\\.vscode\\extensions\\ms-python.python-2022.20.1\\pythonFiles\\get_output_via_markers.py c:\\Users\\11986\\.vscode\\extensions\\ms-python.python-2022.20.1\\pythonFiles\\interpreterInfo.py'
}
[ERROR 2022-11-23 11:32:19.121]: Cannot trigger test discovery as a valid interpreter is not selected
Starting Pylance language server.
Python interpreter path: .\.env\Scripts\python.exe
> ./.env/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/printEnvVariables.py
> .\.env\Scripts\python.exe ~\.vscode\extensions\ms-python.python-2022.20.1\pythonFiles\testing_tools\unittest_discovery.py ./test test_*.py
cwd: .
LINTING: Skipping linting from Python extension, since Flake8 extension is installed.
> ./.env/Scripts/activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2022.20.1/pythonFiles/printEnvVariables.py
LINTING: Skipping linting from Python extension, since Flake8 extension is installed.
Send text to terminal: & c:/Users/11986/pycraft-game/.env/Scripts/Activate.ps1
LINTING: Skipping linting from Python extension, since Flake8 extension is installed.

User Settings

envFile: "<placeholder>"

languageServer: "Pylance"

linting
• flake8Args: "<placeholder>"
• flake8Enabled: true

formatting
• provider: "black"

testing
• cwd: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: true

Extension version: 2022.20.1
VS Code version: Code 1.74.2 (e8a3071ea4344d9d48ef8a4df2c097372b0c5161, 2022-12-20T10:29:14.590Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1195G7 @ 2.90GHz (8 x 2918)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.78GB (8.88GB free)

Process Argv
--crash-reporter-id 35a92b14-edd7-4c88-a33d-3363e8361a6b

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1:30587005
282f8724:30602487
gswce1:30612156
iaj6b796:30613358
89544117:30613380
fim-prod:30623723

It seems like that all the path include ~ character would not properly target to my home dir on my computer.
C:\Users\11986\.virtualenvs>python -V
Python 3.11.0
C:\Users\11986\.virtualenvs>python ~
python: can't open file 'C:\\Users\\11986\\.virtualenvs\\~': [Errno 2] No such file or directory

Add os.path.expanduser() on line 42 at file ~\.vscode\extensions\ms-python.python-2022.16.1\pythonFiles\testing_tools\unittest_discovery.py not working, becault the python 3.11 interpritor do not recognize the ~ characcter.
According to the python docs it says: "Changed in version 3.8: No longer uses HOME on Windows."

It seems like there is runnning thread that wouldn't stop itself in the test_file, which makes unittest_discovery.py stuck.
Maybe add a timeout alert is better.

I think we may be making an error in prepending ~ to the path of the file we are executing on your behalf to run the tests.

Hello, could you please attach your user settings.json and workspace settings.json? THanks


Could not fetch Kafka topic message headers and metadata

I want to get topic message headers basically from AWS MSK with Kafka 2.8.1 version. In documentation:
Each header key is listed as a separate column: __header$HeaderKeyName : String and i applied this into my schema like
{     "metricFieldSpecs": [     ],     "dimensionFieldSpecs": [     ...     {       "name": "__key",       "dataType": "STRING"     },     {       "name": "__header$createdAt",       "dataType": "STRING"     }
but not worked. Also i could not fetch offset information via __metadata$offset : String.  I use latest version of Pinot. (I can get key of message via __key without problem)
Could you give me more information about getting headers or metadata with Pinot from Kafka?

I figured it out finally. I set "stream.kafka.metadata.populate": true configuration in tableIndexConfig.streamConfigs and

{
"name": "__metadata$offset",
"dataType": "STRING"
},
{
"name": "__header$channel",
"dataType": "BYTES"
},
{
"name": "channel",
"dataType": "STRING"
}

added these column definitions into dimensionFieldSpecs. Header values are in BYTES type so I converted them to STRING via this code in ingestionConfig.transformConfigs

{
"columnName": "channel",
"transformFunction": "fromUtf8(__header$channel)"
}

So, channel column is visible in Pinot table.


is it possible to have the downloading progress status on Windows/Mac Electron

Hi guys, we are using RocketChat a lot everyday, and it is amazing. But we will always encounter an issue when we try to download the file from RocketChat with the Mac Election version, that we do not know if the file has finished downloading or not. It will be failed to open if the downloading has not completed. If we open the RocketChat through a Chrome tab page, we can see the downloading progress.
So is it possible for Electron to have that? Thanks a lot!

Good point, we will investigate.

We have developed the download page, I you can see the progress there


Update MD file on new branch 2017-11-10_22-23-30

:warning: Validation status: warnings

File
Status
Preview URL
Details

split/test_link_to_con.yml
:warning:Warning

Details

split/updateTestRef1.md
:white_check_mark:Succeeded

split/test_link_to_con.yml

[Warning] Uid(Microsoft.SqlServer.Server) has already been defined in ref2.yml.
Line 1: [Warning] Invalid file link:(~/content.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


please include LICENSE-* files in published -impl crates

The inventory-impl crates published to crates.io do not contain the LICENSE-APACHE and LICENSE-MIT files. For both those licenses, it's necessary to distribute the license text alongside the covered source code. This creates issues for (linux) distributions which redistribute the crate source code.
Adding symlinks from the impl directory to the files in the root of the repository should be enough to fix this, if you're running cargo publish from linux or mac OS.

Thanks for reporting. I published inventory-impl 0.1.10 with the license files.

Wow, that was fast. Thanks!


Only on live site: Prerendering failed unexpected token ,

Hi,
Loving the template, and the new additions!
I've been chasing my tail all day with this one! I thought I was doing something wrong, so downloaded a fresh copy of the master, built it, and published it to my host. I was met with the same error!

An unhandled exception was thrown by the application.
Microsoft.AspNetCore.NodeServices.HostingModels.NodeInvocationException: Prerendering failed because of error: SyntaxError: Unexpected token ,
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at findBootModule (C:\Windows\TEMP\vbqidlto.3pa:111:17)
at findRenderToStringFunc (C:\Windows\TEMP\vbqidlto.3pa:116:28)
at renderToStringImpl (C:\Windows\TEMP\vbqidlto.3pa:75:51)
at C:\Windows\TEMP\5hbcb1is.3vb:114:

Got to love those errors! somewhere there's a stray comma, or at least its getting one when its not expected! This error was saved in the logs, I can't for the life of me figure out where this is from, I can build and run it within visual studio, both debug and release, but put in a production environment and IIS and this bug crops up, I don't use docker but I assume that shouldn't matter.  I can build and deploy the old Angular 5 version with out any trouble, in case that helps.  Maybe its my host, but since everything else seems to work with them I find it unlikely.
Id love to get this running properly, although it seems to be just me with this issue right now!

@MarkPieszak Some strange warnings, is the render string being cut short?
Screenshot Here

webpack --progress --color "--env.prod"

[1] Hash: e72d29fe14db273c010f151c9be159d98bb60111
Version: webpack 4.12.1
Child
Hash: e72d29fe14db273c010f
Time: 63995ms
Built at: 2018-06-25 15:52:41
Asset      Size  Chunks                    Chunk Names
0.js  1.24 KiB       0  [emitted]
main-client.js  1.81 MiB       1  [emitted]  [big]  main-client
WARNING in<EMAIL_ADDRESS>4808:15-36
System.import() is deprecated and will be removed soon. Use import() instead.
For more info visit https://webpack.js.org/guides/code-splitting/
 @ ./ClientApp/boot.browser.ts 2:0-47 13:4-18

WARNING in<EMAIL_ADDRESS>4820:15-102
System.import() is deprecated and will be removed soon. Use import() instead.
For more info visit https://webpack.js.org/guides/code-splitting/
 @ ./ClientApp/boot.browser.ts 2:0-47 13:4-18

WARNING in asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
  main-client.js (1.81 MiB)

WARNING in entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
  main-client (1.81 MiB)
      main-client.js

There is a fix in this thread:
Add this workaround to the webpack.config.js.
The issue itself is being tracked here: #21560

@Gaulomatic I tried that work around, unfortunately it doesn't seem to remove the error with pre-rendering.
I'm not really much use with webpack, so it may be my code as I had to take an educated guess at it, initially I tried the code as is, but was met with an error about not having ts-loader, so I tried awesome-typescript-loader, but the prerender bug was still there.  I then tried just tagging the additional test to the existing like so:
    module: {
      rules: [{
          test: /\.ts$/,
          use: isDevBuild ? ['awesome-typescript-loader?silent=true', 'angular2-template-loader', 'angular2-router-loader'] : '@ngtools/webpack'
      },
        {
          test<EMAIL_ADDRESS>          use: isDevBuild ? ['awesome-typescript-loader?silent=true', 'angular2-template-loader', 'angular2-router-loader'] : '@ngtools/webpack',
          parser: { system: true },
        },
        {
          test: /\.html$/,
          use: 'html-loader?minimize=false'
        },
        {
          test: /\.css$/,
          use: ['to-string-loader', isDevBuild ? 'css-loader' : 'css-loader?minimize']
        },
        {
          test: /\.(png|jpg|jpeg|gif|svg)$/,
          use: 'url-loader?limit=25000'
        },
        ...sharedModuleRules
      ]
    },
    plugins: [new CheckerPlugin()]
  };

And a couple of other ways. Sadly no matter what, there is still an unexpected token ',' and in addition because I'm so skilled at breaking things, webpack errors now.

 When it runs, it runs great. But the meme "Don't touch a running system" was invented by somebody working with WebPack :-)
I just rewrote my complete WebPack config today and yesterday - it was a nightmare. I altered the paths to /dist/vendor and /dist/application to seperate
Nevertheless, maybe I can help you with your config. Do you have a repo?

At some point I'm going to have to learn webpack properly rather than the couple of hacks I've picked up along the way!  I'm actually getting the error out of the box with this repo, and only when published to a server!? The warnings from webpack aren't really an issue as far as I can see, just an irritation.  The problem comes when the repo is built for production and published to my host.  locally everything is fine, and the only issue is the webpack warnings. If I navigate to the temp site I get "Preredndering failed due to an unexpected token ," which combined with the size warning is what made think maybe something was being cut short, but it could just as easily be a stray comma.

maybe nodejs is not installed or the wrong version on the server?

put node.exe to virtual folder on your hosting

I'm using shared hosting so a virtual directory isn't an option.
I noticed that we can now do self contained publishing in VS2017, can we add node.js to that?
My host says that the version installed on the servers is 8.9.4 but I need to upgrade to a semi-dedicated plan to make use of it. Which is odd since I have had all other versions of this repo working on their servers.

Ohhh. I don't love this repo, cause it contains a lot of garbage... you are use smartepasp?

I am using smarterasp! I generally strip this repo down as it's the SSR that I'm really after, and when I try to make my own from scratch it never seems to work! I've looked at a few repo's and this one seems to be the most stable, the only thing I miss is the full angular CLI integration, which is now on the todo list.

So if are you use smarterasp there is virtual folder in some preferences)
[https://www.smarterasp.net/support/kb/a1922/how-to-set-the-virtual-directory-from-your-hosting-account.aspx](check here)
and then put into this virtual folder your node.exe from direct path in your pc)
same do i) but when i dont do this i have an another exception.
 public void Configure (IApplicationBuilder app, IHostingEnvironment env, IWeatherRepository _weatherRepository) {
            if (env.IsDevelopment ()) {
                app.UseDeveloperExceptionPage ();
            } else {
                app.UseExceptionHandler ("/Home/Error"); < ----- here
            }

but it was another version of this repo (it was dotnet 2.0 and angular 5).
this version i didn`t try to host/
at first try to create vurtual folder with node.

I didn't know that was even there :) do I just create a virtual folder (I'll call it nodejs) upload node.exe, then just publish? Do I need to configure a path anywhere?

Well damn! that worked thanks @hartov


Investigate If OS Inventory Management Info Would Be Useful in Forseti

https://cloud.google.com/compute/docs/instances/os-inventory-management

It is a crucial integration, thanks for adding this in the roadmap. It would be great to alert on:

VMs that do not collect OS inventory at all,
VMs that require updates
VMs that have old packages (this is almost the same as above)

We do not currently have bandwidth to work on this feature. Closing it; We can revisit if there is a more customer interest for this feature in the future.


[cli] should support a global flag of --database-url (shorthand of -D) in addition to DATABASE_URL

My mistake on the PR message. This issue has been addressed and can be closed


'valueForSeries' doesn't exist anymore

Hi,
As said in the title, I try to use this function to get a vertical line showing value
func didTouchChart(chart: Chart, indexes: Array<Int?>, x: Float, left: CGFloat) {
for (serieIndex, dataIndex) in enumerate(indexes) {
if dataIndex != nil {
// The series at serieIndex has been touched
let value = chart.valueForSeries(serieIndex, atIndex: dataIndex)
}
}
}
But Xcode give me an error. Any clue to fix  that ?
Thanks!

Sorry, mismatch with swiftcharts


Ignore invalid actions

added validation check before middleware processing. Actions that are not plain objects or don't have a type property will be ignored and passed to next middleware.

looks great, thanks @amit1911


Compile fails via Carthage with Xcode 6.3 / iOS 8.3 "Unsupported architecture"

Possibly related to #76?
I'm not entirely sure what is going on here, it seems that the entire build is blowing up with a bad architecture, as if it were forcing arm64 with the simulator or something:
$  carthage update
*** Fetching SwiftHTTP
*** Checking out SwiftHTTP at "0.9.4"
*** xcodebuild output can be found in /var/folders/fk/y_3v6btd0s911nzy83hf6s8h0000gn/T/carthage-xcodebuild.Upse7i.log
*** Building scheme "SwiftHTTP" in SwiftHTTP.xcodeproj
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/include/sys/cdefs.h:680:2: error: Unsupported architecture
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/include/machine/_types.h:34:2: error: architecture not supported
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/include/sys/_types.h:55:9: error: unknown type name '__int64_t'; did you mean '__int128_t'?
...
<unknown>:0: error: too many errors emitted, stopping now
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/System/Library/Frameworks/CoreFoundation.framework/Headers/CoreFoundation.h:11:10: error: could not build module 'Darwin'
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/System/Library/Frameworks/Foundation.framework/Headers/Foundation.h:6:10: error: could not build module 'CoreFoundation'
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/include/objc/objc.h:31:10: error: could not build module 'Darwin'
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/include/mach-o/arch.h:32:10: error: could not build module 'Darwin'
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator8.3.sdk/usr/include/dispatch/dispatch.h:25:12015-04-20 17:35:59.051 xcodebuild[54181:2009948] [MT] iPhoneSimulator: SimVerifier returned: Error Domain=NSPOSIXErrorDomain Code=53 "Simulator verification failed." UserInfo=0x7fb4961811e0 {NSLocalizedFailureReason=A connection to the simulator verification service could not be established., NSLocalizedRecoverySuggestion=Ensure that Xcode.app is installed on a volume with ownership enabled., NSLocalizedDescription=Simulator verification failed.}
** BUILD FAILED **

The following build commands failed:
	CompileSwift normal arm64 /Users/piz/sandbox/Pied Piper/Carthage/Checkouts/SwiftHTTP/HTTPRequestSerializer.swift
	CompileSwift normal arm64 /Users/piz/sandbox/Pied Piper/Carthage/Checkouts/SwiftHTTP/HTTPResponseSerializer.swift
	CompileSwift normal arm64 /Users/piz/sandbox/Pied Piper/Carthage/Checkouts/SwiftHTTP/HTTPTask.swift
	CompileSwift normal arm64 /Users/piz/sandbox/Pied Piper/Carthage/Checkouts/SwiftHTTP/HTTPUpload.swift
	CompileSwiftSources normal arm64 com.apple.xcode.tools.swift.compiler
(5 failures)

Same issue occurs with Xcode 6.3.1. For what it is worth the two other items in my Cartfile build without issue.

Ok interesting. I believe I already fixed #76 with the 0.9.4 release. I don't personally use Carthage, but I did just test building the framework in my test iOS and OS X projects and the built fine on xCode 6.3. From what I understand, Carthage only requires the schemes of the xcodeproj to be shared, which they are. I came across this thread:
https://github.com/Carthage/Carthage/issues/381.
I might try installing the Xcode Command Line Tools (from https://developer.apple.com/downloads/index.action?name=Xcode) see if that resolves the issue.

Looks like this isn't a SwiftHTTP issue but instead might be caused by Carthage/Carthage#417

Interesting, nice catch. Let's hope for a quick fix.


unmatched parenthesis

Got a new error with the latest melpa version (20160106.101),
seems to have an unmatched parenthesis in "cmake-ide.el", line 342

Should be fixed in the latest version. Sorry for pushing a buggy one.


[lexical-react] Feature: Add aria-errormessage and aria-invalid support to LexicalContentEditable

Description
Adds the ability to set aria-errormessage and aria-invalid attributes on the Lexical contenteditable div. This allows us to signal that the text input is in an invalid state and to associate it with another element containing an error message.
Impl
Runtime
LexicalContentEditableElement.tsx already spreads all props that are passed to it, so passing aria-errormessage or aria-invalid already works at runtime, but it also explicitly supports camelCase version of aria attributes (e.g. ariaDescribedBy) so we need to add support for ariaErrorMessage and ariaInvalid.
Types
The TS type already implicitly included all HTML attrs via React.AllHTMLAttributes<HTMLDivElement>, but Flow doesn't have a nice type like that, so we allowlist certain attrs. So we update the Flow type to include aria-errormessage and aria-invalid.
I also noticed that we missed aria-describedby, so I added that as well.
And I also noticed that we misspelled aria-labelledby, but fixing that might technically be a breaking change since it could cause a Flow error. So I skipped that for now, but it will not work correctly until we fix the spelling issue, so that's something to consider for the future.
Test plan
Added ariaErrorMessage and ariaInvalid attrs to the LexicalContentEditable in the Lexical Playground and confirmed that the props flowed through to the DOM.

Good catch! Do you want me to fix the other attrs while I'm in there? Or just stick to aria-errormessage/aria-invalid so that we're strictly backwards compatible? (Fixing the other attrs would technically not be backwards compatible since the kebab-case versions are all getting voided out today)

Good catch! Do you want me to fix the other attrs while I'm in there? Or just stick to aria-errormessage/aria-invalid so that we're strictly backwards compatible? (Fixing the other attrs would technically not be backwards compatible since the kebab-case versions are all getting voided out today)

IMO let's just do these new ones for now. Ideally, we'd get rid of these properties altogether and use the DOM provided ones. We can look into bundling this into a minor patch


Accept flex > 2.5.x in configure.

backport from
https://github.com/postgres/postgres/commit/32f15d05c80044335f97347b5406f6736c06a033

Merged into master. Thank you so much @yannick!


Fix nested joins

This makes nested joins work and also improves the validation of join using by doing the following:

Introduce JoinRelation as AnalyzedRelation which represents joins as data structure
Derive the join pairs from the newly introduced JoinRelation
Taking the join conditions into account when selecting the join pairs
Improves the validation/evaluation of join using based on the output, not relying directly lhs/rhs relation-names

fixes https://github.com/crate/crate/issues/13503
Summary of the changes / Why this improves CrateDB
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Thanks for the feedback.
This needs one more iteration, also the changelog entry is missing.

@mkleen Thank you for the work on this, please ping and I will also review once you complete the new iteration.

Ready for another review.

Thanks for the feedback. I am wondering if it maybe makes sense to split this into two prs. One to resolve the nested join issue, the other one for using.

Thanks for the feedback. I am wondering if it maybe makes sense to split this into two prs. One to resolve the nested join issue, the other one for using.

If it's not too much trouble, why not, we can have 2 separate changelog entries as well.

So the initial issue was the following query, which works now.
SELECT
  *
FROM
  j1
  JOIN (
    j2
    JOIN j3 ON j2.x = j3.x
  ) ON j1.x = j2.x

However, we can currently not go infinitely nested the following query does not work and I would consider this out-of-scope for a fix. This would require significant changes in the way joins are treated internally. This is anyway not a common use case.
SELECT
  y,
  z
FROM
  a
  JOIN (
    b
    JOIN (
      c
      JOIN a ON c.z = a.x
    ) temp1 ON b.y = temp1.x
  ) temp2 on a.x = temp2.x;

My suggestion is to throw a reasonable error message and leave it as is. @matriv @mfussenegger @BaurzhanSakhariev

Ready for another review. I split this pr now. The join using stuff goes into a follow-up.


[BUG] Images ignores dataLocality of storageClass

Hi!
When I create a new image and select a StorageClass, the new StorageClass for that image ignores the longhorn parameters.
Steps to reproduce the behavior:

Create a new StorageClass
Add parameter dataLocality: best-effort, strict-local etc...
Create a new image and select the newly created StorageClass
The Longhorn parameters for the image have been lost
New virtual machines created using this image have also lost parameters...

Expected behavior
The Longhorn parameters defined in the StorageClass must be reused when creating the image.
The same parameters must be reused when creating a VM from this image.
Environment

Harvester ISO version: 1.2.1

Additional context
If attach an extra volume to VM using the StorageClass with defined longhorn parameters, everything will work fine.
But not everyone needs extra volumes.

By the way, more... If the problem with using strict-local is only in migrating virtual machines when updating Harvester, then maybe just stop such virtual machines instead of migrating?

Hi @SnelsSM
Harvester supports data locality for images since v1.3.0 https://docs.harvesterhci.io/v1.3/advanced/storageclass#data-locality-settings.
And Harvester doesn't support strict-local because it can affect certain operations such as VM Live Migration

@WebberHuang1118

And Harvester doesn't support strict-local because it can affect certain operations such as VM Live Migration
But  live migration is not always necessary. Why not just turn off such virtual machines if live migration is not required?

@SnelsSM
Strict local makes LH volume have one local replica only, however, live migration is required for the Harvester upgrade.
And one replica also reduces the data availability.

Strict local makes LH volume have one local replica only, however, live migration is required for the Harvester upgrade.
And one replica also reduces the data availability.

A single replica without defined dataLocality also disrupts the operation of some virtual machines when upgrading Harvester, and live migration in this case is pointless.
It might be better to be able to customize the upgrade strategy for Harvester: force live migrate, live migrate if possible, shutdown VMs, etc...
Too many cases when VMs exists just for temporary workload. There is no point migrating virtual machines on upgrade when stopping these virtual machines is acceptable.
As a bonus, it will be possible to use strict-local painlessly, load the network less and have better volume performance. Profit.

It might be better to be able to customize the upgrade strategy for Harvester: force live migrate, live migrate if possible, shutdown VMs, etc...

@SnelsSM Thanks for your suggestion, we will discuss on it.
Just have some clarification:

A single replica without defined dataLocality also disrupts the operation of some virtual machines when upgrading Harvester, and live migration in this case is pointless.

As a bonus, it will be possible to use strict-local painlessly, load the network less and have better volume performance. Profit.

The single replica doesn't disrupt live migration, and if you want to avoid network overhead, considering make use of data locality with best-effort. As a result, LH will always try to build a local replica


Latest Docker Container Fails to Start

I was running this before, but when I pulled the latest version I no longer can get the docker container to start. Below is what is being logged to the console.
$ next start -p 39456
ready - started server on <IP_ADDRESS>:39456, url: http://localhost:39456
Error: Configuration property "header_title" is not defined
at Config.get (/app/node_modules/config/lib/config.js:182:11)

at Object.<anonymous> (/app/next.config.js:6:29)

at Module._compile (node:internal/modules/cjs/loader:1101:14)

at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)

at Module.load (node:internal/modules/cjs/loader:981:32)

at Function.Module._load (node:internal/modules/cjs/loader:822:12)

at Module.require (node:internal/modules/cjs/loader:1005:19)

at require (node:internal/modules/cjs/helpers:94:18)

at Object.loadConfig [as default] (/app/node_modules/next/dist/server/config.js:345:34)

at async NextServer.loadConfig (/app/node_modules/next/dist/server/next.js:112:22)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@endergrimm The default configuration has been updated. Since the config directory (/config) is a Docker volume, it is not deleted when you recreate the container, and default configuration in that volume is therefore outdated. If you delete the volume before you run the Clipface container, it should work as expected. Make sure to back up any config changes you have made first.
In hindsight, making the config directory a volume by default was probably a bad idea, and I will change that. Alternatively, I could perhaps move the default config to a different directory, if that's possible. I will look into it.

Yep, that fixes it. Thanks for your great work! I have this setup with synctoy and shadowplay's automatic highlights to upload clips to a google drive mount. Works out pretty slick to just have my highlights show up on my site.


Lacking support for sysctl value validation

In addition to the existing modules we also need support for sysctl via sysctl.get. There are a handful of CIS checks that validate sysctl values that we'll need to verify.

#34 has sample yaml

Fixed in #35


removed some mistakes from previous pull request

Current changes are to Schedule web-view.

added timezone to db file

Added char_set_client on upgrade_v9

As discussed with @Lunarium-Host this PR can be closed.


Dart2JS does not give a static warning if not implementing inherited method interface with inherited method.

Example:
class C {
  int foo(int x) => x;
}
abstract class D {
  int foo(int x, [int y]);
}
class E extends C implements D {}
typedef int foo2(int x, [int y]);
main() {
  D d = new E();
  foo2 foo = d.foo;
  print(foo(2,2));
}
This should give a static warning since E is a non-static class that doesn't have a method matching the super-interface method D.foo.
It has an inherited method of the same name, but it's not matching (spec, section 7.10).
Gilad: Should this be a compilation error instead?

now handled by CFE


Authentication.md

This is not a question just a query, it is mentioned in authentication.md that facebook OAuth is not working but in my case, it is working completely fine.

Oh! Thanks for flagging that! I think that information in the documentation is wrong, will take a look!


fixed issues with creating infra

Signed-off-by: zhu jing yang<EMAIL_ADDRESS>

fixed the user balance problem


trying out graphql with institutions

Back end structure

/server

/graphql

/entities: GraphQL entity models (implements `models)
/resolvers: GraphQL resolvers (uses schemas)

/models: Typescript interfaces for base data models
/schemas: Mongoose data models (implements models)

Front end structure

/web

/src/API

/queries: User defined graphql queries

/types: Autogenerated Typescript types for aforementiend graphql queries

Steps to generate types on frontend

Run server
Run npm run generate
Generated types will be located in web/src/API/queries/types

Closing in lieu of #43


Quick Fix for #167

Extend CredentialManager to accept refresh_token and add warning message for deprecated GenerateToken
Example usage:
var clientId = "myClientId";
var clientSecret = "myClientSecret";
var accessToken = "myAccessToken";
var refreshToken = "myRefreshToken";

var client = new Client(
    SystemClock.Instance, "https://api.netatmo.com/",
    clientId,
    clientSecret);

client.ProvideOAuth2Token(accessToken, refreshToken);
await client.RefreshToken();
var stationsData = await client.Weather.GetStationsData();

I wrote a small test script to see if it works, below was the output:
Manually provide initial AccessToken & RefreshToken:

AccessToken: ##############
RefreshToken: ##############
ExpiresAt: 2023-07-17T07:23:00Z
ReceivedAt: 2023-07-17T07:22:40Z
**********************************

Request Refresh Token:

AccessToken: ##############
RefreshToken: ##############
ExpiresAt: 2023-07-17T10:22:41Z
ReceivedAt: 2023-07-17T07:22:41Z
**********************************

Livingroom Temperature: 24,2
Office Temperature: 24,8
Outdoor Temperature: 19,6

During init of a Client the token is valid for 20 seconds. After calling RefreshToken() the token gets a validity from the API with 3 hours. I was also able to get my data from Netatmo API.


oha: 0.5.6 -> 0.5.7

Diff: https://github.com/hatoo/oha/compare/refs/tags/v0.5.6...v0.5.7
Changelog: https://github.com/hatoo/oha/blob/v0.5.7/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 218273 run on aarch64-darwin 1

1 package built:

oha


Can't install 1.8.2 into VS2015 targeting .NET 4.7.2

Do you know how to resolve this error?  I've tried NuGet interface and PM directly.  This is in an empty template C# project.
Install failed. Rolling back...
Package 'R.NET.1.8.2' does not exist in project 'WindowsFormsApplication1'
Package 'R.NET.1.8.2' does not exist in folder 'c:\users\jason.chittenden\documents\visual studio 2015\Projects\WindowsFormsApplication1\packages'
Could not install package 'R.NET 1.8.2'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
========== Finished ==========

@jtchittenden - I didn't get this error in VS2017, but was able to replicate in a version of VS2013.  Given that it works in a newer version of VS, it may be something with older VS versions, not the package.  Will see if I can get this working in my VS2013 instance.

It looks like R.NET (starting in 1.8) updated its nuspec to target .NETStandard 2.0, which maintains compatibility with .NET Framework 4.7.2.  It sounds like there are some known issues with NuGet in older VS instances not being able to translate that it should in fact work with 4.7.2.
I think your best options are to update to a newer version of VS, or if that's not possible, look at compiling your own version of R.NET locally and linking that into your project.

I updated to VS 2019.  I now have a whole bunch of other problems, but R.NET ain't one of them.  Thanks @Irasmus

I think I want this on a t-shirt...

I updated to VS 2019. I now have a whole bunch of other problems, but R.NET ain't one of them.

Thanks for the report back, and sorry that the upgrade is causing other issues.


Added options parameters to insert and delete methods.

@danielerota do you have plans to continue work on PR?

@Smolevich no, we have done.

Add test case, please

Closing due to inactivity. Please open new PR with tests as well.


The use of cyber schedule

System information

OS Platform and Distribution ( Linux Ubuntu 14.04):
Apollo installed from (source):
Apollo version (3.5):

Hello, Apollo:
In Cyber's use case presentation, the configuration for scheduling is as follows.
scheduler_conf {
policy: "classic"
classic_conf {
groups:   [
{
name: "group1"
process_num: 16
affinity: "range"
cpuset: "0-7,16-23"
processor_policy: "SCHED_OTHER"
process_prio: 0
task:     [
{
name: "ABC"
prio: 2
}
]
}
.....
Why are few modules in Apollo using Cyber in this way?

Hi, @breakisx, a process has a corresponding schedule conf， many modules in Apollo are loaded into a process to start using the compute_sched.conf or control_sched.conf.

only some use dataprovider key modules using the scheduler

Currently closing this issue. @breakisx  if you have any additional questions, feel free to reopen it!


Fix syntax to correspond to the correct naming of contextIdPattern

Thanks this PR has been merged. Can you close.


Import slow down

Hi,
I was trying to run the demo on an AWS instance and was running into errors/slow down after I imported 12,000,000 paragraphs.
Instance Details:
g4dn.12xlarge
4 T4 GPUs
48 vCPU
192 GB RAM
Ubuntu 18.04 OS
After I import 12 million paragraphs, the machine performance considerably slows down. I start getting a batch creation timeout message for a batch size of 512, and I continue to get the message when I reduce the batch size to 50. Any ideas why the process slows down so much? The "vectorCacheMaxObjects":<PHONE_NUMBER>00 so I know that is not the issue.

Hi @murak038 – apologies for the slow response.
Would you mind bringing this question to our Slack channel? More people might benefit from the solution there.


Build for ARM MacBook M1 spec

Dear Solace.,
We have difficulties on some of our dev machines - them being ARM M1 MacBook Pros. I've downloaded the osx packages from your download site and when trying to build the examples i see:
gcc -g -I.. -I../include -I. -DPROVIDE_LOG_UTILITIES -g -m32 -c HelloWorldPub.c -o HelloWorldPub.o
gcc -g -o HelloWorldPub HelloWorldPub.o -L../lib -L../obj_Linux26-i386_debug/lib -lsolclient -m32
ld: unknown/unsupported architecture name for: -arch armv4t
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [HelloWorldPub] Error 1

A clear token that the libs are only available for x86. If you aren't planning to support M1 anytime soon - maybe you can send me to instructions where we can build these libraries ourselves? The README insists on installing them and I don't see build-from-source instructions.

Hi @remster
You appear to have addressed your query to Solace & mentioned an issue with the Solace API. We aren't Solace & can't offer Solace support.
I can see similar queries on the Solace discussion forums :
https://solace.community/discussion/1074/solace-pubsub-standard-is-not-starting-on-mac-with-m1-chip
https://solace.community/discussion/1291/solace-pubsub-standard-docker-image-for-m1-mac
You could open a ticket there, or contact Solace support if you are a Solace customer.
The KDB+ interface for Solace that this repo represents currently doesn't support Arm based Macs (and will only be possible after Solace update their client APIs to enable support).


'System.Collections.Generic.KeyNotFoundException' in EngineIoClientDotNet.dll when using Socket

I use SocketIOClientDotNEt in WPF .net 4.5 and I get this exception when using websocket.
All I do is Emit an event, and give it a new AckImpl callback, but sometimes I got this error.

I have the same problem. Any info?

This has been fixed in the beta version. (the fix was a switch to a concurrent queue).  Download the beta version from NuGet and you should be all set.

Thank you very much. No problems now.


Update for Mongoid 5

Bumping version to 4.0.0, as there are some backward incompatible changes

Thanks for this @wa0x6e - merging it in now

Have released version 4.0.0 to rubygems :cake: :beers:

Great, thanks


[BUG] OSS Card Wallet v1.4.0 Build 25 Crash On Startup

Which app is your issue for
OSS Card Wallet
Version
OSS Card Wallet(android): v1.4.0 Build 25
app-arm64-v8a-release.apk
What platform are you using?
Android
OS Version
Android 15 (GrapheneOS<PHONE_NUMBER>)
What happened?
Latest release (from github releases/Obtainium) crash at startup
Relevant log output
type: crash
osVersion: google/cheetah/cheetah:15/AP3A.241105.007/2024112700:user/release-keys
flags: dev options enabled
package: com.akylas.cardwallet:25, targetSdk 34
process: com.akylas.cardwallet
processUptime: 356 + 242 ms
installer: com.android.packageinstaller

java.lang.RuntimeException: Unable to start activity ComponentInfo{com.akylas.cardwallet/com.akylas.cardwallet.MainActivity}: com.tns.NativeScriptException: Calling js method onCreate failed
Error: Main entry is missing. App cannot be started. Verify app bootstrap.
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4061)
	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4248)
	at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:112)
	at android.app.servertransaction.TransactionExecutor.executeNonLifecycleItem(TransactionExecutor.java:174)
	at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:109)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:81)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2645)
	at android.os.Handler.dispatchMessage(Handler.java:107)
	at android.os.Looper.loopOnce(Looper.java:232)
	at android.os.Looper.loop(Looper.java:317)
	at android.app.ActivityThread.main(ActivityThread.java:8744)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:580)
	at com.android.internal.os.ExecInit.main(ExecInit.java:50)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:369)
Caused by: com.tns.NativeScriptException: Calling js method onCreate failed
Error: Main entry is missing. App cannot be started. Verify app bootstrap.
	at com.tns.Runtime.callJSMethodNative(Native Method)
	at com.tns.Runtime.dispatchCallJSMethodNative(SourceFile:1)
	at com.tns.Runtime.callJSMethodImpl(Unknown Source:100)
	at com.tns.Runtime.callJSMethod(SourceFile:1)
	at com.tns.Runtime.callJSMethod(SourceFile:2)
	at com.tns.Runtime.callJSMethod(SourceFile:3)
	at com.akylas.cardwallet.MainActivity.onCreate(SourceFile:1)
	at android.app.Activity.performCreate(Activity.java:9055)
	at android.app.Activity.performCreate(Activity.java:9033)
	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1536)
	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4043)
	... 15 more

Code of Conduct

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

@Quince-Pie thanks for reporting and really sorry! fix is building right now.
Will be published tomorrow on izzydroid though. Github and playstore coming soon

@farfromrefug Thank you for the quick response, you're amazing. The new GH release fixes the crash for me.


Update scalar_functions.md

Remove extra space in reference to list_any_value
Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Thanks again @Abdullahsab3


What about a bot? Is it possible to make the bot built-in?

Is it possible to create a bot that is a member of each chat inside of the tenant? Group chat or private, it doesn't matter. I need a possibility to type to the bot from any channel and bot should answer me on that channel. What is more, I shouldn't install the bot myself. It should be built-in or should be added automatically when a channel is created.

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

ID: 8d33f55c-db55-923e-544f-fccb97f3c7a3
Version Independent ID: 9cb02e00-311e-ec7d-c422-ae1cb9e6d31e
Content: Use built-in and custom tabs in Microsoft Teams - Microsoft Teams
Content Source: Teams/built-in-custom-tabs.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@Dmitresky thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


DEVELOP.md

Can you please add

Go (and the min version)
jq (and the min version)
to the dependencies for building.

Also aws is required (even if you are not building for AWS e.g. build -only=virtualbox-iso)

Hi @lummie,
Sorry for the delay. This will get merged in from here before the next release.


Create many to many DB relationship with movies and posters

cc @spotlightishere

Closing as I forgot why I planned to do this


Frontend Testing: Preparing for Saga Tests

Changes:

Added<EMAIL_ADDRESS>Restructured ./src/sagas/index.ts into separate files to ease testing.

Pull Request Test Coverage Report for Build 1834

42 of 227 (18.5%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 25.021%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sagas/playground.ts
8
13
61.54%

src/sagas/login.ts
5
11
45.45%

src/sagas/workspaces.ts
24
198
12.12%

Totals

Change from base Build 1831:
0.2%

Covered Lines:
1304

Relevant Lines:
4340

💛  - Coveralls


SPI Driver apparently not working as expected

I'm attempting to communicate between my esp32 and an ili9341 via SPI, however it seems none of the commands I send actually do anything. After testing a 'demo' code without the std I'm being led to believe there is something
The following is the current code using the std:
use std::time::Duration;

use display_interface_spi::SPIInterface;
use embedded_graphics::{pixelcolor::Rgb565, prelude::*};
use esp_idf_hal::{
    delay::Ets,
    gpio::PinDriver,
    peripherals::Peripherals,
    spi::{config::*, SpiDeviceDriver, SpiDriver, SpiDriverConfig, SPI2},
};
use esp_idf_sys as _;

use mipidsi::Builder;

fn main() -> anyhow::Result<(), Box<dyn std::error::Error>> {
    esp_idf_hal::sys::link_patches();

    let peripherals: Peripherals = Peripherals::take()?;

    let mut delay = Ets;

    let dc = PinDriver::input_output_od(peripherals.pins.gpio2)?;
    let mut rst = PinDriver::input_output_od(peripherals.pins.gpio4)?;
    rst.set_high()?;

    let sck = peripherals.pins.gpio18;
    let miso = peripherals.pins.gpio19;
    let mosi = peripherals.pins.gpio23;
    let cs = peripherals.pins.gpio15;

    let spi = SpiDriver::new::<SPI2>(
        peripherals.spi2,
        sck,
        mosi,
        Some(miso),
        &SpiDriverConfig::new(),
    )?;

    let spi_device = SpiDeviceDriver::new(spi, Some(cs), &Config::new())?;

    let di = SPIInterface::new(spi_device, dc);

    let mut display = Builder::new(mipidsi::models::ILI9341Rgb565, di)
        .reset_pin(rst)
        .init(&mut delay)
        .unwrap();

    display.clear(Rgb565::BLACK).unwrap();

    loop {
        std::thread::sleep(Duration::from_millis(100));
    }
}

with non-std I have:
#![no_std]
#![no_main]

use embedded_hal_bus::spi::ExclusiveDevice;
use esp_backtrace as _;
use hal::{
    clock::ClockControl,
    delay::Delay,
    gpio::{IO, NO_PIN},
    peripherals::Peripherals,
    prelude::*,
    rtc_cntl::Rtc,
    spi::{master::Spi, SpiMode},
    timer::TimerGroup,
};

use embedded_graphics::{pixelcolor::Rgb565, prelude::*};

use display_interface_spi::SPIInterface;

use mipidsi::{models::ILI9341Rgb565, Builder};

use fugit::RateExtU32;

#[entry]
fn main() -> ! {
    let peripherals = Peripherals::take();
    let system = peripherals.SYSTEM.split();
    let clocks = ClockControl::boot_defaults(system.clock_control).freeze();
    let io = IO::new(peripherals.GPIO, peripherals.IO_MUX);

    let mut rtc = Rtc::new(peripherals.LPWR, None);
    let timer_group0 = TimerGroup::new(peripherals.TIMG0, &clocks, None);
    let mut wdt0 = timer_group0.wdt;
    let timer_group1 = TimerGroup::new(peripherals.TIMG1, &clocks, None);
    let mut wdt1 = timer_group1.wdt;
    rtc.rwdt.disable();
    wdt0.disable();
    wdt1.disable();

    let mut delay = Delay::new(&clocks);

    let dc = io.pins.gpio2.into_push_pull_output();
    let mut rst = io.pins.gpio4.into_push_pull_output();
    rst.set_high();

    let sck = io.pins.gpio18;
    let miso = io.pins.gpio19;
    let mosi = io.pins.gpio23;
    let cs = io.pins.gpio15;

    let spi = Spi::new(peripherals.SPI2, 1.MHz(), SpiMode::Mode0, &clocks).with_pins(
        Some(sck),
        Some(mosi),
        Some(miso),
        NO_PIN,
    );

    let spi_device = ExclusiveDevice::new_no_delay(spi, cs.into_push_pull_output()).unwrap();

    let di = SPIInterface::new(spi_device, dc);

    let mut display = Builder::new(ILI9341Rgb565, di)
        .reset_pin(rst)
        .init(&mut delay)
        .unwrap();

    display.clear(Rgb565::BLUE).unwrap();

    loop {
    }
}

The non-std code works as expected, which makes me beliece there is a mistake in the SpiDeviceDriver and SpiDriver objects, however after reading all the docs I could I did not find the mistake in my implementation, therefore I am wondering if there is a bug in those classes.

Closing it, it was my mistake, the dc and rst pin were input_output_od and should only be output.


fix: [IDP]: Added the steps to create pipeline variables

Description

Please describe your changes: Added the steps to create pipeline variables
Jira/GitHub Issue numbers (if any): ______________________________
Preview links/images (Internal contributors only): __________________

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
PRs must meet these requirements to be merged:

[x] Successful preview build.
[x] Code owner review.
[x] No merge conflicts.
[x] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6663cd2aaa149e6ff27b60e0--harness-developer.netlify.app


mvcc: reduce value clone in prewrite

What have you changed? (mandatory)
take value from mutation instead of clone
What are the type of the changes? (mandatory)

Improvement (non-breaking change which is an improvement to an existing feature)

How has this PR been tested? (mandatory)
No need
Does this PR affect documentation (docs/docs-cn) update? (mandatory)
No
Does this PR affect tidb-ansible update? (mandatory)
No

em, can you show me where to reduce the value clone?

@siddontang the original L171 and L190

The origin L171 handles short value, but origin L190 handles not short value, seem not the same? @Connor1996

@siddontang  so it makes if-else in L179

LGTM


Swagger-UI intergration regression can't provide custom plugins, presets etc

We have used the swagger-ui-react library due to some know issues in swagger-ui library when used with React 16.x versions.
But the swagger-ui-react flavor is not configurable as much as it is with the default version. So we will need to :monkey_face:  patch the swagger-ui library until a proper configuring mechanism introduces to swagger-ui-react component.

Related to : https://github.com/wso2/product-apim/issues/4762

Fixed in APIM 3.0.0 Alpha


Md basic shell

Resolves #1
Adding basic Auth0 functionality from Todo app, with users and admins

Assuming this is just pulling in the starter code.. it's too big to review, so LGTM I guess lol

It is just the starter code


Code for deployment

I want API server to cache Spotify Recommendation feed response.
And Netlfiy didn't have this capability for set API servers without using Lambda.
Let move hosting to GCP and use Cloud Storage to hosting the frontend and Cloud Run hosting API.

https://www.pulumi.com/docs/get-started/
Let use pulumi for setup infrastructure.
Probably using Go / Python rather than TS , to get chance to expose other language features.

For ref, https://github.com/pulumi/examples/blob/master/gcp-py-cloudrun-cloudsql/main.py


Fixing goreleaser config for removed functionality

Background
This has been deprecated, and as of the lastest release has been removed.  We have to make this change in order for the latest goreleaser to build
More info: https://goreleaser.com/deprecations/#archivesreplacements
Testing completed

[x] Ran a build locally

I actually don't know the answer to why we're changing the name.  In this PR, I'm trying to make no functional changes and keep the naming convention the same as yesterday.


Add 1.18 generics support for go lexer

Add new predeclared identifiers: any and comparable
Add new operator for type parameters: ~ and |

Ref: https://go.dev/ref/spec
Close #2164

Perfect, thanks!


Add pilots

Adds piloting / The Garage functionality to the Rigs smart contract and associated tests and deployment changes.

I see that artifacts/local.db has some changes. There should't be any changes there, or let me know why there is. If I'm correct, you should revert that change.

Closing in favor of https://github.com/tablelandnetwork/rigs/pull/285, which maintains verified commits and fixes the artifacts/local.db issue noted above.


Bot will only answer to users

Hey,
I've developed a GUI for sidekick, as I post in the channel with my bot Sidekick won't answer.
Is this intended behavior? Is there a way to toggle if it will answer other bots?

not yet. #176 ?

Hadn't found that one, thanks for the answer.


Remove ServiceClaim Webhooks

Story
As a Primaza Developer,
I would like to have ServiceClaim ValidatingWebhooks removed
so that I reduce Primaza impact at Cluster level
Background
Actual ServiceClaim life-cycle is as depicted in the following diagrams:
flowchart TD
    subgraph state
        sStart((Claim\ncreated))
        sPending[Pending]
        sResolved[Resolved]

        sStart --> sPending
        sPending <--> sResolved
    end
    subgraph flow
        Start((Claim\ncreated)) --> Pending
        Pending  -->|Service matched| Resolved
        Resolved -->|Service unmatched| Pending
    end

ServiceClaim validation happens through ValidatingWebhooks.
We'd like to remove ValidatingWebhooks because of their complexity and the impossibility of having them namespaced-scoped.
Out of scope

Validate out-of-scope fields

In Scope

Remove ServiceClaim's ValidatingWebhooks
Use CEL for field validation

Approach
To effectively remove the ValidatingWebhooks we need to implement alternative approaches for validation.
The checks we need to perform are:

Prevent mutually exclusive fields to be defined at the same time
Guarantee immutability for immutable fields
Prevent some fields to be present in the wrong context

Mutually exclusive fields
Mutually exclusive fields can be validated using kubernetes CRD Validations.
It is just needed to move them as child of a parent with MinProperties and MaxProperties set to 1.
As an example ServiceClaim's environmentTag and applicationClusterContext can not be defined at the same time.
They can be moved as child of a target property, and we can set the following constraints on target Go struct:
// +kubebuilder:validation:MaxProperties:=1
// +kubebuilder:validation:MinProperties:=1

Guarantee Immutability
Immutability is guaranteed through Common Expression Language
Wrong context
This check can be completely removed by introducing a new CRD without the prohibited fields and is planned in  #275, do not implement in this Story.
Acceptance Criteria
Development

[ ] CEL is used for ServiceClaim validation
[ ] ServiceClaim webhooks are removed
[ ] ServiceClaim CRDs are refactored wrt mutually exclusive field remediation

QE

[ ] Test cases are updated

Docs

[ ] Update ServiceClaim doc
[ ] Update architecture document with any changes while implementing

Legend

[ ] To do
[x] Done
[ ] ~Unsatisfied~

superseedes #263 and #260


Update pyaedt_cheat_sheet.tex

I have added the final version of the AEDT-API Cheat Sheet, please have a look.

What's the status here? @Revathyvenugopal162 @MaxJPRey @pvinod13

@RobPasMue As soon as @Revathyvenugopal162 suggestion's are merged, it is ready for merging in my opinion.

@pvinod13 @Revathyvenugopal162 following @MaxJPRey's comment - can we get this PR updated and merged after solving comments?

@pvinod13 We had to close on PR and opened another PR with combined AEDT and EDB API Cheatsheet? Is this the over written cheatsheet? I can see all these changes on the AEDT API there. IF both are the same, please add Maxime's suggestion to updated AEDT cheatsheet.

@pvinod13 confirming that all changes have been incorporated into the latest cheatsheet. Sorry for the confusion. Please close the PR.


Safari TP 120: logical border-radius + Edge alignment + Chrome 89

Safari
https://webkit.org/blog/11548/release-notes-for-safari-technology-preview-120/

Implemented logical border-radius (r271447)

Have not yet tested it using https://tests.caniuse.com/css-logical-props though.
Edge
Plus I've changed Edge 87+ to match Chrome 87+. I don't have Edge 87 around anymore, but Edge 88 matches Chrome 88 and since it's Chromium, it's almost certainly the same.

Chrome 89

https://www.chromestatus.com/feature/5631002091192320
https://bugs.chromium.org/p/chromium/issues/detail?id=1155270

Not sure about the failing test for margin-start, but since thats red in Firefox which is marked as fully supported as well, I've gone ahead and changed Chrome to that, for now at least.

Looks great, and thanks for the test screenshots. :)


[Feat]: Add support for running chromadb in server mode with embedchain

What changed and why?
Requested by on discord here: https://discord.com/channels/1121119078191480945/1121119078858358846/1128163917206671371

How was it tested?
Tested locally and works fine. Please find the example jupyter notebook added to the repository for reference.

@cachho also had a similar PR https://github.com/embedchain/embedchain/pull/117
This was missed somehow. Sharing here for future purposes.