Fixed schema of IdentifierUris.

We've been facing the following error when running IAI in our Orchestrated E2E tests starting from 19.10.2021 (sample run):
2021-10-19T06:43:12.9538239Z ##[section]Starting: Run deployment with IAI
2021-10-19T06:43:12.9661593Z ==============================================================================
2021-10-19T06:43:12.9662352Z Task         : Command line
2021-10-19T06:43:12.9662876Z Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
2021-10-19T06:43:12.9663336Z Version      : 2.182.0
2021-10-19T06:43:12.9663721Z Author       : Microsoft Corporation
2021-10-19T06:43:12.9664196Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
2021-10-19T06:43:12.9664725Z ==============================================================================
2021-10-19T06:43:13.9099281Z Generating script.
2021-10-19T06:43:13.9189028Z Script contents:
2021-10-19T06:43:13.9197306Z Microsoft.Azure.IIoT.Deployment.exe
2021-10-19T06:43:13.9491855Z ========================== Starting Command Output ===========================
2021-10-19T06:43:13.9742259Z ##[command]"C:\Windows\system32\cmd.exe" /D /E:ON /V:OFF /S /C "CALL "C:\agent\_work\_temp\ccde4685-ad1b-428f-a8ec-d6cf4450cba4.cmd""
2021-10-19T06:43:15.2020190Z [06:43:15 INF] Starting full deployment of Industrial IoT solution.
2021-10-19T06:43:15.2072250Z [06:43:15 INF] Configured Azure environment will be used: AzureGlobalCloud
2021-10-19T06:43:15.2073824Z [06:43:15 INF] Configured TenantId will be used: ***
2021-10-19T06:43:15.2074734Z [06:43:15 INF] Configured ClientId will be used: ***
2021-10-19T06:43:15.2075379Z [06:43:15 INF] Configured ClientSecret will be used.
2021-10-19T06:43:16.4314578Z [06:43:16 INF] Configured subscription will be used: DisplayName: 'IOT-OPC-WALLS', SubscriptionId: '9dd2b4d0-3dad-4aeb-85d8-c3addb78127a'
2021-10-19T06:43:17.0446715Z [06:43:17 INF] Configured application name will be used: e2etesting2021101945
2021-10-19T06:43:17.5870210Z [06:43:17 INF] Configured to use existing resource group: False
2021-10-19T06:43:17.7867652Z [06:43:17 INF] Configured region will be used: eastus
2021-10-19T06:43:17.7998915Z [06:43:17 INF] Configured resource group name will be used: e2etesting2021101945
2021-10-19T06:43:17.8002619Z [06:43:17 INF] Creating Resource Group: e2etesting2021101945 ...
2021-10-19T06:43:18.1307647Z [06:43:18 INF] Created Resource Group: e2etesting2021101945
2021-10-19T06:43:18.1313604Z [06:43:18 INF] Registering resource providers ...
2021-10-19T06:43:20.7557626Z [06:43:20 INF] Registered resource providers
2021-10-19T06:43:20.7578444Z [06:43:20 INF] Creating service application registration ...
2021-10-19T06:43:20.8625236Z [06:43:20 ERR] Failed to create service application registration.
2021-10-19T06:43:20.8814458Z [06:43:20 ERR] Failed to deploy Industrial IoT solution.
2021-10-19T06:43:20.8815522Z Status Code: BadRequest
2021-10-19T06:43:20.8816341Z Microsoft.Graph.ServiceException: Code: HostNameNotOnVerifiedDomain
2021-10-19T06:43:20.8817627Z Message: Values of identifierUris property must use a verified domain of the organization or its subdomain: 'https://***/e2etesting2021101945-service'
2021-10-19T06:43:20.8818628Z Inner error:
2021-10-19T06:43:20.8819117Z 	AdditionalData:
2021-10-19T06:43:20.8819608Z 	date: 2021-10-19T06:43:20
2021-10-19T06:43:20.8820258Z 	request-id: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8820881Z 	client-request-id: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8821502Z ClientRequestId: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8821957Z
2021-10-19T06:43:20.8823105Z    at Microsoft.Graph.HttpProvider.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, Cancellation*** cancellation***)
2021-10-19T06:43:20.8824103Z    at Microsoft.Graph.BaseRequest.SendRequestAsync(Object serializableObject, Cancellation*** cancellation***, HttpCompletionOption completionOption)
2021-10-19T06:43:20.8825282Z    at Microsoft.Graph.BaseRequest.SendAsync[T](Object serializableObject, Cancellation*** cancellation***, HttpCompletionOption completionOption)
2021-10-19T06:43:20.8826262Z    at Microsoft.Azure.IIoT.Deployment.Infrastructure.MicrosoftGraphServiceClient.CreateApplicationAsync(Application applicationDefinition, Cancellation*** cancellation***)
2021-10-19T06:43:20.8829463Z    at Microsoft.Azure.IIoT.Deployment.Deployment.ApplicationsManager.RegisterServiceApplicationAsync(String serviceApplicationName, DirectoryObject owner, IEnumerable`1 tags, Cancellation*** cancellation***)
2021-10-19T06:43:20.8831327Z    at Microsoft.Azure.IIoT.Deployment.Deployment.ApplicationsManager.RegisterApplicationsAsync(String applicationName, DirectoryObject owner, IEnumerable`1 tags, Cancellation*** cancellation***)
2021-10-19T06:43:20.8832774Z    at Microsoft.Azure.IIoT.Deployment.Deployment.DeploymentExecutor.SetupApplicationsAsync(Cancellation*** cancellation***)
2021-10-19T06:43:20.8833813Z    at Microsoft.Azure.IIoT.Deployment.Deployment.DeploymentExecutor.RunFullDeploymentAsync(Cancellation*** cancellation***)
2021-10-19T06:43:20.8834489Z [06:43:20 INF] Configured to perform cleanup: False
2021-10-19T06:43:20.8835075Z [06:43:20 ERR] Unhandled exception
2021-10-19T06:43:20.8835659Z System.AggregateException: One or more errors occurred. (Code: HostNameNotOnVerifiedDomain
2021-10-19T06:43:20.8836535Z Message: Values of identifierUris property must use a verified domain of the organization or its subdomain: 'https://***/e2etesting2021101945-service'
2021-10-19T06:43:20.8837365Z Inner error:
2021-10-19T06:43:20.8838011Z 	AdditionalData:
2021-10-19T06:43:20.8838676Z 	date: 2021-10-19T06:43:20
2021-10-19T06:43:20.8839399Z 	request-id: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8840824Z 	client-request-id: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8842261Z ClientRequestId: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8843030Z )
2021-10-19T06:43:20.8843712Z  ---> Status Code: BadRequest
2021-10-19T06:43:20.8844574Z Microsoft.Graph.ServiceException: Code: HostNameNotOnVerifiedDomain
2021-10-19T06:43:20.8845982Z Message: Values of identifierUris property must use a verified domain of the organization or its subdomain: 'https://***/e2etesting2021101945-service'
2021-10-19T06:43:20.8847170Z Inner error:
2021-10-19T06:43:20.8848153Z 	AdditionalData:
2021-10-19T06:43:20.8848911Z 	date: 2021-10-19T06:43:20
2021-10-19T06:43:20.8849759Z 	request-id: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8850687Z 	client-request-id: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8851619Z ClientRequestId: d468a602-02c5-4fd5-a0d0-7ed9fe12ed0f
2021-10-19T06:43:20.8852132Z
2021-10-19T06:43:20.8853365Z    at Microsoft.Graph.HttpProvider.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, Cancellation*** cancellation***)
2021-10-19T06:43:20.8854873Z    at Microsoft.Graph.BaseRequest.SendRequestAsync(Object serializableObject, Cancellation*** cancellation***, HttpCompletionOption completionOption)
2021-10-19T06:43:20.8856376Z    at Microsoft.Graph.BaseRequest.SendAsync[T](Object serializableObject, Cancellation*** cancellation***, HttpCompletionOption completionOption)
2021-10-19T06:43:20.8857941Z    at Microsoft.Azure.IIoT.Deployment.Infrastructure.MicrosoftGraphServiceClient.CreateApplicationAsync(Application applicationDefinition, Cancellation*** cancellation***)
2021-10-19T06:43:20.8859933Z    at Microsoft.Azure.IIoT.Deployment.Deployment.ApplicationsManager.RegisterServiceApplicationAsync(String serviceApplicationName, DirectoryObject owner, IEnumerable`1 tags, Cancellation*** cancellation***)
2021-10-19T06:43:20.8861783Z    at Microsoft.Azure.IIoT.Deployment.Deployment.ApplicationsManager.RegisterApplicationsAsync(String applicationName, DirectoryObject owner, IEnumerable`1 tags, Cancellation*** cancellation***)
2021-10-19T06:43:20.8863241Z    at Microsoft.Azure.IIoT.Deployment.Deployment.DeploymentExecutor.SetupApplicationsAsync(Cancellation*** cancellation***)
2021-10-19T06:43:20.8864539Z    at Microsoft.Azure.IIoT.Deployment.Deployment.DeploymentExecutor.RunFullDeploymentAsync(Cancellation*** cancellation***)
2021-10-19T06:43:20.8866694Z    at Microsoft.Azure.IIoT.Deployment.Deployment.DeploymentExecutor.RunFullDeploymentAsync(Cancellation*** cancellation***)
2021-10-19T06:43:20.8867888Z    at Microsoft.Azure.IIoT.Deployment.Deployment.DeploymentExecutor.RunAsync(Cancellation*** cancellation***)
2021-10-19T06:43:20.8868893Z    --- End of inner exception stack trace ---
2021-10-19T06:43:20.8869854Z    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
2021-10-19T06:43:20.8871148Z    at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, Cancellation*** cancellation***)
2021-10-19T06:43:20.8872167Z    at System.Threading.Tasks.Task.Wait()
2021-10-19T06:43:20.8873167Z    at Microsoft.Azure.IIoT.Deployment.Program.Run(IConfigurationRoot configuration)
2021-10-19T06:43:20.9572598Z ##[error]Cmd.exe exited with code '1'.
2021-10-19T06:43:20.9954393Z ##[section]Finishing: Run deployment with IAI

The cause of the error is that the schema that we were using for generating values of IdentifierUris when creating new App Registrations is no longer supported. We were using the following schema:

https://{TenantId}/{ApplicationName}

Recently the following requirement has been added when performing API calls to Active Directory, which defines fixed schemas for IdentifierUris property:

AppId Uri in single tenant applications will require use of default scheme or verified domains

I've changed our code to use the following schema for IdentifierUris properties:

api://{TenantId}/{ApplicationName}

Here is a run of Orchestrated E2E pipeline where one can see that the change fixes the issue with App Registrations.


Add codeclimate/eslint and fix issues

Add codeclimate/eslint and fix issues

:white_check_mark: coverage increased from 50.48% to 57.01%


Multiple callback instances

📚 Documentation
class Counter(Callback):
    def __init__(self, what="epochs", verbose=True):
        self.what = what
        self.verbose = verbose
        self.state = {"epochs": 0, "batches": 0}

    @property
    def state_key(self):
        # note: we do not include `verbose` here on purpose
        return self._generate_state_key(what=self.what)

    def on_train_epoch_end(self, *args, **kwargs):
        if self.what == "epochs":
            self.state["epochs"] += 1

    def on_train_batch_end(self, *args, **kwargs):
        if self.what == "batches":
            self.state["batches"] += 1

    def load_state_dict(self, state_dict):
        self.state.update(state_dict)

    def state_dict(self):
        return self.state.copy()

# two callbacks of the same type are being used
trainer = Trainer(callbacks=[Counter(what="epochs"), Counter(what="batches")])

The code above is quoted directly from https://lightning.ai/docs/pytorch/stable/extensions/callbacks.html as an example to support multiple instances of the callback to the Trainer.
In the example, self._generate_state_key(what=self.what) is used, which is a protected method from the parent Callback class. I am just wondering if it would be better to provide a public method in the parent class to expose that functionality? Thanks.
cc @borda

I think that's a good suggestion! I don't mind making this public. But note, in general I think we would advise users to construct their own key directly. The code is basically very trivial:
    def _generate_state_key(self, **kwargs: Any) -> str:
        return f"{self.__class__.__qualname__}{repr(kwargs)}"

I think we could also just inline this code in the docs example. That's probably the cleanest!


Added three checks proto-gen,proto-format & update-swagger-docs in proto.yml

Added the required checks in .github/workflows/proto.yml

closes: #1403
Added the required checks in .github/workflows/proto.yml

make proto-format
make proto-gen
make update-swagger-docs

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit and integration tests
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added relevant godoc comments.
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Review Codecov Report in the comment section below once CI passes

Due to the age of this and the comments, I'm going to close this. Feel free to update it and re-open it.


Add abbrev_commit (first 7 chars of commit)

In light of #39 and no need really to store full commit in the path.


V2

Previously our process was to only merge commits into main which have been deployed. Now we are updating our process to start merging things into main which have been reviewed, but not necessarily deployed into production or staging.
This PR reconsiles these two processes, so that once this PR is merged, the main branch will have the canonical code that represents our vibc contracts, which contains a mix of code we had from our previous audit, and code we have added to main and deployed into production since our audit.
Note : all changes in this PR should have already been reviewed, either from a PR to v2 directly (i.e. for the audit) or rebased from main (i.e. changes to main after the audit) .
The features added in this PR (which were already included in the past audit) are:

implement channel close
multiclient
misc. doc/security fixes

The only additional changes to these features which differed from the code in our previous audit were the changes required to rebase the new changes we've committed to our main branch since our previous audit. These changes in main include:

uch storage proxy
reodering of dispatcher methods
gas griefing fixes (already included into main so they were ported over when this branch was rebased)

Please split the channel close: update api commit such that we end up with a single commit that adds the ch-close related changes and another commit that fixes/tweaks timeouts
Also, please squash reoder Channel struct to be storage compatible into the first and only ch-close related commit. Again, one feature fix per commit.
Please squash these three commits into "add multiclient support"

add multiclient support + get existing test suite working
simplify connection -> client mapping
clean up client setter naming + docs

Finally, the "+ get existing test suite working" related changes must not be a separate commit but rather be part of those commits that broke the tests. I suggest running git rebase -i main -x 'forge test' to find the exact offender and apply fixes accordingly.

One last note, please do not "squash and merge" when finished but rather "rebase and merge" or all the comments above won't make any difference :D

Please split the channel close: update api commit such that we end up with a single commit that adds the ch-close related changes and another commit that fixes/tweaks timeouts

Done! Should be split into a ch close commit and a sperate timeout timestamp commit

Also, please squash reoder Channel struct to be storage compatible into the first and only ch-close related commit. Again, one feature fix per commit.

This is a great suggestion, now the storage gap should be fixed in the ch-close commit as per your request

Please squash these three commits into "add multiclient support"

add multiclient support + get existing test suite working
simplify connection -> client mapping
clean up client setter naming + docs

Done!

Finally, the "+ get existing test suite working" related changes must not be a separate commit but rather be part of those commits that broke the tests. I suggest running git rebase -i main -x 'forge test' to find the exact offender and apply fixes accordingly.

For context - I always rebase with -x "forge test && yarn lint && forge build --sizes" so I think the "+ get existing test suite working" should have already been working with the test suite. But I agree this commit was admittedly poorly named , so I renamed it to "multi client support" to be clearer. Now (as before) all commits always should pass  the forge test && yarn lint && forge build --sizes command


Fix: load releases for all namespaces at once

Load releases for all namespaces at once if All namespaces context is selected
https://user-images.githubusercontent.com/9607060/107771327-a994ad00-6d4b-11eb-968e-71a930b71311.mp4
Fixes #2137
Signed-off-by: Alex Andreev<EMAIL_ADDRESS>

Lens 4.1 set default namespace selected as default, so I think the inital view should reflect on what's selected in namespace filter. Now releases from all namespaces are displayed.

Lens 4.1 set default namespace selected as default, so I think the inital view should reflect on what's selected in namespace filter. Now releases from all namespaces are displayed.

There was 1 missed loadAll() call without namespace arguments. Fixed.

https://user-images.githubusercontent.com/9607060/107929257-72f8a580-6f8a-11eb-9ba3-fcc829f77465.mp4


[BUG]what‘s is that？I'm getting an error.

I am sorry,I don't know what's the error'

This happens in both a standard installation of Windows (10) or (Ubuntu/CentOS) Linux.
It does not happen on Mac OS X(13.2.1) and it does not happen on a Raspberry Pi 3B with the current Raspberry Pi OS

What can I do for it.

Make sure to manually log in to your bing account, go to https://rewards.bing.com/ and click "Join rewards program" or "Join Bing Rewards" The script will not do that for you.

I have joined rewards when using the script, and I also have some points.

You dont seem to be connecting there might be an issue with the chrome driver you installed. try to download an older version
-Install ChromeDriver from https://chromedriver.chromium.org/downloads
Place the file in X:\Windows (X as your Windows disk letter)

Thank you for your help, I will try it tomorrow, thank you very much. @AlexyGalaxy 😃

I tried but encountered a new problem

@AlexyGalaxy

What region are you in? US or?

I used Authentic passwordless login Microsoft so there was a problem, I will turn off passwordless login Microsoft and then try again, thank you for your help!

It sounds like you never got the script fully running because it is looking for a particular element that is used in you region. Are you outside of the US?
Try changing waitUntilVisible to the code below and let me know what happens.
waitUntilVisible(browser, By.XPATH, '//*[@id="navs"]/div/div/div/div/div[4]/div/button/span/i', 20)
Also disable headless mode by commenting out line 46 and 47 with #. Then watch the script open chrome and look to see where it is stuck. (When done testing make sure to delete the # to rentable headless mode.
#if headless_mode : #comment out to disable headless mode (makes window visable)
#options.add_argument("--headless") #comment out to disable headless mode (makes window visable)
Pause the script by placing the code located below, before waitUntilVisible and once again after waitUntilVisible. Then run the script and post the screen shot here. If the browser is taking too long to load, increase the number at the end of waitUntilVisible to 30-50(this is the time waited)
print('[TEST] Press any key to continue')
input()
If it doesnt work read this:
The way this line of code works is by grabbing the XPATH information. When your script is paused and waiting for your second input to continue, click on the browsers that was opened and running the script, press F12(this will open a page showing the browsers code), then press ctrl+shift+c, then hover over the top banner of the website and right click. Now in that new page that shows the browsers code there is a line highlighted. Right click that line and select Copy>Copy XPATH. Paste that line of code within waitUntilVisible.
waitUntilVisible(browser, By.XPATH, 'PASTE_XPATH_CODE_HERE/DELETE_THESE_WORDS_WITHIN_THE_QUOTES', 20)
let me know if that helps. If so please commnet below with the changes you made to the script.
Someone had this exact issue but unfortunately they did not post the exact changes they made.
https://github.com/charlesbel/Microsoft-Rewards-Farmer/issues/152

When I cancel the passwordless login, I log in successfully but it seems that it cannot run normally.

@AlexyGalaxy I disabled headless mode and ran the script and found an error, and got stuck on the following interface.

@AlexyGalaxy   I disabled headless mode and ran the script and found an error, and got stuck on the following interface.

You are not in the US so i cant be of much help...
Try to pause the script by placing the code located below, before waitUntilVisible and once again after waitUntilVisible. Then run the script in headless mode and wait for the page.
print('[TEST] Press any key to continue')
input()

Once the script is pasues and waiting for an input you need to click on the browser that was opened and is running the script, press F12(this will open a page showing the browsers html code), then press ctrl+shift+c, then hover over the top banner of the website and right click on Rewards. Now in that new page that shows the browsers code there is a line highlighted. Right click that line and select Copy>Copy XPATH. Paste that line of code within waitUntilVisible.

waitUntilVisible(browser, By.XPATH, 'PASTE_XPATH_CODE_HERE/DELETE_THESE_WORDS_WITHIN_THE_QUOTES', 20)

This part of the script is trying to open the rewards dashboard. If this doesnt fix the issue you next solution is to manually direct the script using the code below insdead of waitUntilVisible.
time.sleep(3)
browser.get('ENTERURLHERE.com')
time.sleep(3)

Like i said there have been 2 other people with this issue and unfortunately they did not post their solution. if you figure it out please post what fixes this issue so i may work it into the code.
https://github.com/charlesbel/Microsoft-Rewards-Farmer/issues/154
https://github.com/charlesbel/Microsoft-Rewards-Farmer/issues/152

I am a beginner in python, your code is very difficult for me, I’m sorry I can’t find out what’s wrong with it. I reverted all the changes and turned off headless mode, then tried running it several times and it seemed to work once. Here is the successful content.

seems like it did all searches as intended. I cannot troubleshoot your issues bc I am in the US and you are in Asia. I told you the steps i take to edit XPATH code when bing rewards changes their site there is not much more i can do. sorry

@AlexyGalaxy I'm facing this issue too and I'm in India. I think what's happening is, On Asia/India Microsoft acounts page, we don't have the rewards tab. Since because of this, the browser is not able to find the element.

I am having lots of issues with the script today. Seems bing is updating/updated their site.
During log in I am sometimes asked to click my account and reEnter my password. Then both of those links to the rewards dashboard are no longer working/take too long.
I will wait until tomorrow to see if things start to work again or I can figure out a solution.

@Imgkl So both links bring you to the rewards dashboard?

Yes @AlexyGalaxy, Both links takes me to the rewards dashboard.

Try something for me... Put your script into headless mode, then delete the waitUntilVisable function and the if else statement after and paste the code below:
time.sleep(random.randint(10, 15))

try :
    prYellow('[TEST] Loading https://rewards.bing.com/') #test
    BASE_URL = 'https://rewards.bing.com/'
    browser.get(BASE_URL)
except:
    prRed('[ERROR] Could not Loading https://rewards.bing.com/')#test
    pass

It should look like this.

Run this with headless mode disabled and let me know the outcome.

Getting 504 when I try to access through the script. but when opened manually it shows the dashboard.

Welp this is not good. Not sure about a solution. Maybe they are updating part of their network... or they figured out how to stop selenium users from accessing their site. I will wait until tomrrow to try again.
If you get something working please post it here.

weird. In the same selenium window, I was able to open rewards.bing.com without any issues.
Sure, If I find anything useful, I'll ping here.

The issue no longer occurs. It must have been an issue with bing. The code i provided you does work instead of waitUntilVisable function

I am a beginner in python, your code is very difficult for me, I’m sorry I can’t find out what’s wrong with it. I reverted all the changes and turned off headless mode, then tried running it several times and it seemed to work once. Here is the successful content.

where i can find the 3.0 version?

Updated verison is here on my github. Make sure to set up the Logger and errLoger (read the README) https://github.com/AlexyGalaxy/Microsoft-Rewards-Farmer

Fixed with v3.0 #188


Default answer isn't working

Hey guys, for the third question below the default answer is not being treated.
When seeing (y\N) on the end of a terminal question is expected that the upper case letter is the default one, and so if the user just hits return then that should be the response.
The other thing I notice is the forward-slash (y\N) instead of a slash (y/N), which is more common. A little bit of IMO.

https://github.com/aziontech/azion/pull/670 @tiagokrebs by default if you press enter it understands as no this was added in the latest version

Resolved in the latest deploy


GD-42: Rewrite doubler to allow double core functions

Describe What
GdUnit4 no longer works to mock/spy on core functions.
Describe Why
With Godot 4 it is no longer allowed to override core functions which breaks the current doubler implementation.
Dev hints
Follow the new double prototype to allow double core functions.

Disable override errors by @warning_ignore("native_method_override")

Godot Issues:
https://github.com/godotengine/godot/issues/55024
https://github.com/godotengine/godot/issues/67461

I'm having a lot of behavior issues with mocks  even with custom functions of my classes. is this expected?
I can verify events on mock functions, but cannot override the default return value.
I don't see signals using the double code, but I also have issues with getting that to work.

Oh man, I just realized Im talking to the same person from Godot engine GitHub issue page about event propagation. :) i apologize if I'm clouding the water over there I am using your unit test framework and removing the check to run headless for my ci.
Anyway, I've done a little more trouble shooting and I think there is an issue with returning a custom value and using the "any" matchers. If I setup the do_return on the mock with the same argument values expected, values passed by the tested class, then it will return the custom value. If I use the any matchers then I will only get the default return.
This issue may be different then this one, if I have time I can create a separate issue.
Thanks

if you found such issues about mocking please create an new bug issue with steps to reproduce, this will help me to shedule the fix.
Thanks

@MikeSchulze Discovering GdUnit4 was exciting, offering a valuable solution for testing my C# Godot4 game through its sleek test runner and plugin. However, my enthusiasm was tempered upon realizing that the mocking/spying feature is exclusively available for GdScript, as illustrated in this example. This limitation presents a significant drawback for me, given that mocking and spying are fundamental concepts in testing, and their absence in C# testing diminishes the utility of GdUnit4 for my specific needs.
I acknowledge the positive step in addressing this concern with the statement:

GdUnit4 no longer works to mock/spy on core functions.

However, I believe that rectifying this limitation for C# should be given higher priority.
Additionally, it would be beneficial to communicate this more prominently in the documentation. Presently, users only become aware of this restriction when exploring the Advanced Testing section, and bringing attention to it more prominently can help manage expectations and guide users effectively.

Thanks for your feedback, that is very valuable for me.
Mocking and Spy is not offered by GdUnit for the C# version because there are already enough mock frameworks for C#. You should be able to integrate and use other mock frameworks without any problems.
The C# support is currently also limited, as I have received little to no feedback on the C# version.
But the API is expandable, and feature requests can be created at any time.


Added the contact us form

Made changes to index.html file and pasted the code
made changes to styles.css file and pasted the code

Form looks great! I have a few suggestions. Could you make it look like this instead?

Change bg illustration max-width to 100vw (I saw a 1100ish value somewhere in your CSS)
Change the inner container max-width to 80vw
Add a white (?) Submit button instead of the plain-text "Send". Use the below button style:

<!-- HTML !-->
<button class="button-38" role="button">Button 38</button>

/* CSS */
.button-38 {
  background-color: #FFFFFF;
  border: 0;
  border-radius: .5rem;
  box-sizing: border-box;
  color: #111827;
  font-family: "Lato";
  font-size: .875rem;
  font-weight: 600;
  line-height: 1.25rem;
  padding: .75rem 1rem;
  text-align: center;
  text-decoration: none #D1D5DB solid;
  text-decoration-thickness: auto;
  box-shadow: 0 1px 3px 0 rgba(0, 0, 0, 0.1), 0 1px 2px 0 rgba(0, 0, 0, 0.06);
  cursor: pointer;
  user-select: none;
  -webkit-user-select: none;
  touch-action: manipulation;
}

.button-38:hover {
  background-color: rgb(249,250,251);
}

.button-38:focus {
  outline: 2px solid transparent;
  outline-offset: 2px;
}

.button-38:focus-visible {
  box-shadow: none;
}

Add the references/sources for your form design, in case any


Fix toggling of MenuItem and Selectable with build_with_ref

Selectable or MenuItem should be toggled on click when called with build_with_ref.
This is the behavior that is done in ImGui when  bool ImGui::MenuItem(const char* label, const char* shortcut, bool*p_selected, bool enabled) is called.
Before the fix: Cannot toggle

After the fix: Can toggle (expected behavior)

With this fix, the test_window_impl example works just as the upstream C++ ImGui demo works.

Thanks! :smile:


Update MediaElch.nuspec

@sumo300 I wanted to inform you that the ZIP naming changes a bit. We now build with Qt5 and Qt6. The latter is for Windows 10 and later.

MediaElch_win_7_8_Qt5_2.10.0_2023-02-05_20-06_git-master-960303af.zip
MediaElch_win_10_or_later_Qt6_2.10.0_2023-02-05_git-960303af.zip

This shouldn't be a necessary change.  The nuspec is automatically updated from the URL the pipeline grabs from GitHub when it's posted.  I'll double check when the next version gets posted to make sure the script grabs the right one.

@bugwelle Please see the issue below.  This will be fixed soon and should trigger a release to Chocolatey.
https://github.com/sumo300/chocolatey-packages-au/issues/3


[Feature Request] Ability to add xhtml:link alternates while manually adding dynamic URLs

Clear and concise description of the problem
I am currently developing a multilingual website using @nuxtjs/i18n and @nuxtjs/prismic.
The project in in SSR mode, and while waiting for a proper i18n support, the possibility to manually add alternate versions of a page in the sitemap would be really helpful.
Suggested solution
sitemap: {
  // provide dynamic URLs to be included
  urls: async () => {
    const blogPages = await getBlogPages()

    return blogPages.map((page) => ({
      url: `/blog/${page.slug}`,
      lastmod: page.updatedAt,
      changefreq: 'daily',
      priority: 0.8,
      XHTMLLinks: [
        {
          rel: 'alternate',
          hreflang: 'fr',
          // I guess this would need to be a full url to support i18n's differentDomains feature
          href: `https://www.example.com/fr/blog/alternate-slug`
        },
        // ...
      ],
    }))
  },
},

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Whoops, didn't check the doc thoroughly enough
Already available with:
sitemap: {
  // provide dynamic URLs to be included
  urls: async () => {
    const blogPages = await getBlogPages()

    return blogPages.map((page) => ({
      url: `/blog/${page.slug}`,
      lastmod: page.updatedAt,
      changefreq: 'daily',
      priority: 0.8,
      links: [
        {
          lang: 'fr',
          href: `https://www.example.com/fr/blog/alternate-slug`
        },
        // ...
      ],
    }))
  },
},


AMPI's Hindexed datatype is broken

Original issue: https://charm.cs.illinois.edu/redmine/issues/1143

Running the hindexed test in charm/tests/ampi/mpich-test/pt2pt/ results in a segfault.
I am suspicious of the way that Hindexed's constructor calls Indexed without converting the byte offsets into element offsets... Hindexed_block does not have a test, but it could be suffering from the same issue.
Parallel HDF5 makes heavy use of the H{vector, indexed, indexed_block} MPI datatypes.

Original date: 2016-07-21 04:23:18

Indexed datatype fix: ~~https://charm.cs.illinois.edu/gerrit/#/c/1324/~~ https://github.com/UIUC-PPL/charm/commit/09f872581d3b377d8b23dfc92223de855c4ec2ab

Original date: 2016-07-21 14:09:53

Datatype related tests in tests/ampi/mpich-test/pt2pt that currently fail:
hindexed
hvectest2
typeub
typeub3
dataalign
getelm
sendrecv4
I think many of these failures are related to our poor handling of LB and UB...

Original date: 2016-07-27 14:45:58

Patch set #6 fixes most of these tests, the exceptions are listed below: http://charm.cs.illinois.edu/gerrit/#/c/1321/
getelm fails with "Wrong number of elements for struct recv; got 1001 expected 24"
sendrecv4 fails with many errors
These errors will be fixed in separate commits.


Server: add setuid/setgid capabilities

We add tree new CLI flags to cty serve:

--unix-socket-path: path pointing to the unix socket. Defaults to
./curiosity.sock
--user-name: name of the user we want to run curiosity for.
--group-name: name of the user we want to run curiosity for.

On a production setting, we often like to bind the unix sockets to
/run. You need to be root to do that. The idea is to start the
software as root, let it bind its socket in /run, then setuid/setgid
the process to its definitive user/group.
We decided not to change the state.json uid/gid. It means that we'll
have to "manually" set the appropriate permission. Likely via the
service pre-start procedure. It might be a bad idea we want to
revisit, it might be the right way to do it, only experience will
tell on that one.
We also update the curiosity systemd service to reflect this change.

So, let me try to rephrase what it's doing: the process, typically cty serve, starts as root, so that it can create a UNIX-domain socket in /run.  It does create the socket, changes itself its ownership to curiosity:curiosity, then sets its own uid/guid to the same thing.
So far so good.
I was thinking initially to let dynamically users of the web application start and stop the UNIX-domain socket serving thread. This is what I did for the email processing thread (it's nice to kill that thread and see that outgoing emails remain in the TODO state when the thread is not running; and in cty run, that thread is not running, so that actually processing emails can be an explicit command in the cty run script).
For the UNIX-domain thread, that's not really necessary (to kill/spawn it while the HTTP server is running). But what if I wanted that to be possible ? Once the server has change its own uid/gui, could that thread be started again and create the socket in /run ?
So as I've said, that's not really a problem.
Do you think it's elegant to change the uid/gui in a forkIO thread though ? Here too it's not a big deal if we let it that way for now.


pinCertificates ServerTrustPolicy  wrong behavior of  evaluate pass the SecTrust when choice validate chain and miss  intermediate certificate

when i use pinCertificates ServerTrustPolicy, the certificate miss  intermediate certificate,
and i choice validate chain , the evaluate result is pass , This is an unexpected result.
The following is the unit test code
    func testThatMissingIntermediateCertificateInChainFailsEvaluationWithoutHostValidation() {
        // Given
        let host = "test.alamofire.org"
        let certs = [
            TestCertificates.leafDNSNameAndURI,
            TestCertificates.rootCA,
        ]
        let trust = TestTrusts.trustWithCertificates(certs)
        // When
        let serverTrustPolicy = ServerTrustPolicy.pinCertificates(certificates: certs, validateCertificateChain: true, validateHost: false)
        let serverTrustIsValid = serverTrustPolicy.evaluate(trust, forHost: host)
        // Then
        XCTAssertFalse(serverTrustIsValid, "server trust should not pass evaluation")
    }

Alamofire Environment
Alamofire version: 4.8.2
**Xcode version:**11.1
**Swift version:**4.0
Platform(s) running Alamofire: iOS
macOS version running Xcode: 10.4.4

Our current tests still fail for this scenario. Could you post the code you're actually using? Have you been able to create a test that replicates your issue?

code address: https://github.com/a5978445/Alamofire.git
search testThatMissingIntermediateCertificateInChainFailsEvaluation test case
when i use SelfSignedCertificates ,  The integrity of the certificate chain cannot be verified. I am not sure if this is an issue for a self-signed certificate

Yes, if you're using a self-signed certificate, there is no certificate chain to verify.


#1006 Added Gulp Setup and Troubleshooting to docs/0.4.x

Gulp Setup and Troubleshooting sections added to the 0.4.x docs.

@zeldar Besides the couple line comments above, looks good.
THANKS A BUNCH! :-D

@codydaig Did that squash work?

@zeldar Yes  the squash worked. Thanks!


Validate old globalnet only if globalnet enabled

During an upgrade we should only check if old globalnet config
is valid if globalnet is currently enabled.
Signed-off-by: Vishal Thapar<EMAIL_ADDRESS>

The upgrade still fails:

Error validating existing globalCIDR configmap: invalid GlobalnetCidrRange: invalid CIDR address:

The upgrade still fails:

Error validating existing globalCIDR configmap: invalid GlobalnetCidrRange: invalid CIDR address:

Should pass now.


QUESTION: Is it possible to write custom linting rules, including Quick Fix information, for frontmatter?

I know I can access frontmatter data using params.frontMatterLines; however, the onError function seems to operate solely on the params.lines array. Is there any way to write custom linting rules to validate text in the frontmatter area of a document?

Not directly. Front matter is so varied that I have not thought to support something like this.
But if you want to lint front matter, I suppose you could report errors for line 1 of the Markdown. It would be slightly wrong, but maybe good enough for your purposes.

Your decisions makes sense. I think everything is great in markdownlint as it is. The one thing that would make it perfect would be the ability to tell onError which array to operate on so people could write custom linters for their frontmatter, too, since it is only the reporting that doesn't currently work.
I'll try doing what you suggested with line one of the params.lines array.
Thanks for your response!


Move animation rules near to transition rules

As per suggestion, animations do belong near transition rules

Thanks! Merged in 544d39ad33581afd4e5852d41d5eaa8a1b5e4849


"OffscreenCanvas is not defined" on load in Firefox 103.0

Doesn't seem to be working on the latest Firefox, 103.0.
App doesn't function, and dumps this to the console:
Uncaught ReferenceError: OffscreenCanvas is not defined
    LoadImage https://mrogalski.eu/ansi-art/script.js:104
    onRuntimeInitialized https://mrogalski.eu/ansi-art/script.js:136
    doRun https://mrogalski.eu/ansi-art/ansi.js:1
    run https://mrogalski.eu/ansi-art/ansi.js:1
    runCaller https://mrogalski.eu/ansi-art/ansi.js:1
    removeRunDependency https://mrogalski.eu/ansi-art/ansi.js:1
    receiveInstance https://mrogalski.eu/ansi-art/ansi.js:1
    onmessage https://mrogalski.eu/ansi-art/ansi.js:1
    loadWasmModuleToWorker https://mrogalski.eu/ansi-art/ansi.js:1
    receiveInstance https://mrogalski.eu/ansi-art/ansi.js:1
    receiveInstance https://mrogalski.eu/ansi-art/ansi.js:1
    receiveInstantiationResult https://mrogalski.eu/ansi-art/ansi.js:1
    promise callback*createWasm/instantiateAsync/< https://mrogalski.eu/ansi-art/ansi.js:1
    promise callback*instantiateAsync https://mrogalski.eu/ansi-art/ansi.js:1
    createWasm https://mrogalski.eu/ansi-art/ansi.js:1
    <anonymous> https://mrogalski.eu/ansi-art/ansi.js:1
script.js:104:16

Looks cool, though. Can't wait to give it a spin. :sunglasses:

Thanks! I've published the fix. https://mrogalski.eu/ansi-art/ should be working now :)


Output for small differences in golden tests is misleading.

Use case
For golden test failures where there is a very small difference between the running test and the golden file, the output currently says "0.00% diff detected". While the test does error out correctly, the output makes it feel more like an error with the framework instead of a valid test failure.
Proposal
Update the output when failing at small margins like this to show a non-zero value. Current ideas:

Round to the first non-zero digit. This will potentially make the output longer, but will make sure there's always a non-zero value.
If rounding would output "0.00%", instead output "X pixels did not match" or similar
If rounding would output "0.00%", instead output "a small diff was detected" or similar

Scientific notation is another option. It will be more precise than "a small diff was detected", but also format more nicely than "X pixels did not match" in cases where the test is severely broken.


Filter scenarios by status + display Summary

Summary
Add a filter in the HTML report to only keep scenarios by status. The idea in the long term will be to hide by default scenarios that were not ran.
Details

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

That's a first draft and looks pretty awful, but provides an idea of what this provides :D
Types of changes

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

Checklist:

[ ] The change has been ported to Java.
[ ] The change has been ported to Ruby.
[x] The change has been ported to JavaScript.
[ ] The change has been ported to Go.
[ ] The change has been ported to .NET.
[ ] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have updated the CHANGELOG accordingly.

I've updated a bit the styling, so it could be a starting point to use the filter as a summary of the execution (see issue #1056) - I'll check if I can do something about displaying more info in a third box (like what's in the meta message + execution time for example)

I like how the header/overview section is emerging. I agree the summary can fit in here too.

I've added the content of the Meta message as a base for the execution summary:

I think we can add more useful information later on, such as the overall execution duration. I'm not 100% sure about the order of the items, maybe the search is a bit more important than the execution summary.


IE11 - remaining time position

IE11 has a problem with alignment of the remaining time:

top-left instead of bottom-right? Weird.
I'll look into it when I can. Thanks for reporting. :heart:

wait, it's all messed up, period. :(
Should be like this:

I quickly tried to check where the problem is. There is a width set to 100%. After removing it it looks good also in Chrome but I haven't had time to test it properly after making a change in source code - only web inspector in IE.

Let's run with it and see how it goes. I tested with Edge and Chrome as well.
Fix will be in v1.0.12

It looks good, now in IE11.

Thanks for the feedback. :heart:


[SPARK-16438] Add Asynchronous Actions documentation

What changes were proposed in this pull request?
Add Asynchronous Actions documentation inside action of programming guide
How was this patch tested?
check the documentation indentation and formatting with md preview.

Can one of the admins verify this patch?

@AmplabJenkins I dont know i just create the issue on JIRA and make changes and make pull request for merge , I think it is valid pull request because in real world all application need non blocking execution. So if its is valid then merge it.

@phalodi it's a bot, not a person.

Jenkins test this please

Test build #61979 has started for PR 14104 at commit aba737f.

Test build #61980 has started for PR 14104 at commit aba737f.

Test build #61980 has finished for PR 14104 at commit aba737f.

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

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

Merged build finished. Test PASSed.

Test build #61979 has finished for PR 14104 at commit aba737f.

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

Merged build finished. Test PASSed.

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

Can you paste a screenshot of the doc?

@rxin Below are screen shot of Asynchronous Actions inside actions and screen shot of index of programming guide.

Mostly this just duplicates the non-async documentation. I think it's worth mentioning the existence of the async methods with a pointer to the API docs, but, I don't think this table adds value.

@srowen yeah you are right its not blocking calling thread but they execute sequentially right but in async action its return future so its running on different threads soo not run sequentially soo its fully non blocking example if i have action in that we have some transformation like map n inside map i have blocking code then how its work its block or not?

@srowen yeah i agree with you its same like non async actions but yeah we should list it because its more useful in real life application when single application running multiple jobs of different users. so we should list it so user will more familiar with it and also know which are the async actions. i think its helpful for users still if you think its not a valid point then just tell me i change pull request and add just reference for async actions but i want user should know because when i first time see it i m surprise that in whole documentation no where mention about async actions.

I fixed my comment above, sorry. They do block the calling thread, but actions triggered in different threads on one RDD do not block each other. The first sentence isn't correct. My suggestion is to omit the table, not all of the text you added.

@srowen ok no problem so what you suggest should i remove the table and just add the line below the actions table and give link to scala and java docs? And the line "Spark provide asynchronous actions to execute two or more actions concurrently, these actions are execute asynchronously without blocking each other." is not correct so should i add that to "return future to non-block calling thread?" even in above statement my intention is also talk about calling thread because when we call action it will always in calling thread so calling thread will block but when we use async actions it will not block so we are targeted here non-blocking for calling thread because actions are called in calling thread. so i make changes and push it again as u suggest just add single line at end of actions and give link for scala and java doc api. Its cool?

@srowen i make changes as you suggest i remove the table and add a single below actions table and also change statement to be more clear about non blocking.

@srowen @rxin Please review it and give your comments.

@srowen i know its nothing major just call normal functions in future but still naive user first time who learn scala and spark dont know what are future and all so at least we should add reference of it. if you suggest i simple add reference link without adding any statement of blocking and non blocking. so atleast user know there is some api like this.

Although I don't think it's essential to mention this API (it's in the API doc) it wouldn't hurt to point to it here. The mention should be accurate though. I think it's correct to say that the Spark RDD API also exposes asynchronous versions of some actions like foreach, which return a handle immediately to the caller which can be used to wait for its completion.

@srowen sure i will make appropriate changes and push it again

@srowen now its perfect i think at last from table to one line but yeah you are right it good to just mention that spark provide it and not duplicate table of actions.

@srowen @rxin

@srowen Thanks man i know i am not giving correct language but my intention is also same i hope its final commit :) if its done can you merge it.

@srowen I put back-tick-quote for foreach, foreachAsync and FutureAction.

@srowen Below is final screen shot as you suggested i hope its looks good please review it and merge it.

@srowen Is this is correct if it is then please merge it otherwise give comment if needed.

@phalodi no need to ping. We don't merge things immediately, especially when non-essential. It gives more time for review.

Jenkins retest this please

Test build #62231 has started for PR 14104 at commit 845a123.

Test build #62231 has finished for PR 14104 at commit 845a123.

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

Merged build finished. Test PASSed.

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


Compile the ADSBX feeder client using READSB

Compile the ADSBX feeder using READSB
git clone --depth 1 https://github.com/Mictronics/readsb.git
cd readsb
make RTLSDR=yes
/usr/bin/readsb --net --net-only --quiet
--net-beast-reduce-interval 1
--net-connector feed.adsbexchange.com,30005,beast_reduce_out
--net-connector localhost,30005,beast_in
--net-ro-interval 0.5 --net-ri-port 0 --net-ro-port 0
--net-sbs-port 0 --net-bi-port 0 --net-bo-port 0

https://github.com/adsbxchange/adsb-exchange
I hacked above into out feeder installer.  Hopefully I didn't break anything too badly.
Based on @wiedehopf work here:
https://github.com/wiedehopf/lowBandwidthFeedAdsbX
One of the things to consider adding is this:
https://github.com/adsbxchange/adsbexchange-stats
Step 2 is the setup.
It allows to the individual feeder map and eventually a "stats" dashboard to fulfill the deepest desires of the masses.
The problem is it directly reads the aircraft.json from dump1090 et all forks
JSON_PATHS=( "/run/readsb" "/run/dump1090-mutability" "/run/dump1090-fa" )
https://www.adsbexchange.com/api/feeders/?feed=v9FBlUbrsPtzcExw4o1oHuPamuv8SW452njzmw7ejaVRAYZEFF2jjFTAF35H4eiq&t=
https://www.adsbexchange.com/api/feeders/tar1090/?feed=v9FBlUbrsPtzcExw4o1oHuPamuv8SW452njzmw7ejaVRAYZEFF2jjFTAF35H4eiq&t=
I'm sure it will gain traction and other contributors if you care to join ADSBx discord.
https://discord.gg/DReE2Da
Cheers!

Thanks so much for the suggestions. I've updated the container (version 20200212) implementing both of the above suggestions (readsb and adsbexchange-stats).
I've also joined the ADSBx discord and look forward to talking with you.


[Executor] Debug Graph Executor - Dumping output tensors include topographical ordering

The previous dumping of output tensors from the debug graph executor only used the name of the operation as the key in a dictionary.
This does not work because op-names are in fact not unique! We get around this by including a topological index into the key which should be consistent with a fixed graph.json

cc @tkonolige


chore: update exports

Checklist

[x] npm test passes
[ ] benchmarks are included
[ ] commit message follows commit guidelines
[ ] documents are updated

Description of change

想使用未导出的方法


does wamr support async programing?

If it does, I appreciate your examples, thanks much~

Hi, WAMR supports multi-thread and pthread library, including pthread_cond_wait, pthread_cond_timedwait, pthread_cond_signal and others, you can refer to the document and sample, not sure whether it meets your requirements?


⚠ Bofrost.at has degraded performance

In 6b23a8e, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2167 ms

Resolved: Bofrost.at performance has improved in c36da8e after 14 minutes.


How to predict relations in a new sentence using trained model

I'm trying to use the finetuned model to predict relations in a new sentence, but I cannot find the instructions. Following the OpenNRE, I have tried to add the following code:
 _framework.model.infer({"token": ["he", "has", "combined", "intelligent", "history", "with", "moving", "prose", ",", "creating", "an", "informative", ",", "inspiring", "narrative", "telling", "the", "history", "of", "a", "great", "people", "."], "h": {"pos": [14, 15]}, "t": {"pos": [17, 18]}})
But the program raised an error:

Traceback (most recent call last):
File "E:/Project/REDN-master/redn_trainer.py", line 195, in
train(**args_list[0])
File "E:/Project/REDN-master/redn_trainer.py", line 143, in train
_framework.model.infer({"token": ["he", "has", "combined", "intelligent", "history", "with", "moving", "prose", ",", "creating", "an", "informative", ",", "inspiring", "narrative", "telling", "the", "history", "of", "a", "great", "people", "."], "h": {"pos": [14, 15]}, "t": {"pos": [17, 18]}})
File "E:\Project\REDN-master\opennre\model\para.py", line 46, in infer
logits = self.forward(*item)
TypeError: forward() takes 3 positional arguments but 4 were given

Then I found the 45 line of "REDN-master\opennre\model\para.py" called the self.sentence_encoder.tokenize method and return indexed_tokens, att_mask, new_index, but the self.forward seems to need tokens, att_mask only, so I changed the line 46 to  logits = self.forward(item[0], item[1]), the program still raise the error:

Traceback (most recent call last):
File "E:/Project/REDN-master/redn_trainer.py", line 195, in
train(**args_list[0])
File "E:/Project/REDN-master/redn_trainer.py", line 143, in train
_framework.model.infer({"token": ["he", "has", "combined", "intelligent", "history", "with", "moving", "prose", ",", "creating", "an", "informative", ",", "inspiring", "narrative", "telling", "the", "history", "of", "a", "great", "people", "."], "h": {"pos": [14, 15]}, "t": {"pos": [17, 18]}})
File "E:\Project\REDN-master\opennre\model\para.py", line 48, in infer
logits = self.softmax(logits)
File "C:\Users\HUI\Anaconda3\lib\site-packages\torch\nn\modules\module.py", line 550, in call
result = self.forward(*input, **kwargs)
File "C:\Users\HUI\Anaconda3\lib\site-packages\torch\nn\modules\activation.py", line 1044, in forward
return F.softmax(input, self.dim, _stacklevel=5)
File "C:\Users\HUI\Anaconda3\lib\site-packages\torch\nn\functional.py", line 1442, in softmax
ret = input.softmax(dim)
AttributeError: 'tuple' object has no attribute 'softmax'

I am very grateful if anyone can help me to fix this.
Moreover, I use the  _framework.model.infer instead of  _framework.parallel_model.infer, but the original code train the model using _framework.parallel_model.load_state_dict, as _framework.parallel_model.infer is not implemented. Is that right?

Sorry about the code is not so clean. The infer function you mentioned is a very old version and may not work. This version of the code actually do not has an available infer function. You need write this part of code yourself till now. However, we will soon release a new version with infer function and more friendly code framework.

Thank you for your reply. I found that rewriting eval_model function in sentence.py is much more easier. Looking forward to the new version. Great work!


adds support for dns in stack files

- What I did
Added support for dns config flags in stack files. (only nameservers and search domain)
version: '3'

services:
  busybox:
    image: busybox:latest
    dns:
      - <IP_ADDRESS>

- How I did it
docker service create --dns x.x.x.x ... is supported right now but stack files do not support it.
I just simply hooked the ServiceConfig with the ContainerSpec used in ServiceSpec
- How to verify it

docker swarm init

stack deploy behaviour before this PR

$ docker stack deploy -c docker-compose.yml test
Ignoring unsupported options: dns

Creating network testing_default
Creating service testing_busybox

stack inspect

$ docker service inspect testing_busybox
[
    {
        "ID": "lp97yfpg5mnljpaqn67eu8sys",
        "Version": {
            "Index": 1311
        },
        "CreatedAt": "2017-03-23T23:56:10.907936203Z",
        "UpdatedAt": "2017-03-23T23:56:10.921987465Z",
        "Spec": {
            "Name": "testing_busybox",
            "Labels": {
                "com.docker.stack.namespace": "testing"
            },
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "busybox:latest@sha256:32f093055929dbc23dec4d03e09dfe971f5973a9ca5cf059cbfb644c206aa83f",
                    "Labels": {
                        "com.docker.stack.namespace": "testing"
                    }
                },
                "Resources": {},
                "Placement": {},
                "ForceUpdate": 0
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "Networks": [
                {
                    "Target": "nlz98omhfr3he54gbej4k5ae6",
                    "Aliases": [
                        "busybox"
                    ]
                }
            ],
            "EndpointSpec": {
                "Mode": "vip"
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip"
            },
            "VirtualIPs": [
                {
                    "NetworkID": "nlz98omhfr3he54gbej4k5ae6",
                    "Addr": "<IP_ADDRESS>/24"
                }
            ]
        }
    }
]

stack deploy behaviour with this PR

$ docker stack deploy -c docker-compose-test.yml testing
Creating network testing_default
Creating service testing_busybox

stack inspect

Notice the DNSConfig is passed in correctly.
$ docker service inspect testing_busybox
[
    {
        "ID": "93mp786llsintm6i8ua6eix0w",
        "Version": {
            "Index": 1087
        },
        "CreatedAt": "2017-03-23T23:52:36.844634115Z",
        "UpdatedAt": "2017-03-23T23:52:36.866488582Z",
        "Spec": {
            "Name": "testing_busybox",
            "Labels": {
                "com.docker.stack.namespace": "testing"
            },
            "TaskTemplate": {
                "ContainerSpec": {
                    "Image": "busybox:latest@sha256:32f093055929dbc23dec4d03e09dfe971f5973a9ca5cf059cbfb644c206aa83f",
                    "Labels": {
                        "com.docker.stack.namespace": "testing"
                    },
                    #
                    # DNSConfig are created correctly
                    #
                    "DNSConfig": {
                        "Nameservers": [
                            "<IP_ADDRESS>"
                        ]
                    }
                    #
                    #
                },
                "Resources": {},
                "Placement": {},
                "ForceUpdate": 0
            },
            "Mode": {
                "Replicated": {
                    "Replicas": 1
                }
            },
            "Networks": [
                {
                    "Target": "sogye9h8zmoy23edfg1wncvii",
                    "Aliases": [
                        "busybox"
                    ]
                }
            ],
            "EndpointSpec": {
                "Mode": "vip"
            }
        },
        "Endpoint": {
            "Spec": {
                "Mode": "vip"
            },
            "VirtualIPs": [
                {
                    "NetworkID": "sogye9h8zmoy23edfg1wncvii",
                    "Addr": "<IP_ADDRESS>/24"
                }
            ]
        }
    }
]

- Description for the changelog
add support for dns nameservers and search domains in stack files
- A picture of a cute animal (not mandatory but encouraged)

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "support-dns-stack-file" git@github.com:seriousben/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Cool. I will go forward with a test and also not sending an empty DNSConfig if no dns options are passed in.

Design LGTM

You'll need to update the jsonschema in cli/compose/schema/data (just the latest one), and add to cli/compose/loader/full-example.yml to verify the change

I will add a test for the conversion and will ping you when done.

@dnephin Just added some tests. I believe this PR is ready to go.


ShowSuccess(ShowError) change background color

1.Please check all of the platforms you are having the issue on

iOS

Version of ACR UserDialogs Library 6.38

2. Expected Behaviour
I want to change the background color when I show success or error message use the ShowSuccess or ShowError method
And now ShowSuccess and ShowError method just show the message with the white background color and not Success and Error Image

These methods are being deprecated in the next version.  I would suggest using a toast instead


Incorrect (too precise!) conversion of charge units from kCal to e-

Description
Very, very occasionally, a neutral molecule can end up with a slight, i.e. non-zero charge when converted form an Amber .prmtop file to a Gromacs .top file. (I doubt this would affect many people but you never know!)
Details
I routinely use acpype as a Python script to convert GAFF topologies (generated using antechamber and tleap) in .prmtop format to .top format suitable for use with Gromacs. Very, very occasionally, a neutral molecule can lead to a system with a slight charge: if this is > 0.001 e, then Gromacs complains about it.
I eventually tracked this down to the conversion between the charge units used by Amber (something in terms of kCal) and e, as used by Gromacs...
Digging into the source of tleap, the conversion factor used (ELECTRONTOKCAL in initio.c) is 18.2223; in acpype.py, the value used (qConv) is 18.222281775. This value comes from a combination of various fundamental constants and, usually, the more precision the better, but this difference in precision can occasionally lead to a subtle change in atomic charges.
In most cases, the difference is negligible: in the system where this became an issue, one atom changed by one digit in the 6th decimal place. However, for a condensed phase simulation comprising many hundred of these molecules, the overall charge added up to over 0.001 e and it was flagged by Gromacs.
Modifying acpype.py to set qConv to be (exactly) 18.2223 solved the problem and the individual molecule, and the large, condensed system, had the expected zero charge.

Please use the official Acpype here https://github.com/alanwilter/acpype and report issues there. Thanks, Alan

@alanwilter great that you have an official github repo.  I own acpype at pipy, I can transfer you the ownership.
I created this report several years ago and I was not able to find your repo.

Updated readme and project description to point to official repo.
I will archive this repo also


showpath: fix panic and use default sciond socket

Panic was caused by doing Flush before setting the log.
We do not really need the log facicility for this app, so remove it.
Also use a default sciond path socket to connect in case neither sciond
nor srcIA flags set.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

go/tools/showpaths/paths.go, line 79 at r1 (raw file):

		}
	} else if *srcIAStr != "" {
		fmt.Fprintf(os.Stdout, "srcIA ignored! sciond takes precedence\n")

You can just use fmt.Printf here

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, 1 unresolved discussion.

go/tools/showpaths/paths.go, line 79 at r1 (raw file):
Previously, shitz wrote…
You can just use fmt.Printf here

Done.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


The "model" option does not exist when using php artisan make:filament-auto-relation-manager

Hi there!
I would like to give this package a try but after composer install when I run php artisan make:filament-auto-relation-manager for any model I get the following error:
php artisan make:filament-auto-resource
My Filament panel structure looks like this:

My models are located in the default location of /App/Model.
Laravel 11, latest version of Filament. Any idea what could be going on?

Hello @BoweFrankema. The Filament Auto Panel relies on filament internal APIs, and the filament keeps changing it even in minor updates.
This is probably the case here. I will check what is happening and release a fix asap.

Should now be fixed by 2.0.1.

Thank you, I'll give it a try later this week!


what's the difference between model and regression_model ?

pre-trained model for human hg38  you provided : https://drive.google.com/drive/folders/1KpT6Ajm5qqsGm_G-HMdwKBtmrDcDsi0E
pre-trained regression_model for human hg38  you provided :  https://drive.google.com/drive/folders/1KkI4cc04hSb-foVjNcS253kRyj8EYaLL
Which file is for --model ?
Previously, I used model, but not regression_model, for my human datasets.

Sorry for the late reply. The model is used to predict PAS, while the regression_model is used to quantify the expression of the provided PAS. Hope this answer could be helpful

Thanks.

you are welcome


Add additional fields and states in the protocol

There is a need to add new fields e.g.:  actualTakeOffTime and actualLandingTime
and additional fields for the state of the declaration:
two boolean state variables: approved and completed. A flight plan is expected to transition from proposed (approved = false, completed = false) to active (approved = true, completed = false) to completed (approved = true, completed = true) over the course of its lifecycle.

Added additional states


Request for Version Number in the Gui

Hi David, please is it possible to include in the Menu File, About the version number of the installed fluxengine.exe?
Thank you
Michael

The binary doesn't have a version number! It might be possible to include the build date, though.

Hi David,
nice to hear from you. The integration of the build date would be great.
Thank you
Michael


Why there is no a ChangeLog in the project?

Because Oh My Zsh doesn't have versioned releases that would justify having a changelog. And there are no versioned releases because it hasn't matured into having them. Hopefully in the future though.


Storybook Theme Improvements

Adds SEB fonts to menus etc
Use monochrome icons in menu
Use light toolbars in light mode, dark toolbars in dark mode
Less use of various colors in the Storybook shell

Lol, not sure what I branched of, but there's a ton of other commits here. Will open a new PR.


(ALPHA) V2: Saved Native Wallet Age Displaying incorrectly

https://discord.com/channels/554694662431178782/873244924026449940/922562336911392778
In Web v2, when you go to the saved wallets, if you have a saved native wallet address, it will show up being very old. 52 years in this case.
I was able to remove and re-add the native wallet and it's showing up correctly for now. I am keeping an eye on this to see if it speeds up in time vs how long it's actually been added.

I confirm I was able to see this behavior with old saved wallets but not with new ones.
I checked, and the PR that introduced the created date is https://github.com/shapeshift/web/pull/499.
I agree with @reidrankin that every wallet that already existed before the merge of this PR indicates ~52 years old. It should not appear with wallets created after that.

this only affects people prior to the fix, won't fix this


Broken or Flaky test: ShellServerIT.testFateSummaryCommandWithSlowCompaction

Test name(s)
[ERROR] org.apache.accumulo.test.shell.ShellServerIT.testFateSummaryCommandWithSlowCompaction  Time elapsed: 4.365 s  <<< FAILURE!
org.opentest4j.AssertionFailedError:
reportTime present in root@miniInstance ns1.ShellServerIT_testFateSummaryCommandWithSlowCompaction0> fate -summary -np json -t NEW IN_PROGRESS FAILED
was not true ==> expected:  but was:

I haven't looked at the test but my guess is it should probably be removed. Unless you or Ed want to move it to another IT to test the new summary command in Admin. We have the unit test AdminTest but it will probably be a PITA to mock everything in a unit test.

I'll look at moving it.

Is there a similar test / potential problem with moving the cancel command?

I didn't see one. I'm working on a new test now.


Update MD file on new branch 2017-12-02_03-31-43

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/content1.md
:white_check_mark:Succeeded

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.


openAIChat.streamTokens() doesn't stream the tokens when the response is a function_call (tool_call)

A chunk from when getting a tool response looks like this:
      {
        id: 'chatcmpl-8LOwr2AcOfQU0zPGdCKkyYIlnz30B',
        object: 'chat.completion.chunk',
        created:<PHONE_NUMBER>,
        model: 'gpt-4-1106-preview',
        system_fingerprint: 'fp_a24b4d720c',
        choices: [
          {
            index: 0,
            delta: {
              tool_calls: [ { index: 1, function: { arguments: ', Jap' } } ]
            },
            finish_reason: null
          }
        ]
      }

Our library doesn't expect the delta to be tool_calls, so returns an empty string.
here's another chunk, with the function name:
      {
        id: 'chatcmpl-8LOwr2AcOfQU0zPGdCKkyYIlnz30B',
        object: 'chat.completion.chunk',
        created:<PHONE_NUMBER>,
        model: 'gpt-4-1106-preview',
        system_fingerprint: 'fp_a24b4d720c',
        choices: [
          {
            index: 0,
            delta: {
              tool_calls: [
                {
                  index: 2,
                  id: 'call_ucviJGsYAwobgBAMamh5mGb3',
                  type: 'function',
                  function: { name: 'get_current_weather', arguments: '' }
                }
              ]
            },
            finish_reason: null
          }
        ]
      }

Types were fixed in https://github.com/axflow/axflow/pull/101, but we might need to do more to support tools in the accessors

Yes, I would expect this to be the case, though I agree it's not well documented and therefore confusing.
stream streams the response as is from the underlying provider. streamTokens was meant to be a high-level wrapper that plucks out the message content. You could argue functions/tools are message content, but this considers message content to be the user-facing text output, not other objects in the response. Of the models supported in this library, only openai supports tools/functions. If you want to use those, stream is the appropriate method.


Membership maintainance check

Hi all,
One year has almost passed since the creation of this council and I wanted to trigger a membership maintainance check.

Every six months, one currently active member should open an issue in the team-compass repo asking all currently active team members to reply if they still consider themselves active. If not (or no response is given by a team member), it will be assumed that they have gone inactive. This will help keep the active member list up-to-date.
Remember, an inactive member can return at any time by simply changing their status on the team-compass page.

Please indicate below one way or the other if you would like to remain as an active member of this council, or if you prefer to become inactive at this time.
This poll will remain open until the first week of January, 2024, at which point we will assume an inactive role for anyone not participating.

@Carreau wishes to ...

[x] remain active
[ ] become inactive

@ccordoba12 wishes to ...

[x] remain active
[ ] become inactive

@SylvainCorlay wishes to ...

[x] remain active
[ ] become inactive

@afshin wishes to ...

[ ] remain active
[ ] become inactive

@jasongrout wishes to ...

[x] remain active
[ ] become inactive

@ivanov wishes to ...

[x] remain active
[ ] become inactive

@JohanMabille wishes to ...

[x] remain active
[ ] become inactive

@fperez wishes to ...

[ ] remain active
[ ] become inactive

@minrk wishes to ...

[x] remain active
[ ] become inactive

@blink1073 wishes to ...

[x] remain active
[ ] become inactive

@willingc wishes to ...

[x] remain active
[ ] become inactive

@Zsailer wishes to ...

[x] remain active
[ ] become inactive

@kevin-bates wishes to ...

[x] remain active
[ ] become inactive

I'd like to remain active, but I don't have access to edit the top comment.

Hi @JohanMabille - Thanks for handling this! I too would like to remain active but can't edit.

@Zsailer and @kevin-bates I've checked the box for both of you, and also added the @jupyter/kernels-council to be an admin of this repo, so you should be able to edit yourselves from now on.

Oh, and I now see that neither of you were on that @jupyter/kernels-council  list, so that's also now been corrected.

I'd like to remain (or become) active, but I cannot see myself in the list. How can I join?

Oh, and I now see that neither of you were on that @jupyter/kernels-council list, so that's also now been corrected.

I'd like to remain (or become) active, but I cannot see myself in the list. How can I join?

I'm sending you the invites (both on Github and the google mailing list)

@ivanov can you invite David to the KernelCouncil list, or make me an admin of the team so that I can send invites?

@davidbrochart wrote:

I'd like to remain (or become) active, but I cannot see myself in the list. How can I join?

Thanks for your interest, David, here's the relevant portion of the kernels team compass page about becoming a council member, you already have Johan as your champion so we will start that process internally.
@JohanMabille wrote:

I'm sending you the invites (both on Github and the google mailing list
@ivanov can you invite David to the KernelCouncil list, or make me an admin of the team so that I can send invites?

You should be able to manage that list now. However, I think we should follow the Nominating a new member process outlined on the team compass for adding new members. To that end, I will remove David from the membership check and the mailing list for the time being, until we  add him using the official process. (David, I look forward to having you join the kernels council, so please do not misinterpret my actions as opposition to your participation here).

There is also a second kernel council team which should probably be deleted.

Ah yes,  I suspect it was the concil -> council typo that made that one fly under the radar, I have edited its description so we do not use it. But from there I figured out that there were additional repositories that the council should have administration over (jupyter_console and kernels) so I added those.

Fixed in #8

Sorry for the late reply, just catching up with backlog. But that's a signal I should go inactive, as realistically I can't keep up.


Update: Mozilla.Firefox.DeveloperEdition.lij version 133.0 (133.0b2)

Created by 🥟 Dumplings in workflow run #9186.

Log
Updated: 133.0b1 → 133.0b2
Submitting WinGet manifests
Found existing pull requests:
New version: Mozilla.Firefox.DeveloperEdition.lij version 133.0 (133.0b1) - https://github.com/microsoft/winget-pkgs/pull/186642
The existing pull requests are ignored as the version is updated while the real version isn't
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

@wingetbot run


[Question] BotBuilder SDK v4 Roadmap?

Some issues such as #3639 (limitations of the current i18n implementation) or #3674 (Waterfall default behaviour) have been closed because there is a SDK v4 in the works that is expected to solve them or provide the means to do it.
v4 has been said to be "a complete re-write" of the SDK and "much more modularized", but beyond that there is not much information about it.
It would great if you could share info about the Roadmap or development status of v4.
We are delighted, but a little bit scared about this complete re-write of the SDK.
In the current situation, many doubts arise:

Will v4 be backward compatible with v3? Will bots developed for v3 seamlessly work with v4 or they will need a significant rewrite?
What is the expected design (architecture and modules) of v4?
Which new features will it bring?

Without more info about it, we don't know if investing into using v3 and adapting it to our needs is a good idea. If we do not know how v4 will be, it is hard to prioritize what we should focus our time on, as our adaptations may be already implemented in the upcoming version or (on the other side) may require a complete rewrite in v4.
Both the community and the Bot Framework team could benefit from a public Roadmap of v4 in order to provide feedback about the future version and be prepared for it.
Maybe the Roadmap could be shown in a Github issue or have an alpha branch in the repo with v4 so we can stay tuned on its progress. Any kind of information would be highly welcome.

It would be great if someone from the core team could address this request, regardless if this is doable or not.
I personally would be happy if there is even just an overview of what is coming in the next release and, specifically, backward compatibility with v3. This is critical information for users who are just starting to build their bot services with v3 and need to think ahead of upcoming breaking changes(if any) or new features that would potentially deem unnecessary hacking the existing implementation to do something that would be in the core implementation with the next release.
And last but not least, just taking the opportunity to thank the whole team for open sourcing this wonderful framework for building bots 👏👏👏

We will respond to this thread as soon as we can make information publically available.

Looking forward to an update on this topic. Have been waiting for the .net core 2 BotBuilder for a while.

You may have a look there for news about the v4: https://github.com/Microsoft/botbuilder-js/wiki

Closing this, as there is now a public roadmap (thanks for providing the links @nrobert )


Adding Dark mode

Would be great to have dark mode that would invert the colours of the font & the background so it's easier on the eyes.
This is something that's also present in firefox reader

This is actually pretty important for me as my firefox theme has a dark background and I can't read the markdown render (as the text is black).
Please fix this!


Controller Upgrade procedure needs to be improved

The eksctl command to setup IRSA is missing the --role-name argument. It is not a bug but it makes the tool create a IAM role with a random name.
The manifest to deploy CRDs and the Gateway Controller has a ServiceAccount definition for gateway-api-controller though we are creating the latter using eksctl. Again, this is not an issue until it is. If you unveil a new version, say, deploy-v0.0.2.yaml, and a user deletes the old manifest with kubectl delete -f and then does a kubectl apply -f with the new manifest, user will end up with a ServiceAccount definition without the IRSA annotation and it will break things.

we to investigate how to deal with ServiceAccount


spring-ldap

https://docs.spring.io/spring-ldap/docs/current/reference/

https://www.javaworld.com/article/2077729/open-source-tools/simplify-directory-access-with-spring-ldap.html

https://spring.io/blog/2014/03/26/webinar-replay-spring-ldap-2-0-0


Add case sensitivity support for Oracle

Issue #9457
but only fix mysql part

Thank you for your contribution.
Could you add a unit-test for this change and try to do the same for other DBMSs, please?

Closing since it cannot be merged in this state.


user12986714: Watch \A.{20,}(?:on|for)\W*+roku

user12986714 requests the watch of the watch_keyword \A.{20,}(?:on|for)\W*+roku. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

\A.{20,}(?:on|for)\W*+roku has been seen in 23 true positives, 0 false positives, and 0 NAAs.

Rejected by Daniil in Charcoal HQ. Reason: 'This was decided as not effecient and it has too many fp's.'


Provide configurable set of white listed bundles

An OSGi configuration should be able to be used to specify a list of bundle symbolic names. Bundles part of this white list should be ignored for the purposes of the health check.
This feature is required because some bundles (i.e. webdav) are intentionally disabled for security purposes.

This feature has been implemented in version 1.3.3
https://github.com/shinesolutions/aem-healthcheck/releases/tag/v1.3.3


feat: use verified/turbo flags on SX spaces

Summary
To be merged once APIs are ready and synced.
Closes: https://github.com/snapshot-labs/workflow/issues/215
How to test

Go to http://localhost:8080/#/sn:0x009fedaf0d7a480d21a27683b0965c0f8ded35b3f1cac39827a25a06a8a682a4
Go to http://localhost:8080/#/sn-sep:0x0141464688e48ae5b7c83045edb10ecc242ce0e1ad4ff44aca3402f7f47c1ab9
Those spaces are verified.

Looks good, can we also make SX verified spaces appear first on the explore page?


fix typo

i guess this is a typo ? /cc @akx

Thanks

Whoops, sorry about that... Cheers @revolunet :)


[Wallet-Kit] Bug when using Next.js 13, getServerSnapshot error

When I use wallet-kit and next.js 13 together. The error occurs. Missing getServerSnapshot, which is required for server-rendered content. Will revert to client rendering.

First, make sure you have the latest version of the software installed. You can check this by typing "npm install -g sui" in your command line.

If you still encounter the same error, try clearing your cache by typing "npm cache clean".

If the problem persists, try uninstalling and reinstalling the software by typing "npm uninstall -g sui" followed by "npm install -g sui".

If none of these steps work, you may need to examine your source code to look for any potential errors in your code. Alternatively, you can reach out to the MystenLabs support team for further assistance.

I hope these steps help you resolve the issue you are facing. Good luck!

Hey, I have this issue also. I've tried all the above steps and it doesn't seem to resolve the bug.

This has been resolved on main and will be released soon.

Sorry to reopen this but is this already released? I see a recent release on npm very recently (0.3.3) but I still have this error. My _app.jsx was set up like this, And then Error: Missing getServerSnapshot, which is required for server-rendered content. Will revert to client rendering.
export default function App({ Component, pageProps }) {
  return (
    <>
      <main>
        <div>
          <WalletKitProvider>
            <Component {...pageProps} />
          </WalletKitProvider>
        </div>
      </main>
    </>
  )
}

Hasn't been released yet, but it should be released soon!


[FLINK-7375] Replace ActorGateway with JobManagerGateway in JobClient

What is the purpose of the change
In order to make the JobClient code independent of Akka, this PR replaces the
ActorGateway parameters by JobManagerGateway. AkkaJobManagerGateway is the
respective implementation of the JobManagerGateway for Akka. Moreover, this
PR introduces useful ExceptionUtils method for handling of Future exceptions.
Additionally, the SerializedThrowable has been moved to flink-core.
This PR is based on #4483.
Brief change log

Replace ActorGateway by JobManagerGateway in JobClient
AkkaJobManagerGateway is the Akka based implementation of JobManagerGateway
ExceptionUtils contain new functions to handle future exceptions
SerializedThrowable has been moved to flink-core

Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)

Rebased onto the latest master.

Travis passed. Merging this PR.


create GUI to enable richard weinberg to post data

maybe @j6k4m8 will do this at some point

@j6k4m8 this is you, right?

Work-in-progress!
On Thu, Aug 27, 2015 at 7:03 PM joshua vogelstein<EMAIL_ADDRESS>wrote:

@j6k4m8 https://github.com/j6k4m8 this is you, right?
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/open-connectome/issues/82#issuecomment-135578711
.


can't assign a tuple to a torch.cuda.FloatTensor

Hi,
I get this error 'can't assign a tuple to a torch.cuda.FloatTensor' when I run train.py, and pooling = patchnetvlad in train.ini.
The place where the error occurred is:
vlad_encoding = net.pool(image_encoding)
pvecs[i * bs:(i + 1) * bs, :] = vlad_encoding
and
vlad_encoding：
([tensor([[[ 0.0000e+00,  0.0000e+00,  0.0000e+00,  ...,
But when pooling = netvlad in train.ini
vlad_encoding：
tensor([[[-5.1483e-03, -2.0104e-02,  0.0000e+00,  ...,
The above error will not appear

Hi, please refer to https://github.com/QVPR/Patch-NetVLAD/issues/27
In short, training with patchnetvlad pooling doesn't work - instead train with netvlad pooling and then apply patchnetvlad pooling at inference time.


Handling metrics calls for the current Project in Dependency Track 3.4

The 3.4 API to get all projects doesn't include the metrics Data like in 3.5.
Make the Score Mojo get the metrics when they are not returned.

 When Metrics are null, make an API call to get them


[Bug]: checkConnectivity always returns none on Linux installed on windows with VM (Oracle Virtual Box)

Platform
Linux
Plugin
connectivity_plus
Version
3.0.3
Flutter SDK
3.3.10
Steps to reproduce
1: Install Linux Ubuntu 22 on Windows with Oracle VM VirtualBox
2: Execute a flutter project using connectivity_plus plugin
The following code works with Linux (native), ios, macos, android, windows but doesn't work when Linux is on VM.
NB: Linux on VM can connect to internet with broswer or VS code, etc...
Code Sample
import 'dart:async';

import 'package:connectivity_plus/connectivity_plus.dart';
import 'package:flutter_riverpod/flutter_riverpod.dart';

enum ConnectivityStatus { isConnected, isDisconnected }

class ConnectivityStatusNotifier extends StateNotifier<ConnectivityStatus> {
  ConnectivityStatusNotifier() : super(ConnectivityStatus.isDisconnected) {
    Connectivity().onConnectivityChanged.listen(
      (ConnectivityResult result) {
        final newState = result.toConnectivityStatus;
        if (newState != state) {
          state = newState;
        }
      },
    );
  }
  StreamController<ConnectivityResult> controller =
      StreamController<ConnectivityResult>();
}

extension _ConnectivityResultExt on ConnectivityResult {
  ConnectivityStatus get toConnectivityStatus {
    switch (this) {
      case ConnectivityResult.mobile:
      case ConnectivityResult.wifi:
      case ConnectivityResult.ethernet:
      case ConnectivityResult.bluetooth:
      case ConnectivityResult.vpn:
      case ConnectivityResult.other:

        return ConnectivityStatus.isConnected;
      case ConnectivityResult.none:
        return ConnectivityStatus.isDisconnected;
    }
  }
}

final connectivityStatusProviders =
    StateNotifierProvider<ConnectivityStatusNotifier, ConnectivityStatus>(
  (ref) => ConnectivityStatusNotifier(),
  name: 'connectivityStatusProvider',
);

Logs
No exception

Flutter Doctor
[✓] Flutter (Channel stable, 3.3.10, on Ubuntu 22.04.1 LTS 5.15.0-58-generic, locale fr_FR.UTF-8)
    • Flutter version 3.3.10 on channel stable at /home/reddwarf/Documents/flutterdev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 135454af32 (8 weeks ago), 2022-12-15 07:36:55 -0800
    • Engine revision 3316dd8728
    • Dart version 2.18.6
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /home/reddwarf/Android/Sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /home/reddwarf/Documents/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 14.0.0-1ubuntu1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2

[✓] Android Studio (version 2021.3)
    • Android Studio at /snap/android-studio/125/android-studio
    • Flutter plugin version 71.2.3
    • Dart plugin version 213.7433
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] Android Studio
    • Android Studio at /home/reddwarf/Documents/android-studio/
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /home/reddwarf/Documents/android-studio/
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code
    • VS Code at /snap/code/current
    • Flutter extension version 3.58.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 22.04.1 LTS 5.15.0-58-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Checklist before submitting a bug

[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I'm using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

Hello. Someone works on triage in this repo ? 🙏. Thx


schedule update should start from previous action instead of current time

Actual Behavior
Suppose you have a 5-minute schedule with 1 minute jitter. The next nominal time is 12:20:00, but with jitter it's 12:20:33. Now at 12:20:10 you do an update to the exact same spec. It throws out the previous times and calculates the next times from there. The next nominal time is 12:25:00 now (we're past 12:20:00) and then adds jitter to that. So the run at 12:20:33 is lost.
Expected Behavior
If there is a matching time including jitter after the update time, it should still run, even if its nominal time was before the update time.
Possible Fix
For interval specs, it could just look back one interval, but with calendar specs we can't (easily) look backwards. One idea is to start from the previous action time and start calculating forwards, discarding any times where the actual time (including jitter) is in the past (of the update time). Or better, start from max(create time, last update time, previous action time). We use that same construction as the "retention base" for idle schedules so that makes some sense.

Thanks for reporting this issue. The problem you're encountering is related to the way Temporal handles schedule updates and jitter. Here is a potential solution based on the attached documentation:

Suggested Solution:
You could consider using a different approach, like using the "Start Delay" feature (https://docs.temporal.io/develop/java/schedules#start-delay) instead of relying on the schedule's jitter behavior. This would allow you to schedule the workflow for a specific future point in time, avoiding the issue of lost runs due to updates.

Explanation:
The "Start Delay" feature allows you to schedule a Workflow Execution at a specific one-time future point, preventing the need for the system to continuously recalculate the schedule's time range, thereby avoiding the issue of lost runs due to updates. This approach ensures that your workflow runs as intended without being affected by schedule updates.

Thanks for reporting this issue.
This seems to be a known issue. As you pointed out, the current implementation doesn't properly handle jitter when updating a schedule.
We are aware of this issue and working on a fix, you can track the progress here:  [link to relevant issue tracker].
In the meantime, you can work around this issue by:

Using a smaller jitter value: This will reduce the chances of a run being missed due to the jitter.
Increasing the schedule interval:  If you have a 5-minute interval with 1-minute jitter, you could consider increasing the interval to 6 minutes. This will give you more time before the next run is scheduled, reducing the chances of the jitter causing a run to be missed.
Manually triggering the workflow: If a run is missed due to the jitter, you can manually trigger the workflow to ensure it runs.

Let us know if you have any further questions.

Thank you for reporting this issue. It seems like the issue you're experiencing is related to how Temporal handles schedule updates when there's a jitter in the execution time.
I've reviewed the documentation you've provided, but I need a bit more context to provide a specific solution.
Could you please clarify:

What is the specific Schedule Spec you are using? (e.g., interval, calendar, cron)
How is the jitter being introduced? (e.g., network latency, system load)
Are you using a Retry Policy for the Activity?

Providing these details will help me understand the issue better and suggest a more appropriate solution or workaround.


🌱 feat: Prioritize Global kind Installation Over BINGO-Managed Version

This change respects developers' environments and preferences by prioritizing the globally installed kind binary for managing Kubernetes clusters. It reduces potential conflicts and debugging issues, ensuring better compatibility with existing setups.
Scenarios Addressed

Image Loading Issues:

Using a BINGO-installed kind binary caused images to load into the wrong cluster, leading to debugging delays.

Hidden Clusters:

Clusters created with the BINGO-managed kind were not visible in the global kind context, causing resource leaks and confusion.

Proposed Solution

Check for a globally installed kind binary and use it if available.
Fallback to the BINGO-managed kind binary only when no global version is detected.
Provide clear messaging about the binary being used.

Benefits

Respects developers' preferences and existing environments.
Prevents unnecessary debugging and resource leaks.
Aligns with standard workflows while maintaining BINGO compatibility.

Hi @m1kola

.bingo/Variables.mk is auto-generated. We can't edit it (see notice at the top of the file).

It worked locally. But if it is autogenerated, it will be lost
Oh, that changes a lot of things
So, has no way to implement it with BINGO
Is there no place where I can say the same for BINGO?

Closing this one


Instructor Selection: Event listing headers for Instructor view

The current header for the Instructor view is

(slug) at (venue)

Instead we would like to see

(Lesson Program/Curriculum) at (Host Site) on (dates)

@maneesha by lesson program do you mean for example "Data Carpentry: Genomics"? Or do you mean something else?
For Host Site we don't currently store anything related to site on Host (Organization) model, do you perhaps mean just the Host name?

Yes - this is exactly right. Thank you!