Write-Host "##vso[task.setvariable variable=someVar;]someValue" sets are (sometimes) overwritten with 'default' values in subsequent PowerShell -Argument steps

In a Meta-Task, we've got a Property/Variable defined that needs to be set from within an AzurePowerShell script.
We've verified that the script is writing the correct resulting string with Write-Host, however the next step in the Meta-Task (executed during a Release) is not getting the new value set in the previous step.
In a normal PowerShell script task, the setvariable command works fine.
The steps in this particular Meta-Task were all created automatically by the tool from a build definition where this was working previously.

what is your agent version?

Are you updating a variable that was defined already on your definition? Or is the ##setvariable command defining a new variable?

I spent A LOT of time investigating this, and have found some odd inconsistencies.
It appears this is at least partially-related to Meta-Task execution and the 'magic' that happens behind the scenes with Variables, Parameters, and Environment Variables.
Also in our scenario, the Release in question should not have to specify a value for the variable we are trying to set and then use as a param in a subsequent task.
Scenario 1:
Use a Variable set from a previous PoSh step in a later PoSh step, without using the -Arguments task parameter

Release: no Variables, single Meta-Task Step
Meta-Task: no Properties (no $(variable)s used in task params, yet)

AzurePowerShell: execute .ps1 (no arguments)

write-host "##vso[task.setvariable variable=TestVar]TestVal"

AzurePowerShell: execute .ps1 (no arguments)

write-host ("TestVar:   {0}" -f $env:TestVar)

This results in expected output in the 2.ii : "TestVar: TestVal"
Scenario 2:
Use a Variable set from a previous PoSh step in a later PoSh step, as -Argument -TestVar $(TestVar), without editing the Release (trying to edit the Release will force you to enter a value for the new MT Property.)

Release:

no Variables, single Meta-Task Step (don't update Release after updating MT.)

Meta-Task: 1 Property: TestVar, DefaultValue: {empty}

AzurePowerShell: execute .ps1 (no arguments)

write-host "##vso[task.setvariable variable=TestVar]TestVal"

AzurePowerShell: execute .ps1 (1 argument: "-myTestVar $(TestVar)")

Param( [string]$myTestVar )
write-host ("TestVar:   {0}" -f $myTestVar)

This results in expected output in the 2.ii : "TestVar: TestVal"
Also, in the Log for that Step, you can see the platform make the call to the .ps1, passing the value set from 2.i: timestamp ##[command]& 'C:\apps\buildagent\_work\9384aa42c\folder\myScript.ps1' -myTestVar TestVal
Scenario 3:
Use a Variable set from a previous PoSh step in a later PoSh step, as -Argument -myTestVar $(TestVar), after editing the Release to supply a default value (because it does not allow empty string)

Release:

Meta-Task Step,

TestVar Property: $(TestVar) DefaultValue: "will overwrite"

Meta-Task: 1 Property: TestVar, DefaultValue: {empty}

AzurePowerShell: execute .ps1 (no arguments)

write-host "##vso[task.setvariable variable=TestVar]TestVal"

AzurePowerShell: execute .ps1 (no arguments)

write-host ("TestVar:   {0}" -f $env:TestVar)

AzurePowerShell: execute .ps1 (1 argument: "-myTestVar $(TestVar)")

Param( [string]$myTestVar )
write-host ("TestVar:   {0}" -f $myTestVar)
write-host ("TestVar:   {0}" -f $env:TestVar)

This results in an expected output in the 2.ii AND 3.iii : "TestVar: TestVal"
However, in 3.ii when the platform makes the call to the script, the value being passed for myTestVar is "will overwrite", not "TestVal".

Adding RM who did meta tasks

it sounds like in scenario 3 the variable is getting expanded server side before the job message is sent down to the agent.

Thanks for the Replies.
I've found a workaround for this.

In the Build or Release where the MT is used, create a variable with no value.
In the Meta-Task configuration, specify that variable for the MT Property (which is ultimately not needed in the parent).

I did not test if the variable/property names in the consumer (build/release) or MT can be named differently - in my case they are the same.

Related to this, I've also had trouble retrieving the value of a Property set in a MT, in a subsequent step in the consuming Build or Release. (ie: a MT sets a version number or something similar that would be used in another MT, for instance.) I didn't spend really any time on a thorough investigation though.

@JoeBrockhaus Thanks for a detailed write up of the scenarios that you have tested. I reproduced scenario 3. I think Eric is right that the variable replacement is happening server side where meta tasks are expanded to tasks because of which the variables are replaced before even the build/release has started.
The workaround that you have mentioned circumvents this by using a variable in MT property in a release/build so when the replacement is happened it is replaced with the value which itself contains a variable.
Instead of directly creating a release, create a draft release, then open that draft release. The draft release will show all the meta tasks expanded, you can easily inspect the value substitutions.
About retrieving the value of a variable (not property) set in a MT, this should work properly. If you set something in MT1 by using WriteHost setvariable and then you can use that value in subsequent tasks by using it like $(varName).
As a side thought, I don't know whether its a good idea to have meta task which is dependent on another meta task for setting a variable as it is not explicit. We do have a story coming up which will allow tasks to explicitly set output variables but I don't have the timelines.
Let me know if this solves your issue or not.

@harshil93 Thanks for the feedback. Creating a Draft immediately de-mystified the Meta-Task dereferencing, so that was helpful. This allows us to modify those values when creating manual releases. The caveat of needing to create the (extraneous) variable in the Build/Release is an easy-enough workaround for this.

Also just to clarify what I meant about (dynamically created) variables from a MetaTask being available in subsequent build tasks - the dependency was not between multiple Meta-Tasks, but just another task in the Build/Release.
For instance, when using the GitVersion task, in a following task you may want to leverage the variables it creates (FullSemVer, etc). Similarly, for Meta-Tasks, there are variables, like in our use case which should not be required for the build/release to know about (or provide a value for during configuration), but should be able to use if they know about them in later steps. Perhaps I was doing something wrong (and I did not test this thoroughly), but I was unable to in this case. (I will acknowledge that knowing a bit more how Meta-Tasks are dereferenced makes me question the behavior I saw, but I just thought it was worth mentioning in case it's related to the same bug that causes the wrong -Argument variable expansion in this instance.

I'm trying to set a variable from my inline powershell script Write-Host "##vso[task.setvariable variable=git_date](Get-Content commit.log)[2]"
What I'm getting is the value of git _data is the string literal "(Get-Content commit.log)[2]" and not the value that should be evaluated by the expression. Any ideas? I can do this easily in bash but ps is new to me.

@TingluoHuang @ericsciple - is executing PS commands supported within ##vso commands?

@davidlbyrne this is the syntax you want: Write-Host "##vso[task.setvariable variable=git_date]$((Get-Content commit.log)[2])"
Please open a separate thread if that doesn't work. This thread is too long and more about task groups. Also this sounds more like a generic powershell question.

I have 2 powershell scripts
On macOS
PowerShell script 1
Write-Host "##vso[task.setvariable variable=myvar;]$value"
The above line worked under macOS.
I could see ##[debug]Processed: ##vso[task.setvariable variable=myvar;]/Users/abc/ in the log file
PowerShell script 2
$env:myvar ----> This does not get any value
On Windows it works fine and the PowerShell script 2 does get the proper value of "myvar"

Fixed !!
the variable name was in all CAPS in this case it was MYVAR
on windows I could access by $env:myvar but not in the case of macOS

Starting 11/20 we started seeing the same issue as originally reported:

In a Meta-Task, we've got a Property/Variable defined that needs to be set from within an AzurePowerShell script.
We've verified that the script is writing the correct resulting string with Write-Host, however the next step in the Meta-Task (executed during a Release) is not getting the new value set in the previous step.

I've just run in to this and I can confirm that the workaround recommended by @JoeBrockhaus fixes it.
In my case I have a variable called $(ContentContainer) which is set by powershell inside the task group. I created a release variable called $(ContentContainer) with no value and passed that into the task group from the pipeline. Messy, but it works.
I suggest that task groups should allow parameters to be marked as Internal, meaning that they not exposed in the pipeline parameter dialog.

Workaround of @JoeBrockhaus works!

Starting 11/20 we started seeing the same issue as originally reported:

In a Meta-Task, we've got a Property/Variable defined that needs to be set from within an AzurePowerShell script.
We've verified that the script is writing the correct resulting string with Write-Host, however the next step in the Meta-Task (executed during a Release) is not getting the new value set in the previous step.

This is an enhancement request hence added enhancement label.

I am not having luck with the workaround, but I may have a different problem.
I setup a release pipeline with multiple stages. One stage sets a task variable I need in subsequent stages. I tried setting an empty variable with release scope, but the variable is only available in the stage that creates it. I then tried setting the scope to the stage that requires it, but that did not work either. The variable is getting set and the value is correct.
One thing to note, each stage is made up of task groups, so I then tired to set the variable outside the task group, but again it was only available to the stage that created it,

I think I've found a simpler workaround. Assuming you have a TaskGroup (a.k.a. MetaTask?) with:

a task that sets myvariable with something like this
Write-Host "##vso[task.setvariable variable=myvariable;]banana"
and another task that consumes the $(myvariable) value later

The TaskGroup will add a parameter for $(myvariable). Give it a default value of the literal string $(myvariable) and the calling plan or task group won't recognise it to substitute it, leaving $(myvariable) as the parameter value.
At final execution time the desired value 'banana' is substituted into this variable, and the caller has not needed to know anything of this at all.

@AndyP2  That workaround does not work on Azure DevOps Server for me for some reason. Even though I set the variable in a task, the second task uses the literal value $(myvariable). Have you had that problem? Or maybe it is a different behavior between versions.

I'm using Azure DevOps Service, so that might be the difference, but I have just recreated the scenario and it is working as expected:

TaskGroup

one parameter 'myvariable' with default value $(myvariable)
"task 1: set" powershell inline script:
Write-Host 'setting myvariable=banana'
Write-Host '##vso[task.setvariable variable=myvariable;]banana'
"task 2: display" powershell inline script:
Write-Host 'myvariable is now $(myvariable)'

Release pipeline with one stage, one agent, one task which is the taskgroup:

one parameter 'myvariable' with value $(myvariable) as supplied by the default

Output:

"task 1: set"
setting myvariable=banana
"task 2: display"
myvariable is now banana

I just ran into this "Problem" and it took me a while to find the cause and read this thread.
I have a lot of Task Groups in both Build and Release pipelines and the work-arounds noted here require an increasing number of Build and Release variables. Being able to mark Task Group variables as "Internal" would solve this. Is there any consideration to implementing this?

This issue is stale because it has been open for a year with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days

@AndyP2

I'm using Azure DevOps Service, so that might be the difference, but I have just recreated the scenario and it is working as expected:

Thanks for showing exactly what to do. Saved me a lot time.


Feature/send arrow becames a large button

Description
Closes #2387
Closes #2279
Modify QueryUrl component to change arrow icon with a send button.

Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.

I agree that some folks might prefer a big visible button to perform this action.
However, the current one also looks aesthetically pleasing and is minimalist
Closing this PR as it cannot be merged.
I am open to support an option to toggle this.
I would suggest something that can be in Preferences -> Appearances -> Send Icon that the user can select.

I agree that some folks might prefer a big visible button to perform this action. However, the current one also looks aesthetically pleasing and is minimalist
Closing this PR as it cannot be merged. I am open to support an option to toggle this. I would suggest something that can be in Preferences -> Appearances -> Send Icon that the user can select.

Thank you for reviewing it, giving feedback and giving the new idea!


Update defibrillator.json with most useful presets

so let's try this pr. just simply add more fields to the presets.

@Turnrdev can you check this PR?

Is there something that i could do? Or any reason why the pull request is open?

Hopefully a mod sees it

@quincylvania can i add something more?

I changed descriptionon the last commit.

I've reconsidered it. access_simple is not what i wanted. I wanted a set of meaningful and clear changes. If this is not possible, i am happily closing this PR.


Time: include hours

Include hour information in time, duration and remaining time selectors (only when duration is longer that 1 hour).
Also removed the leading zero in hour info, as it seems to be the default in sites like youtube, mixcloud...

Thanks, this helps out a lot!


Add hyperkit support

This supersedes PR#280. It's missing changes for crc setup in order to download the crc-driver-hyperkit and hyperkit binaries. If hyperkit is in /usr/local/bin and crc-driver-hyperkit is in the PATH, crc start/crc stop/crc delete should work fine.
The Move generation of .crc-exist file to generic code commit does not belong in this PR, but it was more convenient to have it here for now.

Draft and deployments? Something changed recently ;-)

What I force-pushed still needs work, stop/... is not working properly yet.

[WIP] add hyperkit support

Still WIP ?

Draft and deployments? Something changed recently ;-)

Now I'm not sure how to remove the "draft" tag :(

Tested locally, works for me :+1:
The CI failure is due to gofmt error, need to run make fmt and push again.


htmlsafe_dumps doesn't handle lazy strings

I need to be able to handle lazy strings in the Jinja2 |tojson filter and was thinking about some way to do it: as of now, the _iterencode_dict raises a TypeError exception, as expected:
Traceback (most recent call last):
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1836, in __call__
    return self.wsgi_app(environ, start_response)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1820, in wsgi_app
    response = self.make_response(self.handle_exception(e))
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1403, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/base.py", line 68, in inner
    return self._run_view(f, *args, **kwargs)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/base.py", line 354, in _run_view
    return fn(self, *args, **kwargs)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/model/base.py", line 1466, in index_view
    return_url=self._get_list_url(view_args),
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/base.py", line 294, in render
    return render_template(template, **kwargs)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/templating.py", line 128, in render_template
    context, ctx.app)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/templating.py", line 110, in _render
    rv = template.render(context)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/jinja2/environment.py", line 969, in render
    return self.environment.handle_exception(exc_info, True)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/jinja2/environment.py", line 742, in handle_exception
    reraise(exc_type, exc_value, tb)
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/templates/bootstrap3/admin/model/list.html", line 5, in top-level template code
    {% import 'admin/actions.html' as actionlib with context %}
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/templates/bootstrap3/admin/master.html", line 1, in top-level template code
    {% extends admin_base_template %}
  File "/home/manuel/dev/www/python/watest/webfu-app/webfu/modules/backend/templates/admin/custom-layout.html", line 3, in top-level template code
    {% import 'admin/static.html' as admin_static with context %}
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/templates/bootstrap3/admin/base.html", line 80, in top-level template code
    {% block tail %}
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask_admin/templates/bootstrap3/admin/model/list.html", line 171, in block "tail"
    {{ filter_groups|tojson|safe }},
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/json.py", line 243, in tojson_filter
    return Markup(htmlsafe_dumps(obj, **kwargs))
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/json.py", line 186, in htmlsafe_dumps
    rv = dumps(obj, **kwargs) \
  File "/home/manuel/.virtualenvs/webapp/lib/python2.7/site-packages/flask/json.py", line 126, in dumps
    rv = _json.dumps(obj, **kwargs)
  File "/usr/lib/python2.7/json/__init__.py", line 250, in dumps
    sort_keys=sort_keys, **kw).encode(obj)
  File "/usr/lib/python2.7/json/encoder.py", line 209, in encode
    chunks = list(chunks)
  File "/usr/lib/python2.7/json/encoder.py", line 434, in _iterencode
    for chunk in _iterencode_dict(o, _current_indent_level):
  File "/usr/lib/python2.7/json/encoder.py", line 382, in _iterencode_dict
    raise TypeError("key " + repr(key) + " is not a string")
TypeError: key lu'Nome categoria' is not a string

I can't really use the gettext since i need the lazy_gettext version, and was asking for advice and ideas on how to tackle this problem: i tried subclassing the flask.json.JSONEncoder class as per this example and i'm handling lazy strings in the default method there, but it looks like it doesn't get called at all.
There is the iterencode method i could try to subclass, but it probably won't be a clean way to do it?
Thanks for any input you can give.

Ok, for now i reimplemented the original iterencode and i'm handling the is_lazy_string condition in the _iterencode_list, _iterencode_dict and _iterencode methods of the iterencode builder.
While this works fine, i really would like to know if a better solution exists.

@manuelbua Do you have sample code that can replicate the error so we can understand your use case? Thanks.

I think this can be safely closed: i probably managed to get around it in some ways i can't remember..
Feel free to close this issue, thanks!


Fixes #4637 Allow filtering SSE events by types

Allow recievieng only specific events by providing their types
in event_type query params. Old behavaiour remains unchanged.
Cherry-picked: a95701ed755603d620e635ddacb0ff95d7fcf9bd (#4671)

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

@janisz Thanks!


IOS not working.

Hi,
I am currently working on a project with Intel XDK 2807.   We have installed the plugin and wrote all the code for the project in android and it works perfectly.
We have now the need to have it IOS and when we try to run the code, all the functions are returning a unsupported function error.
I am sure this is a small thing that we cannot figure out.
Can you please help us on this.
Thanks

Nothing immediately pops out. We are using this exact code on our iOS app, so if you could make a minimal complete example project that reproduces this issue and put it on github (or create a codepen that I could use to make one), that would help us figure out what's going on.

Are you using Intel XDK as a development platform?  Or something else.   I am starting to think it is a problem in intel XDK
since I cannot get any bluetooth framework to work on IOS.
As for the project example?  Do you want the entire xdk directory?
Thanks
---- Original Message ----
From: George Stocker<EMAIL_ADDRESS>To: Jewelbots/ng-cordova-bluetoothle <ng-cordova-bluetoothle@nAre you using oreply.github.com>
Cc: johrob<EMAIL_ADDRESS>Sent: Sat, Dec 19, 2015 10:43 pm
Subject: Re: [ng-cordova-bluetoothle] IOS not working. (#3)
Nothing immediately pops out. We are using this exact code on our iOS app, so if you could make a minimal complete example project that reproduces this issue and put it on github (or create a codepen that I could use to make one), that would help us figure out what's going on.
—
Reply to this email directly or view it on GitHub.

Just the Cordova and associated JS needed to make an example work.


Rollback Role Grants Changes

Rollback of Role Grants Resource Changes. Solves #922

Test Plan

[x] acceptance tests
[x] tests

@alldoami Can you review, merge and release asap, there are multiple people blocked by this. Thanks in advance


Multiple use

Hi!
Is it possible to multi-use on the same page without duplicating the preview?

So you want to use it multiple times but the preview element should always be the same for multiple inputs? You actually can use it multiple times and since you can specify the class of the preview element it should work to use one of them multiple times. Would overwrite the previous previewed image though.


[compatible] Registry compatibility #3882

What is the purpose of the change
fix #3882
Brief changelog
Registry compatibility: add some abstract class compatible.
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #4015 into master will decrease coverage by 0.27%.
The diff coverage is 0%.

@@             Coverage Diff             @@
##             master   #4015      +/-   ##
===========================================
- Coverage     63.47%   63.2%   -0.28%
  Complexity      565     565
===========================================
  Files           750     759       +9
  Lines         32415   32908     +493
  Branches       5145    5218      +73
===========================================
+ Hits          20577   20799     +222
- Misses         9480    9750     +270
- Partials       2358    2359       +1

Impacted Files
Coverage Δ
Complexity Δ

...pache/dubbo/registry/support/FailbackRegistry.java
74.28% <ø> (ø)
0 <0> (ø)
:arrow_down:

...ibaba/dubbo/registry/support/FailbackRegistry.java
0% <0%> (ø)
0 <0> (?)

...ibaba/dubbo/registry/support/AbstractRegistry.java
0% <0%> (ø)
0 <0> (?)

...ubbo/registry/support/AbstractRegistryFactory.java
0% <0%> (ø)
0 <0> (?)

.../java/com/alibaba/dubbo/common/utils/UrlUtils.java
0% <0%> (ø)
0 <0> (?)

...ava/org/apache/dubbo/common/utils/StringUtils.java
86.22% <0%> (-0.69%)
0 <0> (ø)

...ava/com/alibaba/dubbo/registry/NotifyListener.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...onfig/spring/extension/SpringExtensionFactory.java
78.04% <0%> (-7.32%)
0% <0%> (ø)

...ng/transport/dispatcher/all/AllChannelHandler.java
57.14% <0%> (-5.72%)
0% <0%> (ø)

...in/java/org/apache/dubbo/common/utils/JVMUtil.java
81.13% <0%> (-5.67%)
0% <0%> (ø)

... and 35 more

Continue to review full report at Codecov.

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


DataBlock fixes

Two patches to improve the Data Block and Fragment implementations.
Commit 2851102 is a bug fix related to data serialization, and commit b119727 fixes incorrect CRC masks for Rate 1/2 and Rate 1 Data blocks.
Thanks!

I also have a third patch ready that refactors Data Block size calculation to better distinguishing between various Data Block sizes and their corresponding user data capacity.
It contains no functional changes, so it is obviously less important..
Should I push it to this branch, or do you prefer a separate PR for the refactor?

Thanks!


FlutterCallkitIncoming.endCall is not use when callkit window is full window

when click top popup window, and callkit ui switch to full; now call FlutterCallkitIncoming.endCall(uuid) is not end!! the full window still exist after call

Please update to version 2.0.0 (make sure you check the changelog, because the input structure has been changed)

Thanks a lot


txn: use Commit to clean up pessimistic locks

Signed-off-by: youjiali1995<EMAIL_ADDRESS>
What have you changed?
A pessimistic lock may be left and the corresponding transaction is committed. In this case, the lock will never be cleaned up, so we use Commit to clean up it.
What is the type of the changes?

Bugfix (a change which fixes an issue)

How is the PR tested?

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Does this PR affect documentation (docs) or should it be mentioned in the release notes?
Yes
Does this PR affect tidb-ansible?
No

/run-all-tests

LGTM

/test

/run-all-tests

/test

/test

/test

/test


Develop Evaluation Metric

How can we compare different approaches?

There are different possible ways to formulate an evaluation:

Human extrinsic evaluation: Choose two or three clear test cases of semantic shift where an expert manually annotates different related concepts (to a target term) and how the related concepts vary across different year/decades. Then, compare the terms chosen by automatic methods to the human-labeled examples: how well do the clusters match expectations? This is not scalable, but we have all the control over what domain and cases we care about.
Lexical Semantic Shifts: generate labeled test sets or re-use the datasets created for semantic shift shared tasks on other languages. A good source of inspiration should be the AXOLOTL-24 Shared Task on Explainable Semantic Change Modeling. This is evaluation at scale but the out-of-domain evaluation might not reflect how well the models will perform for our data.
Framing: A popular task with NLP in the social sciences is the concept of Framing Detection. In a way, we are actually detecting how a target term is being framed in the different time epochs. Therefore, we could also look at related work to imitate the ways they have evaluated their results.


[SSR] pass request headers to ssr server

It would be great if the HttpGateway will forward the original http context (headers, ip, etc) to the ssr renderer.
This would unlock client dependent opportunities (mobile detection, regional specific content, etc.) .

Could you elaborate on why this is helpful and how this would work? I'm having a hard time understanding how this would work, while I get the value of it.
To be clear; Inertia's SSR would only render the HTML of the initial request, so it would only render HTML once, after that it's all CSR. This is useful for search engines and an optimization for load times. However, if you're conditionally rendering things based on the headers, that wouldn't work client-side, because that also doesn't receive request headers

Let's look at view port for example
useViewPort.js
import {onMounted, reactive} from 'vue';

// no request context
const vp = reactive({w: 0, h: 0});

// with request context
const vp = reactive({w: parseUserAgent(req.headers.userAgent).type === 'mobile' ? 400 : 1024, h: 0});

export default function useViewPort() {
  if (typeof window !== 'undefined') onMounted(async () => {
    vp.w = window.innerWidth;
    vp.h = window.innerHeight;

    window.addEventListener('resize', () => {
      vp.w = window.innerWidth;
      vp.h = window.innerHeight;
    });
  });

  return vp;
}


The doc command never exits

When you for instance run ng doc router, then it does open the URL as expected, but then command never exits. You have to manually kill the process (e.g. CTRL-C). The reason for this is that it's using open internally and wraps it in a promise. However, the promise is never resolved, so the process will stay alive. Here's the code:
https://github.com/angular/angular-cli/blob/efb97c87f023497dc59a2f4fa3825a2ca78606da/packages/angular/cli/commands/doc-impl.ts#L54-L58
I am not sure if I am missing something, but the promise should be resolved pretty much immediately, because open is also instructed to not wait.
I am happy to fix this in a PR.

@d3lm, I the proposed fix does make sense. Please feel free to open a PR.

Closed via https://github.com/angular/angular-cli/pull/19915


Group-by-min fails on L0 for nullable FP columns

Example query:
SELECT x, MIN(ff) AS val FROM test GROUP BY x ORDER BY val;

Fixed by the shared memory patches series.


Compose: Fix padding in banner/compose when text message is long.

When the text message is long enough to be scrollable in compose, the top border of banner disappears.
CZO Discussion

@zulipbot claim

claim

@zulipbot claim

@zulipbot claim

This issues seems to be resolved as mentioned in CZO.


this.requestData is not a function

I received this error when terminating the recording with a timer and can absolutely not figure out why it appears.
The error references https://github.com/ai/audio-recorder-polyfill/blob/master/index.js#L133 as the source of the issue, but since the class clearly has a method of that name i'm a bit lost on why the error gets thrown.
Sorry if i'm not seeing the clear issue here.
I'm using the suggested polyfill implementation given in the README with Webpack.
Thank you for your help :)

Use of the polyfill can be found here: https://github.com/leifniem/Vue-Audio-Survey/blob/master/src/js/recorderMixin.js

This diff will fix the problem:
- setTimeout(this.$_recorder.stop, maxTakeLength)
+ setTimeout(() => this.$_recorder.stop(), maxTakeLength)

The passing method to setTimeout (or any other function with callbacks) will detach this in this method.

Thank you very very much!
Sorry for raising this as an issue 😅


Local compound database search  (.csv)module input files size

Basic information

My operating system and version: windows 11 pro
My mzmine version: 4.0.8

What happened  -  in this version is not possible to input .csv larger than 10 KB in this annotation module. The following error of task appears: "Input length = 1"
In previous versions I could use files larger than 1 MB, so I think this can be a bug or a error in some code line.

I'm uploading a standalone file and the .csv file that I used to use for this same data in previous versions: https://drive.google.com/drive/folders/1xh_ybMBU7Hvxjn6lMynctzGq0_iWiFep?usp=drive_link

I'm having the same problem - my CSV file only works in MZMine 3.

Same problem here as well (Mzmine 4.3.0)


Please build a new PyPi release

...maybe after Yuvi's suggestion of putting the whole JWT into auth_state.

Yes, I'd also appreciate a new version. I've just realised the version on pypi as ancient and doesn't support configuring header_is_authorization.


Question

How to use schematics

To use schematics you just download the schematic to your likes from the internet. (There are a lot of those, just search on PlanetMinecraft for example) Then put the .schematic file in the BlockSniper/schematics/ folder with the desired name, and finally go in-game and use /schematic paste <schematic file name without .schematic>

The schematic should then pop up on the location you look at. If you have problems with it feel free to ask for some more clarification.

k thx ill try this

there is no such commqnd..

Oops sorry, /paste schematic

doesnt paste..
https://www.planetminecraft.com/project/kayt-the-floating-castle-download/

None of the schematics work..

Big schematics take some time to paste. Don't expect it to happen in an instance. If you turn debug level to 2 in the pocketmine.yml you can see the progress.

21.10 11:29:25 [Server] INFO Fatal error: Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 4096 bytes) in phar:///custom-php7.2.phar/src/pocketmine/block/BlockFactory.php on line 384
21.10 11:29:25 [Server] Server thread/CRITICAL Could not execute asynchronous task PasteTask: Task crashed
21.10 11:29:26 [Server] INFO Fatal error: Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 12288 bytes) in phar:///custom-php7.2.phar/src/pocketmine/level/format/Chunk.php on line 1002
21.10 11:29:26 [Server] Server thread/CRITICAL Could not execute asynchronous task ChunkRequestTask: Task crashed
21.10 11:29:29 [Server] INFO Fatal error: Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 8192 bytes) in phar:///custom-php7.2.phar/src/pocketmine/level/format/Chunk.php on line 1002
21.10 11:29:29 [Server] Server thread/CRITICAL Could not execute asynchronous task ChunkRequestTask: Task crashed

... Which means the schematic was too big to execute. I'll work on doing this in such a way that the least memory gets consumed soon.

So, I cant paste that scheme .-.

In fact... What you COULD try, is setting the async worker memory limit higher. I can't promise that'll make it work, but it might.


:green_heart: Fix missing indent in yaml deploy file

Ticket: N/a
Description:

The script validated as correct, but I think a key was indented wrong? Not sure why the test parser says it's fine but github says it's not.

We should add pre-commit hooks.


It would be nice to select maven/gradle build artifacts for local devappserver runs

Some background info:
For the App Engine standard environment, we have a custom run configuration that runs the devappserver (the local development server used for running AE standard apps locally):

Editing the configuration, you'll notice the 'Artifact to Deploy' field:

This field controls the source of deployment to the local server: currently, the only available source is a native artifact source (that uses the native intellij build system).
The goal here is to allow users to also deploy from Maven sources (Gradle support is likely still limited due to limitations in the gradle integration). This is similar to what we already support for deployment:

Notice the 'Maven build' deployment source, and the 'maven package' before launch task at the bottom.

+1! I think we may already have an issue for this somewhere.
On Tue, Oct 31, 2017 at 11:05 AM, Etan Shaul<EMAIL_ADDRESS>wrote:

Some background info:
For the App Engine standard environment, we have a custom run
configuration that runs the devappserver (the local development server used
for running AE standard apps locally):
[image: image]
https://user-images.githubusercontent.com/1735744/32230920-a01f805c-be2a-11e7-9e38-5198a4e29387.png
Editing the configuration, you'll notice the 'Artifact to Deploy' field:
[image: image]
https://user-images.githubusercontent.com/1735744/32230962-bb611d6c-be2a-11e7-8e55-2367557b15d2.png
This field controls the source of deployment to the local server:
currently, the only available source is a native artifact
https://www.jetbrains.com/help/idea/working-with-artifacts.html source
(that uses the native intellij build system).
The goal here is to allow users to also deploy from Maven sources (Gradle
support is likely still limited due to limitations in the gradle
integration). This is similar to what we already support for deployment:
[image: image]
https://user-images.githubusercontent.com/1735744/32231112-250d1482-be2b-11e7-8e22-963897ff69a2.png
[image: image]
https://user-images.githubusercontent.com/1735744/32231165-450badf2-be2b-11e7-932e-56aba29cd3af.png
Notice the 'Maven build' deployment source, and the 'maven package' before
launch task at the bottom.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1235#issuecomment-340791833,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HUVrg-8ixc9OU-xeCPxOGMKXkPkKks5sxzdPgaJpZM4L8ei0
.

This is the issue :). You created it earlier. I was just adding details for Ivan so that we can assign to him and he has a little bit of context.

Doh!
On Tue, Oct 31, 2017 at 11:27 AM, Etan Shaul<EMAIL_ADDRESS>wrote:

This is the issue :). You created it earlier. I was just adding details
for Ivan so that we can assign to him and he has a little bit of context.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1235#issuecomment-340798889,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HfvyYXqh-8mQfXQsSFbOBcP2LDPJks5sxzxZgaJpZM4L8ei0
.


It is impossible to import project exported in the same app from another comp

Your description here
Expected outcome
What should happen?
Exported file should be imported
Actual outcome
What happened?
Unable to parse the file message
Versions
App: <IP_ADDRESS>6-stable
Chrome: 55.0.2883.87
Platform: Windows (7)
Steps to reproduce

Hi thank you for issue report.
Import / export issues most probably have been fixed recently.
Can you test it in beta version? To do so you need to join beta tester group (https://groups.google.com/forum/#!forum/advanced-rest-client-beta-channel) to be able to install ARC beta  (https://chrome.google.com/webstore/detail/advanced-rest-client-beta/epgngalmiadbjnoompchcohonhidjanm)
It should work there but I'd be grateful for confirmation.

This issue is fixed in the stable release (updated today). Should not be more problems with data import.


Expression boolean string evaluated as long

In GitLab by @ksiero on Jul 30, 2021, 11:09
The Expression should be able to interpret:
 y|Y|yes|Yes|YES|n|N|no|No|NO
|true|True|TRUE|false|False|FALSE
|on|On|ON|off|Off|OFF

Link
as long values (0 or 1).

In GitLab by @ksinkiewicz on Aug 24, 2021, 12:24
mentioned in commit 79d4d15e10bcf369f51dbe8f101f672929c38970

In GitLab by @ksinkiewicz on Aug 25, 2021, 11:03
mentioned in commit 55f96d04d2169efb35354d1a6b8badf649242877

In GitLab by @ksinkiewicz on Nov 14, 2021, 17:13
mentioned in commit 4d12380582ccd84abe604300bf2eb82eb731967d

mentioned in commit 779d99e39adbd01956c232193d8230b15e86a270


Device list arrives but not populated to HA

Describe the bug
I see my devices' list arriving in the debug, but not being set up
Version of the custom_component
1.1.9
Debug log
2024-10-08 10:18:37.504 INFO (MainThread) [homeassistant.components.sensor] Setting up home_connect_alt.sensor
2024-10-08 10:18:37.505 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up home_connect_alt.binary_sensor
2024-10-08 10:18:37.505 INFO (MainThread) [homeassistant.components.select] Setting up home_connect_alt.select
2024-10-08 10:18:37.505 INFO (MainThread) [homeassistant.components.number] Setting up home_connect_alt.number
2024-10-08 10:18:37.505 INFO (MainThread) [homeassistant.components.button] Setting up home_connect_alt.button
2024-10-08 10:18:37.507 INFO (MainThread) [homeassistant.components.switch] Setting up home_connect_alt.switch
2024-10-08 10:18:37.508 INFO (MainThread) [homeassistant.components.time] Setting up home_connect_alt.time
2024-10-08 10:18:37.513 DEBUG (MainThread) [home_connect_async.homeconnect] Exiting SSE event stream
2024-10-08 10:18:37.513 DEBUG (MainThread) [home_connect_async.api]
HTTP GET /api/homeappliances (try=1 count=1)

2024-10-08 10:18:37.809 DEBUG (MainThread) [home_connect_async.api]
HTTP GET /api/homeappliances (try=1 count=1) [200 OK] ====>
{
  "data": {
    "homeappliances": [
      {
        "brand": "Bosch",
        "connected": false,
        "enumber": "WxxxxxxxxxY/01",
        "haId": "xxxxxxxxxxxxxxxxxxxxxxxxxxx",
        "name": "Washing machine",
        "type": "Washer",
        "vib": "WxxxxxxxxxY"
      },
      {
        "brand": "Bosch",
        "connected": false,
        "enumber": "Sxxxxxxxxxxx2",
        "haId": "xxxxxxxxxxxxxxxxxxxxxxx",
        "name": "Dishwasher",
        "type": "Dishwasher",
        "vib": "SxxxxxxxxxxE"
      },
      {
        "brand": "Bosch",
        "connected": false,
        "enumber": "Wxxxxxxxxxxx1",
        "haId": "xxxxxxxxxxxxxxxxxxx",
        "name": "Dryer",
        "type": "Dryer",
        "vib": "WxxxxxxxxxxxY"
      }
    ]
  }
}

2024-10-08 10:18:37.810 DEBUG (MainThread) [home_connect_async.homeconnect] Connecting to SSE stream

then the Status switches from INIT to READY and nothing happens. Tried with the existing Developer Key, created new, nada.
I have the Home Connect app on 4 mobile devices, all wifis were turned off. All HC devices were turned on.
Please advice how to make it work. Thanks!
** network info **
HA is running in Docker on a Raspberry PI. The Pie has wifi and ethernet connection enabled; it's on the same network, AP and VLAN as the HC devices.

home-assistant_home_connect_alt_2024-10-08T14-56-01.263Z.zip
hi, here's the complete log file. however after some restarts and HA update it started working (there was a Bosch API downtime as well in this timeframe) so I still don't know what caused this issue in the first place.

Happy to hear it's working now. I'm going to assume it was related to the HC service issues and go ahead and close this issue now. Feel free to reopen if the problem appears again, just please include a fresh log in that case.


firewal_nat_edit function name typo

This unrelated fix is in a big diff listing of other stuff related to a proposed RADIUS enhancement https://github.com/pfsense/pfsense/pull/3407/files#diff-f080be89fa12ff3c28d7467b12985d09
The accidental typo should be fixed, rather than getting stuck in that other PR.

Note: all this code section looks dodgy also, but that is a separate issue.


Support SSL transport for log messages

+1

Should be supported now.
  -tlskey string
        path to CA key file for TLS-enabled TCP server. If not set, TLS not activated
  -tlspem string
        path to CA PEM file for TLS-enabled TCP server. If not set, TLS not activated


error TS2305: Module ''vscode'' has no exported member 'TreeView'

I tried launching the Tree View sample and basically the "treeview" doesn't exist in the vscode namespace.  I have the latest installed (not sure if that does anything).

Fixed by increasing the vscode.engine version in package.json


.tmpl files need to indicate in their generated output that the file was generated

For example, GameConfig.gd.tmpl creates GameConfig.gd, but Godot only sees the latter.
If a user makes edits to the latter, and then runs build-templates, this will alter the output without the user's edits.
Need to make note in all .tmpl generated files at the top in comments that this is a file generated by OMGD, and note the path (relative) of the original .tmpl file to the user

putting this back to the backlog for now: complications arise around what filetype is being generated, and what the comment rune should be
e.g. in Gdscript, it should be #, and in CSharp, it should be ///. For OMGD to be agnostic towards game engines would mean an exhaustive mapping of comment runes to filetypes based on their extension, which can cause a lot of conflicts down the road as expansions towards other game engines are introduced. This would be nice once this has gotten some to any traction. Will get to it later, maybe.


Alzheimer detection

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Web application for Alzheimer detection
:red_circle: Aim : To identify the stage of Alzhhemir's Disease using  Alzheimer's dataset consists of MRI images and showing result using flask app
:red_circle: Dataset : https://www.kaggle.com/datasets/tourist55/alzheimers-dataset-4-class-of-images
:red_circle: Approach : using CNN  and  InceptionV3 model for  classification of alzhemir disease evaluating their performance using a test dataset for choosing the best deep learning model  and deploying it to a flask app

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name : Pranshu jaiswal
GitHub Profile Link : https://github.com/Pranshu-jais
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):Pranshu | Contributor. Discord ID: anurag342
Approach for this Project :As mentioned above
What is your participant role? GSSoC 2024

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

This problem statement is already done by the contributors.
https://github.com/abhisheks008/DL-Simplified/tree/main/Alzheimers Detection
Closing this issue as duplicate.


Missing ec2 Image attribute in response

How to Reproduce

Create a codespace on master
Run pip install .
Use the following snippet

import boto3
from moto import mock_ec2
from pprint import pprint

@mock_ec2
def test_my_model_save():
    client = boto3.client("ec2", region_name="us-east-1")
    images = client.describe_images(Owners=["amazon"])["Images"]
    res = client.describe_image_attribute(Attribute='productCodes', ImageId='ami-03cf127a')
    pprint(res)

test_my_model_save()

Response
{'ImageId': 'ami-03cf127a',
 'LaunchPermissions': [{'Group': 'all'}],
 'ResponseMetadata': {'HTTPHeaders': {'server': 'amazon.com'},
                      'HTTPStatusCode': 200,
                      'RequestId': '59dbff89-35bd-4eac-99ed-be587EXAMPLE',
                      'RetryAttempts': 0}}

Expected
ProductCodes attributes to be returned instead of launcPermissions
Related to https://github.com/localstack/localstack/issues/7884

I will take a look at how to fix this :)

Hi @tushar5526, welcome to Moto! A PR is always welcome, just let us know if you need any help getting started.

@tushar5526 and @bblommers I can take a look at this


Db init scripts are outdated

From https://hub.docker.com/r/microsoft/mssql-server

Note Starting with SQL Server 2022 CU 14, we are updating SQL Server 2022 container images to include the new mssql-tools18 package. With the introduction of SQL Server 2022 CU 14, and in all future container images, the previous directory /opt/mssql-tools/bin will be phased out. The new directory for Microsoft ODBC 18 tools will be '/opt/mssql-tools18/bin', aligning with the latest tools offering.

Which makes these lines outdated:
https://github.com/Resgrid/resgrid-setup/blob/master/db/initdbs.sh#L2
https://github.com/Resgrid/resgrid-setup/blob/master/db/run-initialization.sh#L6

Hey @deneirgits, thank you! I've merged your fix (thank you again) and I'm working on the setup scripts right now and will have a few more fixes here shortly.


Tutorial stalls on Google Colab

Hello,
When I attempt to run the tutorial depot_preprocessing.ipynb, the step my_deepof_project = my_deepof_project.create(force=True) is extremely slow (currently has been running for 30 minutes). My assumption is that this is not the intended behavior of this code: if it is, it would be good to indicate somewhere that this step can be very time consuming (I've had 2 previous timeouts of my google colab session on this step).

https://github.com/openjournals/joss-reviews/issues/5394

The code is behaving as intended, but area computing is indeed a hotspot for potential optimization. The cell takes around 6 min to run locally on a MacBook Pro 2022, but it's indeed too slow in colab. I'll see what I can do to optimize it, and add a warning to the tutorial if I don't manage. I'll leave it open for now!


Text Sync should handle all document formats (chapter, book-chapter, book-chapter-section, book-line, poem-line, etc.)

We need to work in tandem with the development ongoing for document conversion (issue here: https://github.com/cltk/cltk_api/issues/11) to stabilize the document format and ingest it correctly into the Meteor application's Mongo database.
The current text-server-sync script does not ingest every document format.
Before move forward, we need to stabilize and specify what all document formats should look like.

Issue on the API repo here: https://github.com/cltk/cltk_api/issues/12

@lukehollis That's a great idea.
We should first decide on how the json file should look like.
That will make the document conversion process Specific.

Any changes you need to the flask API, let me know or find someone to assign, and I'll give guidance. I'm replying still to a lot of application inquiries, so can't code myself on this for the next week or so.

@lukehollis @kylepjohnson I can work on this. Let me know where to start.

I don't think we need any changes to the flask API but perhaps can build something that's flexible / somewhat agnostic of what the levels of nesting are. Thanks, @suheb. This is a complex but critical task that will involve changing the collection schema for Texts, renaming the n, book, and chapter fields to something more generalized, such as n_1, n_2, and n_3. It doesn't seems like there's content nested more than 3 levels deep, but this might change in the future, in which case we can add an n_4 or more the n_* fields to an ordered list. Thoughts/perspectives on this? Building frontend templates for more than five document formats (chapter, book-chapter, book-chapter-section, book-line, poem-line, etc.) might be simplified if we just build for varying amounts of nested content.
For book 1, chapter 2, section 3 in a response from the API that look like this:
"1":{
   "1":{
      ...
   },
   "2":{
      "1": ...,
      "2": ...,
      "3": "Quid faciat laetas segetes quo sidere terram .... etc.",
      ...
   },
   ...
},
...

we will need to create an object on the text sync like this:
{
   "n_1" : 1,
   "n_2": 2,
   "n_3": 3,
   "text": "quid faciat laetas segetes quo sidere terram",
   ...etc.
}

If there are only two levels of nested content, n_3 should be null. If there is only one, n_2 should be null.
The frontend ReadingBook.jsx, ReadingChapter.jsx, ReadingText.jsx templates should be restructured to accommodate text objects with only n_1 set, only n_1 and n_2 set, or n_1, n_2, and n_3 set.  ReadingProse.jsx and ReadingPoetry.jsx might be able to be restructured as a part of this as well.
The text-sync script will need to be updated to reflect these changes as well.
But again, I'm very open to suggestion here. I think there are a lot of good possible solutions. We can make this more complex as need be--I think the only thing to avoid is over-optimizing prematurely for use cases that are marginal and/or non-existent.

Worked together the modified collection and text sync here, but this needs further testing to ensure all content is syncing properly: https://github.com/cltk/cltk_frontend/blob/master/server/text-server-sync.js
One issue that needs more investigation is not all keys in the JSON response can be parsed as integers.

We've moved past syncing data from the text server to importing it manually one way or another, so this is ready to be closed.


Catalog that previously ran, fail with "Error with unsupported config option" error

Rancher versions: v1.6.1-rc8
Steps to Reproduce:

Add my catalog
Run the Config test 2 or Config test 3 catalogs

Results:  Error (Unsupported config option for version service: 'questions' Unsupported config option for name service: 'version' Unsupported config option for service: 'name')
These catalogs were tested for config changed in 1.5.10 and were working at that time.

Both Config Test 2/3 are invalid as expected. These catalogs are invalid as you can't put the .catalog info under the services key.
@tfiduccia Can you fix your catalogs?

I was able to fix this simply by moving .catalog out from under the services key as @deniseschannon suggested. Is there documentation on this somewhere that I've missed?


Leaf-list does not seem to work as RPC input

curl -k -u admin:admin      -H "Content-Type: application/yang-data+json"      -X POST      --data '{
        "infix-system:input": {
           "parameters": [
             "primary",
             "secondary"
           ]
       }
     }'   https://localhost:443/restconf/operations/infix-system:set-boot-order

Where the RPC is defined in:

     rpc set-boot-order {
    description
      "Set order of boot-partions";
    input {
      leaf-list parameters {
        type string;
      }
    }

Am I doing anything wrong here? When looking at the RFC it looks like it is correct.

This looks good. Before I start reproducing this locally, what is the error message that you're getting and what is the expected behavior?

{
  "ietf-restconf:errors": {
    "error": [
      {
        "error-type": "application",
        "error-tag": "operation-failed",
        "error-message": "Validation failed. Invalid input data."
      }
    ]
  }
}

Expected behavior: To be able to set a sorted leaf-list, that will be handled for the callback to work on.

I tried to reproduce this with the latest devel of everything upstream (which means also these four sysrepo-cpp patches 1 2 3 4 and a patch to rousette due to a change in error reporting format in sysrepo). In order to reproduce, I used this patch for the test suite:
diff --git a/tests/restconf-rpc.cpp b/tests/restconf-rpc.cpp
index c4229a0..68a5d33 100644
--- a/tests/restconf-rpc.cpp
+++ b/tests/restconf-rpc.cpp
@@ -123,6 +123,15 @@ TEST_CASE("invoking actions and rpcs")

             REQUIRE_CALL(rpcCall, rpcCall("/example:test-rpc-no-input-no-output", std::map<std::string, std::string>({})));
             REQUIRE(post(RESTCONF_OPER_ROOT "/example:test-rpc-no-input-no-output", {AUTH_ROOT, CONTENT_TYPE_JSON}, "") == Response{204, noContentTypeHeaders, ""});
+
+            REQUIRE_CALL(rpcCall, rpcCall("/example:test-rpc", std::map<std::string, std::string>({{"/example:test-rpc/i", "ahoj"}, {"/example:test-rpc/ll[1]", "a"}, {"/example:test-rpc/ll[2]", "b"}})));
+            REQUIRE(post(RESTCONF_OPER_ROOT "/example:test-rpc", {AUTH_ROOT, CONTENT_TYPE_JSON}, R"({"example:input": {"i":"ahoj", "ll": ["a", "b"]}}")") == Response{200, jsonHeaders, R"({
+  "example:output": {
+    "out1": "some-output-string",
+    "out2": "some-output-string-2"
+  }
+}
+)"});
         }

         SECTION("Data format")
diff --git a/tests/yang/example.yang b/tests/yang/example.yang
index 5d586a0..43ca82b 100644
--- a/tests/yang/example.yang
+++ b/tests/yang/example.yang
@@ -172,6 +172,9 @@ module example {
         type string;
         mandatory true;
       }
+      leaf-list ll {
+        type string;
+      }
     }
     output {
       leaf out1 { type string; }

...and everything worked just fine.
Could you please check whether this still happens with the following commits:

CESNET/libyang@6edf345fa
sysrepo/sysrepo@539ea145
CESNET/libyang-cpp@a1acdc79
sysrepo/sysrepo-cpp@eac5f76
rousette f730748

Note that there are some big changes in how the operational DS is implemented in these versions (which will become a release shortly).

I can confirm that it works, we can close this issue.


Lambda to poll and notify on old deploys

What is this PR trying to achieve?
Notification of out of date deploys (part 24-C).
Depends: https://github.com/wellcometrust/platform-api/pull/447

[ ] Run terraform apply.

For: https://github.com/wellcometrust/platform-api/issues/426


Include Vehicle Make and Model

The Get Vehicles route (/api/locations/{locationId}/vehicles) returns makeId and modelId. It should also return make and model, respectively.

Resolved.


Stop retrying setup on killed runs

Closes #610.
If run setup fails, Vivaria retries it, up to three setup attempts in total. However, if run setup fails because a user killed the run during setup, Vivaria doesn't notice that and tries to set up the run again. This can lead to Vivaria starting a container or pod for the run, which can take up computational resources, especially in a k8s cluster (e.g. GPUs).
This PR fixes the issue by having Vivaria check if the run's trunk branch has a fatal error before each setup attempt. If the run does, Vivaria won't attempt to set up the run.
I also added a fatal error check right in front of the point where Vivaria creates an agent container, to reduce the risk of a race condition between run killing and agent container creation.
Needing these fatal error checks indicates to me that we could afford to refactor our code somehow to avoid sprinkling them all over.
TODOs:

[x] Should we check for more than just a fatal error? E.g. what if the run has a submission? Maybe we should pull down the run's setup state?

I don't think we'll ever end up in a spot where Vivaria is trying to set up a run that already has a submission. It doesn't seem worth checking for.

[x] Is this actually checking frequently enough? Do we need to check partway through run setup, too?

Yes, seems possible for a user to kill the run, then for setupAndRunAgent to create the agent container without checking that the run wasn't killed. I'll add a fatal error check right before creating the agent container. There's still the chance of a race condition, but such a check should lower the chance.

Testing: Covered by an automated test. I've checked that the test fails on the old version of RunQueue#startRun.

Needing these fatal error checks indicates to me that we could afford to refactor our code somehow to avoid sprinkling them all over.

Opinions before I saw this PR:
https://evals-workspace.slack.com/archives/C07KLBPJ3MG/p1730644603334419?thread_ts=1730043320.033699&cid=C07KLBPJ3MG

I think we would rather keep the "branch setup state" in one place (only branches or only "runs"). If I understand the code correctly, the state is currently in "runs" (but would be better in "branch").
If we keep it in "runs", then my intuition is to add an "abandoned" state (to the "runs"), and not ask the queue to check for fatal errors in the branch
wdyt?
[please don't feel blocked by this comment]

Hmm yeah! Good point Yonatan. Maybe something like, "instead of a fatal error, use setupState = FAILED to track whether setup has failed, then on a run-ending error both record a fatal error and set the run's setup state to FAILED".
But we do also want to record a fatal error. Because we want to show users what went wrong during setup. But yeah the fatal error doesn't need to be the source of truth for whether a run has failed setup or not.

The problem is, I don't trust setupState as a source of truth. We don't have any code that sets a run's setup state to FAILED. I'm going to merge this PR as-is except I'll add a TODO.


Use iota_stronghold from crates.io

Description of change
Use the stronghold version on crates.io instead of pinning to GitHub.
Links to any relevant issues
required for #869.
Type of change
Add an x to the boxes that are relevant to your changes.

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

How the change has been tested
Built the crates locally.
Change checklist
Add an x to the boxes that are relevant to your changes.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Can we just merge https://github.com/iotaledger/identity.rs/pull/867 instead? it's going to cause problems after the crates are renamed otherwise.

Can we just merge #867 instead? It's going to cause problems after the crates are renamed otherwise.
The concern was, that we can't prove the correctness of the implementation as tracked in #868. Would you guys be in favor of merging anyways for the upcoming release?

we can't prove the correctness of the implementation

Basically the same problem with #809, I see no difference really.

we can't prove the correctness of the implementation

Basically the same problem with #809 and that was merged, I see no difference really.

@PhilippGackstatter what do you think?

I didn't have the time to check whether #867 is compatible with other crates in the ecosystem, so this was the quicker solution. Yeah, we also can't prove correctness like #809 just yet, not sure if that justifies adding more code that's not provably correct, though. But if this complicates the crate renaming somehow, I'm also fine with merging #867.

I didn't have the time to check whether #867 is compatible with other crates in the ecosystem, so this was the quicker solution. Yeah, we also can't prove correctness like #809 just yet, not sure if that justifies adding more code that's not provably correct, though. But if this complicates the crate renaming somehow, I'm also fine with merging #867.

Then let's go for that, sorry for the confusion.


Fixed RootModule bug

PR Summary
Some PS modules do not specify RootModule in their psd1.
In such cases Get-Module fills in RootModule with full path to psd1, which is misleading for discovering class-based resources.
This was causing internal failures in PsDscAdapter.
This PR fixes that with explicit check for such condition and adds some tracing to make diagnostics easier.

What about cases where people split their module code without using NestedModules?
For example, the pattern built by the DSC Community has base classes etc defined in a sub-module and has using/import statements to retrieve the code:

SqlServerDsc root module
SqlServerDsc module manifest

What about cases where people split their module code without using NestedModules?
For example, the pattern built by the DSC Community has base classes etc defined in a sub-module and has using/import statements to retrieve the code:

SqlServerDsc root module
SqlServerDsc module manifest

strictly speaking this is out of scope of this particular bug;
I've looked through the PSAdapter code and your example module; and looks like such cases should be handled just fine when...
... class-inheritance will be implemented.
Thanks for a good example module; that will help with development.


Add ability for multiline key to be a function.

This allows you to do more dynamic items such as two new lines for end of input, and any other number of things.
Example https://gist.github.com/blainesch/b6c0a3f188ec306c6940

Sorry for the delay, I have been on holiday, should be back at work in about a week and will review/merge then.
Thanks!

Apologies, manually merged in 1af5be6b168ddac77e728e49c5155aaec732018d available in 0.1.12.

Thanks!


Get stopServer{Graceful,Immediate} to pass mocha tests

These 2 test cases in server.spec.ts are currently disabled via xit because they are failing.  Fix them so that they pass.

I've got these working on my development system (MBP x86 with macOS 14.2.1), but CI seems to be having issues on the same OS, but others are passing.

Increasing the time it takes for the server to process a signal from up to 1 second to up to 2 seconds resolved the issue with macOS 14.


Vertical X axis labels

I have rather long strings as the labels for each X value, and they are currently tilted and getting cut off. Is there any way to have them vertical and show the full string?

Plotly Express sets the automargin flag in the underlying Javascript library which tries to leave room for labels but if they would take up more than 50% of the side of the figure it gives up... If you labels are really extremely long you could try increasing the size of your figure?


Client Allocation Request for: Taiwan Envionmental Information Center

Client Allocation Questions
Core Information

Name: Taiwan Envionmental Information Center
Website / Social Media: https://e-info.org.tw/about
Region: Asia excl. Greater China
DataCap Requested: 15TiB
Addresses to be Notarized: f1zlmlnspyivvevewh7hqfx4g7y3yc4z44unfcwei
Notary Requested: ozhtdong

@harrissss3 Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Thanks for your application. I have some questions about you and your company:
1.What's your name? What's your position?
2.What's your company's business? Do you have any other social media link?
3.Could you show me your company's business license?
4.How many miners do you want to store your data to? How much data for each miner?
5.Will you record your allocation decision in public? Which platform will you use?
6.What method/tool will you use to inspect miners? Which aspect of miners will you inspect?

My name is Anna, I am the community editor of my company
Environmental Information Center is a non-profit online media. Since 2000, we have been providing comprehensive environmental coverage domesticly and abroad. We hope to make voice for the mountains, seas and lands that have no votes.
Will send an email
We want to have 5 miners, and provide the miners more data who have faster network
Yes decisions will be public on github.
Filfox, miners with fast internet

Request Approved
Your Datacap Allocation Request has been approved by the Notary
Message sent to Filecoin Network

bafy2bzacecajf3m246byhiy4txkydrejvjc7akm2mk6wmuk7wr7zj5p6wwbcu

Address

f1zlmlnspyivvevewh7hqfx4g7y3yc4z44unfcwei

Datacap Allocated

NaNB

Signer Address

f1lwpw2bcv66pla3lpkcuzquw37pbx7ur4m6zvq2a

You can check the status of the message here: https://filfox.info/en/message/bafy2bzacecajf3m246byhiy4txkydrejvjc7akm2mk6wmuk7wr7zj5p6wwbcu


Use the USERPROFILE environment variable for Windows users.

I'll see if I can open a pull request to solve this.

https://github.com/jlvihv/BingGPT/pull/2

I'll have to implement a few more changes before this PR can be merged.

This is the first PR I have received, pleasant experience, thank you very much, have merged.


fix(isolated-declarations): accidentally collected references of original ast

#6102  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


Sighup handling, including integration with --compile-table.

I believe this has partly been done by @dpino, but this depends on https://github.com/Igalia/snabbswitch/issues/151 to do fully.

Done, quite a while ago.  If there are bugs, let's open new tickets.  See additional comments on #151.


Naming convention warnings from Graal's native-image

Graal's native-image (v1.0.0-rc14) issues some warnings when compiling scalameta (v4.1.4 with Scala 2.12.8):
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$XtensionMySyntacticInfo$1;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$XtensionMySyntacticInfo$1; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$ValidityState$1;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$ValidityState$1; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$OperatorState$1;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$OperatorState$1; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Accepted$1$;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Accepted$1$; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Valid$1$;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Valid$1$; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Invalid$1$;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Invalid$1$; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Forbidden$1$;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Forbidden$1$; which is not following the naming convention.
warning: unknown locality of class Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Required$1$;, assuming class is not local. To remove the warning report an issue to the library or language author. The issue is caused by Lscala/meta/internal/prettyprinters/TreeSyntax$syntaxInstances$1$Required$1$; which is not following the naming convention.

Steps to reproduce:
wget -O sireum.jar http://files.sireum.org/sireum
native-image -jar sireum.jar

Thanks for reporting! This looks like a native-image regression, it was working before v1.0.0-rc14. Please report to the GraalVM team.

I'm happy to merge a PR fixing this issue, if you are interested in taking a stab at this @robby-phd


Check that we got the expected name type when verifying name constraints

If a SAN field contains an SmtpUTF8Mailbox name then it is expected to
have a UTF8String type. We should verify that it really does before we
attempt to use the value in it.
Reported by Corey Bonnell

This pull request is ready to merge

Pushed. Thanks.

After expiration of test/certs/bad-othername-namec.pem on Jul  2 13:42:35 2021 GMT,
the negative test case will succeed for the wrong reason and thus become useless.
I'll fix this by adding -attime<PHONE_NUMBER>.

Should we really do this check without -x509_strict?
So far, we don't do inessential X.509 well-formedness checks without it.

After expiration of test/certs/bad-othername-namec.pem on Jul 2 13:42:35 2021 GMT,
the negative test case will succeed for the wrong reason and thus become useless.
I'll fix this by adding -attime<PHONE_NUMBER>.

Good idea.

Should we really do this check without -x509_strict?

I'm not sure why we need it for this test? It should fail without "-x509_strict".

Should we really do this check without -x509_strict?
So far, we don't do inessential X.509 well-formedness checks without it.

I'm not sure why we need it for this test? It should fail without "-x509_strict".

I actually meant the check implemented in the lib.
This check, and thus also the new test case, is (so far) independent of X509_V_FLAG_X509_STRICT / -x509_strict.

I see many instances of X509_V_ERR_UNSUPPORTED_NAME_SYNTAX without any reference to X509_V_FLAG_X509_STRICT. This seems correct to me.


Fix issue #684 Bug in project.json file

Related Issue
fix issue number #684
fix json file as the teck key value was not correct (due to which some project was not showing when doing sorting) and also updated contribute.md file so people can follow same naming convention when writing their tech name
as you can see localhost project

and deploy project their is change in number of project

and same goes for other tech

run pnpm format to fix formatting issue

do i need to run it on my code locallay and then again create a pull request as i did run it before creating pr

do i need to run it on my code locallay and then again create a pull request as i did run it before creating pr

have you created PR directly from github?

yes

yes

then don't need to run in locally I'm merging

okay good

can you tell difference between pr directly from github and from vs code iguess?

can you tell difference between pr directly from github and from vs code i guess?

simple you solved a problem & created PR directly from github & you used GUI for vs code: you cloned it in your local system, fixed problems & pushed your code using CLI


use notion as a backend

Implemented the thing we have talked about for a while now.
Delving into react was pretty fun although the layers of abstraction gave me several headaches
benefits of using notion as a backend:

very easy to edit for non-technical executive members
low update latency since updates are not dependent on a single person
hopefully less downtime since there is a caching layer between notion and the website that is a simple json file
easier to maintain assuming that notion doesn't go bankrupt
it becomes effectively free to add/modify/delete columns and its very easy to store additional data (the new api already provides a lot more than the current route)

Issues:

obviously it is extremely reliant on our continued use of notion
I took the hackathon approach of implementing this, which is to say that I tore away at the existing code until finding a solution that worked - I'm getting a lot of errors on my localhost console that probably shouldn't be pushed to prod
one more api gateway to maintain because I don't know how to code in C# and also there is no notion sdk for C#

and of course this pull request is dependent on https://github.com/langaracpsc/notion-web-api


The receipt image is not displaying on the confirmation modal

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @ayazhussain79
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697631191229619
Action Performed:

Open a chat.
Go to Request money > Manual.
Enter an amount and proceed to the next step.
Click on the three-dot menu and upload a receipt.
Notice that the receipt is not showing on the confirmation modal

Expected Result:
he receipt image should be displayed on the confirmation modal
Actual Result:
The receipt image is not showing on the confirmation modal
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/93399543/eb75412c-64cb-4975-8ed4-ae1467007ba7

Android: mWeb Chrome

https://github.com/Expensify/App/assets/93399543/e6c4d640-6fdd-4cfe-b1dd-b5bb3b3905d7

iOS: Native

https://github.com/Expensify/App/assets/93399543/df6d0091-5084-434a-a0dd-4c748e33b1ea

iOS: mWeb Safari

https://github.com/Expensify/App/assets/93399543/113616c9-5607-4532-bc1e-ac9d3e1cfdd0

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/93399543/c160a41b-4146-4693-9ac7-6b0e7ac97cbc
https://github.com/Expensify/App/assets/93399543/75ac876c-a41e-4229-8420-9961ac853e05

MacOS: Desktop

https://github.com/Expensify/App/assets/93399543/66f33e3f-a312-488f-a754-0ee6879dda19

View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

This seems a duplication of https://github.com/Expensify/App/issues/29855

@cristipaval agreed - do you want to grab this issue, or should I just close it?

I think we can close this one, we already have an accepted solution for the other issue.

got it, closing!


Section 05 - Conclusions

https://github.com/Reproducible-Science-Curriculum/organization-RR-Jupyter/blob/gh-pages/_episodes/05-conclusion.md

[x] Actually add content
[ ] First pass of comments

Updated this episode, though currently it is not very long and mostly recaps what has already been covered. LMK and we can start iterating from here.


@motocycle/history

API needs to be discussed and split into issues

I think I'm mostly in favor of creating a component that takes a single stream in of different shaped objects, with the help of a DSL to make it nicer to work with. Something like
import { History, push, replace, go } from '@motorcycle/history'

function Effects(sinks) {
  const { location$ } = History(sinks)

  return { location$ }
}

function App(sources) {
  ...

  // push calls history.pushState()
  const history$ = constant(push('/login'), isUnauthorized$)
  // replace calls history.replaceState()
  const history$ = constant(replace('/path'), stream)
  // go calls history.go()
  const history$ = constant(go(-1), stream)
}


Add depth, no_tags, and filter options to import_from_git action

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.
[x] I've added or updated relevant unit tests.

Motivation and Context

Description
This pull request enhances the import_from_git action by adding three new options:
depth: Allows performing a shallow clone with a history truncated to the specified number of commits.
no_tags: Enables cloning without tags.
filter: Provides a filter to include only specific types of objects in the clone.
These options provide more flexibility and control over the cloning process, making it easier to manage large repositories or specific use cases.
Testing Steps

@KrauseFx Please review pull request.

I think we can specify the tag from which to import the code


Keep at least one thread in the pool of the "old file cleaner"

Otherwise newThread of the pool will be executed constantly, which will bring the CPU to 150%.
Closes #299

+1

Thanks Jesse, will merge when Travis passes.

Many Thanks :-)


Support Carthage

Context
Some developers might build a macOS app that leverages xcodeproj. To make the integration easy, you could support Carthage from xcodeproj. Compared to CocoaPods Carthage provides more control for developers and less version screw ups.
What
Support Carthage (dynamic framework necessary)
Proposal
Create xcodeproj as a framework to support Carthage

This would require Carthage adding support for Swift PM packages. There's an open PR for that https://github.com/Carthage/Carthage/pull/1945
The other option is to check in a custom xcode project. I'm not sure that carthage is compatible with the one that Swift PM generates (hence the trouble in the above PR), otherwise we'd have to do it ourselves. Maybe we can dog-food https://github.com/yonaskolb/XcodeGen and use that to generate the project

Would we build a circular dependency if we use XcodeGen? :trollface: @yonaskolb.

I don't think we can reuse the project that gets generated by SPM. I think we should automate the process of generating that project, and XcodeGen is the best candidate to do that.

We'll work on this @olbrichj, great idea 😛

We'll work on this for the next version, 0.1.3

sounds great 👍

I think generating Carthage compatible xcodeproj is too much for this core library.
Shouldn't this feature be outside of xcproj?
I think xcproj should focus on providing API to access xcodeproj related files.

I guess it was proposed because we also support CocoaPods. I was thinking about two options:

Either not gitignoring the SPM project and see if Carthage can use that to generate the framework.
Use XcodeGen to automate the creation of the Carthage project and generate it as part of the release process.

What do you think @toshi0383 ?

Oh I understood.
I think second option is better and safer. SPM generated one can lose Carthage compatibility in future, even if it was compatible now.

Either not gitignoring the SPM project and see if Carthage can use that to generate the framework.

I confirmed in version Swift 4.0.0-dev (swiftpm-13126) and it is not Carthage compatible.
It's even missing Info.plist.
executable $ tree
.
├── Package.swift
├── README.md
├── Sources
│   └── executable
│       └── main.swift
├── Tests
└── executable.xcodeproj
    ├── project.pbxproj
    ├── project.xcworkspace
    │   ├── contents.xcworkspacedata
    │   └── xcuserdata
    │       └── a14786.xcuserdatad
    │           └── UserInterfaceState.xcuserstate
    ├── xcshareddata
    │   └── xcschemes
    │       ├── executable-Package.xcscheme
    │       └── xcschememanagement.plist
    └── xcuserdata
        └── a14786.xcuserdatad
            └── xcschemes
                └── xcschememanagement.plist

Oops, sorry it was executable type, not library.

Cool! Would you like to tackle this @toshi0383 ?

Hmm maybe not right now. wish I had time to do this.


Popover border overlaps arrow when placement is top in some resolutions

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
This is similar to https://github.com/twbs/bootstrap/issues/38200, but I opened a new ticket since it's somewhat more urgent. I noticed that the popover border overlaps the arrow on my wide monitors at work and at home, though it works correctly on my macbook built-in display. My home monitor is set to 1920x1080. Scaling to 960x540 causes the issue to resolve.
I have a different laptop running ArchLinux with Wayland compositor. I attached this machine to the same monitor, and the issue did not appear in my chromium browser. Just mentioning as it seems like it's not necessarily just the resolution or monitor. Though the issue appears in the more normal configuration using the macbook. Unfortunately I don't have other devices around for testing.
Attached screenshot of the defect:

Reduced test cases
Visit https://getbootstrap.com/docs/5.3/components/popovers/#four-directions and click the Popover on Top button on a display set to resolution 1920 x 1080, connected to a macbook pro.
What operating system(s) are you seeing the problem on?
macOS
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.3.2

I have tried in macOS external display set to 1920x1080 chrome with version 5.3.2 but not it's not overlapping for me.
Have you tried anything else ?


[BUG] BoringSSL: error:10000438 when making several requests asynchronously in threads to the same site

**### https://<IP_ADDRESS>:4443/remote/login |Failed to perform, curl: (35) BoringSSL: error:10000438:SSL routines:OPENSSL_internal:TLSV1_ALERT_INTERNAL_ERROR. See https://curl.se/libcurl/c/libcurl-errors.html first for more details.
https://<IP_ADDRESS>:4443/remote/login |Failed to perform, curl: (35) BoringSSL: error:10000438:SSL routines:OPENSSL_internal:TLSV1_ALERT_INTERNAL_ERROR. See https://curl.se/libcurl/c/libcurl-errors.html first for more details.**

`
options = {
    CurlOpt.SSL_VERIFYHOST: 0,
    CurlOpt.SSL_VERIFYPEER: 0,
    CurlOpt.TLS_KEY_USAGE_NO_CHECK: 1
}
async with AsyncSession(impersonate=BrowserType.chrome, curl_options=options,
                        timeout=300, verify=False,
                        # proxy="http://<IP_ADDRESS>:8080",
                        ) as session:
    res = await session.get(link)

    **it comes out when I make several requests asynchronously in threads to the same site
    For example if aiohttp use force_close = True in the connector, it helps. What should I do here?**

See my comments on #319.


Repo sync for protected CLA branch

The pull request is created from master637365638843261738 to master to fix git push error for protected CLA branch

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


refactor: refactor policy check code, add withPassword enhancer, fix tests

A few plugins are treated as builtin and don't need to be explicitly configured in ZModel:
@zenstack/prisma, @zenstack/model-meta, @zenstack/access-policy.
Model meta and policy code are, by default, generated into node_modules/.zenstack


Signing in Chrome on Windows PC

Home Assistant release with the issue:
0.80.3
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):
hassbian on Rpi
Component/platform:
hassbian
Description of problem:
Since I have a local home assistant user in place I noticed I can't sign in proper. Signing in on cell or tablet gives no issues, but when trying signing in on Windows PC using Chrome, I on average have to sign in 5-8 times before I can proper sign in to it.
Tried:
deleted the cookies
flushing DNS
tried adding local ip to \hosts file in windows folder
used incognito chrome (gives the same number of signing in before I can get one time correct signing in)
tried Firefox
reboot Pi

This is the bug/issue tracker for Home Assistant. Please use the forum for questions about installation, setup, configuration and usage.
If it's a bug, please re-open the issue with the issue template filled.


set required endDate

This change is

Coverage increased (+0.02%) to 92.672% when pulling 4a9d39c11e41b070d20982baf64e2840fa4d3936 on VolVoz:master into cfe219d46683ef46873d363f7bc610e9a705df83 on openprocurement:master.


Test out tofu curry

holy heck I'd like to eat some right now

Absolutely delicious, but needed more salt


Hermes support Android 15

Change Type (required)
Indicate the type of change your pull request is:

[ ] patch
[ ] minor
[ ] major

Does your PR have any documentation updates?

[ ] Updated docs
[ ] No Update needed
[ ] Unable to update docs

📦 Published PR as canary version: 0.9.1--canary.509.17499

Try this version out locally by upgrading relevant packages to 0.9.1--canary.509.17499

/canary

/canary

/canary

/canary


⚠ Secret Website 3 has degraded performance

In 0f90dfe, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2956 ms

Resolved: Secret Website 3 performance has improved in 78b4fdd.


[FLINK-9654] [core] Changed the check for anonymous classes to avoid InternalError

What is the purpose of the change
This pull request avoids triggering SI-2034 for Scala classes that are defined inside of Scala objects. The issue will be fixed only when Scala is will be officially supported by Java 9, as, after all, it's fixed in Java 9: https://bugs.openjdk.java.net/browse/JDK-8057919.
As explained in FLINK-9654, whenever there is a custom TypeSerializer implementation that, when serialized, has in its object graph a reference to a class that triggers SI-2034, it makes the task manager instance fail, potentially bringing down the entire Flink cluster.
Brief change log

made the classname-related checks happen before the call to Class.isAnonymousClass, after all, there is no reason to call it if we can know it just by looking at the class name;
added the check for "$macro$" in the name checks, as, after all, macro-generated classes are always anonymous;
wrapped the call to isAnonymousClass into a try-catch block, to catch the InternalError that the issue might trigger.

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
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

It would be great if somebody could help me understand what went wrong with the tests. I tried running the same tests locally (kafka connector-related tests), but they pass for me. Is this some kind of instability?

hi @zsolt-donca I have seen the Travis build error log, the failed reason is not because of your code. This PR looks good, but if you can add a test for isAnonymousClass method, that would be better.
cc @tillrohrmann

Thanks for looking into this @zsolt-donca.
The changes looks good to me, but as @yanghua mentioned, a test to cover the previous bug would be nice here and allow the reviewer to understand directly that it is a required fix.

Thanks for the review! I will update the MR with tests covering the bug.

@zsolt-donca I actually added some test to my branch https://github.com/tillrohrmann/flink/commits/FLINK-9654. If this should cover your fix, then I could merge your PR with this test. What do you think?

@tillrohrmann looks good to me. The class Foo.Bar.Foobar should trigger the issue. Thanks for writing the test!

Glad to hear. Then I will merge your PR with this test. Thanks for fixing this problem @zsolt-donca.


Playing out of fullscreen

This plugin is awesome but can the player not be triggered on full screen alone as many of us will like to give our users the options to go fullscreen or not. an instance is to be able to put a livechat below the player so while a stream is on, our users can interact. please is there a solution for that?

This should create a player control in a div where you can do more stuffs with the app, not just listen to music/video.

Does anyone have a workaround for this feat?

@acetechnology @GuilhermeSanches There was a modified version of this plugin just to handle this feature. It was available on Github but account does not exist anymore. link to npm

yeah, i did it. lol
On Fri, May 26, 2017 at 3:06 PM, M Nauman Rafique<EMAIL_ADDRESS>wrote:

@acetechnology https://github.com/acetechnology @GuilhermeSanches
https://github.com/guilhermesanches There was a modified version of
this plugin just to handle this feature. It was available on Github but
account does not exist anymore. link to npm
https://www.npmjs.com/package/cordova-plugin-streaming-media-mod
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nchutchind/cordova-plugin-streaming-media/issues/74#issuecomment-304291147,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALDDGmAJZxxE2owJdftLdpOiIgKmRkE2ks5r9tx2gaJpZM4Jqn2A
.

it's ultimately unnecessary. if you want inline video you can use html5 or the handful of other video plugins.


Password

Is there any way to put password on the db file?

Yes:
https://github.com/mbdavid/LiteDB/wiki/Connection-String

@ftamminga Thank You. :)