Error Message

The line that says "In case of a failure while publishing, the status will change to failed with an appropriate error message" should be amended to say "In case of a failure while publishing, the status will change to failed with an completely useless error message". Seriously though, the error message just tells me that there is an error and to contact support with a correlation id.

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

ID: 4c31b388-68fd-649d-eb12-37c94fa6793c
Version Independent ID: a590f5fc-c426-ef66-a3c5-732928325347
Content: Publish applications to Intune Company Portal - Visual Studio App Center
Content Source: docs/distribution/stores/intune.md
Service: vs-appcenter
GitHub Login: @pnghub
Microsoft Alias: gned

@brimmy11 thank you for the feedback; I've asked @gaknoll to review your comment.

Hi @jwargo @gaknoll , I didn't really expect to be taken seriously but since I have an audience let's address it. Below is an error we (my scrum team) are receiving when attempting to publish an application from App Center to Intune.
One of my colleagues is already in contact with App Center support to understand the details of the error so I do not require support with that. My comment was around the documentation not being accurate.

@brimmy11 we're committed to making App Center the best tool it can be, so your feedback is greatly appreciated. I agree that the error message doesn't tell you a lot, so we can definitely make things better (assuming that we have additional information about the error that we can share). It could be that we don't know much beyond what we've told you, but I'm going to have to let @gaknoll  answer that one. Please keep the feedback coming.

@brimmy11 sorry for the delay in getting back to you. We greatly appreciate the feedback and I'll be working with our Stores integration team to improve the Intune documentation to be more accurate and useful. I hope our support team was able to help you resolve the error though!


What does it mean output of record_measurments.py ?

I have data but what does [XXX] blocks mean in output.txt file from record_measurments.py ?

See iter_measurments docs. It should be strength of reflected light, though I am not sure why you get such uniform values.

I found in iter_measures() function in rplidar.py file.
Yields
------
new_scan : bool
True if measures belongs to a new scan
quality : int
Reflected laser pulse strength
angle : float
The measure heading angle in degree unit [0, 360)
distance : float
Measured object distance related to the sensor's rotation center.
In millimeter unit. Set to 0 when measure is invalid.
'''


Schema discussion draft

What's changing
Initial proposal for schema handling
How to test it
Related Jira Ticket
Additional notes for reviewers
I already...

[ ] added some tests for any new functionality;
[ ] updated the documentation.

You can generate a sample OpenAPI schema using
pants run lumigator/python/mzai/schemas/openapi.py:schemas_sources@parametrize=darwin

We can discuss what pieces would still be missing in here (mainly the endpoints) and how to get them more or less automatically from live inspection.

Obsolete.


Could not open database file (target android 10)

My test device is a galaxy A51 (android 10)
If I target android 10 in my app, creating a new sqliteconnection(path) throws.a "could not open database file" exception.
If i target android 9 in my app and run on the same galaxy A51 device, it works.
Are there any plans to support android 10?

It appears this issue has to do with the introduction of new access permissions introduced in android 10. So this is something i gotta figure out how to implement.


should support specify which folders can be synced back

There are cases that we need to ignore auto-generated stuff (node_modules, bower_componets, vendors) to be synced into the VM.
But we'd like to check its source code into the host machine.
Currently, we must gen these stuff on the host machine (which again require the host machine to install dependent packages to do so, which is against our intention: the host should be minimal as possible).
If there's a way to allow this situation, it's great. This will boost productivity a lot.
related: https://github.com/smerrill/vagrant-rsync-back/issues/6

this is the extension feature since v0.6, so it's not relevant anymore, close now.


is it impossible to run task each 3 min ?

i need this jop to run on each 3 min but the problem it don't . it run on each min this is the log of the time
Fri Aug 02 20:21:04 GMT+03:00 2019
Fri Aug 02 20:22:01 GMT+03:00 2019
Fri Aug 02 20:23:49 GMT+03:00 2019
Fri Aug 02 20:24:41 GMT+03:00 2019
Fri Aug 02 20:25:22 GMT+03:00 2019
Fri Aug 02 20:26:23 GMT+03:00 2019
Please advice
and as i understand
.setTrigger(Trigger.executionWindow(WhenStart, HowlongitRmemain))
so: WhenStart you can set it 20, and HowlongitRmemain is the time before service call again.
But any numbers you add - no mater - it will start each min.
android O
Job job = dispatcher.newJobBuilder()
//persist the task across boots
.setLifetime(Lifetime.FOREVER)
//.setLifetime(Lifetime.UNTIL_NEXT_BOOT)
//call this service when the criteria are met.
.setService(MyJobService.class)
//unique id of the task
.setTag("UniqueTagForYourJob")
//don't overwrite an existing job with the same tag
.setReplaceCurrent(false)
// We are mentioning that the job is periodic.
.setRecurring(true)
// Run between 30 - 60 seconds from now.
.setTrigger(Trigger.executionWindow(20 , 300))
// retry with exponential backoff
.setRetryStrategy(RetryStrategy.DEFAULT_LINEAR)
//.setRetryStrategy(RetryStrategy.DEFAULT_EXPONENTIAL)
//Run this job only when the network is available.
//  .setConstraints(Constraint.ON_ANY_NETWORK, Constraint.DEVICE_CHARGING,Constraint.DEVICE_IDLE)
.build();
        dispatcher.mustSchedule(job);

Its quite simple
just replace
.setTrigger(Trigger.executionWindow(20 , 300))
with
.setTrigger(Trigger.executionWindow(180, 180))
this execution window is a time range (in seconds) to trigger this job.
180 means 3 minutes here.

In April 2019 we announced that Firebase Job Dispatcher would be deprecated today, April 7th 2020.  For this reason we are going to close all open issues and archive the repository.  We will also stop supporting FJD for new app installations (such as those targeting sdk versions greater than Android Q).  Existing apps that rely on FJD should continue to function as usual.
While we will no longer work on FJD, we encourage you to migrate to Work Manager which is a superior tool and fully supported by the Android team.
Thank you for taking the time to try the library and provide this feedback.  We sincerely appreciate your effort and we apologize for not addressing it in time.


Support for TVOS or OSX?

Could we add support for these in the podspec?

Sure thing. Have you tried to see if there are any errors when running on tvOS and OS X?
If so, do you want to open a pull request?

Sure thing. Have you tried to see if there are any errors when running on tvOS and OS X?
If so, do you want to open a pull request?

I wrote an OS X support at https://github.com/aschuch/AwesomeCache/pull/53
Please check it! 🙏


Documentation for new modules added in 3.0.0

Documentation for these modules is missing from docs/modules.

ingress
xquic
xudp

xquic:
http://tengine.taobao.org/document_cn/xquic_cn.html
https://github.com/alibaba/tengine/blob/master/modules/ngx_http_xquic_module/README.md
xudp:
http://tengine.taobao.org/document_cn/xudp_cn.html
ingress:
http://tengine.taobao.org/guide_cn.html

@drawing Will you copy the documentation on tengine.taobao.org to this repository?

Except for xquic compilation documents, other documents are already on the official website. At present, the official website does not have compilation documents for specific modules. Putting them in the module readme may be more friendly to users who compile the module. And more closely matches the version.


cloud-779 update eap sso templates for sso quickstarts

Hey @bdecoste, can you push the examples into jboss-openshift/openshift-quickstarts and reference those, as opposed to your personal repository?

The personal repo is only temporary. The KC team is creating a 7.0.x-ose branch under https://github.com/redhat-developer/redhat-sso-quickstarts. I am going to make the required changes there and use that. I've opened RHSSO-379,380,381 so we can use a tag off of the master branch once completed.


Sort out all the dependabot alerts

I don't think any of these are actually valid attack vectors for the app but worth bumping the up as you go if they pass the CI check

Almost all CRA spam


Q: Does this actions support major.minor.patch.release format?

Does this actions support major.minor.patch.release format?
Thanks, Vitaly

No


Refactoring the source code structure

@cortze hope this patches kind of make it so now this meets your criterion on how a golang project's source code should be structured.

I also fixed a little compilation error I didn't catch at the time oops...


gunpowder.Stack only output a single random image

I am trying to use the gunpowder.Stack class to request a stack of random images from the source (saying 5).
The returned image stacks always have one new random image appended on the previous batch request. (saying 4 old images + 1 new image).
To reproduce the issue:
source = gp.ZarrSource(
    pathZarr,
    {
      raw: 'tr/tr000',
      gt: 'gt/gt000'
    },
    {
      raw: gp.ArraySpec(interpolatable=True),
      gt: gp.ArraySpec(interpolatable=False)
    })

pipeline = (
    source
    + gp.RandomLocation()
    + gp.Stack(5)
)

request = gp.BatchRequest()
request[raw] = gp.Roi((0, 0), (256, 256))
request[gt] = gp.Roi((0, 0), (256, 256))

with gp.build(pipeline):
    for i in range(3):
        batch = pipeline.request_batch(request)
        imshow(batch[raw].data, batch[gt].data) # custom plot function

The image shows outputs from batch requests:

# custom imshow function
def imshow(*args, n=5, figurezize=(10, 4)):
    num_args = len(args)
    plt.figure(figsize=figurezize)
    for row_idx, image_set in enumerate(args):
        image_set = np.array(image_set)
        n = min(n, image_set.shape[0])
        for col_idx in range(n):
            ax = plt.subplot(num_args, n, row_idx * n + col_idx + 1)
            plt.imshow(image_set[col_idx])
            plt.axis('off')
    plt.show()

``Temporary (?) solution
Keep the batch request in the for loop should solve the problem.
e.g.,
with gp.build(pipeline):
   for i in range(3):
        request = gp.BatchRequest()
        request[raw] = gp.Roi((0, 0), (256, 256))
        request[gt] = gp.Roi((0, 0), (256, 256))
        batch = pipeline.request_batch(request)
        imshow(batch[raw].data, batch[gt].data) # custom plot function

This has been solved: https://github.com/funkelab/gunpowder/commit/dfde284bde5420e206db9ba99795514aa1cd2fe4


Migrate to jakarta

My approach here was iterative:

Just migrate to jakarta -- circle CI didn't work and I couldn't even get builds to run
Copy over all of the gradle config from a recent highline-generated service
Get it building without palantir network connection by removing things it couldn't find and comparing to metric-schema (another open-source palantir repo)
Get tests building and running -- including upgrading the library that does the generation

Run the policy mr. policy bot!

Run again!

Released 0.13.0


Provide an extension method to add Telemetry with no Config

Fixes #1763

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1


PX4 on STM32F4Discovery

I like to port the PX4 on STM32F4Discovery manual
https://pixhawk.org/modules/stm32f4discovery#flashing_the_px4_bootloader
to http://dev.px4.io/
But therefore I like to get this thing again working ;-)
I am trying to get the STM32f4Discovery working with the actual bootloader/firmware
I am working on linux.
Bootloader is builded successfully, and flashed via stlink (red led is flashing after each reset)
Firmware is builded successfully with make px4-stm32f4discovery_default
but with the additional update to load the firmware with the bootloader doesn't work:
[ 98%] uploading /home/stefan/src/firmware/build_px4-stm32f4discovery_default/src/firmware/nuttx/nuttx-px4-stm32f4discovery-default.px4 Loaded firmware for 63,0, size: 350212 bytes, waiting for the bootloader... If the board does not respond within 1-2 seconds, unplug and re-plug the USB connector
=> here it stops, even If I press the black Reset Button and the red led starts flashing
The Board is connected over the two USB Cables
The bootloader usb port is visible as /dev/ttyACM0 and the stlink as /dev/ttyUSB0
So I tried also to flash the firmware with:
firmware/Tools $ python ./px_uploader.py --port /dev/ttyACM0 ../build_px4-stm32f4discovery_default/src/firmware/nuttx/nuttx-px4-stm32f4discovery-default.px4  Loaded firmware for 63,0, size: 350212 bytes, waiting for the bootloader... If the board does not respond within 1-2 seconds, unplug and re-plug the USB connector.
=> here it stops, even If I press the black Reset Button and the red led starts flashing
The stlink:
[ 6119.725240] usb 1-2: new full-speed USB device number 58 using xhci_hcd [ 6119.910477] usb 1-2: New USB device found, idVendor=0483, idProduct=3748 [ 6119.910486] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
The bootloader usb port:
[ 6236.379183] usb 1-1: new full-speed USB device number 62 using xhci_hcd [ 6236.564315] usb 1-1: New USB device found, idVendor=26ac, idProduct=0001 [ 6236.564331] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 6236.565453] cdc_acm 1-1:1.0: ttyACM0: USB ACM device

Try to read the Tools/px_uploader.py script and see if it locks out the Disco board through PID / VID or something else.
Can I have the output of lsusb with verbose flag?

It was a permission problem to acces /dev/ttyACM0  ;-)

firmware/Tools $ sudo python ./px_uploader.py --port /dev/ttyACM0 ../build_px4-stm32f4discovery_default/src/firmware/nuttx/nuttx-px4-stm32f4discovery-default.px4
Loaded firmware for 63,0, size: 350212 bytes, waiting for the bootloader...
If the board does not respond within 1-2 seconds, unplug and re-plug the USB connector.
attempting reboot on /dev/ttyACM0...
if the board does not respond, unplug and re-plug the USB connector.
attempting reboot on /dev/ttyACM0...
if the board does not respond, unplug and re-plug the USB connector.
Found board 63,0 bootloader rev 5 on /dev/ttyACM0
ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff ffffffff type: ÿÿÿÿ
idtype: =FF
vid: ffffffff
pid: ffffffff
coa: //////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////8=
sn:<PHONE_NUMBER>31471432383435
chip: 10016413
family: STM32F40x
revision: Z
flash 1032192
Erase  : [====================] 100.0%
Program: [====================] 100.0%
Verify : [====================] 100.0%
Rebooting.


Cut the whale of the changelog into manageable pieces?

The changelog page is very long:

https://docs.python.org/dev/whatsnew/changelog.html

It's currently 219,974 words, that's longer than Moby Dick (212,794 words)... 🐳
It contains all the NEWS entries back to Python 3.5.0 alpha 1 (February 8, 2015).
It loads okay on deskstop, but my phone struggles to render it, and the browser hangs when trying to search for text.
I tried to check the accessibility report using Google's PageSpeed Insights:

https://pagespeed.web.dev/analysis/https-docs-python-org-dev-whatsnew-changelog-html/9zu7fhwlzu?form_factor=mobile

It shows good initial numbers:

But the rest of the report is missing: "Oops! Something went wrong. generic::deadline_exceeded: Render timeout received in extension."

Shall we break the changelog page into smaller, more manageable chunks?

Right now, the changelog.rst page includes the NEWS file:
.. _changelog:

+++++++++
Changelog
+++++++++

.. miscnews:: ../build/NEWS

https://github.com/python/cpython/blob/3d5df54cdc1e946bd953bc9906da5abf78a48357/Doc/whatsnew/changelog.rst
The NEWS is compiled by blurb from the individual release files in https://github.com/python/cpython/tree/main/Misc/NEWS.d:
Building NEWS from Misc/NEWS.d with blurb

https://github.com/python/cpython/blob/3d5df54cdc1e946bd953bc9906da5abf78a48357/Doc/Makefile#L50-L66

I think splitting to major versions at least makes sense (so potentially /changelog/3.13.html, akin to /whatsnew/blah.html?)
There's an argument to break further, to e.g. a page per micro release, but I think that would inder Ctrl-F searching within each version.
a

This was discussed at the Feb 2024 docs meeting: https://github.com/python/docs-community/blob/main/docs/monthly-meeting/2024-02.md
The general consensus was that splitting the changelog makes good sense. Let's add to March 2024 agenda for next steps.

There's an argument to break further, to e.g. a page per micro release, but I think that would inder Ctrl-F searching within each version.

There is also a form to filter changes, so that people can easily enter the name of a module/function and see all the changes that affected it.  This was broken and got fixed recently in:

python/cpython#115324

For this specific use case, having everything on one page is convenient, but if we kept at least the last 3 versions on a single page, it would probably be good enough.  By doing this we could reduce the overall size to ~1/3.

When I use the changelog, I use Ctrl+F to look for the history of a function or feature. On the detail/noise spectrum, the changelog is somewhere between whatsnew & versionchanged notes on one side, and Git history on the other. And the changelog tends to work better for things that were renamed or moved around.
This use case might be an outlier, so it might be OK to break it. But: do we know of any other use for the changelog?
The newly restored changelog filter looks good; maybe it could be taught to display entries from old versions in the main document?

if we kept at least the last 3 versions on a single page, it would probably be good enough.

It might even be reasonable to trim that list to the last 5 minor versions, which covers everything that was in the "supported" window for CPython (with the newer annual releases + 5 year support cycle).

One thing we could do is add a warning to the link to the changelog, warning people to not open it on a phone.

We can’t do that in all websites and search engines that link to the changelog, though.


What are best practices for using MathJax in ReactJS/NextJS?

function fetchOutput() {
   setShowOutput(false);
   setOutput("$...$");
}

useEffect(() => {
  (async () => {
    MathJax.typesetClear();
    await MathJax.typesetPromise();
    setShowOutput(true);
  })();
}, [output]);

On a click of a button fetchOutput is called to generate new maths. To not display the $$ delimiters, I hide the output div while MathJax is typesetting. Once the asynchronous typesetting is complete, I show the output div.
The problem is that sometimes the output stays hidden. So the code after await MathJax.typesetPromise() does not run.
Is the problem with using an async function in useEffect?
Is the problem with MathJax and React trying to manipulate the DOM at the same time?

I have never used React.js or Next.js, so I can't really tell you what best practices are, but I do wonder whether useEffect() is expecting to have an async function, and whether that isn't the problem.  Your suggestion that React and MathJax are competing for the DOM sounds like a reasonable hypothesis.  The fact that it only happens sometimes suggest a race condition of that kind, and the async function is a likely culprit.
If you comment out the two setShowOutput() commands, so that the output is always shown,  does the math get processed?
If you add a console.log() call after the await command, does its output show up in the browser console?

I can get it work, but I am not sure if my solution is "correct" or if any anomalies will arise at some point.
Does the MathJax team have any plans to provide official packages for different frameworks?

Does the MathJax team have any plans to provide official packages for different frameworks?

The MathJax team is just two people, and we do not have the resources to make and maintain official plugins for all the popular frameworks.  Developing the needed expertise in a range of diverse frameworks takes time, and keeping up with changes in those frameworks is a maintenance cost that is beyond our current means.  The community members of those frameworks are in a better position to support their framework-specific plugins.  We answer questions for them as best we can, but that is the best we can offer.


modified threading handling in config for multithreaded flask

handling multithreading within dsp.settings in setting config
modified relevant methods that involve thread->stack dictionary
refers to this issue

Thanks for this, it works for my use case where I'm using HFClientTGI in multiple threads.

thanks for this, wasn't working w/ FastAPI


Feature Request: manual merge

Occasionally the scraper doesn't merge items. It would be great to have a manual merge option to combine duplicates that are missed.

Can you specify the titles that doesn't merged. Thanks. (Manual merge will not be added.)

It's more when my titles in the filename aren't right, I have corrected the match afterwards but they still don't merge. For example a couple of my MSU-1 hacks didn't recognize at first and I have no way to combine them post-scan (unless I'm missing something)?

For example here I have two versions of Earthbound which have the same database match and the same display title, but I believe since one had "Mother 2" in the filename it didn't merge and I can't do it afterwards

Please try to resync.

Ah perfect that fixed it, just make sure the titles playable titles are the
same and the re-sync picks it up.
On Wed, Mar 15, 2023 at 12:28 PM TapiocaFox @.***>
wrote:

Please try to resync.
—
Reply to this email directly, view it on GitHub
https://github.com/magneticchen/Daijishou/issues/310#issuecomment-1469311324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5SRY5U7FREOHKHONWPDSLW4FANXANCNFSM6AAAAAAV3FLB5E
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Zach Howard


Add more examples of workflows created with scriptcwl

For example nlppln and ochre.

List of non-toy cwl workflows
https://view.commonwl.org/workflows


Master

Decent Romanian translation. Missing the numeral attribute agreement in the genitive case. Forced to add some new resources due to the specificity of the Romanian language when specifying 'from x to y' or 'x through y' expressions.

Thank you @illegitimis !


fix(types): allow evaluate functions to take a readonly array as an argument

Fixes #6953

Thanks for this change!
I'm curious, if we made the type JSONArray = readonly Serializable[], would that work? I think a mutable array can become a readonly, but not the other way round. So if so we can avoid the union type and just define it with readonly.

Hi @jackfranklin,
yes, it seems so 👍
I will change the PR later today.

Updated. Please take a look :)


Update to latest Rails patch release 4.2.5

Updates smart answers to the use the latest patch release of Ruby on Rails.
Changelog links:

ActionMailer
ActionPack
ActionView
ActiveModel
ActiveRecord
ActiveSupport
ActiveJob

The url_for method no longer modifies arguments in polymorphic URLs but it doesn't seem to effect smart answers.
Seems to be mostly ActiveRecored relation changes.
Expected changes

none

Looks good to me, although it'd be good to make sure the regression tests all pass before deploying.

Rebased with master, the regression seem ok:
Finished in 4435.497196s, 4.9388 runs/s, 0.0257 assertions/s.

21906 runs, 114 assertions, 0 failures, 0 errors, 0 skips


thread safety issues

cherrypy+ws4py create a thread per WebSocket connection when running a WebSocket server. This gives rise to thread safety issues in classes such as TSServer where lists of connections are altered whilst they are being iterated over.
Fortunately it occurs relatively rarely. But is still a good idea to fix.

Provisionally seem to be fixed by latest commits.


Merge dev to staging

Codecov Report

Merging #185 (98f8a3a) into staging (fc0f57f) will decrease coverage by 1.46%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           staging     #185      +/-   ##
===========================================
- Coverage    69.64%   68.18%   -1.47%
===========================================
  Files          307      277      -30
  Lines        34876    33911     -965
  Branches      4761     4538     -223
===========================================
- Hits         24291    23121    -1170
- Misses       10129    10335     +206
+ Partials       456      455       -1

Impacted Files
Coverage Δ

meteor/lib/ReactiveStore.ts
16.07% <ø> (ø)

meteor/lib/Rundown.ts
41.17% <ø> (+1.78%)
:arrow_up:

meteor/lib/Settings.ts
100.00% <ø> (ø)

meteor/lib/api/ExternalMessageQueue.ts
100.00% <ø> (ø)

meteor/lib/api/client.ts
100.00% <ø> (ø)

meteor/lib/api/mediaManager.ts
100.00% <ø> (ø)

meteor/lib/api/methods.ts
77.14% <ø> (ø)

meteor/lib/api/peripheralDevice.ts
93.61% <ø> (-3.85%)
:arrow_down:

meteor/lib/api/pubsub.ts
93.33% <ø> (ø)

meteor/lib/api/rundownLayouts.ts
55.22% <ø> (-1.60%)
:arrow_down:

... and 226 more

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

Looks like the Playout gateway is not using the latest TSR. Other than that, looks good

Updated


missing code elements in challenge 15 of the odin project

in the odin project, there is a sentence that is worded like

You should always have the meta tag for the charset encoding of the webpage in the head element: <meta charset="utf-8">.

it should be worded like

You should always have the meta tag for the charset encoding of the webpage in the head element: <meta charset="utf-8">.

Here is the file https://github.com/freeCodeCamp/freeCodeCamp/blob/569fc3196b2d3a9a96706f14b13bda48388d2c9a/curriculum/challenges/english/10-coding-interview-prep/the-odin-project/html-boilerplate-question-c.md#the-charset-meta-element

If you would like to fix this issue, please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this.

can I solve this?


Analysistests

a little bit of refactoring

Codecov Report

Merging #440 into master will increase coverage by 0.06%.
The diff coverage is 94%.

@@            Coverage Diff             @@
##           master     #440      +/-   ##
==========================================
+ Coverage   69.45%   69.51%   +0.06%
==========================================
  Files          42       42
  Lines       13670    13645      -25
==========================================
- Hits         9495     9486       -9
+ Misses       4175     4159      -16

Impacted Files
Coverage Δ

tests/test_analysis.py
97.14% <100%> (+0.84%)
:arrow_up:

androguard/core/analysis/analysis.py
77.46% <92.68%> (+1.4%)
:arrow_up:

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 abed877...8ca3b99. Read the comment docs.


do_predict?

Hi,
Can the script do predict? I may miss it, but I didn't see a "do_pred" flag.

Hi @acmilannesta,
do_predict added.

Great, thx so much!
One more issue for "create_finetuning_data.py", I got the following error when I run in colab:
    !python /content/ALBERT-TF2.0/create_finetuning_data.py \
        --input_data_dir=/content/input \
        --spm_model_file=/content/drive/My\ Drive/albert_model/large/vocab/30k-clean.model \
        --train_data_output_path=/content/input/train.tf_record \
        --eval_data_output_path=/content/input/eval.tf_record \
        --meta_data_file_path=/content/input/meta_data \
        --fine_tuning_task_type=classification \
        --max_seq_length=142 \
        --classification_task_name=COLA

Traceback (most recent call last):
  File "/content/ALBERT-TF2.0/create_finetuning_data.py", line 149, in <module>
    app.run(main)
  File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 299, in run
    _run_main(main, args)
  File "/usr/local/lib/python3.6/dist-packages/absl/app.py", line 250, in _run_main
    sys.exit(main(argv))
  File "/content/ALBERT-TF2.0/create_finetuning_data.py", line 137, in main
    input_meta_data = generate_classifier_dataset()
  File "/content/ALBERT-TF2.0/create_finetuning_data.py", line 122, in generate_classifier_dataset
    do_lower_case=FLAGS.do_lower_case)
  File "/content/ALBERT-TF2.0/classifier_data_lib.py", line 832, in generate_tf_record_from_data_file
    train_input_data_examples = processor.get_train_examples(data_dir)
  File "/content/ALBERT-TF2.0/classifier_data_lib.py", line 269, in get_train_examples
    self._read_tsv(os.path.join(data_dir, "CoLA", "train.tsv")), "train")
  File "/content/ALBERT-TF2.0/classifier_data_lib.py", line 113, in _read_tsv
    for line in reader:
  File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/lib/io/file_io.py", line 220, in __next__
    return self.next()
  File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/lib/io/file_io.py", line 214, in next
    retval = self.readline()
  File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/lib/io/file_io.py", line 178, in readline
    self._preread_check()
  File "/usr/local/lib/python3.6/dist-packages/tensorflow_core/python/lib/io/file_io.py", line 84, in _preread_check
    compat.as_bytes(self.__name), 1024 * 512)
tensorflow.python.framework.errors_impl.NotFoundError: /content/input/CoLA/train.tsv; No such file or directory

It seems to ask for a CoLA directory, while classification_name only accepts "COLA".

Great, thx so much!
But do you also need to add something like prediction data output in "create_finetuning_data.py"?

@acmilannesta
for running predict, additional flags
--do_predict --predict_data_path=${OUTPUT_DIR}/${TASK_NAME}_predict.tf_record --input_data_dir=${GLUE_DIR}/

Epoch 1/3
7698/7698 [==============================] - 9878s 1s/step - loss: 0.8664 - accuracy: 0.7629 - val_loss: 0.0000e+00 - val_accuracy: 0.0000e+00
Epoch 2/3
2445/1925 [======================================] - 2886s 1s/step - loss: 0.5667 - accuracy: 0.8351
Got it. Now I got into another issue. It seems the 2nd training epoch will use my validation set. My training set has 7698 batches, and my validation set has 1925 batches.

Second epoch won't use validation dataset as training set, even though it seems like that.
Model.fit api has known issues when tf.data is given as input , steps calculation issues.
Only after first epoch model will know the complete data size . Ignore it.
You can also train using --custom_training_loop

Thank you!
I've just run my model on AWS g4dn.xlarge (Tesla T4 GPU) VM. However, it almost took 3 times longer than running bert-base model.

About 170-175 ms/step on bert
480-490 ms/step on albert
Kamal Raj<EMAIL_ADDRESS>于2019年11月11日周一 上午8:10写道：

@acmilannesta https://github.com/acmilannesta
How much time for bert and Albert ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kamalkraj/ALBERT-TF2.0/issues/3?email_source=notifications&email_token=ALL6NUWY7UFIKTTK6X4CWV3QTFKTTA5CNFSM4JJMRWA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDWY3FA#issuecomment-552439188,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALL6NUWUQN4MF2UYGU5MKELQTFKTTANCNFSM4JJMRWAQ
.

Which implementation of bert are you using ?
Is batch size same in bert and albert training ?

I used a package called keras_bert (https://github.com/CyberZHG/keras-bert), whcih basically load ckpt into keras model.
Yes, the batch size is same = 16.

TensorFlow version for keras_bert ?

Yes.

Tensorflow 1.X or 2.0 ?

I think both work. But I'm running on 1.x

Tensorflow 2 is slower than 1.x
https://github.com/tensorflow/tensorflow/issues/33487

https://github.com/tensorflow/models/tree/master/official/nlp/bert
TF 2.0 implementation of BERT

I see. Let me try this

The above one runs on TensorFlow 1.15

I just tried. About 2.4 steps/seconds (416 ms/step).

https://github.com/tensorflow/tensorflow/issues/33487#issuecomment-543652394
Based on this comment, would you suggest turning off eager in tf2.0 to run your codes?

@acmilannesta
Try and let me know the results

Unfortunately, it doesn't allow for disabling eager in tf2.0.
Kamal Raj<EMAIL_ADDRESS>于2019年11月11日周一 下午1:01写道：

@acmilannesta https://github.com/acmilannesta
Try and let me know the results
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kamalkraj/ALBERT-TF2.0/issues/3?email_source=notifications&email_token=ALL6NUSJ64UUGRPMVMBHOCTQTGMYFA5CNFSM4JJMRWA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDXTVQI#issuecomment-552549057,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALL6NUSGQ6ODPQ6NIJQGXZLQTGMYFANCNFSM4JJMRWAQ
.


Install/update improvements. Restart on driver update.

Also mostly pretty uncontroversial @max @gabriel , with possibly one exception, as noted.

(Max is @maxtaco on github, not at-max!)

Don't understand the code much, but :thumbsup: :)


feat(hooks-overview): Translation to Italian

Closes #44

Thanks @LucaBlackDragon ! All corrections/suggestions applied, closing 👍


Small Shiny Sprites

Hey talwat! Hope you are doing well!
pokemon-colorscripts added shiny sprites so it'd be nice if we can also get shiny sprites in this repo.

Heya! Yeah, the source they found is actually really cool. I can add them to the vanilla sprites (PokeAPI) since they would fit best there.

It might take me a while to get around implementing, but I can do it. I also need to move the sprites to a separate repo (finally) and also improve the self update functionality a lot.

This has been added to vanilla sprites.


Up/Down panel direction

It would be awesome if the panel could also be configurable to slide up and down.
An example use case would be like Google Play Music, Spotify and Soundcloud's bottom bar to swipe up and see the album art or swipe down to navigate the rest of the app.
I'm not sure if that's outside the scope of this project, but the interaction is almost the same as a left/right slideout menu.
Would be happy to contribute towards this feature.
Thanks!

Is it still developing?


Feature: Support asynchronous accessors for Blazor Server

Some might use this package in Blazor Server. In Blazor Server we can't use IJSInProcessObjectRefereces we currently use to get properties like Name from a FileSystemHandle synchronously. It would be nice to have a sample project that uses Blazor Server and to set up the service structure so that you don't need to initialize an IJSInProcessObjectReferece if you don't use it.
A proposed name for the asynchronous counterpart i.e. the Name property would be GetNameAsync().

In the new packages that this project will rely on which are Blazor.Streams and Blazor.FileAPI I have started a new wrapper structure that simplifies how to have the functionality that is supported in Blazor Server, but also the easy accessors that are available in Blazor WASM through the use of IJSInProcessObjectReferences.
The new structure that I use in those projects should be familiar to people as I basically have some implementation supported in Blazor Server (i.e. the Blob wrapper class) and then another wrapper class that has the features from Blazor WASM which extends the Blazer Server version. (i.e. the BlobInProcess wrapper class). This is similar to the relationship between the IJSRuntime and IJSInProcessRuntime.
I want to adopt this structure in this project. This will be a breaking change but will make it possible to use the package in both Blazor Server and Blazor WASM.

This was implemented as a part of #28 and has been published in version 2.0.0 to NuGet.
We have normalized the structure of the wrapper classes to have Blazor Server compatible base implementations and Blazor WASM versions that extend these.


Default Topic MQTT seems broken

Hi there,
Thanks for making a great library on pymadoka and a MQTT broker, trying to get this to work for HVACS.
I noticed 2 things already:
When using root topic starting with a / you get some weird behaviour, at least on mosquito:
Defining a root topic without a trailing / fixes this, although the default ROOT TOPIC in mqtt.py is still defined with a /
Furthermore, my madoka keeps changing names in bluetooth. Half of the time it is called "UE878_RF_MODULE" and the other half "BRC1H_AA_BB-CC" . i changed the mqtt library to accept a config value "root_topic_only" that omits the device name.
      def get_device_topic(self):         """ Get the customized device topic using the device name and the root topic.         Returns:             str: The device topic in the form /root_topic/device_name"""         root_topic = self.ROOT_TOPIC         if "root_topic" in self.mqtt_cfg:             root_topic = self.mqtt_cfg["root_topic"]         if "root_topic_only" in self.mqtt_cfg:             return root_topic         else:             normalized_name = self.controller.connection.name             normalized_name = normalized_name.replace(" ","_")             normalized_name = normalized_name.replace(":","_")             normalized_name = normalized_name.replace("/","_")             return "/".join([root_topic,normalized_name])

Hi,
I will have a look at it and issue a new version with your suggestions. I
didn't test it with mosquito and it looked good by the time with the
command line tools I used. The problem with the name comes from the
thermostat and the BT library, but there isn't much I can do to override it
because no configuration is stored by the pymadoka library. Anyway, your
patch should be enough, thank you.
On Sat, 5 Nov 2022 at 14:53, rekkebus @.***> wrote:

Hi there,
Thanks for making a great library on pymadoka and a MQTT broker, trying to
get this to work for HVACS.
I noticed 2 things already:
When using root topic starting with a / you get some weird behaviour, at
least on mosquito:
Defining a root topic without a trailing / fixes this, although the
default ROOT TOPIC in mqtt.py is still defined with a /
Furthermore, my madoka keeps changing names in bluetooth. Half of the time
it is called "UE878_RF_MODULE" and the other half "BRC1H_AA_BB-CC" . i
changed the mqtt library to accept a config value "root_topic_only" that
omits the device name.
def get_device_topic(self): """ Get the customized device topic using the
device name and the root topic. Returns: str: The device topic in the form
/root_topic/device_name""" root_topic = self.ROOT_TOPIC if "root_topic" in
self.mqtt_cfg: root_topic = self.mqtt_cfg["root_topic"] if
"root_topic_only" in self.mqtt_cfg: return root_topic else: normalized_name
= self.controller.connection.name normalized_name =
normalized_name.replace(" ","") normalized_name =
normalized_name.replace(":","") normalized_name =
normalized_name.replace("/","_") return
"/".join([root_topic,normalized_name])
—
Reply to this email directly, view it on GitHub
https://github.com/mduran80/pymadoka/issues/10, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFK3CTZND7G2UPXHHIGMWCTWGZRFLANCNFSM6AAAAAARX6AFRA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I updated the library (0.2.8) so the address is always sent as part of the root topic (instead of the name provided by the bluetooth connection). Anyway, using the root_topic_only is still supported with slight changes to what you proposed.


⚠ Samsung has degraded performance

In dfb9bfe, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2838 ms

Resolved: Samsung performance has improved in c262b9f.


For Python 3, attempt to use the selectors module from asyncio package.

The selectors module is found underneath the asyncio package in Python3.  This patch allows us to import selectors from within asyncio if the original import fails.

Thanks, and sorry for the delay, python3.3 is a bit old and it takes a bit of work to build it.


Sequential and Shell mode return not valid annotation values

When the shell mode is executed, in Mac and Windows systems. The return is providing not valid annotated values for the magnetic components.
It seems there is an issue with the concatenate process once the swarm residuals are downloaded and the dataframe is created to be the input of the annotation process.

Current version has address this issue.


Doc added how to block search engine indexation of repository

Added documentation on how to block search engines indexation of gitea repository

Codecov Report

Merging #9566 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9566      +/-   ##
==========================================
+ Coverage   41.98%   41.99%   +0.01%
==========================================
  Files         577      577
  Lines       75970    75970
==========================================
+ Hits        31899    31907       +8
+ Misses      40125    40118       -7
+ Partials     3946     3945       -1

Impacted Files
Coverage Δ

models/unit.go
62.16% <0%> (-5.41%)
:arrow_down:

modules/log/event.go
64.61% <0%> (-1.03%)
:arrow_down:

models/gpg_key.go
55.59% <0%> (+0.55%)
:arrow_up:

services/pull/merge.go
53.92% <0%> (+0.78%)
:arrow_up:

models/webhook.go
70.46% <0%> (+1.06%)
:arrow_up:

services/pull/temp_repo.go
34.18% <0%> (+2.56%)
:arrow_up:

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 9600c27...b7ae6bb. Read the comment docs.

To be honest I think it would be reasonable to just add a very restricted default robots.txt and get users to override that if they want things to be indexed.

worth a look is https://codeberg.org/robots.txt ...

worth a look is https://codeberg.org/robots.txt ...

ia_archiver bot is from Wayback Machine, used to snapshot a site for archival.

@guillep2k thanks, what's LGTM?

@6543 ooops!, sorry about that, I didn't know it either. I'll fix it and commit again.

@6543 commited in one batch (didn't know how to do it from github so I did it on my computer).

You can do it on the "Files changed" view ... a nice way if you are not at home (and change PR with your webbrowser ...)
In the end it doesnt mather how you do it :)

@guillep2k thanks, what's LGTM?

Means "looks good to me". 😄


Error with "uiwjs/react-codemirror" "Field is not present in this state"

System Info
  System: Linux (ubuntu)
  Binaries:
    Node: 18.16.0 - ~/.asdf/installs/nodejs/18.16.0/bin/node
    npm: 9.5.1 - ~/.asdf/plugins/nodejs/shims/npm
    pnpm: 8.9.0 - ~/.asdf/installs/nodejs/18.16.0/bin/pnpm
  Browsers:
    Chrome: 117.0.5938.92
  npmPackages:
    @rspack/cli: latest => 0.3.8

Also tried with 0.3.8-canary-1c9f8af-20231026052844
Details
Getting the following error with https://uiwjs.github.io/react-codemirror/
When you click into the input, you get the following with the production build:
Compiled with problems:
ERROR
Field is not present in this state
RangeError: Field is not present in this state
    at eb.field (http://localhost:8080/main.js:1:404152)
    at d (http://localhost:8080/main.js:1:318114)
    at ex (http://localhost:8080/main.js:1:338603)
    at U.update [as updateF] (http://localhost:8080/main.js:1:337941)
    at Object.update (http://localhost:8080/main.js:1:396056)
    at eb.computeSlot (http://localhost:8080/main.js:1:404778)
    at X (http://localhost:8080/main.js:1:399389)
    at new eb (http://localhost:8080/main.js:1:404054)
    at eb.applyTransaction (http://localhost:8080/main.js:1:404734)
    at get state [as state] (http://localhost:8080/main.js:1:400853)

I cannot reproduce this issue with webpack.
Reproduce link
No response
Reproduce Steps
Create an app using rspack
pnpm create rspack@latest
pnpm add @uiw/react-codemirror

Update  main.jsx with
import React from 'react'
import ReactDOM from 'react-dom/client'
import CodeMirror from '@uiw/react-codemirror';

ReactDOM.createRoot(document.getElementById('root')).render(
  <React.StrictMode>
   <CodeMirror />
  </React.StrictMode>
)

Updated the rspack.config.js to use production mode.
module.exports = {
	mode: 'production',
	context: __dirname,
	entry: {main: "./src/main.jsx"},
	devServer: {hot: false},
	builtins: {html: [{template: "./index.html"}]},
	module: {rules: [{test: /\.svg$/,type: "asset"}]}
};

Run the dev-server
pnpm run dev

Getting the following error
Field is not present in this state
RangeError: Field is not present in this state
    at eb.field (http://localhost:8080/main.js:1:404152)
    at d (http://localhost:8080/main.js:1:318114)
...

Thanks!


⚠ Bofrost.at has degraded performance

In 8277b67, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1379 ms

Resolved: Bofrost.at performance has improved in cfc21fe.


Dataframe tasks not inheriting connection ID in 0.5.1

Context
As of 0.5.1, dataframe tasks are not inheriting connection IDs from upstream tasks. dataframe tasks with or without an output table currently fail with:
raise AirflowNotFoundException(f"The conn_id `{conn_id}` isn't defined") airflow.exceptions.AirflowNotFoundException: The conn_id `None` isn't defined
Possibly related to https://github.com/astro-projects/astro/issues/117
Desired Behavior
dataframe tasks should inherit the connection ID from an upstream task if there is one.

@kentdanas Thank you very much for reporting this issue. @dimberman already identified the problem and we will soon have a fix. In the meantime, we'll yank the 0.5.2 release. If possible, please, stick to the previous releases.

Addressed at the same time as #124


Sysmon Parser - 'extend' operator: Failed to resolve scalar expression named '["@Name"]'.

Describe the bug
Using the Sysmon Parser(https://github.com/Azure/Azure-Sentinel/blob/master/Parsers/Sysmon/Sysmon-AllVersions_Parser.txt) to create an analytics rule.  You are presented with the error:
'extend' operator: Failed to resolve scalar expression named '["@Name"]'.
To Reproduce
Steps to reproduce the behavior:

Create the following query in Azure Sentinel as an scheduled analytics rule:

This will present the error.

Expected behavior
No error should occur.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser Firefox
Version 102.0

Additional context
Add any other context about the problem here.

Just to link a similar issue I found raised last year:
https://github.com/Azure/Azure-Sentinel/issues/2200

@WoodellJ : We merged the PR  Could you please let us know still you are facing the issue ?

@WoodellJ : We merged the PR Could you please let us know still you are facing the issue  or issue got resolved ?

Hi @WoodellJ,
We are closing this issue as its already addressed and we are not seeing this issue anymore. Please find the below screenshot for your reference. Please feel free to reopen if you need any further assistance on this.

Thanks


Add query token-factory method and TWAP to stargate

Closed #457
Major: Add query token-factory and TWAP method to stargate
Minor: Add some comment and change func name for more detail

hey @GNaD13, I think #457 should be solved in a separate PR.


beforeSave makes all fields undefined

When I add a beforeSave function to my Parse hosted CloudCode, all fields in the class I'm saving get changed to undefined.  It doesn't matter what I put in the beforeSave code.  A simple function like:
Parse.Cloud.beforeSave("chart", function(request, response) {
    console.log("Running beforesave")
     response.success()
});

changes all fields to undefined.  If I switch to JSSDK 1.5.0, everything works fine.  So it appears to be a bug in 1.6.x and higher.

Here's the log output when I use beforeSave. The "update changed to {}" is what baffles me.
I2015-09-23T23:05:51.493Z]v85 before_save triggered for chart for user YUUdJazO4j:
Input: {"original":null,"update":{"ACL":{"YUUdJazO4j":{"read":true,"write":true}},"designer":{"__type":"Pointer","className":"designer","objectId":"sl5smLJb2A"},"name":"BeforeSaveTest","notes":"","owner":{"__type":"Pointer","className":"_User","objectId":"YUUdJazO4j"}}}
Result: Update changed to {}
I2015-09-23T23:05:51.529Z]Running beforesave

This isn't happening for me with version 1.6.2 in either node or the browser.
Here's my log output when I try to replicate:
I2015-09-27T19:20:26.892Z]v37 before_save triggered for chart for user UTsoNVljmJ:
Input: {"original":null,"update":{"ACL":{"UTsoNVljmJ":{"read":true,"write":true}},"designer":{"__type":"Pointer","className":"designer","objectId":"iTe5InCIij"},"name":"BeforeSaveTest","notes":"","owner":{"__type":"Pointer","className":"_User","objectId":"UTsoNVljmJ"}}}
Result: Update changed to {"ACL":{"UTsoNVljmJ":{"read":true,"write":true}},"designer":{"__type":"Pointer","className":"designer","objectId":"iTe5InCIij"},"name":"BeforeSaveTest","notes":"","owner":{"__type":"Pointer","className":"_User","objectId":"UTsoNVljmJ"}}
I2015-09-27T19:20:26.912Z]Running beforesave

Hi Dan - here's some additional detail:

beforeSave works if I use REST/CURL (JSSDK 1.5.0 and latest)
beforeSave works if I update an existing record with IOS or Android (JSSDK  1.5.0 and latest)
beforeSave works if I update via browser (JSSDK 1.5.0 and latest)
beforeSave works if I add a new record using IOS or Android (JSSDK 1.5.0)
beforeSave fails if I add a new record with IOS or Android (JSSDK latest)

I originally opened an issue for Android-SDK but found the same issue with IOS and realized the problem goes away when I use JSSDK 1.5.0.

By "fails", I mean all the fields get changed to undefined.

Doesn't seem to happen for me; maybe the Parse devs will have a better idea. Have you tried running it with only this function and no other cloud code?  Are you sure the code is exactly this:
Parse.Cloud.beforeSave("chart", function(request, response) {
    console.log("Running beforesave")
     response.success()
});

Maybe you could upload a reproducible example?

@ridergeek can you tell me what version of the JS SDK is hardcoded into your config/global.json file when you encounter this problem? We're trying to track down an issue where cloud code sometimes doesn't recognize that 1.6.2 is the "latest" version.

and :+1: to what @danrobinson said: Reproducible test cases are what we need for solving bug reports. Otherwise, it's difficult to replicate a variety of environmental factors.
I really appreciate that you've broken down the success/failure cases above, but I still need a bit more info

https://dl.dropboxusercontent.com/u/13394990/beforesavebug.zip
Here's an example project that duplicates the problem.  I included the cloud code too.
Just change the application and client keys to a valid project in appdelegate.swift before you run.

Can confirm this behavior (had tried client code version 1.6.2 but not Cloud Code version 1.6.2; sorry @ridergeek).  It happens whenever beforeSave is run on an update (whether a new record or an existing record) that includes a change to the ACL.  No matter what is in the beforeSave code, the update will become {} (so it doesn't change anything).  It happens with "jssdk" set to either "1.6.2" or "latest".
Here's a minimal example in Node: https://github.com/danrobinson/beforesavebug
The devs will have to help since this seems to be a problem with beforeSave, which like the other server-side JS code isn't in this repository.

Glad to see this will be fixed in 1.6.5. I downgraded to 1.5 for now, but I wonder if useMasterKey() in the beforeSave hook would work around the issue temporarily.

+1 on the glad this is fixed in 1.6.5!  I tried to use master key but it didn't help.  I think the only workaround (I haven't tested this) would be to not set an ACL before you save. You save the object without an ACL and then use beforeSave or afterSave to set the desired ACL.  Again, just a theory.


Rename la_arena::Idx to la_arena::Id

This makes naming consistent with la_arena::RawId. Alternatively, la-arena’s documentation could be updated to use ‘index’ terminology instead of ‘ID’ terminology, and RawId renamed to RawIdx.
This pull request doesn’t compile because dependencies on la-arena go through crates.io, so existing dependencies on the crate are referencing an old version. As such, this PR will only compile once a new la-arena version has been published.

I think we should make the index terminology canonical. arena is simple, so it makes sense to expose the underlying abstraction here. Big :+1: for improving consistency here!

I think we should make the index terminology canonical. arena is simple, so it makes sense to expose the underlying abstraction here. Big :+1: for improving consistency here!

I’ve reverted the first commit and renamed RawId instead. Should I squash. everything?

I’ve reverted the first commit and renamed RawId instead. Should I squash. everything?

You don't have to, but it might be easier if you rebase to solve the conflicts.

You don't have to, but it might be easier if you rebase to solve the conflicts.

I’ve just been going through and fixing the conflicts; I think I’ll squash before force-pushing to reduce confusion.

I’ve just been going through and fixing the conflicts; I think I’ll squash before force-pushing to reduce confusion.

bors r+

bors r+

bors r+

bors r+


Revert "Emit a precise error message when lldb can't load a swift AST"

This reverts commit 2bde84223ec637fb27575ef48f7207eb3d95585f
because it broke the bots.

@swift-ci test and merge


Campberbot not issuing cookies/brownies

Challenge Name

Issue Description
Since the FCC website crash the other day, camperbot is no longer issuing cookies/brownies.
He does respond to other commands such as find, botstatus, eightball, rooms.
This is affecting all rooms in chat not sure if it is affecting the challenges or the forum.
Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

@QuincyLarson @BerkeleyTrue

Thanks @mstellaluna for staying on top of things. We recently upgraded camperbot so this could be the cause. I will look into this shortly

@BerkeleyTrue thank you :) let me know if you need me to test camperbot when you are ready.

fixed. Thanks for the help @mstellaluna
Happy Coding

thanks !!


Add gnport to list of packages for depot_toolsport

I'm certain this is wrong, but I need it for depot tools.  Perhaps once zoslib dependency is resolved, gnport will build, and a binary with a tag will be present so this is done automatically.  If not, this is the start of the manual process. No rush on this pull request.

ahh, this is done automatically. No need for this.


Rename TryImmunity to TryInvulnerability

It's a check for semi-invulnerability rather than any sort of immunity.

Maybe just onInvulnerability?

I did say "maybe". What does everyone else think?

Mostly, I feel like onTryBlah is only used if we already have an onBlah that does something different.

... that's why it's a separate commit so it can be easily reverted.

I didn't say you did anything wrong. :p

Yes! Thank you!


Strip code comments from build output

We are currently emitting code comments inside the ESM and CJS files in our build output. We don't have to go full minification, but it would be nice to remove the inline comments there to save some space. The publicly necessary comments (like public APIs and documentation) will remain to be visible in the *.d.ts output.
This should be simple to implement by using the terser plugin for Rollup, which we can add after the TypeScript compilation step.

@GuillaumeSalles @ofoucherot Any thoughts on this, or are you on board with this?

The goal is to not have full minification, but to strip confusing comments, TODOs, FIXMEs, etc. from the final output and keep those scoped to just the source code, where they make more sense. A lot of our code comments talk about types, or point to locations using ^^^^ markers, etc, and in the final output those are unhelpful and sometimes even confusing.


Implement a compiled RiscV parser

implement src/riscv2fj.py
elf riscv (RV32I) executable  ==>  .fj file using the riscvlib.fj standard library file.

closed because we switched to arm.
the riscv2fj.py file will be a good example of how to make the arm-one.


[HOLD for payment 2024-03-29] [$250] [Wave Collect] [Workflows] Clean up the isAutoApprovalEnabled flag

Problem
We use the isAutoApprovalEnabled flag to decide if the approval toggle should be on or off in Workflows page https://github.com/Expensify/App/blob/f84219f187f9960df17c584e7c8b10feee77f27f/src/pages/workspace/workflows/WorkspaceWorkflowsPage.tsx#L137
We should however use a comparison to the policy.approvalMode as we do here to define if the auto approval is enabled. It is true when the approval mode is set to basic.
The isAutoApprovalEnabled property is not passed from the backend, it should be removed for now.
This property exists, but its used in different way and we can bring it to the app later.
Solution
Use the approvalMode property to determine the toggle state
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01573ee41af24d66fa
Upwork Job ID:<PHONE_NUMBER>309750784
Last Price Increase: 2024-03-19

Issue OwnerCurrent Issue Owner: @slafortune

@mountiny confirming we're not looking for volunteers here and we're done?

We are not, @abzokhattab sorry, I marked this as internal as there might be some changes required in the backend, I will handle this one

PR is in review

$250 to @hoangzinh for this this one

No need for the checklist here

Invite sent here @hoangzinh

Paid


Should not prompt to delete master branch after merge

If a change is committed to :master, and then merged, the PR (when viewed from within this plugin in VS Code) prompts you to delete the master branch. This prompt would obviously be fine if it was anything other than master, but deleting master is not really what anyone wants (particularly as selecting the "delete on remote" option puts the remote fork in a confused state where GitHub web interface thinks the forking process is still underway and the only way to fix that is to push master back to the remote fork).
Indeed, the GitHub web interface suggests deleting the fork, not the master branch in such situations.

Version information:

Extension version: 0.16.0
VSCode Version: 1.45.1
OS: Windows 10

Steps to Reproduce:

Fork repository.
Commit to master of fork.
Make a PR from within VS Code using this extension
Merge the PR
Refresh the PR in VS Code
See that it suggests deleting the master branch (which is inconsistent with the GitHub web interface)

Note: If this has to be coded as a special case, it may rear it's head again when master is replaced with a different term.

Seeing this again in https://github.com/github/codespaces/issues/1608

@burkeholland This change hasn't been released yet, should be fixed in tomorrow's release

I see this in the most recent nightly 2020.10.41223

Confirmed resolved in 2020.11.3841 (Nightly). 🎉

@connor4312 Oops, sorry, missed responding to this earlier. This is actually expected, we still offer deleting the local copy of the branch, just not the remote one


diagnostics: 1.8.9-0 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository diagnostics to 1.8.9-0:

upstream repository: https://github.com/ros/diagnostics.git
release repository: https://github.com/ros-gbp/diagnostics-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.20
previous version for package: 1.8.8-0

diagnostic_aggregator
* Add version dependencies in package.xml
* Add version check in cmake
* Add functionality for dynamically adding analyzers
* Contributors: Michal Staniaszek, trainman419

diagnostic_analysis

No changes

diagnostic_common_diagnostics

No changes

diagnostic_updater

No changes

diagnostics

No changes

self_test

No changes

test_diagnostic_aggregator
* Add version dependencies in package.xml
* Contributors: trainman419

Hold for coordinated release with #10558


Allow num to be a complex type to support Series operations.

Closes #103

[ ] Closes #103
[ ] Tests added: test_types_complex_arithmetic

Can you add a test with a reference to the original issue?

Sure - do you have an example of the kind of test you would like to see for this change? I was looking for something similar, but didn't see anything.

Thanks @aholmes


Build failing with a missing tests.settings

Details

Read the Docs project URL: https://awesome-django-timezones.readthedocs.io/
Build URL (if applicable): https://readthedocs.org/projects/awesome-django-timezones/builds/8510026/
Read the Docs username (if applicable): wgordon17

Expected Result
My project is a Django package, which imports the Django settings. Locally, I'm able to get things working by setting a DJANGO_SETTINGS_MODULE environment variable that points to tests.settings` (a directory and file in my git repo). Unfortunately, RTD can't seem to find the file when I set the environment variable, and removing the environment variable also doesn't work
ImportError: No module named 'tests.settings'

Actual Result
My assumption is that RTD is cloning my entire, which means tests.settings should be available? Unless it's under a different package name by chance?

I think this is because the command is executed inside the docs folder, and the env variable is set relative to the root of the project. I'm proposing #4962 to avoid this things

Thank you @stsewd! That pointed me in the right direction! Adding a __init__.py to the docs/ directory...and symlinking my tests/settings.py into the docs/ repo as well...worked great! Oh, and I also changed my DJANGO_SETTINGS_MODULE to docs.settings instead of tests.settings.
Worked like a charm 👍


node-sass deprecation results in broken compilation on latest sass features coming with angular material design

NPM version (npm -v):
6.14.13

Node version (node -v):
14.17.0

Node Process (node -p process.versions):
{
node: '14.17.0',
v8: '8.4.371.23-node.63',
uv: '1.41.0',
zlib: '1.2.11',
brotli: '1.0.9',
ares: '1.17.1',
modules: '83',
nghttp2: '1.42.0',
napi: '8',
llhttp: '2.1.3',
openssl: '1.1.1k',
cldr: '38.1',
icu: '68.2',
tz: '2020d',
unicode: '13.0'
}

Node Platform (node -p process.platform):
linux

Node architecture (node -p process.arch):
x64

node-sass version (node -p "require('node-sass').info"):
node -p "require('node-sass').info"
node-sass	6.0.0	(Wrapper)	[JavaScript]

npm node-sass versions (npm ls node-sass):
/home/thierry/sass
└──<EMAIL_ADDRESS>

BUG
"dependencies": {
"@angular/cdk": "^12.0.0",
"@angular/core": "^12.0.0",
"@angular/material": "^12.0.0",
"node-sass": "^6.0.0",
"node-sass-tilde-importer": "^1.0.2"
}
node-sass style.scss --importer=node_modules/node-sass-tilde-importer -o dist
It will be error of syntax on the core() below copied form the material design doc.
style.scss:
@use '~@angular/material' as mat;
@import '~@angular/material/theming';
@include mat.core();
I know why
the libsass delivered via npm in node-sass has a too old version.
And even if it was updated, it is officially deprecated by the sass team.
https://sass-lang.com/blog/libsass-is-deprecated
Maybe document in the README that it is deprecated?

https://github.com/sass/node-sass#node-sass

thanks :)


Error event doesn't work

Overview
I would like to check if there's been an error with the animation but I'm currently unable. I've been trying it through the prop onEvent and even though I source a failed .json file I don't receive an error.
Here's what I'm trying to do:
onEvent={(event) => {
        if (event === 'error') doSomenthing()
      }}

Any idea on how to verify that? Thank you!
Consuming repo

What repo were you working in when this issue occurred?

...
Labels

[x] Add the Type: Bug label to this issue.

the same issue, for the onEvent method only not getting trigged ,
any help?

Facing same issue, any fix yet?

Fixed with v3.5.2 🎉


transmission: rename from transmission_4

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This looks like transmission: rename from transmission_4. And Transmission 4 contains at least one regression causing data loss, see the original PR: https://github.com/NixOS/nixpkgs/pull/215316#issuecomment-1485097961

Transmission 4 contains at least one regression causing data loss

Why do you consider it as "data loss"? It's not files that were already downloaded are deleted from your storage, but rather it is the "torrent configuration" loss. I personally don't think it is such a bad bug to live with.

Yes, it loses torrent configuration in a way that downgrading does not restore. This is quite painful if you have large amount of affected torrents that you have configured. Thankfully, I had backups or I would be very annoyed.

Hmm I understand... Your usage of transmission is unique IMO. Perhaps we can add some release notes, with links to upstream bug reports? My personal opinion is that unless upstream released a completely broken package, a distribution shouldn't hold such significant updates from all users just because some users experience a bug that can barely be reproduced... I wasn't aware of this upstream release if I hadn't noticed it by chance by browsing Nixpkgs' pull requests.
BTW I don't understand what is the ofborg-eval-darwin error :/.

I'm attempting to fix the darwin build of transmission 4. I pushed several other improvements to both expressions, along with a release-notes line for the possible upstream bug experience.

@ofborg build transmission

The darwin build seems fixed.

I've been using 4.0.3 for a while, and lately ran into an issue where data was being downloaded, but not saved to disk. The torrents showed multiple GBs downloaded but still 0% progress. This was happening with all downloading torrents, even newly added ones, and was fixed by restarting Transmission.
I haven't reported it upstream since 4.0.4 is out now and I'm not using it yet.
So even though I'm using v4 I'm against making it the default as in my experience it's not yet as stable as v3.
Your goal seems to be to raise awareness about v4. I can think of a couple ways to do that without risking people's data:

add a release note mentioning v4 is packaged
deprecate transmission and push users towards transmission_3 or transsmission_4, similar to Python 2/3.

In both cases, we should explain why v4 isn't the default and link the PRs/upstream bug so users can make an informed decision.

Thanks @ThinkChaos for the ideas. I like them overall. As for:

deprecate transmission and push users towards transmission_3 or transsmission_4, similar to Python 2/3.

Were you thinking of something like this in aliases.nix:
transmission = throw "Please instead of attribute `transmission`, use `transmission_3` or `transmission_4`";

vs:
transmission = lib.warn "The transmission attribute without version suffix is deprecated, please switch over to either transmission_4 or transmission_3. Note the release-notes mentioning upstream bugs." transmission_3;

Or simply (which would not make a difference for most users, unless aliases are disabled in their nixpkgs.config):
transmission = transmission_3;

I'd appreciate your vote on either of these options. Moreover, if you'd report that with 4.0.4, you don't experience the buggy behavior you observed with 4.0.3, that should affect this decision.

Thanks @ThinkChaos for the ideas. I like them overall. As for:

deprecate transmission and push users towards transmission_3 or transsmission_4, similar to Python 2/3.

Were you thinking of something like this in aliases.nix:
transmission = throw "Please instead of attribute `transmission`, use `transmission_3` or `transmission_4`";

vs:
transmission = lib.warn "The transmission attribute without version suffix is deprecated, please switch over to either transmission_4 or transmission_3. Note the release-notes mentioning upstream bugs." transmission_3;

Or simply (which would not make a difference for most users, unless aliases are disabled in their nixpkgs.config):
transmission = transmission_3;

I'd appreciate your vote on either of these options. Moreover, if you'd report that with 4.0.4, you don't experience the buggy behavior you observed with 4.0.3, that should affect this decision.

sorry for noise
but what does
transmission = lib.warn evaluate to ? null ? eg what is output when you try to build it ?

transmission = lib.warn evaluate to ? null ? eg what is output when you try to build it ?

See: https://noogle.dev/?selected="lib.trivial.warn"&term="warn"

transmission = lib.warn evaluate to ? null ? eg what is output when you try to build it ?

See: https://noogle.dev/?selected="lib.trivial.warn"&term="warn"

@doronbehar thank you for you response
@ThinkChaos I like your suggestion, I would be leading towards throw but that's just my opinion

I wasn't aware of this upstream release if I hadn't noticed it by chance by browsing Nixpkgs' pull requests.

I would prefer throwing over a silent migration to a broken version but I do not think there is much of a point. Nixpkgs is method for distributing software (which needs to be working to be useful) before being a mechanism for announcing latest versions of upstream projects. Also, eventually, we are going to remove transmission_3 and then we would probably want to go back to using transmission attribute.

Perhaps we can add some release notes, with links to upstream bug reports?

I do not think many people running unstable read release notes. Personally, I skim the commit log but it is really easy to miss something important there. As such, I would not consider a mention in release notes to be a sufficient precaution for bumping the transmission attribute to a version that eats data.
There is a section for announcing new versions and Transmission 4 definitely deserves a mention (with a warning) but that just would not be enough for the bump IMO.

My personal opinion is that unless upstream released a completely broken package, a distribution shouldn't hold such significant updates from all users just because some users experience a bug that can barely be reproduced...

I would consider any data loss a serious breakage. I would not be against bumping the attribute if it was just the feature that was broken but it clears the torrent status so it is not possible to fix by downgrading once user ran 4.0. And the bug can be reproduced easily – just because it is a niche feature that does not affect many torrent files does not mean it does not seriously affect many peopleʼs workflows.

I would personally lean more towards warn for backward-compatibility reasons, and since it's similar to the established patern for module options (for instance mkRenamedOptionModule).
That would also allow you to backport the change and reach people using stable.

I do not think many people running unstable read release notes

I think you're right, personally I've started diffing the next release notes md file when updating my flake, works great :)

I would not consider a mention in release notes to be a sufficient precaution for bumping the transmission attribute to a version that eats data.

I agree, I meant just as a way to say "_4 exists, use it if you want".

I opened a PR that does everything done in this file besides the rename, so that the discussion here will stay focused: https://github.com/NixOS/nixpkgs/pull/259361 . Your review is welcome.

There is a section for announcing new versions and Transmission 4 definitely deserves a mention (with a warning) but that just would not be enough for the bump IMO.

@jtojnar I feel we are in almost full agreement. Could you perhaps voice perhaps a more concrete opinion on the options suggested in my previous comment above?

Haven't changed this PR fundamentally, still suggesting the same rename, just fixed the merge conflicts after #259361 .

Usually, we would first do alias without warning (evaluation checks did not like warnings during package set evaluation, not sure if we now run the checks with allowAliases = false), then switch to a throw a cycle later. The workflow is not ideal but :woman_shrugging:
But I am questioning whether such action is desirable when eventually we are going to drop transmission_3 eventually (hopefully sooner than later) and then we will want transmission to point to Transmission 4.

Just fixed evaluation from the rebase in the last force push. I think I'll come back to this later, and I'll give upstream a chance to respond to the issues presented to them, and suggest a solution afterwards.

We also need these settings into config file.
rename-partial-files = true;
lpd-enabled = false;
LPD should be disabled by default as stated here.
Strangely, partial files are not being renamed anymore with V4. Maybe this is related to https://github.com/NixOS/nixpkgs/pull/258058#issuecomment-1741416536?

@bb2020 are you trying to say that setting these may reduce the chance for the bugs reported in #215316 (comment) to appear?

Normally incomplete files used to have .part extension. This new behavior leads to a massive confusion especially when incomplete-dir-enabled is disabled. Because of that we should override the default.

Strangely, partial files are not being renamed anymore with V4. Maybe this is related to #258058 (comment)?

I do not think that is related – that issue is with the torrent file itself, not the downloaded data.

Oh I didn't mean to close this, I just cleaned up my remote branches and deleted this old branch accidentally.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-to-introduce-a-breaking-version-bump/46746/1

Can you cherry pick these changes into your PR? This should keep the older defaults.

Can you cherry pick these changes into your PR?

@bobby285271 I decided to change this PR a bit after the discussion on discourse and these changes maybe don't fit now. Perhaps you can submit a PR where the new settings you introduce change their default value based on the version of cfg.package?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/how-to-introduce-a-breaking-version-bump/46746/7

I decided to change this PR a bit after the discussion on discourse and these changes maybe don't fit now.

I see 4.00 still has some issues.

Perhaps you can submit a PR where the new settings you introduce change their default value based on the version of cfg.package?

I think you should still cherry pick my changes.
They are the defaults for older version and would minimize confusion if someone switches between V3 and V4.

I see 4.00 still has some issues.

Maybe we should create a thread in Discourse Announcements category like the following, and link it in the error message:
https://pad.lassul.us/lHdWr37LRxS-8gEHYWvfuA?both
(Feel free to edit)

They are the defaults for older version and would minimize confusion if someone switches between V3 and V4.

I think this is not our responsibility. And doing so might instead cause confusion for people switching from other distribution to NixOS. At most, we can mention it in the announcement.

It looks like a nice use case for RFC 127 problem infrastructure!

Thanks for the ideas @jtojnar . I added both a notice to the upcoming release notes, based on the text you wrote here.

They are the defaults for older version and would minimize confusion if someone switches between V3 and V4.

I think this is not our responsibility. And doing so might instead cause confusion for people switching from other distribution to NixOS. At most, we can mention it in the announcement.

I agree. I'll write a comment at the discourse thread when this is merged.

I ran into another v4 bug that's technically data loss, sharing here for awareness: Downloaded data not saved, might be nice to also add to the release notes.

I ran into another v4 bug that's technically data loss, sharing here for awareness: Downloaded data not saved, might be nice to also add to the release notes.

Linked to it in the release notes :+1:.

So.. @jtojnar do I get your final approval on this change?

Once again I fixed the merge conflicts. Since the last revision of this PR, I got only approvals and hadn't seen any objections to it. Hence I'll merge it myself in a day or two.


Vireo does not support ICH IDE devices

Build: 918
Today I tested Vireo on another computer (this time WinXP era). It all went fine: Vireo detected loads of PCI devices and found an IDE device (Device ID 24CB from Intel (Vendor ID: 8086)) and it loaded the appropriate (and only) driver. However, the driver did absolutely nothing, not even the usual "driver mark I" message. Vireo does get past the driver though, for it reports its build number (which is the last thing done before the endless while loop). The driver doesn't hang.
This either comes down to the driver not getting the INIT command (which would be weird, but would explain the driver successfully returning command back to Vireo), or something else. I'll have to look into this. I do want this to work, since the test machine is one of the few machines I own with a serial port.
The machine uses an ICH4 IDE controller. The builds do work on PIIX(4) devices. I tested this in Virtualbox and a laptop from ~1999. Both use Device ID 7111 by Intel.
Reproduction: in Virtualbox open the settings and go to storage. Click on the IDE controller and on the right hand side select ICH6 (which behaves similarly) in the 'Type' dropdown menu. Virtualbox uses PIIX4 by default. Anyway, after doing so, start the machine with build 918.

I found the problem...

I forgot I only ran the driver on device ID 0x7111 (if found) during testing of the driver in kernel.c.


[prometheus-nut-exporter] migrate to common

Description of the change
Migrate prometheus-nut-exporter to the common library
Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[x] (optional) Chart is using our common library as a dependency.
[x] (optional) Variables are documented in the README.md

@all-contributors add @onedr0p for code


[docs] Mention delay instead of transition twice

fix typo

[ ] I have followed (at least) the PR section of the contributing guide.

Thanks!


[SPARK-48392][CORE] Also load spark-defaults.conf when provided --properties-file

What changes were proposed in this pull request?

Currently if a property file is provided as argument to Spark submit, the spark-defaults.conf is ignored. This PR changes the behavior such that spark-defaults.conf is still loaded in this scenario, and any Spark configurations that are in the file but not in the input property file will be loaded.
Why are the changes needed?

Currently if a property file is provided as argument to Spark submit, the spark-defaults.conf is ignored. This causes inconveniences for users who want to split Spark configurations into the two. For example, in Spark on K8S users may want to store system wide default settings in spark-defaults.conf, while user specified configurations that are more dynamic in an property file and pass to Spark applications via --properties-file parameter. Currently this is not possible. See also https://github.com/kubeflow/spark-operator/issues/1321.
Does this PR introduce any user-facing change?

Yes, now when a property file is provided via --properties-file, spark-defaults.conf will also be loaded. However, those configurations specified in the former will take precedence over the same configurations in the latter.
How was this patch tested?

Existing tests and a new test.
Was this patch authored or co-authored using generative AI tooling?

No

cc @viirya @dongjoon-hyun @cloud-fan let me know what you think

I think this proposed behavior looks reasonable to me. If there is any document on this, we probably need to update it too.

Thanks @viirya . There is a related documentation here: https://spark.apache.org/docs/latest/configuration.html#dynamically-loading-spark-properties. It looks like the behavior change in this PR is consistent with the description there:

Any values specified as flags or in the properties file will be passed on to the application and merged with those specified through SparkConf. Properties set directly on the SparkConf take highest precedence, then flags passed to spark-submit or spark-shell, then options in the spark-defaults.conf file.

Do you also think we should add an item to migration guide for this?

Yes sure. I can add this to the migration guide as a separate PR afterwards.

Thanks @viirya . There is a related documentation here: https://spark.apache.org/docs/latest/configuration.html#dynamically-loading-spark-properties. It looks like the behavior change in this PR is consistent with the description there:

Yea, but seems it doesn't mention how does --properties-file work with spark-defaults.conf. Maybe we can add few words there too.

Yea makes sense. Just updated the doc too.

Thanks! merged to master/4.0

You need to update all the usage information for commands with --help

@yaooqinn do you mean the --help from spark-submit / spark-shell? currently the usage about --properties-file is as follow:
  --properties-file FILE      Path to a file from which to load extra properties. If not
                              specified, this will look for conf/spark-defaults.conf.

which I think is also consistent with the behavior here although not complete? I can add more info there.

--properties-file FILE   Path to a custom Spark properties file. Default is conf/spark-defaults.conf.

Do the commands with the above message also get affected?

No they are not affected. The change in this PR is only in SparkSubmitArguments. Classes such as HistoryServerArguments calls Utils.loadDefaultSparkProperties.

I'm not sure if such an implicit discrepancy is user-friendly or not.

spark-defaults.conf --> which stores the default cluster settings
spark-cluster-a.conf --> which stores the cluster settings for cluster a
spark-cluster-b.conf --> which stores the cluster settings for cluster b

For the properties defined in spark-cluster-a.conf, it will be effective. So any duplicate properties defined in spark-defaults.conf as default ones, will be overwritten. I think this still follows original behavior.
For what is described, it seems giving this change more support? As users can put common default ones in spark-defaults.conf and apply them to all clusters. Only the different properties need to be defined in separate files.

+1 on what @viirya said.
@advancedxy to be clear the configurations from spark-cluster-a.conf will still take higher precedence than those from spark-defaults.conf, and I do think this is more aligned with the purpose of spark-defaults.conf. This also addresses an inconsistency in the current implementation: for configurations passed through --conf flags, Spark will still load spark-defaults.conf, but it will not for those passed from --properties-file, which is a bit confusing.
Since we are preparing a new major release, I'm just hoping to take the opportunity to improve this. This is also important for kubeflow Spark k8s operator users, since currently there is no way to separate system-wide default configurations and user and job specific configurations.

IIUC, we want to have a way to load the default config files, and it's cleaner if --properties-file can do it. However, I do share the same concern of @advancedxy . Adding --extra-properties-files won't hurt and you can use this new option to load the default config files. Then we can leave --properties-file unchanged and avoid the risk of breaking Spark users during version upgrade.

BTW, I agree that it's a better behavior to just let --properties-file load the default config file. We should have used this behavior on the first day. But now I think it's a bit overkill to make a breaking change just for a cleaner API. --extra-properties-files should be sufficient functional wise.

+1 for --extra-properties-files.
As a maintainer of Apache Kyuubi, which supports multitenant and multi-runtime environments. This change might pollute an isolated custom spark conf.

Thanks for all the feedback! Let me re-purpose the follow up PR #46782 to add this extra flag then (and we no longer need to update the migration guide). One minor inconvenience is we'd also need to update kubeflow k8s operator to consume this flag, and then users of the operator need to upgrade first in order to use this. I'll make a PR there too.


Correct F# versions

F# 4.7 has been in .NET Core 3.0 since preview 7

The 3.0.0 final release also has version 4.6 listed.
@leecow Is this something that should also be fixed on your end?

Yep, thanks for the cc.


Zoom image show when taking picture from camera

i am using this library, its working fine but only getting issue when i captured image from camera...
when i am taking image from camera then goes for crop ,its automatically zoom image show. is there any solution for that? and working proper when take from gallery.

Can you post the code you use to create capture image from camera, get the captured uri and how you set it for cropping.

i use this code for open dialog
  public void onSelectImageClick() {         Utils.keyboardHide(this);         CropImage.startPickImageActivity(this);     }
then  for cropping
 private void startCropImage(Uri imageUri) {         CropImage.activity(imageUri)                 .setGuidelines(CropImageView.Guidelines.ON).setFixAspectRatio(true)                 .start(this);     }
and then
` @Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
super.onActivityResult(requestCode, resultCode, data);
if (requestCode == CropImage.PICK_IMAGE_CHOOSER_REQUEST_CODE && resultCode == Activity.RESULT_OK) {
Uri imageUri = CropImage.getPickImageResultUri(this, data);
startCropImage(imageUri);
}
// handle result of CropImageActivity
if (requestCode == CropImage.CROP_IMAGE_ACTIVITY_REQUEST_CODE) {
CropImage.ActivityResult result = CropImage.getActivityResult(data);
resultUri = result;
if (resultCode == RESULT_OK) {
loadImage(profileImageView, result.getUri().getPath());
        } else if (resultCode == CropImage.CROP_IMAGE_ACTIVITY_RESULT_ERROR_CODE) {
            Toast.makeText(this, "Cropping failed: " + result.getError(), Toast.LENGTH_LONG).show();
        }
    }
}`

do you see the same issue when you run the sample app?

i have to check sir..please wait for 15 minutes i will check this issue in sample app...

i checked in sample app it is fix...no option to zoom image when capture image or fetch from gallery so not possible to check it properly

hmmm.... I'm not sure what you mean by zoom, you are not talking about the auto-zoom feature of the library it seems.

i think problem is in my code....so please close this issue and thanks for help...i checked the sample app properly and with changes its working fine..thanks sir

No problem, happy to be of some help, it is always good to check with a working code sample.
It will be also great to explain in a few words what was the issue, other people may encounter it and reach this page via google.
Feel free to close the issue yourself too :)

my captured image like this

after captured its showing like this...

ya same problem with me after pressing save it takes complte zoom

this is my issue. i want same image show without zoom for crop after capturing from camera

heyy arpit in the sample app it works properly but at the same time same code it gives issues as u mentioned earlier...ny help will be really apriciated

ArthurHub  i am not closing issue this time because i am getting issue still yet.. i shared images so please check ..

what's different between your code and the sample app?
maybe something in initialization...

Sorry for late reply  .... i used this setAutoZoomEnabled(false) now its working properly thanks  ArthurHub  for help ....

You just disabled the auto-zoom feature :(
It is possible that there is a bug in the library but I don't understand how to reproduce it... you said that you can't reproduce it in the sample app because "no option to zoom image when capture image", I have no idea what it means...
@ashishCDN0135 also mentioned he has this issue so probably it is a thing, but he didn't give any more info to go on...
This make me very sad :disappointed:

actually ArthurHub there were two sample app in this module on the time of my comment i was tested second sample app which contain only function of taking picture from gallery and camera....then i checked next one which contain all also included zoom of or on ....so sorry for that..for me library so helpful and working properly in my code ...thanks for help....and close this issue


Add ability to tag/group services for filtered service view

We love portainer, and we are running a lot of services, and that services list is getting a little hard to maintain.
If we could group them, into clienta, clientb, internal, webserver, db etc it would be nice to be able to filter the service list by those groups.
Maybe having tags, for cross filtering might be nice.

I think leveraging that would be easiest... and make the most sense.
A select2 type filter would be nice. Not sure if there is enough real estate to show the labels in the list view.


Add RequiersPermission annotation for setRequireOriginal api

Hello, I add RequiresPermission annotation for flipImageHorizontally and flipImageVertically method.
Thanks for your reply!

Thank you!


Error: can't convert Fixnum into String

I get the
Error: can't convert Fixnum into String

When i try to install anything.
~$ brew config
HOMEBREW_VERSION: 0.9.5
ORIGIN: git://github.com/Homebrew/linuxbrew.git
HEAD: 46013be9b4019b3186ceacf39e0acb636382a269
Last commit: never
HOMEBREW_PREFIX: /home/test/.linuxbrew
HOMEBREW_REPOSITORY: /home/test/.linuxbrew
HOMEBREW_CELLAR: /home/test/.linuxbrew/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://linuxbrew.bintray.com
CPU: 8-core 64-bit ivybridge
OS X: 0-x86_64
Xcode: N/A
CLT: N/A
Clang: N/A
X11: 2.7.8 => /usr
System Ruby: 1.8.7-p72 => /usr/bin/ruby
Perl: /usr/bin/perl
Python: /usr/bin/python => /usr/bin/python2.6
Ruby: /usr/bin/ruby
Java: N/A

The complete output is:
~$ brew install git
==> Installing dependencies for git: xz, pkg-config, makedepend, zlib, gpatch, openssl, curl, expat
==> Installing git dependency: xz
==> Downloading https://fossies.org/linux/misc/xz-5.2.2.tar.gz
Already downloaded: /home/test/.cache/Homebrew/xz-5.2.2.tar.gz
Error: can't convert Fixnum into String
Please report this bug:
    https://github.com/Linuxbrew/linuxbrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting
/usr/lib64/ruby/1.8/fileutils.rb:987:in `fu_get_gid'
/usr/lib64/ruby/1.8/fileutils.rb:926:in `chown'
/home/test/.linuxbrew/Library/Homebrew/extend/fileutils.rb:26:in `mktemp'
/home/test/.linuxbrew/Library/Homebrew/resource.rb:88:in `unpack'
/home/test/.linuxbrew/Library/Homebrew/resource.rb:81:in `stage'
/home/test/.linuxbrew/Library/Homebrew/formula.rb:1539:in `stage'
/home/test/.linuxbrew/Library/Homebrew/formula.rb:922:in `brew'
/home/test/.linuxbrew/Library/Homebrew/build.rb:108:in `install'
/home/test/.linuxbrew/Library/Homebrew/build.rb:177

This is a x64 sles 11 service pack 1.
The relevant part from the mentioned file is:
    begin
      chown(nil, group_id, tmp)
    rescue Errno::EPERM
      opoo "Failed setting group \"#{Etc.getgrgid(group_id).name}\" on #{tmp}"
    end

Please report ruby --version. If you can, upgrading Ruby will like resolve this issue.

Never mind. Ruby 1.8.7, from above output.

I comment those lines in fileutils.rb and tried to update ruby, but this fails with:
==> Applying mkconfig.patch
patching file tool/mkconfig.rb
==> ./configure --prefix=/home/test/.linuxbrew/Cellar/ruby/2.3.0 --enable-shared --disable-silent-rules --with-sitedir=/home/test/.linuxbrew/l
==> make
Last 15 lines from /home/test/.cache/Homebrew/Logs/ruby/02.make:

[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html

make: *** [encdb.h] Aborted
make: *** Waiting for unfinished jobs....
/tmp/ruby20160216-11768-hr5o5p/ruby-2.3.0/lib/fileutils.rb:1155:in `rescue in block in touch': uninitialized constant Errno::ENOENT (NameError)
        from /tmp/ruby20160216-11768-hr5o5p/ruby-2.3.0/lib/fileutils.rb:1153:in `block in touch'
        from /tmp/ruby20160216-11768-hr5o5p/ruby-2.3.0/lib/fileutils.rb:1151:in `each'
        from /tmp/ruby20160216-11768-hr5o5p/ruby-2.3.0/lib/fileutils.rb:1151:in `touch'
        from ./tool/mkconfig.rb:298:in `<main>'
rbconfig.rb updated
make: *** [.rbconfig.time] Error 1

Please report brew gist-log ruby.
You may want to report the bug upstream to Ruby at http://www.ruby-lang.org/bugreport.html

chmod is supposed to be able to take an Integer or a String, so I'm not really sure what's going on here. Sorry. Perhaps it's a bug in Ruby 1.8.7.
Commenting out the chgrp line seems a reasonable workaround to install Ruby 2.3.0 using Linuxbrew.

It is chown, not chmod. The failure happens when it tries to change the group of a temporary folder. @sni  can you make sure that you can change group in the $HOMEBREW_TEMP folder? Just do: cd $HOMEBREW_TEMP && mkdir delete_me && chown $USER:<yourgroupname>? Did you by any change install coreutils before that? I have an issue with coreutils: after I install it, my whoami command returns numbers and it breaks a lot of things...

Typo, sorry. I meant chown. It also takes an Integer or a String.

Changes owner and group on the named files (in list) to the user user and the group group. user and group may be an ID (Integer/String) or a name (String). If user or group is nil, this method does not change the attribute.