If I have 2 OpenSprinkler units, how is the best way to set them up via this plugin?

Describe Your Problem:
I have 2 open sprinkler systems, what is the best way to setup the 2 units via this plugin?

Thanks mate for the reply. In the interim is there another plugin I can use to get the 2 open spinkler units working on the 1 homebridge RPI? Eager to get both my sprinklers work now that its spring in Sydney.

Yeah so I know nothing about the other opensprinkler plugins. But, it does seem like it’s pretty easy to set up multiple homebridge instances. Check out this doc: https://github.com/oznu/homebridge-config-ui-x/wiki/Homebridge-Service-Command#multiple-instances
I’ll get working on that functionality as soon as I can though. Sorry that it isn’t available now!

Perfect, thanks so much for the responsiveness.

So it looks like you have multiple OSBee units so that must be what you're trying to use the plugin for? Since the OSBee API is so different I don't think I'll be able to support it. I wish it was an easy fix to help you out, but it isn't. I do think though that it's probably a good idea to bring the multiple unit support to the plugin.


Don't emit Ruby warnings when requiring opensearch-dsl

Description
The removed define_method in options.rb just ensured that you are able to use source and _source, that's all this does. The other entries where this isn't a problem are simply overwritten, as you can see from the warnings. Just switch to handwriting this one special case.
The second change removes a option_method :max_expansions from match.rb. This previously appeared twice in the list and also caused a warning.
$ RUBYOPT=-w bundle exec irb
irb(main):001> require "opensearch-dsl"
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old fields
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of fields was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old script_fields
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of script_fields was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old fielddata_fields
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of fielddata_fields was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old rescore
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of rescore was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old explain
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of explain was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old version
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of version was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old indices_boost
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of indices_boost was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old track_scores
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of track_scores was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old min_score
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of min_score was here
opensearch-ruby/lib/opensearch/dsl/search/options.rb:59: warning: method redefined; discarding old track_total_hits
opensearch-ruby/lib/opensearch/dsl/search/options.rb:55: warning: previous definition of track_total_hits was here
opensearch-ruby/lib/opensearch/dsl/search/base_component.rb:75: warning: method redefined; discarding old max_expansions
opensearch-ruby/lib/opensearch/dsl/search/base_component.rb:75: warning: previous definition of max_expansions was here
=> true

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Woah. Nice catches! Thank  you!!


Stable imageurl

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

Make imageUrl props stable

❓ Shouldn't we mark as @deprecated the legacy profileImageUrl? Or will we do this on v5?

https://github.com/clerkinc/javascript/pull/1239#discussion_r1203906892


add flush option to hdf5 write_metadata

Fixes issue with HDF5 files that are not properly closed.
When metadata is written after the main data has been written, the HDF5 file was properly closed. This could lead to currupt HDF5 files. This PR fixes the issue by flushing the HDF5 file by default after writing the metadata.
@jenshnielsen @WilliamHPNielsen

@astafan8 The PR passes all tests.


Move to fabric8-kit's BuildService

Remove dependency on dmp and move to "BuildService" API from the https://github.com/fabric8io/fabric8-kit library.

Implement an S2I BuildService

Think about Jibn implementation

@lordofthejars @dev-gaur Actually this would be the starting point for the GSoC project dealing with Jib or Buildah.

https://github.com/jshiftio/jshift-kit has been created.


Hot Restart from Google's source code/build environment crashes component on <elided configuration & hardware>

https://buganizer.corp.google.com/issues/159167220.

engine.cc(436)] Could not configure some native embedder bindings for a new root isolate.

Comment on the issue: fuchsia devices do not support hot restart. This is disabled in the flutter_tool, and would likely need to be disabled in google3 as well.


[BUG]

Description
cms.admin.ContentForm overwrites attributes of slug widget.
Steps to reproduce
When setting the attributes of a slug widgets, these attributes are overwritten in
https://github.com/django-cms/django-cms/blob/3e3a86b4f09c021bb4548add090f441b300a4a9e/cms/admin/forms.py#L222
This is unexpected behavior.
Additional information (CMS/Python/Django versions)
Branch develop-4. Latest commit hash: 52e6f8751e2d28db7c2abb6bdbbbc9c9909ba03d
All Django/Python versions.
Do you want to help fix this issue?
I have a patch. PR upcoming.

[x] Yes, I want to help fix this issue and I will join #workgroup-pr-review on Slack to confirm with the community that a PR is welcome.
[ ] No, I only want to report the issue.

@jrief Can we close this?


Clean up docs for the execution_summary module

It looked good when I tox -e docsed it. So I'll just merge. :)


fix: use the unused minRating prop

Changes

Use the minRating props as the minimum value Math.max function. (This props was unused before)

Checklist
I assured that:

[x] The component works as expected with the minRating prop

I removed the minRating prop at some point since it is pretty easy to implement it yourself in the onChange function. It was removed in the context of this issue: https://github.com/bviebahn/react-native-star-rating-widget/issues/19
I guess I forgot to remove it from the type. If you want you can update this PR to do that. Thanks.

I deleted the minRating that I added. Also I deleted minRating from prop types

Yes exactly. Great, thank you! 👍

@bviebahn please remove use the unused minRating prop from changes of the new release to avoid confusion. 🙌


add license

You are violating your own license by not distributing it with the code:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

Also, I think we can agree that letting everyone know that:

you wrote this software
it's copyfree/open-source software

is beneficial.

Thanks


Add proteomicsLFQ modules.

We need to add the proteomics LFQ modules to the pipeline.

Is your feature request related to a problem? Please describe

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Done


OverflowError

Bug Report

run tx.run("MERGE (a:Person {id: $id}) ", id=10000000000000) get OverflowError: Integer<PHONE_NUMBER>0000 out of range
My Environment
Python Version: 3.11.2
Driver Version: 5.6.0
Server Version and Edition: 5.6.0 community
Operating System: Windows 10

Hi and thanks for reaching out. This is a limitation of the DBMS (and is also reflected by the protocol). If you look here https://neo4j.com/docs/api/python-driver/current/api.html#core-data-types you'll see that the DBMS is using long to store integers. So this limits all integers going through neo4j to be in the range -2147483648 <= x <=<PHONE_NUMBER>


dandelion=0 Does Not in Fact Seem to Disable Dandelion

Actual behaviour
After putting dandelion=0 in zcoin.conf or appending it to the zcoind -daemon command line, Dandelion log messages are still being produced
Desired behaviour
Dandelion should be disabled and not produce any more log messages
Steps to reproduce

Deactivate Dandelion
Still find new Dandelion log messages being written to debug.log

dandelion=0 makes a node passing txes directly to mempools, bypassing the Dandelion stem pool broadcasting mechanism. At the same time, the node may take part in the Dandelion stem pools, providing the Dandelion functionality for the nodes with enabled Dandelion. That is where the Dandelion log messages come from.

Makes sense. Thanks for the explanation!


Improve overall new examples' accessibility

Small tweaks caught by Pa11y on Boosted. Mostly:

ensuring having main and h1 on each page,
a few input missing a label,
some redundant alt on img inside a link,
contents not wrapped in a landmark.

I ignore some other errors since they're not applicable for such snippets IMHO (several banner roles instead of one, for example).
Non-whitespace diff: https://github.com/twbs/bootstrap/pull/33772/files?w=1

Note that my requested changes (the addition of aria-current) are admittedly snuck in here - they're not new things added/done by this PR, but as I stumbled across them...would be good to sneak those in too. other than that this PR looks good to me.


Fix crate name in README.md

@Noah-Kennedy Want to take a look or squash and merge? It was my typo but you have to do the releases and getting notes updated and so forth.


UrJTAG: error: libusb error: libusb_init() failed: 6

jtag> cable dirtyjtag
error: Couldn't connect to suitable USB device.
error: libusb error: libusb_init() failed: 6
jtag>
Shows up properly in lsusb and dmesg

Hi,
It probably is a permission error. The short and hacky solution would be to run openFPGALoader/UrJTAG/whatever as a root user. The long and cleaner solution is to setup udev rules.

Unfortunately running as root and sudo both result in the same result, same with openFPGALoader

Don't worry I can reopen issues.
Can you give me more information that could help me reproduce the issue?

Which hardware platform are you using?
What firmware version are you using? Did you compile it yourself?
What operating system are you using?

Closing issue due to lack to reply from original poster. Feel free to comment if the issue persists, I'll re-open the issue.


onChange does not return any value

Hey, i tried to use this slider but the onChange function seems to not fire?

The slider itself does display the right way:

Any idea?
Greetings,
Chris

Okay i found out how to use the onChange :)

How did you do it in the end? I'm running into the same issue here …

I had placed onChange at the wrong position. This is my working solution:
`    ////// Start - Range slider
/////////////////////////
var rangeSlider = new rSlider({
    target: '#rangeSlider',
    values: [0, 1, 2, 5, 10, 30, 50],
    range: true,
    tooltip: false,
    scale: true,
    labels: true,
    set: [0, 50],
    onChange: function (vals) {
        let sliderValues = vals.split(',');
        tableMinPrice = sliderValues[0];
        tableMaxPrice = sliderValues[1];
        createTable();
    }
});`


Is it necessary to train a backbone before I train the model?

I wonder if I must train a backbone by runing:

sh scripts/${DATASET}/train_${DATASET}_backbone.sh

before I run the train  command:

python train.py --cfg_file ${CONFIG_FILE}

Or, can I just run the second command directly without running the train backbone command at first?

You need to train backbone first by setting the TRAIN_RESUME: False.
Once the backbone training is done, set TRAIN_RESUME: True, and python train.py --cfg_file .

Thanks so much for your help and it works!


 After I save the config and reload the page, an empty "Update commit status during build" block has reappeared.
It also appears to override the "do not update commit status" block, so running the job results in a commit status being sent to github (with the default name "default") instead of nothing being sent.

same issue

I'm also experiencing this issue, has anyone found a workaround for it yet?

Do you have any global settings which could interfer? "default" is normally coming the global config.

As far as I'm aware, there's no global setting which interferes. After all, I can change the configuration to be one of the various options and they all work fine AFAIK... except for "Do not update commit status".

I could workaround this issue by setting all messages to --none--.


Review consequences of Cuda 7 Independent Thread Scheduling on warp-synchronicity assumptions

From https://github.com/data61/cuda-fixnum/issues/45:

Guidance is provided here.

Article on things to look for: https://devblogs.nvidia.com/using-cuda-warp-level-primitives/


Add mean Earth radius to constants

Cannot you please add mean earth radius to constants?
6,371,000 m is OK.

Is there an authoritative source for this number? And does it make sense to add just this one, or is there a larger set of astronomy related metrics that would make sense?

Well, we got it from MATLAB's Phased Array System Toolbox.
http://www.mathworks.com/help/phased/ref/physconst.html
We need it to calculate reflections from the earth in one of our Python projects.

If you want a more complete set, maybe a Particle Data Group constant set will be OK?
Alas, there is no mean Earth radius (only mean equatorial), but the handbook is well-known among scientists.

Hmm, we now have a fairly well-defined set of fundamental physical constants; adding this one because Matlab has it is maybe a bit random. Can you run this by the scipy-dev mailing list?

Well, if want a more balanced astronomical constant set, we can take NASA's one.
I think my Earth mean radius was taken from there.
http://nssdc.gsfc.nasa.gov/planetary/factsheet/earthfact.html
And the ones related with Sun and Moon, for example:
http://nssdc.gsfc.nasa.gov/planetary/factsheet/moonfact.html
http://nssdc.gsfc.nasa.gov/planetary/factsheet/sunfact.html
P.S. I don't even know where is the scipy-dev mailing list. Mayby you'll do it? Or give me a link?

Would be great if you could do this @Felix-neko. List info is at http://scipy.org/scipylib/mailing-lists.html
I'm fine with expanding the scope of constants with those sets of data, because the maintenance overhead will be very low. I could imagine that people may find it too domain specific though and that it would better fit in AstroPy.

NASA says this about their fact sheets:
Most values listed in the factsheets are from the following sources:
  IAU/IAG Working Group Report, 2006
  Astronomical Almanac, 2000, 2001
  Global Earth Physics, American Geophysical Union, 1995
  Astrophysical Quantities, C.W. Allen, 1981, 2000
  Recent journal articles and personal communications

Note that the values listed on the factsheets are not "official" values,
there is no single set of agreed upon values.  They are based on ongoing
research and as such are under study and subject to change at any time.
Every effort has been made to present the most up-to-date information,
but care should be exercised when using these values.

If you want more constants, Astropy has a reasonable selection, including
an Earth radius, tagged with units:
http://astropy.readthedocs.org/en/latest/constants/index.html
Anne
On Tue, Jun 9, 2015 at 2:48 PM Eric Moore<EMAIL_ADDRESS>wrote:

NASA says this about their fact sheets:
Most values listed in the factsheets are from the following sources:
IAU/IAG Working Group Report, 2006
Astronomical Almanac, 2000, 2001
Global Earth Physics, American Geophysical Union, 1995
Astrophysical Quantities, C.W. Allen, 1981, 2000
Recent journal articles and personal communications
Note that the values listed on the factsheets are not "official" values,
there is no single set of agreed upon values.  They are based on ongoing
research and as such are under study and subject to change at any time.
Every effort has been made to present the most up-to-date information,
but care should be exercised when using these values.
—
Reply to this email directly or view it on GitHub
https://github.com/scipy/scipy/issues/4943#issuecomment-110346715.

@aarchiba thanks, that helps. If AstroPy already has them, probably not a good idea to add them to Scipy?

Agreed, no reason to make redundant constants for everything above the atmosphere if AstroPy is implementing them!
However, I don't know if there is a GeographyPy, etc... but the Earth radius is generally useful for many scientific disciplines, as is c and G, which SciPy includes.
I vote add R_earth

Was this ever implemented?  This is a very common unit in space physics and I think it brings value to scipy.

Note that I know of
👍

but the Earth radius is generally useful for many scientific disciplines, as is c and G, which SciPy includes.

There's an important difference there: c and G are fundamental constants, so uniquely defined and shipped as part of CODATA. R_earth isn't - https://nssdc.gsfc.nasa.gov/planetary/factsheet/earthfact.html alone has 4 different definitions for an earth radius (equatorial, polar, volumetric, and a rounded 6378 km).
In the absence of follow-up on the mailing list and no consensus, I'm going to close this issue as wontfix.


Hello
I'm built flutter android app successfully . and now I'm converting to flutter web. but I have been a problem with all URL (Get & Post request)  is there any way to fix this issue?
Flutter 1.18.0-11.1.pre • channel beta

Hi @harithany
It's not clear what the error do you have.
could you provide your error log and a minimal complete reproducible code sample, and your flutter doctor -v?

Thanks for response
this is chrome console
Access to XMLHttpRequest at 'https:/mydomian.com/api/apisearch' from origin 'http://localhost:10265' has been blocked by CORS policy: The 'Access-Control-Allow-Origin' header contains multiple values 'http://localhost:10265, *', but only one is allowed. mydomain.com/api/apisearch:1 Failed to load resource: net::ERR_FAILED
and this is flutter doctor
`[√] Flutter (Channel beta, 1.18.0-11.1.pre, on Microsoft Windows [Version
10.0.18362.836], locale en-US)
• Flutter version 1.18.0-11.1.pre at C:\flutter
• Framework revision 2738a1148b (3 weeks ago), 2020-05-13 15:24:36 -0700
• Engine revision ef9215ceb2
• Dart version 2.9.0 (build 2.9.0-8.2.beta)
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)    • Android SDK at C:\Users\Harith\AppData\Local\Android\Sdk
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = C:\Users\Harith\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b03)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 3.5)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 39.0.3
• Dart plugin version 191.8423
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b03)
[√] Connected device (2 available)
• Web Server • web-server • web-javascript • Flutter Tools
• Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.61
• No issues found!`

@harithany
You may get some help if you post it on Stack Overflow or https://www.reddit.com/r/flutterhelp/.
Closing since this platform is not meant for assistance on personal code and this doesn't look like an issue with flutter.
if you disagree please write in the comments and I will reopen it

@VladyslavBondarenko
I disagree with you . post and get requests have issue with flutter web . you can write in google search (flutter web post request ) you can see many of issue . flutter web in dev channel and have some troubleshoot .  and this  platform if not help us in this case . for any case help ?

@VladyslavBondarenko
A simple google search after the error you are getting in Chrome console would point you in the right direction.
Your remote server does not have CORS setup properly so the browser is blocking your request.

@harithany
I don't know what you are using as server, but removing the 'Access-Control-Allow-Origin' '*' header may be a solution https://github.com/nelmio/NelmioCorsBundle/issues/40#issuecomment-310044311

Sorry @VladyslavBondarenko , I tagged you by mistake, my message was for @harithany


adapt to azure openai

Thank you for your work, this is very helpful.
do you think you can provide me with something to test this manually, I don't have access to Azure AI...


Sphinx documentation does not render

tsbootstrap version: 0.0.3
Python version: 3.10
Operating System: Ubuntu 20

Expected behavior
Sphinx documentation to be built properly and rendered on github
Actual behavior
However, it renders correctly on my local system but not online
Code to reproduce the problem
cd docs
poetry run make html

Then open docs/build/html/index.html in a web browser to view your generated documentation.

@astrogilda, why are we not getting a readthedocs build off PR?
Have you activated the integration?

@astrogilda, why are we not getting a readthedocs build off PR? Have you activated the integration?

Yep! pushed this just now. opening a pr.


add uspb.deno.dev

try add screenshot but got an error:
(base) ubuntu@honer:~/github/deno/fresh$ deno task screenshot https://uspb.deno.dev uspb
Task screenshot deno run -A www/utils/screenshot.ts "https://uspb.deno.dev" "uspb"
error: Uncaught Error: Could not find browser revision 1022525. Run "PUPPETEER_PRODUCT=chrome deno run -A --unstable<EMAIL_ADDRESS>to download a supported browser binary.
      if (missingText) throw new Error(missingText);
                             ^
    at ChromeLauncher.launch (https://deno.land/x/puppeteer@16.2.0/src/deno/Launcher.ts:99:30)
    at eventLoopTick (ext:core/01_core.js:183:11)
    at async file:///home/ubuntu/github/deno/fresh/www/utils/screenshot.ts:24:17

Can anyone run this cmd for me or I just take a screenshot manually?


Not updating view, when AppServiceProvider changes.

Issue
When making changes in boot() inside AppService provider as follows:
    /**
     * Bootstrap any application services.
     *
     * @return void
     */
    public function boot()
    {
        Blade::directive('datetime', function($expression) {
            return "<?php echo with{$expression}->format('m/d/Y H:i'); ?>";
        });
    }

Changes are not applied to cashed views. For them to apply you need to go to the view itself and re-save  it.
Solution
Update all views (or at least ones containing the function specified in Blade::directive()) when saving AppServiceProvider (or any ServiceProvider containing Blade::directive()).

This is NOT a big. You MUST manually clear the cached views after making such changes.

Your work around is incorrect btw. You should just clear the cached views out. We have an artisan command for that, or you can just delete the files in the view cache folder by hand if you wish.

Yes, I know you need to delete cached views. But it's not that intuitive and may cause a big headache for starting developers...

At least documentation should at least mention that.

Try to run php artisan view:cache to manually clear the view cache after that it will works. In my case i have changed on boot() method.  after view not getting new changes. so i clear the view cache manually and its works

Try to run php artisan view:cache to manually clear the view cache after that it will works. In my case i have changed on boot() method.  after view not getting new changes. so i clear the view cache manually and its works

"php artisan view:cache" works! Thank you!


SFH- Accession ID discrepancies

This week's QC report flagged the following Accession ID discrepancies, please investigate:

There were also others that we can ignore that were flagged due to "." between IDs vs. "," and extra spaces. Please note that there is a considerable amount of work involved in cleaning up these issues, it is imperative that SFH work to ensure back end clinical collection data processes are improved to cut down on manual entry. And, if/when manual entry is needed, please emphasize to team members the importance of ensuring it is correct. Thanks!

@erincschwartz  I tagged myself in this, but rereading the issue it seems that maybe SF needs to be tagged in this instead?

Added to this board in error. Deleting.


Better Discord for Mac

The betterdiscord site has the MAC download grayed out. I just want an answer, yes or no, whether it works for OSX or not. If so, could I get some help? Thanks in advance!

@EphemeralHope He was supposed to be working on a Mac version installer last I remembered.

@Outsanity Thanks! Looking through the other posts about OSX, people are just giving too many answers I dunno which one is true. :)


Fix typo in keyboard manager

A small PR to fix a grammatical error in one of the UI strings in the keyboard manager module.
Tests, documentation and everything should be irrelevant as this is just a small typo fix.

@christianlw 100% agree on the fix, can you please create an issue so we can give you credit in release notes?

Sure, it's issue #24032


Helm detects wrong state when chart contains envFrom

EnvFrom is a kubernetes v1.6 feature, but helm uses kubernetes v1.5 as dependency. When I try to update a release that uses EnvFrom, helm will fail with Error: UPGRADE FAILED: failed to create patch: unable to find api field in struct Container for the json field "envFrom" -- which is fine, given helm does not support this yet.
When I run the same upgrade command again, helm will copy a new state as ConfigMap in namespace kube-system and pretend the upgrade was successful. The actual state of the release does not change (upgrade), though.

So your process was:

install without envFrom
upgrade to a release with envFrom (FAILED)
upgrade again with env from (FALSE SUCCESS)

What resource type were you adding envFrom to? And was it running after the second upgrade?

The resource type is a deployment. The process was

install with envFrom (TRUE SUCCESS)
upgrade to a release with an arbitrary change (FAILED)
upgrade again w/o further change (FALSE SUCCESS)

The deployment did not change its actual state since step 1.
I assume the first install is a success because there is no attempt to diff. Our workaround is to delete and install the chart anyway due to the lacking feature. But the issue at hand is helm's lying about the actual state.

Yeah, I think it must be that the second kube diff operation does not generate anything. /cc @adamreese

Is there a workaround for this other than not using envFrom?

The only workaround I know is to helm delete the chart and then helm upgrade --install it again. If that's not an option for you (e.g. rolling update), I guess you'll have to abstain from envFrom since as of now helm creates an undefined state.
Note that this issue is not about a lacking feature, but lacking robustness in face of an unknown feature. I.e. this is rather an important bug report, not a question/support ticket @technosophos. ;)

We are running into a similar problem with DaemonSet and   updateStrategy:     type: RollingUpdate

@wjkohnen what version of helm are you using?  1.6 features are supported in helm v2.4

There are really three problems that contributed to this bug.
The particular problem with envFrom (rooted in Kubernetes changed schemas between 1.5 and 1.6) was resolved in Helm/Tiller >= 2.4.1. That alone is probably enough to close this particular issue.
With Deployments and DaemonSets, there are added problems with the fields they silently treat as immutable. These are documented in the Kubernetes docs, but not schematized. There's not really much Helm can do about those. In those cases, schema validation passes, but Kubernetes ignores all "immutable" fields.
Finally, there's the case where resource definitions get out of sync between Tiller and Kubernetes. That's a well-understood problem without an obvious solution. There has long been talk of fixing the Kubernetes apply logic, which we could then utilize. But in the near term we haven't devised an elegant solution.
We need to decide on a single issue to treat as the definitive one for the out-of-sync problem, and then close the rest.

@technosophos can we please have this labeled as a bug

there's the case where resource definitions get out of sync between Tiller and Kubernetes. That's a well-understood problem without an obvious solution.

I am sorry, but solution is also well understood and was mentioned multiple times: store SUCCESS/FAILURE states per individual resource, rather than whole manifest. then generate patches  against last successful resource version, not last manifest irregardless of its version like it is happening now.

@redbaron, please be nice.
I assume this is the key point in the discussion here that is blocking it from happening:

There has long been talk of fixing the Kubernetes apply logic

If this assumption is wrong and you have a patch that fixes it to save state from each individual resource, please feel free to contribute a fix!

I'm going to close this issue as helm uses the kubernetes 1.8 client libraries, so the issue OP mentioned was fixed a long time ago.

The particular problem with envFrom (rooted in Kubernetes changed schemas between 1.5 and 1.6) was resolved in Helm/Tiller >= 2.4.1. That alone is probably enough to close this particular issue.

For anything else, please open a new issue so we can track that discussion separately. Thanks.


add build success/fail counts to metrics

This PR adds four new records to the /about/metrics endpoint:

The total number of crates built in the last six hours
The number of crates built successfully in the last six hours
The number of crates which failed to build in the last six hours, due to a compile error
The number of crates which failed to build in the last six hours, due to being flagged "not a library"

By making the metrics a sliding window of "the last six hours", we can better track the rate of failures, rather than any individual success/failure count. For example, calculating failures / total builds, we can get a rolling calculation of our build failure rate.
(It would be really cool to have some kind of inspection of the build logs to flag errors due to build scripts, pkg-config failing, etc, to get an idea of crates that need some kind of system dependency versus those that may be due to our own build configuration causing an issue, but queries on the build output take too long to be repeatedly polled. Perhaps something like that can be tracked as a counter that is incremented after a build finishes, rather than a query that's repeatedly executed.)
cc @pietroalbini

By making the metrics a sliding window of "the last six hours", we can better track the rate of failures, rather than any individual success/failure count. For example, calculating failures / total builds, we can get a rolling calculation of our build failure rate.

I'd still prefer to use a counter that shows data for all time (either backed by the database or incremented on the fly, letting prometheus dealing with resets). That gives us way more flexibility while graphing and alerting. For example, the same behavior in this PR can be replicated with a counter and the query increase(docsrs_metric_name[6h]).

Thanks!


Draft: feat(auth): add forgot password feature

add forgot password
#77
Description

Linked Issues
Preview / Screenshot

Photo
Video

Checklist

[ ] I have followed commit guideline to create PR title (https://conventionalcommits.org/en/v1.0.0/)

📝 Changed routes:

/reset-password

(view full size)

Commit 7cad312dba52c1f1f747e01ca86c212f41eea6f7 (https://spoker-storybook-ew28fzpng-sozonome.vercel.app).


Links mix AzureRM and Az commands

This page could be improved by removing legacy AzureRM commands, adding examples for creating, managing, monitoring and removing schedules

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

ID: 6a48fd0e-fe6f-3732-ad36-4ac9ef8a1685
Version Independent ID: e2700f9f-3178-4dc0-d565-ddd4bad2766c
Content: PowerShell cmdlets reference - Azure Scheduler
Content Source: articles/scheduler/scheduler-powershell-reference.md
Service: scheduler
GitHub Login: @derek1ee
Microsoft Alias: deli

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Hi @Karishma-Tiwari-MSFT, @derek1ee . Please give some update on this problem, as now I can't check my JobSchedulers, in the root page of documentation there are link titles with commands which are not found  in Az powershell module,  even using AzureRM module with links attached, I can't execute that commands, they are not working, I'm receiving errors "AzureRM.Scheduler\Get-AzureRmSchedulerJob : Method 'get_SerializationSettings' in type
'Microsoft.Azure.Management.Internal.Resources.ResourceManagementClient' from assembly
'Microsoft.Azure.Commands.ResourceManager.Common, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=31bf3856ad364e35'
does not have an implementation.
At line:1 char:1"


Quit application shortcut changed to a key combination : LShift + Esc.

Some users have lost their work by pressing Esc. I propose LShift + Esc.

Good idea, approved.
You could also add some logic to your application's update() method to handle this
if (!AppBase::update()) {
   if (saveRequired) {
      // show a dialog box e.g. 'Work not saved, are you sure you want to quit?`
   }
}


Sign meilisearch docker image

We would like to make our official docker image signed
Example of sources: https://betterprogramming.pub/docker-content-trust-security-digital-signatures-eeae9348140d

We should look into that: https://github.com/sigstore/cosign

Hello,
Would you be open to a PR signing your Docker image using Cosign with the keyless mode?
https://github.com/sigstore/cosign/blob/main/KEYLESS.md
It is still marked as experimental since the Sigstore Public Good instance is not yet considered GA (should happen soon(ish), Rekor is currently at the 1.0 RC). That does not prevent you to use a key you manage afterwards, it will be a one line addition to the GitHub Actions file.
Also note we could also use Cosign to sign the binaries associated to your releases.

Hello @LeSuisse
I'm really sorry for the late answer, I missed this notification!

Would you be open to a PR signing your Docker image using Cosign with the keyless mode?

Yes please! 😊

It is still marked as experimental since the Sigstore Public Good instance is not yet considered GA (should happen soon(ish), Rekor is currently at the 1.0 RC). That does not prevent you to use a key you manage afterwards, it will be a one line addition to the GitHub Actions file.

I'm not sure I really understand this part of your comment, can you detail it? 😊

Also note we could also use Cosign to sign the binaries associated to your releases.

Oh would be a good addition!

Thanks for the confirmation. I will open a PR by the end of this week or the next one :) .

I'm not sure I really understand this part of your comment, can you detail it? :blush:

The keyless mode of Cosign is still marked as experimental but since my last message the experimental flag is being removed (https://github.com/sigstore/cosign/pull/2387) so it will not really be an issue.


Adapt simple pack pipeline to work with large GEMM

With this PR, matmul size 2048x2048x512 can be compiled and run correctly on hardware. Currently, we use --iree-amdaie-enable-large-gemm to enable passes support for the large gemm sizes. Some passes may not be needed for smaller gemm sizes (and can cause error without changing the parameters), so using the flag to switch on and off.
This PR is based on a separate PR https://github.com/nod-ai/iree-amd-aie/pull/136.
TODO:
1. Test different input sizes and use different tile sizes for AffineLoopOptPass instead of using --iree-amdaie-enable-large-gemm to switch between the compilation flow for small and large gemm sizes.
2. Test different input sizes and make sure the results are correct on device.

Seems OK too. Please ping after you land the dependent PR and Ill take a look again.

@MaheshRavishankar The dependent PR is merged and this one is rebased.


What type of update are you requesting?
A new version of an existing package
Current Package Identifier
mcmilk.7zip-zstd
Package Version
1.5.5-R2
Please describe the changes you would like to see
https://github.com/mcmilk/7-Zip-zstd/releases/tag/v22.01-v1.5.5-R2

It look like the manifest was up to date.


Migrate old data

The old versions of Observatory and the WIki need to be migrated to the new database as soon as we have a new production DB running.
Old data can be found on:

The current rcos.io MongoDB instance
The old Observatory-new server has the SQLite database it used and DokuWiki files
Google Sheets documents
And possibly elsewhere?

Postgrest's bulk insert routes will come in handy here.

Postgrest's bulk insert routes will come in handy here.

Probably the easiest and best way to do this would be to transfer the old DO Droplet to the new RCOS account, then pull the data off of it. This would also preserve a backup of the old server in case we ever need it.
Actually migrating the data might be a bit of a pain though. We're probably going to have to use mongoexport or mongodump to dump the data to JSON (or CSV?), and then edit it to match the new schema before importing it to Postgres.
Something tells me this is going to be harder than it seems though.

Probably the easiest and best way to do this would be to transfer the old DO Droplet to the new RCOS account, then pull the data off of it. This would also preserve a backup of the old server in case we ever need it.
Actually migrating the data might be a bit of a pain though. We're probably going to have to use mongoexport or mongodump to dump the data to JSON (or CSV?), and then edit it to match the new schema before importing it to Postgres.
Something tells me this is going to be harder than it seems though.

Attacked is a ZIP containing a script to dump files from BSON to JSON, and then a set of jq filters to transform the JSON to a more compatible schema.
data-transforms.zip

Attacked is a ZIP containing a script to dump files from BSON to JSON, and then a set of jq filters to transform the JSON to a more compatible schema.
data-transforms.zip


Create new feature parameterAllowedBeforeEndOfOptions

Create new feature parameterAllowedBeforeEndOfOptions to allow restricting positional parameters until after EndOfOptions.  Enhancement for and fixes #2103

Apologies. Family circumstances prevent me from working on my open source projects at the moment.

I am trying to decide if I should fork the project or wait.  Do you have an ETA for your return to working on this project?

Just a side note, I think these files might need to be cleaned up.  It looks like you accidentally pushed CRLF (or GIT failed to remove the CR during the push).
docs/A-Whirlwind-Tour-of-Picocli.html
docs/announcing-picocli-1.0.html
docs/autocomplete.html
docs/build-great-native-cli-apps-in-java-with-graalvm-and-picocli.html
docs/feedback.html
docs/groovy-2.5-clibuilder-renewal-part1.html
docs/groovy-2.5-clibuilder-renewal-part2.html
docs/groovy-2.5-clibuilder-renewal.html
docs/index.html
docs/man/index.html
docs/migrating-from-commons-cli.html
docs/picocli-2.0-do-more-with-less.html
docs/picocli-2.0-groovy-scripts-on-steroids.html
docs/picocli-on-graalvm.html
docs/picocli-programmatic-api.html
docs/quick-guide.html
docs/zh/picocli-2.0-do-more-with-less.html
docs/zh/picocli-2.0-groovy-scripts-on-steroids.html

Just a side note, I think these files might need to be cleaned up. It looks like you accidentally pushed CRLF (or GIT failed to remove the CR during the push). docs/A-Whirlwind-Tour-of-Picocli.html docs/announcing-picocli-1.0.html docs/autocomplete.html docs/build-great-native-cli-apps-in-java-with-graalvm-and-picocli.html docs/feedback.html docs/groovy-2.5-clibuilder-renewal-part1.html docs/groovy-2.5-clibuilder-renewal-part2.html docs/groovy-2.5-clibuilder-renewal.html docs/index.html docs/man/index.html docs/migrating-from-commons-cli.html docs/picocli-2.0-do-more-with-less.html docs/picocli-2.0-groovy-scripts-on-steroids.html docs/picocli-on-graalvm.html docs/picocli-programmatic-api.html docs/quick-guide.html docs/zh/picocli-2.0-do-more-with-less.html docs/zh/picocli-2.0-groovy-scripts-on-steroids.html

It is possible that what you are seeing is related to this recent change: https://github.com/remkop/picocli/pull/2174
(which ironically was meant to fix CRLF issues...)

when editing the documentation, so I need to modify both index.adoc and index.html?

No, there’s no need to change the HTML, those are generated from the AsciiDoc.
Just the AsciiDoc is fine.

Requested changes complete.  Please re-review.

Thank you!
Still reviewing, but looks good so far.
Note that I’ll probably do one more 4.7.x release before merging this PR into the main branch.


Nessie sanity update - align to rocks

Codecov Report

Merging #1338 (da64243) into master (0ac3f17) will decrease coverage by 0.02%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master    #1338      +/-   ##
==========================================
- Coverage   47.09%   47.07%   -0.03%
==========================================
  Files         203      203
  Lines       15905    15908       +3
==========================================
- Hits         7491     7488       -3
- Misses       7424     7430       +6
  Partials      990      990

Impacted Files
Coverage Δ

graveler/graveler.go
35.63% <71.42%> (+0.43%)
:arrow_up:

config/logger.go
64.28% <0.00%> (-10.72%)
:arrow_down:

catalog/mvcc/cataloger_create_branch.go
81.53% <0.00%> (-3.08%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
62.96% <0.00%> (+3.70%)
: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 0ac3f17...da64243. Read the comment docs.

Codecov Report

Merging #1338 (da64243) into master (0ac3f17) will decrease coverage by 0.02%.
The diff coverage is 71.42%.

@@            Coverage Diff             @@
##           master    #1338      +/-   ##
==========================================
- Coverage   47.09%   47.07%   -0.03%
==========================================
  Files         203      203
  Lines       15905    15908       +3
==========================================
- Hits         7491     7488       -3
- Misses       7424     7430       +6
  Partials      990      990

Impacted Files
Coverage Δ

graveler/graveler.go
35.63% <71.42%> (+0.43%)
:arrow_up:

config/logger.go
64.28% <0.00%> (-10.72%)
:arrow_down:

catalog/mvcc/cataloger_create_branch.go
81.53% <0.00%> (-3.08%)
:arrow_down:

catalog/mvcc/cataloger_create_repository.go
62.96% <0.00%> (+3.70%)
: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 0ac3f17...da64243. Read the comment docs.


Build test darwin target

This PR subsumes https://github.com/cilium/cilium/pull/21568.
(Copied original reviewers.)
Fixes: https://github.com/cilium/cilium/issues/19569

Maybe we can skip the removal of test artifacts from the build target. The clean target should do that.

@aditighag as long as the test file being in the repo doesn't prevent the darwin build from running - that's why I assumed that the rm was happening in between before.

Good point! The rm step was only added to the darwin target. Anyway I don't think it's a problem.
Both the targets are compiled - https://github.com/cilium/cilium/actions/runs/4010655158/jobs/6887402660


[BEAM-9603] Add timer family support to FnApiDoFnRunner

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @boyuanzz
This is ready for review.

retest all please

retest all please

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Streaming

retest all please

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Streaming

retest all please

Run Java PreCommit

retest all please

Run Java PreCommit

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Streaming

Run Java PreCommit

retest all please

retest this please

Run Java PreCommit

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Streaming

Run Java Flink PortableValidatesRunner Batch

Run Java Flink PortableValidatesRunner Streaming

Seems like Flink VRs are failing at head: https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Batch/
https://builds.apache.org/job/beam_PostCommit_Java_PVR_Flink_Streaming/

This PR did not remove the exclusion of the tests on Flink so running the PVR jobs on it was not validating the proper support of timer family.
https://github.com/apache/beam/blob/03d99dfa359f44a29a772fcc8ec8b0a237cab113/runners/flink/job-server/flink_job_server.gradle#L150
Maybe worth to create a new PR that enables the tests to validate that the support works on Portable Flink.

Additionally it seems the breaking tests are passing now #11825 so it should be good to go.

This PR did not remove the exclusion of the tests on Flink so running the PVR jobs on it was not validating the proper support of timer family.
https://github.com/apache/beam/blob/03d99dfa359f44a29a772fcc8ec8b0a237cab113/runners/flink/job-server/flink_job_server.gradle#L150
Maybe worth to create a new PR that enables the tests to validate that the support works on Portable Flink.

Hi Ismaël, I'm not sure what's the support status of flink and spark now. Do they support timer family over FnApi?


Add id identifier to marker-press event on Android

Currently, on iOS the onMarkerPress callback includes the identifier of the map marker as an id property. Google Map markers do not store their identifier. This change aligns both platforms.

Thanks! 🍻


added option to enter self hosted url

this helps those who might have a self hosted plausible

Hello @thanesh,
Thank you for your conditions. Does it still work for the non-self hosted versions? It appears as if the default isn't in, is it?
Cheers,
Peter

Good question. Default was removed with my change. Let me see if I can make
this change.
Thanks
On Fri, Jul 1, 2022 at 6:12 AM Peter Thaleikis @.***>
wrote:

Hello @thanesh https://github.com/thanesh,
Thank you for your conditions. Does it still work for the non-self hosted
versions? It appears as if the default isn't in, is it?
Cheers,
Peter
—
Reply to this email directly, view it on GitHub
https://github.com/spekulatius/vuepress-plugin-plausible/pull/4#issuecomment-1172182750,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIPTXHZGIPTOHBKRNNPG3DTVR277BANCNFSM52LOH2HA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @thanesh,
Thanks, that looks great!
I've merged it and tagged a new release! Let me know if any issues come up!
Cheers,
Peter


[11.x] Add Str::extract

Description
This PR adds a Str::extract method to be able to retrieve pieces of text using a template string.
On various projects I've had to use different regex patterns to extract pieces of information. Such as ID's from URL's, information from comments, area codes from phone numbers, etc. A built-in way to extract this kind of data from known formats would have been a big time saver, and also help those who don't want to dive into their own regex to be able to do so.
Usage
use Illuminate\Support\Str;

// ['last_4' => '5000']
Str::extract(
    '4242-4242-4242-5000',
    '*-*-*-{last_4}'
);

// ['area_code' => '800']
Str::extract(
    'Phone Number: 1-(800)-555-5555',
    '*1-({area_code})-*'
);

// ['email' =><EMAIL_ADDRESS>Str::extract(
    'Contact us at<EMAIL_ADDRESS>
    '* at {email}.'
);

// ['user_id' => '1', 'post_id' => '2']
Str::extract(
    '/users/1/posts/2/comments',
    '/users/{user_id}/posts/{post_id}/*'
);

// ['day' => '1st', 'month' => 'January']
Str::extract(
    'My birthday is on the 1st of January',
    'My birthday is on the {day} of {month}'
);

// ['street' => '123 Main St', 'city' => 'Anytown', 'region' => 'CA']
Str::extract(
    'The address is 123 Main St, Anytown, CA.',
    '*address is {street}, {city}, {region}.'
);

@stevebauman what about extracting values that contain { and } characters? Do we need tests for that? Any other weird limitations?

@taylorotwell I added more edge case tests and was able to break it here:
https://github.com/laravel/framework/pull/53781/files#diff-be47dbd336aece128f999b4c2d8b4fc7ee809a1d1e0ddd178547542201d4e897R254
$values = Str::extract('{\\{bar}\\}', '*{foo}\\}');

// ['foo' => '}']
var_dump($values);

// Should be:
// ['foo' => '{bar}']

Not sure if this okay to have, let me know! Maybe a regex wizard and drop in and lend a hand 🧙

I don't know about wizard, but one approach would be to tighten the "placeholder" values to be {name} where name is any valid PHP variable name. I'll take a quick look to see if I can get these passing...

Took a quick look. I'm glad to look more, but the root problem here is going to be the root problem with any dynamic regular expression - escaping. Specifically what needs to be escaped versus what is already escaped.
The example you have is rather dense and focuses on braces. But the wildcard presents the same issues. Consider:
Str::extract('what about *bold* words', '*\*{word}\**'));

I'm not sure if this is an intended use, but that's what I would expect to write when trying to extract the word bold.
Similar to Blade parsing (which is done with regular expression), there are limits to their use. Those have to be mitigated with rules. For example, when using Str:extract(), you only need to escape literal instances of * or placeholders (not loose braces).

Thanks @jasonmccreary! Really appreciate you diving into this 🙏
Yea you're right. We're going to hit some limitations and edge-cases here regardless due to regex's limitations.
I think my previously provided example wasn't a display of a good edge case, as we can actually just escape the brackets in the pattern (which is what we can always control) vs what is provided as a haystack string (which isn't what we can always control):
// ['foo' => '{bar}']
Str::extract('{{\\{bar}\\}}', '*{\{foo}\}*');

I've added a bunch more edge case assertions and simplified the pattern a bit.
I think it's solid now. Let me know your thoughts!

I've added a bunch more edge case assertions and simplified the pattern a bit.
I think it's solid now. Let me know your thoughts!

@stevebauman - Looks good, I think the only way to really improve on the reliability would be to tokenize it, however thats probably far to much complexity for what you're trying to achieve.
I put it through it's paces, and only escape chars that are really causing the issues (as you're aware), for example this:
$pattern = '*/{first}/{second}/*';
$haystack = '123/131415*\\/\\d+d/7\\8\\9/101112';
$expected = [
    'first' => '131415*\\',
    'second' => '\\d+d',
];
//Expected: 131415*\, got: \d+d
//Expected: \d+d, got: 7\8\9

Setting more explicit / clear placeholder boundaries would allow this pattern to pass as expected, and could be a better option? However, doesn't help with Jasons edge case.
    public static function extract($haystack, $pattern)
    {
        $placeholders = static::matchAll('/\{([^{}]+)}/', $pattern);

        $pattern = preg_quote($pattern, '/');

        foreach ($placeholders as $placeholder) {
            $pattern = static::replace(
                preg_quote('{'.$placeholder.'}', '/'),
                '(?<'.$placeholder.'>[^\/]+?)',
                $pattern,
            );
        }

        $pattern = static::replace('\*', '.*?', $pattern);
        $pattern = static::replace('\{', '{', $pattern);
        $pattern = static::replace('\}', '}', $pattern);

        if (preg_match("/^{$pattern}$/i", $haystack, $matches)) {
            return array_intersect_key($matches, $placeholders->flip()->all());
        }

        return [];
    }

I think it will be a great feature so long as the limitations & requirements are documented, especially as I can see people who are not comfortable with Regex reaching for it.
Should ensure the docs cover:

Placeholder names should be unique, made up of letters, numbers and underscores (no reserved characters)
Reserved characters can't be used as delimiters: (, *, ^, !, @).
The effects of backslashes or delimiters appearing in the value to be extracted when parsing user input data.

I agree with the tokenization. But I believe this could be achieved with the understanding you only escape the special characters used by extract (i.e. *, {, }).
If you all want to beef up the test cases with real-world examples, I'll get them passing.

Thanks @CamKem! I've updated the PR with your suggestions and edge case.

I still think there are some oddities here. Some of these "edge cases" don't seem very real-world and/or break what I would consider the natural escaping rules for extract.
For example, the same result of these two is odd.
$this->assertSame(['foo' => '{bar}'], Str::extract('{\\{bar}\\}', '*{\{foo}\}*'));
$this->assertSame(['foo' => '{bar}'], Str::extract('foo bar* {{bar}}', '* {{foo}}'));

The first assertion seems to escape the placeholder. Furthermore, it escapes the inner opening brace, but the outer closing brace. This either (incorrectly) implies the name can contain braces or reveals a loophole in the escaping. The second assertion escapes nothing. Which may be fine. But odd that both are true.
I think using a real world example instead of simply trying to break the algorithm helps reveal the escaping problem. Consider wanting to extract digits from a partially masked credit card number. I'd personally write the following: But this doesn't work.
$this->assertSame(
    ['first_4' => '1234', 'last_4' => '7890'],
    Str::extract('1234*********7890', '{first_4}*\*{last_4}')
);

I don't mean to noisy up this PR. I think this is a cool feature. Would just advocate for it to follow the same rules/ideas as its underlying regular expressions. Or, at the least, have a clear rule of when/what to escape.

Another set of real-world examples that fail. These reveal issues with the "greediness" of the underlying regex, as well as what it matches (e.g. [^\/]+?)
$this->assertSame(
    ['first_4' => '4242'],
    Str::extract('4242-4242-4242-5000', '{first_4}*')
);
$this->assertSame(
    ['path' => 'docs/11.x/strings'],
    Str::extract('https://laravel.com/docs/11.x/strings#method-str-is', 'https://laravel.com/{path}#*')
);

Again, all solveable with defining some rules around how this is used. But felt these should be noted as they are different issues than the escaping previously noted.

Kinda fear this could be a black hole of edge cases and additional PRs, so going to table this one for now. 😅

@taylorotwell haha totally fair! Thanks for your time 🙏


MatplotlibDeprecationWarning

The register_cmap function was deprecated in Matplotlib 3.7 and will be removed two minor releases later. Use matplotlib.colormaps.register(name) instead.

Hi, Yuting. I appreciate your reminder.
I also noticed this warning and have already added a try and except in the source code. So it won't get an error in a new release.


88 add xrf measurents

Still work in progress. @hampusnasstrom wanted to see a draft. :slightly_smiling_face:

Overview on the work which has been done:

Created a schema with XRayFluorescence etc. closely mirrored the structure from xrd schema
a ELNXRayFluorescence reference implementation which should be extendable to handle other file formats
specific reader for extracting data (multiple layers, elements, elemental lines and intensities) from the UBIK XRF file format

Things which still are unclear/not implemented

Sample handling: Up to now only Sample id as string
UBIK files do not contain information regarding measurement setup
(energy, spot size, integration time etc -> XRFSettings)
Library measurement as HZB stuff not included


Create Automated Release Workflows

There's some fairly complicated logic in a few places so I created a couple flow charts at ReleaseWorkflows.md.
Basically, this is a way to keep the plugins up to date with acapy releases automatically. If all the tests pass for a plugin it will be updated and be considered stable with acapy. If it doesn't then it won't be upgraded and will remain verified against an earlier release. A maintainer can create patch releases if a plugin which did fail for a release gets fixed before another version of acapy. A message is appended to the plugin description as well with the supported acapy version. I'm hoping this can be used to provide warnings in acapy when a plugin falls behind acapy.
There is some bash scripting. I tried to limit it as much as I could by utilizing the repo_manager.py script. The manager script has been changed slightly and some additional options for creating and parsing release information has added.
I had to do a bit of work for some tests after the upgrade but they all passing now so they will all be on version 0.12.0 of acapy initially. Two unit tests for rpc I removed. I couldn't figure out why they were only failing in the github action but not locally.
*** Note: *** I'm not sure if the bot will be able to create the release PR's for this repo. Might need to change it to a fork strategy.

@jamshale, One question.  It looks like a release is done for the plugins as a whole.  Is that correct?  Is the plan to later support releasing the plugins individually so they can evolve independently?

@jamshale, One question. It looks like a release is done for the plugins as a whole. Is that correct? Is the plan to later support releasing the plugins individually so they can evolve independently?

With this PR, yes, you are correct. The entire repo is released at the same time as acapy. However, it does allow for plugins to be upgraded independently. So plugins can now be left in a non-upgraded state indefinitely, and only say they are fully supported for an older version of aca-py. When installing a specific plugin the aca-py agent could target any of the release tags and the subdirectory of the plugin.
There is no publish step yet. I was thinking that this could be done as a separate task. When publishing to pypi only plugins which had been upgraded would be published. Allowing them to evolve independently as a published package.
I didn't have a solid plan about having a common naming or package versioning. I wasn't sure if we wanted plugins versions to match aca-py or not, or have there own versioning. Currently most of them are just 0.1.0 and don't get changed with this workflow. The plugin names don't get aries-plugin or anything pre-pended to the package name either.
Either of these things would be easy to do. All I do in this workflow is add the supported aca-py version in the package description.

Please ignore any WIP commits happening here when I work on the improvements.

Going to close a re-open this later. Need to figure some stuff out that requires pushing a lot of commits.


Compiler crashes on bad input

let prql = "from foo bar";
if let Ok(sql) = compile(&prql, Options::default()) {
    println!("SQL: {}", sql)
}

thread 'main' panicked at 'bad transform cast:

[Expr {
  id: Some(3),
  kind: Ident(Ident { path: ["default_db"], name: "foo" }),
  span: Some(span-chars-5-9),
  target_id: None,
  target_ids: [],
  ty: Some(table<[foo.*]>),
  needs_window:
  false,
  alias: None,
  flatten: false },
Expr {
  id: None,
  kind: Literal(Null),
  span: None,
  target_id: None,
  target_ids: [],
  ty: None,
  needs_window: false,
  alias: None,
  flatten: false }]

prql-compiler-0.5.2/src/semantic/transforms.rs:779:29
stack backtrace:
   0: rust_begin_unwind
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/std/src/panicking.rs:575:5
   1: core::panicking::panic_fmt
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/panicking.rs:64:14
   2: core::result::unwrap_failed
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/result.rs:1791:5
   3: core::result::Result<T,E>::expect
             at /rustc/d5a82bbd26e1ad8b7401f6a718a9c57c96905483/library/core/src/result.rs:1070:23

Is this on main? This was fixed in https://github.com/PRQL/prql/pull/1928
Closing but reopen if still valid

No, this is not on `main, it is with 0.5.2. Maybe time for 0.5.3 soon?

No, this is not on main, it is with 0.5.2. Maybe time for 0.5.3 soon?

Yes. If it's blocking your development, I can do one now!
Otherwise we try and do around every two weeks, so we'd do one in a week.

No, it is not blocking, its just a slight nuisance. I can wait, no worries.

Thanks! Let me know if it becomes blocking.


Completed MVP #2 features with layer limits, cleaned up sidebar, and other UI improvements

MVP #2 scope included deleting, updating, and creating OUs as well as basic filtering to limit the number of OUs displayed at a time - this was accomplished through layer limit rendering. Search feature implementation scoped for MVP #3.

Like the UI a lot. Great job. Is search suppose to work for MVP #2?

Awesome, thanks! And no, the MVP 2 focus is on basic filtering by layers; Search is the more advanced MVP 3 filtering feature (as it requires searching for an orgunit, managing potential duplicate names, and then tracing the path from the parent to said orgunit).
MVP 2:

OU Visualization, Prashant
a. Customer can create, delete, and update OUs
b. Limit the amount of OUs that show up on screen, possibly limit the amount of work API is doing
i. Use basic filtering to make it work (i.e. show the top N layers. Show the N layers below or above a particular OU, etc.)

Okay. Normally, we shouldn't put the UI element in until it works and it's also not best practice to include commented out code as well (ie. var searchButton....)
Approving the changes

Yeah, that's a great point, I agree it doesn't make much sense to show the Search Bar in our presentation demo if it doesn't work yet. I removed the commented code as well as the Search Bar from the UI for the time being.


feat: Add macOS support

Overview
This change adds a macOS implementation of the clipboard. The Objective-C implementation was copied over from the current implementation under React/CoreModules in Microsoft's react-native-macos repo.
Test Plan
Basic functionality was tested using a simple test app under example/macos. The implementation is similar to that of the already existing test app for Android and iOS, but due to differences between which version of React Native we pull, we have to create a separate test project for macOS. This test project has been slimmed down to only include the macOS implementation.
Test App Screenshot

Amazing @amgleitman!


Adds spo file copy command

Adds spo file copy command solving https://github.com/SharePoint/office365-cli/issues/286

Coverage remained the same at 100.0% when pulling 9272ddb71fff6eef4dbc37247f338fa6f260cc9b on VelinGeorgiev:copy-file into 413988dcaaee73aee1f15eb0096647c15ffbc280 on SharePoint:dev.

Merged manually


RePlAce fails to place all Insts on grid for Coyote

After running RePlAce on Coyote and loading into innovus, checkplace reports several cells not placed on the manufacturing grid
Insts not on placement grid, or blocks not on manufacturing grid (279)
See attachment: t9_place_2019-06-04_10-19.tar.gz

Hi Tutu,
I was not able to find your archive file...
Could you send this file to my email?
Kind regards,
Mingyu Woo

Did you find it now?

Yes. I've found out. Let me check this issue.

NTUPlace* will be removed and OpenDP will be used.
Close this issue.


[AIRFLOW-862] Fix Unit Tests for DaskExecutor

Unit tests were inadvertently disabled for DaskExecutor added in #2067.
@bolkedebruin in reviewing the tests, I fixed the ImportError that caused them to be disabled, streamlined them slightly, and removed one that turned out to be useless without a BackfillJob checking the executor's event buffer -- that case is already covered by the Dask integration test.
Dear Airflow Maintainers,
Please accept this PR that addresses the following issues:

https://issues.apache.org/jira/browse/AIRFLOW-862

Codecov Report

Merging #2076 into master will increase coverage by 0.44%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master    #2076      +/-   ##
==========================================
+ Coverage   66.94%   67.39%   +0.44%
==========================================
  Files         140      140
  Lines       10635    10638       +3
==========================================
+ Hits         7120     7169      +49
+ Misses       3515     3469      -46

Impacted Files
Coverage Δ

airflow/executors/dask_executor.py
79.06% <60%> (+79.06%)
:white_check_mark:

airflow/ti_deps/deps/not_skipped_dep.py
88.88% <ø> (-11.12%)
:x:

airflow/models.py
86.24% <ø> (+0.08%)
:white_check_mark:

airflow/jobs.py
73.43% <ø> (+0.95%)
:white_check_mark:

airflow/executors/base_executor.py
94.64% <ø> (+3.57%)
:white_check_mark:

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 b0ae70d...8cd2654. Read the comment docs.

@jlowin looks good, can you investigate why postgres is failing on py3? Maybe unrelated, not sure. and maybe rebase to see if decrease in coverage and landscape errors will go away.

@bolke weird error... seems unrelated. I'm guessing the coverage decrease is because the unit test I deleted had a failed task in it and the remaining one doesn't. I don't really see what else could have caused that (the two unit tests were almost identical otherwise). I'm not sure what landscape's issue is either, when I click details it says no problems.
I'm going to rebase and push and let's see what happens!

LGTM


uuid() function not working if used in a property of an abstract class

OrientDB Version, operating system, or hardware.

v2.0 SNAPSHOT[ ] - .18[ ] .17[ ] .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
v2.1 SNAPSHOT[ ] - .16[ ] .15[ ] .14[ ] .13[ ] .12[ ] .11[ ] .10[ ] .9[ ] .8[ ] .7[ ] .6[ ] .5[ ] .4[ ] .3[ ] .2[ ] .1[ ] .0[ ]
v2.2 SNAPSHOT[X] - .rc1[ ] .beta2[ ] .beta1[ ]

Operating System

[ ] Linux
[ ] MacOSX
[X] Windows
[ ] Other Unix
[ ] Other, name?

Expected behavior and actual behavior
if a new document is inserted, all the previous documents are getting the new generated id
Steps to reproduce the problem

Hi @Pro-Vizion
I'm not sure I got the point, could you please post an SQL script to reproduce the problem?
Thanks
Luigi

Hi,
to reproduce :
CREATE CLASS _test ABSTRACT
CREATE PROPERTY _test.id string
ALTER PROPERTY _test.id default uuid()
CREATE CLASS test EXTENDS _test
CREATE PROPERTY test.name string

Now, if we insert a record :
INSERT INTO test (name) VALUES ("Pascal")

and another one :
INSERT INTO test (name) VALUES ("Aubry")

Both, have the same uuid.

Hi @Pro-Vizion
If you execute
ALTER PROPERTY _test.id default uuid()

the uuid() function is executed during the ALTER PROPERTY statement execution and its value is saved as default value, so the result is what you are obtaining.
To do what you need, you can do the following:
ALTER PROPERTY _test.id default "uuid()"

(see the quotes around uuid())
Unfortunately this use case is not as easy as it seems, you can find a detailed description of this behavior here:
https://github.com/orientechnologies/orientdb/issues/6333#issuecomment-230101894
I'm closing this, as the main problem will be tracked on the linked issue
Thanks
Luigi

@luigidellaquila - As a workaround, could this also be solved with a dynamic hook, that calls the UUID function at record creation?
Scott


[CI] BDD Tests that are not implemented: should the build fail or warn?

We noticed that there are a few BDD files under https://github.com/elastic/apm-agent-python/tree/master/tests/bdd/features

api_key
azure_app_service_metadata
outcome

But only the API Key ones are implemented.

[2021-08-02T10:01:23.365Z] tests/bdd/init.py                                               0      0      0      0   100%
[2021-08-02T10:01:23.365Z] tests/bdd/api_key_tests.py                                         31     15      0      0    52%
[2021-08-02T10:01:23.365Z] tests/client/init.py                                            0      0      0      0   100%

You can check that they do not appear under the test list for that package: https://apm-ci.elastic.co/job/apm-agent-python/job/apm-agent-python-mbp/job/master/500/testReport/tests.bdd/
I'd like to ask about your expectations on it: should the build fail because they are not implemented, or show them as skipped?

Show them as skipped, I think. Otherwise we'll start failing the moment that BDD tests are merged upstream, and I don't think that's the right behavior.

Then I think the team needs to provide the scaffolding code for skipping the test using python's test runner. Otherwise they won't appear as skipped


Cannot read channel messages if channel is marked NSFW?

I could not get this working in a channel, so I started testing on a personal server and realized that this error I was getting was because the server channel I was trying to run it in was marked NSFW. I'm not 100% this is the issue but it seems like it. The error log below is what I get when I try and run it in an NSFW channel that has already been accepter by me manually. Otherwise in normal channels it works fine. What I want to know is there any possible fix someone could direct me to? In DisCum documentation I saw a includeNsfw (Optional[bool]) Parameter but I'm not very proficient with this so I don't really know if that's helpful. Thanks.

0|waifu  | Exception ignored in thread started by
0|waifu  | :
0|waifu  | <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x7f0dec7ab3d0>>
0|waifu  | Traceback (most recent call last):
0|waifu  |   File "/root/.local/lib/python3.9/site-packages/discum/gateway/gateway.py", line 299, in _response_loop
0|waifu  |     func(resp)
0|waifu  |   File "/root/waifu/MudaeAutoBot.py", line 763, in on_message
0|waifu  |     msg = get_server_settings(gid,matched_channel)
0|waifu  |   File "/root/waifu/MudaeAutoBot.py", line 180, in get_server_settings
0|waifu  |     FsResults = bot.filterSearchResults(FsMsgs)
0|waifu  |   File "/root/.local/lib/python3.9/site-packages/discum/discum.py", line 313, in filterSearchResults
0|waifu  |     return imports.Messages(self.discord, self.s, self.log).filterSearchResults(searchResponse)
0|waifu  |   File "/root/.local/lib/python3.9/site-packages/discum/messages/messages.py", line 245, in filterSearchResults
0|waifu  |     jsonresponse = searchResponse.json()['messages']
0|waifu  | KeyError: 'messages'

That just searching for settings but I can see if I can try to add it in Sent from my iPhoneOn Jan 21, 2023, at 4:55 AM, veetus1 @.***> wrote:
I could not get this working in a channel, so I started testing on a personal server and realized that this error I was getting was because the server channel I was trying to run it in was marked NSFW. I'm not 100% this is the issue but it seems like it. The error log below is what I get when I try and run it in an NSFW channel that has already been accepter by me manually. Otherwise in normal channels it works fine. What I want to know is there any possible fix someone could direct me to? In DisCum documentation I saw a includeNsfw (Optional[bool]) Parameter but I'm not very proficient with this so I don't really know if that's helpful. Thanks.
0|waifu  | Exception ignored in thread started by 0|waifu  | : 0|waifu  | <bound method GatewayServer._response_loop of <discum.gateway.gateway.GatewayServer object at 0x7f0dec7ab3d0>> 0|waifu  | Traceback (most recent call last): 0|waifu  |   File "/root/.local/lib/python3.9/site-packages/discum/gateway/gateway.py", line 299, in _response_loop 0|waifu  |     func(resp) 0|waifu  |   File "/root/waifu/MudaeAutoBot.py", line 763, in on_message 0|waifu  |     msg = get_server_settings(gid,matched_channel) 0|waifu  |   File "/root/waifu/MudaeAutoBot.py", line 180, in get_server_settings 0|waifu  |     FsResults = bot.filterSearchResults(FsMsgs) 0|waifu  |   File "/root/.local/lib/python3.9/site-packages/discum/discum.py", line 313, in filterSearchResults 0|waifu  |     return imports.Messages(self.discord, self.s, self.log).filterSearchResults(searchResponse) 0|waifu  |   File "/root/.local/lib/python3.9/site-packages/discum/messages/messages.py", line 245, in filterSearchResults 0|waifu  |     jsonresponse = searchResponse.json()['messages'] 0|waifu  | KeyError: 'messages'
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Any luck with this? I was looking for a solution to this as well.

Ive added it in to the bot you guys can test it now and see if it works


Running/developing on Windows?

First I just want to say I came across this from your YouTube video and it's an awesome project. I was wondering though if it works/could work on Windows. My (limited) understanding of the project is that it should be able to run on Windows, but I haven't yet gotten it working.
I also haven't worked with Python in awhile, so sorry if I'm missing something basic. As it stands after I've downloaded the repo, I've tried running devdeck.py, but I get an error on some of the imports:
PS C:\Repos\devdeck\devdeck> python .\devdeck.py Traceback (most recent call last):   File "C:\Repos\devdeck\devdeck\devdeck.py", line 3, in <module>     from devdeck.deck_context import DeckContext   File "C:\Repos\devdeck\devdeck\devdeck.py", line 3, in <module>     from devdeck.deck_context import DeckContext ModuleNotFoundError: No module named 'devdeck.deck_context'; 'devdeck' is not a package
That doesn't seem to be related to running in the Windows environment, but I wanted to post this issue as a broader conversation of whether this does/can work on Windows.
Thanks

Hey,
I didn't specifically target windows as I figured most windows users would be content with the official Elgato software, however I'm happy to get it working on Windows if there is an apetite, which it sounds like there is.
So in theory the bulk of it should work on Windows, the only things that definitely won't are the audio controls for volume and muting as those are OS specfic, but there is no reason why they shouldn't work.
I'll look into what it will take to get this working on Windows.

I think I've figured out the cause of this and am working on an update to address the isses.

Version 1.0.12+ now supports Windows.
The installation instructions have also been updated as you will need to install libUSB DLLs


Pluggable metrics registry

The current codebase uses old yammer libs, and the world already moves to dropwizard.
Considering the difficulty of the upgrade for existing users, shall we think of abstract Metrics/MetricsRegistry(maybe more) as interfaces and build yammer/dropwizard plugins for that?

@jackjlli ^^

+1 for this. We have seen a lot of issues with the out dated yammer metrics lib. For example, it has the stale metrics issue as reported here: https://engineering.salesforce.com/be-careful-with-reservoirs-708884018daf. This makes some alerts not working properly. The new lib should allow configuration of more recent metrics implementation. @fx19880617 @Jackie-Jiang

What do you people think of https://micrometer.io/ ?

micrometer.io looks a good idea if it can deliver like slf4j.

Looks like work has already begun on this : https://github.com/apache/incubator-pinot/pull/6579 thanks to @jackjlli


Improve Tag Input Parsing

Background
For some usecase, we need to list much pr labels for the actions. Currently, the action only separate the input by comma character, therefore using new lines causes tag to be parsed incorrectly. We also found that the system doesn't trim the PR labels, therefore the system may interpret PR labels with whitespace.
Changes

Remove node_modules and use ncc build instead
Improve input parsing to allow new lines and also introduce trimming

Resolved in https://github.com/danielchabr/pr-labels-checker/pull/13


Design a lower level interface

When we attach, we straight get a session. This is very limiting in several usecases:

Target autodetect
More complex unlocking sequences
Recover MCU state

and many more.
We want more low level interface access that is more granular & specific than the current Session.
We still want to keep the Session and its interface, but we want an interface point before the Session where we can do more low level operations.

Lower level is a bit vague IMO. We already have system-level (Session) and core-level APIs, I'm not sure if we can go lower than core-level. On the other hand, the current model is slightly insufficient, as the Core model is entangled with the debug modules, which behave differently between architectures.

Lower means AP level here kind of. I added a comment :)


chore: remove unused skipInstallations option

The skipInstallations option is not used in any business logic and is undocumented. Removing it will prevent potential confusion for developers.

Thanks, this LGTM 👌 .


[pthreads] Build error (derived from mosquitto)

Package: pthreads[core]:x64-windows -> 3.0.0#13
Host Environment

Host: x64-windows
Compiler: MSVC 19.29.30141.0
vcpkg-tool version: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
vcpkg-scripts version: 1cc952582 2023-02-15 (2 hours ago)

To Reproduce

Initially found by setting up a dummy cmake project with manifest file including mosquitto.
I get the same error when installing pthreads directly. vcpkg install pthreads
Tried with both static/dynamic triplets in both cases.

fmt and several other packages I tested works fine with the setup, so I believe pthreads to be the issue?
Any help is appreciated - thank you!
Failure logs
-- Using cached pthreads4w-code-v3.0.0.zip.
-- Cleaning sources at C:/Users/Mads/Documents/projects/testVcpkg/dependencies/vcpkg/buildtrees/pthreads/src/49e541b66c-6b4ff17b62.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/Mads/Documents/projects/testVcpkg/dependencies/vcpkg/downloads/pthreads4w-code-v3.0.0.zip
-- Applying patch fix-arm-macro.patch
-- Applying patch fix-arm64-version_rc.patch
-- Applying patch use-md.patch
-- Applying patch fix-pthread_getname_np.patch
-- Applying patch fix-install.patch
-- Using source at C:/Users/Mads/Documents/projects/testVcpkg/dependencies/vcpkg/buildtrees/pthreads/src/49e541b66c-6b4ff17b62.clean
-- Found external ninja('1.10.2').
-- Getting CMake variables for x64-windows
-- Building and installing x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
    Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Professional/VC/Tools/MSVC/14.29.30133/bin/Hostx64/x64/nmake.exe" /NOLOGO /G /U /F Makefile all install "INSTALLDIR=C:\\Users\\Mads\\Documents\\projects\\testVcpkg\\dependencies\\vcpkg\\packages\\pthreads_x64-windows\\debug" "DESTROOT=C:\\Users\\Mads\\Documents\\projects\\testVcpkg\\dependencies\\vcpkg\\packages\\pthreads_x64-windows\\debug"
    Working Directory: C:/Users/Mads/Documents/projects/testVcpkg/dependencies/vcpkg/buildtrees/pthreads/x64-windows-dbg
    See logs for more information:
      C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\buildtrees\pthreads\install-x64-windows-dbg-out.log
      C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\buildtrees\pthreads\install-x64-windows-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_build_nmake.cmake:156 (vcpkg_execute_build_process)
  scripts/cmake/vcpkg_install_nmake.cmake:52 (vcpkg_build_nmake)
  buildtrees/versioning_/versions/pthreads/f4037e12c8075b814cab20c65509b49bd7f59257/portfile.cmake:44 (vcpkg_install_nmake)
  scripts/ports.cmake:147 (include)

C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\buildtrees\pthreads\install-x64-windows-dbg-out.log
Included: common.mk
	"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" /E clean VC-debug
	if exist *.obj del *.obj
	if exist *.def del *.def
	if exist *.ilk del *.ilk
	if exist *.pdb del *.pdb
	if exist *.exp del *.exp
	if exist *.map del *.map
	if exist *.o del *.o
	if exist *.i del *.i
	if exist *.res del *.res
	if exist *_stamp del *_stamp
	cd tests && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" clean
	if exist *.dll erase *.dll
	if exist *.lib erase *.lib
	if exist _ptw32.h erase _ptw32.h
	if exist pthread.h erase pthread.h
	if exist semaphore.h erase semaphore.h
	if exist sched.h erase sched.h
	if exist *.e erase *.e
	if exist *.i erase *.i
	if exist *.obj erase *.obj
	if exist *.pdb erase *.pdb
	if exist *.o erase *.o
	if exist *.asm erase *.asm
	if exist *.exe erase *.exe
	if exist *.manifest erase *.manifest
	if exist *.pass erase *.pass
	if exist *.bench erase *.bench
	cl /errorReport:none /nologo /MDd /I. /DHAVE_CONFIG_H /W3 /Z7  /D__PTW32_BUILD_INLINED /D__PTW32_CLEANUP_C -c pthread.c
pthread.c
	rc /d__PTW32_ARCHAMD64 /d__PTW32_RC_MSC /d__PTW32_CLEANUP_C version.rc
Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384

Copyright (C) Microsoft Corporation.  All rights reserved.

	cl /errorReport:none /nologo /LDd /Zi pthread.obj version.res /link /implib:pthreadVC3d.lib  /out:pthreadVC3d.dll
cl : Command line warning D9025 : overriding '/Zi' with '/Z7'
cl : Command line warning D9025 : overriding '/Zi' with '/Z7'
   Creating library pthreadVC3d.lib and object pthreadVC3d.exp
	"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" /E clean VCE-debug
	if exist *.obj del *.obj
	if exist *.def del *.def
	if exist *.ilk del *.ilk
	if exist *.pdb del *.pdb
	if exist *.exp del *.exp
	if exist *.map del *.map
	if exist *.o del *.o
	if exist *.i del *.i
	if exist *.res del *.res
	if exist *_stamp del *_stamp
	cd tests && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" clean
	if exist *.dll erase *.dll
	if exist *.lib erase *.lib
	if exist _ptw32.h erase _ptw32.h
	if exist pthread.h erase pthread.h
	if exist semaphore.h erase semaphore.h
	if exist sched.h erase sched.h
	if exist *.e erase *.e
	if exist *.i erase *.i
	if exist *.obj erase *.obj
	if exist *.pdb erase *.pdb
	if exist *.o erase *.o
	if exist *.asm erase *.asm
	if exist *.exe erase *.exe
	if exist *.manifest erase *.manifest
	if exist *.pass erase *.pass
	if exist *.bench erase *.bench
	cl /errorReport:none /nologo /MDd /EHs /TP /I. /DHAVE_CONFIG_H /W3 /Z7  /D__PTW32_BUILD_INLINED /D__PTW32_CLEANUP_CXX -c pthread.c
pthread.c
	rc /d__PTW32_ARCHAMD64 /d__PTW32_RC_MSC /d__PTW32_CLEANUP_CXX version.rc
Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384

Copyright (C) Microsoft Corporation.  All rights reserved.

	cl /errorReport:none /nologo /LDd /Zi pthread.obj version.res /link /implib:pthreadVCE3d.lib  /out:pthreadVCE3d.dll
cl : Command line warning D9025 : overriding '/Zi' with '/Z7'
cl : Command line warning D9025 : overriding '/Zi' with '/Z7'
   Creating library pthreadVCE3d.lib and object pthreadVCE3d.exp
	"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" /E clean VSE-debug
	if exist *.obj del *.obj
	if exist *.def del *.def
	if exist *.ilk del *.ilk
	if exist *.pdb del *.pdb
	if exist *.exp del *.exp
	if exist *.map del *.map
	if exist *.o del *.o
	if exist *.i del *.i
	if exist *.res del *.res
	if exist *_stamp del *_stamp
	cd tests && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" clean
	if exist *.dll erase *.dll
	if exist *.lib erase *.lib
	if exist _ptw32.h erase _ptw32.h
	if exist pthread.h erase pthread.h
	if exist semaphore.h erase semaphore.h
	if exist sched.h erase sched.h
	if exist *.e erase *.e
	if exist *.i erase *.i
	if exist *.obj erase *.obj
	if exist *.pdb erase *.pdb
	if exist *.o erase *.o
	if exist *.asm erase *.asm
	if exist *.exe erase *.exe
	if exist *.manifest erase *.manifest
	if exist *.pass erase *.pass
	if exist *.bench erase *.bench
	cl /errorReport:none /nologo /MDd /I. /DHAVE_CONFIG_H /W3 /Z7  /D__PTW32_BUILD_INLINED /D__PTW32_CLEANUP_SEH -c pthread.c
pthread.c
	rc /d__PTW32_ARCHAMD64 /d__PTW32_RC_MSC /d__PTW32_CLEANUP_SEH version.rc
Microsoft (R) Windows (R) Resource Compiler Version 10.0.10011.16384

Copyright (C) Microsoft Corporation.  All rights reserved.

	cl /errorReport:none /nologo /LDd /Zi pthread.obj version.res /link /implib:pthreadVSE3d.lib  /out:pthreadVSE3d.dll
cl : Command line warning D9025 : overriding '/Zi' with '/Z7'
cl : Command line warning D9025 : overriding '/Zi' with '/Z7'
   Creating library pthreadVSE3d.lib and object pthreadVSE3d.exp
	"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" /E clean
	if exist *.obj del *.obj
	if exist *.def del *.def
	if exist *.ilk del *.ilk
	if exist *.pdb del *.pdb
	if exist *.exp del *.exp
	if exist *.map del *.map
	if exist *.o del *.o
	if exist *.i del *.i
	if exist *.res del *.res
	if exist *_stamp del *_stamp
	cd tests && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Tools\MSVC\14.29.30133\bin\Hostx64\x64\nmake.exe" clean
	if exist *.dll erase *.dll
	if exist *.lib erase *.lib
	if exist _ptw32.h erase _ptw32.h
	if exist pthread.h erase pthread.h
	if exist semaphore.h erase semaphore.h
	if exist sched.h erase sched.h
	if exist *.e erase *.e
	if exist *.i erase *.i
	if exist *.obj erase *.obj
	if exist *.pdb erase *.pdb
	if exist *.o erase *.o
	if exist *.asm erase *.asm
	if exist *.exe erase *.exe
	if exist *.manifest erase *.manifest
	if exist *.pass erase *.pass
	if exist *.bench erase *.bench
	if not exist C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\packages\pthreads_x64-windows\debug\bin mkdir C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\packages\pthreads_x64-windows\debug\bin

C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\buildtrees\pthreads\install-x64-windows-dbg-err.log

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

cl : Command line warning D9025 : overriding '/Zi' with '/Z7'

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

cl : Command line warning D9025 : overriding '/Zi' with '/Z7'

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

cl : Command line warning D9025 : overriding '/Zi' with '/Z7'

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

Microsoft (R) Program Maintenance Utility Version 14.29.30141.0
Copyright (C) Microsoft Corporation.  All rights reserved.

The system cannot find the path specified.
NMAKE : fatal error U1077: 'if' : return code '0x1'
Stop.

Additional context
vcpkg.json
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "name": "test",
  "version": "1.0.0",
  "builtin-baseline": "25f613278886a8055aded1bffb14daba98c39d6c",
  "dependencies": [
    {
      "name": "fmt",
      "version>=": "9.1.0"
    },
    {
      "name": "mosquitto",
      "version>=": "2.0.14"
    }
  ]
}

I'm not able to repro this issue in my side. Seems like your Visual Studio is broken, please repair your VS and try again.

I've just repaired VS and the issue persists.

I found this issue 27258 which seems to have a similar error code.
But the fix should have been merged already?

#27258 is unrelated.
The system cannot find the path specified.
NMAKE : fatal error U1077: 'if' : return code '0x1'
Stop.

AFAICT if should be interpreted by the command interpreter, not run as an executable. Did you change ComSpec or replace cmd in another way?

Not that I know of. In environmental variables it is set to:
%SystemRoot%\system32\cmd.exe
Which I believe is default?

Not that I know of. In environmental variables it is set to: %SystemRoot%\system32\cmd.exe Which I believe is default?

This is okay.
The package builds in CI and is also known to build for users. The Makefile is fairly simple.
In your report, nmake seems to deal with all steps of the all target (including if) but fails on the first command of the install target. Strange.
Or is there anything preventing successful mkdir C:\Users\Mads\Documents\projects\testVcpkg\dependencies\vcpkg\packages\pthreads_x64-windows\debug\bin?

I don't think so, I can use mkdir from the cmd-prompt in the folder without any elevated rights.
I actually attempted to create the path manually prior to running cmake, but I believe it was deleted again.

@MadsTrel, does the problem resolve finally? it may due to long path in the directory? could you try a shorter directory?

That might have been the problem yes, can not say for sure. I moved my entire workspace directory to the C:/project at one point - after i saw several people say this might be a solution to various problems. And i haven't seen it since.


Multiple versions of libraries

As noted in https://github.com/observablehq/framework/pull/1015#issuecomment-1984893780, we can get duplicate versions of libraries. Sometimes this is because libraries themselves have non-overlapping version ranges (this is often the case with apache-arrow because they don’t use semantic versioning and frequently bump the major version number), and other times it’s because jsDelivr resolves the exact version of dependencies when a library is published and does not rebuild when dependencies are updated (this is most noticeable in the vega packages, and jsDelivr says that this behavior is by design).
So I think we’ll have to rewrite the imports we get from jsDelivr and re-resolve them against the versions we have locally, rather than respecting the baked-in versions that jsDelivr has. We could do this naively by respecting the major version, or better, we could load the package.json and respect the declared range.
And in the case of apache-arrow, I think we may chose to ignore the declared range, and force all versions to be the same (currently 15.0.1). This is particularly so because some libraries use instanceof checks on Arrow tables, so if you have multiple instances of Arrow loaded, things will break.
All in all, kind of a mess! But fortunately we can compensate for this mess as a static site generator. 🙂

If we re-resolve jsDelivr dependencies, we may want to apply content hashes to _npm during build also, or else cache-control: immutable could cause problems.

Fixes in #1021.


Add ability to have derivs everywhere.

New SS attribute "force_derivs", when nonzero, will store and compute
derivatives for all float-based symbols, even if dependency analysis shows
they are not needed.
This is handy for quantifying how good we are at recognizing when we need
derivs (answer: very good, only a small percentage of post-optimized syms
end up with derivs) and also for debugging suspected derivative problems
(by essentially forcing derivs on almost everywhere).
Also amend stats report how many symbols carry derivatives.

I pushed an updated with a new name for the attribute, that I liked better. No other changes.

LGTM


Bug: Non-editable variables only using the value from the latest server for that particular game

I have modified numerous service options to have variables that users can customize. For example, the ability to modify the server name or description as well as other values. These may be required or non-required, but they are visible and editable.
However, there are also other service options that are specified only by admins. Therefore these are classified as non-editable. They are still visible to the users and in most cases are required. This includes items such as an RCON port number or maximum players.
Issue: Any non-editable value seems to only use the value from the most recently created server for that particular game. For example, let's say we're talking about Minecraft. SRV1 has a non-editable value of {{SERVER_MAXPLAYERS}} which references the --max-players command in the startup command. Let's say SRV1 has a max players of 10. This command works normal when there is only one server. However, I created SRV2 for a friend which also has the max players variable. I created max players of 20 for SRV2. All works normal, it seems. However, the owner of SRV1 decided to change his server name to "Best Server" and then noticed that his max players changed from 10 to 20. He can't edit this because it's non-editable. I can edit this, but if he changes his startup arguments again, this value changes back to 20. I created SRV3 to test for myself. I configured SRV30 with 30 players. Now, if I edit either SRV1 or SRV2, the max players value now changes from 10 or 20 to 30. Thus, whichever server is the most recent is the one in which it seems the non-editable commands are following. These commands do not follow through to any other service options. For example, the {{SERVER_MAXPLAYERS}} value for Minecraft does not affect CS:GO. However, if I have 3 CS:GO servers, the same issue does persist.
I did not do further testing to determine if this being "not visible to the user" would affect anything. As you can imagine, this is really only a big deal because I specify non-editable RCON ports that the user should know. When SRV1 and SRV2 try to make a simple change to their server name or other value, their RCON ports change to whatever the most recent server is using for its RCON port and then they can't access RCON anymore.

We seem to have fixed this in develop at some point in time. I'll wait for you to play with it and confirm.

I have confirmed that this appears to be resolved in 0.6.