Access to OData is disabled in Outlook REST API

We have created an add-in that sends requests to the Outlook REST API based on the following document.
https://docs.microsoft.com/en-us/office/dev/add-ins/outlook/use-rest-api
An error occurred when an external server sent a request using the retrieved token.
HTTP/1.1 403 Forbidden

{"error":{"code":"ErrorAccessDenied","message":"Access to OData is disabled."}}

Based on the error message, we searched and found the following information.
https://blogs.msdn.microsoft.com/wushuai/2017/04/01/how-to-fix-access-to-odata-is-disabled-when-calling-graph-api/
We checked whether EwsApplicationAccessPolicy was set or not from the following command, but it was not set for the relevant tenant.
Get-OrganizationConfig | select EwsApplicationAccessPolicy, EwsAllowList, EwsBlockList

We looked for other related documents, but could not find any.
Could you please provide us with the necessary configuration information or related documentation so that requests to the Outlook REST API are not denied with tokens obtained from the add-in?
Thanks.

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

ID: fde53b2d-39f8-5b6d-5e37-068b4d93f049
Version Independent ID: 9c7ff3ef-a188-bd28-65bb-1d620d4a8842
Content: Use the Outlook REST APIs from an Outlook add-in - Office Add-ins
Content Source: docs/outlook/use-rest-api.md
Product: outlook
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@clavx Thanks for asking about this.
@exextoc Can you take a look?
Thanks.

@clavx Do you hit this error when the add-in is making the REST request or are you using the token provided by the addin (by calling getCallbackTokenAsync with isRest true) and making a REST request through an external server using this token?

Thank you for your response.

are you using the token provided by the addin (by calling getCallbackTokenAsync with isRest true) and making a REST request through an external server using this token?

We tested only this way.
We didn't check the behavior when the add-in made a REST request.
We would like to confirm this, but the tenant experiencing the issue is a customer environment, so it is expected to take some time.

Just a follow-up here, this documentation page has some useful information that might help with configuring your customer's ApplicationAccessPolicy:
https://docs.microsoft.com/en-us/graph/auth-limit-mailbox-access


NTR - remove unnecessary deprecations

1. Why is this change necessary?
Cause this repo will be shopware 6.0 :-D
2. What does this change do, exactly?
removes unneeded deprecation and warnings/erros
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[ ] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[ ] I have read the contribution requirements and fulfil them.

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

what about changing 6.0 to 5.8 and removing them then?

not my business @mitelg :-D

ok @mitelg I changed it to 5.8 so @shyim can create the removal pr :trollface:

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-25807
Please use this issue to track the state of your pull request.

Thanks


support python 3.3+

steve should support Python 2.7 and 3.3+.

As a first step: there are a few print statements in some of the .py files. We should changes those to function calls and include
from __future__ import print_function

at the top of all .py files (which gives you early detection by raising  an error if you use a print statement instead of function in 2.7)

I've done a lot of this work before, so I know how I would go about doing it.
If you want to tackle this, then go for it. Otherwise I'm going to leave it because I think some of the other things @codersquid and I have been talking about are higher priority.

Sorry, did not want to imply you did not know how to proceed with this.
I should have just asked if it is ok for me to already insert the from __future__  import print_function.
I tend to debug (understand the code) with print statements and, after a long time still using print statements by default, I now finally naturally type print('some_variable:', some_variable) and that comes out as tuple in steve %-) every time.
The rest has lower priority from my side as well.

No worries! I'm just trying to help by letting you know what I'm thinking priorities-wise.
I definitely want to add support for Python 3.3. richard supports it already amongst other things. I'm just saying that I personally won't be working on this right now because there are other things that have more impact on @codersquid's workflow.
Want me to assign this to you?

Go ahead and assign.

I can't figure out how to assign you without dealing with github's user/group/permissions system. I'll deal with that later.

No problem. Are you ever online at #richard ? I tried to setup IRC on  irc.mozilla.org but I am not sure I am on the right channel

We hang out on IRC on Freenode in #richard. Looks like the README the wrong IRC information--I'll fix it now. Sorry about that!


Using locales disabled by recent bugfix

Since 28e505c, paper-calendar.html loads moment-import.html instead of moment-with-locales-import.html, but paper-date-picker.html doesn't.
paper-date-picker.html loads moment-with-locales-import.html before loading paper-calendar.html, which in turn loads moment-import.html. The app ends up with window.moment pointing to the moment object without locales, and the locales cannot be html-imported anymore because they have already been imported.
I think paper-date-picker.html should also import moments-import.html instead of moment-with-locales-import.html. This way, a user can decide for themselves to import the locales after importing the date picker.
EDIT: I see there already is a fix for this. +1!

I need the locale import, so I wouldn't load moments-import.html and next load moment-with-locales-import.html, because the first moments-import.html would be useless.
I prefer to load only moment-with-locales-import.html, and now I MUST to delete the row 10 in paper-calendar.html in order not to overwrite the moment instance from the "locale's one" to the "without-locale's one":
...
09: <link rel="import" href="../iron-resizable-behavior/iron-resizable-behavior.html">
10: <!--<link rel="import" href="../moment-element/moment-import.html">-->
11: <link rel="import" href="paper-date-picker-icons.html">
...

The proposed fix means that who wants the locales need to loads moment-with-locales-import.html AFTER all paper-date-picker loads. Why not to load only the "locale version"? It would be a little more heavy, but it will solve all this issues.


Add new deprecated directive

Implementation for issues #2006, #1166
Proposal https://gist.github.com/timotheeguerin/f525f392a5d39e3d3d92260167e62c3e
Add a new #deprecated directive
Syntax
Parameters:

message: valueof string: [REQUIRED] Deprecation message

#deprecate "<message">

Unify with @deprecated
Current @deprecated decorator should align to have the same behavior. And don't recommend using it.
Behavior
Reporting
A type that has been marked as deprecated will report itself as deprecated in the IDE(strikethrough Foo) and emit a warning diagnostic
A flag --ignore-deprecation will prevent those from being reported but still show the strikethrough in the IDE.
This way we can ensure deprecation are not breaking if you want it to not be and are using --warn-as-error
Carry over
A deprecation does NOT carry over to models and op using model is or op is
#deprecated "Don't use Foo"
model Foo {}

model Bar is Foo {}
             ^ warning: deprecation Don't use Foo

model Baz is Bar {}  // no issue here

However an operation included via extends will carry over the deprecation. (Same for model properties)
interface Foo {
  #deprecated "Don't use foo"
  foo(): void;
}

interface Bar extends Foo {

}

op baz is Bar.foo;
              ^ warning: deprecation Don't use foo

Deprecating service types(operation, models, etc.)
That directive should be able to work in the same way to deprecate emitted types.
Having another decorator(or something else) for that would only add confusion on when to use which.
#deprecated "Service deprecated read operation in 2022-01-01"
op read(): void;

See Azure extended deprecation for a more detailed azure deprecation experience
Emitter changes
When the new directive is added, the existing decorator and api should still work as they were. To add support for the new directive and you should be able to just use the new API.
As the @deprecated decorator will be calling to the same logic(on top of the legacy one) you should just have to worry about that and not have to keep checking both.
Note about clients:
Because the deprecated status doesn't carry over in op is if using a client that is redefining the structure of the service with many op is the emitters will have to be checking the sourceOperation as well for deprecation. Or the client operation will also need to be marked as deprecated(Probably the better idea)

est: 8


Bug: fails to deploy two manifests with the same name

What happened?
I have the following:
      ...
      ...
      - name: Deploy frontend & backend
        uses: azure/k8s-deploy@v4
        with:
          namespace: default
          manifests: |
            artifacts/frontend/deployment.yaml
            artifacts/backend/deployment.yaml
      ...
      ...

Since the two manifests have the same name (deployment.yaml) it deploys the same file twice. Probably, because all files are copied to the same /tmp folder, overwrite each other, and then deployed by their name only.
There's a simple workaround to use two separate steps for that, which I did and it works fine now, But I have suffered a lot before figuring out the issue.
The workaround:
      ...
      ...
      - name: Deploy frontend
        uses: azure/k8s-deploy@v4
        with:
          namespace: default
          manifests: |
            artifacts/frontend/deployment.yaml

      - name: Deploy backend
        uses: azure/k8s-deploy@v4
        with:
          namespace: default
          manifests: |
            artifacts/backend/deployment.yaml
      ...
      ...

Version

[X] I am using the latest version

Runner
ubuntu-latest
Relevant log output
##[debug]Evaluating condition for step: 'Deploy frontend & backend'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Deploy frontend & backend
##[debug]Loading inputs
##[debug]Evaluating: github.token
##[debug]Evaluating Index:
##[debug]..Evaluating github:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'token'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Loading env
Run azure/k8s-deploy@v[4](https://github.com/motcke/*****#step:6:4)

##[debug]Input manifest files: /tmp/deployment.yaml,/tmp/deployment.yaml
::group::Deploying manifests
Deploying manifests
  ##[debug]Kubectl run with command: /usr/bin/kubectl apply,-f,/tmp/deployment.yaml,/tmp/deployment.yaml,--namespace,default
  /usr/bin/kubectl apply -f /tmp/deployment.yaml,/tmp/deployment.yaml --namespace default
  service/*****-svc unchanged
  deployment.apps/*****-deploy configured
  horizontalpodautoscaler.autoscaling/*****-scaler unchanged
  secretproviderclass.secrets-store.csi.x-k8s.io/******-sync-env-vars configured
  service/******-svc unchanged
  deployment.apps/******-deploy configured
  horizontalpodautoscaler.autoscaling/******-scaler unchanged
  secretproviderclass.secrets-store.csi.x-k8s.io/******-sync-env-vars unchanged
  ##[debug]Deployed manifest files: /tmp/deployment.yaml,/tmp/deployment.yaml
  ::endgroup::
::group::Checking manifest stability
Checking manifest stability
...
...
...

In my case it detects multiple manifests, but duplicates first one.
Run ls -l manifests
total 8
drwxr-xr-x 2 runner docker [4]096 Jun 18 22:19 manifests-front
drwxr-xr-x 2 runner docker 4096 Jun 18 22:19 manifests-imgproxy

In both (or more) directories there are deployment.yml service.yml and ingress.yml
And then I'm applying them:
      -
        name: Deploy manifests to cluster
        uses: azure/k8s-deploy@v5
        with:
          manifests: |
            manifests
          imagepullsecrets: ghcr

But for some reason instead using all files for kubectl apply, it is duplicating paths always from first one. So also If will try to deploy manifests for 3 services (x, y, z), it will try to deploy "x" three times instead. That has to be a bug.

/usr/bin/kubectl apply -f
/tmp/Deployment_imgproxy_1718749155628,
/tmp/Ingress_imgproxy_1718749155628,
/tmp/Service_imgproxy_1718749155628,
/tmp/Deployment_imgproxy_1718749155628,  // it should be "front"
/tmp/Ingress_imgproxy_1718749155628,  // it should be "front"
/tmp/Service_imgproxy_1718749155628  // it should be "front"
--namespace default

@motcke you said that issue is maybe due to fact that all directories are merged into /tmp. It is true, but in theory it should be handled ok. In logs we can see that this action is generating unique names based on original subdirectory and timestamp, so there should be no problem with conflicts.

looking into this!


Add quick e2e tests for vSphere

Issue #, if available:
Description of changes:
This PR adds the remaining new vSphere e2e tests to the quick test suite.
Testing (if applicable):
Manually invoked tests runs
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


bug(table): mat-table filter *matNoDataRow with mat-row tag

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Hello @angular/material development team!
I really love your product and use it everyday.
But while using mat-table with mat-row, I found that *matNoDataRow with  tag(not  doesn't work well.
It only shows a blank row eventhough it has content with  in it.
I think it works with  and  tags, but while implementing matRipple for the rows, this bug was found.
Please have a look at it and let the users know.
Thanks,
Angular Fan.
Reproduction
meeting-list.html
  ...
      <mat-row *matNoDataRow>
        <mat-cell mat-cell *matCellDef>
          No data matching the filter "{{input.value}}"
        </mat-cell>
      </mat-row>
  ...

meeting-list.ts
...
  applyFilter(event: Event) {
    const filterValue = (event.target as HTMLInputElement).value;
    this.meetings.filter = filterValue.trim().toLowerCase();

    if (this.meetings.paginator) {
      this.meetings.paginator.firstPage();
    }
  }
...

Expected Behavior
The matNoDataRow should have the content with No data matching the filter "{{input.value}}".
Actual Behavior
The matNoDataRow should shows only a blank row.
Environment

Angular: 14
CDK/Material:
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu):

Missing stackblitz reproduction - feel free to reopen with a clear example we can use to diagnose the issue you are reporting


[New game]: Dot Connect Game

🎮 Game Request
Game logic and basic description : It was a two player game Red and yellow are two members and connect the dot to win the game
Point down the features
Game points
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @codewithganeshhh , You can't have another issue before completing the previous one 😀
you already have the following 1 open issues 👀 ! :
#3178

Hey @codewithganeshhh ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

Hey @codewithganeshhh !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

/assign

Hey @MrPC7 ! , This issue is already assigned to @codewithganeshhh. 💗
You can work on other issues 🚀
If there is anything wrong you can contact us on Discord🕹👀


Documentation website

Poe the poet is growing in complexity to the point where a single readme.rst isn’t the clearest form of documentation. Setting up a documentation website, probably sphinx based would be a lot better, and lay the groundwork for me useful docs.

Have you seen https://pdoc3.github.io/pdoc/? It helped me get a quick first working version, and i then iterated to sphinx a few months later once i had the docs more mature.
I can try to open a pr with pdoc if you agree

@Ambro17 thanks for the offer, that might be worth a shot. Although the front page gives the impression it's more geared towards code documentation (i.e. from docstrings, rather than usage guides), which isn't so relevant at this point.
I appreciate the point about sphinx + rst being a bit inconvenient, but I think that's what I want longer term, so I'd rather stick with rst (having dealt with it so far for the readme).
Do you think it still makes sense?

@nat-n, Would you be open to a PR to add a docs folder intended to be served via github-pages? (i.e, renders with sphinx + rst and/or markdown)?

Hi @mshafer1, thanks for the suggestion. I'd totally be open to progressing in that direction.
Sphinx with rst would be my default choice, à la ReadTheDocs. IMO rst is not much fun to work with but markdown is not expressive enough. I'm still open to other suggestions as well.
However the main obstacle is the work required to create a good document structure for the new docs website, and populate enough of it from the readme that it could functionally replace the readme as a reference, without causing confusion about how to maintain docs between the readme and the website.
So I think to realise value from this is not a trivial task, and would probably take a little bit of iteration to get right. My priority for the time I am able to dedicate to this project in the near term is to focus on fixing bugs and adding high value features. But if you're keen to contribute some effort to work on this then that's very cool.

The new documentation website is live, thanks to @usr-ein


fix nrp resources based on s360 checks

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify : Updating Network resource properties previously identified by S360

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. : April 2021
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. 05/07/2021
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Changes made based on PR https://github.com/Azure/azure-rest-api-specs/pull/12570.
These property issues were identified by S360 checks, and were fixed for 2020-07-01 and 2020-08-01, but got missed in subsequent api versions, due to network branch cut before PR merge.
so, adding these properties in 2021-02-01 and 2020-11-01 (separate PR: https://github.com/Azure/azure-rest-api-specs/pull/14217 )

The Cross Version BreakingChange is not related to this PR and it seems to be a false alarm


fix scope of Azure Load Balancer

@mikebaz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

will resubmit as corp id


Fix webpack HMR

We had HMR set up to accept to app/routes.js so all dependency paths that pass through would trigger a reload. Currently on a failed hot reload a warning lists a dep propagation through that file, so for some reason webpack thought we weren't set up to handle it. Fixed by splitting up app/routes.js into two files with their respective trees as default exports, which webpack seems to handle better.
This also uses the react-hot-loader v4 scheme, which does away with AppContainer and uses a helper in the main component's export instead. I still need to test that production builds work as expected.
r? @keybase/react-hackers

@akalin-keybase Just fixed a small typo in .babelrc. I'm going to test that the desktop prod build works as expected and then merge.


string concatenation

Describe the bug
norminette does not allow string concatenation in header files
Erroneous code
if we try to define literal consisting two string - we getting an error
#ifndef _H
# define _H

# define HELLO		"Hello, "
# define WORLD		"world!"

# define STRING1	"Hello, " "world!"
# define STRING2	HELLO "world!"
# define STRING3	"Hello, " WORLD
# define STRING4	HELLO WORLD

#endif

non of these ways are allowed
norminette return
Error: TOO_MANY_VALS        (line:   7, col:  27):	Too many values on define
Error: TOO_MANY_VALS        (line:   8, col:  23):	Too many values on define
Error: TOO_MANY_VALS        (line:   9, col:  31):	Too many values on define
Error: TOO_MANY_VALS        (line:  10, col:  27):	Too many values on define

It also means, that there is no possibility to define large literals wich are longer than 67 characters

Additional infos

OS: Linuxmint 20.2 uma
python --version: Python 3.8.10
norminette -v: norminette 3.3.40

Hello,
I can reenable basic string concat/maths in define stuff, but it's not up to me.
That's a design choice by 42network so for now i won't reenable it.
I'll ask around
Have a good day


Prefs broken after Wait Of The World update

Running ukbutt prefs in the console gives the following error:
Command 'ukbutt' failed. void GameConsole.CommandRoot.Leaf(string.System.Action)
Not sure if this just needs a rebuild to update symbols or what, haven't tried, just been getting support requests on discord.

Just checked, recompile seems to fix it.


Getting error (init() got an unexpected keyword argument 'user_agent') in devops pipeline while using below command

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az extension add
Errors:
  File "C:\hostedtoolcache\windows\Python\3.6.8\x64\lib\site-packages\azure\cli\core\_profile.py", line 939, in find_from_service_principal_id
    result = self._find_using_specific_tenant(tenant, token_entry[_ACCESS_TOKEN])
  File "C:\hostedtoolcache\windows\Python\3.6.8\x64\lib\site-packages\azure\cli\core\_profile.py", line 1033, in _find_using_specific_tenant
    client = self._arm_client_factory(token_credential)
  File "C:\hostedtoolcache\windows\Python\3.6.8\x64\lib\site-packages\azure\cli\core\_profile.py", line 881, in create_arm_client_factory
    base_url=self.cli_ctx.cloud.endpoints.resource_manager, **client_kwargs)
TypeError: __init__() got an unexpected keyword argument 'user_agent'
To open an issue, please run: 'az feedback'
##[error]Error Code: [1]
##[debug]Processed: ##vso[task.issue type=error;]Error Code: [1]
##[error]Error: Azure login failed
##[debug]Processed: ##vso[task.issue type=error;]Error: Azure login failed
##[debug]task result: Failed
##[error]Script failed with error: ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: __init__() got an unexpected keyword argument 'user_agent'
Traceback (most recent call last):
  File "C:\hostedtoolcache\windows\Python\3.6.8\x64\lib\site-packages\knack\cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "C:\hostedtoolcache\windows\Python\3.6.8\x64\lib\site-packages\azure\cli\core\commands\__init__.py", line 657, in execute
    raise ex

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az extension add -n {}

Expected Behavior
as i am running CLI command through pipeline and logged in already this error should not appear
Environment Summary
Linux-5.4.0-1051-azure-x86_64-with-debian-10.2 (Cloud Shell)
Python 3.6.10
Installer: DEB

azure-cli 2.25.0 *
azure-cli-ml 1.29.0

Extensions:
azure-cli-ml 1.29.0
ai-examples 0.2.5
ssh 0.1.5

Additional Context

@jiasli for awareness

Seems to be the same issue as #18626, related to Machine Learning pipelines.

@jiasli Thanks for your reply, issue is resolved by adding 'azure-mgmt-resource==18.0.0' in my requirements.txt.

As stated in https://github.com/Azure/azure-cli/issues/18626#issuecomment-879609185, adding azure-mgmt-resource==18.0.0 will break azureml-core which requires azure-mgmt-resource>=1.2.1,<15.0.0.


VSC never sign the merge commit even if I turned Enable Commit Signing on

VS Code Version: 1.53.2
OS Version: 19042.746

As what the title described, I have encountered several times: when I use VSC to merge 2 branches, either with conflicts or not, the commit will not be signed, which causes several troubles.
Steps to Reproduce:

Use VSC to merge 2 branches

Does this issue occur when all extensions are disabled?: Yes/No

Also facing this issue.

@martin-luo-webjet, @stacks13 sorry for not getting back to you on this.
Are you able to reproduce the same with the latest version of VS Code? Thanks!

Version: 1.63.2 (Universal)
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:37:28.172Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 20.6.0

The issue is still present. Even I have Enable Commit Signing set as true.
From the below image. Both the commit and merge are made using VSCode UI. The regular commit gets signed automatically as expected, however, the merge commit does not.

Also experiencing this... seems like something the setting Git: Always Sign Off should fix, but it does not :/

Seems for me at least the issue was with my git config... going through these steps again resolved it:
git config --global user.signingkey my_key_id
git config --global commit.gpgsign true

Not really sure why this fixed it for me as my understanding was these would need to be set for any commits to be signed, which non-merge and non-cherry-pick commits always were.

Adding some resources for signing merge commits:

https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
https://git-scm.com/docs/git-merge#Documentation/git-merge.txt--Sltkeyidgt


fix openmpi version on Hercules

Summary
Switched from used installed openmpi 4.1.6-gcc-12.2.0-spack to system installed<EMAIL_ADDRESS>This fixed problem on installing gcc environment on Hercules.
Testing
Installed spack-stack-1.8.0/gcc
Wiki page updated,
Systems affected
Hercules
Issue(s) addressed
#1278
Checklist

[x] This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
[x] These changes have been tested on the affected systems and applications.
[x] All dependency PRs/issues have been resolved and this PR can be merged.

That's fantastic! I guess it warrants re-tagging once more, but I am going to wait until we (hopefully) have a PR merged for S4, too.
Can you confirm that Orion is also good now? I see you updated the Wiki page for that system.

Can you confirm that Orion is also good now? I see you updated the Wiki page for that system.

Confirming, both Hercules and Orion have both Intel and GNU environments installed.

@climbfuji
In the meantime I tried to run ufs-weather-model on Hercules using 1.8.0 (both Intel and GNU). It did compile, but when linking, it complained that curl is having problem with openssl. I made changes in packages.yaml to use system installed curl, openssh and openssl, and model is running now.
Changes:
<     curl:
<       externals:
<       - spec<EMAIL_ADDRESS><         prefix: /usr
100,107d62
<     openssh:
<       externals:
<       - spec<EMAIL_ADDRESS><         prefix: /usr
<     openssl:
<       externals:
<       - spec<EMAIL_ADDRESS><         prefix: /usr

While typing this, I saw you committed this PR. I'll do another one. Or, maybe I can try to run ufs-weather-model other machines and collect changes (if any other that Hercules) into one PR.

hmm ok - yes please, try the other platforms if you can

@climbfuji here we stand with ufs-weather-model:

Hera, Gaea-C5, and Hercules (with curl/openssl changes) works OK.
Orion is missing zlib-ng (old issue #1055).  I'm installing zlib-ng right now, but it takes time, lots of dependencies. Hopefully this will work.
ufs-weather-model-env is missing SP library everywhere. Only Derecho is using it, so it failed. When I load manually sp lib, Derecho compiled OK.
Jet - failed in cmake, I'll take a look into this next.

Can you please check why is 1.8.0 skipping sp library for ufs-weather-model-env/1.0.0.lua? BTW, it is missing in 1.7.0 as well, 1.6.0 is OK.

Regarding sp, this is expected and the solution is to manually load it if needed. This is not an error.
See also https://github.com/JCSDA/spack-stack/issues/1330

OK, we can add it in ufs-weather-model derecho module file.

I don't understand why that is needed. All UFS platforms currently load the individual modules explicitly, including sp.
https://github.com/ufs-community/ufs-weather-model/blob/develop/modulefiles/ufs_common.lua

Not all, Derecho is (for reason unknown to me) using:
setenv("CMAKE_Platform", "derecho.intel")
load("ufs-weather-model-env")

in ufs_derecho.intel.lua

Not all, Derecho is (for reason unknown to me) using:
setenv("CMAKE_Platform", "derecho.intel")
load("ufs-weather-model-env")

in ufs_derecho.intel.lua

Now I remember ... but I don't remember why we had to do this. Ok, makes sense then.


helm_release and kubernetes_secret_v1 always update in-place

Hey all,
First, thank you for the work on this module, it's been really helpful and the examples are very useful too.
I wanted to ask for some help on an issue that i'm running into.  I'm currently following the AWS example, which leverages gitops-bridge to provide the metadata between TF and argo.  What i'm noticing is that no matter what I do, the helm_release for argo and the kubernetes secret consistently want to update every single time I run TF apply.  Here's the exact message:
  # module.eks_cluster.module.gitops_bridge_bootstrap.helm_release.argocd[0] will be updated in-place
  ~ resource "helm_release" "argocd" {
        id                         = "argo-cd"
      ~ metadata                   = [
          - {
              - app_version = "v2.8.2"
              - chart       = "argo-cd"
              - name        = "argo-cd"
              - namespace   = "argocd"
              - revision    = 6
              - values      = jsonencode(
                    {
                      - configs = {
                          - secret = {
                              - argocdServerAdminPassword = "(sensitive value)"
                            }
                        }
                      - server  = {
                          - service = {
                              - type = "LoadBalancer"
                            }
                        }
                    }
                )
              - version     = "5.45.0"
            },
        ] -> (known after apply)
        name                       = "argo-cd"
        # (28 unchanged attributes hidden)

      - set_sensitive {
          # At least one attribute in this block is (or was) sensitive,
          # so its contents will not be displayed.
        }

        # (1 unchanged block hidden)
    }

  # module.eks_cluster.module.gitops_bridge_bootstrap.kubernetes_secret_v1.cluster[0] will be updated in-place
  ~ resource "kubernetes_secret_v1" "cluster" {
        id                             = "argocd/eks-blueprints-green"
        # (4 unchanged attributes hidden)

      ~ metadata {
          ~ annotations      = {
              - "addons_repo_basepath"                         = "argocd/"
              - "addons_repo_path"                             = "argocd/bootstrap/control-plane/addons"
              - "addons_repo_revision"                         = "HEAD"
              - "addons_repo_url"                              = "git@github.com:aws-samples/eks-blueprints-add-ons"
              - "argocd_password"                              = (sensitive value)
              - "argocd_route53_weight"                        = "0"
              - "aws_account_id"                               = "xxxxx"
              - "aws_cloudwatch_metrics_iam_role_arn"          = "arn:aws:iam::xxxxx:role/aws-cloudwatch-metrics-20231107191852092600000027"
              - "aws_cloudwatch_metrics_namespace"             = "amazon-cloudwatch"
              - "aws_cloudwatch_metrics_service_account"       = "aws-cloudwatch-metrics"
              - "aws_cluster_name"                             = "eks-blueprints-green"
              - "aws_for_fluentbit_iam_role_arn"               = "arn:aws:iam::xxxxxxx:role/aws-for-fluent-bit-20231107191852093100000029"
              - "aws_for_fluentbit_log_group_name"             = "/aws/eks/eks-blueprints-green/aws-fluentbit-logs-20231107191821378800000019"
              - "aws_for_fluentbit_namespace"                  = "kube-system"
              - "aws_for_fluentbit_service_account"            = "aws-for-fluent-bit-sa"
              - "aws_load_balancer_controller_iam_role_arn"    = "arn:aws:iam::xxxxxxxx:role/alb-controller-20231107191852090300000024"
              - "aws_load_balancer_controller_namespace"       = "kube-system"
              - "aws_load_balancer_controller_service_account" = "aws-lb-sa"
              - "aws_region"                                   = "us-east-1"
              - "aws_secret_manager_git_private_ssh_key_name"  = "github-blueprint-ssh-key"
              - "aws_vpc_id"                                   = "vpc-0c98bdd52eb907def"
              - "cert_manager_iam_role_arn"                    = "arn:aws:iam::xxxxxxx:role/cert-manager-20231107191852092600000026"
              - "cert_manager_namespace"                       = "cert-manager"
              - "cert_manager_service_account"                 = "cert-manager"
              - "cluster_autoscaler_iam_role_arn"              = "arn:aws:iam::xxxxxxx:role/cluster-autoscaler-20231107204205450400000001"
              - "cluster_autoscaler_namespace"                 = "kube-system"
              - "cluster_autoscaler_service_account"           = "cluster-autoscaler-sa"
              - "cluster_endpoint"                             = "https://xxxxxxxxx.gr7.us-east-1.eks.amazonaws.com"
              - "cluster_name"                                 = "eks-blueprints-green"
              - "ecsfrontend_route53_weight"                   = "0"
              - "eks_cluster_domain"                           = "eks-blueprints.xxxxxxxxx"
              - "env"                                          = "green"
              - "environment"                                  = "eks-blueprints"
              - "external_dns_iam_role_arn"                    = "arn:aws:iam::XXXXX:role/external-dns-20231107191852090600000025"
              - "external_dns_namespace"                       = "external-dns"
              - "external_dns_policy"                          = "sync"
              - "external_dns_service_account"                 = "external-dns-sa"
              - "external_secrets_iam_role_arn"                = "arn:aws:iam::XXXXXX:role/external-secrets-20231107191852089100000023"
              - "external_secrets_namespace"                   = "external-secrets"
              - "external_secrets_service_account"             = "external-secrets-sa"
              - "gitops_workloads_path"                        = "envs/dev"
              - "gitops_workloads_revision"                    = "main"
              - "gitops_workloads_url"                         = "git@github.com:aws-samples/eks-blueprints-workloads"
              - "ingress_type"                                 = "alb"
              - "route53_weight"                               = "0"
            } -> (known after apply)
            name             = "eks-blueprints-green"
            # (5 unchanged attributes hidden)
        }
    }

Plan: 0 to add, 2 to change, 0 to destroy.

Changes to Outputs:
  ~ gitops_metadata   = (sensitive value)

Is there a way to avoid this consistently changing?

Do you know which 2 changes is referring to?
Which example your using? this would help us reproduce it. Perharps the blue-green pattern here? for @allamand to take a look


Feature Request

I use dreamweaver for coding i also like VSCode but what makes me to stick to dreamweaver is its color picker/pallet(While Coding CSS) so i request VSCode dev to create the dreamweaver like color picker/pallet for VSCode

duplicate of #625

@aeschli i think dreamweaver colorpicker is more User friendly


use thiserror instead of derive_more for error handling

Signed-off-by: koushiro<EMAIL_ADDRESS>

Can you briefly explain why? I'm not following the comparison between thiserror and derive_more, and this PR doesn't look like it saved much LOC either.

derive_more is a good toolkit that provides derive macros of many standard library traits, but thiserror is more focused on error handling (although the usage here is not much different), and as far as I know, thiserror is the most commonly used error handling library in the current Rust community.

@sorpaas  what do you think?

Since paritytech/substrate#10696 has been merged, I think this PR should be fine, what do you think? @sorpaas


Use stable cluster name in subtest

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[x] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[ ] Does not have any changes that may affect Istio users.

In response to a cherrypick label: new pull request created: #32343


Creating a new Gradient2D resource shows up as pink

Tested versions
4.3 beta1
System information
Godot v4.3.beta2 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; <IP_ADDRESS>42) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)
Issue description
Creating a new GradientTexture2D creates a solid pink texture despite the gradient being the default black-white. Making any changes to the gradient fixes it.

Steps to reproduce
New project > Add Sprite2D > Add new GradientTexture2D as the texture
Minimal reproduction project (MRP)
N/A

Can't reproduce in beta2. Please provide full system information, you can copy them from Help -> Copy System Information. Also, what renderer are you using in your project?

Sure thing. This happened just recently and I can say my computer is rather old at this point. I wouldn't be surprised if it's a hardware issue or something.
Godot v4.3.beta2 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 (NVIDIA; <IP_ADDRESS>42) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

It's not a hardware issue (you have better specs than mine 🙃). Maybe driver bug or something.

I tried to update my drivers and rebooted and I still get the solid pink gradient.

I didn't mean that my specs were bad 😅 They're almost 9 years old now so I wouldn't be surprised if something's starting to fail at this point. If all signs points toward an issue with my machine. There's not much to do. Want me to close this?

I think it can be open for now, in case someone has the same issue.
Though you could check if you see this bug in older versions.

Alright. I tried it on 3.5.2, 4.0.2, 4.1 and 4.2. Only occured on 4.3beta1 👍

I did some test and i can reproduce this issue, looks like a regression between v4.2.dev3.official [013e8e3af] and v4.2.dev4.official [549fcce5f]. This bug seems a little tricky because sometimes not happen, but i was able to reliable trigger setting the texture to GradientTexture1D first and after setting to GradienTexturet2D, doing that 1~3 times is enough to trigger the bug.
https://github.com/godotengine/godot/assets/44306054/1523f8f4-308e-4589-9805-69b60a38f3ee

The v4.3.beta2.official [b75f0485b] can reproduce this bug too:

Also when i close godot after reproduce the bug the console prints an error and a warning (the amount of RID's vary accordingly the amount of times i reproduce the bug):
ERROR: 7 RID allocations of type 'N10RendererRD14TextureStorage7TextureE' were leaked at exit.
WARNING: 14 RIDs of type "Texture" were leaked.
     at: finalize (drivers/vulkan/rendering_device_vulkan.cpp:9655)

I tried to bisect but i can't reproduce this issue on my self compiled versions using MSVC or MinGw as compiler with dev_build=yes. @KoBeWi you know what compiler and what args are used to compile official releases?

AFAIK official builds use production=yes.

AFAIK official builds use production=yes.

Thanks, using that i was able to reproduce the bug in my compiled versions

Bisecting points to #81137 as the culprit:

I can't reproduce it no matter how many times I try:
https://github.com/godotengine/godot/assets/2223172/9985ad63-1b0e-485b-8cd4-53a2f7ca6b0d

i wondering if it maybe has something to do with how emit_changed() is no longer being called after _update finishes
https://github.com/godotengine/godot/pull/81137/files#diff-07c3cddd56772030a7fc531ae661b56edebe1c566c741b0921ef49b4671c88cdL143-L144
https://github.com/godotengine/godot/pull/81137/files#diff-07c3cddd56772030a7fc531ae661b56edebe1c566c741b0921ef49b4671c88cdL268
but these const_casts (grrrr) are wayy more sus bc of how the bug only happens on an optimized build
https://github.com/godotengine/godot/pull/81137/files#diff-07c3cddd56772030a7fc531ae661b56edebe1c566c741b0921ef49b4671c88cdR400
https://github.com/godotengine/godot/pull/81137/files#diff-07c3cddd56772030a7fc531ae661b56edebe1c566c741b0921ef49b4671c88cdR168
if thats the problem, then it could be solved by making update_pending mutable (texture is already mutable)
then making update_now and _update const
then removing the const_cast (grr)

but these const_casts (grrrr) are wayy more sus bc of how the bug only happens on an optimized build

I tested yesterday and i can confirm commenting this line stops the bug

@matheusmdx Since you can confirm the issue and the fix, do you mind making a PR with the fix?
If you confirm that it works and make a PR, then @Kobewi can review the code and ensure it doesn't break anything


talk/groups: expanded images in chat sometimes don't embiggen

Describe the bug, optionally with screenshots
sometimes when I click on an image in chat it's still the same tiny size when expanded. If I open source it's much much bigger so it's not actually that small:

this seems to be consistent with the particular images that don't embiggen, but other images embiggen correctly. Maybe the type of image?
To Reproduce
Steps to reproduce the behavior:

click to expand image
sometimes not any bigger

Expected behavior
should be enbiggened
Additional context:

Ship type: planet
Instance type self-hostedch
OS/browser qutebrowser / chromium

> +vat %groups
%groups
  /sys/kelvin:      [%zuse 417] [%zuse 416] [%zuse 415] [%zuse 414]
  base hash:        0v4.nsfam.srqbc.p002p.q0ham.f0fqd.gg4gi.bqtu9.p6245.b49ch.hk0d2
  %cz hash:         0v4.nsfam.srqbc.p002p.q0ham.f0fqd.gg4gi.bqtu9.p6245.b49ch.hk0d2
  app status:       running
  force on:         ~
  force off:        ~
  publishing ship:  [~ ~sogryp-dister-dozzod-dozzod]
  updates:          remote
  source ship:      ~binnec-dozzod-marzod
  source desk:      %groups
  source aeon:      114
  kids desk:        ~
  pending updates:  ~[[%zuse 414]]
::
> +vat %talk
%talk
  /sys/kelvin:      [%zuse 417] [%zuse 416] [%zuse 415] [%zuse 414]
  base hash:        0ve.3r4jj.n5ish.n63h8.1qu3o.vkodt.dvhm9.4aisd.opm40.pub9c.5a1p3
  %cz hash:         0ve.3r4jj.n5ish.n63h8.1qu3o.vkodt.dvhm9.4aisd.opm40.pub9c.5a1p3
  app status:       running
  force on:         ~
  force off:        ~
  publishing ship:  [~ ~sogryp-dister-dozzod-dozzod]
  updates:          remote
  source ship:      ~binnec-dozzod-marzod
  source desk:      %talk
  source aeon:      107
  kids desk:        ~
  pending updates:  ~[[%zuse 414]]
::

Images posted from Escape are having their dimensions set incorrectly so they show up small everywhere. This was fixed in Groups/Talk, but won't go away until people posting switch from Escape.


[FEATURE] Exists function in DeltaTableStep should not log error

Is your feature request related to a problem? Please describe.

https://github.com/Nike-Inc/koheesio/blob/90e48fc0729973e22d459c4a575d4f649ae7ccd4/src/koheesio/spark/delta.py#L307
Exist function should not be biased when it comes to evaluating whether it is good or bad for a table to exist.
Describe the solution you'd like
Few possible suggestions:

change to warning or info
keep error, but check that if self.create_if_not_exists is false, then do log as an error.

Describe alternatives you've considered
N/A
Additional context
N/A

Assign it to Federica

Fixed with #70


export 08/11

Codecov Report
Base: 57.54% // Head: 57.54% // No change to project coverage :thumbsup:

Coverage data is based on head (e15605d) compared to base (a30ae1a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #179   +/-   ##
=======================================
  Coverage   57.54%   57.54%
=======================================
  Files           7        7
  Lines         855      855
=======================================
  Hits          492      492
  Misses        325      325
  Partials       38       38

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Update New-CsTeamsUnassignedNumberTreatment.md

Adding comment on assigned numbers in unassigned number range

Docs Build status updates of commit 743f339:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e703d1f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsTeamsUnassignedNumberTreatment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

Docs Build status updates of commit a20e539:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

teams/teams-ps/teams/Get-CsTeamsUnassignedNumberTreatment.md
:white_check_mark:Succeeded
View (teams-ps)

teams/teams-ps/teams/New-CsTeamsUnassignedNumberTreatment.md
:white_check_mark:Succeeded
View (teams-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@tiburd Please merge this PR. Thanks


prefix crash

if i try to put a folder with spaces in its name (like home/user/prefixes/Windows Game), faugus launcher crashes. this doesn't happen if i use a folder with no spaces or if i put a quotation mark (like "home/user/prefixes/Windows Game")

Thanks for reporting.
It should be fixed now.
Please update Faugus Launcher.

Thanks for fixing


Show containers health on check-service

Actually, the command only shows if the service is not health, the objective of this issue is show in message, how many and which containers are unhealthy/degraded

fixed on this commit


Add a writeback cache

This adds an optional writeback cache similar to the one that is in the standard library's shelve module. The writeback cache allows for mutable items to behave as expected at the cost of having to write all items to disk upon close() or sync()

Additional Comments:

Before, the "dictionary" was bounded by disk space, i.e: adding new items just uses disk space, now they would also consume memory through the internal writeback dictionary. I admit I have never used this in scenarios where this would matter, but I still think it's something to consider.

Yes, this is true and there are many other downsides. It is imperfect but the ideas was to be based on (both in concept and in implementation) to how shelve does it. Maybe we should add more comments in the README about it but it is pretty clear in the shelve documentation

Before, this could be used as an OS-wide dictionary.
...

We can document this if you think it's needed. Personally, if you want to document this, I think it would be good to, in general, emphasize that this tool is designed with that use case (and then writeback also fails). I know that is a major benefit  of course but it's not as clear

General Reply
Thanks for the comments and suggestions. I had enough time right now to respond but I won't get to add these comments until later today and/or week. (just FYI)


fixed broken link

Docs Build status updates of commit bf0617e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/direct-manipulation.md
:white_check_mark:Succeeded
View

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.


(INF): change Language to object instead of a class

This removes classes RustLanguage and TomlLanguage and uses objects instead.
See https://github.com/alexeykudinkin/intellij-rust/issues/144 and https://github.com/alexeykudinkin/intellij-rust/commit/c35874d618d732d39de5558b6842330e65d1f7c3 for motivation.
@alexeykudinkin @atsky if it is OK, I would like to refactor FileTypes in a similar manner.

:+1:

removed all INSTANCEs

:+1:


vessel art make:something always hangs for a while before returning

Description
Running the latest vessel, composer required today. Whenever I run vessel art make:model Something -mf the command pretty much instantly outputs that model was created, but then kind of spins/hangs for up to one minute before the command line is usable again for new input.
Unsure what I can do to fix this, or if that is even Vessel/Docker or my machine (Macbook Pro 15" late 2019)
OS
My OS is:

[*] MacOS [Catalina]
[ ] Linux
[ ] Windows

Docker
The output of docker version:
➜ docker version
Client: Docker Engine - Community
 Version:           19.03.8
 API version:       1.40
 Go version:        go1.12.17
 Git commit:        afacb8b
 Built:             Wed Mar 11 01:21:11 2020
 OS/Arch:           darwin/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.8
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.17
  Git commit:       afacb8b
  Built:            Wed Mar 11 01:29:16 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          v1.2.13
  GitCommit:        7ad184331fa3e55e52b890ea95e65ba581ae3429
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

The output of docker-compose version:
➜ docker-compose version
docker-compose version 1.25.5, build 8a1c60f6
docker-py version: 4.1.0
CPython version: 3.7.5
OpenSSL version: OpenSSL 1.1.1f  31 Mar 2020

I can't really reproduce this one. Any idea if a good old fashioned restart would resolve this?


build: do not build unnecessary build targets in bazel test jobs

Currently in Bazel test jobs we simply use //src/.... This results
in non-test targets which are simply unnecessary (e.g. npm_packages),
being built. Instead, we can specify --build_tests_only to instruct
bazel to only build targets needed for testing.
We verify our build in a separate bazel_build job, so building
unrelated things in every test job is superfluos.

Note: I think it's okay to repeat this flag where needed. We don't want to add this as the default, as using this flag only makes sense in certain contexts (or in this case: CI jobs)


How access HLS streaming source?

I am using server running on port 80, but if i try to access to: http://localhost/live/STREAM_NAME/index.m3u8 also from browser it return to me 404 not found.
What is the problem?

You can play HLS stream using hls.js on any non safari browser.

https://github.com/video-dev/hls.js

There is video.js too to play HLS:

https://github.com/videojs/video.js
You should be able to download the HLS from the server just by inserting the URL inside your browser (basically as  @outdatedpizzatech said).
If you want to see the video in your localhost env, you can use VLC-> Open Network Stream (here you need to insert the link to the master playlist).


Serve REX-Ray API (for CLI) over unix domain socket

TODO:

[ ] Manually test REX-Ray CLI

REX-Ray doesn't support unix domain sockets for this option 😢 I'll just pick a port for it.

There is a block over 65k that is outside of those we give to mesos and outside of the Linux ephemeral port range. If you look at the or to change agent port checking, should be able to pick it out


Any ideas why the authentication is failing?

I'm trying to send messages and receive messages from twitch chat for a custom overlay which I plan to do a lot more with later but for now this will do. I've done everything in the chat example scene. My token is up to date:
Here's what the log looks like:
[TwitchService] Setup
[TwitchAuthorization] Connecting to https://id.twitch.tv
[TwitchAuthorization] Start Request(0) /oauth2/.well-known/openid-configuration
[TwitchHttpClient-1-https://api.twitch.tv] connecting to https://api.twitch.tv
[TwitchService] Start
[TwitchHttpClient-1-https://api.twitch.tv] Connection state changed: true
[TwitchAuthorization] Start request processing [0] /oauth2/.well-known/openid-configuration
[TwitchAuthorization] Connecting to https://id.twitch.tv
true
[TwitchWebsocket] Set connection to wss://irc-ws.chat.twitch.tv:443
[TwitchHttpClient-1-https://api.twitch.tv] Start Request(0) /helix/chat/emotes/global?
[TwitchHttpClient-1-https://api.twitch.tv] Start request processing [0] /helix/chat/emotes/global?
[TwitchHttpClient-1-https://api.twitch.tv] Start Request(0) /helix/chat/emotes?broadcaster_id=1054205040&
[TwitchHttpClient-1-https://api.twitch.tv] Start request processing [0] /helix/chat/emotes?broadcaster_id=1054205040&
[TwitchHttpClient-1-https://api.twitch.tv] Start Request(0) /helix/chat/badges/global?
[TwitchHttpClient-1-https://api.twitch.tv] Start request processing [0] /helix/chat/badges/global?
[TwitchHttpClient-1-https://api.twitch.tv] Start Request(0) /helix/chat/badges?broadcaster_id=1054205040&
[TwitchHttpClient-1-https://api.twitch.tv] Start request processing [0] /helix/chat/badges?broadcaster_id=1054205040&
[TwitchWebsocket] Set connection to wss://eventsub.wss.twitch.tv/ws
[TwitchWebsocket] Set connection to ws://<IP_ADDRESS>:8081/ws
[TwitchHttpClient-1-https://api.twitch.tv] Start Request(0) /helix/bits/cheermotes?broadcaster_id=1054205040&
[TwitchService] Initialized and ready
[TwitchHttpClient-1-https://api.twitch.tv] Start request processing [0] /helix/bits/cheermotes?broadcaster_id=1054205040&
[TwitchWebsocket] Connecting to wss://irc-ws.chat.twitch.tv:443
[TwitchWebsocket] connected to wss://irc-ws.chat.twitch.tv:443
[TwitchIRC] < NICK QueueStudioQuinn
[TwitchIRC] < CAP REQ :twitch.tv/commands
[TwitchIRC] < JOIN #queuestudioquinn
[TwitchIRC] > [         NOTICE] tmi.twitch.tv: Login unsuccessful
[TwitchIRC] Authentication failed.
[TwitchIRC] Can't connect
[TwitchIRC] > [            CAP] tmi.twitch.tv: twitch.tv/commands
[TwitchIRC] < JOIN #queuestudioquinn
Here's what my general project settings look like:

Here's my twitcher project settings look like:

Here's what I've already tried:

I tried messing with my firewall
All of the different authorization settings in general
Messing with my IRC name and channel name in the settings

Here's what I haven't tried:

Turning shields down on the brave browser
Trying other browsers

Hi that seems to be a hard problem.
I would exclude network based issues cause you got a connection to IRC.
Browser shouldn't be a problem either, you got redirected to the login page / authorization of the scopes?
Looks similar to that:

second thing that could be a problem. Under wich account did you created the application? Do you have an explicit bot account? Cause twitch doesn't allow Bot accounts without mod permissions to read chat of other persons anymore.
Another option you could look into Twitch has a new eventsub that also receives chat messsages.
https://dev.twitch.tv/docs/eventsub/eventsub-subscription-types/#channelchatmessage
In my opinion even the better solution cause it does alot of parsing for you. When I wrote the lib it wasn't there, so the example still uses the IRC one.

Nope! Never seen a page like this before. Here's the page it directs me to before it breaks.

then i get a problem loading page error.

FIXED!
I used http intsead of https


Key Vault: renamign Certificates AdministratorDetails -> AdministratorContact

closes #8369

Can one of the admins verify this patch?


binary autoselect like bwa-mem2?

Is it possible to build all chipset binaries and have the tool auto-select the correct one for the system it is running on in the same way as the original bwa-mem2 works?
https://github.com/bwa-mem2/bwa-mem2#installation
Without this I'm not convinced a bioconda version will be as useful.

Thank you for your interest!
We are going to add "-mode" option in BWA-MEME executable.
Then, users may be able to choose the mode of BWA-MEME according to their RAM size.
(I assume you meant the mode should be supported with a single binary executable, current BWA-MEME in Bioconda supports various chipsets but with a mode that requires 118GB RAM size)

we will add bioconda installation is available once we add the mode option

I was meaning the avx512, avx2, SSE4.2 binary selection, I was thrown off by the requirement to build each individually rather than a make multi directive, but it appears you have this covered.


Update repositories.toml

Add my project to this repo list. thank you.

Hey there -- thank you for the contribution. Please verify if the repository meets the criteria to list a new project in Good First Issue.


llmq: Store encrypted DKG contributitons

This is like #3937 (where this one is based on) also a preparation for the next coming PR which will use this encrypted contributions after DKG to share them with other members.

Needs rebase (probably)

Needs rebase (probably)


IndentationCharacterCheck: multiline strings should be ignored

	public static inline var TEST1:String = "
	class Test {
		 var _a:Int;
		public function new() {}
	}";

test/checks/whitespace/IndentationCharacterCheckTest.hx:34: character 0 : Info: Wrong indentation character (should be tab)

#191


[DON'T MERGE] - Feature/lending sdk merge

Integrated create market logic - hard coded based on cofre for testing purposes. Set up a dummy create market page.

After finishing up the loan part on Solana requesting merge into development. Only issue should be a package.json / yarn.lock


Comments don't take effect?

Describe the bug
Excuse me if this has been implemented elsewhere. It looks like the commit at https://github.com/adieyal/sd-dynamic-prompts/commit/efe24266bbeed94d19d9441fac2d13995d302049 removed the strip_comments function entirely. I can see the commented portions of my prompt in the txt2img output when an image is generated, is this intentional?
Expected behaviour
I expected the previous behavior, where the commented parts were removed from the prompt entirely before they were passed to txt2img

could you share your promt?

Sure thing,
a cat

a cat
a beach

a cat
// a beach

a cat
/* a beach */

Due to a recent update, c-style comments are not supported right now. You can use python comments, i.e. anything following a # is ignored. I may re-implement // and /* ... */ in future, but fore now, python comments should be almost as good.

Thanks, why is that specifically? Was it because the implementation was buggy? I ask because I find inline comments way too useful to give up

I'm using pyparsing to tokenize the prompt template. It gives you // and
/*... */ for free. It also ignores whitespace which is great. I then
received a request to maintain the formatting, especially newlines. To
achieve this, pyparsing must consider whitespace as significant. For
reasons that I haven't investigated, comments are no longer free. The
quickest way to bring back comments was to ignore a # character and
everything else up until the newline.
I would like to bring them back, but I haven't had the time to work on it.
On Wed, 11 Jan 2023, 06:04 space-nuko, @.***> wrote:

Thanks, why is that specifically? Was it because the implementation was
buggy? I ask because I find inline comments way too useful to give up
—
Reply to this email directly, view it on GitHub
https://github.com/adieyal/sd-dynamic-prompts/issues/172#issuecomment-1378213464,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADGXMVYVVHGL25D7SPX55TWRYWLLANCNFSM6AAAAAATUZHZ6E
.
You are receiving this because you commented.Message ID:
@.***>


Custom theme in Style Settings has unusable transparency

If in Style Settings I choose Custom theme (either dark or light setting), the result has such transparency from the overlays that it becomes unusable.
In the screenshot this is the view while the Style Settings menu is open and I've just switched to Custom, can see the page open just behind, an can interact with the style settings in front.,

Using Origami <IP_ADDRESS>

Thanks for bringing this to my attention. The color theme works if you select colors below, but i am having some trouble getting a default to stick so you don't get that awful transparency. just wanted to give an update; still working on it but its going to take some more tinkering! if you want to make a custom theme, i can explain how (i tried to keep it pretty simple & similar to making a vanilla theme :))


Proposal: Error propagation not issued for function parameters if not used within function body.

In above mentioned snippet i.e https://go.dev/play/p/a4Xm3Eidkd0 , demoStr is declared as parameter to function but never used within function.
What did you expect to see?
In above mentioned snippet i.e. https://go.dev/play/p/a4Xm3Eidkd0 , This should raise error for demoStr as its not being used within function, agnostic of caller is passing or not. If its defined as parameter it should be consumed.

NeedsFix

@gopherbot, please add labels NeedsFix

@gopherbot, please add labels compiler/runtime

A function may not use one of its parameters in the following cases:

The function implements a method of an interface and does not need to use the parameter. In some cases, it may still be preferable to keep the parameter name instead of replacing it with the blank identifier.

A refactor has been done on an exported function, and the parameter is no longer used. For compatibility reasons, the parameter must be retained. From my perspective, it is better to keep the parameter name and document that it is no longer used, rather than replacing it with a blank identifier without any explanation in the documentation.

That said, the proposed change is not backward-compatible and would require modifying existing code.

Related Issues

gopls isn't emitting warnings #30932 (closed)
x/tools/gopls: unusedparams analysis does not check exported functions #65401 (closed)
proposal: cmd/compile: provide 'evaluated but not used' error when function returned from another function is not used (called or assigned) #29428 (closed)
compiler: dead code and labels cause compilation failure #66803 (closed)
x/tools/gopls: Warn UnusedVar for unused assign #56598 (closed)

Related Discussions

error question

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


Trouble with thumbnail URL and URL linking

The webhook generally works and editing the title does too. However:

"Thumbnail url" sometimes works (I think I manged to have a thumbnail once out of 10 tries) but most of the time the field just resets to being empty on the next build.
"URL linking" either doesn't work (i.e. stays checked butt no linking happens) or resets to unchecked on the next build.

The "Jenkins Location - Jenkins URL" is configured correctly. I don't see anything related in the system logs.
Using Jenkins 2.141 and jenkins-discord v1.3.0.
Running out of ideas for what to try. Any help would be much appreciated.

URL  linking turns itself off automatically if it doesn't detect Jenkins URL.
When it happens you should see this inside your job Console output:
Your Jenkins URL is not set (or is set to localhost)! Disabling linking.
Was the Jenkins URL set automatically? If yes please update it in some way (eg. change it to something else and back).
As for the thumbnail issue I'm still looking into it, but can't reproduce it yet.

I do see that output. I just tried setting the url to google.com, reenabling the setting and running the job, followed by setting it back to the previous url and doing the same. Got the same Your Jenkins URL is not set (or is set to localhost)! Disabling linking. both times.
Jenkins is configured to require login without any access for anonymous users, could that be an issue?

Ok, another idea.
Can you please install this version of the plugin, run the job and find in the Console output something like this:
global config1: null: false, urlNull: false
global config: null: false, urlNull: false

Then post it here.
And configuration requiring login shouldn't be an issue.

Sorry for the delay, here's the output:
global config1: null: false, urlNull: true
global config: null: false, urlNull: false


Add string arrays

blah blah blah

@samos123 that test is now passing and the strings are getting written to weaviate because of the changes I made to the marshalling logic


Are multi-step predictions possible?

Hey,
thanks for providing this nice library! :)
Running your example I was wondering if it is possible to change the length of the predictions. As far as I have seen, only a prediction of length 1 is produced. But for my thesis I would like to forecast up to 96 time-steps into the future...
Would that be possible and if yes could you provide an example?
Thanks in advance and have a great day!

Generally, there are two kinds of multi-step predictions:

single-shot model: it is controlled by y_dim. For example, if you want to do 2-step predictions, you are required to preprocess training data
autoregressive model: it is not mentioned in the paper, and da_rnn does not support regression and it only could predict y_T_hat, see here.

Besides, IMO, time-series prediction is a very bad way to do quant trading and multi-step predictions will brings even worse results.
I think a 96 time-step prediction will be worse than doing nothing.


Read a graphql type schema

We need to add testing. Probably best implemented by writing a printer, and seeing if the printed output is the same as the input.


Hope to support "Max Conntions Per Host”.

Hop to support the max_connections_per_host in the config of pool.
The following is the implementation of golang
https://github.com/golang/go/blob/go1.23.2/src/net/http/transport.go#L218

maybe this solution will solve your problem click


fix: do not backdoor more than once

Closes #256

While realistic in a real world scenario, I don't see the pre-check as necessary in the case of this game because it already prevents the same script being run on the same server with the same arguments. Did something change to now allow that?

I don't know, but I've seen the scripts running several times (up to 5x). Maybe that's a change/regression in 2.2


Error When Customizing providers Section in hovercraft.nvim Configuration

Issue Description:
When using the default configuration for the hovercraft.nvim plugin, everything works as expected. However, customizing the providers section in the configuration leads to an error upon restarting Neovim.
Configuration Causing the Issue:
{
    'patrickpichler/hovercraft.nvim',
    dependencies = { { 'nvim-lua/plenary.nvim' } },
    opts = {
        providers = {
            providers = {
                { 'LSP', require('hovercraft.provider.lsp').new() },
                { 'Man', require('hovercraft.provider.man').new() },
                { 'Dictionary', require('hovercraft.provider.dictionary').new() },
            }
        },
    },
}

Error Message:
Error detected while processing /Users/andreaventi/.config/nvim/init.lua:
Failed to load `user.plugins.user`

~/.config/nvim/lua/user/plugins/user.lua:332: module 'hovercraft.provider.lsp' not found:
^Ino field package.preload['hovercraft.provider.lsp']
cache_loader: module hovercraft.provider.lsp not found
cache_loader_lib: module hovercraft.provider.lsp not found
^Ino file './hovercraft/provider/lsp.lua'
^Ino file '/opt/homebrew/share/luajit-2.1/hovercraft/provider/lsp.lua'
^Ino file '/usr/local/share/lua/5.1/hovercraft/provider/lsp.lua'
^Ino file '/usr/local/share/lua/5.1/hovercraft/provider/lsp/init.lua'
^Ino file '/opt/homebrew/share/lua/5.1/hovercraft/provider/lsp.lua'
^Ino file '/opt/homebrew/share/lua/5.1/hovercraft/provider/lsp/init.lua'
^Ino file './hovercraft/provider/lsp.so'
^Ino file '/usr/local/lib/lua/5.1/hovercraft/provider/lsp.so'
^Ino file '/opt/homebrew/lib/lua/5.1/hovercraft/provider/lsp.so'
^Ino file '/usr/local/lib/lua/5.1/loadall.so'
^Ino file './hovercraft.so'
^Ino file '/usr/local/lib/lua/5.1/hovercraft.so'
^Ino file '/opt/homebrew/lib/lua/5.1/hovercraft.so'
^Ino file '/usr/local/lib/lua/5.1/loadall.so'

# stacktrace:
  - plugins/user.lua:332
  - ~/.config/nvim/lua/astronvim/lazy.lua:43
  - ~/.config/nvim/init.lua:10
Press ENTER or type command to continue

Additional Observations:

The plugin does not break when configuring keys = {} and window = {} configurations within opts.
Setting opts = { providers = { providers = {} }, }, does not break the plugin, but triggers an error No active providers for line! when using the keymap for hovercraft.
The goal is to add more providers as mentioned in the README, but this leads to the stated issue.

Request for Help:
I'm unsure why configuring opts = { providers = { providers = {} }, }, with additional providers causes these errors. Any guidance or suggestions to resolve this would be greatly appreciated.
NOTE: I am using AstroNvim Neovim distribution. I also tried different ways to configure the plugin, one under it's own .lua file and another under user.lua.
Current Working Configuration:
    {
        "patrickpichler/hovercraft.nvim",
        dependencies = {
            { "nvim-lua/plenary.nvim" },
        },
        event = "User AstroFile",
        opts = {
            keys = {
                { "<C-u>", function() require("hovercraft").scroll { delta = -4 } end },
                { "<C-d>", function() require("hovercraft").scroll { delta = 4 } end },
                { "<TAB>", function() require("hovercraft").hover_next() end },
                { "<S-TAB>", function() require("hovercraft").hover_next { step = -1 } end },
            },
        },
    },

Hey :)
Thanks for giving hovercraft.nvim a shot and rising the issue! The problem is in the documentation 🤦  Of course the sample doesn't work, as the opts are eagerly loaded and hence it cannot find the requested modules.
Here is how it should work:
   {
  "patrickpichler/hovercraft.nvim",
  dependencies = {
    { "nvim-lua/plenary.nvim" },
  },
  event = "User AstroFile",
  opts = function()
    return {
      providers = {
        providers = {
          { 'LSP',        require('hovercraft.provider.lsp').new() },
          { 'Man',        require('hovercraft.provider.man').new() },
          { 'Dictionary', require('hovercraft.provider.dictionary').new() },
        }
      }
    }
  end,
}

I will update the README :)
Let me know if this doesn't solve the issue :)

The readme should be udpated now 😅

Hey, thank you, that fixed it!
Great plugin!


Random chance for showing chatbot

Add a feature flag whether the chat is enabled at all.
Also add a value for how many percent of users should get the chatbot displayed.
Needs to be a region setting probably.

https://github.com/digitalfabrik/integreat-cms/pull/2738#issuecomment-2124112802

Is there an issue for implementation in the cms?

https://github.com/digitalfabrik/integreat-cms/pull/2856


#410: Update python version for environment

Update python version for conda environments to solve an error:
ERROR: Package 'mlagents-envs' requires a different Python: 3.9.18 not in '<=3.10.12,>=3.10.1'

Hey, thanks for pointing this out 🤗 I merge your PR and then close the issue.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Hyperapp Community Projects

For current and new npm modules: Do we want to publish them as @hyperapp/gizmo scoped packages or regular hyperapp-gizmo prefixed packages?

Babel is also looking to use scoped packages, might be worth looking how & if they pick it up: https://babeljs.io/blog/2017/09/12/planning-for-7.0#using-npm-scoped-packages

Whatever path we choose, I hope most of those repos & projects can live under the new HyperappCommunity organization

I think we should not publish community projects under @hyperapp scope while we do not have naming collisions between repo owners. And it also less work for both @hyperapp npm scope owner and repo owner. I would reserve @scope for possible future official packages.

Scopes!!!
I like being able to do a quick poke into node_modules to see what kind of stuff is being used.

I like the idea of using the @hyperapp/ scope for HyperappCommunity packages, but who manages the publishing rights?

@SkaterDad Yes, that's the other issue. It's more work. I wouldn't mind inviting more people to the npm org (we have like 4 or 5 people currently there already).

Looks like we're using the @scoped packages now: https://www.npmjs.com/package/@hyperapp/transitions

Let's make it worth it! Only the creme de la creme. 🍨

@okwolf @JorgeBucaran Didn't mean to claim that transitions is creme-de-la-creme 😉   Sorry if I jumped the gun on this! -- I plead confusion from the many moves and directives that came in a short period of time.  The reasons I did it:

It bugged me to have hyperapp in the repo name since it's already under (the very long) HyperappCommunity. So I changed the name. And I like my packages named same as the repo.

Some packages in the community org are already doing it that way (html, router et al). Moving them to the community in a way sets a standard for how repos should be named and published.  (Unless we plan to name them hyperapp-router et c)

From here and slack I got the impression that the majority consensus, although not unanimous, is in favor of @-scoped packages.

... so it seemed the natural next step. But don't worry -- I can go back to publishing under the name hyperapp-transitions no problem :)
(And I'll hold off renaming my other packages awaiting further comments)

@JorgeBucaran I think there should be a standard among community packages -- or the community will look very messy. Perhaps the "creme-de-la-creme"-criterion should be a bar for being moved into community? (I say that realizing that some/all of my packages might be moved back out if that's how we decide)

@zaceno The three defining moments in the life of a Hyperapp Gizmo.

username/hyperapp-gizmo
HyperappCommunity/hyperapp-gizmo
hyperapp/gizmo

@JorgeBucaran 👍  good structure!
As you know, at first I advocated only a single org, but I see now that comes with ownership/curation issues. This structure is good.

@zaceno To be honest, right now I would prefer to go back to:
(1) and then (3) if the module gets to that level. But I had to write that up because, after all, I am the one who is responsible for the whole mess. 😓

Makes sense too. I wouldn't mind moving my packages back to zaceno/gizmo. There's always the awesome-list to get exposure. Except ... as long as there is a HyperappCommunity, I think that's where I want my packages, just not to give the impression that they're somehow experimental (unless they are ;) )
But if you decide to shut it down and have everyone move their packages back, that's fine with me!

@zaceno Well done. I went ahead and deleted it. Now it's only github.com/hyperapp.

Conclusion
Got a cool idea for a module you want to make that depends on hyperapp or extends hyperapp functionality, e.g., a higher order app, a utility library, a helper function? Use this simple template and publish it on npm as hyperapp-foo.
Think your module is relevant enough to be published as an "official", @hyperapp/foo? Create an issue or let us know on Slack and we'll take it for consideration. If it's approved, you'll be invited to the Hyperapp GitHub and npm organization so you can take care of your own module.


crowded with cells after second rotation of the view

Dear Jay,
thanks for your decent pod! Since v6.1.13 I am observing the following behavior:
I start the calendar in one orientation. All cells were indented as expected.

After rotating the device in one direction, sometimes the cells are indented as expected, sometimes it is like in this screenshot:

But in both cases I am observing an issue. After rotating the device again to another orientation, the view is crowded with cells at various positions:

After rotating the device there is a new (since v6.1.13) resizing behavior with a blank screen towards the lower end of the view. Once the resizing is completed the issue occurs.

I can only reproduce this behavior on an iPhone (and iPhone simulator). On the iPad I cannot observe that issue. It occurred first on v6.1.13. Up to v6.1.12 the cells were indented correctly and it worked fine.
Is this the behavior you described at point 4 in "common questions": "My views are being randomly repeated across dateCells"?
Thanks in advance!
János

the highest version 6 is version 6.1.6
Also, all errors like this has been fix in version 7.
Is it possible that you can update?

Yes, this effect is also there on 6.1.6. It was introduced with version 6.1.13.
Unfortunately, I cannot update to version 7 given the lack of support for iOS 8.
Do you have an easy workaround for that effect?
Otherwise I would simply stay on v6.1.12 and update to the recent version after increasing my deployment target.

See the thing is, version 6 is good. But there are issues that needs to be fixed.
This is why i completely re-engineered version 7.0 from the ground up. All issues like this are fixed.
Lets get version 7 compatible for you.
is the compatibility problem because of this variable in the 7.0 library? --> semanticContentAttribute
If it is, then I can make version 7 to be iOS 8 compatible for you.

closing until user responds.


Uploaded image never showed after uploading in panel

Hi.
I can't see image some times after uploading.
Image is totaly uploaded, but cms can't show me it.
What I need to change? What's can be problem?

Please provide more information about your server and the image you are trying to upload.


[bezierTools] suggestion to add a function for finding the closest point on a cubic curve

I just discovered how to find the closest point on a cubic curve using Newton–Raphson method. Please let me know if this is something that can be considered as an addition to bezierTools. Here is the code and demo and a sample visualization in drawbot as a gist.
Sample render

Nice. Can you modify it to return all solutions? There may be at least two or even three points at the same distance. Or maybe this is fine to have as is.

The analytical solution involves solving a quintic equation. I have some code that takes this approach, but it depends on numpy for the quintic solver. Happy to share as a reference.

interesting, thanks for sharing. Could you also provide a link or citation to where you discovered this (paper or source code etc.)?

It's a numerical brute-force. It samples n points, takes closest, then do Newton-Raphson to adjust.

I just updated the gist and now even with loops and inflection points, the solution looks visually accurate. I will post some distance transform sample to show the result. The function right now returns more than one point, but I'm not sure if this is really accurate or useful. Please let me know what you think.

interesting, thanks for sharing. Could you also provide a link or citation to where you discovered this (paper or source code etc.)?

It was from stack overflow, but for fitting a curve to a set of points. I can't find it, but it was used at the last step to make the curve fit better to the input points. As behdad said, it's basic a search algorithm (bisection) for the best time value. It's done by starting from a set of sample points on the curve. Then choosing a set of points that have the closest distance to the reference point. At the end newton method is used to refine the time value by looking at which proximity point, the derivative vector become perpendicular to the line crossing between sample and reference point.
I looked at many solutions, but each require a lot of code for implementation. There are some other implementations using c which is of course faster like this one. This repo uses a more analytical solution, but the math was beyond me.


Integration tests have been taking longer.

Fail after 10 minutes, not 5 minutes like we do now.
Hopefully both the bigtable and hbase cluster tests will fail less frequently, especially on developer machines.

LGTM


Destructuring assignment removes undefined from type when default value is given

Fixes #9341

@mhegazy I think you are the best person to look at this while @ahejlsberg is gone.

Looks good to me. i would give @ahejlsberg some more time to check it as well.

Sure. @ahejlsberg do you want to take a look?

:+1: Once you make the indicated change.


In Parse Dashboard email verification field in User collection is not displaying data.

We are using email verification for a new user and the user is getting email verification links to their Email.
Here the problem is when the user is created, as we have set email verification field to true, we are unable to see the same in parse dashboard User collection. In User collection it shows as an empty space for email verification field but when the same if we call through REST service we can find the email verification data as true/false.
Conclusion-
In parse dashboard in User collection email verification field is not showing data. It is showing empty or undefined. But using REST service we are getting the data. Dashboard having some issue with displaying emailverification field.

Please open on the https://github.com/parseplatform/parse-dashboard repository


In win11: System Error -> libdl.dll was not found

Maybe @guregu has an idea.

I only have a Windows 10 machine to work with but I'll see if I can reproduce 🙏

Submitted a fix at #294, the next release after that's merged should have a working Windows release.

Hopefully fixed for you now.
On Thu, Aug 3, 2023 at 8:00 PM no-e-in @.***> wrote:

—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/290, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEUXPYDAGNGDALV4JUDXTNZE3ANCNFSM6AAAAAA3CQRIUA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Btw, the Logtalk installer for Windows provide preliminary support for Trealla Prolog. But it's currently non-functional, most likely due to path representation issues on Windows. If those issues are solved, all the Logtalk distribution tests could be run.

Thanks, worth look into. I remember you once saying not to do anything
special for DOS/Windows paths, I may need to follow through on that.
On Sun, Aug 6, 2023 at 4:09 PM Paulo Moura @.***> wrote:

Btw, the Logtalk installer for Windows provide preliminary support for
Trealla Prolog. But it's currently non-functional, most likely due to path
representation issues on Windows. If those issues are solved, all the
Logtalk distribution tests could be run.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/290#issuecomment-1666734912,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSESVKUFS2IH6QUDIK43XT4YJNANCNFSM6AAAAAA3CQRIUA
.
You are receiving this because you commented.Message ID:
@.***>

ok


Deprecate mnemonic jp [hl]

It's still working, it just outputs a warning.
This mnemonic is confusing as it may be thought that the CPU reads the
value pointed by hl and jumps to it.

I guess you're planning on going ahead with the plans you thought about in #73? If you're planning on doing that, are you also planning on deprecating other mnemonics (e.g. ldi hl, a, which that PR was related to)?

Well, the others are probably more a personal choice... I don't intend to actually remove this one, just to tell people not to use it. And that's because it's incorrect.

I'll add a comment later to clarify the intention of the patch.

My bad, I didn't read correctly. Yes, I'll update the PR to warn about the other invalid mnemonics.

I've just fixed the commit title.


How can use it in Linux

I use it in windows for a long time.
Now I work in Linux enviroment , there is a  error  when I build expect.go by myself.
➜  go build expect.go
go build github.com/zetamatta/go-console/screenbuffer: build constraints exclude all Go files in /root/go/src/github.com/zetamatta/go-console/screenbuffer
# github.com/zetamatta/go-console
/root/go/src/github.com/zetamatta/go-console/handle.go:38:15: undefined: syscall.Handle
/root/go/src/github.com/zetamatta/go-console/handle.go:40:16: undefined: syscall.NewLazyDLL

Ignore my poor English, Thanks

Thank you for using expect.exe
It does not support Linux as platform because it reads console data with Windows native API by syscall library. I recommend the original Linux version of expect.
https://linux.die.net/man/1/expect .

@zetamatta
Thank you for your reply


Add Content - Funding (S)

As a user I want to read about the HARH funding so that I can see who are the funders or how to become a possible funder.
Acceptance Criteria
A/C 1: Displays 'Funding - Funding Partners, Become a Funder' content.
Implementation Notes
Note 1: Use the individual page template that Nishka created to create the Funding page.
Note 2: Add content to the page
Note 3: Ensure that the page matches and is aligned to the UI/UX.
Note 4: Link page to the menu bar.
See the content linked below.

How to become a funder content/form TBC.
HARH.Website.Content.docx

Font Family: Roboto Font Family @tersiakoetzee
Heading 1: 48px
Heading 2: 28px
Paragraph: 20px


Examples Review: Phase 2

I wanted to give the examples a spin, and can report the following findings:
Here are my setup steps:
$ git clone
$ cargo build --workspace
$ cd examples
$ cargo run --example

Available examples:
    client1
    client2
    fetch_and_cat
    ipfs_bitswap_test
    ipfs_ipns_test

cargo run --example client1 produces no output to stdout
cargo run --example client2 seems to hang indefinitely
cargo run --example fetch_and_cat seems to work, requires a CID. Maybe provide a default? I assume this will improve once we have DHT swarming operational
cargo run --example ipfs_bitswap_test seems to hang indefinitely.
cargo run --example ipfs_ipns_test panics, can probably be removed?

Overall these could be a lot more user-friendly and showcase the extent of the work that exists inside the crates.

cargo run --example fetch_and_cat seems to work, requires a CID. Maybe provide a default? I assume this will improve once we have DHT swarming operational

This was just added and I did include usage, runtime guidance and these comments:
    // this example will wait forever attempting to fetch a CID provided at command line. It is
    // expected to be used by connecting another ipfs peer to it and providing the blocks from that
    // peer.

Sadly using some default Cid doesn't really seem feasible, unless it was something we'd know would always be available. With client DHT this example would become more useful. Once I get rust-ipfs node running on my rasperrypi, maybe I can semi-consistently provide some previous release tarball :)
The rest of the examples are "legacy," or "early integration test cases." This is all I know of them:

cargo run --example client1 produces no output to stdout

This does not seem useful at all.

cargo run --example client2 seems to hang indefinitely

I have no idea what this could had done ever, as the path has zero segments. Perhaps different paths were tested manually using this.

cargo run --example ipfs_bitswap_test seems to hang indefinitely.

I was about to clean this up while working on the fetch_and_cat, but noticed I was already doing a +1k PR.
I remember trying this out as a go-ipfs 0.4.2x testing and the gist is that the first block should be downloadable in the example by connecting a node to it (as long as you can calculate the Cid for it outside the example), and the "block-want" is awaited forever until one is provided. The providing can be done on a throwaway go-ipfs node like echo -n block-want | ipfs block put.

The examples seem to be using logging for the output and env_logger defaults to only showing error messages unless you specify the logging level with the RUST_LOG env variable.
So you can see the output if you run the examples with for example:
$ RUST_LOG=debug cargo run --example client1

Another way would be to change the default log level used by env_logger so that you don't have to specify the RUST_LOG env variable when running the examples. This can be done by replacing:
env_logger::init();

with
env_logger::from_env(Env::default().default_filter_or("debug")).init();

The log messages should also give you some insight as to why some of the examples are hanging.

@r-marques Good point. I think the examples should be using just println for simplicity sake, maybe diagnostics to eprintln! if stdout is used for something useful, like the file contents with fetch_and_cat.
We may have actually had RUST_LOG overwriting code in the past in ipfs::IpfsOptions, and could be that the examples expected the automatic env rewriting. It was quite confusing not to have the usual RUST_LOG setting getting applied.

I agree that using println would be the way to go for the examples.


CCN202002013_class.tsv expresses column outdated

Currently CCN202002013_class.tsv expresses column in https://github.com/obophenotype/brain_data_standards_ontologies/tree/dosdp_based_pipeline/src/patterns/data/bds
does not match up with https://github.com/obophenotype/brain_data_standards_ontologies/blob/dosdp_based_pipeline/src/markers/CS202002013_Allen_markers.tsv
This is used to create subclass patterns in https://github.com/obophenotype/brain_data_standards_ontologies/blob/4170773534595[…]a295b2f4e90b905/src/patterns/dosdp-patterns/taxonomy_class.yaml
I can update the class file according to the markers file manually by using the PR equiv, however, would be good if there is something that would take the ensembl to convert to PR or something like that (I somewhat rmbr talking about this before @dosumis?)

I've removed all the curation of GABAergic types as they are all now X-like, which means the root "expresses" need to be curated on too

Added all PR terms to expresses column here: https://github.com/obophenotype/brain_data_standards_ontologies/commit/7ba14a108798b5ebe72db43a82c8d13f086bec2d
also made them all mouse specific


Fix Fibonacci Sequence text

Describe the Issue
This should be a relatively easy fix for a first-time contributor :)
This challenge says the first two numbers are 1 and 1 when in fact the first two numbers are 0 and 1.
The first few numbers are: 0, 1, 1, 2, 3, 5 and 8
So when you update the text to also check the tests and make sure this doesn't change any of the expected test outcomes.
Affected Page
https://www.freecodecamp.org/learn/javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/sum-all-odd-fibonacci-numbers
Your code

Expected behavior
The text should correctly state the first numbers as 0, 1, 1, 2, 3, 5 and 8
Screenshots
No response
System

Device: [e.g. iPhone 6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.04]
Browser: [e.g. Chrome, Safari]
Version: [e.g. 22]

Additional context
No response

An issue with the https://github.com/freeCodeCamp/freeCodeCamp/labels/first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum

The affected file can be found here: https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/02-javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/sum-all-odd-fibonacci-numbers.md

Hello!
I'm a rookie software developer and I'm looking for a "good first issue" to start contributing to open-source projects.
So could I be assigned to fix this issue please?


fix: Code: clean-up #8951

#8951 was a major change in the VS Code extension and caused quite a few problems. This PR is a catch-all for bugs and improvements in the new code.
This should fix:

#9284
this unreported bug
...and one or two uncaught exceptions I just found

The original lack of testing was my own fault, but this area of the VS Code API is also tricky for a couple reasons:

The FileSystem API does not list or warn about any exceptions, but FileSystemProvider (which FileSystem is a wrapper of, AFAICT) does.
At first glance, Uri.path looks like it works for FS operations. It does not, at least, on Windows. You need to use Uri.fsPath.

I only use Windows, so I need people on macOS, Linux, and (possibly) NixOS to test this.

/home/runner/work/rust-analyzer/rust-analyzer/editors/code/src/main.ts is not formatted

bors d+

Looks fine, I guess? I can't test it right now, but I'm in favor of merging it optimistically.

It can't make it worse than it is right now, can it?

I sure hope not :). I'll merge then.
bors r+


Select many on the list crashes the application

When I'm trying to select many torrents on the list, using keyboard arrows and shift Pico crashes every time.
Windows 10, PicoTorrent 0.17.0

https://ci.appveyor.com/project/picotorrent/picotorrent/builds/28606172
Try to download build for your CPU architecture (x86 or x64) - choose artifacts tab.

@dawidgorczyca please try the latest version and see if this is resolved. Feel free to reopen och create a new issue if it's not!