CORS issue in creating origin headers

Environment
Node: v18.15.0
npm: v9.5.0
Nuxt: v3.2.3 + nuxt-security v0.11.0
Reproduction
https://github.com/maxdzin/nuxt-cors-issue
Describe the bug
When working on API, I used nuxt-security and I noticed that the Access-Control-Allow-Origin header is not set correctly.
So, there could be a bug related to the just-merged @nozomuikuta/h3-cors into H3.
There is a discussion about the CORS problems in this nuxt-security issue and it is related to h3-cors things.
In short, there's a response 'Access-Control-Allow-Origin' header is not set correctly, while the options contain specific origin values.
So, there are these problems:

If the H3CorsOptions.origin value is set as an array of strings or an array of RegExp, the access-control-allow-origin header is not set in this case. In order to set that response header correctly, I believe that createOriginHeaders method must return with access-control-allow-origin value set in the last return block here:

export function createOriginHeaders(
  event: H3Event,
  options: H3CorsOptions
): H3AccessControlAllowOriginHeader {
  const { origin: originOption } = options;
  const origin = getRequestHeader(event, "origin");

  if (!origin || !originOption || originOption === "*") {
    return { "access-control-allow-origin": "*" };
  }

  if (typeof originOption === "string") {
    return { "access-control-allow-origin": originOption, vary: "origin" };
  }

  return isCorsOriginAllowed(origin, options)
    ? { "access-control-allow-origin": origin, vary: "origin" }
    : {};
}

So, if the isCorsOriginAllowed is false, it returns an empty object. But, it must be set by originOption value instead.

And there's confusion with H3CorsOptions type:

export interface H3CorsOptions {
  origin?: "*" | "null" | (string | RegExp)[] | ((origin: string) => boolean);
  ...

The string type is missing there.
Additional context
No response
Logs
No response

@maxdzin
Thank you for reporting the issue.

If the H3CorsOptions.origin value is set as an array of strings or an array of RegExp, the access-control-allow-origin header is not set in this case. In order to set that response header correctly, I believe that createOriginHeaders method must return with access-control-allow-origin value set in the last return block here:

Yes, it seems to be a bug, and CORS handler should return some specific access-control-allow-origin when the request origin is not allowed. Otherwise, as far as I see your reproduction, the app behaves like being set access-control-allow-origin header as * (allow CORS from any origin).
return isCorsOriginAllowed(origin, options)
  ? { "access-control-allow-origin": origin, vary: "origin" }
  : {};

Then, although this is a design mistake that I inherited from Express CORS middleware, we have to provide a way to set the specific access-control-allow-origin to fix this issue, especially when origin option is a RegExp, an array of string and/or RegExp, or a function that currently returns boolean.

And there's confusion with H3CorsOptions type:

This is my design as the original author of the feature. I wanted to treat "*" and "null" as special cases and wanted developers to be aware of them apart from specific origins, and also wanted to handle the former apart from the latter in the code.
But, thinking in again, it would be more convenient if developers can specify the only one allowed origin as an unwrapped string or RegExp.

To avoid breaking changes, how about the following hot-fix?
// As-Is
export interface H3CorsOptions {
  origin?:
    | "*"
    | "null"
    | (string | RegExp)[]
    | ((origin: string) => boolean)
}

// To-Be
export interface H3CorsOptions {
  origin?:
    | "*"
    | "null"
    | string // (1)
    | [RegExp, string]  // (2)
    | (string | RegExp | [RegExp, string])[]  // (3)
    | ((origin: string) => boolean | string)  // (4)
}

Single string type is newly added for convenience
Single RegExp is newly supported, but with origin string when request origin doesn't match
[RegExp, string] is newly supported as (2). Add deprecate/security warning for unwrapped RegExp usage.
string return type is newly added to set access-control-allow-origin in case request origin is not allowed. Add deprecate/security warning when the function returns false.

@pi0
Sorry to bother you, but do you have any thoughts on this issue? My idea above is based on my guess that you don't want to introduce breaking changes and bump up to new major version. But, if possible, there would be more sophisticated API.
@maxdzin
Any feedback from you is also welcome.

@NozomuIkuta great! That should work.
I'm thinking about one more thing in the createOriginHeaders method... If originOption is set as an array of strings or an array of RegExps, that must set access-control-allow-origin header by the request origin that matches some of originOption, that's clear, but if it is not matched, then it shouldn't set the header. Maybe that's the correct behavior.
For me, it was not clear how to set the originOption if I require an exact value to be matched (since as of type, it accepts string[], but not string). But I think that if a string will be added as one of the possible types, it should solve the issue.
 At least for string[], RegExp, and RegExp[] - it is not so obvious how it is about to be considered and used to check/set the access-control-allow-origin header in this case. So, adding some short explanations of those types would help.


Death bans still occuring after module disabled

Module was working correctly, was enabled and worked, then when disabled seemed to still be running

Invalid, was plugin conflict


Revisit default for editor.suggestSelection setting

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:1.51.1
OS Version: Windows 10 Pro

To support intellisense in our VSCode extension, I have implemented vscode.CompletionItemProvider interface and call to provideCompletionItems() returns the list of vscode.CompletionList.
When completion item list, gets displayed then scroll bar is not positioned at the first item in the list.
It exists somewhere in the middle of list. To go to the first item I need to manually move scroll bar to the top which is not a good user experience.
As per reply from forum,  this can be controlled by editor.suggestSelection setting.
But Most users of Our VSCode extension, won't be aware of editor.suggestSelection setting
so Is there any other way to keep scroll bar position at first item?
Basically can we set some variable or pass some parameter to VSCode API, to keep scroll bar position at first item?
I have tried setting CompletionItem. isIncomplete to true/false but no luck.
Keeping scroll bar at first position,  is one of the most important requirement for our extension.
Please let me know what I need to do so that scroll bar is always positioned at the first item in the list?

This is controlled via the following user setting: editor.suggestSelection. The default is to remember the last selected suggestion (based on context) but I assume your desire is "editor.suggestSelection": "first".

Let's try this during this dev month (for VS Code Insiders) and see what feedback comes in

The default is first since a while and I no complaints have been heard. Let's ship this to stable and wait for feedback


Enforce better globbing in bar2vtk

Instead of just globbing velbar*.{timestep number}*, have it be more strict by only allowing the * to apply for file extensions.
Example: For time step number = 200:
Match:

velbar.200
velbar.200.1

Fail:

velbar.2001
velbar.20000

The following regex string works for the above cases: ^velbar\.200(?!\d).*$
Effectively, after 200, if the next character is a digit, the matching fails. Otherwise, it succeeds with any other characters.
In [5]: os.listdir('.')
Out[5]: ['velbar.200', 'velbar.200.1', 'velbar.2000']

In [6]: for filename in filter(re.compile(r'^velbar\.200(?!\d).*$').match, os.listdir('.')):
   ...:     print(filename)
   ...:
velbar.200
velbar.200.1


support for tls connections on 5223

instead of starttls on 5222 (and fail hard in the case of 5222 and no starttls)

no need anymore... (seems like nobody uses this anyways)


Update Telemetry Page

https://github.com/kinnay/NintendoClients/wiki/Telemetry-Servers lists only receive for data telemetry - it now seems https://fw-api.lp1.nso.nintendo.net/v1/events is also used when enabled via sprofile, and events such as the following are sent:
{"type_name":"online_play","version":1,"occurred_at":1645484612,"application_id":"01006f8002326000"}

with {"message":"OK"} as a response.
Also, "telemetry" is misspelt a few times ^^

CORRECTION: This API isn't (just?) for Telemetry - it's for Nintendo Switch Online's webapp rewards; events such as uploading save data to the cloud, online play, and playing NES games all trigger events that give you point rewards.
Application event example (NES app, playing a game):
{"type_name":"application_event","version":1,"occurred_at":1646124653,"application_id":"0100d870045b6000","event_data":"{\"title_id\":\"CLV-P-NAACE-sp1\"}"}

And a savedata upload:
{"type_name":"savedata_upload","version":1,"occurred_at":1646124902,"application_id":"0100d870045b6000"}


python27Packages.bitarray: 1.2.2 -> 1.3.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python2.7-bitarray/versions.
meta.description for python27Packages.bitarray is: "Efficient arrays of booleans"
meta.homepage for python27Packages.bitarray is: "https://github.com/ilanschnell/bitarray"
meta.changelog for python27Packages.bitarray is: "https://github.com/ilanschnell/bitarray/blob/master/CHANGE_LOG"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.3.0 with grep in /nix/store/rf5js84xh7j6127aqm65dn5rciarnvbr-python2.7-bitarray-1.3.0

directory tree listing: https://gist.github.com/c48945a6708e0c2385bfdf2bac646f0d

du listing: https://gist.github.com/e2410b66b2ce3268c691b1caa3385b9c

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

6 package rebuild(s)

6 x86_64-linux rebuild(s)
6 i686-linux rebuild(s)
6 x86_64-darwin rebuild(s)
6 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
glasgow
python27Packages.bitarray
python37Packages.bitarray
python37Packages.glasgow
python38Packages.bitarray
python38Packages.glasgow

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/rf5js84xh7j6127aqm65dn5rciarnvbr-python2.7-bitarray-1.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python27Packages.bitarray https://github.com/r-ryantm/nixpkgs/archive/1e338c42bfbb707c67df281fb33ac65cfa9dfbf3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/rf5js84xh7j6127aqm65dn5rciarnvbr-python2.7-bitarray-1.3.0
ls -la /nix/store/rf5js84xh7j6127aqm65dn5rciarnvbr-python2.7-bitarray-1.3.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

2 packages failed to build:
- glasgow (python38Packages.glasgow)
- python37Packages.glasgow

3 packages built:
- python27Packages.bitarray
- python37Packages.bitarray
- python38Packages.bitarray

Maintainer pings
cc @bhipple for testing.

Thanks @drewrisinger !

Result of nixpkgs-review pr 92840 1

5 packages built:
- glasgow (python38Packages.glasgow)
- python27Packages.bitarray
- python37Packages.bitarray
- python37Packages.glasgow
- python38Packages.bitarray


Nunit support

Hi
Great extension, really useful. What would be involved in adding support for nunit? I often use the "Create unit tests" feature in Studio with the nunit adapter installed but the handling of Moq and DI in this extension is better so would happily swap if nunit was supported. I suspect this would increase potential userbase for this extension considerably.
Thanks

Thanks! Added NUnit support in 1.4.1. It should automatically detect which projects are using it. Feel free to leave a review if this helps you out: https://visualstudiogallery.msdn.microsoft.com/f3f3b2a7-cefe-4ffe-add1-9740ae117252

Awesome, thanks!


Round 2 feedback

@chrisvfritz
In the repo, bootstrap_alert_spec.rb doesn't have any :pending

@chrisvfritz couldn't figure out the colors for my command line

@chrisvfritz much easier this time around. I started with the bootstrap alert method, because it was already active in rspec, but the image tag is definitely the easiest to start with. If you are going to have one that's on by default the first time you run rspec, I'd do that one instead of the bootstrap alerts. Talk to me if you don't know what I'm talking about - I'm probably using the wrong vocabulary.


qlcplus: init at 4.10.4

Motivation for this change
Bringing DMX lighting software to NixOS!
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

hi, I am getting a compilation error: mkdir: cannot create directory '//etc/udev': Permission denied.

@sleexyz ping

I'm closing as abandoned. If @sleexyz or anyone wants to pick it back up it can always be reopened.


Don't render all releases on version specific JSON pages

Reverts the streaming JSON, it didn't work and complicates the code/tests
Version specific legacy JSON pages only have information for that version now.
Non version specific legacy JSON pages still have information on all releases.

This is a breaking change, but it's a needed one if we're going to keep PyPI stable.

With this change, I think the poetry lock process is now failing: https://github.com/python-poetry/poetry/issues/5970
I checked the metrics in PyPI Public Dashboard, and it makes sense that this change had to be merged quickly.
However, I still think that there is a way to revert the previous PR or rollback to the previous version rather than making a breaking change in the API.
It would be nice to have a way to notify the package manager maintainer if there is a case where API breaking changes are made in the future.

If the change was to be reverted, on Poetry side we would probably only need to bring back the version requested in /pypi/<project_name>/<version>/json endpoint in releases key, because that's exactly what we did before this change.
So for instance, if we query /pypi/requests/2.28.1/json, we would only need 2.28.1 in releases, not the other versions.
I understand that a revert (even a partial one as suggested that would add back only the requested version) is cumbersome and a pretty big request (especially since this PR is about PyPI stability, which is obviously important), but just to bring awareness about the impact, basically all released versions of Poetry (as of writing this) are affected, preventing the retrieval of hashes when locking dependencies, since they rely on releases key, so the impact is quite high for Poetry end users.
We are in the process of releasing an express new Poetry 1.1 version that relies on urls key instead of releases, so people will have a workaround, but people with older versions will have no other choice than updating, which can be quite disruptive.

I went back and forth on whether to leave the releases key there with just the current version in it or not.
I ultimately decided not to for one major, and one minor reason.
The minor reason is just that the data already exists on the response in the urls key, so it was duplicative.
The major reason though is that I think breaking loudly is better than breaking quietly, and while poetry's specific use here wouldn't be affected, it's just as easy to imagine someone iterating over the list of releases rather than looking for a specific release. If they did that, then they would get silently wrong data instead of breaking loudly.

The major reason though is that I think breaking loudly is better than breaking quietly, and while poetry's specific use here wouldn't be affected, it's just as easy to imagine someone iterating over the list of releases rather than looking for a specific release. If they did that, then they would get silently wrong data instead of breaking loudly.

This is perfectly understandable. I've only recently started contributing more and more to Poetry (so disclaimer, not a core contributor), so I lack a bit of context to know if it should/could have used urls from the beginning, but on a broader level, it's a bit frightening that Poetry relies on an API that could break (even if the reasons to break things are perfectly valid, so I'm mostly reasoning from a Poetry end user and maintainer point of view).
Was there a way to know beforehand about the removal of releases in the API? Maybe in a mailing list for instance?
I've noticed https://github.com/pypi/warehouse/issues/11559 following another issue that recently affected Poetry, and I agree that it would be awesome to document a bit more what to expect from the different APIs in terms of stability. Having deprecation notices, even if short ones, would at least make it possible to update the API requests on Poetry side, which would be a better experience for Poetry users since it would give them time to upgrade rather than being forced to.

Hi there - thanks for the context on this change. I'm curious if/when the releases key will be removed on the non-versioned json API endpoint as well. I noticed that the documentation was updated to include a note that it may be deprecated in the future; any timeline you are able to share with me would be helpful!

As far as we can tell, there's not currently any major problems stemming from that specific key since it's one extra response to cache (versus an unbounded number of extra responses to cache when it was on the versioned URL). Given that, there's currently not any specific plan to remove the releases key from the non-versioned URL, so the answer to that is basically "nobody knows, it might never be removed, or it might be in the future if it starts to cause problems because it makes the responses huge".
That warning was put there mostly to guide people to attempt to find an alternative solution if one exists to relying on that key OR if an alternative solution doesn't exist, to follow up on the issue tracker or on discuss.python.org with their use cases that aren't handled currently by the other keys in the JSON API or, even better, by the simple repository API so we can figure out if there's a better, less problematic, answer we can add to support them.


Unable to scroll using  inside .

I have a lengthy list of radio buttons with yes/no options. But, the problem here is I am unable to scroll down to the list , so, Is there any way that I can insert ScrollView at the begin and end of the list of radio buttons
ScrollView
Radio/
Radio /
.
.
.
.
Radio /
/ScrollView

I wrapped complete radio list rendering component inside ScrollView component of react-native, but it doesn't scrolls.

Solved: Able to scroll inside the accordion after making the height of the wrapper  smaller the height of ScrollView.
<View style={{flex:1, height:height *0.6  }}>
     <Text>{'HEADING 1'}</Text>
    <ScrollView style={{ height:height *0.7 }}>
    <Accordion
    style={{borderColor:'gray', borderWidth:2}}
      sections={this.SECTION}
      renderHeader={this.renderHeader}
      renderContent={this.renderContent}
    />
    </ScrollView>

  </View>

Solved: Able to scroll inside the accordion after making the height of the wrapper View smaller than the height of ScrollView.
`
<`View style={{flex:1, height:height *0.6 }}>
     <Text>{'HEADING 1'}</Text>
    <ScrollView style={{ height:height *0.7 }}>
    <Accordion
    style={{borderColor:'gray', borderWidth:2}}
      sections={this.SECTION}
      renderHeader={this.renderHeader}
      renderContent={this.renderContent}
    />
    </ScrollView>

  </View>

`

What is the height variable here?

VirtualizedLists should never be nested inside plain ScrollViews with the same orientation because it can break windowing and other functionality - use another VirtualizedList-backed container instead. I get this error when I apply your method.


Slow #0 when using map to tokenize.

Hi, datasets is really amazing! I am following run_mlm_no_trainer.py to pre-train BERT, and it uses tokenized_datasets = raw_datasets.map(             tokenize_function,             batched=True,             num_proc=args.preprocessing_num_workers,             remove_columns=column_names,             load_from_cache_file=not args.overwrite_cache,         ) to tokenize by multiprocessing. However, I have found that when num_proc>1，the process #0 is much slower than others.
It looks like this:

It takes more than 12 hours for #0, while others just about half an hour. Could anyone tell me it is normal or not, and is there any methods to speed up it?

Hi, I have found the reason of it. Before using the map function to tokenize the data, I concatenate the wikipedia and bookcorpus first, like this:
        dataset1 = load_dataset(args.dataset_name1, args.dataset_config_name1, split="train")
        dataset1 = dataset1.remove_columns('title')
        if args.dataset_name2 is not None:
            dataset2 = load_dataset(args.dataset_name2, args.dataset_config_name2,split="train")
            assert dataset1.features.type == dataset2.features.type, str(dataset1.features.type)+';'+str(dataset2.features.type)
           datasets12 = concatenate_datasets([dataset1, dataset2], split='train')

When I just use one datasets, e.g. wikipedia, the problem seems no longer exist:

Bookcorpus has more row numbers than Wikipedia, however, it takes much more time to process each batch of wiki than that of bookcorpus. When we first concatenate two datasets and then use map to process the concatenated datasets,  e.g. num_proc=5, process 0 has to process all of the wikipedia data, causing the problem that #0 takes a longer time to finish the job.
The problem is caused by the different characteristic of different datasets. One solution might be using map first to process two datasets seperately, then concatenate the tokenized and processed datasets before input to the Dataloader.

That makes sense ! You can indeed use map on both datasets separately and then concatenate.
Another option is to concatenate, then shuffle, and then map.


update urls in package.json

Codecov Report
Patch and project coverage have no change.

Comparison is base (9d0b5a7) 97.27% compared to head (bb7ec23) 97.27%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   97.27%   97.27%
=======================================
  Files           3        3
  Lines         623      623
  Branches       20       20
=======================================
  Hits          606      606
  Misses         17       17

Flag
Coverage Δ

unittests
97.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Need documentation for textual device config

There's no documentation about textual device config. We need to document it.
https://docs.rs/furiosa-device/0.1.1/furiosa_device/struct.DeviceConfig.html#

This issue is resolved at #19 .


As a data developer, I want to add the New York State draft list of DACs to the comparison tool, so I can understand how they compare against other indices.

Description
New York just released its draft definition of DACs with a 120-day comment period, including:
Documentation: https://climate.ny.gov/DAC-Criteria
Map: https://climate.ny.gov/Our-Climate-Act/Disadvantaged-Communities-Criteria/Disadvantaged-Communities-Map
Data download: https://data.ny.gov/Energy-Environment/Draft-Disadvantaged-Communities-DAC-2021/xj7e-q8ja
Add this to the comparison tool to generate comparison results.

This is ready to go but currently is in emma-nechamkin/1149-pairwise-comparison-tool.


update components resource request

https://github.com/open-cluster-management/backlog/issues/14982
/hold and will be merge to 2.3 z stream
Signed-off-by: Song Song Li<EMAIL_ADDRESS>

need to update e2e test and doc

depends on this PR: https://github.com/open-cluster-management/observability-e2e-test/pull/229

doc PR: https://github.com/open-cluster-management/rhacm-docs/pull/2542

/lgtm

/unhold

/test test-e2e

/test test-e2e


For recommendations using implicit data and user/item feature, adding new observation data do not reflect in the recommendations.

I am using implicit data, user and item feature to create a recommendation system model.
Implicit data like,
+--------------+-----------------+
|     User     |       Item      |
+--------------+-----------------+
|    Aarav     | Item1  |
|    Ayaan    | Item1  |
|    Nakul     | Item2 |
+--------------+-----------------+
model = tc.recommender.create(interaction_data, user_data=user_details, item_data=loan_details)
I have created some new interactions, new_interaction.
Made recommendations,

model.recommend(["User_id"])
model.recommend(["User_id"], new_observation_data=new_interaction)

Both recommendations are the same with the same score. I have tried different combinations of user and item to create new_interaction. But still the recommendations are the same.

I have the same issue, though not with implicit data, but with the RankingFactorizationRecommender. I create models like so:
model = tc.ranking_factorization_recommender.create(
            observation_data=tc.SFrame({'id': [..], 'user_name': [...], 'rating': [...]},
            user_id='user_name',
            item_id='id',
            target='rating',
)

and can make recommendations just fine. But if I want to add new observation data
new_observations = tc.SFrame({'id': [..], 'user_name': ['user', ...], 'rating': [...]}
model.recommend(['user'], new_observation_data=new_observations) # or
model.recommend_from_interactions(new_observations)

the only change is that those items with ID in new_observations will be filtered out, but otherwise the recommendations are exactly the same.

https://github.com/apple/turicreate/blob/master/userguide/recommender/using-trained-models.md#incorporating-new-observation-data
"Currently, the ItemSimilarityModel makes the best use of this information."

"best use" or "only one to use"?

For all recommender models other than ItemSimilarityModel, new observations are only used to filter out those items from the items that are returned. In order to use these new observations to make better predictions, you need to retrain your model.
ItemSimilarityModel does use new observations when picking predictions.


请问下主机的DNS如何填写？

我想让服务端来解析DNS，而不是主机来解析DNS。主机可以填常规的公共DNS可以连接。但是如果填了服务端的网关就提示出错。主机是Switch

pcap2socks does not own a local DNS server. You should designate a existed public DNS server in your console.

pcap2socks does not own a local DNS server. You should designate a existed public DNS server in your console.

请问如何操作呢，文档没看到有关于DNS的用法

You can just use any public DNS in your console.


Lesly branch

Commit Message Guidelines
Header
Blank Line
Body
Blank Line
Footer

The header should look like:
<type>(<scope>): <subject>

The body should have any necessary detailed info about the commit:
An example, references as to where this idea came from, etc.

The footer should have all the issues tagged:
Fixes #123, Fixes #456

So a commit should look like:
feat(users): Add new Yahoo authentication

Yahoo authentication idea proposed by @codydaig
Example implementation in file.js

Fixes #82

Types:

feat - Features, Enhancements, and overall Improvements
fix - Fixes, Bugs, HotFixs, etc...
doc - Changes to the Documentation and doesn't actually touch any code.

Scope:

The scope should be where the change took place.
Examples: users, core, config, articles

Subject:

The subject line should be clear and concise as to what is being accomplished in the commit.

General Rules:

No Line in the Commit message can be longer than 80 characters.

Reference: Angular Conventions

Hey @leslyvj1987, please make your own repository to learn pull requesting. Now you're just causing extra work for volunteers here. Thanks.


ContextCache.GetContextFor is not thread safe

Despite using a ConcurrentDictionary under the hood the ContextCache implementation of GetContextFor isn't thread safe, it uses tryGetValue and then if that fails calls the constructor, which calls the context add method to add itself to the cache. There is a TOCTU problem there where another thread could add a different instance bound to the same underlying handle violating the reference equality guarantees.
ContextCache internally hides the ConcurentDictionary via an IDictionary interface, it shouldn't do that.  It should leverage the members of the Concurrent dictionary like GetOrAdd() etc... to ensure proper thread safety and ref equality guarantees.

Additionally the Context Constructor needs to split to a two stage construction where the context is constructed with a handle and the second stage does the rest and isn't called unless the context was actually added, if it wasn't added, then the context is a new wrapper around an instance already in the cache and should be detached from the the underlying handle so it doesn't destroy the context when the GC kicks in.


Executing command timeout

Hi
We are using jPowerShell to stop windows service, and waiting for the status to switch with following command (“foreach($service in (Get-Service -Computer ipAdress -Name serviceName)) {$service.stop(); $service.WaitForStatus("Stopped",'00:00:30')}”)
Sometimes it takes longer than 10 seconds for the service to stop and then we get and timeout in jPowerShell before the command returns.
Is it possible to get a change where we can set the MAX_WAIT? Maybe as a parameter to openSession?
Thanks

Hello,
Yes, I have to take a look to see how to override the MAX_WAIT... I will keep you updated.
Thanks

Hi again,
Could you test this?
https://oss.sonatype.org/content/repositories/snapshots/com/profesorfalken/jPowerShell/1.5-SNAPSHOT/jPowerShell-1.5-20160531.184520-1.jar
I have added a mechanism to configure jPowershell.

You can configure it by project creating a jpowershell.properties file in the classpath of your project and settings the variables you want to override.

Or you can configure it by call using a map that can be chained to powershell call.

For example, in your case:
Map<String, String> myConfig = new HashMap<>();
myConfig.put("maxWait", "30000");
PowerShell powerShell = PowerShell.openSession();

PowerShellResponse response = powerShell.configure(myConfig).executeCommand("Get-Process");

Or directly:
PowerShellResponse response = PowerShell.openSession().configure(myConfig).executeCommand("Get-Process");
The three variables that can be configured are:
maxThreads: the maximum number of thread to use in pool. 3 is an optimal and default value
waitPause: the pause in ms between each loop pooling for a response. Default value is 10
maxWait: the maximum wait in ms for the command to execute. Default value is 10000
Tell me if it works

Hi
Thanks for your fast response.
I have tried the solution with the property file but did not succeed, I can’t find any references to the PowerShellConfig class.
The configure method on PowerShell works but there is a bug in the PowerShellCommandProcessor.startReading where Thread.sleep are using maxWait instead of waitPause and this make it very difficult to test.
Thanks

Ups! I had to generate the jar quickly and I had no time to write tests (and, moreover, I did not have access to a Windows machine).
I will generate today a new version correctly tested.

Hello again,
It should be all right now for both the config file and the bug in the variable maxWait
https://oss.sonatype.org/content/repositories/snapshots/com/profesorfalken/jPowerShell/1.5-SNAPSHOT/jPowerShell-1.5-20160601.204944-2.jar

Hi again
Now it’s working as expected!
Thank you very much for your work

Great!
I have created a 1.5 version that includes this feature. It is already published in Maven Central.
I close this issue.
Thank you


The actual exe file isn't in the git?...

Hi,
I had to google up JNSoundboard, and download it from a softpedia page.
Granted, I'm kind of a dumbass, so maybe I'm just not accessing the right files to execute it.
Lemme know if my concerns are legit, or just from stupidity. I can take objectivity, it's all good.

You can get it from the Releases page: https://github.com/Jitnaught/JNSoundboard/releases

Oh, cool.
Maybe a link to that on the front side of the readme with:
You can download new versions from the Releases page: https://github.com/Jitnaught/JNSoundboard/releases
Just for those not used to github? Thanks for the response.

Added the link in a435ddb443fce30aee6cb5ace68becddbaf8644f :)


Correct Portal 2 Live Timer parsing

Correct Map Names & order
Handle merging of consecutive maps with the same name

Maybe we need something like cargo bomb / crater to parse all splits on splits i/o whenever we make changes to the parsers, so we know we don't break something.

Like for example you changed the order, but I'm pretty sure this used to be the correct order. But maybe not. Who knows.

It might have been at one point, i'm not sure I don't really follow Portal. I just know this is the order that I saw on https://wiki.sourceruns.org/wiki/Portal_2_Maps and in the PLT source

Also it looks like Splitter Bomb couldn't even find a single successfully uploaded Portal 2 Live Timer splits file on splits i/o. So I guess there's no proof it ever worked with any actual splits file.


chore: fix shellcheck sh2140 failures

Tested here: https://github.com/splunk/splunk-add-on-for-google-workspace/pull/459

Will be done in #158


a11y prototype - nav with toast notification

For one of the next GMS sessions, we'd like to test the roles "alert" and "status" in the context of a toast notification.
For this review, we'll need the following updates:

update the navigation as list prototype so that clicking specific menu items trigger the display of a toast notification. For example

Clicking Technology could display an error or warning toast
Clicking Entertainment could display an informational toast notification

We'll use the toast notifications that are currently included on the toast notification prototype page, but these will require updates to include the role attribute

toast notifications that are warning or error should have role="alert"
toast notifications that are success should have role="status" (also for informational, but that type isn't included in the test page)

A few helpful notes:

the role alert implicitly has aria-live set to assertive
the role status implicitly has aria-live set to polite
it might be worth testing that those attributes are actually working as expected, in case we need to explicitly set them
the toast notifications that are currently implemented have slight variations in them, to help us figure out how to best structure the related elements in a toast. Should we pick a single variation to use for this aria-live test?

Demo available at https://rawgit.com/andresgalante/jenn/master/single-notification.html

Some things we noticed when working on this:

There seem to be more differences in how role="alert" behaves vs role="status" besides just aria-live being assertive or polite. For our purposes:

role="alert" seems to be be best fit for toast notifications
`role="alertdialog" would be best for confirmation prompts
role="status" had different behaviors across screen readers and browsers. I'm not sure if there's anything in patternfly where this should be used.

Even though role="alert" implicitly has aria-live="assertive", I found that at least with testing in VO, it should be explicitly defined.


#2765 apply white label

Description
It is developed for the request to change the logo by applying white label to login screen and GNB.
Related Issue : #2765

How Has This Been Tested?

Check by modifying the svg tags in lnb-logo.component.html, login-logo.component.html, and the corresponding css.
Check if the login screen and GNB logo are displayed normally (by theme)
Need additional checks?
Change Logo Guide : https://github.com/metatron-app/metatron-discovery/blob/f%232765-white_label/discovery-server/src/main/asciidoc/change-logo-guide.adoc
Types of changes

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

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.

Additional Context

deploy to 4

@minhyun2 I hope you put some guidelines that any users can use

deploy to 4


Update README and solo node start to provide commands to setup kubectl port forward for network nodes

requested by Simi for uses to be able to leverage to setup a connection against the network.

Need more elaboration on this, is ths about to adding new flags to enable services such as
haproxy--svc ?

This is from our FST deployment notes.txt:
Get the name of the envoy gateway system:
  export ENVOY_SERVICE=$(kubectl get svc -n envoy-gateway-system --selector=gateway.envoyproxy.io/owning-gateway-namespace="${NAMESPACE}",gateway.envoyproxy.io/owning-gateway-name=fst -o jsonpath="{.items[0].metadata.name}")

Forward a port on the gateway to a local port:
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system "${LOCAL_PORT}":"${GATEWAY_PORT}" &

Some examples, that for convenience, use the same local port as that on the gateway:

To access the Hedera Mirror Node Explorer locally (port 8888 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 8888:8888 &
  open http://<IP_ADDRESS>:8888

To access the GRPC port of node 2 (starting port 52000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 52002:52002 &

To access the GRPC secure (TLS) port of node 1 (starting port 53000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 53001:53001 &

To access the gossip port of node 0 (starting port 51000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 51000:51000 &

To access the GRPC web port of node 5 (starting port 18000 for node 0 on the gateway):
  kubectl port-forward "svc/${ENVOY_SERVICE}" -n envoy-gateway-system 18005:18005 &

So, something like this, except use our haproxy grpc port.  test the commands to make sure they are good, then add them to a section in the README.md to help those less familiar with Kubernetes and kubectl expose the ports locally so they can use their network nodes to run tests against.

:tada: This issue has been resolved in version 0.31.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update Dagger for sample app to 2.4

Changelog https://github.com/google/dagger/blob/master/CHANGELOG.md#version-24-2016-04-21

Ok


GitHub Action

Can just do a request to /add with the URL
https://github.com/Satak/webrequest-action
It would be great if I could use an action in my action but it doesn't look like I can

Just need to test now


Two commands to launch Sensors in the Command Menu

I'm wondering why there are two options to open the Sensors drawer? Both the options seem to be doing the same thing.

AB#41385461

Thanks for filing. I'll make sure this shows up on the team's radar. It seems to me like we should just remove one in this case.

It's the same issue in Chrome as well, so I guess it could be an upstream issue.

I reported it here too: https://bugs.chromium.org/p/chromium/issues/detail?id=1365975


Use ceph image with a more specific tag that includes the date or commit ID

Currently, ceph csi image is built using ceph image with tag, v14.2. We can use a ceph image with tag that is more specific, e.g., with the date the image was created, v14.2.2-20190722, or with the HEAD commit ID. Rook does this currently.

@ajarr how this is helpful for the end user?

I'm not sure who you're referring to as end user?
IMO, this is good practice for the person who builds the CSI image that he uses a image with a more detailed tag. Unless otherwise you want the base Ceph image to always be the latest 14.2.x ? What if there was a bug in latest 14.2.x stable that affects Ceph CSI?

the commit tag added to the image in this PR https://github.com/ceph/ceph-csi/pull/469. from this, we can check from which tag the image is built.

PR #469 helps check the tag of Ceph-CSI release. I'm talking about the base Ceph image.

@ajarr if you do docket inspect on the image you will see ceph version
docker inspect quay.io/cephcsi/cephcsi:canary
[
    {
        "Id": "sha256:afb0079dd922597a926b8692af128455e1d33bf0c41244def8ce59f3636be7f0",
        "RepoTags": [
            "quay.io/cephcsi/cephcsi:canary"
        ],
        "RepoDigests": [
            "madhupr001/cephcsi@sha256:c16e6807a91102645840afbcf2311126610bb72683c8f79460d9fe8019a79e1a"
        ],
        "Parent": "sha256:91bd0b5601734afff652662f400e7176f0a106c6c29a22d727994abb4341bf0e",
        "Comment": "",
        "Created": "2019-07-24T11:35:45.79180354Z",
        "Container": "5b5c2db9e9b7de7aecb03da8a300b7aa02f20578123e0c032249c78919d40f03",
        "ContainerConfig": {
            "Hostname": "5b5c2db9e9b7",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "CEPH_VERSION=nautilus",
                "CEPH_POINT_RELEASE=-14.2.1",
                "CSIBIN=/usr/local/bin/cephcsi"
            ],

is this enough?

@Madhu-1 , let's suppose Ceph 14.2.3 has a bug that affects Ceph-CSI. The travis CI would start failing once the new image is pushed with tag v14.2 in ceph/ceph repo. Can you not avoid this with more detailed tags?

@ajarr you are taking from client library side right? this  cannot be avoided as the base ceph-csi image  as FROM ceph/ceph:v14.2 i assume this is a stable image

@ajarr you are taking from client library side right? this cannot be avoided as the base ceph-csi image as FROM ceph/ceph:v14.2 i assume this is a stable image

Yes, client side. And the base ceph csi image cannot be changed to FROM ceph/ceph:v14.2.2-20190722? v14.2.x might have bugs, right?

the ceph/ceph:v14.2 tag refers to the latest image build with Ceph 14.2.x. We should trust the Ceph maintainers to not introduce regressions in the 14.2.x stable updates. We do want updates of the image, specially for security and bugfixes in the packages that are provided by the OS.
I do not see a need for fixing the base image for Ceph-CSI to a very particular version of the Ceph image. It would cause more maintenance work (tracking Ceph image releases and updating FROM) than it is worth.
@ajarr Can this be closed now?

the ceph/ceph:v14.2 tag refers to the latest image build with Ceph 14.2.x. We should trust the Ceph maintainers to not introduce regressions in the 14.2.x stable updates. We do want updates of the image, specially for security and bugfixes in the packages that are provided by the OS.

There have been Ceph stable releases with regressions in the past. In that case wouldn't automatic updates be an issue?

I do not see a need for fixing the base image for Ceph-CSI to a very particular version of the Ceph image. It would cause more maintenance work (tracking Ceph image releases and updating FROM) than it is worth.

Ceph stable releases don't happen too often. I'm not sure if it's too much maintenance work.
Rook does this currently, https://github.com/rook/rook/blob/master/images/ceph/Makefile#L20

@ajarr Can this be closed now?

On Tue, Nov 19, 2019 at 05:22:04AM -0800, Ramana Raja wrote:

the ceph/ceph:v14.2 tag refers to the latest image build with Ceph 14.2.x. We should trust the Ceph maintainers to not introduce regressions in the 14.2.x stable updates. We do want updates of the image, specially for security and bugfixes in the packages that are provided by the OS.

There have been Ceph stable releases with regressions in the past. In that case wouldn't automatic updates be an issue?

Yes, that could be a problem. But this should almost never happen. In
case of regressions we can always introduce a temporary workaround.

I do not see a need for fixing the base image for Ceph-CSI to a very particular version of the Ceph image. It would cause more maintenance work (tracking Ceph image releases and updating FROM) than it is worth.

Ceph stable releases don't happen too often. I'm not sure if it's too much maintenance work.
Rook does this currently, https://github.com/rook/rook/blob/master/images/ceph/Makefile#L20

I do not know what advantage there could be for Rook. Maybe @leseb can
explain the reason. Otherwise they also might want to move to
ceph/ceph:v14.2 so that they do not need to update their Makefile everye
time.

the ceph/ceph:v14.2 tag refers to the latest image build with Ceph 14.2.x. We should trust the Ceph maintainers to not introduce regressions in the 14.2.x stable updates. We do want updates of the image, specially for security and bugfixes in the packages that are provided by the OS.
I do not see a need for fixing the base image for Ceph-CSI to a very particular version of the Ceph image. It would cause more maintenance work (tracking Ceph image releases and updating FROM) than it is worth.

Please see comment dropped here, I am unsure if the base image is auto updated and reduces any work in terms of maintenance and rebuilds of CSI image when this changes.


[FSunstone] Add LDAP Support

Description
Same functionality as RSunstone

Progress Status

[ ] Code committed
[ ] Testing - QA
[ ] Documentation (Release notes - resolved issues, compatibility, known issues)

No additional configuration is required, since the core use of the LDAP driver and fireedge use of XMLRPC, it is already a function of the oned to authenticate a user.


Rakesh mohan msft

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

Fixes https://github.com/Azure/azure-sdk-for-net/issues/22086

Duplicate PR


Contribution

Hi, I'd love to contribute to your research and learn more about how you've put these details together.
Are you experimenting in-game or looking through source files?
Thanks.

I'm looking through the source files to find all this information. Without going into too much detail (since this is most likely frowned upon by the developer), there's another Github repo out there that details unpacking Unity projects, as well as how to inspect Unity DLLs.

Good points. I haven't seen much code relating to the global push-to-talk, so I'm not too sure how that ties in to getting the speech system working again. Then again, the local push-to-talk working sporadically is definitely a bug.
IL2CPP will definitely make datamining harder, but not impossible. I've got a copy of the current build so I can try compare any new updates with the IL2CPP assembly. No guarantees though.

I would like to know where in the code he found the bad words. Find out if the game has the ability to translate bad words into other languages. I would like more about the "Generic reaction phrases"

also i would be down to help you guys confirm the info you find. i was planning on making a list like this myself but here it is and id be glad to help.

@caiocolin All phrases the game recognises are listed in PhraseListenerController::SetupKeywords(). The stable build of the game does not have localised version for curse words, but this may be different in the beta branch.
@RealPyretic Feel free to! I doubt the information in here will remain relevant for long, depending on how much the devs update the game in the coming months.


Problem running example

Running into very simple problem causing the sample program in the read me to fail.  Song.number is never populated.  In fact, it doesn't even exist in the Song.py class.  I added a couple lines (to Library.py and Song.py) that took care of this and fixed it...
Library.py
diff --git a/pyItunes/Library.py b/pyItunes/Library.py
index 60bb75b..2b91266 100644
--- a/pyItunes/Library.py
+++ b/pyItunes/Library.py
@@ -37,6 +37,7 @@ class Library:
                format = "%Y-%m-%d %H:%M:%S"
                for trackid,attributes in self.il['Tracks'].items():
                        s = Song()
+                       s.number = int(trackid)
                        s.name = attributes.get('Name')
                        s.artist = attributes.get('Artist')
                        s.album_artist = attributes.get('Album Artist')

and
Song.py
diff --git a/pyItunes/Song.py b/pyItunes/Song.py
index e6f00a2..4dc605e 100644
--- a/pyItunes/Song.py
+++ b/pyItunes/Song.py
@@ -2,6 +2,7 @@ class Song:
        """
        Song Attributes:
        name (String)
+       number (Integer)
        artist (String)
        album_artist (String)
        composer = None (String)
@@ -32,6 +33,7 @@ class Song:
        length = None (Integer)
        """
        name = None
+       number = None
        artist = None
        album_artist = None
        composer = None

I wonder if Song.number was removed in a new version of iTunes? Can you double check all the keys associated with each song? Maybe they've renamed it. The solution above assumes that the order of iteration equals song number (not sure this is the case).

There is a key called "Track ID" but no key called number in my iTunes Library XML file.  That key (Track ID) in the dictionary entry for the song is the same value as the dictionary entry's key in that dictionary.

EDH via Overlord

On Mar 28, 2016, at 11:05 AM, Liam Kaufman<EMAIL_ADDRESS>wrote:
I wonder if Song.number was removed in a new version of iTunes? Can you double check all the keys associated with each song? Maybe they've renamed it. The solution above assumes that the order of iteration equals song number (not sure this is the case).
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Ok, can you use Track Id then? I'll happily accept a pull request!

You bet — I’ll modify my original change and test it and then do a pull request

On Mar 31, 2016, at 10:10 AM, Liam Kaufman<EMAIL_ADDRESS>wrote:
Ok, can you use Track Id then? I'll happily accept a pull request!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub https://github.com/liamks/pyitunes/issues/25#issuecomment-203956204

Actually, do you have an  "iTunes Music Library.xml" file that used to work?  I'd like to make sure that any change can handle either version ;-)  -- maybe consider adding a folder to the root of the project and throwing a couple library XML files in there...would be a good place to proxy track library.xml schema changes, anyway


Support wildcard capture for Java methods with invariant T in return

Limited wildcard capture was added in #6682 but doesn't help with the Java method:
import java.util.concurrent.Callable;

public class TJ {
    public static <T> Callable<T> echo(Callable<T> t) {
        return t;
    }
}

where T appears invariantly in the return. (Note that Callable above is Java's Callable.)
import java.util.concurrent { Callable }

shared void run() {
    Callable<out Object> computer = nothing;
    TJ.echo<Object>(computer);
}

// source/simple/run.ceylon:5: error: argument must be assignable to parameter 't' of 'echo' in 'TJ': 'Callable<out Object>' is not assignable to 'Callable<Object>?'
//     TJ.echo<Object>(computer);
//                     ^
// 1 error

The actual use case is to construct a covariant FutureTask from a covariant Callable:
import java.util.concurrent { Callable, FutureTask }

shared void run() {
    Callable<out Object> computer = nothing;
    FutureTask<out Object> ft = FutureTask(computer); // can't
}

In principle, it would be possible to add in an overloaded version of the method, transforming to:
shared class TJ {
    shared overloaded static <T> Callable<T> echo(Callable<T> t);
    shared overloaded static <T> Callable<out T> echo(Callable<out T> t);
    shared overloaded static <T> Callable<in T> echo(Callable<in T> t);
}

However, that would make a lot of Java APIs look pretty ugly in the IDE.
An alternative approach might be to really implement wildcard capture, as suggested by @RossTate, but only enable it for generic types without reified type arguments (i.e. for Java types).

Actually there's probably a relatively simple way to implement a sort of "minimal" support for wildcard capture that would handle this case. Let me try.

Done. I'm now pretty far down the path of fully general support for wildcard capture for Java methods!
If I'm not mistaken, all I need now is to be able to capture contravariant wildcards in argument types.

I've updated the issue description to reflect that this is not restricted to the case of invariant occurrences in the return type 😄

Excellent!

On Sep 13, 2018, at 6:05 PM, Gavin King<EMAIL_ADDRESS>wrote:
I've updated the issue description to reflect that this is not restricted to the case of invariant occurrences in the return type 😄
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Added support for capturing contravariant wildcards in 17b6034. Enjoy!

There's one minor remaining limitation to this stuff.  It does work when the in Key and out Item occur in separate parameters, however, or when they both have the same variance.

Also, perhaps I should turn it on for Java constructor invocations, as well as method calls.

perhaps I should turn it on for Java constructor invocations, as well as method calls.

Done!

Ah, don't allow the type Map<in Key,...> at all! I did a study on mixing declaration-site and use-site variance, and I found that people just get really confused by use-site variances that "oppose" the corresponding declaration-site variances.
And I'm guessing "minimal" support just captures the explicit in/out argument and not the constraints that the class itself imposes on the corresponding type parameter? If so, that's fine, and I found that most (though not quite all) use cases of wildcard capture are covered by that.

Oh, sorry, @RossTate , that was confusing, my bad. I'm assuming this is the invariant type java.util.Map.
I agree that we don't need to let you override declaration-site variance with use-site variance annotations.

And I'm guessing "minimal" support just captures the explicit in/out argument and not the constraints that the class itself imposes on the corresponding type parameter?

Right. It's really pretty "dumb" TBH. Not much new code there at all.

You say "dumb", I say "simple" :)


[zh] Umbrella issue: pages out of sync in tasks section

The following pages are out of sync as of Jan 21, 2021. When signing up and working on a particular task, please leave a comment to this issue and ensure you have fetched the latest master.
Audit (XXL)

[ ] content/zh/docs/tasks/debug-application-cluster/audit.md

Kubeadm Upgrade (XXL)

[ ] content/zh/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md

Install Kubectl (XXL)

[ ] content/zh/docs/tasks/tools/install-kubectl.md

Stateful App (XL)

[ ] content/zh/docs/tasks/run-application/run-replicated-stateful-application.md

Connecting Frontend Backend (XL)

[ ] content/zh/docs/tasks/access-application-cluster/connecting-frontend-backend.md

HPA (XL)

[ ] content/zh/docs/tasks/run-application/horizontal-pod-autoscale.md

Probes (XL)

[ ] content/zh/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md

CRICTL (L)

[ ] content/zh/docs/tasks/debug-application-cluster/crictl.md

Service Account (L)

[ ] content/zh/docs/tasks/configure-pod-container/configure-service-account.md

Topology Manageer (L)

[ ] content/zh/docs/tasks/administer-cluster/topology-manager.md

Portforward (L)

[ ] content/zh/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md

HA (L)

[ ] content/zh/docs/tasks/administer-cluster/highly-available-master.md

Misc Batch 1 (M)

[ ] content/zh/docs/tasks/extend-kubernetes/setup-konnectivity.md
[ ] content/zh/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions.md

Misc Batch 2 (S)

[ ] content/zh/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md
[ ] content/zh/docs/tasks/tools/_index.md
[ ] content/zh/docs/tasks/manage-kubernetes-objects/kustomization.md
[ ] content/zh/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch.md
[ ] content/zh/docs/tasks/administer-cluster/namespaces.md
[ ] content/zh/docs/tasks/administer-cluster/nodelocaldns.md
[ ] content/zh/docs/tasks/administer-cluster/out-of-resource.md
[ ] content/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

Tip
To understand what are the contents to be synced, run this for example:
./scripts/lsync.sh content/zh/docs/tasks/administer-cluster/out-of-resource.md

/language zh
/triage accepted
/help

/language zh
/triage accepted
/help

I will try to work on some of items. I will mark which item I'm currently working on in the comment later.
/assign

I will try to work on some of items. I will mark which item I'm currently working on in the comment later.
/assign

I will try to sync Misc Batch 1 (M).
/assign

I will try to sync Misc Batch 1 (M).
/assign

I will work on the remaining items in Misc Batch 2 (S)

[ ]  content/zh/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md
[ ]  content/zh/docs/tasks/tools/_index.md
[ ]  content/zh/docs/tasks/manage-kubernetes-objects/kustomization.md
[ ]  content/zh/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch.md
[ ]  content/zh/docs/tasks/administer-cluster/nodelocaldns.md
[ ]  content/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

I will work on the remaining items in Misc Batch 2 (S)

[ ]  content/zh/docs/tasks/debug-application-cluster/debug-pod-replication-controller.md
[ ]  content/zh/docs/tasks/tools/_index.md
[ ]  content/zh/docs/tasks/manage-kubernetes-objects/kustomization.md
[ ]  content/zh/docs/tasks/manage-kubernetes-objects/update-api-object-kubectl-patch.md
[ ]  content/zh/docs/tasks/administer-cluster/nodelocaldns.md
[ ]  content/zh/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

I'm working on following items:

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (open)

Service Account
WIP

I'm working on following items:

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (open)

Service Account
WIP

I'm working on following items:

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (merged)

Service Account (L)
#26257 (merged)

Portforward (L)
#26283 (merged)

HA (L)
WIP

CRICTL (L)
WIP

I'm working on following items:

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (merged)

Service Account (L)
#26257 (merged)

Portforward (L)
#26283 (merged)

HA (L)
WIP

CRICTL (L)
WIP

I'm working on following items:

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (merged)

Service Account (L)
#26257 (merged)

Portforward (L)
#26283 (merged)

CRICTL (L)
#26316 (open)

HA (L)
#26332 (open)

@tengqm
The PR for "Service Account (L)" is merged. You might want to update the issue list with the PR #26257 .
The only item left seems to be "Topology Manageer (L)".

I will finish the last item "Topology Manageer (L)" in next couple days.

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (merged)

Service Account (L)
#26257 (merged)

Portforward (L)
#26283 (merged)

HA (L)
#26332 (merged)

CRICTL (L)
#26316 (open)

Topology Manageer (L)
WIP

All items are completed!

Issue Name
PR

Misc Batch 2
#26250 (merged)  #26252 (merged)

Service Account (L)
#26257 (merged)

Portforward (L)
#26283 (merged)

HA (L)
#26332 (merged)

CRICTL (L)
#26316 (merged)

Topology Manageer (L)
#26363 (merged)

🎉   We made it!
/close


'completionCurve' is ignored

It seems that completionCurve in ignored in the current implementation (it always seems to uses a linear curve when completing the transition animation). It'd be nice if we could use the easy in out curve for completion (while keeping the linear one when interacting with the transition).

Agreed. I would happily review a PR :)
One would have to map the UIViewAnimationCurve enum to a CAMediaTimingFunction name and then do a bit of math on cubic bézier curves in a category to get the progress value for each point in time.


"bind: address already in use" after docker restart

Hi cpuguy83,
Following your explanations on http://www.tech-d.net/2014/08/28/docker-grand-ambassador/ I tried to use your ambassdor image.
docker run --name mysql-amb -v /var/run/docker.sock:/var/run/docker.sock -d cpuguy83/docker-grand-ambassador -name mysql

docker run --name mysql -p 43306:3306 -d

(not complete command; Image Dockerfile contains EXPOSE 3306)
Then I restarted the mysql container with docker restart mysql. Unfortunately the ambassador is not able to bind the address and stops itself.
Do you know this issue?
2014/09/10 15:07:24 Container does not exist mysql
2014/09/10 15:07:24 Waiting for container to be created: mysql
2014/09/10 15:07:44 Initializing proxy
2014/09/10 15:07:44 Handling Events for: 221563a448ff64db0c12dd238277ce660d14e53662e1d07e8c9464cb7d57d6c3: /mysql
2014/09/10 15:07:45 Received event: &{221563a448ff64db0c12dd238277ce660d14e53662e1d07e8c9464cb7d57d6c3 start}
2014/09/10 15:07:45 Handling event start/restart
2014/09/10 15:07:45 Closing old servers
2014/09/10 15:07:45 Servers closed
2014/09/10 15:07:45 Proxying <IP_ADDRESS>:3306/tcp
2014/09/10 15:08:35 Received event: &{221563a448ff64db0c12dd238277ce660d14e53662e1d07e8c9464cb7d57d6c3 die}
2014/09/10 15:08:35 Handling event for stop/die/kill
2014/09/10 15:08:35 Received event: &{221563a448ff64db0c12dd238277ce660d14e53662e1d07e8c9464cb7d57d6c3 start}
2014/09/10 15:08:35 Handling event start/restart
2014/09/10 15:08:35 Closing old servers
2014/09/10 15:08:35 Servers closed
2014/09/10 15:08:35 Proxying <IP_ADDRESS>:3306/tcp
2014/09/10 15:08:35 Received event: &{221563a448ff64db0c12dd238277ce660d14e53662e1d07e8c9464cb7d57d6c3 restart}
2014/09/10 15:08:35 Handling event start/restart
2014/09/10 15:08:35 Closing old servers
2014/09/10 15:08:35 Servers closed
2014/09/10 15:08:35 Proxying <IP_ADDRESS>:3306/tcp
2014/09/10 15:08:35 listen tcp <IP_ADDRESS>:3306: bind: address already in use

Thanks for checking this issue. I would really like to use your image.

Thanks for fixing this issue :-)


Xtensa code relocation

Enable ARCH_HAS_CODE_DATA_RELOCATION for Xtensa, as well as add support for two platforms. As Xtensa lacks a common linker script, it is necessary to enable each platform individually. This patchset enables for "sample_controller" and "intel_adsp/cavs" ones.
Support for using "program headers" (phdr) in the memory regions passed to gen_relocate_app.py is added as some linker script uses them.
Finally, updated test to support xtensa/sample_controller, and a sample added to show it working for xtensa/intel_adsp/cavs, as due some peculiarities of the platform (discussed in the sample), it can't use tests/application_development/code_relocation.

as @marc-hb pointed in a private conversation I should also get a look on this. Will do it in on tomorrow (Thursday).

as @marc-hb pointed in a private conversation I should also get a look on this. Will do it in on tomorrow (Thursday). Would appreciate if this can be delayed by 1 day.

@dbaluta gentle reminder to review this one =D


conda support not activated, virtualenv is used

I tried to use conda support as explained in the docs, but virtualenv is still being used. My test build is at https://readthedocs.org/projects/-pitrou-llvmlite/builds/3609496/.
The changeset it points to is the following: https://github.com/numba/llvmlite/commit/e99dbc88e488f18e3b6133677f8635dea677aabd

Hmm, it looks like the second build on a server picks up conda correctly. I'll investigate.

Believe this should be resolved. Let me know if it isn't working for you.


Build a Durm-Machine

**Drum Machine **
Description:
This pull request introduces a fully responsive Drum Machine web application built using React. The app allows users to interact with different drum pads to play corresponding sounds, creating their own beats. The design is optimized for mobile and tablet devices, ensuring smooth performance and user experience across various screen sizes, including screens as small as 430 px.
Features:

Responsive Design: The layout adjusts seamlessly to different device sizes, ensuring accessibility on both mobile and tablet devices.
Interactive Pads: Each drum pad is clickable and triggers the associated sound effect.
Keyboard Support: Users can also use their keyboard to interact with the drum pads.
Clean and Modular Code: The project follows React best practices with a clean component structure, making it easy to maintain and extend.
Improvements:
Enhanced user interface for better usability and aesthetics.
Optimized performance for faster loading times and smoother interactions on all devices.
Added support for smaller screens to enhance mobile user experience.
Next Steps:
Implement additional sound packs for a wider variety of drum sounds.
Introduce features like recording and playback to allow users to save their beats.

Hi! Please change the settings in Vercel so that anyone with the link can see it.


[🐛 Bug]: Flickering when specifying location (settings) for weather

VSCode Environment
Version: 1.70.0 (Universal)
Commit: da76f93349a72022ca4670c1b84860304616aaa2
Date: 2022-08-04T04:38:55.829Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 21.6.0
Marquee Version
v3.2.1659813370
Workspace Type
Local Workspace
What happened?
When a user starts typing it appears that the modal reloads/rerenders with every keystroke that leads to an odd flickering. While manageable it does negatively affect the UX.
What is your expected behavior?
No flickering and potentially better interaction response.
Relevant Log Output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Is there an existing issue for this?

[X] I have searched the existing issues

@sourishkrout moved dialog outside of the widget to avoid the flicker effect


Add colorbar to the multiple xyz overlay plot

Hi Sebastian,
I’ve added a colorbar to facilitate the interpretation of the plot that arises from:
python3 xyzoverlay.py multi-mol_trj.xyz -aa -vcm -cm coolwarm -ee H
the new feature should appear by just adding the keyboard -cb True:
python3 xyzoverlay.py multi-mol_trj.xyz -aa -vcm -cm coolwarm -cb True -ee H
otherwise I think that it was not completely clear how many structures were considered in the plot. In my specific case, it is interesting to know how many steps did it take to optimize the molecular structure with quantum mechanics. Besides, it also helps to point towards the first and last structure, which could be a bit confusing without a color reference.
I hope it may be of interest and let me know if any adjustments are needed!
Best,
Enric

Hi Enric,
now I got the FutureWarning regarding Downcasting again. Uncommenting pd.set_option("future.no_silent_downcasting", True) removes it. Otherwise your addition is nice. However, it works only good for a large number of molecules where the number of colors is equal or the number of molecules is larger than the number of colors in the colormap. Try it with two or three molecules to check what I mean.
Best,
Sebastian

Hi Sebastian,
As far as I can tell, it was related to how the **xyz_df_list ** was constructed. The total number of xyz was always minus one.
Instead, if the following function is employed to construct the same list, the issue is solved, and one can get a plot where two and three xyz have different colors.
Let me know if you find it useful.
Best,
Enric

def read_xyz_to_dataframe(file_path):
    """
    Given a text file with concatenated xyz coordinates, the function generates
    a list of panda objects for each xyz.
    """

    with open(file_path, 'r') as file:
        lines = file.readlines()
    data = []
    i = 0
    while i < len(lines):
        # Number of atoms (first line)
        num_atoms = int(lines[i].strip())
        i += 1
        # Second line (energy or other information)
        i += 1
        # Temporal list for every xyz
        data2 = []
        # Extract atomic coordinates
        for _ in range(num_atoms):
            line = lines[i].split()
            element = line[0]
            x, y, z = map(float, line[1:4])
            data2.append([element, x, y, z])
            i += 1
        # List of xyz
        data.append(data2)

    # Now convert it to list of pd objects
    xyz_df_list = list()
    columns = ["element", "x", "y", "z"]
    for structure in data:
        xyzdata = structure
        df = pd.DataFrame(xyzdata, columns=columns)
        xyz_df_list.append(df)

    return xyz_df_list

xyz_df_list = read_xyz_to_dataframe(args.filename[0])


Search/replace results: align right the folder path

I think it would be nice to have this:

Instead of this:

To be able to see which files are in the same folder and which are not.
It's really useful when you have a lot of search results in the large project.

/duplicate of #74637
@koteyur your suggestion of right-aligned paths doesn't exactly match proposals in the linked issue, so you may like to contribute ideas there.


Vite change detection very delayed

Describe the bug
I'm running the dev server and seeing that after I make a change to a file in my repository it takes many minutes to trigger an HMR update
Reproduction
https://github.com/bringel/arena-draft-trainer
Steps to reproduce

npm run dev
Change a file in the repository and wait for HMR update

In this case you can see the file timestamp is "Nov 22 09:30", but vite didn't pick up the change until 9:39
System Info
➜ npx envinfo --system --npmPackages '{vite,@vitejs/*,rollup}' --binaries --browsers
Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y) y

  System:
    OS: macOS 13.6
    CPU: (4) x64 Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz
    Memory: 29.35 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Safari Technology Preview: 17.0
  npmPackages:
    @vitejs/plugin-vue: ^4.3.4 => 4.5.0
    vite: ^4.4.9 => 4.5.0

Used Package Manager
npm
Logs

Vite logs
➜ npx vite --debug hmr

  VITE v4.5.0  ready in 911 ms

  ➜  Local:   http://localhost:5173/
  ➜  Network: use --host to expose
  ➜  press h to show help
  vite:hmr [self-accepts] src/App.vue +0ms
  vite:hmr [self-accepts] src/Home/Home.vue +51ms
  vite:hmr [self-accepts] src/assets/main.css +143ms
  vite:hmr [self-accepts] src/CardGrader/CardGrader.vue +33ms
  vite:hmr [self-accepts] src/components/Button.vue +296ms
  vite:hmr [self-accepts] src/components/Nav.vue +15ms
  vite:hmr [self-accepts] src/components/Card.vue +0ms
  vite:hmr [self-accepts] src/CardGrader/components/GradingScale.vue +11ms
  vite:hmr [self-accepts] src/components/DatasetSelector.vue +36ms
[@vue/compiler-sfc] `defineProps` is a compiler macro and no longer needs to be imported.

[@vue/compiler-sfc] `defineEmits` is a compiler macro and no longer needs to be imported.

  vite:hmr [self-accepts] src/components/segmented-control/SegmentedControl.vue +161ms
  vite:hmr [self-accepts] src/components/segmented-control/Segment.vue +7ms
  vite:hmr [file change] src/CardGrader/CardGrader.vue +9m
  vite:hmr [vue:update(template)] /Users/bringel/Coding/arena-draft-trainer/web/src/CardGrader/CardGrader.vue +0ms
9:39:18 AM [vite] hmr update /src/CardGrader/CardGrader.vue, /src/assets/main.css
  vite:hmr [self-accepts] src/assets/main.css +58ms
  vite:hmr [self-accepts] src/CardGrader/CardGrader.vue +7ms

file timestamp
➜ ls -al web/src/CardGrader
total 4
drwxr-xr-x  4 bringel staff  128 Nov 10 16:49 .
drwxr-xr-x 13 bringel staff  416 Oct 23 12:32 ..
-rw-r--r--  1 bringel staff 1697 Nov 22 09:30 CardGrader.vue
drwxr-xr-x  3 bringel staff   96 Nov 19 11:08 components

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The repro link is a 404. If this is your full app, please first try to remove plugins to see if you find where is the issue and be able to create a good minimal reproduction.

Whoops sorry @patak-dev , forgot the repository was set to private.  It is my full app but I don't have any plugins other than the vue plugin installed for vite:
import { defineConfig } from 'vite';

const Path = require('path');

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [vue()],
  resolve: {
    alias: {
      '@': Path.resolve(__dirname, './web/src')
    }
  },
  root: './web',
  build: {
    outDir: '../public',
    emptyOutDir: true
  },
  server: {
    proxy: {
      '/api': 'http://localhost:9292'
    },
    open: '/'
  }
});

HMR is instant for me when I try it at https://stackblitz.com/~/github.com/bringel/arena-draft-trainer
One thing that it may be an issue, you are setting outDir to be /public. You need to disable or change in that case the default public dir. Using publicDir: false or give it another folder.

Interesting I will give it a shot with the public directory change. It's also working normally in the stackblitz for me so I was assuming it was something with my setup on my computer

Like all things in life, this was fixed by rebooting. Something must have gotten funky with the filesystem events I think since HMR would run, just like 15 minutes after changing the file. Thanks for checking and making sure that my config wasn't messed up

Your config is wrong though, you need to disable publicDir or your output files could be served during dev.

Sorry yeah I meant other than that


add OSGi manifest headers for jars

The gradle plugin that is added to the build is provided by BND tools: https://github.com/bndtools/bnd/tree/master/gradle-plugins. General info about BND tools can also be found on https://bndtools.org/
Adobe Experience Manager is also using the Maven variant for example in their archetype to achieve OSGi compatible JAR's bundles: https://github.com/adobe/aem-project-archetype/blob/master/src/main/archetype/pom.xml#L214
resolves #86

There's a similar PR in opentelemetry-java right now: https://github.com/open-telemetry/opentelemetry-java/pull/6669
My comment there is applicable here as well:

As someone without OSGi experience, I think its important to add some sort of end-to-end integration test. A sample app built with OSGi which consumes these artifacts and demonstrates it works as intended.

@jack-berg yes I noticed, @royteeuwen and myself are working on some details how to solve the current issues we are seeing while testing, this topic definitely needs some more work!


(EAI-177): Implement FAQ Finder

Jira: https://jira.mongodb.org/browse/EAI-177
Changes

Adds FAQ finding to the scripts package
Using DBSCAN algorithm to cluster similar questions
Script takes optional epsilon argument (otherwise defaults to 0.05). Epsilon is the max distance to form a cluster.
Stores FAQ entries in a 'faq' collection in the database for further processing. Each question and response is stored even though many are similar.

Example FAQ entry document:

Notes
The intention is to run this on cron maybe daily or every five days. Because each run stores the timestamp, we'll be able to look at trends in FAQ over time.
For verified answers, the next step is to script a transfer from the faq collection to a yaml document that can be filled out by a human, per the spec.

I haven't pushed upstreammmm


Expose the secret as an environment variable

I was a bit too eager to remove the GITHUB_TOKEN lines from the environment variables setup. Although using the new mechanism I no longer need a Personal Access Token (PAT), the created secret must still be exposed as an environment variable for some of the action steps to pick it up.
Signed-off-by: Ringo De Smet<EMAIL_ADDRESS>

@ringods YAY!


Conditional redo

For example:

Take umbrella if it's rainy
Bring power outlet if it's Tuesday

This is in my head as well :)


Exclude Shelly H&T if powered by USB and not by battery

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
SSIA
Describe the solution you'd like
Exclude Shelly H&T if USB powered
Describe alternatives you've considered
Manual excluding the device, but if in future you switch to battery you easily forget to re-enable it
Additional context

The way others have got around this multiple power source issue is to have the library with a MANUAL battery type, that way it won't get discovered and people can add it manually and put USB or battery type depending.
I'll update the library to this, I don't have one of these myself so didn't know it was dual power.


Harbor Version v2.3.3 METHOD_NOT_ALLOWED

Describe the bug
made terraform apply and get
 Error: [ERROR] unexpected status code got: 405 expected: 200
  {"errors":[{"code":"METHOD_NOT_ALLOWED","message":"method PUT is not allowed, but [POST] are"}]}

   with harbor_retention_policy.policy["project"],
   on retention.tf line 7, in resource "harbor_retention_policy" "policy":
    7: resource "harbor_retention_policy" "policy" {

Expected behavior
apply all =)
Additional context
on older version of harbor its work

Error: [ERROR] unexpected status code got: 401 expected: 201
  {"errors":[{"code":"UNAUTHORIZED","message":"{\"code\":10011,\"message\":\"unauthorized\",\"details\":\"unauthorized\"}"}]}

   with harbor_garbage_collection.main,
   on retention.tf line 1, in resource "harbor_garbage_collection" "main":
    1: resource "harbor_garbage_collection" "main" {


Failed to check Electron's module version number

On Windows:
> .\node_modules\.bin\electron-rebuild.cmd
46
Failed to check Electron's module version number: [...]

electron-prebuilt and electron-rebuild were both installed with npm install --save-dev:
"devDependencies": {
    "electron-prebuilt": "^0.35.2",
    "electron-rebuild": "^1.0.2"
}

It seems that w/ electron-prebuilt 0.35.2, line
versionAsString = (result.stdout + result.stderr).replace(/\n/g, '');
leads to an empty version string.
Manually setting versionAsString = '46' solved the problem.
My guess is that electron.exe's std(out|err) is not forwarded to electron-rebuild, but printed straight to the console (46 in the log above).

I'm getting this on Windows too. Does this need filing in the electron repo?

I am also having this issue on Windows, and can confirm that result.stdout and result.stderr are both empty strings inside the getElectronModuleVersion method.

I get the same issue, when rebuilding electron 32bit from a windows 8.1 32bit box.
Rebuilding electron 64bit  from a 32bit box works, and building both of it from windows 10 64bit works.
Tested with electron-prebuilt 0.35.4 installed as devDependencies

Gonna try to fix this soonish, sorry about the bug

No worries, thanks for keeping an eye on it! This project definitely makes my build process simpler.

I am trying to electron-rebuild but it fails. After settings versionAsString = '46' in lib/main.js:124 I got further. But now I'm facing another issue:

npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g
gyp ERR! clean error
gyp ERR! stack Error: EPERM: operation not permitted, unlink 'C:\Users\developer\Desktop\EPS\node_modules\nslog\build\Release\nslog.node'
gyp ERR! stack     at Error (native)
gyp ERR! System Windows_NT 10.0.10240
gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\developer\Desktop\EPS\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\developer\Desktop\EPS\node_modules\nslog
gyp ERR! node -v v5.3.0
gyp ERR! node-gyp -v v3.2.1
gyp ERR! not ok

Hah, after deleting that file manually it worked. Anyhow, please fix the original issue :)

A quick fix is to set the ELECTRON_NO_ATTACH_CONSOLE environnement variable to 1 when rebuilding.
In cmd:
SET ELECTRON_NO_ATTACH_CONSOLE=1 && node_modules\.bin\electron-rebuild

In shell
ELECTRON_NO_ATTACH_CONSOLE=1 node_modules/.bin/electron-rebuild

I made a pull request a few weeks ago to fix the issue. Waiting for merge.

@felicienfrancois This indeed fixed it, thank you very much.
Line 14 in rebuild.js now looks like this (for me, on windows):
return promisedExec('SET ELECTRON_NO_ATTACH_CONSOLE=1 && ' + electron + ' --version')

This happen systematically when using a UNIX shell emulator (MinGW & co)


Fonts don't work when building with Cairo on Windows

When building with the Cairo graphics backend under Windows (using msys2-mingw64, which seems to be the best solution for porting a Gtk+ 3 application to Windows at the moment), all fonts fall back to the default sans font (so no math symbols render correctly, etc.) This is because Cairo::select_font_face always uses the "system default" font selector, which is the native win32 mechanism when building under Windows, but Font_cairo loads fonts by making them visible to fontconfig only.
I have a solution to this that stores a Cairo::FtFontFace object inside Font_cairo and loads it using Cairo::set_font_face, and can make a PR if you are interested. I haven't tested it that extensively though, and you might want pick a different approach.

@blackhole89 Any PR is appreciated! I'm waiting for your PR :grinning:

The gdi_win could be removed at compile time if porting the Gtk+ 3 to Windows but can be reserved as a demo to show how to implement the Win32 version.

Well, I built with linux defined manually; it doesn't seem like msys2 even contains gdi+ headers. (My use case ultimately involves rendering to a Cairo surface, so doing any rendering with GDI would be annoying anyway.)

OK, I have the plan to port the Gtk+ 3 to Windows and macOS, so the annoying macros __OS_Linux__ / __OS_Windows__ / ... can be removed.


Run Keyword If and Run Keywords do not work correctly in dry-run if used with Given/When/Then prefixes

Looking to upgrade to from version 2.9 to version 3.0.2 on Ubuntu and when I ran a dryrun on our suite I found that preceding 'Run Keyword If' with an 'ELSE' clause with a Gherkin keyword causes the ELSE clause to be ignored and it to be used as arguments to the keyword.
This example test runs and dry runs fine on 2.9, and runs fine on 3.0.2, but fails during a dry run on 3.0.2.
*** Test Cases ***

Gherkin
    [Documentation]  This test case fails a dry-run
    Given Run Keyword If  3 == 4  Fatal Error  ELSE  No Operation
    When Run Keyword If  3 == 4  Fatal Error  ELSE  No Operation
    And Run Keyword If  3 == 4  Fatal Error  ELSE  No Operation
    Then Run Keyword If  3 == 4  Fatal Error  ELSE  No Operation

No Gherkin
    [Documentation]  This test case works just fine
    Run Keyword If  3 == 4  Fatal Error  ELSE  No Operation

# pybot --version
Robot Framework 3.0.2 (Python 2.7.12 on linux2)
# pybot --dryrun ./run_keyword_if.robot
==============================================================================
Run Keyword If
==============================================================================
Gherkin :: This test case fails a dry-run                             | FAIL |
Several failures occurred:

1) Keyword 'BuiltIn.Fatal Error' expected 0 to 1 arguments, got 2.

2) Keyword 'BuiltIn.Fatal Error' expected 0 to 1 arguments, got 2.

3) Keyword 'BuiltIn.Fatal Error' expected 0 to 1 arguments, got 2.

4) Keyword 'BuiltIn.Fatal Error' expected 0 to 1 arguments, got 2.
------------------------------------------------------------------------------
No Gherkin :: This test case works just fine                          | PASS |
------------------------------------------------------------------------------
Run Keyword If                                                        | FAIL |
2 critical tests, 1 passed, 1 failed
2 tests total, 1 passed, 1 failed

To be honest, I didn't write the test so I'd have to talk to the dev who
did to come up with the reasoning as why they did it.  I agree with you
that it is pretty ugly, and it is actually worse because the place it is
used is in a test case using a template.  We do some parsing of our tests
to produce a test document so I'd have to look to see what it ends up
looking like.  Of the approximately 1,700 test cases we have this only
happens in one place so changing the test or marking it to be skipped
during a dry run would be easy, but I figured I should at least report it
since I didn't see it as a known issue and it appears to be a regression
between 2.9 and 3.0.2.
On Fri, Oct 26, 2018 at 3:27 PM Pekka Klärck notifications-at-github.com
|GitHub/Home|<EMAIL_ADDRESS>wrote:

I can reproduce this in dry-run mode but it doesn't occur when executing
tests normally. Most likely wouldn't be too complicated to fix, but to be
honest I don't think that's worth the effort. The reason to use the gherkin
style is to create extremely readable test cases, and Run Keyword If is
extremely unreadable and generally shouldn't even be used in the test case
level. Could you clarify the use case for such a strange combination?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/robotframework/robotframework/issues/2994#issuecomment-433533459,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFL06l6RwjrOeGHtsO190pxBk0rym5UZks5uo3AfgaJpZM4X81Vn
.

This turned out to be so easy to fix that I can do it even though I'm still not certain about the use case. The fix will be only in RF 3.1 beta 2, so if you are planning to migrate to 3.0.2 or 3.0.x in general you won't get it.

Great, thanks.
On Fri, Oct 26, 2018 at 5:16 PM Pekka Klärck notifications-at-github.com
|GitHub/Home|<EMAIL_ADDRESS>wrote:

This turned out to be so easy to fix that I can do it even though I'm
still not certain about the use case. The fix will be only in RF 3.1 beta
2, so if you are planning to migrate to 3.0.2 or 3.0.x in general you won't
get it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/robotframework/robotframework/issues/2994#issuecomment-433557690,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFL06h5pBJFhG7CQS6e77dXL2gHj9Yvrks5uo4mzgaJpZM4X81Vn
.

I can reproduce this in dry-run mode but it doesn't occur when executing tests normally. Most likely wouldn't be too complicated to fix, but to be honest I don't think that's worth the effort. The reason to use the gherkin style is to create extremely readable test cases, and Run Keyword If is extremely unreadable and generally shouldn't even be used in the test case level. Could you clarify the use case for such a strange combination?

I also encountered this problem.I am now migrating the company's test cases from Python2 to Python3.And now,all test cases are reported wrong: Keyword 'BuiltIn.Run Keyword If' expected at least 2 arguments, got 1.
How should I change now, and all test cases need to be changed " BuiltIn . Run Keyword If"?

@shadowmimosa Is it really the exact same problem? Do you have the errors when using dry-run and Gherkin steps? Can you test with latest 3.1beta1?

This problem is not Python version dependent. It's fixed now but the fix is not in beta 1 yet.

@HelioGuilherme66 Sorry, I was a little mistaken. It's not the same problem.
This is not a question of "Run Keyword If", but of the keyword "Get Json Value" in the "HttpLibrary. HTTP" library.
I heard that HttpLibrary.HTTP was abandoned in Python3, so it was not used.
Is there any good way to replace it?


ChatGPT Aliases Should Search for Keyword Within the Prompt, Instead of the Other Way Around

Is your feature request related to a problem? Please describe.
In the case of using a prompt again and again, the prompt usually is used to explain a task for processing other text. ChatGPT aliases should work like it will search for the keyword in the prompt, instead of searching for a full match to see if the original prompt is a key as is in the aliases_dict
Describe the solution you'd like
I'm using the following ChatGPT aliases:
EEE=Please provide the English translation for these sentences:;JJJ=Please provide the Japanese translation for these sentences:;CCC=Please provide the Mandarin Chinese translation for these sentences:

And I hope when I type EEE こんにちは ChatFred will actually send Please provide the English translation for these sentences: こんにちは to ChatGPT instead of doing nothing because EEE こんにちは itself is not a keyword.
Describe alternatives you've considered
Instead of
    aliases_dict = __prepare_aliases()
    if prompt in aliases_dict:
        return aliases_dict[prompt]
    return prompt

in file workflow/src/aliases_manager.py, my tested and suggested code:
    aliases_dict = __prepare_aliases()
    for k, v in aliases_dict.items():
        prompt = prompt.replace(k, v)
    return prompt

Hey @Sponge-bink!
Maybe you want to create a PR for this too?


Roll Flutter Engine from 0631c3f870d9 to 700507fea698 (2 revisions)

https://github.com/flutter/engine/compare/0631c3f870d9...700507fea698
2022-09-27<EMAIL_ADDRESS>Adds documentation for core snapshot targets (flutter/engine#36434)
2022-09-27<EMAIL_ADDRESS>Roll Dart SDK from b304248654ab to 5130dce07cd8 (1 revision) (flutter/engine#36440)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Landing this manually since this is only waiting on the Cirrus customer_testing shard, which is a duplicate of a LUCI shard.


feat: show slash command prompt on focus in property pane

Description

[!TIP]
Add a TL;DR when the description is longer than 500 words or extremely technical (helps the content team).
Please also include relevant motivation and context. List any dependencies that are required for this change. Add links to Notion, Figma or any other documents that might be relevant to the PR.

Fixes #Issue Number
or
Fixes Issue URL

[!WARNING]
If no issue exists, please create an issue first, and check with the maintainers if the issue is valid.

Automation
/ok-to-test tags=""
:mag: Cypress test results

[!CAUTION]
If you modify the content in this section, you are likely to disrupt the CI result for your PR.

Summary by CodeRabbit

New Features

Enhanced the code editor to dynamically show a slash command menu for certain widgets, improving the user's editing experience.
Introduced logic to selectively enable slash command functionality for table and JSON widgets, specifically for the data property.

Enhancements

Updated the code editor's hint system to support additional context, including datasource information and feature flags, enriching the autocomplete and suggestion capabilities.

Bug Fixes

Fixed an issue where unnecessary bindings were applied to widgets, ensuring cleaner and more relevant code generation.

/build-deploy-preview skip-tests=true

Keeping in draft state, because we still need to decide whether to add this behind a flag or release it to everyone

/build-deploy-preview skip-tests=true

/build-deploy-preview skip-tests=true


[Request] Make a fake Inter font version

I use Linux and the font I use is Inter, the symbols do not show up unless i switch my font to Helvetica which (in my opinion) doesn't work as a system font.
If its not too much extra effort could you make it?

if you don't want to maintain it just providing how you made the fake Helvetica would be very useful


Update community codeowners

This adds both org admins as maintainers of the community repo to help with reviews.

Summary

Release Note

Documentation

@cpanato added you as well


way to combine files before applying filters

so maybe I missed something, but is there a switch or method to combine the files of an asset collection before running them through the filters associated with the collection?
Ex:
		$AssetManager = new AssetManager();
		// Prepare the AssetManager with all core assets
		$AssetManager->set('coreCss', new AssetCollection(array(
			new FileAsset('module/Application/assets/css/sheet1.scss'),
			new FileAsset('module/Commerce/assets/css/sheet2.scss'),
		)));

		$FilterManager = new FilterManager();
		$FilterManager->set('scss', new ScssphpFilter());

		$factory = new AssetFactory('/');
		$factory->setAssetManager($AssetManager);
		$factory->setFilterManager($FilterManager);

		// Create the assets
		$coreCss = $factory->createAsset(array(
				'@coreCss',
			), array(
				'scss',
				'?cssmin',
			), array('output' => 'assetic/core.css')
		);

if I have scss variables defined in sheet1, and referenced in sheet2.scss, the compiler fails when trying to compile sheet2.scss, as it's compiling the .scss files separately.

+1!
I need to combine first and then apply less filtering on two bootstrap files:

variables.less // from AppBundle
bootstrap.less // from a vendor repo

Then i would create a named asset "bootstrap":
assetic:
assets:
bootstrap:
inputs:
-<EMAIL_ADDRESS>-<EMAIL_ADDRESS>filters:
- lessphp
Thanks!

:+1: Also, it seems like #605 is related to this?

+1
Is any workaround solution for this feature?


Asset Share Commons Share And Download buttons not functioning

We are using Asset share commons 2.1.12 version.....we were using the share and download modals that are present but we are not able to make them work.
We believe it to be an error in the UrlImpl.java file present at the location "asset-share-commons-asset-share-commons-2.1.12\asset-share-commons-asset-share-commons-2.1.12\core\src\main\java\com\adobe\aem\commons\assetshare\content\properties\impl" as this the error that is getting thrown when we use the button.

Can you please help us with this issue?

Is this happening for every asset? If only certain ones, can you provide the path (or even better a package of an asset that doesn't work)?
Thanks!

This is happening for every asset from what we can see....

path from where we try to download: "/content/dcx-mediaplace/asc/en/home/category-page/subcategoryList/subcategoryResult.html".
Asset path example: "/content/dam/multisite/multi-brand/parts/na/multi-country/images/complementary/online-complementary/12499/1234-PIC31.jpg".

@Shubhankar-Kumar-1 -
What version of AEM are you one?
So it looks like the problem is the Path computed property is not active, thus not injected, thus null.
https://github.com/adobe/asset-share-commons/blob/develop/core/src/main/java/com/adobe/aem/commons/assetshare/content/properties/impl/UrlImpl.java#L74
Can you check in /system/console/components what the OSGI component registration for PathImpl looks like?
com.adobe.aem.commons.assetshare.content.properties.impl.PathImpl

this is the component status in our aem

I would kindly request you to help us on this matter as we are not able to fix this issue and the code is already in production...this will get escalated on our side if we don't fix this soon. We can also connect if required for this matter.

Hi @Shubhankar-Kumar-1  - sorry, I cannot reproduce this w/ 2.1.12 on 6.5.11 -- this all works fine for me.  So I don't know how to help you. I suggest you try reproducing this on a vanilla AEM 6.5 SP11 with vanilla ASC 2.1.12 (or even better, you should be using 2.2.0)
The exception you provided doesn't make sense since from what i can tell the only thing i can see on that line that would cause a NPE is if the PathImpl OSGi component is not active, which you show as active in the previous screenshot.
Maybe you can download ASC source code (using git tag for 2.1.12) and hook up a remote debugger to your local that is exhibiting this to understand whats going on in your AEM better.

Closing. Please re-open of you need more help.


cannot import name 'SGD'

Traceback (most recent call last):
  File "train_models.py", line 13, in <module>
    from keras.optimizers import SGD
ImportError: cannot import name 'SGD'

https://stackoverflow.com/a/68199964

replaced keras with tensorflow.keras


504 Gateway time out

https://d2s.dschu012.dev/ won't load. 504 Gateway time out

back up.

Thank Much