ACI-Networking: Ports are always exposed to other Container inside a Goup

Corresponding section in the documentation:

Containers within a group can reach each other via localhost on the ports that they have exposed...

And on yaml reference:

ports: # Exposed ports on the instance
- protocol: string
port: integer

But regardless of whether I expose a port or not, it is always accessible within the group(instance).
The expizite specification in YAML has no effect.
According to my understanding of the documentation, a port that is not specified in YAML should not be accessible through other containers within a group. (Similar to docker Compose)
This is currently not the case.
I have created a small test scenario:
1 container with a greeting service on Port 8080
1 container with a greeting service on Port 8090
A third container tries to reach the services within the group with curl.
(curl localhost:8080/greet/FromPort8080 --next  localhost:8090/greet/FromPort8090)
I expose port 8080 for container 1 but I do not expose port 8090 for container 2 in the deployment YAML.
Deployment YAML
Result:

{"message":"Hello FromPort8080!"}{"message":"Hello FromPort8090!"}

Container 3 can access both services although I did not release port 8090 in container 2.
I would like to have the option, as stated in the documentation, to release a port within the groups only if explicitly specified. The default should be not to expose.
But until then the documentation has to be adapted to the current behavior.

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

ID: ff247151-29f6-4a55-61b2-e5eae2d48927
Version Independent ID: 159517fe-202c-967d-f572-49c4f6988c46
Content: Azure Container Instances container groups
Content Source: articles/container-instances/container-instances-container-groups.md
Service: container-instances
GitHub Login: @dlepow
Microsoft Alias: danlep

@Herr-Sepp
Thanks for the feedback! We are currently investigating and will update you shortly.

@Herr-Sepp Ports specified in the yaml will be opened for the public ip which is assigned to that ACI.
If we are using localhost, There is no port restriction. Thats why all the third container is able to reach other containers.
In your case, You have opened 8080, So you can access that port only via the public ip assigned to that ACI.
you cant access 8090 via the public ip.
Let me know if you need more information

Ok so all ports are always accessible for all container inside the group and that can not be prevented? This should be included in the documentation.
What do you mean with:

If we are using localhost,

Is there another way?

In your case, You have opened 8080, So you can access that port only via the public ip assigned to that ACI.

In my example this is not yet the case.
To reach a port from the outside I have to release it within the container declaration AND within the IpAddress configuration.
What i mean with Container declaration:

properties:
  containers:
  - name: containername
    properties:
      image: imagepath
      ports:  <--

What i mean with Group ipAdress declaration:

properties:
 ipAddress:
    type: Public
    ports: <--

So releasing the port only within the container configuration has no effect as long as I don't specify it with ipAdress as well? There should be a warning that the setting has no effect.
But what is the use of port release within the container configuration at all?
Since there is only one address range, a port cannot be occupied by several containers.
Specifying wich ports you want to expose inside IpAdress should be enough, right?

Yes. all ports are open for containers inside the container group. That cannot be prevented.
Thats mentioned in the document under networking like this.
 Containers within a group can reach each other via localhost on the ports that they have exposed, even if those ports aren't exposed externally on the group's IP address.
If you are using localhost  means accessing the services via http://localhost and not via http://publicip.
Obviously, When once container will use the localhost (<IP_ADDRESS>) to access the services from other containers.

So releasing the port only within the container configuration has no effect as long as I don't specify it with ipAdress as well? There should be a warning that the setting has no effect.

In Azure cli, we will explicitly specify ports to open.  For yaml, we can add a note.
@dlepow Add your thoughts for the above question.

But what is the use of port release within the container configuration at all?

We will be having that config in Dockerfile as well.  In ACI there is no effect on the port specified in the container.

Since there is only one address range, a port cannot be occupied by several containers.
Specifying wich ports you want to expose inside IpAdress should be enough, right?

Yes. that should be enough.

Thank you very much for your explanations.
Containers within a group can reach each other via localhost on the ports that they have exposed, even if those ports aren't exposed externally on the group's IP address.
Maybe the sentence can be adjusted to make what is meant clearer.
I had assumed that this sentence meant only the ports specified in the container declaration, also because the YAML reference says on these Container declaration:
"ports: # Exposed ports on the instance".
But what actually as you said has no effect on its own

Specifying wich ports you want to expose inside IpAdress should be enough, right?

Yes.` that should be enough.

At the moment, at least when using YAML, the ports in the container config must be specified as well.
Following ports '8080' in the 'ipAddress' are not used by any container in container group 'port_expose'.

Nice.  I didnt know about that error. Thanks.
@dlepow Please validate the request to enhance the doc

#assign:@dlepow  - Assigning to myself to determine/recommend appropriate doc enhancement. Thanks!

Documentation updated: https://docs.microsoft.com/en-us/azure/container-instances/container-instances-container-groups#networking
Thanks again, @Herr-Sepp
#please-close


Take photo permission bug

I am able to pick a photo from gallery but I am not able to take a picture from camera.
Version 4.0.26 running Android P  on Google Pixel. Also If I add the permission from Settings/Apps the app crash when I take the picture.

Issue seems to be fixed in 4.1.8

@agustinsivoplas We could not reproduce this problem in the newest version of Chat SDK, so we will close this issue. If the issue persists, please re-open it.


chore: fund test suite's account by default in local-test node

Description
Funds account associated with  de97d8624a438121b86a1956544bd72ed68cd69f2c99555b08b1e8c51ffd511c which is used in the test suite. This is done since locally we tend to rely on ci's initial state which should include this account so that some deployment transactions (required for updating contract ids) can be executed.

Deployment failed due to insufficient funds. Please be sure to have enough coins to pay for deployment transaction.

Do we need to add more to the account?


Combat skill level on compound powers cannot be used

Weapons built as compound powers are not using the combat skill levels they are built with. I'm not sure how much of a major issue it would be to fix this, but it would be nice if the CSLs would be included.
The character already has 4 CSLs. Which is what is displayed on the screenshot. However the two from the sword are not being applied. So the total should be 6.

From hero designer you can see the sword has 2 CSLs:

However, the weapon's CSLs are showing on the skills tab. For some reason under weaponsmith:

The box is checked, but the CSLs are not being apply to the attack:

Like I said, I'm not sure how much of an issue this would be to fix, but as a stop gap you could always bring back modifying OCV and DCV for the attack power.

@tthomsen I'm pretty sure I have this fixed.  Mind attaching Rollos.HDC so I can confirm?

Here you go.
Rollos.zip

Let me check on my end. Maybe I'm missing something.

Good to know. For now we can just add them in manually. As always thank you for everything you do.


Cors filter is broken since 2.14

What steps will reproduce the problem?
We have some action responding to the OPTIONS calls.
It is replying with the Access-Control-Allow-Methods set to available verbs. That is required for CORS requests to be done.
What is the expected result?
We see the response header.
What do you get instead?
We have 200 status and no headers.
Additional info
That is caused by a wrong condition in a Cors filter.
https://github.com/yiisoft/yii2/blob/master/framework/filters/Cors.php#L109
We never get our options action running.

Q
A

Yii version
2.15.1

PHP version
7.1

Operating system
Linux

@samdark we had not configured allowed methods
    ...
    'Access-Control-Request-Method' => ['GET', 'PUT', 'DELETE', 'PATCH', 'POST', 'HEAD', 'OPTIONS'],
],

But instead we was sending this headers in the separate OPTIONS action.
Looks everything is working if we add all verbs to the Access-Control-Request-Method param.

That configuration works perfectly for me
        $behaviors['corsFilter'] = [
            'class' => Cors::class,
            'cors' => [
                'Origin' => ArrayHelper::getValue(\Yii::$app->params, 'cors.origin', ['*']),
                'Access-Control-Request-Headers' => ['Authorization', 'Access-Control-Allow-Origin', 'X-Pagination-Total-Count', 'X-Pagination-Page-Count', 'X-Pagination-Current-Page', 'X-Pagination-Per-Page'],
                'Access-Control-Expose-Headers' => ['Authorization', 'X-Pagination-Total-Count', 'X-Pagination-Page-Count', 'X-Pagination-Current-Page', 'X-Pagination-Per-Page'],
            ]
        ];


Add auto release logic to appveyor.yml

Create a new published release on PyPi using Appveyor
on_success:
  - "%PYTHON%\\python.exe -m pip install wheel"
  - "%PYTHON%\\python.exe setup.py bdist_wheel"
  - >
    IF "%APPVEYOR_REPO_BRANCH%" == "master"
    (
    IF "%APPVEYOR_REPO_TAG%" == "true"
    (
    echo SHOULD PUBLISH TO PyPi
    python -m pip install twine &&
    python -m twine upload dist/* --repository-url %REPO% -u %PYPI_USERNAME% -p %PYPI_PASSWORD%
    )
    )

May want to confirm that all Travis CI tests pass as well though


#190: JS API: Expose PropertyEditor

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-14922

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16030


Missing documentation of upgrading Docker@1 to Docker@2

Upgrading v1 tasks to v2 is hard because the documentation of v1 is missing so it's hard to know what the differences are.
E.g. for login going from v1 to v2 you have to remove azureSubscriptionEndpoint and azureContainerRegistry and add containerRegistry, but it's not clear if you have to change parameters. Anyway, the upgrade seems to create a new service connection.

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

ID: 0d9dbf88-7e55-d427-145e-d36b04fb197f
Version Independent ID: a3f30c00-817c-9c05-7a57-3f2bf618821e
Content: Docker task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/docker.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @azooinmyluggage
Microsoft Alias: atulmal

I am facing the same issue. Please make documentation for each version of each task available easily

Still an issue here.

As a work around at least we can target the previous specific version like this<EMAIL_ADDRESS>


[BUG] wmctrl displays an error when running from ssh

Describe the bug
When running macchina in ssh (or et), the error Cannot open display is shown multiple times and the WM data row is still displayed.
To Reproduce
Steps to reproduce the behavior:

Connect to your machine through ssh.
Run macchina.

Expected behavior
No error displayed and WM - row hidden.
Screenshots

System Information

Distribution: Arch Linux, Fedora
Desktop Environment: None
Terminal: ssh
Macchina's version: v0.5.9

Thanks for reporting this!
I'll check this out ASAP :+1:

https://github.com/grtcdr/macchina/commit/2c769066dcaab67d14bc4de1157c4b01d27483f1 should fix this :smile:

Works great, thanks!

I'm gonna try and eliminate duplicate words in machine information, keep an eye out on the repo if you can :+1:


Trouble playing general midi file percussion

Two problems I've run into so far:

The example3 app mapped all channels to 0, whereas GM seems (from my limited understanding) to map channel 10 (index 9 in this library's case) to a special percussion sound set. My understanding is coming from this page: https://www.midi.org/specifications/item/gm-level-1-sound-set
When I manually mapped channel 10 to the right bank/program for my sound font, it seems it wasn't playing just the percussion sound that it should have been. As far as I can tell, it was hitting multiple notes at once - both what sounded like the right crash cymbal (49) and some sort of cowbell sound. This might partly be an artifact of the sound font I was using for testing, which is called GeneralUser GS MuseScore v1.442.sf2

I can provide a sample midi file if that helps. I looked at the binary of the midi in a hex editor with midi template support, and ran the sample code through the debugger. There's no program specification on that channel at all, and no bank switching. It seems the midi file is relying on mapping to the GM standard.
I can just manually map to solve problem 1, but problem 2 I don't fully get how to work around. I tried playing just "note 49" by hard coding it in the sample program, and it still played the extra note.

I tried hacking the region matching code to only match ranges where the top/bottom note exactly matched the played note, and it seemed to play the correct instrument without the extra sounds. I am not sure if this is the right solution or not for a drum patch. I'm also not sure if there's a proper generic way to detect which preset should be used for drums.

I added more special case code for the program switch event, and my second midi track mapped the drums correctly this time. Basically if the channel is 10 (== 9), try loading from bank 128. If it can't find 128 + program num, fall back on looking up 128 + program 0.
It still needs the special case code to only search for a range that maps the key to the key range exactly, but now I've gotten two tracks to seemingly map correctly. Still not sure if this is a correct or foolproof way to do this, just hacking around.

Hi there!
Thank you for the report and the detailed testing.
Turns out the code marked with "that may not be correct" was indeed not correct.
Commit d21c521c2f7fc85b9d490a5852fa05f2994171eb now correctly filters zone regions (aka instrument splits) by key/velocity ranges of parent preset region (aka preset layer).
And then I also committed an update to example3 2e4021b25f023a79c9b53811289c3e975f903533 which should handle the percussion of the 10th MIDI channel (at least most cases I hope).
Though... both changes were done in kind of a hurry so I hope you can test and confirm them a bit more thorough than I just did.
Thanks again!

This is much closer! :) 👍
The percussion channel for one of the midi files I'm using isn't explicitly sending a program change message before it starts playing notes. The sample seems to assume that would be the case. I'm not sure if this is a thing that should be automatically done or not.
After these commits, the only thing I had to do to work around an issue was add this after the sound font loading code to get the instruments to be assigned the way the midi seems to expect: g_MidiChannelPreset[9] = tsf_get_presetindex(g_TinySoundFont, 128, 0);

Yay, good to hear!
Yeah the initial preset setting for the 10th channel is indeed required, I'll add that to the example3 as well.

@kavika13
@schellingb
Sorry this is many years later, but I'm just learning about the GM specs (1 and 2) and trying to figure out how I should make a GM2-compliant synthesizer (well, my aspirations are far less lofty - really I just want to play midi files that I generate which are written in a GM2-compliant way so they play well on other MIDI players tpp - I so have some control over the MIDI files). Maybe I would be happy with GM1-compliant instead. I'm not sure.
Anyway, I was wondering where you got 128==0x80 from? In reading the GM2 spec, it looks like all we need to do is default channel 10 (==9) to the bank 0x7800 and default to preset 0 (where the key->drum mapping is given in the GM1 spec), and all other channels to the bank 0x7900 (where the presets are given by the GM1 spec). Having loaded an allegedly GM2 .sf2 file, I can't see any mention of bank 0x7900 or 0x7800, but I do see drums in bank 0x80, so there must be something about 128==0x80.
I also found this interesting comment about some synthesizers sneakily mapping bank 0x80 from the soundfont to bank 0x7800, so that they remain GM2 compliant.
Perhaps we're not trying to be GM2 compliant, but instead GM1 compliant. The GM1 spec doesn't talk about banks, so I reckon it doesn't expect them to be configurable. I didn't see anywhere where mentioned the bank 0x80==128 though. Do you know where this standard came from?
Reading a little more, it sounds like maybe this is an .sf2 convention? Which means that .sf2 is not compatible with GM2 since 0x80 != 0x7800 (or at least it requires the synthesizer to do the mapping from the comment I linked above, so that any bank select messages from a GM2 MIDI file talking about 0x7800 get mapped to 0x80).
This is all very confusing, sorry for not being very coherent here. This is just me trying to figure something out by asking as many people as possible!

SoundFont banks only support an 8 bit bank field, with banks of 0-127 being instrument banks, and bank 128 being the drum bank. Anything else is non-standard.

Ok, that makes sense, thanks. I find it odd that in none of the specs is there a well defined mapping between the Midi version of a bank (0x0000 to 0xFFFF) and the soundfont version of the bank (0-128). It's just left to the synthesiser to guess.


Issues with slimmed image

This ticket collects all issues originating from removing "developer stuff" from the ISO.
Apparently some "developer stuff" is required for the operation of FreeBSD by "mere mortals" who do not even know what a compiler is:

[ ] libLLVM-12.so needed for swrast_dri.so

libEGL warning: DRI2: failed to authenticate
libEGL warning: MESA-LOADER: failed to open swrast: Shared object "libLLVM-12.so" not found, required by "swrast_dri.so" (search paths /usr/local/lib/dri)

Unfortunately, this is a 87 MB file. Is there any way around this?

Let's see if things improve with https://github.com/helloSystem/ISO/commit/e26134cfef0f416cdba456b756cf53edfdd8b109

One idea to create the separate user and developer filesystem trees:

Write a developer.exclude list that contains fnmatch(3) search patterns for the developer files
Use mtree(8) to generate a spec file
Use the spec file when generating the filesystem image with makefs(8)[https://www.freebsd.org/cgi/man.cgi?makefs]

There we have it - no copying around of trees, no deleting of files from the trees.
Seems like the BSD people have thought of everything you might need when putting together systems. :+1:

Say this is our excludelist:
# If the pattern contains a `/' character,
# it will be matched against entire pathnames (relative
# to the starting directory); otherwise, it will be
# matched against basenames only

doc
docs
*.la
man
/usr/include
/usr/local/include
*.h
.cache
debug
*.a
*.o
src
git-core
git
devhelp
*-doc
examples
/usr/bin/svn*
/usr/bin/clang*
/usr/bin/c++
/usr/bin/cpp
/usr/bin/cc
/usr//bin/lldb*
/usr/local/bin/ccxxmake
/usr/bin/llvm*
/usr/bin/ld.lld
/usr/bin/ex
/usr/bin/nex
/usr/bin/nvi
/usr/bin/vi
/usr/bin/view

# TODO: Delete /usr/local/llvm* EXCEPT for 'libLLVM-*.so*'
# Must not delete libLLVM-12.so which is needed for swrast_dri.so
# TODO: Translate the following to a fnmatch(3) pattern

Then we can create the spec file with:
cd /usr/local/furybsd/uzip/
mtree -c -X ~/helloSystem/ISO/testdir.exclude > ~/helloSystem/ISO/spec

Now, how can we get the exact reverse of the excluded files? We would need to use what is in the spec file as an excludelist. Can it be converted into that format?

Another approach:

Create a snapsot
find /usr/local/furybsd/uzip/ > all.files
Delete the developer files (as we do now)
find /usr/local/furybsd/uzip/ -type f -or -type s > user.files
Create and upload user.iso
Restore snapshotted state
Delete the files in user.files

Create and upload developer.iso

The following should work:

create a manifest and convert it to 1-liner format
add a comment to the developer files in the manifest using regex (sed)
copy manifest 2x
leave only the marked lines in the developer manifest
in the user manifest leave only the unmarked lines

mtree -p /usr/local/furybsd/uzip/ -c > spec
mtree -C -f spec > spec.developer
sed -i '' -e 's|^\./usr/include/.*|& # developer|' spec.developer

This has been implemented in https://github.com/helloSystem/ISO/commit/bee4d65479bafbabb7b3266a6b864d3e71ace37d


chore: release 0.48.1

Related issue
# followed by the number of the issue
Summary
Notes
Please check if the PR fulfills these requirements

[ ] If necessary, the changelog has been updated
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] The commit message follows the conventional commit specification
For any breaking changes, companion PRs have been opened on the following repositories:

[ ] substra-tests
[ ] substrafl
[ ] substra-documentation

I think we want to update substra-tools deps to enforce the new version of the docker images

Missed that it was a dev dependency, but actually asked myself how it was enforced. Should I just do:
            "substratools>=0.21.0",

In extra_requires?


docs: create docs with docusaurus

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a9993a2). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #23   +/-   ##
=========================================
  Coverage          ?   76.84%
  Complexity        ?       31
=========================================
  Files             ?        7
  Lines             ?       95
  Branches          ?        1
=========================================
  Hits              ?       73
  Misses            ?       22
  Partials          ?        0

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


CNI config docs are out of date

Missing at least the hostname field: https://github.com/projectcalico/cni-plugin/blob/master/utils/types.go#L56
This issue covers ensuring that the docs are updated to cover all supported fields.

CC @djosborne


Covid stats in javascript

Description
Hi i want to make a code to show covid stats in a country. This code will need a country code as an input and will return covid stats in the country.
Technologies and Languages
covid api & javascript
Aditional Work

Hi can i assigned for this


Consider new API for deploy

Current deployIfDifferent function accepts quite a few arguments and it can be confusing to new users of this plugin. Here is the source of the function I had to look at in order to understand what the function calls actually mean.
source: https://github.com/wighawag/buidler-deploy/blob/177e8c1ac598180c5b827adcbec274a65d3bd4ca/src/utils/eth.js#L225-L233
The current example usage in the README is the following (reformatted with Prettier):
const deployResult = await deployIfDifferent(
  ["data"],
  "GenericMetaTxProcessor",
  { from: deployer, gas: 4000000 },
  "GenericMetaTxProcessor"
);

const deployResult = await deployIfDifferent(
  "data",
  "Token",
  { from: deployer },
  "Token"
);

const deployResult = await deployIfDifferent(
  "data",
  "ERC721BidSale",
  { from: deployer },
  "ERC721BidSale",
  Token.address,
  1,
  3600
);

Using Named Parameters
At first glance, this code doesn't really tell you what is going on (unless you are already very familiar with the API). I suggest we used named parameters as it is a lot more explicit and actually quite flexible if you wish to add or remove features later on.
For example (along with my suggestion from #6):
const deployResult = await deploy({
  name: "GenericMetaTxProcessor",
  contractName: "GenericMetaTxProcessor",
  fieldsToCompare: ["data"],
  options: { from: deployer, gas: 4000000 }
});

const deployResult = await deploy({
  name: "Token",
  contractName: "Token",
  fieldsToCompare: "data",
  options: { from: deployer }
});

const deployResult = await deploy({
  name: "ERC721BidSale",
  contractName: "ERC721BidSale",
  fieldsToCompare: "data",
  options: { from: deployer },
  args: [Token.address, 1, 3600]
});

Further Refinement
A further refinement could be to:

Assume a default value for fieldsToCompare to be data.
Assume contractName to be the same as name (can specify if it's not the case)
In-line the options object

This would lead to:
const deployResult = await deploy({
  name: "GenericMetaTxProcessor",
  from: deployer,
  gas: 4000000,
});

const deployResult = await deploy({
  name: "Token",
  from: deployer,
});

const deployResult = await deploy({
  name: "ERC721BidSale",
  args: [Token.address, 1, 3600],
  from: deployer,
});

Conclusion
This is just to spark some discussion, I hope this has been useful. I think simplifying the API for end-users is an important step of getting adoption.

Hi @adrianmcli thanks so much for the detailed feedback. I agree completely, this make a better api. Going to implement these.
I am going to rethink the other api too.

Will consider renaming deployIfDifferent to deploy as part of this issue.

I had a deeper look and I am gonna go with a slightly different signature :
deploy(name: string, options: DeployOptions, ...args: unknown[]): Promise<DeployResult>;

where DeployOptions is
    from: string;
    contractName?: string,
    fieldsToCompare?: string | string[],
    linkedData?: any; // JSONable ?

This is to keep the name as the first param for all deployment related function and to keep args as variadic.
This is almost like before except for the contractName btu I think it is quite self explanatory. what do you think ?

👍 on having the name parameter first.
Having options last is a very common pattern, so I am worried about having it first. But having options last can also be confusing because every contract can have different number of params. Both can be problematic (see below).
I want to suggest a third alternative where the args are part of the options object. Let's list out examples for each three alternative and see which one "feels" best:
1. Args first
deploy(name: string, options: DeployOptions, ...args: unknown[]): Promise<DeployResult>;

const deployResult = await deploy("ERC721BidSale", Token.address, 1, 3600, {
  from: deployer,
});

At first glance this looks fine, but when run through a formatter, it can look pretty ugly and unreadable because the contract name blends in with the args:
const deployResult = await deploy(
  "ERC721BidSale",
  Token.address,
  1,
  3600,
  { from: deployer }
);

2. Options first
const deployResult = await deploy(
  "ERC721BidSale",
  { from: deployer },
  Token.address,
  1,
  3600
);

But if you don't have any options object to pass, you will have to pass an empty object literal which can look really strange and requires extra work on the user:
const deployResult = await deploy("ERC721BidSale", {}, Token.address, 1, 3600);

3. In-line args (my suggestion)
So far, I think this is the most readable.
const deployResult = await deploy("ERC721BidSale", {
  args: [Token.address, 1, 3600],
  from: deployer,
});

The benefit of this approach is that even when run through a formatter with large number of params, you can still clearly see which are the args:
const deployResult = await deploy("ERC721BidSale", {
  args: [
    Token.address,
    12345,
    360000,
    someOtherVar,
    andAnotherVar,
    andEvenOneMoreVar,
  ],
  from: deployer,
});

@wighawag thoughts?

Yes, I considered adding options last but do not like that. and prefer option first
regarding 2. Note that  const deployResult = await deploy("ERC721BidSale", {}, Token.address, 1, 3600); is not valid as you always need to specify the address that will deploy, so the empty {} will not happen
Now I am not sure we should consider formatter to drive our API design.
Plus this is quite easy to read too:
const deployResult = await deploy(
   "ERC721BidSale",
    {
      from: deployer,
    },
    Token.address,
    12345,
    360000,
    someOtherVar,
    andAnotherVar,
    andEvenOneMoreVar,
});

Technically we could support both. like we can detect if args is supplied as part of the options and if not fallback on the variadic argument. Like this we have both but not sure if this a good idea ?

🤔🤔🤔
You make a good point, you're right it doesn't look too bad. I guess I just enjoy the args as part of options because it feels cleaner to me and I am always very wary of variadic arguments because it feels like it introduces uncertainty.
I want to have the choice of both, but I also agree it might be weird to support two ways. I'm not sure what the best way forward is. Maybe we should ask @alcuadrado and other people on the Buidler Telegram group to take a quick poll?

closing it as it has now been implemented in v0.4.0


When will support for canceling a request be available?

For example:
$connection->query('SELECT count(*) FROM users', new TimeoutCancellation(600));

So far I've not found this to be necessary. Cancelling insert/update/delete queries isn't very practical. Unbuffered select queries can be effectively cancelled by not consuming the entire result set. There is the initial round-trip time to the server where a select query could be cancelled, but would require interface changes in this library as well amphp/sql and amphp/sql-common, which would affect amphp/mysql as well. I'd have to investigate if query cancellation is possible there, or if the connection would just need to be closed.

You can use pg_cancel_query.
This is necessary, for example, when an HTTP request arrived and it was closed due to a timeout. In this case, the backend does not need to continue to wait for a response from the database; it needs to cancel the request using the database. This immediately reduces the extra load on the database, for example during DDOS attacks. Or when the database is overloaded, there is no point in loading it with more queries, the answers to which no one needs anymore.

I understand there may be some advantage, particular with buffered select queries. I would be open to implementing this in the future, but first will require some investigation as the best way to go about it. As I mentioned in my prior comment, full support would either 1) require modifying the common components supplied by amphp/sql-common and adding support in amphp/mysql (which I believe requires a second connection to kill a query on the first connection); or 2) not using some common components in amphp/sql-common.


Ohhhh jeeee: ... this is a bug (sexp.c:1340:vsexp_sscan)

Receive this error upon first scan (just did the quick scan).

Can you provide more context and a full trace?

Please feel free to reopen if you can provide more details.


[Theme-request] winter is coming

Describe your request
Hey guys, I really like the Winter is Coming themes, both the dark and the light variant. I would like to port these to Doom Emacs but I have no idea how to get started.
If I get a few pointers I might be able to create the PR myself. Otherwise - would anyone else care to do it?
Briefly explain its use-case
n/a

(I moved this to doomemacs/themes, since that is our themes repo.)
I'm assuming you're referring to this Winter is Coming theme? I'll welcome a PR for it.

a few pointers

Copy themes/doom-one-theme.el to themes/doom-winter-is-coming-theme.el,
Edit the metadata in the header comment,
Rename all references to doom-one to doom-winter-is-coming,
Adjust the faces accordingly.

By convention, our themes avoid the following:

Setting :fonts or :inheriting from variable-pitch, fixed-pitch, or derivative font faces.
Setting :heights for faces. E.g. org-level-N faces.

Hope that helps!

I put it under ~/.doom.d/themes but I honestly can't even figure out how to load it. How can I load the theme after I created the file so I can test the colors?

Just as a follow-up, I can't really get it to look good. I'm attaching the theme as it is if someone wants to work on it. I don't have the competence for this.
https://pastebin.com/uKewkm5Z

@hlissner how can I assign styles to certain parts of the theme, e.g.,
             (keywords       (cyan :weight "bold))


feat: add rules ks-admission-general-block-nodeport-services&ks-admission-general-container-resource-limits

feat: add rules ks-admission-general-block-nodeport-services&ks-admission-general-container-resource-limits

Forgot to pull first, my fault. I will open a new pr after pulling


[Feature]: Crown for top three in leaderboard

Fixes #248

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊


少了一个参数

loss = fed_single_update(model,doc_encoder,user_encoder,num,get_user_data,train_uid_table)

Thank you for your attention on our work. Could provide more details on this issue?

函数调用要7个参数，你只传了六个

I have locally checked my code with VSCode and did not find the issue mentioned by you. Could you provide more details such as error logs?


Custom Size Icon

Icon Request

Icon name: custom size
Tags of this icon: custom width and hight, custom size
Screenshots of similar icons:

Hey bro,
https://remixicon.com/icon/custom-size


Fix problem that unable to get notebook filename on JupyterLab 3.0

What this PR does / why we need it:
The notebookapp has been changed from JupyterLab 3.0 to serverapp, so the list of servers is not returned.
So if there is a Jupiter_server module, I changed it to get the list of servers from serverapp.
Which issue(s) this PR fixes
Fixes #551
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

Fixed to return notebook filename on JupyterLab 3.0

@googlebot I fixed it.


Correcting Optional Route Parameter Syntax

According to the upgrade path, ?/:p? is the correct syntax for optional route parameters, not (/:p). Anyway I tried both ways by fiddling with the examples and only the first one worked.

The latter syntax is supported in 1.0. The former in 0.13. You were probably reading the docs for 1.0 and running 0.13.


Very Slow with 1600 Keywords

Hello, the GUI becomes very unresponsive after adding 1600 keywords to a website. Might want to add pagination to this, not sure.
When loading into a website to check on those serps it is very very unresponsive with that many keywords
Has anyone else had this issue?

Try the latest version. The issue should be fixed.


Bluetooth: ISO: Fix build on native_posix_64 with debug

On native_posix_64 we get the following compile error in CI:
error: format %u expects argument of type unsigned int
Fix by using %zu instead of %u as type is of size_t.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

@galak Duplicate of https://github.com/zephyrproject-rtos/zephyr/pull/38210


Fix build problems on nRF target

@arturkow2000 LGTM.
Please create new tag on master after merging.

Tag v0.2.4 pushed


Update dependencies for the project

Bump framework versions and grade to the actual state.

also when merged we need to update the dependabot PRs

make sure to build our internal project with these changes, verify compatibility.

Yes, did it before PR

Final changes tested also for all architectures


make phn2annot case insensitive, fix #68

change phn2annot function so that it checks
for both .wav and .WAV files when
opening the file to determine the sampling rate,
which it does to convert samples to seconds
for onsets and offsets
fixes bug on some versions of TIMIT dataset
where audio files end in .WAV instead of .wav

closing this, cherry-picked the commits into another branch where I'm fixing another issue since they both need to be fixed for tests to pass

closing this, cherry-picked the commits into another branch where I'm fixing another issue since they both need to be fixed for tests to pass


Feature request: Adding support for telescope.

Is there any plans for adding the option to choose between Telescope and FZF ?
At the moment, Telescope seems to be the most extensible fuzzy finder (and in consequence, probably the best one), it is written entirely in lua (unlike the FZF plugin for vim) and it has become the most popular fuzzy finder for users moving their configuration over to lua,  and those users usually only want lua plugins.
It just makes sense adding support for telescope. How difficult would it be to implement ? Both plugins are written in lua so maybe that would make it a little bit easier.

Hi,
I think there's a misunderstanding here about the goal of this plugin. This plugin is to allow people who are happy with FZF, want to keep using it and want to use FZF to navigate the built-in LSP client results.
If you're not in this case, you should use Telescope which comes with full support for the LSP client already (unlike FZF) and you can totally ignore this plugin :)

you should use Telescope which comes with full support for the LSP client already

My bad, I didn't know Telescope already has full LSP support. I was having issues with LSP when looking for references because of the way buffers  are handled, so I was looking for a better solution.
You're absolutely right, it makes no sense supporting Telescope if it already LSP builtin.
Thanks for mentioning that, if you wouldn't have say that I'd be still looking for a solution.


Install and use a reverse proxy for staging devfile registry

What type of PR is this:
/kind feature
Installs a reverse proxy based on nginx to cache the requests to https://registry.stage.devfile.io
Limits the requests by User-Agent
I didn't find a way to configure the Load Balancer for nginx to see the original IP address of the client andd filter on this IP (the only IP nginx is seeing is the IP address of the load balancer)
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #5920
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

How to test changes / Special notes to the reviewer:

@anandrkskd Can you take a look at this?

/approve
The OpenShift tests pass on prow.

/override ci/prow/unit-and-validate-test

/retest

/test v4.10-integration-e2e

/test v4.10-integration-e2e

Do we need this when the same tests on IBM Cloud have passed? Also, has the issue with unit and 4.10 integration tests on prow been completely addressed, that is, are they reliable again?


Replace the "OPTIONAL" entity qualifier with "CONDITIONAL" where appropriate

As was discussed while clarifying that session labels are REQUIRED in some cases (https://github.com/bids-standard/bids-specification/pull/532), thus not exactly OPTIONAL as defined in rfc2119 ("truly optional"), it appears this is the case for many other (most?) OPTIONAL entities in the entities table.
We could therefore mark them as being CONDITIONAL instead.
While this table is being modified to be machine readable (https://github.com/bids-standard/bids-specification/pull/475), I think it would be ideal to add a link to the section where the specific conditions are described for each entity, if possible.

I agree that it'd be nice to have a solution for the "conditionally optional" as opposed to "truly optional" cases.
Personally, I think it could be a nice idea to extend rfc2119 to include one more definition for that reason (the CONDITIONAL you propose).
However, @effigies recently uttered a contrary opinion.


Unified Interface protocol & Removed unnecesary exceptions.

systemImplementing:, unresolvedSystemDependencyTo: now expect an interface name (#TimeSystem).
SystemImplementationNotFound & SystemInterfaceNotFound removed and replacer with Error with a proper description.

Coverage remained the same at 100.0% when pulling 6faf34f954e5dae3b72755e2a5ea2f2387809b92 on enhancement#48 into d43a139911a8bcc9c79d9cf64e4fb58c1392d459 on master.


KAFKA-7763: commitTransaction and abortTransaction should not wait endless when brokers are down

Currently, commitTransaction and abortTransaction invoke Latch#await to wait for the request completion. When brokers are not available, these calls await forever and producer never ends. This fix replaces it with the timed equivalent await(timeout, unit). When timeout occurred, producer throws a TimeoutException.
More detailed description of your change,
if necessary. The PR title and PR message become
the squashed commit message, so use a separate
comment to ping reviewers.
Summary of testing strategy (including rationale)
for the feature or bug fix. Unit and/or integration
tests are expected for any behaviour change and
system tests should be considered for larger changes.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

retest this please

retest this please

retest this please

@guozhangwang shall we file a JIRA to make sure we follow up?

retest this please

retest this please

Thanks @huxihx. Merging to trunk.


Accept an object to the arg of wrapper class

Accept an object to change a class dynamically
For example:
<template>
  <tags-input
    :wrapper-class="{'invalid': isValid}"
  >
...
</template>

<script>
...
const isValid = () => {
  ....
}
</script>

note:

Strings are also possible as before

You can also do this just using :class and using your own CSS:
  <tags-input
    :class="{'is-invalid': !isValid}"
  >

    border: 1px solid $danger !important;
}```

Thx, that is easier and better


Inputs break all component slots except default

Reproduction
https://stackblitz.com/edit/nuxt-starter-uqs28w?file=app.vue
Describe the bug
Using <FormKit type="..." /> in a component with slots breaks all slots except default. This bug only occurs if the component with slots is the root of the template of another component:
<template>
  <ExampleLayout>
    <!-- this slot does not work -->
    <template #title> Some Title </template>

    <!-- commenting out this line makes the slot above work again -->
    <FormKit type="text" />
  </ExampleLayout>
</template>

This is probably caused by unplugin-formkit.
Environment
• OS: macos
• Browser: chrome

I was working with the same bug yesterday and I found that if you wrap the content of app.vue in a div it starts working.
I thing there is a bug in Vue or Nuxt but I'm not so sure.
<template>
	<div>
		<ExampleLayout>
			<template #title> Some Title </template>

			<FormKit type="text" />
		</ExampleLayout>
	</div>
</template>`

Yeah, this is silly of us. We used to inject a lazy provider to check for a suspense boundary, but that is no longer necessary. We should just inject useConfig instead. I’m going to close this issue in favor of formkit/unplugin-formkit#7.
Thanks for the report ❤


google-pub-sub-grpc, google-cloud-bigquery-storage: Bump pubsub protos and protobuf-java dep

These protos were a couple years old, and so if you happen to also include newer GCP Java libs on your classpath, you can easily get conflicts between the class files generated by Pekko Connectors and those. This version is not quite the newest... unfortunately any newer version gives the following error which I'm disinclined to troubleshoot right now:
[error] /Users/dvangeest/projects/incubator-pekko-connectors/google-cloud-pub-sub-grpc/target/scala-2.13/pekko-grpc/main/com/google/protobuf/descriptor/FeatureSet.scala:301:21: illegal cyclic reference involving type EnumType
[error]     type EnumType = EnumType
[error]                     ^
[error] one error found

Also, depending on protobuf-java seems unnecessary?

Hmm sorry about that, was too hasty. Would it make sense to bump protobuf-java then, and also add the Runtime scope to make it more clear it's not required for compile?

I can look at this in more detail later. So far, we have been conservative when upgrading dependencies. Any changes so far have been to lower the number of dependencies with CVEs. We tend to make more people unhappy with significant upgrades. In the end, each connector is pretty small code wise. Users can take our code and adjust it to suit their own needs.
If you can provide a test case where it is proven that there is an issue that can affect most users, it will improve the chances that we will make changes.

Thanks, I appreciate it. The main trouble we hit is when mixing Connectors libs with up-to-date GCP Java libs on the same classpath.  A test case would be tricky, because certain clients need to be on the class path at specific versions to produce a runtime error.
The particular thing we hit was this (omitted irrelevant parts of the trace):
com.google.api.gax.rpc.ApiException:
	at com.google.cloud.pubsublite.internal.CheckedApiException.<init>(CheckedApiException.java:51)
	at com.google.cloud.pubsublite.internal.CheckedApiException.<init>(CheckedApiException.java:55)
	at com.google.cloud.pubsublite.internal.ExtractStatus.toCanonical(ExtractStatus.java:53)
	at com.google.cloud.pubsublite.cloudpubsub.PublisherSettings.getAdminClient(PublisherSettings.java:238)
	at com.google.cloud.pubsublite.cloudpubsub.PublisherSettings.instantiate(PublisherSettings.java:260)
	at com.google.cloud.pubsublite.cloudpubsub.Publisher.create(Publisher.java:27)
....
Caused by: java.lang.NoSuchMethodError: 'com.google.longrunning.OperationsClient com.google.longrunning.OperationsClient.create(com.google.longrunning.stub.OperationsStub)'
	at com.google.cloud.pubsublite.v1.AdminServiceClient.<init>(AdminServiceClient.java:188)
	at com.google.cloud.pubsublite.v1.AdminServiceClient.create(AdminServiceClient.java:169)
	at com.google.cloud.pubsublite.cloudpubsub.PublisherSettings.getAdminClient(PublisherSettings.java:230)

This was with "com.google.cloud" % "google-cloud-pubsublite" % "1.12.17" on the classpath.
I did actually wonder about tackling this by shading the GCP/proto/gRPC deps in the Connectors lib. Not something I have a ton of experience with, and I believe it's somewhat of an unsolved problem in Scala, but I did manage to get something going with sbt-shaded. Didn't really have time to test it out yet and was unsure if this approach would be acceptable... in particular I was unsure how far I should go with the shading. Any thoughts on that approach?

I was trying to suggest you copy paste the code that you need, inline it and compile it with your favourite jar dependencies. gRPC is in the same ballpark as Hadoop in terms of the number of dependencies it brings and the minefield of managing that when you have other dependencies that bring clashing version requirements.

Yep, got it. Definitely something we can consider. Was trying to be a good open-source citizen but understand that it's hard to balance the needs of many different users.

I can look at this in more detail later. So far, we have been conservative when upgrading dependencies. Any changes so far have been to lower the number of dependencies with CVEs. We tend to make more people unhappy with significant upgrades. In the end, each connector is pretty small code wise. Users can take our code and adjust it to suit their own needs.
If you can provide a test case where it is proven that there is an issue that can affect most users, it will improve the chances that we will make changes.

Even if it is a valid issue, I still think such a significant change should be marked for pekko connectors 1.1.x, although nothing is stopping us from creating a 1.1.x branch and even a milestone if it helps


[WHOOP] ... Error loading Biometrics in Raycast

Extension
https://www.raycast.com/josha1len/whoop
Description
Error:
RangeError: Invalid time value

yne:biometrics.tsx:19:2

---
16: import { WhoopColor } from "./helpers/constants"

### Steps To Reproduce

Open raycast
Launch Biometrics

### Current Behaviour

Error when loading biometrics

### Expected Behaviour

See biometrics

Hey @connerdrew, thanks for reporting. A potential fix has been approved here. Please could you update the WHOOP extension and retry viewing your biometrics?

@raycastbot close this issue


Pass real WorkflowId and RunId for full replay exposed to users in Worker#replayWorkflowExecution

Actual Behavior
Currently during a full replay that is explicitly exposed to users using Worker#replayWorkflowExecution, JavaSDK supplies fake WorkflowId and RunID which can break determinism if workflow code depends on these values.
Expected Behavior
Actual values from the history should be taken and supplied to the Workflow in WorkflowInfo during replay.
Additional context
https://community.temporal.io/t/recommended-approach-to-testing-backwards-compatibility/5511

The workflow code must not depend on runId as reset operation changes it.

@mfateev Fair, good catch on runId. I will add this comment on WorkflowInfo#getRunId javadoc, because I don't think we state this unobvious fact anywhere.

We should consider putting run_id in unsafe (might be too late though), the only issue is that the current run_id isn't stored in history so we can't provide it to the replayer, we only have original_run_id in WorkflowExecutionStarted which is the closest thing.

There is originalRunId that is preserved on reset.

Addressed by #1497


3.2.4 is broken for docker (at least on Travis)

Issue Type

Bug report

Molecule and Ansible details
Ansible 3.0 with Molecule 3.2.4
Ansible and Molecule installation method:
pip3 install molecule[lint,docker]

Detail any linters or test runners used:
Desired Behavior
Travis CI job that worked yesterday with 3.2.3 should work.
Actual Behaviour
As of this morning all CI jobs with molecule are failing on Travis. The breakage happened when 3.2.4 appeared. Reverting to 3.2.3 fixes it. I'm still debugging but it's hard to iterate usefully on Travis :(
INFO     Sanity checks: 'docker'
ERROR! couldn't resolve module/action 'docker_container'. This often indicates a misspelling, missing collection, or incorrect module path.
The error appears to be in '/home/travis/virtualenv/python3.8.3/lib/python3.8/site-packages/molecule_docker/playbooks/destroy.yml': line 8, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
  tasks:
    - name: Destroy molecule instance(s)
      ^ here

Results after change to pip3 install molecule[lint,docker]==3.2.3
default > destroy
INFO     Sanity checks: 'docker'
PLAY [Destroy] *****************************************************************
TASK [Destroy molecule instance(s)] ********************************************
changed: [localhost] => (item=ubuntu_2004_js_env)

[ch197666]

Also, changing to ansible-lint 5.x is going to break a number of people. Why was this a patch release?

Can you share your travis logs?
FWIW I ran a molecule test just recently and didn't have a problem with molecule 3.2.4.
https://github.com/aminvakil/ansible-role-docker-installation/runs/2124376202?check_suite_focus=true#step:4:10

Can you share your travis logs?

Private repo so not the entire log. What are you looking for? It doesn't get very far so...
$ pip3 install molecule[lint,docker]
Collecting molecule[docker,lint]
  Downloading molecule-3.2.4-py3-none-any.whl (238 kB)
Collecting enrich>=1.2.5
  Downloading enrich-1.2.6-py3-none-any.whl (8.6 kB)
Collecting paramiko<3,>=2.5.0
  Downloading paramiko-2.7.2-py2.py3-none-any.whl (206 kB)

.... etc, pretty base 20.04 ubuntu builtin python 3.8
$ cd roles/js_env && molecule test
INFO     default scenario test matrix: dependency, lint, cleanup, destroy, syntax, create, prepare, converge, idempotence, side_effect, verify, cleanup, destroy
INFO     Running default > dependency
default > dependency
WARNING  Skipping, missing the requirements file.
WARNING  Skipping, missing the requirements file.
INFO     Running default > lint
default > lint
COMMAND: set -e
yamllint .
ansible-lint
flake8
./handlers/main.yml
  2:27      error    no new line character at the end of file  (new-line-at-end-of-file)
./tasks/ubuntu.yml
  10:18     error    too few spaces after comma  (commas)
./tasks/install_nvm.yml
  22:1      warning  comment not indented like content  (comments-indentation)
CRITICAL Lint failed with error code 1
WARNING  An error occurred during the test sequence action: 'lint'. Cleaning up.
INFO     Running default > cleanup
default > cleanup
WARNING  Skipping, cleanup playbook not configured.
INFO     Running default > destroy
default > destroy
INFO     Sanity checks: 'docker'
ERROR! couldn't resolve module/action 'docker_container'. This often indicates a misspelling, missing collection, or incorrect module path.
The error appears to be in '/home/travis/virtualenv/python3.8.3/lib/python3.8/site-packages/molecule_docker/playbooks/destroy.yml': line 8, column 7, but may
be elsewhere in the file depending on the exact syntax problem.
The offending line appears to be:
  tasks:
    - name: Destroy molecule instance(s)
      ^ here
CRITICAL Ansible return code was 4, command was: ansible-playbook --inventory /home/travis/.cache/molecule/js_env/default/inventory --skip-tags molecule-notest,notest /home/travis/virtualenv/python3.8.3/lib/python3.8/site-packages/molecule_docker/playbooks/destroy.yml

Locking the version to 3.2.3 solves the problem fully.
The other PR isn't relevant since it was using Ansible 3.1.0 which includes the necessary community modules.
$ ansible-galaxy collection list |grep -e docker -e general
community.docker              1.3.0
community.general             2.2.0

Using 3.0 also covers that.
$ ansible-galaxy collection list |grep -e docker -e general
community.docker              1.2.2
community.general             2.0.1

This is not a bug, please use discussions in the future instead of the issue tracker. Installing ansible itself is outside the scope of molecule cli.

This is not a bug, please use discussions in the future instead of the issue tracker. Installing ansible itself is outside the scope of molecule cli.

I'm sorry, but on what basis do you make this claim that it's not a bug. It runs in previous version, it fails in the new version. The one and only response to this issue referred to issues with older modules, which I showed to be unrelated as we're using the newer modules.
If you have some justification for calling this not a bug, then please present that.  Closing a repeatable issue with a clear replication state as "not a bug" without any justification isn't very helpful.
ALSO - you didn't reference the semver failure in introducing a major new version with different requirements in a patchfix version.

So I've discovered the problem. Ansible was installed in the system python, molecule was being installed in user space.
sudo pip3 install ansible
pip3 install molecule[lint,docker]

This used to work in 3.2.3, and stopped working in 3.2.4. Workaround is:
sudo pip3 install ansible
sudo pip3 install molecule[lint,docker]

I fail to understand why molecule will not run from a user-space installation, and why this behavior change was pushed out in a patchfix release?


How to point to local compiler for testing

Hi Josh,
recently at Apache Royale we added more compiler enhacements to support Flex MX RemoteObject (I'm talking about mx:methods, mx:arguments, symbol).
Right now as3&mxml extension complains from "sysmbol" tag and from some bindings to operation.
I think the extension points to official compiler, I would like to point to local one for testing purposes, could you give guidance if this is possible and where I should look to try in a local build?
Thanks in advance for your help

https://github.com/BowlerHatLLC/vscode-nextgenas/wiki/Extension-settings#as3mxmlsdkeditor

Thanks josh :)


Format of Personal Defined Dataset for Evaluation

Hi developers,
I am wondering, if there's an instruction on how to create a self-defined eval dataset, like what the format should be, which could be executed by the lm_eval_harness ?
Thanks for your help ~

Hi! in our documentation we provide a description of how to add and define a new task.
For your own dataset, the only precondition is that you turn this into a Hugging Face dataset loadable with the datasets library—then in your task definition you can use all the column values.


Return Organizations as an ordered list

http://civictechindex.org/contributors/all displays organizations as nested sets of orgs (Root -> parent -> children). This will be easier if we return the organizations in a data structure that already has that in place.

This is now available on my org-tag branch. I suspect we will need to make some frontend changes when this gets rolled out so we should coordinate how we want to to do that. One option might be to deploy the new code to AWS and have people switch to using that endpoint for development until we can switch the entire app to use the new code.
The primary driver for this change was that the /api/organizations/ endpoint is very slow. It really isn't any faster after this change to use a more performant tree structure in the database. The major slow down is serializing all the links. I would like to explore not returning the links when returning the entire list of orgs. If some of our pages do need the links, then another option we should explore is getting rid of the separate links table and put the links in columns in the organizations table. Anyone want to experiment with doing that? I can coach you but don't have time to do this all myself.

This is deployed to AWS now


Defined new revisions for golang dep: github.com/prometheus-junkyard/tsdb

Ran component through the scanners since I noticed it had not been harvested yet and it correctly declared the license. Closing PR as it is no longer needed.


Excluding directory does not exclude submenu

If you exclude a directory, it's pages will still show up on the heading 1 right menu on the print page.

I am experiencing the same issue, is there a workaround for this?


Install the OMS Dependency agent on Linux is not working

[Install the OMS Dependency agent on Linux is not working}
https://docs.microsoft.com/en-us/azure/azure-monitor/vm/vminsights-enable-hybrid#dependency-agent,
In docs it is showing <IP_ADDRESS>00 version, but link is downloading <IP_ADDRESS>30 version with below URLs, and <IP_ADDRESS>30 is a corrupted version as per error message. Can you fix it ASAP, or provide url to download older version , it is effecting a large audience worldwide.

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

ID: ea7aad71-a30a-452a-b06f-18da91d41565
Version Independent ID: d7db47e0-c5ca-1f2f-45ba-c820c3b62ed7
Content: Enable Azure Monitor for a hybrid environment - Azure Monitor
Content Source: articles/azure-monitor/vm/vminsights-enable-hybrid.md
Service: azure-monitor
Sub-service: virtual-machines
GitHub Login: @bwren
Microsoft Alias: bwren

Thanks for bringing this to our attention. We will investigate it further and update you shortly.

@akn9050 - I have reached out to Product team and awaiting their response. I will keep you posted as soon as I hear back from them. Thank you for your patience.

@akn9050 - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Improvements json query and log level

Maybe, you should use PATCH method substitute as PUT event because it doesn't create new object in database but it changed some value with existed.
70# api.Put("/alert", handlers.UpdateAlert)

Dose it can use like following code?
70# api.Patch("/alert", handlers.UpdateAlert)

Yes, You can use PATCH instead of PUT
And for clear

POST is used to add a new item
PUT used to update an item (PUT also be idempotem, check this)
PATCH like a put but in partial update (some field of item that is why called PATCH)

Metrics from Graylog always send in full format and we replace the data into the old item or create a new one if not exist in the database.
IMO, In the first design, It should use PUT because we have updated the item like replace.
BUT After some research It should use POST because the above behaviors (Also check this)

Next, Can you move dashboard feature in new PR? and add new variable for enable or disable this feature.

I thought No because of a lot of improvements It takes much effort to do it (My bad) But I will add an environment variable to disable the dashboard.


ci: skip rbd command in ci

until we fix the rbd hang command issue let's skip this in CI so that other PR's CI goes to running.

Description of your changes:
Which issue is resolved by this Pull Request:
Resolves #
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] CI tests has been updated, if necessary.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.

instead of commenting it , remove the code and we can use git revert to revert back the changes. WDYT?

I commented on those so that if someone(or me) look at that, gets reminder to fix the CI issue :XD

Going ahead with Merge as CI is know issue


Test the MutatorOrchestrator

We didn't have any tests for the MutatorOrchestrator so I added one. I'm aware that this code conflicts with the .NET core branch. I'll fix that after we merge either of the branches.

Note: This is PR is not yet done. I want to trigger SonarQube and refactor the code.

Might want to look into why it's triggering two builds too... branch + pr or is that because the push triggered one and then the subsequent pr did too?

I believe one builds this branch and one builds the branch after a merge with master. SonarQube only reports new issues right?

The branch branch build does:
git clone -q --branch=test-mutatororchestrator https://github.com/infosupport/stryker-net.git C:\projects\stryker-net
git checkout -qf ab0da2ce5bc7431fea300191ac7e410fb4997cb8

And the pr build does:
git clone -q https://github.com/infosupport/stryker-net.git C:\projects\stryker-net
git fetch -q origin +refs/pull/11/merge:
git checkout -qf FETCH_HEAD

So it seems to attempt to merge.
In other news. SonarQube ignores my unused variable :(

@simondel it seems to be a matter of build order. Sonarqube noticed your variable in some point of time, and then in has been removed in another point of time:
https://sonarqube.com/component_issues?id=Stryker.NET#types=CODE_SMELL|resolutions=FIXED
I think one build introduced this unused variable, and other removed it, so sonarqube marked it as "FIXED". I don't yet know wchich build done what . If there were only one build triggered it wouldn't happen.

@pavzaj how'd you configure it? Currently this repo is set to build on push and on PR. I kind of like it that way, but don't like how Sonar handles it :) Any ideas?

As I said, in my opinion two build definitions will solve the case. One should be configured to start on push and PR on master branch only and there should be SQ analysis. Second build definition configured on push (and PR maybe) on all branches other than master and it shouldn't start SQ analysis. It should only build and run tests. Alternatively on second branch we could run preview SQ analysis only.
Such configuration will give us every push built and tested, and every push and PR on master branch analysed in SQ.

Odd. SonarQube is acting up. Could it be because the Project GUID changed?
Sonarqube analysis for: 17f1fa339e0ec8d2ca796824ba07892b829b9ae2
Analysing Pull Request 11
SonarQube Scanner for MSBuild 2.2
The format of the analysis property sonar.login= is invalid
The format of the analysis property sonar.github.oauth= is invalid
Default properties file was found at C:\projects\stryker-net-u3136\Stryker.NET\packages\MSBuild.SonarQube.Runner.Tool.1.0.0\tools\SonarQube.Analysis.xml
Loading analysis properties from C:\projects\stryker-net-u3136\Stryker.NET\packages\MSBuild.SonarQube.Runner.Tool.1.0.0\tools\SonarQube.Analysis.xml
Command exited with code 1

@simondel my bad, forgot to save the changes :D

Fixed the issue with SonarQube analysis.

As I see this is the latest branch. When do you plan to merge with master?

@simondel any thoughts?

I'll make some changes tomorrow and then it can be merged


[Tokio Branch] hyper::server::response::{ Body and IntoBody } are private, propose to expose publically

Currently, you can call response.set_body() with anything that implements hyper::server::response::IntoBody, and right now that is just Body itself, Vec<u8> and &'static [u8].
In my application, I have my own ResponseBody struct, that I would like implement IntoBody, (to pass to response.set_body() but I cannot because IntoBody is private.
Additionally, I would like to be able to use the hyper::server::response::Body type, so that I can do the Body::pair() and tx.start_send() within my application, then pass that result to response.set_body().
Is that potentially breaking any Hyper conventions? Are they private for a reason, and is there a better way of doing what I want to do? (Other than simply converting my ResponseBody to Vec<u8> and passing that in.)

In general things are private because I'm being much more conservative with what is made public, so internal optimizations can be made without breaking people.
In this particular case, I didn't really like the idea of a IntoBody trait, but instead wanted Into<Body>. The IntoBody trait currently exists because I cannot impl Into<Body> for Vec<u8>, since neither Body nor Vec<u8> are defined in hyper. I think what is probably the best to do is to create hyper::Body, which may just wrap around tokio_proto::streaming::pipeline::Body, and so I can also kill the trait.
A reason for hyper to have its own Body is because once hyper supports HTTP2, it would need to use tokio_proto::streaming::multiplex::Body, and I'd rather take care of those details internally.
I hadn't done all this yet because, well, I've forgotten, and I also wasn't certain if it was the right thing to do, but it currently feels like it.

Oh, yes, creating a hyper::Body that is just a wrapper around the tokio_proto Body is a good idea, so that you can implement Into<Body> on that.
Then if that hyper::Body was exposed publicly,

Oh, yes, creating a hyper::Body that is just a wrapper around the tokio_proto Body is a good idea, so that you can implement Into<Body> on that.
Then if that hyper::Body was exposed publicly, I could do impl Into<hyper::Body> for MyResponseBody and be able to pass MyResponseBody directly into set_body(). That way I don't need to add a dependency on tokio_proto into my application, and can simply use hyper::Body.

Another point to make. Currently hyper::server::response::Body and hyper::client::response::Body are both separately defined to tokio_proto::streaming::pipeline::Body. Would a hyper::Body replace both of those? Will server::response::Body always be the same as server::client::Body, regardless of what tokio_proto Body it is using?

They should probably be the same type, and they should be made to work regardless of whether 1 side is HTTP1 and the other is HTTP2, and the type is really just meant to describe something that implements Future<Item=hyper::Chunk, Error=hyper::Error>.


delete pending-upgrade release

Output of helm version: 3.9.0
Output of kubectl version: 1.18.7
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  own bare-metal
I'd like to remove pending-upgrade release automatically in Gitlab. Is there any helm analog for command
kubectl -n NS delete secret -l name=release-name,status=pending-upgrade
I use helm docker image in Gitlab and I'd like not to add kubectl to image.

i think you just need to use helm uninstall <releaseName> rather than to delete the secret.


No Hello world

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/run
Operating System: linux
Nothing happens when running the project.
The message won't appear in the console.

Do you get anything? Any error messages?

Hello,
First C# extension in VSCode says .Net is not installed properly but the build works.
The problem is that the execution doesn't print the message.


Update authorization of collection - add cfg property to allow users/submitters to update Item

Problem description:

Eperson should have a possibility to edit metadata of already published Item (item published by himself). Edit User - there is a checkbox to allow editing users item by himself
cfg property lr.allow.edit.metadata = LRT + Open Submissions Data & Tools means 'allow editing of every Item in the collection by his creators'

21/May/2024:
Check this discussion, maybe it would be helpful: https://groups.google.com/g/dspace-tech/c/0SxZZ-fuDqY/m/qwIPGnkRAAAJ?utm_medium=email&utm_source=footer

ufal-important
Milan si mysli, ze to jde resit vanilla prostredky


Only 40 movies/tvshows on each category

I'm submitting a ...

[ ] bug report
[ ] feature request
[X ] support request

General infomration
I only get 40 movies or tvshows on each genre that i browse.
Also today when try to browse a tvshow it returns error.
Movies work ok. Also tv shows that i already have on my library via emby/kodi work ok.
Thanks
Prerequisites

[ ] Are you running the latest version?

Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Context (Environment)
Installation

[ ] I installed the plugin via zip from the Releases page
[ ] I´m using the Netflix Repo
[ ] I´m using a different source (Please tell which)

Operating System

[ ] Linux (x86/x64)
[ ] OSX (x86/x64)
[ ] Windows (x86/x64)
[ ] Linux (ARM)
[ ] Android

Additional informatin on the environment
[Descripe your environment a bit more detailed, are you using LibreElec f.e.]
Debug log
[Please include a link to your debug log (use something like http://sprunge.us/) or similar, please do not paste]
Other information
[e.g. detailed explanation, related issues, suggestions how to fix, links for us to have context, etc.]
Screenshots
[Please add a screenshot if that helps understanding your problem]
[You can erase any parts of this template not applicable to your Issue.]

No debug log, no mention of what OS you are using, no mention of what version you are using. How can you expect anyone to help with the lack of information supplied? Always supply as much information as you can, it takes some time but remember it takes the developers a lot of time so sparing a few more minutes of your own time is the least that can be done.
Also don't forget to check out other reported issues....2 have been created today with regards not being able to browse episodes...so sounds like a duplicate. But the mention of only 40 per category could be unique so it would be helpful to state how many you see in Netflix ideally with a screenshot

Hello
Sorry for the lack of information.
I am running the plugin on the latest nightly of Kodi 18, on a Nvidia shield tv(1st gen).
My library is working with emby/kodi with the emby server running on a windows server machine.
I have added some tvshows and some movies to my library (all play ok through the library), only when browsing the plugin I am not able to browse the episodes.
Concerning the 40 entries per category I try later to send screenshot or more info, because now I'm at work.
Thanks for your help.

Duplicate of https://github.com/asciidisco/plugin.video.netflix/issues/215


Fix action and add Patreon link (not functional yet)

Had to fork the action and also used another action to push changes. in https://github.com/SideStore/.github/settings/actions make sure Workflow permissions is set to Read and write permissions. (that took a while to figure out)
patreon link is currently nonexistent. I think it would be better to setup sponsors/funding since they can have Patreon links. also we could probably use emojis instead of the web/discord/twitter icons since they don’t look very good in dark mode

@lonkelle

We have a Patreon tho: https://www.patreon.com/SideStore - or am I confused?

Sorry, bad wording on my part - I've added the link to the metadata at the bottom, but there isn't a link on the README that uses it yet. I think GitHub's Sponsor/Funding system supports Patreon links, so that should probably be added.


Schematics documentation

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request

Versions.

Latest
Desired functionality.

Very excited to see Schematics support has landed! Will usage be documented here or is this something we should look for over at angular/devkit repo?
One thing we would love to be able to do is create our own application structure. Also, additional generators for things like lazy-loaded-feature which contain ngModule, component ts, html, scss, etc. Are these supported use-cases?

I have no idea about what is chematics, but as it is now a way to generate app, I'd really like to see full docs. I wonder how you guys found possible to release it without any docs.

@AloeDream, this issue is trying to clarify, first and foremost, whether this repo is even the right place for this documentation. Technically, the functionality is provided via https://github.com/angular/devkit. Ideally, documentation is also provided from that repo and maybe we get some recipes here https://github.com/angular/angular-cli/wiki/stories.
But, yes, would be great to get some feedback from the team with a rough estimate on when we might expect that. My guess is that this functionality was added primarily for internal purposes and the fact that it enables users to customize is icing on the cake. In which case, documentation probably isn't the highest priority at the moment.
In the meantime, you might want to consider opening a similar issue over at angular/devkit repo.

@bmayen this feature is critical for CLI, as I go type ng help to review ng new command parameters and see that many of them disappeared and one new appeared without any explanation how to use it. So yes, I think this is the right place to at least mention where to find its docs and how it's not the highest priority, as I can't create new or update existing project without those docs?

There should be some slides and talks coming out of AngularMix in a couple weeks which provide considerable information about Schematics. I'm unsure if there are plans to provide significant documentation on the feature before then, but hopefully soon :)
Some details can be found in this blog post.

@Brocco First of all, thanks for all the hard work on the CLI 🥇Love it.
I have one quick question related to @Splaktar 's above comment. AFAIK you presented at AngularMix on the CLI/schematics, but the session was not recorded/published on the youtube channel. Is there any material (slides etc)  you could make available? Thanks in advance.

I don't believe that there were many slides in that talk. Most of it was a demo of how the schematics work. It's very unfortunate that it wasn't recorded :(
I know that there is work happening to document the schematics feature. However I have no idea what the ETA might be.

@tomwanzek schematics were on the latest Angular Air.

@Splaktar Thanks for the hint re ngAir...checking it out.

@Splaktar were you able to test our your custom schematics? Following @Brocco 's instructions on the ngAir episode I ran the following commands:
npm i -g @angular-devkit/schematics
npm i @schematics.schematics -g
schematics @schematics/schematics:schematic --name schematics-test
i than installed/built schematics-test, and npm link'd it.
In an empty directory I attempt to run: schematics schematics-test:my-full-schematic --name test
and I get the error "tree.branch is not a function". I've spent a few hours trying to figure out what this could possibly be with no luck. Any insight?

@jimdubbs Yes, I got everything working.
I also ran into those tree.branch is not a function errors. I think that I hit them when trying to generate an application using my schematics with ng new. I've since switched to just using the schematics command directly and I haven't hit that issue since. It's most likely just a configuration issue.
Note that my solution combined the contents of @schematics/angular with the output of @schematics/schematics. I don't think that the output of @schematics/schematics is really ready for prime time yet, but it gave me enough to work with that I could wire everything up. Specifically, I have utility/ and strings.ts in my-schematics/src/.
I also had to add the following to the package.json generated by @schematics/schematics to get npm test to work:
  "devDependencies": {
    ...
    "common-tags": "1.4.0",
    "portfinder": "1.0.13",
    "selenium-mock": "0.1.5",
    ...
}

Here's my full package.json, not all of this is required (like angular here just helps my IDE)
{
  "name": "my-schematics",
  "version": "0.0.1",
  "private": true,
  "description": "Schematic plugins to Angular Devkit",
  "engines": {
    "node": ">= 6.11.0",
    "npm": ">= 3.10.0"
  },
  "keywords": [
    "schematics"
  ],
  "dependencies": {
    "@angular-devkit/core": "0.0.20",
    "@angular-devkit/schematics": "0.0.34",
    "@types/jasmine": "2.6.2",
    "@types/node": "8.0.47",
    "jasmine": "2.8.0",
    "typescript": "2.5.3"
  },
  "devDependencies": {
    "@angular/common": "4.4.6",
    "@angular/compiler": "4.4.6",
    "@angular/core": "4.4.6",
    "@angular/platform-browser": "4.4.6",
    "@angular/platform-browser-dynamic": "4.4.6",
    "@angular/router": "4.4.6",
    "@types/jasmine": "2.6.2",
    "@types/jasminewd2": "2.0.3",
    "@types/node": "6.0.60",
    "common-tags": "1.4.0",
    "portfinder": "1.0.13",
    "protractor": "5.2.0",
    "selenium-mock": "0.1.5",
    "ts-node": "3.3.0",
    "tslint": "5.8.0",
    "zone.js": "0.8.18"
  },
  "optionalDependencies": {},
  "peerDependencies": {},
  "scripts": {
    "build": "tsc -p tsconfig.json",
    "schematics": "schematics",
    "list": "npm run schematics -- my-schematics --list-schematics",
    "test": "npm run build && jasmine src/**/*_spec.js"
  },
  "schematics": "./src/collection.json"
}

@jimdubbs I actually just hit that error again while trying to run my schematics globally in a brand new Node environment.
I resolved it by moving "@angular-devkit/schematics": "0.0.34" from dependencies to devDependencies, and peerDependencies in my-schematics repo.
Then I ran into Cannot find module 'rxjs/add/operator/map'. This was fixed by adding "rxjs": "5.4.2", to the dependencies of my-schematics repo.

@Splaktar Still running into the tree.branch is not a function issue. My package.json dependencies for my schematic project is
"dependencies": {     "@angular-devkit/core": "0.0.20",     "@types/jasmine": "2.6.2",     "@types/node": "8.0.47",     "jasmine": "2.8.0",     "typescript": "2.5.3"   },   "peerDependencies": {     "@angular-devkit/schematics": "0.0.34"   },   "devDependencies": {     "@angular-devkit/schematics": "0.0.34",     "@angular/common": "4.4.6",     "@angular/compiler": "4.4.6",     "@angular/core": "4.4.6",     "@angular/platform-browser": "4.4.6",     "@angular/platform-browser-dynamic": "4.4.6",     "@angular/router": "4.4.6",     "@types/jasmine": "2.6.2",     "@types/jasminewd2": "2.0.3",     "@types/node": "6.0.60",     "common-tags": "1.4.0",     "portfinder": "1.0.13",     "protractor": "5.2.0",     "selenium-mock": "0.1.5",     "ts-node": "3.3.0",     "tslint": "5.8.0",     "zone.js": "0.8.18",     "rxjs": "5.4.2"   }
Globally I have the following installed:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>I've npm linked my schematics project so I should be able to access it globally.
from the command line I attempt to run "schematics schematics-test:my-full-schematic --name test" from an empty folder and I get the tree.branch error. Any insight as to what Im doing wrong?do I need to have something installed locally in the directory im trying to run the schematics command from?

Do I need to have something installed locally in the directory im trying to run the schematics command from?
Nope.

tree.branch is defined in @angular-devkit/schematics. So your project is not picking that up for some reason.
If you are using it via npm link, make sure to run npm run build in your schematics-test projects before trying to run the command.
You shouldn't need<EMAIL_ADDRESS>installed globally. Here's what I have:
npm list -g --depth=0
/Users/splaktar/.nvm/versions/node/v8.6.0/lib
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Can confirm I've ran npm run build in my schematics project.
Tried installing<EMAIL_ADDRESS>in local project that Im trying to run schematics schematics-test:my-full-schematic --name test from and still no dice :(

@jimdubbs The environment that I'm using to run schematics my-schematics:application --name tmp --directory tmp is NodeJS 8.6.0 w/ nothing in it but those global dependencies above. I'm in a directory that does not have any project (package.json) in it. This is generating a new app, not generating something in an existing app.
If you are trying to use your schematics in an existing project to generate services/components, etc. then you in that project's package.json, you'll want
devDependencies: {
    ...
    "@angular-devkit/schematics": "0.0.34",`
    "my-schematics": "git+ssh://git@github.com:myname/my-schematics.git",
    ...
},

Adding the following to that project's .angular-cli.json will allow you to skip defining the collection every time when using ng g:
  "defaults": {
    "schematics": {
      "collection": "my-schematics"
    },

You may also want to add this to your scripts in package.json:
    "schematics": "schematics",

This way you can do something like npm run -- schematics my-schematics:my-test-schematic --name foo.  This allows you to run the schematics command in your local project (rather than use the global package) and may help you avoid the failure to lookup @angular-devkit/schematics that you are hitting.

@Splaktar Not trying to run from an existing project, completely empty like you. Quite a frustrating error, and it seems I have an Identical setup as you.

I am getting these errors too.
Running this with an Ubuntu, it never picks up @angular-devkit/core.
testproject $ node --version
v8.5.0
testproject $ npm --version
5.3.0

Using all the workarounds, I then get the error
Cannot read property 'entries' of undefined
when running
npm run schematics -- --debug my-schematics/schematics:component --name customTestComponent
Nothing useful as far as error logs go, the debug option doesn't really help.
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:289:16)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at EventEmitter.emit (events.js:213:7)
13 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
13 verbose stack     at emitTwo (events.js:125:13)
13 verbose stack     at ChildProcess.emit (events.js:213:7)
13 verbose stack     at maybeClose (internal/child_process.js:927:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)

I've found that --debug and --verbose don't seem to output anything different when I run into issues :(
@Vaelor wouldn't it be npm run schematics -- --debug my-schematics:component --name customTestComponent?

@jimdubbs error seems to be a common issue atm (multiple issue open against angular/cli): https://github.com/angular/angular-cli/issues/8167

@Splaktar Indeed, I've found a workaround for now - instead of testing my schematics with the Schematics binary im just using the CLI and it seems to be fine.

There is also a video from the June MTV Angular Meetup that was just posted in October that has Hans covering Schematic concepts and demoing a number of features.

There is also a newer schematics documentation issue here: https://github.com/angular/angular-cli/issues/12149

Hello,
I couldn't find docs about "defaults" configuration, thanks to an example I know it's possible to configure a default value with argv, but that's all. I don't know if it's possible, for example, to define a default value based on another parameter.
There should be a section about defaults in the documentation please.
Thanks.

@no-more good suggestion. I've added it to an outline that is currently being worked on as part of the official schematic docs.

Closing this issue so we can use https://github.com/angular/angular-cli/issues/12149 instead.


How to calculate TFLOPS in LSTM.cu

The output of this code is runtime, but what i want to compare is throughput, how do i convert the runtime into TFLOPS.
I mean how the computation is related to the other parameters.

The vast majority of FLOPs in an LSTM are in the matrix multiplications. A single matrix multiplication requires 2MN(K+1) FLOPs. There are 8 matrix multiplications per layer per timestep, and in this case M=K=hiddenSize, N=minibatch. Therefore the total FLOPs are:
layers * timesteps * 8 * 2 * hiddenSize * minibatch * (hiddenSize + 1).
In reality there's a few more FLOPs due to biases and activation functions. These are only significant if hiddenSize is very small as they scale linearly with hiddenSize rather than with the square.


ERROR: Failed building wheel for pybinding

Hi!
I am trying to install pybinding on my existing miniconda environment (the one I use for basically all my work). I am trying to do so with pip install pybinding
but with no success (Details ahead). The installation works in another miniconda environment I do not use, but for me it is essential to use pybinding in my usual environment. The error I get in the installation is:
Building wheel for pybinding (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
A LOT OF TEXT
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pybinding
Running setup.py clean for pybinding
Failed to build pybinding
ERROR: Could not build wheels for pybinding, which is required to install pyproject.toml-based projects
Any idea on how I can fix this? I am such a dummy for technical stuff. I have also tried with the other suggested installation methods but they did not work.
Suggestions?
Thanks in advance

Hi
I'll update the pip installation next year, but for now, you ca install pybinding using the following commands:

pip install numpy scipy matplotlib pytest
pip install -i https://test.pypi.org/simple/ pybinding

This is not yet for 3.12, you'll have to downgrade to an earlier version of python.
Let me know if it works.
Best
Bert

It works now!
Thanks a lot Bert!


can't find OpenSSL

I've updated my installation guide Install Ruby with Frum for Ruby 3.1. I'm advising to install OpenSSL using Homebrew before installing frum. However, after installing OpenSSL, frum, and Ruby 3.1, when I try to install the rails gem, I get:
$ gem install rails
ERROR:  While executing gem ... (Gem::Exception)
    OpenSSL is not available. Install OpenSSL and rebuild Ruby (preferred) or use non-HTTPS sources

Looking at closed issues, it looks like frum version 0.1.2 fixes any issues with OpenSSL. What am I overlooking? Do I need to install ruby with the option --with-openssl-dir=<ssl_dir>? Or do I need to add openssl to my PATH?
Let me know and I'll update my guide.

What versions of frum do you use? From v0.1.2, frum uses<EMAIL_ADDRESS>

I ran into a similar error while trying to bring up a rails app.  Prefixing arch -arm64 to my requests seems to have fixed the issue.
arch -arm64 gem install bundler

Hope this helps!

I was able to get past the openssl issue by reinstalling ruby. Using frum,
frum uninstall 3.1.0
frum install 3.1.0 --with-openssl-dir=`brew --prefix openssl`

I'm unable to install any rubies using frum on an M1 running Monterey: not even with @151henry151 suggestion.
I think this is the same issue, so won't open a new one.
The error I get is
error: Can't build Ruby: make install: Configured with: --prefix=/Library/Developer/CommandLineTools/usr --with-gxx-include-dir=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/4.2.1

Generating RI format into /Users/lnoble/.frum/versions/.downloads/.tmpXy9clZ/ruby-2.7.5/.ext/rdoc...
/Users/lnoble/.frum/versions/.downloads/.tmpXy9clZ/ruby-2.7.5/lib/rubygems/core_ext/kernel_require.rb:83:in 'require': cannot load such file -- openssl (LoadError)
	from /Users/lnoble/.frum/versions/.downloads/.tmpXy9clZ/ruby-2.7.5/lib/rubygems/core_ext/kernel_require.rb:83:in 'require'
	from /Users/lnoble/.frum/versions/.downloads/.tmpXy9clZ/ruby-2.7.5/lib/rubygems/specification.rb:2430:in 'to_ruby'
	from ./tool/rbinstall.rb:846:in 'block (2 levels) in install_default_gem'
	from ./tool/rbinstall.rb:279:in 'open_for_install'
	from ./tool/rbinstall.rb:845:in 'block in install_default_gem'
	from ./tool/rbinstall.rb:835:in 'each'
	from ./tool/rbinstall.rb:835:in 'install_default_gem'
	from ./tool/rbinstall.rb:799:in 'block in <main>'
	from ./tool/rbinstall.rb:950:in 'block in <main>'
	from ./tool/rbinstall.rb:947:in 'each'
	from ./tool/rbinstall.rb:947:in '<main>'
make: *** [do-install-all] Error 1

frum versions returns 2.7.5 but attempting frum uninstall 2.7.5 results in
==> Uninstalling Ruby 2.7.5
error: No such file or directory (os error 2)

Hopefully this is useful information - sadly I don't know Rust.

I'm unable to install any rubies using frum on an M1 running Monterey

@docljn Have you tried manually removing the 2.7.5 directory from .frum/versions?
$ rm -rf ~/.frum/versions/2.7.5

I did do exactly that @shanebarringer thank you. The joys of being an early adopter, I guess :)

The joys of being an early adopter, I guess :)

I know right 🙃
Once you've removed it, maybe try prefixing arch --arm64 to your install request.
$ arch -arm64 frum install 2.7.5

Does everyone in this issue use M1 mac? I want to know your environment like the following.
MacBook Air (M1, 2020)
Apple M1
Memory 8G
macOS Big Sur version 11.5.2
Frum: 0.1.0

0.1.2 compiles everything without issue for me (pre 0.1.2, I did have openssl issues as without @1.1 in the prefix, it was targeting @3 on my machine by default).
One thing to mention is that if memory serves me correctly when the M1 was released, a lot of early adopters had to use arch -arm64 to install Homebrew.
That changed some months after, but I wonder if having to use arch -amd64 is now an unfortunate consequence of that initial install.
MacBook Air (M1, 2020)
Apple M1
Memory 16GB
macOS Monterey 12.0.1
From 0.1.2

error: No such file or directory (os error 2)

I noticed a similar error if there's a default alias symlink left.

Does everyone in this issue use M1 mac? I want to know your environment...
@TaKO8Ki in reference to your question, here are my device specs

MacBook Pro (16-inch, 2021)
Apple M1 Max
Memory 32GB
macOS Monterrey 12.0.1
Frum 0.1.2

Does everyone in this issue use M1 mac? I want to know your environment
I am on macOS Monterey, Version 12.0.1, MacBook Pro (12-inch, M1, 2020) with 8GB memory, frum 0.1.2

maOS Monterey
Version 12.1
MabBook Pro (14-inch, 2021)
Apple M1 Pro Chip
16GB memory
frum 0.1.2

Thank you for your reply. I understand everyone uses Monterey on M1 mac. I don't have a M1 mac, but I'm going to look it into.

maOS Monterey
Version 12.0.1
Mac Mini 2020
Apple M1
8GB memory
frum 0.1.2

Same issue here on M2. Such a shame I wanted to give frum a try. Has anyone found a solution?
frum install 2.7.5 --with-openssl-dir="/opt/homebrew/opt/openssl@3"
==> Downloading https://cache.ruby-lang.org/pub/ruby/2.7/ruby-2.7.5.tar.xz
==> Extracting ruby-2.7.5.tar.xz
==> Building Ruby 2.7.5
error: Can't build Ruby: make install:
Generating RI format into ~/.frum/versions/.downloads/.tmp7Ul3nL/ruby-2.7.5/.ext/rdoc...
~/.frum/versions/.downloads/.tmp7Ul3nL/ruby-2.7.5/lib/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file -- openssl (LoadError)
	from ~/.frum/versions/.downloads/.tmp7Ul3nL/ruby-2.7.5/lib/rubygems/core_ext/kernel_require.rb:83:in `require'
	from ~/.frum/versions/.downloads/.tmp7Ul3nL/ruby-2.7.5/lib/rubygems/specification.rb:2430:in `to_ruby'
	from ./tool/rbinstall.rb:846:in `block (2 levels) in install_default_gem'
	from ./tool/rbinstall.rb:279:in `open_for_install'
	from ./tool/rbinstall.rb:845:in `block in install_default_gem'
	from ./tool/rbinstall.rb:835:in `each'
	from ./tool/rbinstall.rb:835:in `install_default_gem'
	from ./tool/rbinstall.rb:799:in `block in <main>'
	from ./tool/rbinstall.rb:950:in `block in <main>'
	from ./tool/rbinstall.rb:947:in `each'
	from ./tool/rbinstall.rb:947:in `<main>'
make: *** [do-install-all] Error 1

@monfresh I have tried frum install 2.7.5<EMAIL_ADDRESS>without luck. Is there any other way? Thanks!

I was installing ruby 3.x and got the error error: Can't build Ruby: make failed: . ./vm_opts.h
brew install libyml
frum install 3.2.2
Ruby was installed successfully after installing libyml,

You probably

I was installing ruby 3.x and got the error error: Can't build Ruby: make failed: . ./vm_opts.h
brew install libyml frum install 3.2.2
Ruby was installed successfully after installing libyml,

I think you meant to write
brew install libyaml instead of brew install libyml.


Compile error on linux, ncInput missing eff_text

error[E0063]: missing field `eff_text` in initializer of `bindings::ffi::ncinput`
  --> src/input/mod.rs:66:9
   |
66 |         NcInput {
   |         ^^^^^^^ missing `eff_text`

error[E0063]: missing field `eff_text` in initializer of `bindings::ffi::ncinput`
   --> src/input/mod.rs:123:9
    |
123 |         NcInput {
    |         ^^^^^^^ missing `eff_text`

For more information about this error, try `rustc --explain E0063`.
warning: `libnotcurses-sys` (lib) generated 5 warnings
The following warnings were emitted during compilation:

warning<EMAIL_ADDRESS>Keeping vendored files…

error: could not compile `libnotcurses-sys` (lib) due to 2 previous errors; 5 warnings emitted

added eff_text : [0;4], on a downloaded copy of the repo and it compiles.

this was added to notcurses in eac79ee6801610eef7347ea8940db731480f38bd

https://github.com/dankamongmen/notcurses/commit/d8cb625b9a8c007df92dfaf2130076e18c620ab3

@Kodiak-Web do you want to prep that as a PR? @joseluis will hopefully merge it or if he's not around, i will (once i determine that it's right, which i'm guessing it is)

oh, sorry, yeah
honestly i didnt set it as a pr or anything as i didn't know if it was a my system thing or something
yeah i can make a pr rq

Current version of libnotcurses-sys is compatible with the notcurses release 3.0.9. That change in the input struct hasn't been officially released yet. I was waiting for a 3.0.10 release in order to make the necessary updates... @dankamongmen Do you plan on doing a small release with the changes since december 2022?


Robust Error-Handling for Matoya Clients

This PR introduces the ability for users of libmatoya to query for errors and handle them accordingly. Currently, only GPU errors are being reported.
The proof-of-concept is done. What is pending is to clean up the implementation.
WINDOWS-ONLY for now

it occurs to me that maybe there is something much simpler that solves the problem at hand: instead of a queue of MTY_Error, you may really want a bitmask, with one bit for each possible MTY_Error. if there are 64 or fewer error types, this fits into a uint64_t. it can be tested by ANDing the uint64_t with (1ULL << error_code), etc. this is because you probably don't care exactly what order the errors occurred in, but you probably do care about which combination of 2+ errors occurred.


begin blog darkmode

Related Issue
Closes: #1636
Description
i started adding CSS to bring dark mode in the blog.html page. will continue changes.

Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

let me know if there are any conflicts please!

thank you!

can you also add ssoc label to this please?


Message chnage on "Reject request"

-Wrong message on ‘Reject Request’.
-It should just say ‘Request Rejected’

The error message is for invalid decryption (we would need to have an alternate message if the request is rejected (no input press).


Update paye-tools to 17.0.17068.356

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask's name and version.

Thank you for the contribution. It was merged directly as 9c79b60b6b2d069760edff2556327869748e293b to keep commit history cleaner. Your contribution is still credited to you.


17 1 release

@viktormalik

it should merge into the v0.17.1_release branch, we can then tag that as v0.17.1 and create the release entry