Missing openai.error module

When I try to run the python prompt2model_demo.py, there is a ModuleNotFoundError: No module named 'openai.error'.
I think this may have something to do with the openai library renew recently.

Thank you for surfacing this issue, @MarkJYC001. #378 will address this (by simply specifying the exact litellm and openai verisons to use). We will merge this PR in a few minutes, then the demo will be operational again.

For the future, we might consider looking at this discussion to update our scripts that use OpenAI https://github.com/openai/openai-python/discussions/742. openai.error is indeed one of the many things they have changed with the new release


Npm install fails

React-tap-event-plugin requires higher version of react.
npm ERR! peerinvalid The package react does not satisfy its siblings' peerDependencies requirements!  npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

See https://github.com/zilverline/react-tap-event-plugin/issues/38.

@oliviertassinari That doesn't help since the dependency is  in material-ui is react-tap-event-plugin": ">=0.1.3
Which would go up to 0.2.0
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

am getting this.
npm ERR! peerinvalid The package react does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>

@payner35 there is a pull request to fix this issue #1714

great... thanks.

got the same erorr

@shaurya947 Can you have a look? I think that a quickfix is needed here.

I've merged #1714. The error should go away now. Thanks @oliviertassinari!

Your welcome. You gonna have to publish 0.11.2 with the fix.

Yup, getting on it!

i am having the same problem too.

@dinardln if you pull the latest from master, this issue should have gone away.
As for support for v0.14.0-rc1, we're working on it and will try to include it in a new release of Material-UI which is most likely coming today.

still broken :(

Tried npm install material-ui with Node 4.1 today and got below error:
DBSQAs-MacBook-Pro:tquesto dbsqa$ npm install material-ui --save
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from material-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from material-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from react-tap-event-plugin will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm ERR! Darwin 13.4.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "material-ui" "--save"
npm ERR! node v4.1.0
npm ERR! npm  v2.14.3
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/dbsqa/Desktop/Tapas/RnD/Gitlabs/tquesto/npm-debug.log
DBSQAs-MacBook-Pro:tquesto dbsqa$

Looking forward to this being pushed to npm!

I included  "react-tap-event-plugin": "~0.1.3" in my dependencies in my own project (package.json) and i no longer have that problem since material-ui only requires a version>=0.1.3.

@olivierGM if i do that i get the error npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>... the project i'm working on is using react 0.14.0-rc1

I am using "react": "~0.13.3" and i am not ready to move to react 0.14 so this fix works for me (react 0.13)  but not 0.14...

+1, a fix for 0.14.* would be lovely :+1:

+1 for the update to 0.14!

Does the code from the react-0.14-support branch help you guys? Of course, it'll be a while before it is pushed to npm.

I tried adding it to package.json as "material-ui": "git@github.com:callemall/material-ui.git#react-0.14-support" and that did allow npm install to go through in my project. But then I discovered that my imports couldn't find material-ui and I believe that's because I'd need to manually build material-ui in my node-modules. Unfortunately, running npm i in there it gives me linting errors: https://gist.github.com/bdefore/56d92d050c86894c2390

If I comment out all the pipes to eslint in the gulpfile.js and run npm run build it appears to work for me. I also had to take out an instance in my code where I was using mui.Styles.ThemeManager(); .. this helps me move on for now, thanks @shaurya947

@bdefore glad you could get this through. I'm not sure which ESLint rule (if any) applies to the linting error you had.
As for the ThemeManager stuff, all that has changed! See here and here

In case anyone else is down this path, I ended up hitting a wall. The current state of react-0.14-support is not quite ready yet, I can get it to compile and partially style, but still get runtime errors about refs being on a parent instead of an owner. I think I saw an issue filed about that somewhere. I think I'll hold off for now.

@bdefore I get this error when using react 0.13.  did you cleaned you node_modules folders before trying the branch?

@cgestes I've reproduced the refs related error. There's nothing in my code that is using refs. Per the help documentation referenced, it recommends ensuring I don't have mismatching React versions in play, so I've done an npm list for both my root and the material_ui I've build in node_modules: https://gist.github.com/bdefore/a05d3a8254c6dc9ecb8a

I'm just starting out with React and wanted to use Material UI. So I'm not sure this is helpful, but here's what I ended up installing, and it resulted in no conflicts...
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>material-ui
Obviously I'm using React 0.13 instead of 0.14.

I got this problem
npm ERR! Darwin 14.5.0
npm ERR! argv "/opt/local/bin/node" "/opt/local/bin/npm" "install" "material-ui" "--save"
npm ERR! node v0.12.7
npm ERR! npm  v2.14.3
npm ERR! code EPEERINVALID
npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>|| ~0.13.x || ~0.12.x
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! Please include the following file with any support request:
npm ERR!     /Users/bunniehsieh/npm-debug.log
Which version should I use? 0.13 or 0.14?Thank you!!!!

@BUNNIEHSIEH if you want to use the current stable version of Material-UI, use React 0.13.3.
If you want to check out our experimental support branch for React 0.14, get the source code from the react-0.14-support branch and compile it using babel. If using this branch, I would recommend updating your global npm packages.

How can anyone try the react-0.14-support branch with those lint errors? I had to disable them manually as well.

@bdefore I also had the "ref owner" issue you refer to. As I had built material-ui locally my node_modules looked like your gist. You still have two instances of React - one at the top level and one in "node_modules/material-ui"
I deleted "node_modules/material-ui/react" and the problem was fixed

excellent @benjeffery thanks! works for me too.

This should be fixed with the latest release.

I tried to install material-ui today but get:

react-tap-event-plugin is a peer dependency. You have to install it on your project.

Ah ok, never used them before.

What is the correct way to go about solving this:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>No description ```

@QuantumInformation Have a look at our examples: https://github.com/callemall/material-ui/blob/master/examples/webpack-example/package.json.

@oliviertassinari thx, if I use them I get:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>No description

@QuantumInformation npm install --save react-tap-event-plugin history

That's an issue with react router and history. Not material ui.
Install the history version specified not the latest. It's on react routers change log. Sorry  I would link but I'm on my phone.

Here is the change log for the latest (as of now) version of react-router.


[SecretManagment not supported in non-standard Windows accounts] Get-Secret breaks JEA transcript

Hi,
I've been investigating an odd issue, where Get-Secret is exposed through JEA. And when it's called, it breaks transcript logging for the reminder of the entire JEA session. I wonder if this a bug, or by design.
JEA transcript log:

Windows PowerShell transcript start
Start time:<PHONE_NUMBER>5906
Username: n/a
Host Application: C:\Windows\system32\wsmprovhost.exe -Embedding
Process ID: 2956
PSVersion: 5.1.17763.771
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.771
BuildVersion: 10.0.17763.771
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: <IP_ADDRESS>
PS>CommandInvocation(Get-Secret): "Get-Secret"

ParameterBinding(Get-Secret): name="Name"; value="testcred"
ParameterBinding(Get-Secret): name="Verbose"; value="True"
ParameterBinding(Get-Secret): name="Debug"; value="True"
CommandInvocation(Out-Default): "Out-Default"

Windows PowerShell transcript end
End time:<PHONE_NUMBER>5913

thanks
Pete

Closing this issue as I feel it needs to be investigated by PowerShell team, since it is breaking PowerShell transcripts/data streams, and it has been transferred to PowerShell repository.

Oh, I see this is the same PR just transferred.  Re-opening.

@PaulHigin It looks like the microsoft-github-policy-service bot is over actively closing stale issues. Would you be able to reopen this?


fix: updated deps

:tada: This PR is included in version 1.10.100 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Do not start the search when columns are invalid

Added early abortion if unknown search field is found.


Reply – Reply number is 1 for user B when create a multi-level thread

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

Version Number: 9.0.21-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4863048
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Log in as user A
Open chat with user B
Log in as user B in Incognito tab
Open chat with user A
As user A send a message, reply in thread and send comment
Create a thread within the thread
Repeat steps until you have 5 different levels of threads
As user B observe chat

Expected Result:
Number of Replies is 5
Actual Result:
Number of Reply is 1
Workaround:
Unknown
Platforms:

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

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/1d7e8f93-7a39-44a3-8001-914f303b820a
View all open jobs on GitHub

We think that this bug might be related to #vip-vsp

@dylanexpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

BE issue : returning different action.childVisibleActionCount for the two users

Reviewing today!

BE element here

Will likely take a bit to find volunteer here

pending someone picking up

Same

Same

Closing for focus


Use thread-local storage for the global error state

I think this should resolve https://github.com/cython/cython/issues/4503


Implement @globalConstructor attribute

This attribute mirrors the behavior of __attribute__((constructor)) in C based languages to allow functions to run on the load of a binary / library. This is implemented with a new attribute that feeds the function into the global @llvm.global_ctors variable, which does the appropriate things per-platform.
https://github.com/apple/swift-syntax/pull/1120
https://forums.swift.org/t/pitch-globalconstructor/61901/3

https://github.com/apple/swift-syntax/pull/1120
@swift-ci please test

https://github.com/apple/swift-syntax/pull/1120
@swift-ci please test

https://github.com/apple/swift-syntax/pull/1120
@swift-ci please test

https://github.com/apple/swift-syntax/pull/1120
@swift-ci please test

https://github.com/apple/swift-syntax/pull/1120
@swift-ci please test

current windows failure appears unrelated

https://forums.swift.org/t/pitch-globalconstructor/61901


Update testsuite for Generator, simplify service provider and mock

Summary
I think the models were not typehinted because of Lumen etc. Now that we've bumped versions, we can skip Lumen.
Also simplified the serviceprovider and the mock a bit, to allow for testing the Generator.
The Filesystem mock only mock the Put method now, rest is not mocked (partial mock).
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[x] Misc. change (internal, infrastructure, maintenance, etc.)

Checklist

[ ] Existing tests have been adapted and/or new tests have been added
[ ] Update the README.md
[ ] Code style has been fixed via composer fix-style

Ah yes, of course the actual file is different based on the PHP version, which makes it a bit difficult I guess 🤔


Fix #42: Add means of formatting env values for gulp-eslint

Associated Issue:
#42
Changes made:

Add a simple mapping method to ensure that the config is formatted properly for gulp-eslint

does this need it's own issue?  not sure I'm seeing the direct connection to #42


Trying to fix the CI: py.test -> pytest

I'm still seeing things like https://github.com/robotools/fontMath/actions/runs/3649471028/jobs/6164190348

Please upload with the Codecov repository upload token to resolve issue.

which reminds me of https://github.com/fonttools/fonttools/issues/2763
I think we can try fix it in the same way

or we just accept codecov is flaky and make it not fail the whole PR checks

by which I mean changing this
https://github.com/robotools/fontMath/blob/678c0714d9f8dab1766612ac4c5c5b644b3a51fa/.github/workflows/run-tests.yml#L52
to

fail_ci_if_error: false

Working on this


publish<EMAIL_ADDRESS>

Requested by: @mitsuhiko
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Targets

[ ] github
[ ] gh-pages
[ ] registry
[ ] gcs
[ ] docker[release]
[ ] docker[latest]

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

ok, this issue is undead i think?  is that how craft works?  anyway, approve it now because we're trying to release today: https://github.com/getsentry/symbolicator/runs/4949148778

The action got stuck. I'm going to delete the tag in Symbolicator (required) and will then restart the action.


feat:修改线程死锁问题

Make sure that:

[ ] You have read the contribution guidelines.
[ ] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

hi，pls modify title to english


Ambiguous object reference - non system object

The following code gives an error that the reference to the No. Series table is ambiguous. I had a similar issue with referencing system tables (see #184 ) so this may or may not be a result of the same issue.
PROCEDURE IngredientNoSeriesIsDefault() : Boolean;
  var
    NoSeries : Record "No. Series";
  begin
    IF NoSeries.GET(DetermineIngredientSeriesNo) THEN
      EXIT(NoSeries."Default Nos.");

    EXIT(FALSE);
  end;

This issue seems to stem from the fact that I have defined a dependency to my library extension. As soon as I do that, every base object reference shows as ambiguous. If I remove the dependency the base object errors go away.

Thanks for the follow up. The root cause of this bug is the same as #184 and has been fixed for the May Update.


Flatten and simplify Helm charts

Consolidate into a single level of charts to simplify structure.

Problems with Travis


Added Aos animation on scroll to index.html and services.html page

I added Aos animation support on scrolling to index.html and services.html page. @harshgoel05

I will do check it and merge @Malhar37 . Tagging issue #8

Looks amazing! Good to go @Malhar37 . Thanks for contributing! 🚀

Will this pull request count to my progress in hacktoberfest? @harshgoel05


Categorize by enabled/disbaled

Would be particularly useful with FreeFlarum where there are a lot of extensions installed but not necessarily used

good idea! will add this hopefully soon


tilseq_mut no longer generates calibratePhred files

It appears that since the introduction of the --errorOverride flag, the script stopped generating calibratePhred files altogether, even when the flag is not used.

Nishka ran her workflow with the following parameters:
0.6.940
fastq,/home/rothlab/nkishore/ATP7B/TileSeq_R6_20230110/ATP7B_R6
output,/home/rothlab/nkishore/ATP7B/TileSeq_R6_20230110/ATP7B_R6
param,/home/rothlab/nkishore/ATP7B/TileSeq_R6_20230110/ATP7B_R6/20230110_TileSeqR6.csv
name,ATP7BDTR6
skip_alignment,False
r1,None
r2,None
log_level,info
environment,galen
at,48
mt,58
mm,15
c,8
base,33
test,False
rc,False
sr_Override,False
posteriorQC,False
wt_override,False
calibratePhredWT,True
calibratePhredPhix,False
errorOverride,False
resubmit,False
logger_time,300
version,None

Inspecting the logs from individual mut_count jobs:
2023-01-11 00:49:50,772 - main.log: INFO Counting mutations ...
2023-01-11 00:49:50,772 - main.log: INFO Removing existing phred files...
2023-01-11 00:49:50,786 - count.mut.log: INFO Counting mutations in sample-184
2023-01-11 00:49:50,786 - count.mut.log: INFO Sam file input R1:/home/rothlab/nkishore/ATP7B/TileSeq_R6_20230110/ATP7B_R6/ATP7BDTR6_2023-01-10-23-24-43/sam_files/184_S184_R1_001.sam
2023-01-11 00:49:50,786 - count.mut.log: INFO Sam file input R2:/home/rothlab/nkishore/ATP7B/TileSeq_R6_20230110/ATP7B_R6/ATP7BDTR6_2023-01-10-23-24-43/sam_files/184_S184_R2_001.sam
2023-01-11 00:49:50,791 - main.log: INFO Running multi-core analysis ...
2023-01-11 00:49:50,815 - count.mut.log: INFO Start reading SAM files...
2023-01-11 00:54:56,299 - count.mut.log: INFO File streamed to subprocesses, waiting for jobs to finish...
2023-01-11 02:10:56,560 - count.mut.log: INFO Pool closed
2023-01-11 02:10:56,571 - count.mut.log: INFO Raw sequencing depth: 2973985
2023-01-11 02:10:56,571 - count.mut.log: INFO Number of reads without mutations:2306600
2023-01-11 02:10:56,571 - count.mut.log: INFO Final read-depth: 2953779

Compared against the log statements from main.py:
# submit job with main.py -r1 and -r2
        # run main.py with -r1 and -r2
        logger_mut = self._logging.getLogger("count.mut.log")
        self._log.info("Removing existing phred files...")
        #phred_flist = glob.glob(os.path.join(self._output, '*_phred.*'))
        #if phred_flist != []:
        #    os.system(f"rm {os.path.join(self._output, '*_phred.*')}")
        mut_counts = count_mut.readSam(self._r1, self._r2, self._param_json, self._args, self._output, self._args.c, logger_mut)
        self._log.info("Running multi-core analysis ... ")
        if self._args.calibratePhredWT:
            self._log.info("Adjusting phred scores using WT samples...")
            adjusted_phred = mut_counts.adjust_er(wt_override=self._args.wt_override)
        elif self._args.calibratePhredPhix:
            self._log.info("Adjusting phred scores using Phix...")
            adjusted_phred = mut_counts.adjust_er_phix()
        else:
            adjusted_phred = []
        mut_counts.multi_core(adjusted_phred)

We can see the Removing existing phred files.. and Running multi-core analysis ...  messages, but no Adjusting phred scores using WT samples..., which means it did not evaluate self._args.calibratePhredWT as true. So the problem would appear to lie with the calibratePhredWT flag not being set despite it being used as a command line argument


Error handling: what to do with @ethersproject/logger?

Follow-up after #1153.
What should we do with the usage of @ethersproject/logger for throwing errors? Currently, throwing errors is done in two ways inside of the SDK, either via throw new Error(...) or logger.throw(...).
With the merging of #1153, we have a standardized way of throwing errors via new FuelError(...) and we need to start doing #1156. Should we just get rid of @ethersproject/logger as it was, as far as I can tell, only used in conjunction with our versions package to log the version alongside the error? Now FuelError has the SDK version info on it directly and I don't see the need for having the @ethersproject/logger dependency.

I agree that following #1153 we should now deprecate the usage of @ethersproject/logger in place of using a FuelError

I think we can move to FuelError completely


Questions about Geowave-Geoserver plugin error

Hi all.
I have questions about geowave-geoserver plugin. it's ok until before maybe 1~2 months ago update 0.9.8 and early 1.0.0. Recently it's not good to work with geoserver. before guess 2 weeks ago, i asked that geoserver didn't make new geowave data store. but at that time geowave command that 'geowave gs addlayer' was working and good to connect with geoserver for publishing a layer. However nowadays it's all not working. it's all the same environment. Is this coz the jar file version both geowave-accumulo or geowave-geoserver is not correct? anyway i'd attach the error log when i was commanded 'geowave gs addlayer'  and version info.
version info;
geoserver : 2.13.2
geowave tools jar: 1.0.0-cdh5-tools
geowave accumulo jar : 1.0.0-cdh5-accumulo
geowave geoserver jar : deploy-1.0.0-geoserver ('1.0.0-cdh5-geoserver' is not work at geoserver. The 'gs addlayer' command is not accepted with 404 or 500 error.)
cdh5 name node with accumulo and geoserver is different device. but no matter to ping-pong with cdh5 zookeeper like 'ingest' on cli
it's geowave side typed in 'gs addlayer';

it's geoserver side after sending geowave command;

the results on geoserver browger;

I keep try to fix up using many ways but situation is worse. i think it's not normal. Did i mistake something? so Please let me know what is problem and how to fix up please...ASAP
plus. The geowave-geoserver-1.0.0.jar I made in September is fine.

Sorry, I hope I had answered this on another channel and didn't just completely miss this.  This looks to be pretty clearly a result of our update to GeoServer 2.14.0 ... generally speaking we can be backwards compatible with previous geotools/geoserver releases, but the step to 2.14.0 has breaking changes in the JTS package renaming that make backwards compatibility impossible.  I hope you had found that upgrade your version of GeoServer solves this issue!  And very sorry if I did just completely miss this one earlier.


Added highlight for the 'unchanged' lines diffs

Altered lua/neogit/status.lua and /syntax/NeogitStatus.vim so the unaltered lines in diffs have a highlight called NeogitDiffDelete

Could you squash down your commits? Looks like you have some artifacts from integrating upstream changes in there


Consider both contiguous and channels_last tensors for FusedSGD

Authored by @luise1030 to address the issue of tensor memory type inconsistency on Resnet50 trained with NHWC format.
To run the corresponding unit tests for the code changes in this PR:
$ python tests/L0/run_test.py --include run_optimizers
test_float (test_fused_optimizer.TestFusedSGD) ... ok
test_half (test_fused_optimizer.TestFusedSGD) ... ok
test_multi_device (test_fused_optimizer.TestFusedSGD) ... ok

Internal JIRA ticket for the context: https://ontrack-internal.amd.com/browse/SWDEV-357815

This PR is to resolve the issue when p in parameters() of apex.optimizers.FusedSGD and p.grad are not same memory format.


Add Support JSON output

Add support json output  reference issue #54

Thanks! Making release v<IP_ADDRESS> to include this


Autorest Regen Preview to 3.0.0-alpha.20230828.4 by Anne Loomis Thompson from refs/pull/3674/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3674
This completes the work started in https://github.com/Azure/azure-sdk-for-net/pull/38286

Closing in favor of generated PR: https://github.com/Azure/azure-sdk-for-net/pull/38396


[RCNConfigContent copyFromDictionary:toSource:forNamespace:] crash

[REQUIRED] Step 2: Describe your environment

Xcode version:  10.2.1
Firebase SDK version:  6.4.0 ~ 6.5.0
Firebase Component: RemoteConfig
Component version: 4.2.1

[REQUIRED] Step 3: Describe the problem
We're seeing some crashes in the wild, with stack trace:
Crashed: com.google.GoogleConfigService.FIRRemoteConfig
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000010

0  CoreFoundation                 0x1f11cb2b0 -[__NSDictionaryM setObject:forKeyedSubscript:] + 500
1  our app                       0x102a35518 -[RCNConfigContent copyFromDictionary:toSource:forNamespace:] +<PHONE_NUMBER>
2  our app                       0x102a31b00 __49-[FIRRemoteConfig activateWithCompletionHandler:]_block_invoke +<PHONE_NUMBER>
3  libdispatch.dylib              0x1f0d14a38 _dispatch_call_block_and_release + 24
4  libdispatch.dylib              0x1f0d157d4 _dispatch_client_callout + 16
5  libdispatch.dylib              0x1f0cf0dec _dispatch_lane_serial_drain$VARIANT$armv81 + 548
6  libdispatch.dylib              0x1f0cf192c _dispatch_lane_invoke$VARIANT$armv81 + 408
7  libdispatch.dylib              0x1f0cf9e08 _dispatch_workloop_worker_thread + 584
8  libsystem_pthread.dylib        0x1f0ef6114 _pthread_wqthread + 304
9  libsystem_pthread.dylib        0x1f0ef8cd4 start_wqthread + 4

crash happen at:
-[RCNConfigContent copyFromDictionary:toSource:forNamespace:] +<PHONE_NUMBER>

Hi..we are trying to repro this. In the meantime, would be useful to know if any others are seeing this.
Few questions:
a. Are you integrating with the FirePerf SDK?
b. Can you share the code snippet of how/where you integrate with RC?
c. Are you able to repro this by yourself? If so, repro steps would be useful.
d. Is it possible to know how frequent and the devices on which this is failing?

Seeing this crash as well.
a. Yes
b. Below
c. No luck so far
d. So far we have seen crashes on iOS 12.3.1 and 12.4 on various devices iPhone7+
RemoteConfig.remoteConfig().activate { _ in
    RemoteConfig.remoteConfig().setDefaults(<dictionary here>)
    RemoteConfig.remoteConfig().fetch(withExpirationDuration: 60) { status, _ in
        guard status == .success else { return }
        RemoteConfig.remoteConfig().activate(completionHandler: { _ in
            <our logic here>
        })
    }
}

We do not have a repro yet, but have some overall stability improvements which should hopefully fix this issue. Please retry with the upcoming Firebase release (next week) and reopen if still an issue.


Incorret offset in DB for java.time.LocalDateTime

I used JPA2.1 converters for my LocalDateTime fields to convert them to java.sql.Timestamp before save. All working fine until I decided to use hibernate-envers which is not support JPA2.1 converters. Then I switched to hibernate @Type annotation using jadira-usertypes extension.
First it seems working fine but then I notice then all my localdatetimes stored in DB with offset (+3h). When it retrieved it of course converted back (-3) and all seems to working fine. But it is not. It is wrong because LocalDateTime is designed to represent not instant in time but some local datetime for current place (whichever place you located at the moment). So when it saved to DB it must not use any timezone information. It must just be saved AS IS.
For example if I read my DB from another PHP application it must apply (-3) offset to all dates. Or if my database already filled with some data - all local dates will be wrong when read by this jadira mapper.
My DB isq Mysql with date type is DATETIME and the field represent exactly what LocalDateTime was designed for - start of working day - it is timezone agnostic. If Bob starts working at 8:00 it starts working at 8:00 in place where it working even if I observe he's working graphic from another timezone.
This bug also was found on this  stackoverflow (not mine): http://stackoverflow.com/questions/31826867/how-to-setup-jadira-persistentlocaldatetime-with-java-time-localdatetime

Setting
jadira.usertype.javaZone=Z
jadira.usertype.databaseZone=Z

or
jadira.usertype.javaZone=jvm
jadira.usertype.databaseZone=jvm

also doesn't help.
(It actually helps in my DEV enveronment with H2 databse, but doesn't help in my production environment with MySQL databse).

In my project I created custom implementation of PersistentLocalDateTime and TimestampColumnLocalDateTimeMapper for it.
public class PersistentLocalDateTime
		extends AbstractVersionableUserType<LocalDateTime, Timestamp, TimestampColumnLocalDateTimeMapper>
		implements ParameterizedType, IntegratorConfiguredType {

	private static final long serialVersionUID = -2195437660203845282L;

	@Override
	public int compare(Object o1, Object o2) {
		return ((LocalDateTime) o1).compareTo((LocalDateTime) o2);
	}

	@Override
	public void applyConfiguration(SessionFactory sessionFactory) {

		super.applyConfiguration(sessionFactory);

		TimestampColumnLocalDateTimeMapper columnMapper = getColumnMapper();
		columnMapper.setDatabaseZone(null);
		//columnMapper.setJavaZone(null);
	}
}

public class TimestampColumnLocalDateTimeMapper extends AbstractTimestampThreeTenColumnMapper<LocalDateTime> implements DatabaseZoneConfigured<ZoneOffset> {

	private static final long serialVersionUID = -2085262909771406619L;

	public static final DateTimeFormatter LOCAL_DATETIME_FORMATTER = new DateTimeFormatterBuilder().appendPattern("yyyy-MM-dd HH:mm:ss").appendOptional(new DateTimeFormatterBuilder().appendLiteral('.').appendFraction(ChronoField.NANO_OF_SECOND, 1, 9, false).toFormatter()).toFormatter();

	public TimestampColumnLocalDateTimeMapper() {
		super();
	}

	public TimestampColumnLocalDateTimeMapper(ZoneOffset databaseZone) {
		super(databaseZone);
	}

    @Override
    public LocalDateTime fromNonNullString(String s) {
        return LocalDateTime.parse(s);
    }

    @Override
    public LocalDateTime fromNonNullValue(Timestamp value) {
    	return value.toLocalDateTime();
    }

    @Override
    public String toNonNullString(LocalDateTime value) {
        return value.toString();
    }

    @Override
    public Timestamp toNonNullValue(LocalDateTime value) {
        return Timestamp.valueOf(value);
    }

	@Override
	public ZoneOffset parseZone(String zoneString) {
		return ZoneOffset.of(zoneString);
	}
}

This mapper works fine and correctly saves LocalDateTime to DB in both environments (DEV with H2 databse and PROD with MySQL).
I don't know if this correct approach and also some code may be redundant (overriding some methods, unused static field) but it works.

With MySQL it is recommended to pass the connection parameters "zeroDateTimeBehavior=convertToNull&useLegacyDatetimeCode=false". Can you confirm you are using these?

I am using zeroDateTimeBehavior=convertToNull but not using useLegacyDatetimeCode=false. May it help? I will try later on monday.

Yes, useLegacyDatetimeCode=false helps me. With this jdbc-connection setting org.jadira.usertype.dateandtime.threeten.PersistentLocalDateTime starts work as intended.
Thanks for help.


feat: declare module name based on federation alias with --useFederatedAlias

I would like to propose new optional --useFederatedAlias argument which takes precedence over automatically generated module name in declaration file (*.d.ts):
AS IS:
a) With federation.config.json like this:
{
  "name": "app",
  "exposes": {
    "./ComponentA": "./src/shared/ui/ComponentA",
    "./ComponentB": "./src/shared/ui/ComponentB",
  }
}

make-federated-types produces the following declarations (shared path is omitted):
declare module "app/ui/ComponentA"
declare module "app/ui/ComponentB"

b) With federation.config.json like this:
{
  "name": "app",
  "exposes": {
    "./ComponentA": "./src/shared/ui/ComponentA",
    "./ComponentB": "./src/test/ui/ComponentB",
  }
}

make-federated-types produces the following declarations (shared and test path are taken into module names):
declare module "app/shared/ui/ComponentA"
declare module "app/test/ui/ComponentB"

As you can see generated module name depends on source path (imho ts.createProgram somehow combines path) and you can not rely on this name during the imports on remote applications because you can have two possible import paths (and you don't know which one will be generated):
import ComponentA from "app/ui/ComponentA"; // with a)
// or
import ComponentA from "app/shared/ui/ComponentA"; // with b)

TO BE:
make-federated-types --config ./path/to/my/config.json --useFederatedAlias
When you have federation.config.json like this:
{
  "name": "app",
  "exposes": {
    "./ComponentA": "./src/shared/ui/ComponentA",
    "./ComponentB": "./src/shared/ui/ComponentB",
  }
}

make-federated-types produces the following declarations:
declare module "app/ComponentA"
declare module "app/ComponentB"

When you have federation.config.json like this:
{
  "name": "app",
  "exposes": {
    "./myScope/ComponentA": "./src/shared/ui/ComponentA",
    "./myScope/ComponentB": "./src/test/ui/ComponentB",
  }
}

make-federated-types produces the following declarations:
declare module "app/myScope/ComponentA"
declare module "app/myScope/ComponentB"

Nice PR!
But
You should use path.join instead of `replace('./', '')
Just like in my closed PR:
https://github.com/pixability/federated-types/pull/12/files#diff-180b3d2af89416b99563fff8c37eb8ca1ef7591fc1ddd736b5dacf740ccd3760R80
const moduleDeclareName = path.join(federationConfig.name, exposeName).replace(/[\\/]/g, '/');

Also:
ts.createProgram + emit() may generate additional declarations
Example:
"exposes": {
  "./BellIcon": "./src/components/icons/BellIcon",
  "./MainAppContextProvider": "./src/components/main-app-context/MainAppContextProvider"
}

Generates 3 declarations, not 2:
declare module "icons/BellIcon" {
  ...
}
declare module "main-app-context/MainAppContext" {
  ...
}
declare module "MainAppContextProvider" {
  ...
}

So your compileKeys[index] won't match found moduleName

@crutch12 Nice catch! Thanks!
I have fixed PR with you solution and removed redundant --useFederatedAlias

@gthmb WDYT about this? :)

@crutch12 Nice catch! Thanks!
I have fixed PR with your solution and removed redundant --useFederatedAlias

Nice!
I think it's right decision: useFederatedAlias should be default behavior.
But it's breaking change, so we have to release a new minor version :) (v0.2.0)

I think it's right decision: useFederatedAlias should be default behavior.

Exactly, I think the same that exposed name should take precedence over module name  👍

But it's breaking change

We can keep compatibility but after this we should introduce new argument for using exposed name as module name

@gthmb Do you still support this package?


Error occurred when executing DownloadAndLoadFlorence2Model:  Object of type Florence2LanguageConfig is not JSON serializable

This is caused by the transformers version is incompatible, so just
pip install --upgrade transformers should be fix this issue


Should we allow duplicate programs within a channel?

I have channels that just rotate through all of the Fast & Furious movies, so the same movies are in the channel multiple times per day.  I could also see there being a use case for kids content, where kids like very specific episodes and people make channels that rotate through a select number of episodes.

Yea naturally the channels will loop, but in the programming editor you could add the program multiple times and it would loop on top of that. It's kinda a nuance I guess and not really something that matters in practice
For instance a lineup could be

Program 1
Program 2
Program 1
Loop

So then you have back to back Program 1


Configurable connect function

The connect function does all the things that are required for connection itself. However there could be other things around it which could be customised, e.g. execute a command/script after a connection is created. This particular feature is implemented with a callback (#160). However there are variations which make it too much to implement, e.g. execute a command/script before a connection is created.
It is already possible to define a custom function that does what connect does and more. This new function can be used in place of connect function after the peek is launched. However, at launch time, the connect function is used internally to create the default connection and this is not replacable. Do we want to allow it to be replaced? Or is it sufficient if #162 is implemented?

Accidentally closed. Reopen.


Remote desktop app does not handle key input properly in Samsung Dev

Tested in my Galaxy S21 Dex mode with external monitor and bluetooth keyboard, with latest version of MS Remote desktop (<IP_ADDRESS>4), with Android 12.0
When I use IME(Japanese) on a remote PC(Windows 10 Pro), it seems MS remote desktop app sends unicode instead of scancode, so it ends up IME not recognizing characters I type as “raw input” and it does not convert into Japanese.
I know this app has an option in setting “use scan code input when available”. however this did not fix even if I turn this option on or off.
I tried the same using Parallels Client, exact same setup on Samsung Dex and it did not have this issue at all.
Please see video below for evidence.
https://drive.google.com/file/d/1PX-4AfNHQOjJGWotW2UUqyeP2t3UVQ1g/view?usp=sharing

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


Gotta return

Adds missing return to generated initialViewController method in storyboard templates.

Thanks for the PR!
Damn, I really need to make this script checking that the templates compile work some day!

Damn I merged before realizing you forgot to add entry in CHANGELING ^^ I will add it on master.


Add missing max. number of samples (MSAA) check

Fixes #9908.
OpenGL ref - glRenderbufferStorageMultisample

Hm, would be interesting to retrieve this value in-game somehow, so if we add a "Graphics Options" menu, it's possible to limit to the player's hardware capability.

More globally, we could have something like Engine.get_graphics_capabilities() which would return a dictionary of such driver-dependent values.

Hm, would be interesting to retrieve this value in-game somehow, so if we add a "Graphics Options" menu, it's possible to limit to the player's hardware capability.

Indeed !
If there is a way to retrieve this value, I'm interested.

@fabriceci Is there a lot of hardware out there that doesn't support MSAA past 8×? (I don't consider 16× MSAA here as it's too expensive to be usable in a modern engine.)

@Calinou I had the warning on mac when I try to set 16x MSAA, that what leads me to this issue, I will limit MSAA to 8X to get rid of that like you suggest and explained.
To be honest, I thought 16x was too much, but by tests, I noticed that it's the only one that be able to remove scaling effect on cube's edges (a bit less notable here due to compression): , but I can live with that.


Use linkify-it instead of custom regex

The library is more reliable way of detecting links and fixes some of the
edge cases old regexes were failing at. For example:

node.js is not an url.
e.g. is not an url
unicode links
only links in valid TLDs are detected.

Fix #6, fix #4

:+1:

:+1:

@tasti can you merge/release this one please? it will make component way more useful :)


Potential Additions

I've been using street mix and think its great for quick mock ups but have noticed a couple things that could be improved to make it even better.
Storm water planters and rain gardens
Bumpouts with parking lanes (similar to parklets already in streetmix)
Ability to adjust setback on buildings.
Curb and gutter allowance.  Depending on the community, curb and gutter will take up between 6" and 2.5' per side of road.  Sometimes this can be used as part of the streets, as in the case of parking.  Sometimes it can't
Addition of text (or manual override) at bottom

We've heard a lot of this feedback before, and this is where I stand on some of these:

Stormwater management - This would be good to have, but we don't actually know anything about this
Bumpouts in parking lanes - I'd love to do this, but we don't have a good way of implementing this right now.
Building setbacks - This is not likely to happen. I'm intentionally opinionated about the street wall.
Curbs and gutters - If there's an automatic way of inserting them where it makes sense, that might work.
Manually overriding text on the bottom - We'd like to do this.

If there's anything you would like to contribute to specifically, please find or open individual issues for each subject area. Otherwise, thanks for the feedback!


add ::theme and ::part selectors

It would be awesome to know the support for these.
https://css-tricks.com/part-theme-explainer/

I'm looking forward to this as well, although it might be a bit before we need the tables.  I don't think they're implemented anywhere yet since it's still a draft.

I'm looking forward to this as well, although it might be a bit before we need the tables. I don't think they're implemented anywhere yet since it's still a draft.

That link is now deprecated and replaced by this one:
https://drafts.csswg.org/css-shadow-parts/

Available at https://caniuse.com/#feat=mdn-css_selectors_part


all chart and reports related to engagment type are done. except for …

…cascading college filter

#459 , #825 , #821 , #824  are all done with this same pull request


Newsletter 11: NodeFX

Part of #172.
Unsure if there's any specific order to the newsletter, but I tried to mirror what was in #172.
If there is any issues, I'll be available for the next few hours.

Merged, thanks!

Made a few small style tweaks

I actually had them on separate lines like that originally, haha.


Power Automate Flows as Templates

I was looking for an answer to the question s it possible to create and share templates privately (either within and organisation or across organisations) - this page may benefit from an answer to that question (I presume it is currently not supported)?

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

ID: 3bf8d0d2-3a6f-c3f1-494d-b0ea73c22f9b
Version Independent ID: 41bc35b2-5a4d-7406-1ae7-27b292033fcd
Content: Submit a cloud flow template - Power Automate
Content Source: articles/publish-a-template.md
Service: power-automate
Sub-service: cloud-flow
GitHub Login: @MSFTMan
Microsoft Alias: deonhe

@iddycol Thanks for reporting this issue. Templates are for the public gallery only. We've updated the article and you'll see this update within 24 hours.


docs: Add Committer Expectations document

Collect up all the committer expectations and PR requirements into a single place. Add additional guidelines about creating small PRs and how to break up PRs into multiple commits.
Signed-off-by: Keith Short<EMAIL_ADDRESS>

Marked as a draft, but this is ready for feedback. Once the content has of this doc has consensus, I'll also update the guidlines.rst to remove redundant/obsolete info and link to this doc.

https://github.com/zephyrproject-rtos/zephyr/issues/50836

Commit https://github.com/zephyrproject-rtos/zephyr/commit/16bdac253c34019a2dbcf66a89bacff8231a2085 is a rebase only.

@fabiobaltieri ping

Commit https://github.com/zephyrproject-rtos/zephyr/commit/20d2c15ff4c233c383b220254a96ad2e03aa936d is a rebase only.  I still need to address outstanding comments.

Commit https://github.com/zephyrproject-rtos/zephyr/commit/12ca7f4c05d8cb5126b985179446d704257d7cf0 is another rebase before the resolving the open comments.

Highlights of https://github.com/zephyrproject-rtos/zephyr/commit/f7aa72f2dd7c0fe7b20cb633792c0d6bc50162a1:

Changed references of "you" to committer/reviewer as appropriate
Small PRs -> Smaller PRs
Provided additional details for when to add new tests (under "Defining Smaller PRs)

@keith-zephyr thank you for taking the time to look at and work towards refining the language, this looks pretty good to me now. I will spend some time looking things over one more time before I add a +1, but my concerns I believe have all been addressed.

for some open source projects, "committer" has a very different meaning from what is implied here, one that is closer to our definition of maintainer I guess. I would expect that a vast majority of first-time contributors wouldn't consider themselves "committers" and would

that is actually a very good point, goes unnoticed when you are in the weeds. We should stick to the existing terminology we use across the documnetation, which is 'contributor' if I am not mistake.

for some open source projects, "committer" has a very different meaning from what is implied here, one that is closer to our definition of maintainer I guess. I would expect that a vast majority of first-time contributors wouldn't consider themselves "committers" and would

that is actually a very good point, goes unnoticed when you are in the weeds. We should stick to the existing terminology we use across the documnetation, which is 'contributor' if I am not mistake.

Sounds good.  I'll make the change from "committer" to "contributor".  This permits me to link to the existing contributor definition.
Lots of quality feedback is coming in, so I'm going to let the current commit soak a bit and push a new version capturing the outstanding comments by the end of the week.

for some open source projects, "committer" has a very different meaning from what is implied here, one that is closer to our definition of maintainer I guess. I would expect that a vast majority of first-time contributors wouldn't consider themselves "committers" and would

that is actually a very good point, goes unnoticed when you are in the weeds. We should stick to the existing terminology we use across the documnetation, which is 'contributor' if I am not mistake.

Sounds good. I'll make the change from "committer" to "contributor". This permits me to link to the existing contributor definition.

Great!

Lots of quality feedback is coming in, so I'm going to let the current commit soak a bit and push a new version capturing the outstanding comments by the end of the week.

Sounds great -- I might actually have another pass then, if I'm not that late in the end :)

for some open source projects, "committer" has a very different meaning

This meaning is now obsolete but I'm afraid you're right, that old terminology seems to be still sticking in a number of places. Best avoided.
https://en.wikipedia.org/wiki/Committer#Commit_bit
https://www.freebsd.org/internal/proposing-committers
<gray beard trivia>
In obsolete centralized version control (before the bitkeeper/git/mercurial/... revolution) you cannot commit in private, every commit is public. So commits had to be restricted to a limited number of powerful "committers". I remember very clearly teaching myself git-svn for this only purpose: use local commits and branches to manage work in progress privately.
Just for fun, someone thinks commits should be restricted even in private: https://fossil-scm.org/home/doc/trunk/www/rebaseharm.md


Fix decoding of BASIC auth credentials

The decoding process is messing up passwords that contain a ":"
character. For example,
if a username/password combination like { "user", "abcd:1234" }
is passed in, the password is interpreted as "abcd".
This commit fixes that problem. The first colon encountered in the auth
string is the only one that's interpreted. That is, in this commit,
the password is correctly interpreted as "abcd:1234".

does your fix address the possibility of multiple colons?

Yes. In basic auth, we see a Base64-encoded USERNAME:PASSWORD. Jaasmine splits on the ":". Came across a user with a ":" in the password (USERNAME:PASS:WORD). This fix addresses that.


[iOS] Sample App Update

Related Issue
Description

Allow flexible width for AdaptiveCards when the width is set to 0
Fixed background image issue when loaded from a resource bundle
Fixed having extra space when a large image is scaled down in a column.
Updated Input Wrapper View's intrinsic content size
Update Content View to better manage its subviews content size
Fixed background Image rendering for inner AdaptiveCards of ShowCard
Changed sample app to update a row instead of table view when resources are loaded
Updated sync mechanism
Updated scroll behavior
Updated app to test images in a resource bundle

How Verified
Before Fix

After Fix

Looks good -- just to be clear, there aren't any breaking changes here?

Yes, there are no breaking changes.


unstable accessory

hello I have created
https://github.com/ageorgios/esp-homekit-motor
but I find the accessory quite unstable
in the log I have this when the accessory is marked unresponsive, I cannot understand the reason it is happening and when.
>>> homekit_client_process: [Client 6] Finished processing
>>> mdns_recv: pbuf too big
>>> HomeKit: [Client 5] Closing client connection
>>> homekit_client_process: [Client 6] Got 129 incomming data
>>> homekit_client_process: [Client 6] Decrypting data
>>> homekit_client_process: [Client 6] Decrypted 111 bytes, available 0
Decrypted data (111 bytes): "GET /characteristics?id=1.11,1.10 HTTP/1.1\x0D\x0AHost: ESP\\032Homekit\\032Motor\\03212\\0581C\\0584C._hap._tcp.local\x0D\x0A\x0D\x0A"
>>> HomeKit: [Client 6] Get Characteristics
>>> homekit_server_on_get_characteristics: Free heap: 23136

any ideas?

"No Response" is not related to what you see in this log, it is a problem with mDNS/Bonjour. Maxim is aware of issues with mDNS, but we have yet to find the solution.
Try updating the esp-homekit submodule there was one change that might improve it for your network situation.

you are right! wasn't on latest commit! definitely improved!


Draft: Move login methods into a dedicated UserAuthModal

Draft #39 so there's already a start.
To be done:

Style it: https://www.figma.com/file/396p2PzjnIXSbHmuBuj7oK/Website?type=design&node-id=3531%3A6970&t=dMENrEOC7TIIGXF6-1
Email input with deep link into Sequence email auth popup
Auto-trigger the login modal on first load, but not on refresh

were you following wagmi/seq best practices to add a mount hook b.c our Next version isn't up to date? https://docs.sequence.xyz/wallet/connectors/FAQ/#how-do-i-use-a-wallet-library-and-connector-with-nextjs-using-the-pages-directory-all-versions-of-nextjs

Not even! I was googling for solutions and this came out. Kind of sad that this is the documented best practice hah. I kind of like their approach though 🤔


Mac binary scripts/ contain temp files

There are *~ files in several releases. Is something wrong with a release script? Should they clean the tree?

I think these were fixed, and with #951 we can build from clean trees on buildbot.
Not sure about the scripts situation at this point.

Yes, the scripts have been improved, manual builds could possibly still include temp files, but buildbot should always generate clean builds.


Conjuctions like the/as/that etc. are not searched

Hi,
It looks like lunr by default, not search for conjunctions. Is there any way to stop this default behaviour?
Example - search for the/as/that on https://olivernn.github.io/moonwalkers/
Related issue - https://github.com/olivernn/moonwalkers/issues/2
Thanks.

These words are filtered out by the lunr.stopWordFilter. The goal is to remove additional words that are typically not very much use for determining the relevancy of a search to a document.
This behaviour is the default and it can be disabled by removing the lunr.stopWordFilter from both the indexing and searching pipelines:
lunr(config => {
  config.pipeline.remove(lunr.stopWordFilter)
  config.searchPipeline.remove(lunr.stopWordFilter)
})


ArrayIndexOutOfBoundsException in TaskAdapter

Process: com.google.codelab.networkmanager, PID: 17258
java.lang.ArrayIndexOutOfBoundsException: length=12; index=-1
at java.util.ArrayList.get(ArrayList.java:310)
at com.google.codelab.networkmanager.TaskAdapter$1.onClick(TaskAdapter.java:98)
at android.view.View.performClick(View.java:5198)
at android.view.View$PerformClick.run(View.java:21147)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5417)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Error occurs when try to delete an item from list

I can confirm this: happens when you start the network-manager-start app and click delete very fast.

Exactly when I am getting the error. Try adding many Requests and delete first one.

Classic issue with the second call of onClick not being expected. The disable doesn't happen fast enough.
The best way to deal with this is using the onClick annotation of ButterKnife, which handles debouncing for you.
Alternatively, you can add a boolean that's checked for, so that the onClick cannot be called twice.
Likely not worth adding to the codelab though since it would be additional distracting code that doesn't serve to illustrate the point of the exercise.

I agree that Codelabs should have as little code as possible. But they should also be (like any other software) technically correct: crashes or severe bugs are not acceptable.
At least, there should be a comment to explain that there are some known problems and how to fix them.


ARM Port

Would it be possible to add an official ARM port of this for armhf and aarch64?  NATS itself supports ARM and this seems like a great message bus for IoT and embedded devices.  With AWS supporting ARM on Graviton and soon EKS I think it would make sense to add an ARM port of this operator.

So, just out of curiousity I created an ARM build of the Operator at:
charlesdburton/operators:nats
Seems to work fine:
time="2019-06-12T20:02:42Z" level=info msg="nats-operator Version: 0.5.0-v1alpha2+git"
time="2019-06-12T20:02:42Z" level=info msg="Git SHA: 7ecd1fc"
time="2019-06-12T20:02:42Z" level=info msg="Go Version: go1.12.5"
time="2019-06-12T20:02:42Z" level=info msg="Go OS/Arch: linux/arm64"
time="2019-06-12T20:02:42Z" level=info msg="nats-operator is operating at the namespace scope in the "default" namespace"
time="2019-06-12T20:02:59Z" level=info msg="Event(v1.ObjectReference{Kind:"Endpoints", Namespace:"default", Name:"nats-operator", UID:"c1cee45f-8d35-11e9-979d-b827eb6dba96", APIVersion:"v1", ResourceVersion:"2214253", FieldPath:""}): type: 'Normal' reason: 'LeaderElection' nats-operator-844dc7d468-fsb7b became leader"
time="2019-06-12T20:03:00Z" level=info msg="started workers" pkg=controller
time="2019-06-12T20:03:18Z" level=info msg="waiting for pod "default/nats-cluster-1" to become ready" cluster-name=nats-cluster namespace=default pkg=cluster
time="2019-06-12T20:03:21Z" level=info msg="pod "default/nats-cluster-1" became ready" cluster-name=nats-cluster namespace=default pkg=cluster
time="2019-06-12T20:03:21Z" level=info msg="waiting for pod "default/nats-cluster-2" to become ready" cluster-name=nats-cluster namespace=default pkg=cluster
time="2019-06-12T20:03:23Z" level=info msg="pod "default/nats-cluster-2" became ready" cluster-name=nats-cluster namespace=default pkg=cluster
time="2019-06-12T20:03:24Z" level=info msg="waiting for pod "default/nats-cluster-3" to become ready" cluster-name=nats-cluster namespace=default pkg=cluster
time="2019-06-12T20:03:26Z" level=info msg="pod "default/nats-cluster-3" became ready" cluster-name=nats-cluster namespace=default pkg=cluster
If someone wants to give me a quick rundown of your build system and whether or not I could integrate an ARM build I think this would be trivial.


When can we get pinned version of vsphere-automation-sdk-python library?

Since I am using this library as a requirement but we have pinned version dependency project, since it's a URL package dependency so can't use it in my project. Are you guys planning to upload to PyPI so we can use it as a specific version of this library?

Hi @vishalxebia
Here is a very long thread about pushing the package to PyPI #38
Until then if you want to pin to a certain version, could you try this https://github.com/vmware/vsphere-automation-sdk-python/issues/211#issuecomment-593996001 way?
Thanks,
Anusha Hegde

@anusha94  The thread didn't help much. I am not sure why you guys can't publish this SDK even people are requesting since 2 yrs almost.

@vishalxebia
Unfortunately, I don't have a definite answer to that right now. But we want to get there eventually.
In the meantime, try if this https://github.com/vmware/vsphere-automation-sdk-python/issues/211#issuecomment-593996001 works for you
You can pin to a release tag or commit.

No that doesn't work either. In my project, we need to really pin the version like vsphere-automation-sdk==1.23.0 something like this which can be installed easily by pip. But l have to find another way. Thanks @anusha94 .

Closing this issue as pinning to a version is not supported as of now. Uploading to PyPI issue is being tracked separately.


Please rename to graylog

greylog is the wrong product name, see:
https://www.graylog.org/

@runningman84  doh!


changes to make it easier for other server implementations and componentizing

I'm holding on the Wasm Componentizing PR until it is cleaned up.
I found the following changes make it easier for componentizing pieces of the Registry implementation as well as building another server implementation that imports from these crates.
It would be helpful to have them in the main repo as opposed to on a branch. Please let me know if some variation of this PR is acceptable to merge.

I agree, plus there's also a general loss of type-safety with making things take bytes instead of records, which increases the chance of errors being made.

Yes, I understand the concerns. Let me revise and separate in two PRs, one for the changes required to compile another server implementation and another one for componentizing the Registry logic. It will be easier to evaluate.


Add temporal fix for handling enums in qt_json_form

Description

Fixes #2634
Type of change

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

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[x] example: all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

This fix should get the things working for now @tlambert03


Rounding Behavior in Compact Notation

ICU overrides the default rounding strategy when compact notation is used.  ICU's compact rounding strategy is to round to the nearest integer, except to add a single digit after a decimal separator if to ensure there are always at least two significant digits shown:

1.2K
12K
123K
1.2M
12M
123M

Should this rounding strategy be defaulted when compact notation is used in ECMAScript, or should the default rounding strategy of 3 fraction digits be used, and leave it up to the user to override it?

I'd suggest, when no rounding options are passed in, ICU's rounding strategy should be used (and this should be reflected in resolvedOptions()); when rounding options are passed in, those should be respected. This would mirror what is done for currencies.

Okay.
An issue is that ICU's rounding strategy cannot be expressed as either fraction digit rounding or as significant digit rounding.  It needs a new construct.
See this ticket for more context:
https://unicode-org.atlassian.net/browse/ICU-20019
I have been working on this puzzle for a year and a half, and I still haven't come up with a clean API that covers all of the cases in the table on that bug, which I will reproduce here:

Description
In ICU?
3.1
3.01
0.03333
32.1
65432

Nearest integer
Y
3
3
0
32
65432

Nearest integer, keep two significant digits, no trailing zeros
Y
3.1
3
0.033
32
65432

Nearest integer, keep two significant digits, trailing zeros
N
3.1
3.0
0.033
32
65432

Nearest integer, keep two significant digits but not more than three, no trailing zeros
N
3.1
3
0.033
32
65400

Nearest integer, keep two significant digits but not more than three, trailing zeros
N
3.1
3.0
0.033
32
65400

Max three significant digits
Y
3.1
3.01
0.0333
32.1
65400

Max three significant digits, but no more than one fraction digit, no trailing zeros
N
3.1
3
0
32.1
65400

Max three significant digits, keep two significant digits, but no more than one fraction digit, trailing zeros
N
3.1
3.0
0.0
32.1
65400

Nearest integer, keep two significant digits but not more than three, no more than one fraction digit, no trailing zeros
N
3.1
3
0
32
65400

Nearest integer, keep two significant digits but not more than three, no more than one fraction digit, trailing zeros
N
3.1
3.0
0.0
32
65400

ICU compact notation currently uses the second row, but internally at Google we've had requests to move to some of the other options in this table.
Can you help brainstorm an API for Intl.NumberFormat that is capable of expressing a larger subset of these rounding strategies?

tc39/ecma402#239 is related.

@srl295 also suggested that we should include rounding increments (nickel rounding) since those are required by some currency implementations.

As you can see from ICU-20019, I haven't really come up with a super nice way of expressing these various strategies, and it also isn't obvious that we really need so much API surface to control this.
What do you think about supporting a function parameter that performs the rounding?  The function really needs only one parameter: the magnitude of the most significant digit.  For example, for the default ICU compact notation rounding strategy, the function would look like this:
function(magnitude) {
  if (magnitude < 1) {
    return magnitude - 1;
  } else {
    return 0;
  }
}

That function produces the second row in my table.  To support trailing zeros, the function could be,
function(magnitude) {
  if (magnitude < 1) {
    return {
      roundTo: magnitude - 1;
      trailingZerosTo: magnitude - 1;
    };
  } else {
    return 0;
  }
}

It may or may not be important to support different trailing zero behavior based on whether or not digits were "rounded off" the end.  For example:

Trailing Zeros?
3
3.01

Always
3.0
3.0

Never
3
3

If Rounded
3
3.0

If we wanted to support this, we could make the function return an object with three fields:
{
  roundTo: ___,
  trailingZerosAlwaysTo: ___,
  trailingZerosIfRoundedTo: ___
}

Another issue is that in some cases you might want different rounding behavior in different locales.  For example, suppose you want to render the number 987654321 in en-US.  You might say, "988,000,000".  However, in en-IN, since grouping is different, you might round differently, as in, "99,00,00,000".  I don't have any studies to say whether this is actually the case, but it seems like we should at least consider the fact that rounding could be locale-sensitive.

I'm glad you are putting in this detailed thought here. I am not sure if what the problem is if the default rounding strategy can't be expressed in terms of other primitives; resolvedOptions can be a separate representation. For nickel rounding, that seems very useful, but if an API hasn't been figured out, I think we can just expect it to be done at the application level for now, and provide support in a follow-on proposal.

I see, so for now make the spec implement the rounding strategy needed for compact notation, but don't expose it right now on the API level.  That makes sense.


Dynamically set RoutingKey={application} as an option

Question or Enhancement
I deployed ConfigServer as a PCF webapp

A developer commits a configuration change in the git repo
GitHub detects the change and triggers a hook sending a web request to ConfigServer/monitor
ConfigServer receives the request, git pull to get latest changes, and writes a message to SpringCloudBus (rabbitmq) to notify clients
Clients receive the notification and reloads values from ConfigServer

I am using one instance of ConfigServer to handle configuration changes for many applications (multitenant). The message written to SpringCloudBus has RoutingKey=”springCloudBus” and Payload contains “destinationService”:”{application}:**”. My problem is the message is received by clients from all applications and every app has to add code to filter by destinationService. I want the message to be received only by the {application} clients and it can be accomplished by setting RoutingKey={application}. Is there any way to do it today? Is it in the backlog?

Every spring bus client already has code to filter by destination service. Why do you need to add code?

My application is in dotnet core. Steeltoe does not provide the SpringCloudBus client

Ack. :+1:

@olegz or @sobychacko I think the question here is: is there a way to dynamically set the RoutingKey using spring cloud stream abstractions?

@spencergibb I think routingKeyExpression producer property is what you're looking for.
A SpEL expression to determine the routing key to use when publishing messages. For a fixed routing key, use a literal expression, such as routingKeyExpression='my.routingKey' in a properties file or routingKeyExpression: '''my.routingKey''' in a YAML file.
https://cloud.spring.io/spring-cloud-stream-binder-rabbit/spring-cloud-stream-binder-rabbit.html#_rabbit_producer_properties

Interesting. What object is available as context for the expression? OP wants something dynamic.

It's extended Rabbit producer properties: spring.cloud.stream.rabbit.bindings.<channelName>.producer.routing-key-expression=blah


Update build.sh to use specific version of repo

downgrade repo version for build
add release workflow for prebuilt image

tested on my own fork: https://github.com/dm4/wasmedge-seL4/actions

This PR fixed #9


__eq in metatable for C++ objects?

Our (PowerDNS) love for luawrapper continues to be grandiose! We've built most of dnsdist on it, and now also the Lua integration in the upcoming Recursor 4.x release, thanks!
To make things really shine, we'd like users to be able to compare two DNSName objects in Lua like this:
if(nameA == nameB) then .. stuff .. end
Where nameA are created with newDN() which returns a DNSName.
I've tried:
d_lw->registerFunction("__eq", &DNSName::operator==);
Which would of course be grand. When I explicitly call it (nameA:__eq(nameB)), it works too. But it is not in the metatable, so nameA==nameB does not call operator==. Unsure what it does call, btw! (perhaps it compares exact object identity?).
I see that I could do it with writeVariable to a specific named Lua-side object, but I don't think I could do this from my (C++ based) newDN() function, since my object need not even have a name yet.
Naively, it looks like registerFunction needs a variant for writing to metatables, but I could be wrong.
Help! :-)

Unfortunately I stopped using Lua a while ago, so I really don't remember much about all this.

Ok, thank you for all your great work! As PowerDNS we are pondering taking
over maintenance of a public fork of LuaWrapper, if we do so, would you
consider doing a commit to your README pointing people to our work?
Thanks again!
On Mon, Dec 21, 2015 at 12:39:27PM -0800, tomaka wrote:

Unfortunately I stopped using Lua a while ago, so I really don't remember much about all this.

Reply to this email directly or view it on GitHub:
https://github.com/tomaka/luawrapper/issues/31#issuecomment-166411148

Sure!

Hello @tomaka, I am working with @ahupowerdns on PowerDNS. Would you be open to handing over the whole repository (what Github calls 'Transfer ownership' in the repo settings 'Danger Zone') so the issues and open pulls also become our problem?


add basic pull request template to force

I was inspired by Cohesion to create a simple PR review template to remove some of the redundancy around including/linking jira tickets etc.
Let me know if there's anything that would be worth it to add? A header for screenshots maybe?

(And no worries on other sections; this will be flexible enough to account for all kinds of things in force)


Test: TestCtlV3Lock

--- FAIL: TestCtlV3Lock (16.15s)
	ctl_v3_test.go:138: test timed out for 7s

--- FAIL: TestCtlV3Lock (1.11s)
	ctl_v3_lock_test.go:91: expected different lock name, got l1="a/186d573fc1f99c04\r\n", l2="Error:  lost watcher waiting for delete\r\n"

Got another failure

I'm getting hanging/timeouts when trying to obtain a lock when using master. Using v3 works fine. The hang appears to be in waitForDelete(), so it may be related to this.

@justinruggles It would be great if you can help to debug this if you can reproduce. Also it would be useful to share how to reproduce it.

When I tried again using etcd server from master there was no problem, so I think this was just an issue with using release-3.0 etcd server with a master branch client. Sorry for the noise.

@mitake @AkihiroSuda I had hard time to reproduce this. Can you try to help?

@xiang90 ok, I'll try it out

I tried to reproduce the fails with more than 2000 iterations by namazu process inspector (that increases randomness of thread scheduling) but couldn't reproduce. How long did you need to produce the above fails? @xiang90 @gyuho

@mitake I cannot reproduce it myself. :( I suspect that it might be caused by CPU starvation. But I am not sure.

Didn't hit as well..

Still happening. https://semaphoreci.com/coreos/etcd/branches/master/builds/1034

I was able to reproduce ctl_v3_test.go:138: test timed out for 7s by putting a if rand.Intn(2) == 0 { time.Sleep(15 * time.Second) } right after waitKeys in Lock() (the 7s is misleading; the timeout is really 15s). This simulates a broken watch cancel path where the watch channel never closes out after a cancel.
I don't think locks are broken here because otherwise the integration lock tests would be exploding as well. The difference from those tests and e2e is the e2e test will cancel a blocked lock (and therefore the watch) when it sends a SIGINT to the process. I suspect this is fixed by the watch refactor.

@heyitsanthony Sounds reasonable. Can we:

fix the wrong timeout printing
panic when there is a timeout instead of fatal to print out the stack trace. if it happens again, it is easier for us to debug.

is OK
panic() probably won't do much for e2e debugging. It'll catch the stalled process Close but the interesting traces will be in separate processes. Some infrastructure around the process stuff that would SIGQUIT + collect the resulting stack traces would be much more useful.

@heyitsanthony right. let's close this for now.

Still seeing timeouts,
https://semaphoreci.com/coreos/etcd/branches/master/builds/1274

i have seen this for quite a while, and cannot reproduce it. so closing this for now.


Node.js Package Analyzer may run into ConcurrentModificationException

As can be seen in the conversation of #4089 there is a potential for the Node.js Package Analyzer to run into a ConcurrentModificationException under for now unknown circumstances.
Raising a new ticket as #4089 was about the NullPointer that emerged from it while creating the nestedCauseList for an ExceptionCollection when the ConcurrentModificationException (which has a null-valued message) is the first exception in the ExceptionCollection.
As the ConcurrentModificationException occurs in unknown circumstances we had to split fixing the NPE and further research into the ConcurrentModificationException.

i have the same issue using 6.5.3  (ci/cd via travis)..
i have 3 node applications being build in the same pipeline, 2 of them do pass , 1 recently start failing with the error above.
There is no real explanation for this, it only start happing in the last few weeks, out of the 5 tries, 4 failed
thanks

@huineng did your ci/cd stack recently update its Gradle version?

i have no idea, it looks like gradle version is 5.1.1
it also looks to me that this issue might be related
https://github.com/jeremylong/DependencyCheck/issues/4380
the only thing i can compare of is that from the 2 applications i run through the same pipeline (ow one never fails and the other nearly always, is that the latter is having some vulnerabilities and the former doesn't

Hello,
Just fall into the ConcurrentModificationException too after update maven plugin from 6.5.3 to 7.3.2 :
[WARNING] Analyzing `C:\Git\parent\html\default\package-lock.json` - however, the node_modules directory does not exist. Please run `npm install` prior to running dependency-check
Analyzing `C:\Git\aparent\html\default\package-lock.json` - however, the node_modules directory does not exist. Please run `npm install` prior to running dependency-check
dependency skipped: node module fsevents seems optional and not installed
dependency skipped: node module fsevents seems optional and not installed
dependency skipped: node module fsevents seems optional and not installed
An unexpected error occurred during analysis of 'C:\Git\parent\skin\mod\package-lock.json' (Node.js Package Analyzer): null

[ERROR]
java.util.ConcurrentModificationException
    at java.util.TreeMap$PrivateEntryIterator.nextEntry (TreeMap.java:1211)
    at java.util.TreeMap$KeyIterator.next (TreeMap.java:1265)
    at java.lang.Iterable.forEach (Iterable.java:74)
    at java.util.Collections$UnmodifiableCollection.forEach (Collections.java:1080)
    at org.owasp.dependencycheck.analyzer.DependencyMergingAnalyzer.mergeDependencies (DependencyMergingAnalyzer.java:156)
    at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies (NodePackageAnalyzer.java:420)
    at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies (NodePackageAnalyzer.java:365)
    at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.analyzeDependency (NodePackageAnalyzer.java:266)
    at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze (AbstractAnalyzer.java:131)
    at org.owasp.dependencycheck.AnalysisTask.call (AnalysisTask.java:88)
    at org.owasp.dependencycheck.AnalysisTask.call (AnalysisTask.java:37)
    at java.util.concurrent.FutureTask.run (FutureTask.java:266)
    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)

After some digging, reverting commit 1bded568d3fcf4bb7d445ba508e96a31a56d7342 seems to solve this issue.
However, I don't run all tests.
NOTE: I was a little bit disappointed since I do not want any NodeJS analysis on this project and have already set those properties :
        <nodeAnalyzerEnabled>false</nodeAnalyzerEnabled>
        <pnpmAuditAnalyzerEnabled>false</pnpmAuditAnalyzerEnabled>
        <retireJsAnalyzerEnabled>false</retireJsAnalyzerEnabled>
        <yarnAuditAnalyzerEnabled>false</yarnAuditAnalyzerEnabled>

So I can't understand why NodePackageAnalyzer is still launched.

I see this error with Version 7.4.1 too:
[INFO] Analysis Started [INFO] Finished Archive Analyzer (2 seconds) [INFO] Finished File Name Analyzer (0 seconds) [INFO] Finished Jar Analyzer (1 seconds) [WARNING] No lock file exists - this will result in false negatives; please run npm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] An unexpected error occurred during analysis of '/home/jenkins/agent/workspace/xxx/package.json' (Node.js Package Analyzer): null [ERROR]  java.util.ConcurrentModificationException     at java.util.TreeMap$PrivateEntryIterator.nextEntry (TreeMap.java:1208)     at java.util.TreeMap$KeyIterator.next (TreeMap.java:1262)     at java.lang.Iterable.forEach (Iterable.java:74)     at java.util.Collections$UnmodifiableCollection.forEach (Collections.java:1085)     at org.owasp.dependencycheck.analyzer.DependencyMergingAnalyzer.mergeDependencies (DependencyMergingAnalyzer.java:156)     at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.processDependencies (NodePackageAnalyzer.java:456)     at org.owasp.dependencycheck.analyzer.NodePackageAnalyzer.analyzeDependency (NodePackageAnalyzer.java:270)     at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.analyze (AbstractAnalyzer.java:131)     at org.owasp.dependencycheck.AnalysisTask.call (AnalysisTask.java:88)     at org.owasp.dependencycheck.AnalysisTask.call (AnalysisTask.java:37)     at java.util.concurrent.FutureTask.run (FutureTask.java:264)     at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1128)     at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:628)     at java.lang.Thread.run (Thread.java:834) [WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock[WARNING] No lock file exists - this will result in false negatives; please runnpm install --package-lock [INFO] Finished Node.js Package Analyzer (0 seconds) [INFO] Finished Dependency Merging Analyzer (0 seconds) [INFO] Finished Version Filter Analyzer (0 seconds) [INFO] Finished Hint Analyzer (0 seconds) [INFO] Created CPE Index (1 seconds) [INFO] Finished CPE Analyzer (3 seconds) [INFO] Finished False Positive Analyzer (0 seconds) [INFO] Finished NVD CVE Analyzer (0 seconds) [INFO] Finished RetireJS Analyzer (3 seconds) [INFO] Finished Sonatype OSS Index Analyzer (7 seconds) [INFO] Finished Vulnerability Suppression Analyzer (0 seconds) [INFO] Finished Dependency Bundling Analyzer (0 seconds) [INFO] Finished Unused Suppression Rule Analyzer (0 seconds) [INFO] Analysis Complete (18 seconds)


DontShow parameters should not appear in syntax diagrams

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
A parameter with the DontShow property is hidden from tab-completion, so as to hide parameters that aren't meant to be used directly by the caller.
Similarly, one what expect to be hidden from the syntax diagrams that are shown via -? (Get-Help) and arguably also via Get-Command -Syntax.
(Those interested in seeing all parameters can use commands such as (Get-Command ...).Parameters).
function Get-Foo { param([Parameter(DontShow)] $Bar) }

Get-Foo -?
'---'
Get-Command -Syntax Get-Foo

Loosely related:

#18472

Expected behavior
NAME
    Get-Foo

SYNTAX
    Get-Foo [<CommonParameters>]

ALIASES
    None

REMARKS
    None

---
Get-Foo [<CommonParameters>]

That is, the -Bar parameter should not show up.
Actual behavior
NAME
    Get-Foo

SYNTAX
    Get-Foo [[-bar] <Object>] [<CommonParameters>]

ALIASES
    None

REMARKS
    None

---
Get-Foo [[-bar] <Object>] [<CommonParameters>]

That is, the -Bar parameter still shows up.
Error details
No response
Environment data
PowerShell Core 7.3.0-rc.1

Visuals
No response

A few additional things

DontShow isn't documented in about_functions_advanced_parameters cc @sdwheeler / @michaeltlombardi
In my time of using PowerShell I've not seen a great usecase for it, though clearly others have
There are are only 10 instances of DontShow showing in the PowerShell codebase (inc comments)
There are many instances of it being used as per the following searches

https://github.com/search?q=[Parameter(DontShow)&type=code  -  [Parameter(DontShow) - 7.3k files
https://github.com/search?q=[Parameter(Mandatory+%3D+%24false%2C+DontShow+%3D+%24true)&type=code - [Parameter(Mandatory = $false, DontShow = $true) - 4 files

So this may be worthwhile to do but is likely a low priority for the team but have assigned this to what I think are the appropriate working groups

A few additional things

In my time of using PowerShell I've not seen a great usecase for it, though clearly others have

I have found 2 uses (1)  parameters which are no longer used but to prevent breaking scripts that use them the parameter remains with don't show  (2) parameters which are passed when a function is called by another function, or when the function calls itself recursively (e.g. how far should I indent printed output) but shouldn't be passed when a user calls the function.
I think for a developer writing something I would want them to the parameter is there, for a user calling it from the command line I'd prefer to hide it - so I can see both sides and don't think either is a clear winner. I wouldn't bother changing it (and if had been as Mike suggests from day 1 I would bother changing the other way).

Good summary of the use cases, @jhoneill.
A prominent example of (1)  would  be Export-Csv's -NoTypeInformation; there's also Format-Hex's -Raw.

I think for a developer writing something I would want them to the parameter is there

As noted, (Get-Command ...).Parameters would always give you that.
Given the two audiences - users of a command vs. its developers - to me there's no question that consistently implementing the feature for the benefit of the command's users should be the guiding principle here.
Otherwise, you're asking for confusion.
An example of where the syntax diagram already does hide internal-use-only parameter is the CLI: pwsh -? - commendably - does not show you parameters such as -servermode, namedpipeservermode, and removeworkingdirectorytrailingcharacter

@theJasonHelmick
This issue makes the case for one possible design rationale:

If a parameter is to be hidden from tab completion, the implication is that isn't relevant to end users.
Given that syntax diagrams, like tab completion, are meant for end users, it makes sense to hide such parameters there too.
(And if you don't do both, users can get confused: why is parameter x - clearly shown in the syntax diagram - not tab-completed?)

I did miss an aspect, however: the docs state, "This is primarily to be used in functions that are implementing the logic for dynamic keywords."
Yet, I wonder if in practice the property is also used as described in the initial post.

What is the design rationale for the current behavior?
Saying just, "This is by design" in the abstract doesn't help the community understand why things were designed this way, which, unfortunately, seems to be a recurring theme.


Cherry-pick #288

feat(snapshot/commitment): use commitment when creating a snapshot
Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge


Not working in static TableViewController Cell

It freezes my TableViewController when i subclass the TextField to WSTagsField in the Storyboard,
and i get the below error after the app stops

Discarding message for event 1 because of too many unprocessed messages
2017-03-13 16:56:26.713355 LocationApp[46653:475740] [Client] Discarding message for event 27 because of too many unprocessed messages
(lldb)

i try subclassing in my TableViewController class only, like this
@IBOutlet weak var tagsTextField: WSTagsField!
But its not putting the text in tags, treating it like normal TextField

@moderateepheezy Could you upload a functional project where I can test and debug it? Thanks

https://github.com/moderateepheezy/testproject
you can check the project in the above link, the issue is on the EventsTab, when i click on the Plus button nav bar, the app hangs, the plus button is suppose to present to you the CreateEventVC(TableViewController) Class where i have one of the TableViewCell item as WSTagField.
you'll see the screenshot below

the same problem to me .

Same here. Its weird because there isn't a crash, the app is just non-functional aka frozen.

I'm trying to solve this but I can't understand what's wrong. The table view blocks completely?

Correct the app stays in a frozen state. It doesn't accept any user interactions. Check to make sure you haven't blocked the main thread.

On Apr 28, 2017, at 2:42 PM, Ricardo Pereira<EMAIL_ADDRESS>wrote:
I'm trying to solve this but I can't understand what's wrong. The table view blocks completely?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

repositionViews() cost loop

Can anyone confirm that this only happen when the WSTagsField has constraints in the table view?

@moderateepheezy Please try pod 'whitesmith/WSTagsField', :git => 'https://github.com/whitesmith/WSTagsField.git', :branch => 'fix-37' and see if it works.

Came here with the same UI-locking issue, but the 'fix-37' branch addressed things for me.
One note:  When using in conjunction with auto-resizing cells, sometimes my typing will wrap to the next line, and the height won't adjust (see below).

@technicallyerik Ok, thanks. I'll try to reproduce that.

@technicallyerik I can't reproduce your problem :/ Can you build an example app please?

I'm closing this because version 2.1.2 has been released. Any other problems should result a new issue. Thanks.


data_dir seems to wrongly be local.

This is a bug coming from the just tool:
https://github.com/casey/just/issues/2212
It seems that data_dir() returns some local folder such as /home/mini-me/.local/share and not some system wide folder such as /usr/local/share.
Maybe there is something that I don't quite get, but this seems to more or less be intended behaviour, when looking at the codebase of dirs-rs.

Correct.
There are some platforms (like Windows) that distinguish(ed) between data that's stored on the machine and data that is associated with a user account and synced to the machine when the user logs in.
data_dir vs. data_local_dir allows you to select the appropriate one, even if it may not make a difference on the operating system you are currently running on.


After updating luci-base, only one wireless can be started when the wireless country or region is "drive default"!

Not a LuCI bug.


Intersection of Two Arrays II

@bhumikatewary Please assign me this too.

@bhumikatewary  Can you please assign this task to me.


Import YOLOv5

From this repository: https://github.com/ultralytics/yolov5
Figure out all of the components that we need to run the detections. Ideally, the less the better. For example, it may store the models but we can download those later or create new ones when we do our own training (models, weights, .pb files, etc.)
Store all of the imported code in it's own package (e.g. folder with an init.py file)

yolov5 is now a package in the repo. Hence was able to create a file called detect_sample.py, which is a modified version of the detect.py from the yolov5 repo. There arent too many changes, but all of the changes are commented.
In order to run detect_sample.py you must

detect_sample.py expects images in a folder ~/inference/images . A sample inference folder is in our yolov5 package (~/yolov5/inference/images). The ~/yolov5/inference folder should be copy-pasted to our home directory.
detect_samply.py expects a file called yolov5s.pt in the home directory. However if yolov5s.pt is not in the home directory, the script will download it automatically.
(BTW the 's' stands for small. We are using the small version of yolo, there is a medium, large and extra large option).

For those who don't have a lot of experience in the command line, to tun it go to the BNA-traffic folder and run 'python  detect_sample.py'.