False Ring Info?

I came across this weird example where the atoms in the ring info don't match the actual ring atoms.
To reproduce:
acetaminophen_inchi = "InChI=1S/C8H9NO2/c1-6(10)9-7-2-4-8(11)5-3-7/h2-5,11H,1H3,(H,9,10)"  # taken from pubchem
acetaminophen_mol = rdkit.Chem.MolFromInchi(acetaminophen_inchi)
ring = acetaminophen_mol.GetRingInfo().BondRings()[0]  # (2, 4, 3, 6, 5, 1)
rdkit.Chem.Draw.MolToImage(acetaminophen_mol, highlightAtoms=ring)

The result looks like this:

I expect the atoms to be the ring atoms and not to include the one on the right.
This is the molecule with atom indices:

So I expect ring to be (1, 6, 2, 4, 7, 3) (or some other configuration of these numbers).
Also, if I use SMILES instead of InChI:
acetaminophen_smiles = "CC(=O)NC1=CC=C(C=C1)O"
acetaminophen_mol = rdkit.Chem.MolFromSmiles(acetaminophen_smiles)
ring = acetaminophen_mol.GetRingInfo().BondRings()[0]
rdkit.Chem.Draw.MolToImage(acetaminophen_mol, highlightAtoms=ring)

I get:

Which is different but still false.
Configuration (please complete the following information):

RDKit version: 2023.3.2
OS: macOS 12.3
Installed via pip install -U rdkit

GetRingInfo().BondRings() returns the indices of the bonds in the ring. I
expect that if you change your drawing call to “highlightBonds=ring” you
will see something more sensible.  Alternatively, try
GetRingInfo().AtomRings().
On Sun, 20 Aug 2023 at 12:44, NadavQuris @.***> wrote:

I came across this weird example where the atoms in the ring info don't
match the actual ring atoms.
To reproduce:
acetaminophen_inchi = "InChI=1S/C8H9NO2/c1-6(10)9-7-2-4-8(11)5-3-7/h2-5,11H,1H3,(H,9,10)"acetaminophen_mol = rdkit.Chem.MolFromInchi(acetaminophen_inchi)ring = acetaminophen_mol.GetRingInfo().BondRings()[0]rdkit.Chem.Draw.MolToImage(acetaminophen_mol, highlightAtoms=ring)
The result looks like this:
[image: image]
https://user-images.githubusercontent.com/103879485/261849615-55ef8aea-7c72-4f9f-8bc3-fd353d62b82d.png
I expect the atoms to be the ring atoms and not to include the one on the
right.
Configuration (please complete the following information):

RDKit version: 2023.3.2
OS: macOS 12.3
Installed via pip install -U rdkit

—
Reply to this email directly, view it on GitHub
https://github.com/rdkit/rdkit/issues/6648, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACGF2FWU76BRKQRIFULGM5DXWH2DDANCNFSM6AAAAAA3XHEVTU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
David Cosgrove
Freelance computational chemistry and chemoinformatics developer
http://cozchemix.co.uk

Oh I understand, thanks! AtomRings indeed works!


flares despawn shortly after expiring

Why / Balance

Garbage cleanup, unlike empty mags these serve no purpose but to take up space on the screen, among performance reasons I suppose.
Technical details

Adding onto UpdateVisualizer, whenever the item progresses to the spent sprite, the TimedDespawnComponent is given so the item is deleted after the default 5 seconds have passed, similar to current blood puddles.
I think this is the least obtrusive way to add this functionality without touching more than this one upstream file.
I also do not know much about coding.
/shrug
Changelog
:cl: Whisper

add: Spent flares will now despawn.

Spent flares are one of the items I used for game sense for checking of any marines have been through this area and how long it's been since then. I'm not sure exactly how useful that is, but it's a small thing that I think is at least a tiny bit useful.
I'm not super against despawning them, but just wanted to provide a reason why they shouldn't be if it wasn't known before.


Update README.md

dotnet-core is not an allowed product name - https://review.learn.microsoft.com/en-us/help/platform/metadata-taxonomies?branch=main#product

@paolosalvatori Can you merge this?


Support attribute to indicate the type of a key in dictionary

Here from
https://github.com/RicoSuter/NJsonSchema/pull/755
https://swagger.io/docs/specification/data-models/dictionaries/ "OpenAPI lets you define dictionaries where the keys are strings."
Can create a new attribute to indicate the type of key in the dictionary for primitive types such as Guid, Int and so on ? To expand the rule
In service:
[UseDictionaryKey(typeof(Guid))] // or just attribute with no parameters
public IDictionary<Guid, object> Items { get; set; }

In generated client "now":
public IDictionary<string, object> Items { get; set; }

In generated client "may be":
public IDictionary<Guid, object> Items { get; set; }

wrong project, now in https://github.com/RicoSuter/NSwag/issues/3002


Missing module 'ssm.plots'

hello! I was trying to do the tutorial but I encounter this error that prevents me to generate plots.
`ModuleNotFoundError                       Traceback (most recent call last)
 in ()
5 import ssm
6 from ssm.util import find_permutation
----> 7 from ssm.plots import gradient_cmap, white_to_color_cmap
8
9 import matplotlib.pyplot as plt
ModuleNotFoundError: No module named 'ssm.plots'`
I am beginner in Python, so I don't really know if I can fix this by myself or I need this specific module from the developers of ssm.
Thanks in advance!
best,
BT

For my case, placing plots.py file in this repository to the directory where ssm package locates solves this issue.


Add option for renaming table and column names

I would like to suggest a new feature inspired by json_serializable.
The naming convention for Dart is lowerCamelCase.
As SQL is a commonly used database, everyone has its preferences for naming tables and columns.
As such, we could have an option as json_serializable offers in build.yaml:
targets:
  $default:
    builders:
      json_serializable:
        options:
          field_rename: none/pascal/kebab/snake [as lowerCamelCase is default for dart, `none` would also be lowerCamelCase)

In a example, the following class
@Entity()
class MyClass {
  MyClass({this.aLongVariableName});
  String aLongVariableName;
}

the variable aLongVariableName would be mapped to a_long_variable_name column name, when using the snake case option.

I'm not sure on the specifics yet (e.g. where to configure that) but this seems like a reasonable feature.
But I have to mention that we will probably only have to convert between names with underscores and names without them, as -(kebab-case) is probably not used (can't be used in dart and has to be escaped in sqlite) and sql is not case-sensitive, so converting ClassName(dart) <-> classname(sql) is not necessary.


Support for RN 0.52 ?

Is it planned? For now, I can't build the lib when using 0.52 or 0.51.

latest RN releases are now supported, please try version 5.2.0
thanks


goffice: 0.10.53 → 0.10.54, gnumeric: 1.12.53 → 1.12.54

Description of changes
https://gitlab.gnome.org/GNOME/goffice/-/compare/GOFFICE_0_10_53...GOFFICE_0_10_54
https://gitlab.gnome.org/GNOME/gnumeric/-/compare/GNUMERIC_1_12_53...GNUMERIC_1_12_54 <- Why so many ChangeLogs?
Things done

Built on platform(s)

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

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

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

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

23.05 Release Notes (or backporting 22.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

@ofborg build gnumeric goffice

Ping reviewers? :eyes:

@ofborg build gnumeric


Added default Groovy installation version.

As a developer,
I want to be able to configure the Groovy installation version for Jenkins
Signed-off-by: Northard, Robert A<EMAIL_ADDRESS>

@nickdgriffin branch has been rebased.

LGTM. thanks @RobertNorthard!


Fix "resource that supports" to accommodate "after_unknown" values

Fixed an issue where the omission of after_unknown values were breaking the Given step resource that supports.
Addresses #438, #441
Please note, in this setup the regular Given works well:
using Given I have aws_rds_cluster defined with the other two steps:

passes with good kms_key_id
fails with bad kms_key_id (null)

Also note that kms_key_id is going to be an after_unknown value if and only if kms_key_id has a bad value (e.g. null)
So the Given I have resource that supports kms_key_id defined step is the culprit of this bug, as opposed to the omission of after_unknown values

Might want to add the feature file to the test dir? :)

Might want to add the feature file to the test dir? :)

Haha yes, I agree with @sleightsec here :)

Haha yes, I agree with @sleightsec here :)


Error: Unexpected value 'LangSwitcherComponent' exported by the module 'MultilingualModule'

[*] bug? - not in seed itself
npm run build.prod.exp at 'compile.ahead.prod' throws the above (or similar) whenever it encounters multiple export class... alongside @DeCorator.
This will be caused by export function translateFactory confusing the target of @NgModule. Moving it out will likely solve.

@CNSKnight I have no idea how this related to angular2-materialize. Can you elaborate please?
If you know what needs to be fixed a PR would be very welcome :)

@rubyboy sorry, idk how this ended up here either. you may safely delete.


onResponseUpdate callback

I'd like to visualize the response json every time it gets updated.
Is there a way to hook into this?
I expected to find a prop like onResponseUpdate (that receives the new response json), but can't find anything like that.

Hi @moroshko; you can implement this in your fetcher function - intercept the response before you pass it into GraphiQL.
[semi-automated message] Thanks for your question; hopefully we're well on the way to helping you solve your issue. This doesn't currently seem to be a bug in the library so I'm going to close the issue, but please feel free to keep requesting help below and if it does turn out to be a bug we can definitely re-open it 👍

How to go about it?
function graphQLFetcher(graphQLParams: any): Object  {
  return fetch(URL, {
    method: "post",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify(graphQLParams),
    credentials: "omit"
  }).then((response) => {
    console.log(response);      // -> I'd like to do something with the response over here, but this does not have the response body
    return response.json()      // -> This is  a method; I thought it was the response.
  });
}

function graphQLFetcher(graphQLParams: any): Object  {
  return fetch(URL, {
    method: "post",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify(graphQLParams),
    credentials: "omit"
  }).then((response) => {
    console.log(response);      // -> I'd like to do something with the response over here, but this does not have the response body
    return response.json()      // -> This is  a method; I thought it was the response.
  }).then(json => {
    console.log(json);
    return json;
  });
}

Thanks! I cloned the response, and then was able to reuse it twice. But this seems much much better.


keyword argument for config()

Hi,
I have a problem with the path for the DotEnv.config() function.
When I try to call config with path="user_path" it says that config does not accept keyword arguments :
DotEnv.config(path="C:\\users\\...")

function config does not accept keyword arguments

Do you have an idea of what the problem could be ?
Thanks.

Thank you for your report. I will be fixing this right now.
v0.2.1 fixes this.
Regards

Thank you for the update. However it seems now that DotEnv.config() (with and without path) doesn't work anymore...
show(DotEnv.config())
> nothing
show(DotEnv.config(path="user_path"))
> nothing
Thanks.

My bad. Just the version of config with a custom path doesn't work !

Ok, I get it. The way that config() works when there is a path specified is different than when no custom path :

DotEnv.config() : all the .env in the current directory (I guess)
DotEnv.config(path = "user_path") : the path is not the directory but the .env file so It adds only the specified file.

Everything works fine. Just a thought, it would be nice to be able to specified the folder that contains .env files for custom path either than just the .env path so to add multiple .env files.
Thanks


Add gesture classification for demo

Partially resolves https://github.com/opencv/opencv_zoo/issues/127
Add handpose estimation (0-9)

@yqxzy friendly reminder.


Fix error message for non-existing directory

As described in issue #1995, the error message thrown when the template directory does not exist was very misleading. This is a simple attempt to fix that.
fixes #1995

This seems even less clear. It doesn't say what package, or what directory name. I'm pretty sure this specific message can happen in other cases too, not just when the directory doesn't exist, so you'll need to split out detection of that and raise a specific error.

If I understand correctly, in cases where the package/module does not exist, we get an assertion error. So this is left exclusively for cases where the template directory does not exist.

I could add the package name and template directory to the error message if you think that's better. My reasoning for not including them was that in most cases these are included as strings, so you could see it right in the stack trace.

I think if there is a case that we can find a package, but cannot find any path associated for it, this can happen too. Not quite sure if that's possible or not. But even in that case, the original error message doesn't make a lot of sense.

duplicate of #1706


Implement topic merging in Clustering models.

Rationale:
Clustering topic models by default and usually have a clustering method that can learn the number of topics from the data.
This is nice, but a lot of times it results in too many topics. Both BERTopic and Top2Vec have methods for reducing the number of topics to a desired amount.
Details
The two approaches seem to be the following, the both the documentation and code in both repositories is incredibly cryptic around this (plus the papers have no info about it).
BERTopic
Run Agglomerative Clustering on the cluster centroids (topic vectors), then merge all topics that belong to the same cluster.
I found this in the paper:

Finally, by iteratively merging the c-TF-IDF representations of the least common topic with its most
similar one, we can reduce the number of topics to
a user-specified value.

(Like what the hell does this mean)
As far as I understand from digging in the code what they do is simply recalculate the c-TF-IDF representations with the new merged labels, and that's it.
Top2Vec
The algorithm seems to be something like this:

If the number of topics is already small enough, throw an error
Until the number of topics is small enough:

Find the smallest topic
Find the closest topic to this (by dot product?)
Merge by taking a weighted average of the two topic vectors combined_vec = self._l2_normalize(((top_vec_smallest *smallest_size) + (top_vec_most_sim * most_sim_size)) / (smallest_size + most_sim_size))
Recalculate term importances

Implementation
I think the most sensible option would be to make this part of the fit() method, as you still have access to the predicted labels.
The models could have a n_reduce_to parameter passed at initialization like this:
model = ClusteringTopicModel(n_reduce_to=10)

Additionally we could have a method that can reduce the topic when given the document-topic matrix. I think it would probably be smartest if it returned a new model instead of modifying the original one:
model = ClusteringTopicModel()
doc_topic_matrix = model.fit_transform(corpus)

reduced_model = model.reduce_topics(10, doc_topic_matrix)

To specify which method users want to use for topic reduction we should have a merging_method class attribute, with the possible values of "agglomerative_clustering", "merge_smallest"

Addressed by #8


Clarification of Modify roleDefinitionIds requirements

The roleDefinitionIds requirement states

The role defined must include all operations granted to the Contributor role.

I expected, that the role needs to have at least the same permissions as the Contributor role, as this is the way me and my team interpreted the sentence above.
We built a custom tagging policy and used the tag contributor instead. So far the policy seems to work.
Did we misinterpret the sentence or what is the reason for this requirement?

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

ID: d52df521-f6fb-6b7c-11de-7eef01d60ecd
Version Independent ID: 947c0c04-1e48-7e6f-40a3-9517294740c8
Content: Understand how effects work - Azure Policy
Content Source: articles/governance/policy/concepts/effects.md
Service: azure-policy
GitHub Login: @davidsmatlak
Microsoft Alias: davidsmatlak

#assign:davidsmatlak
#label:"product-question"
#label:"triaged"

@QBY-ThimoLimpert Thanks for your question. I'll refer it to the product team and post an update when more information is available. I created a backlog work item so I'm closing this issue.

#please-close

The response I received to your question was that there might be edge cases where a custom policy checks tags and possibly other properties. For example, the Tag Contributor role might not have Read access to the other property. The article states to use Contributor role to prevent that type of situation.

Thank you for your fast response!
So it does not need to contain all permissions of Contributor, it is just a recommendation to avoid issues? When we only got a policy working at tags, I think it is reasonable to use Tag Contributor to use least privilege?

Using the Contributor role is the recommendation but you can choose to use a different role if that works for your situation. If you have more questions, please contact Azure Support or post a question on Microsoft Q&A.


Investigate how to further use Isabelle proofs to support static analysis

Investigated to some extent. Will explore further in the future


Output relative paths for local imports

In the common case of endpoints/foo.ts importing models/bar.ts, the
output of compile_ts_code would contain "endpoint/foo.ts", but
"file:///path/to/models/bar.ts". That is inconvenient since the
absolute paths will be different in the server.
With this patch we output "endpoint/foo.ts" and "models/bar.ts", which
is the format we want when sending multiple modules to the server.
This also fixes the output path of a top level JS file. A testcase is
included.

The code looks good.
I'm only worried about possible unforeseen consequences of mutating map.written. Any problems that could come from that?

I don't think so. Note that map comes from
let mut map = op_state.take::<DownloadMap>();

So it is not a reference. We see all uses of it.


added IAB stream documents

Hmm. These are already available at:
https://rfc.fyi/?stream=iab
I think it'd be better to add a new UX on the front page for accessing streams directly. I've created #20 for that; if you want to take a stab at it that's great, otherwise I'll try eventually.


Gh-2840: MapStore MatchedVertex inconsistent

Related issue

Resolve #2840

Ready for re-review
Can the mergers please ensure that the squashed commit message contains a reference to #3314 for the history


remove jcenter repository

jcenter is being shut down, so every project should move to mavenCentral

Thanks for your PR!


Can't configure default input device

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

Hi, I tried running SampleApp from our board in development (Ubuntu18.04).
When I look at the log, it seems that the voice capture fails.
It seems to be a problem with the ALSA device configuration, but I don't know how to fix it.
What is the expected behavior?

I want to configure ALSA to capture the voice properly.
What behavior are you observing?

The wrong device is recognized as the default device and voice capture is attempted.
Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

Our board has one sound card, and I want to configure it to capture and playback audio.

capture : hw:0,2 playback: hw:0,0

arecord -l
**** List of CAPTURE Hardware Devices ****
card 0: lgedqb0sndcard [lge,dq-b0-snd-card], device 0: CPU BE I2S0 snd-soc-dummy-dai-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: lgedqb0sndcard [lge,dq-b0-snd-card], device 1: DSP HOSTLESS snd-soc-dummy-dai-1 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: lgedqb0sndcard [lge,dq-b0-snd-card], device 2: DSP PDMMIC snd-soc-dummy-dai-2 []
Subdevices: 1/1
Subdevice #0: subdevice #0
aplay -l
ubuntu@DQ1:~/my_project/build$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: lgedqb0sndcard [lge,dq-b0-snd-card], device 0: CPU BE I2S0 snd-soc-dummy-dai-0 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: lgedqb0sndcard [lge,dq-b0-snd-card], device 1: DSP HOSTLESS snd-soc-dummy-dai-1 []
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: lgedqb0sndcard [lge,dq-b0-snd-card], device 2: DSP PDMMIC snd-soc-dummy-dai-2 []
Subdevices: 1/1
Subdevice #0: subdevice #0
I made an $HOME/.asoundrc like this:
pcm.!default {
        type asym
        capture.pcm "mic"
        playback.pcm "speaker"
}
pcm.mic {
        type plug
        slave {
                pcm "hw:0,2"
        }
}
pcm.speaker {
        type plug
        slave {
                pcm "hw:0,0"
        }
}

I tried to capture and play my voice using aplay and arecord, which worked fine.
arecord -t raw -r 16000 -f S16_LE -c 1 -d 5 111.pcm
aplay -t raw -r 16000 -f S16_LE -c 1 -B 1 111.pcm

I start Samplee App after enabled Portaudio log and I saw [default] device set as default input/output.
I don't know the [default] device come from.
before paHostApiInitializers[0].
ALSA version (build): 1.1.3
ALSA version (runtime): 1.1.3
BuildDeviceList: Ignoring ALSA plugin device [cards] of type [unknown]
BuildDeviceList: Found plugin [sysdefault] of type [unknown]
....
........
BuildDeviceList: Found plugin [spdif] of type [unknown]
BuildDeviceList: Found plugin [hdmi] of type [unknown]
BuildDeviceList: Found plugin [dmix] of type [unknown]
BuildDeviceList: Ignoring ALSA plugin device [dsnoop] of type [unknown]
BuildDeviceList: Found plugin [modem] of type [unknown]
BuildDeviceList: Found plugin [phoneline] of type [unknown]
BuildDeviceList: Ignoring ALSA plugin device [hw] of type [hw]
BuildDeviceList: Ignoring ALSA plugin device [plughw] of type [plug]
BuildDeviceList: Ignoring ALSA plugin device [plug] of type [plug]
BuildDeviceList: Ignoring ALSA plugin device [shm] of type [shm]
......
.........
BuildDeviceList: Found plugin [default] of type [asym]
BuildDeviceList: Found plugin [mic] of type [plug]
BuildDeviceList: Found plugin [speaker] of type [plug]
BuildDeviceList: Filling device info for 23 devices
FillInDevInfo: Filling device info for: lge,dq-b0-snd-card: - (hw:0,0)
2020-09-08 07:59:03.379 [  5] 9 LibCurlHttpContentFetcher:transferThread::end
2020-09-08 07:59:03.379 [  5] 9 LibCurlHttpContentFetcher:stateTransition:oldState=FETCHING_BODY,newState=BODY_DONE:State transition
GropeDevice: collecting info ..
GropeDevice: collecting info ..
Default input device: lge,dq-b0-snd-card: - (hw:0,0) hw:0,0
Default output device: lge,dq-b0-snd-card: - (hw:0,0)             --> eunjung: default input & output device added here.
FillInDevInfo: Adding device lge,dq-b0-snd-card: - (hw:0,0): 0
FillInDevInfo: Filling device info for: lge,dq-b0-snd-card: - (hw:0,1)
GropeDevice: collecting info ..
GropeDevice: collecting info ..
FillInDevInfo: Adding device lge,dq-b0-snd-card: - (hw:0,1): 1
FillInDevInfo: Filling device info for: lge,dq-b0-snd-card: - (hw:0,2)
GropeDevice: collecting info ..
GropeDevice: collecting info ..
FillInDevInfo: Adding device lge,dq-b0-snd-card: - (hw:0,2): 2
FillInDevInfo: Filling device info for: sysdefault
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
FillInDevInfo: Adding device sysdefault: 3
...
......
FillInDevInfo: Filling device info for: mic
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
FillInDevInfo: Adding device mic: 4
FillInDevInfo: Filling device info for: speaker
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
FillInDevInfo: Adding device speaker: 5
FillInDevInfo: Filling device info for: dmix
GropeDevice: collecting info ..
FillInDevInfo: Adding device dmix: 6
FillInDevInfo: Filling device info for: default
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
GropeDevice: collecting info ..
GropeDevice: Limiting number of plugin channels to 128
Default input device: default default
Default output device: default           --> eunjung: default input & output device added again.
FillInDevInfo: Adding device default: 7

Listening is displayed in the Sample App, so even if you input a voice, it goes to idle without any data captured on the log.  All of bytesRead was 0.
After modifying the PortAudioMicrophoneWrapper.cpp code to use PaDeviceIndex 2 arbitrarily in initialize() function, the voice was captured normally and I was able to talk with Alexa. (PaDeviceIndex 2 means hw: 0,2 as shown in Portaudio log)
I want to know how to configure ALSA to use hw:0,2 as default input device.
What version of the AVS Device SDK are you using?
  <1.20.1>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[ O] Other - tell us more:

Tell us about your OS (Type & version):

[O ] Linux - Ubuntu18.04
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @ejlim81,
Can you take a read through some of these resources and see if they can help resolve your problem?

https://wiki.archlinux.org/index.php/Advanced_Linux_Sound_Architecture#An_example_of_setting_default_device_using_"defaults"_node
https://www.alsa-project.org/wiki/Asoundrc

Closed due to inactivity. Please open a new issue if this continues to be a problem.


Proposed: special handling of external redirect

I was recently trying to write a test for an app that redirects to an external URL. As it turns out, Rack::Test processes the redirect in the app itself which may result in unexpected behavior.
Here's an example: https://gist.github.com/iamvery/44c553d88d4ae9402fd7. I wouldn't expect the redirect to render the /:place route.
I'm not confident I understand enough about Rack::Test to offer any definitive solutions, but one idea that comes to mind would be to have an error raised for any request processed to an "external" URL (for some definition of external).
Some other references:

http://stackoverflow.com/questions/2297497/cucumbercapybara-problem-with-a-scenario-that-redirects-the-browser-outside-of
https://github.com/jnicklas/capybara/issues/1388

Have you tried without capybara and just using follow_redirect to see what it does?

No feedback received from @iamvery - closing for now, feel free to reopen if there is still an issue without capybara.

Thanks for following up. This is such an old issue that it's no longer applicable for me. I'll definitely try to remember to reopen the discussion if it comes up again. Thank you!


Prevent parse.form from including query string

Is there a quick way (i.e. option setting) to prevent the query string from being included in the parsed output of a form-data body?

we didn't include query string when parse form body,  https://github.com/cojs/co-body/blob/master/lib/form.js#L46  the second argument queryString is the configurations of qs to parse the request body.


I found a text error on an article page

I found a text error on an article page written by you in the "Contributors Who Open the Most Non-Duplicate Issues" section of the first contributor "Qantex", but changed the name to "Avdax" a few days ago.

 https://github.com/microsoft/terminal/issues/5245#issuecomment-609961617
Link: https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-11-release/

The article was written by
Kayla Cinnamon

We are not going to update old blog posts because somebody changed his name after the blog post was released. Sorry.

Thanks for the report! :smile:

It's okay but what is about j4james

Oh, my bad. I'm sorry.

(Sorry that I was curt!)

That's not a problem! :)


Support tools for SRML

In modules folder there is a support folder which needs documention

https://github.com/paritytech/substrate/issues/1981

I can tackle this @shawntabrizi @AmarRSingh .

@Kianenigma please assign yourself to both issues :)
You will probably need to come up with your own template of sorts since support is quite different.
Just get the data written down, and we can iterate on format later :)

I'll give up on this in case someone wants to take over in favor of time + it is not a priority. Some components in the support (storage, macros etc.) have already been documented as well.

My understanding is that this issue is for a page on substrate.dev, not reference docs. The reference docs are pretty complete already.
I'd like to get at least some common understanding of what this issue is asking for before I make a big PR. Here are some observations
Some support macro related content lives https://substrate.dev/docs/en/runtime/substrate-runtime-module-library#support-macros. Should this content be moved, or duplicated into the new page?
@shawntabrizi I believe you suggested that this page replace both of

https://substrate.dev/docs/en/runtime/macros/construct_runtime
https://substrate.dev/docs/en/runtime/macros/decl_module
That sounds like the opposite plan of what's implied by all of the [here] (Coming Soon) links
I prefer to leave at least the section about when to use which runtime types in tact.

@JoshOrndorff This is probably duplicate effort with the larger documentation of the macros and a single page talking about the macros.
Coming soon links can point directly to the reference docs where applicable.
When to use each runtime type might make the most sense in the reference docs since those types may change over time. But I defer to make that decision based on how you want to structure the final content.


shooting game scratch

I am a 8th class student and I have developed this shooting game in scratch

Great work


feat: Support analyze with sample automatically

Proposed changes

Analyze with sample automatically when table size is greater than huge_table_lower_bound_size_in_bytes(5G by default).


Missing exclamation mark on if statement in PlayerLifecycleHelper.cs

Affects: Release v0.2.4

Description
Hi! Sorry if I'm wrong on this, however, in PlayerLifecycleHelper.cs , I saw what should be an error in PlayerLifecycleHelper.IsOwningWorker() (line:36) :
if (entitySystem.GetEntitiesInView().Contains(entityId))
{
                throw new InvalidOperationException(
                    $"Entity with SpatialOS Entity ID {entityId.Id} is not in this worker's view");
}

An entityId found will throw the error since HashSet<T>.Contains() return true if something is found :
https://docs.microsoft.com/en-us/dotnet/api/system.collections.generic.hashset-1.contains?view=netframework-4.8#System_Collections_Generic_HashSet_1_Contains__0_
Link of the line :
https://github.com/spatialos/gdk-for-unity/blob/36cf14b1a230b37a1603b2a034a92f13e01b6086/workers/unity/Packages/com.improbable.gdk.playerlifecycle/PlayerLifecycleHelper.cs#L36
Workaround
shouldn't it be :
if (!entitySystem.GetEntitiesInView().Contains(entityId))
In other words, adding the missing exclamation mark would simply fix it.
PS: I'm not used to GitHub, and sorry for my english.

Hey @TagXy thanks for the report! I've submitted a fix for this in #1027 and added some test cases to cover this sort of thing.
This fix should be released in v0.2.5

This bug was released yesterday in 0.2.5!


A few improvements to the Tabs component

Enables using the mousewheel to scroll through the tabs
Brings the active tab into view when it changes
Includes the icon in the clickable area of the tab
Simplifies tabInfo by adding editorId and removing the properties that were precomputed based on it, active, onClick and onClose.

Depends on https://github.com/revery-ui/revery/issues/579 to fix tabs overflowing

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @glennsl ,
Sorry - realized the CI was busted for this change! I'll merge up master for this and re-kickoff the CI.
So excited to have this in 🎉

Oh - looks like I need to bring in the overflow Revery fix to it. Looking into that.

Found and fixed an additional overflow issue: https://github.com/revery-ui/revery/pull/599
Brought it in; I'll merge up and this should be good-to-go! 👍

Green now - thanks @glennsl for the incredible contribution! 🎉


Button to create a QR code for the currently selected tab

It would be pretty convenient. You click a button, and it generates a qr code for the URL of whatever tab you have selected at the moment.
I wouldn't mind implementing it if you assign the issue to me

It would be pretty convenient. You click a button, and it generates a qr code for the URL of whatever tab you have selected at the moment. I wouldn't mind implementing it if you assign the issue to me

yeah sure go ahead sounds really interesting!


Amazon urls response 503

Hello,
Lately I've noticed that when trying to crawl amazon urls the crawler is getting 503 status code in response and emits fetch error. I've tried getting to the urls manually and it all worked fine. It all worked perfect till last month. The crawler version I'm using is - 1.0.1
Here's a code snippet which rarely works now:
var crawler = new Crawler("http://www.amazon.com/ZenFone-Laser-Unlocked-Smartphone-Storage/dp/B015AH8TQE%3Fpsc%3D1%26SubscriptionId%3DAKIAJLBZH5H3HZQ5IYDA%26tag%3Driviere-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3DB015AH8TQE");
    crawler.maxConcurrency = 1;
    crawler.decodeResponses = true;

The response from the fetch error event is:

Hi @Alon-Katz — thanks for filing an issue. Had you been using 1.0.1 previously, and it had been working fine?

Afais that's one of Amazons' many bot protection features.
Some of the things you could do:
Scrape slower. Introduce some randomness. Use a Common, modern User-Agent. Use multiple IPs.
(But of course you won't b/c scraping data from Amazon is against their TOS. So instead you are going to use the [https://affiliate-program.amazon.com/gp/advertising/api/detail/main.html](Amazon Product Advertising API), I'm sure  ;)

Thanks for the information, I tried using the api but its missing the most basic option, to know the stock
of an item so you wont publish out of stock items in your webiste :(
Hi @cgiffard :), I have been using an older version around the 0.6.2 and when I started geting
the 503 I have upgraded to the latest, but as @Abromeit said its amazon bot protection :(
btw the crawler is amazing, thanks for all the hard work.

Best thing to do would be to try and change the user agent to something believable. Thanks for filing an issue anyway!


Endless stream of errors in 2.1rc1 high DPI

On Windows 10, v2.1rc1, high dpi 2K display:
Launching the old Godot 2.0.x works fine. Completely not working in 2.1rc1. I get an endless (literally) stream of errors in the terminal that opens with Godot.
Set Godot to launch in high DPI mode in the settings, relaunch, and this should happen (never works again). I am on a 2736x1824 at 267 PPI display.
Error dump on gist
I should note that after ~8 mins it opens the project manager, when selecting a project it completely crashes!

Looks related to either the libpng update or the asset library...

Or the 2x png images are bogus.

Aight, I spent this morning trying to fix this without success. I tried disabling high DPI scaling, and this time I didn't get any errors, it just crashed. Same results when using Windows Troubleshooter. It seems the 'hi dpi' setting is stored somewhere else like in the registry/appdata & I can't make it go away (even though I'd love me some high DPI). Guess I'll be using the older version for now! Tell me if I could be of any help.

On Windows, the editor settings are located in C:\Users\USERNAME\AppData\Roaming\Godot\editor_settings.tres.
As a workaround to change back to LoDPI mode for now, you'll want to change
global/hidpi_mode = 2

to
global/hidpi_mode = 1

Or the 2x png images are bogus.

That seems to be the case. Here is a section of the generated header for HiDPI (all of them have the same data):
static const unsigned char icon_add_track_hidpi_png[]={
0x89,0x50,0x4e,0x47,0xa
};

Now, why this affects only Windows? Since this data is generated by a Python script, what could be different in the platform?


tests: drivers: bbram: refactoring

Refactored to use a single prj.conf file.

The tests are failing. It's a bit challenging to debug because 1) I cannot run Twister on my Windows machine, and 2) I am not familiar with yaml and how the tests are setup/executed. I was hoping the refactoring would be as easy as replicating the structure from one of the other tests (drivers/flash), so I gave it a shot.

Sorry for all of the extra reviewer requests. My PR got a bit messy as I made a couple mistakes during my interactive rebasing. It's all sorted now.
@nashif and @erwango I misunderstood the real problem described of the @erwango's issue. This resulted in me doing too much refactoring while not fully understanding how things worked resulting in some test build errors. When I re-read @erwango's issue, I realized what was required and simplified things. Everything seems to be working now now, so the review can continue.

Can anyone tell me what the "footprint delta" is and why it might be failing? Happened after rebasing with master.


fix bug about pixel overlap of adjacent tiles

Description

Types of Changes

[ ] Core
[x] Bugfix
[ ] New feature
[ ] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

Fixes:
https://github.com/histolab/histolab/issues/370

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi @nipeone, congrats on your first contribution to Histolab 🎉

but if i create new PR,need i create unit test about this issue?

For this issue, an integration test would be better. Please note that we are testing the Tilers using the locate_tiles method (better to visualize, easier to test) https://github.com/histolab/histolab/blob/master/tests/integration/test_tiler.py#L331
So you could write a new test using only 1 or 2 fixtures following the test structure of it_locates_tiles_on_the_slide and changing the value of the parameter pixel_overlap.
Of course, if you need guidance on this we are here ❤
Alessia

so sad,it's a little hard to me add integration test in test_tiler.py,  i have tried.

so sad,it's a little hard to me add integration test in test_tiler.py,  i have tried.

Hey @nipeone, I added the missing integration test, no problem.
@ernestoarbitrio however, this PR will fail again for the same reason as #371

Hey @nipeone, I added the missing integration test, no problem.
@ernestoarbitrio however, this PR will fail again for the same reason as #371

now it should be ok

Hey @nipeone, I added the missing integration test, no problem.
@ernestoarbitrio however, this PR will fail again for the same reason as #371
that's great!!!


cras_ros_utils: 2.3.0-2 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cras_ros_utils to 2.3.0-2:

upstream repository: https://github.com/ctu-vras/ros-utils
release repository: https://gitlab.fel.cvut.cz/cras/ros-release/ros-utils.git
distro file: noetic/distribution.yaml
bloom version: 0.11.2
previous version for package: 2.3.0-1

cras_cpp_common
* Increased minimum CMake version to 3.10.2.
* log_utils: Fixed a potential segfault when instances of MemoryLogHelper get recycled.
* Contributors: Martin Pecka

cras_docs_common
* Increased minimum CMake version to 3.10.2.
* Contributors: Martin Pecka

cras_py_common
* Increased minimum CMake version to 3.10.2.
* Contributors: Martin Pecka

cras_topic_tools
* priority_mux: Added possibility to send a message just before disabling a topic.
* shape_shifter: Improved getHeader().
* Increased minimum CMake version to 3.10.2.
* priority_mux: Total rewrite, now it should really work.
* Contributors: Martin Pecka

image_transport_codecs
* Increased minimum CMake version to 3.10.2.
* Contributors: Martin Pecka

@peci1 This is only a debian increment suggesting that the upstream package wasn't released before this was bloomed. Is that what you intended?

Ooops, I forgot to push to the public repo before blooming. I'll send a new PR.


⚠ Bofrost.be has degraded performance

In 02a2bc3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 804 ms

Resolved: Bofrost.be performance has improved in 32cfa89.


storage: avoid buffer bleed when reading past the end of the file

bytes_read == 0 is an EOF condition. If we failed to read anything, better to zero out the buffer explicitly, like we do for other failure cases, so that the caller doesn't see "garbage" data that was there before.
This shouldn't matter in practice, as the caller always verifies the checksum anyway, but still feels like a good defense in depth.

Found this one live at https://youtu.be/THWDx_RyZ6A!


fix nitro cors handling

#44  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @techwithanirudh and the rest of your teammates on  Graphite

Merge activity

Nov 6, 4:34 AM EST: A user merged this pull request with Graphite.


[ParseableInterface] Distinguish SDK and non-SDK dependencies

Honor -track-system-dependencies when building swiftinterfaces into swiftmodules on demand, then start distinguishing SDK and non-SDK dependencies to allow for relocating SDKs.
One interesting thing here is that the decision of whether or not to track system dependencies ends up going into the cache key for a swiftmodule built from a parseable interface, because it affects that module's up-to-date check. If we didn't include -track-system-dependencies in the cache key, we could end up tracking system dependencies for some modules but not others in the same build.
There's a bit of a bug here where -track-system-dependencies is not honored if the top-level invocation isn't tracking any dependencies, but given how uncommon this flag and that situation are in practice that's probably okay for now.
Still TODO: honor this for -build-swiftmodule-from-parseable-interface as well. That's currently not tracking dependencies at all and it probably should.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - d6fd413d3c0cbd64d71ca11bdfc549d2efd8ba4c

Build failed
Swift Test OS X Platform
Git Sha - d6fd413d3c0cbd64d71ca11bdfc549d2efd8ba4c

Can you also update the comment in ModuleLoader.cpp that says we currently don't pass true for system dependencies?

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 092a85b093a9b1622384dcf98af5ef5e0cda8bf9

Build failed
Swift Test OS X Platform
Git Sha - 092a85b093a9b1622384dcf98af5ef5e0cda8bf9

The tests probably need to be updated.

@nathawes picked this up in #23665.


Add QR/QL/QI in linear operator of GMI

This is a place holder to be acted on when PR#1257 is approved ...
Perhaps other MW data need similar revisions (certainly AMSR2)

I am close this in view of: https://github.com/GEOS-ESM/swell/pull/422


odo search service doesn't honor experiment flag

/kind bug
What versions of software are you using?
Operating System:
Output of odo version:
odo v1.2.2 (a15a99e)
Server: https://api.crc.testing:6443
Kubernetes: v1.17.1
How did you run odo exactly?
 odo catalog search service mysql
 ✗  unable to list services because Service Catalog is not enabled in your cluster: unable to list services: unable to get cluster serviceClassExternalName: unable to get cluster service classes: unable to list cluster service classes: the server could not find the requested resource (get clusterserviceclasses.servicecatalog.k8s.io)
[jichen@jjtest2 nodejs-ex]$ odo preference set Experimental true
? Experimental is already set. Do you want to override it in the config Yes
Global preference was successfully updated
[jichen@jjtest2 nodejs-ex]$ odo catalog search service mysql
 ✗  unable to list services because Service Catalog is not enabled in your cluster: unable to list services: unable to get cluster serviceClassExternalName: unable to get cluster service classes: unable to list cluster service classes: the server could not find the requested resource (get clusterserviceclasses.servicecatalog.k8s.io)

the list command provided different output when Experiment flag is set or not
Actual behavior
Expected behavior
Any logs, error output, etc?

/assign


[BUG] - SHFQA / UHFQA return wrongly scaled data.

Describe the bug
For an S21 measurement we expect a dip in the measurement at the resonance frequency. In the recent LabOneQ we observe a peak instead of a dip at the resonance frequency.
To Reproduce
Run S21 measurement with either SHFQA or UHFQA.
Expected behavior
A clear and concise description of what you expected to happen.
Code & Screenshots
L1Q: 1.0.0

QCCS: 0.66 (Different resonator, but behaviour effects all resonator measurements.)

Versions used:

laboneq: 1.0.0

Context

[ ] Do you know a workaround for the issue? If yes, please provide a short description. : No
[ ] Does the issue block your experiments?: Yes

It seems something changed in our configuration. VNA measurements had the same results.


Source code license clarification: language port

Hello, I'm currently looking at potentially porting the transcoder portion of the basis universal source to another language (Zig). I'd love to get some clarification on the Apache 2 license, as I'm not entirely sure how it applies in this case. Should a source port be made to have the same license, or does it just need to retain a copy of the original license, or...?

If it's a port, it should retain a copy of the original Apache 2.0 license somewhere. Any new code can be covered by your copyright/license in the port.


DataFrame Renderer

The DataFrame (formerly known as SchemaRDD) is a new core abstraction in Spark.    Major subsystems such as Spark SQL and the new Spark ML are based on DataFrames.   DataFrames are column-oriented, schematized tables.
A table-like renderer should be provided, resembling the output from DataFrame::show().  Ideally the table would be paged and capable of lazily exploring the entire contents of the DataFrame.

:+1:  having both the schema and the paginable table in two different tabs for instance?

A few words on the data types.  DataFrame supports a wide variety of column types, defined here:
https://github.com/apache/spark/tree/branch-1.4/sql/catalyst/src/main/scala/org/apache/spark/sql/types
Note that UDTs also exist, such as VectorUDT.
The DataType classes facilitate language-neutral serialization of values, both for caching purposes and for python support.
Another curiosity is column metadata or attributes.  For example, the StringIndexer transforms a column of string labels into a numerical index, with the lookup table attached as a column attribute.   Makes for useful hints to a UI.  Further information in the SPARK-4588 design doc.

Feeling ambitious?  Another feature here would be to support custom cell renderers.    Maybe the renderer would be selected based on the UDT or based on column attributes.

@EronWright cool references indeed. Very helpful when we'll start the work.
I think there is already some stuffs in the notebook that can be reused for this one.
Best is to move with small steps to have something usable quickly and then iterate on it.
what exists
The Reflector is able to take a type, deconstruct it (first level only, the heuristic is trivial atm) and returns a mapping name → value.
The reflector will be used in widgets to convert a list of objects to a list of maps (using the typeclass MagicRenderPoint).
This conversion will allow to things:

conversion to Json to be used on the client side, see here and there
define defaults charts based on the components: see here

That means that we could have something quick for both charts/table of DataFrame and auto plotting by having a conversion more generic than only for Seq, Array or Map:

here is the automatic conversions to the magic points that adds the metadata necessary for the auto plotting
there is for the auto plotting based on the container type (need to add DataFrame)

[not tested]
I  think something like this will gives us some results:
Renderer.scala

  implicit object dfAsWidget extends Renderer[DataFrame] {
    def render(x: DataFrame) = x match {
      case x if x.take(1).isEmpty => widgets.layout(0, Seq(widgets.text("")))
      case _ => display(x.take()
    }
  }

** package.scala**

Incremental progress sounds good.   But please consider, a DataFrame does not contain Scala types, it contains SQL types.    The intended way to reason about the schema is not to use reflection but to use the schema property.   The best results will come from leveraging the provided schema and column information.
Given that JSON is involved in rendering, it would probably be worthwhile to look at the JSON conversion support in DataFrame itself (start here).  Granted it converts from JSON->DataFrame (the opposite of what we need here), but for symmetry's sake an examination is worthwhile.

Mmmh indeed, so we might have more stuffs at our disposal to do something tightly coupled.
Now, only "sequences" are taken into account, so if we stick with that, we'll lose the DataFrame, schema and so on, because we'll end up with Rows :-S.
So we really need something dedicated to DataFrame, that would include maybe also a tab for the schema and one for the plan.
That leads to the conclusion that we need a dedicated display function in widgets that will create the things we can plot or simply render the content. And based on your helpful pointers, we won't need the so-called MagicRenderPoint anymore.
At first very first step we can try this out then, but simply drawing a table, because the second step will refactor the Charts to work based on a simple Json representation (or something like that)

This https://github.com/andypetrella/spark-notebook/pull/214 has been merged.
You can check sql/DataFrame.snb for some examples.
Of course, this can be extended horizontally (for instance a tab for the schema) and vertically (more charts, more customization)
@EronWright if you can give it a try, we can see what would be absolutely necessary to complete this first iteration on this?

Andy I will have a look tonight.
Sent from my phone.

From: Andy<EMAIL_ADDRESS>Sent: 6/14/2015 10:49 AM
To<EMAIL_ADDRESS>Cc: Eron<EMAIL_ADDRESS>Subject: Re: [spark-notebook] DataFrame Renderer (#200)
This https://github.com/andypetrella/spark-notebook/pull/214 has been merged.
You can check sql/DataFrame.snb for some examples.
Of course, this can be extended horizontally (for instance a tab for the schema) and vertically (more charts, more customization)
@EronWright if you can give it a try, we can see what would be absolutely necessary to complete this first iteration on this?

Reply to this email directly or view it on GitHub:
https://github.com/andypetrella/spark-notebook/issues/200#issuecomment-111855593

cool :-)
On Sun, Jun 14, 2015 at 8:07 PM Eron Wright<EMAIL_ADDRESS>wrote:

Andy I will have a look tonight.
Sent from my phone.

From: Andy<EMAIL_ADDRESS>Sent: 6/14/2015 10:49 AM
To<EMAIL_ADDRESS>Cc: Eron<EMAIL_ADDRESS>Subject: Re: [spark-notebook] DataFrame Renderer (#200)
This https://github.com/andypetrella/spark-notebook/pull/214 has been
merged.
You can check sql/DataFrame.snb for some examples.
Of course, this can be extended horizontally (for instance a tab for the
schema) and vertically (more charts, more customization)
@EronWright if you can give it a try, we can see what would be absolutely
necessary to complete this first iteration on this?

Reply to this email directly or view it on GitHub:
https://github.com/andypetrella/spark-notebook/issues/200#issuecomment-111855593
—
Reply to this email directly or view it on GitHub
https://github.com/andypetrella/spark-notebook/issues/200#issuecomment-111859552
.

Based on our discussions it'd be okay to close this one right? And directly create some enhancement tickets behind :-D
wdyt?

Closing, to open new enhancement issues.

Note that the improvements discussed above were implemented in #246.


weekly image cve patching from Sec Pipelines (kube-proxy)

What type of PR is this?

What this PR does / why we need it:
CVE found on existing images, we need to preload new versions and bump to use them
Which issue(s) this PR fixes:
this PR introduces some new kube-proxy images with CVE fixes
Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
this part of PR https://github.com/Azure/AgentBaker/pull/3249 that does not break future auto-patch
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.973%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
2544

Relevant Lines:
4105

💛  - Coveralls


Riscv re-factoring

Refactor the trap handler macro Since portasmHANDLE_INTERRUPT is removed at FreeRTOS-kernel, Riscv re-factoring (#444) (commit: 9efca75d1e) We don't need this definition anymore
We also remove the unused function definition

Styling the file header to pass the checker Remove an extra space

Description

Test Steps

Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Hi @aggarg, Thank you for assisting me in fixing the problem.

You are welcome @tony2037! Thank you for your contribution.


Feature request:  Add Input menu?

In programming, input windows are often used to collect data from users. i believe it useful.

+1
It will be so sweet...


Set connection and response timeout in milliseconds

https://github.com/rancher/rancher/issues/8944

LGTM


fpgaotsu and fpgasupdate are not found on ubuntu 20.04

Hi, I'm new to using Intel FPGA PAC.
I'm trying to install PAC D5005 on ubuntu 20.4 and Acceleration Stack. But, I can't find 'fpgaostu' and 'fpgasupdate' program.
(I know ubuntu is not officially supported, but I need it.)
I downloaded Acceleration Stack Version 2.0.1 and installed using 'setup.sh' script.
Before running the script, I changed 'is_ubuntu' to 1(encouraged by this link ). Also, I inserted a few lines for converting *.rpm to *.deb using 'alien' program.
To verify the installation, I checked the driver installation, OPAE library installation, FIM/BMC version using fpgainfo.
$sudo lsmod  | grep fpga
$sudo dpkg -l | grep opae
$sudo fpgainfo fme
The above tests can be passed.
However, some programs are missing.
I can find:
fpgabist fpgaconf fpga_crossgen fpgad fpgadiag fpga_dma_test fpgainfo fpga_libtool fpgamux
I can't find:
fpgaotsu fpgasupdate
Where can I find those programs or What package do I miss/fail to install?
thank you.

You could use
$ pip install opae-sdk/python/opae.admin

which should give you those scripts.  They are part of the opae.admin python project.

@tswhison thank you. successfully installed.

Filer was able to install the requested scripts.

did you get the intel fpga driver installed on ubuntu 20.04 successfully ?


[go_router] Check if route exists

Use case
I apologize if this already exists, I haven't been able to find anything about it!
I'd like to be able to check if a route (path?) exists. For example, I want to be able to check if '/home' is a route that is configured in my GoRouter.
Our app has banners that have links attached to them. We get these banners + links from the server and they're the same for our web app and mobile app. The mobile app is using GoRouter and I want to check if the path in the link is a valid route in our GoRouter. If it is a valid path, we can .go to it, and if it isn't a valid path we can just open the link in web view.
I've found that I can use routerInformationParser.matcher.findMatch(path) to do this. Currently, findMatch will throw an exception if the path doesn't exist so I can catch the exception and handle the non-valid path case there. I'm okay with using this for now, but I'm afraid that if findMatch changes in the future to not throw an exception (perhaps it will just return an empty list), my code will break.
If there is a better way to handle this already, please let me know!
Proposal
Add a .hasRoute(String route) method to GoRouter.

I think this can be closed as it is possible with
GoRouter.of(context).routeInformationParser.configuration.findMatch(String location);

I think this can be closed as it is possible with GoRouter.of(context).routeInformationParser.configuration.findMatch(String location);

That didn't work for me. For some reason there is a No GoRouter found in context exception thrown when I try to access it within the redirect implementation. In addition you have to check if (context.mounted) before the call to avoid the BuildContexts across async gaps warning, which doesn't make sense in this case.
As a workaround what I did is worked directly with the router instance configuration, so I added in my app.dart file the following:
final GoRouter _routerInstance = createRouter();

// TODO: routeExists implementation is a workaround to known issue: https://github.com/flutter/flutter/issues/117514
// routeExists is defined here so we can keep the router instance private
bool routeExists(String route) {
  try {
    return _routerInstance.routeInformationParser.configuration.findMatch(route).matches.isNotEmpty;
  } catch (err) {
    return false;
  }
}

I then import it in my routes.dart file and re-export it there as a utility function (see the comment in code block above).
Ugly, but does the job until this issue is resolved.

return goRouter.routeInformationParser.configuration.findMatch(route).matches.isNotEmpty;

The argument type 'String' can't be assigned to the parameter type 'Uri'. dart[argument_type_not_assignable](https://dart.dev/diagnostics/argument_type_not_assignable)

return goRouter.routeInformationParser.configuration.findMatch(route).matches.isNotEmpty;

The argument type 'String' can't be assigned to the parameter type 'Uri'. dart[argument_type_not_assignable](https://dart.dev/diagnostics/argument_type_not_assignable)
(3.24.1)

Maybe, you could convert your location to the expected Uri like this:
final uri = Uri.parse(location);   // May throw a FormatException if invalid
GoRouter.of(context).routeInformationParser.configuration.findMatch(uri);


Add federation support

This is a draft PR which adds apollo federation support to hiku.
Union type is required to implement federation, so I've added it into hiku internals.
Federation can be implemented either as a separate package or inside hiku.
What is added:

Added Union type
Added federation support https://www.apollographql.com/docs/federation/federation-spec/
Added example for federation (example server works as a server which exposes Astronaut entity with "id" as its primary key)
Added several tests for federation (will add more if we will agree on an idea and implementation)

What is not ready:

https://www.apollographql.com/docs/federation/federation-spec/#requires
https://www.apollographql.com/docs/federation/federation-spec/#provides
https://www.apollographql.com/docs/federation/federation-spec/#external

There are some questions about the proper approach for implementing Unions.
And also this code may be written by not following hiku idioms, but I am ready to work for a better solution.
Thanks

Union type can't be added right now, as you said, this requires a lot of changes. Mostly because of how link resolvers are designed.
I think that federation can be added on top of hiku, with original resolvers. So there is no need to use FederatedResolver class.
Federation is mostly about SDL, directives and one special _entities resolver. I think that you can extend or rewrite hiku's GraphQL introspection implementation to support SDL and directives. And override Engine class to execute GraphQL query a little bit differently.
Generally hiku executes query from the root node. Here is how you can change this strategy and process specific nodes with specific ids (this is what _entities resolver should do). Replace
query_workflow.start()

with something like this
for node, node_query, node_ids in representations:
    query_workflow.process_node(node, node_query, node_ids)

where
query ($_representations: [_Any!]!) {
     # ^^^^^^^^^^^^^^^^^ node_ids
  _entities(representations: $_representations) {
    ... on Product {
      reviews {  # <-- node_query
        body
      }
    }
  }
}

After executing this query, you can access all field values in the result object. Then you will need to properly denormalize result into what federation spec expects.

Union type can't be added right now, as you said, this requires a lot of changes. Mostly because of how link resolvers are designed.
I think that federation can be added on top of hiku, with original resolvers. So there is no need to use FederatedResolver class.
Federation is mostly about SDL, directives and one special _entities resolver. I think that you can extend or rewrite hiku's GraphQL introspection implementation to support SDL and directives. And override Engine class to execute GraphQL query a little bit differently.
Generally hiku executes query from the root node. Here is how you can change this strategy and process specific nodes with specific ids (this is what _entities resolver should do). Replace
query_workflow.start()

with something like this
for node, node_query, node_ids in representations:
    query_workflow.process_node(node, node_query, node_ids)

where
query ($_representations: [_Any!]!) {
     # ^^^^^^^^^^^^^^^^^ node_ids
  _entities(representations: $_representations) {
    ... on Product {
      reviews {  # <-- node_query
        body
      }
    }
  }
}

After executing this query, you can access all field values in the result object. Then you will need to properly denormalize result into what federation spec expects.

Thanks for the response. I will try to rewrite some parts of PR and will see where it goes.
As for

I think that you can extend or rewrite hiku's GraphQL introspection implementation to support SDL and directives.
If I understand you correctly, this will allow me to add unions.. without adding actual unions ? In other words, is there are chances to implement federation without actual support of Unions ?

Thanks for the response. I will try to rewrite some parts of PR and will see where it goes.
As for

I think that you can extend or rewrite hiku's GraphQL introspection implementation to support SDL and directives.
If I understand you correctly, this will allow me to add unions.. without adding actual unions ? In other words, is there are chances to implement federation without actual support of Unions ?

Our introspection implementation wasn't written with extensibility in mind, but I'm ok to make it extensible if possible.
I'm also ok to add federation support into hiku, but I want it to be implemented on top of core functionality, with loose coupling.
Yes, I suggest you to use Union without actually adding the Union type into hiku :) Federation-aware introspection will extend original graph introspection with this:
scalar _Any
scalar _FieldSet

union _Entity = User | Product  # <-- generated from graph nodes

type _Service {
  sdl: String
}

extend type Query {
  _entities(representations: [_Any!]!): [_Entity]!
  _service: _Service!
}

directive @external on FIELD_DEFINITION
directive @requires(fields: _FieldSet!) on FIELD_DEFINITION
directive @provides(fields: _FieldSet!) on FIELD_DEFINITION
directive @key(fields: _FieldSet!) on OBJECT | INTERFACE

# this is an optional directive discussed below
directive @extends on OBJECT | INTERFACE

_entities field shouldn't be added into the graph definition, federation-aware engine should process this field by itself (as in my previous comment), because this field is very special and can't be processed as other regular fields in the graph. So in this way we don't have to add unions into our graph definition.

Our introspection implementation wasn't written with extensibility in mind, but I'm ok to make it extensible if possible.
I'm also ok to add federation support into hiku, but I want it to be implemented on top of core functionality, with loose coupling.
Yes, I suggest you to use Union without actually adding the Union type into hiku :) Federation-aware introspection will extend original graph introspection with this:
scalar _Any
scalar _FieldSet

union _Entity = User | Product  # <-- generated from graph nodes

type _Service {
  sdl: String
}

extend type Query {
  _entities(representations: [_Any!]!): [_Entity]!
  _service: _Service!
}

directive @external on FIELD_DEFINITION
directive @requires(fields: _FieldSet!) on FIELD_DEFINITION
directive @provides(fields: _FieldSet!) on FIELD_DEFINITION
directive @key(fields: _FieldSet!) on OBJECT | INTERFACE

# this is an optional directive discussed below
directive @extends on OBJECT | INTERFACE

_entities field shouldn't be added into the graph definition, federation-aware engine should process this field by itself (as in my previous comment), because this field is very special and can't be processed as other regular fields in the graph. So in this way we don't have to add unions into our graph definition.

@vmagamedov Hi. I did a complete rewrite of the federation implementation. It would be great if will take a look :)

Introspection will be extended with federation's types in a bit hacky way but this allows to keep core almost unchanged (and no unions needed)
Refactored directives in introspection, added directives to Node and Field. This is the most important change, as directives give us a lot of flexibility in how to work with graph and its items.
New federation-aware engine, handles _service and _entities queries differently
New federation-aware endpoints with custom denormalization logic
Sdl printer based on graphql ast instead of string concatenation

@kindermax Hi, impressive work, sure, I'll take a look

Would be nice to avoid having directives argument in the classes in the hiku.graph module. I'm currently thinking about some sort of metadata argument for extensibility in general, but don't see yet how to do this better. Want to have extensibility and ease of use at the same time.

Would be nice to avoid having directives argument in the classes in the hiku.graph module
For not I have no any good ideas how to do it differently

Also noticed that for example @key directive is repeatable (can be used several times for one type), but @deprecated directive is not repeatable. So, we have to figure out how to validate this during graph creation

@kindermax I think that this PR is good enough, but maybe it can be polished in the future. My main concern was the public API exposed to the users. It is harder to change API than to change/fix implementation details in the future.
I also didn't had time to completely review this PR, only partly. And I think that I'm significantly slowing down your progress. So, since this project is mainly used by one company, I think that it would be right to:

give you access rights to this repository to commit/merge/release new versions
transfer this project to the evo-company org
transfer ownership for the hiku package on the PyPI

I think that we can merge this PR and release some draft version, use this version for some time, polish public API and then after some iterations, release new version.
As for the ownership question, for now, access rights to the repository is enough for now to proceed further with the federation.
As to evo-company, I think it is a good move but I can not solely make that decision (but I will talk to evo-company org members), so we can make a decision later in another issue.

I've already sent you an invitation. Try to merge this PR to check your access rights. Then you need to update version here https://github.com/vmagamedov/hiku/blob/edcd3c177044010ecd11b1bf33fa43a40531605c/hiku/init.py#L1 and tag this commit. Release workflow should work fine.

I merged PR successfully. Thank you for you support in implementing this feature.


Provide setting for cell CSS class prefix

At the moment, the cell class is prefixed with the stringcell-tag-:
https://github.com/parmentelat/jupyterlab-celltagsclasses/blob/9dce9dc8be59c3200ba6d97f4c853cf4d5e21dc6/src/index.ts#L36
It might be convenient to allow the user to specify this via a class prefix preference setting, or perhaps set an even more general pattern as a regex.

it feels there is a one-to-one relation ship between between tag and class..
for this reason I am a bit reluctant to going this way: for example I have already written a few extensions that rely on this one,
but none of them are going to work in a context where this naming scheme is altered by configuration
what exactly would be the use case for using another naming scheme ?

Part of the reason is simply the flexibilty. I'm refactoring https://github.com/innovationOUtside/jupyterlab_empinken_extension to use this extension (which is really handy:-) for the logical cell tag to cell HTML class mapping and have previously worked in a previous namespace with a different convention.
I do appreciate the benefits of hard-coding the prefix though eg in terms of consistency. (I don't see why your other extensions would fail though if the the default was to the current value?)

what I'm saying is, if I ship extension A that relies on the current scheme, and you ship extension B that needs to change the setting, then extensions A and B will be unable to run together (because the css rules that come with A will no longer trigger)
so imho it's better if you align your extension on the current hard-wired scheme
I understand it is painful, but otoh it's a finite change, as it does not impact the notebooks that rely on your extension
is that a convincing enough argument ?


docs: The "Introduction to Storybook" doc needs improvement

The document could be improved for clarity.
The heading tags are not used consistently. An h2 tag was used for the header, and another h2 tag was used for the subheader. The correct usage would be to use an h2 tag for the header and an h3 tag for the subheader.
There is a typo that needs to be corrected.

.take

.fixed


Adds more documentations around ignoreSemantics deprecations.

migration guide update https://github.com/flutter/website/pull/9124
fixes the concerns in https://github.com/flutter/flutter/pull/120619
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

How will that render for the various places that use the macro, compared to the place that declares it?
(To put it another way, I recommend auditing all the places in the codebase that mention flutter.widgets.IgnorePointer.Semantics. I see eleven. From a quick inspection, I expect this PR will result in some of those places not being as clear as we would like. In general when editing a macro one should always verify how it affects all the places that use the macro.)

@Hixie i rewrote some of the doc, PTAL


check remaining subKey

incorrect returned value if we have subkeys

I think this was addressed here: #74


gnu(6480)=16551

GAP      e403849e47a7bdf008c9406a15912559fe2e9f8c
GrpConst 2.5
Runtime: 26242640 ms
Isomorphic groups eliminated

Thank you for submitting new gnu(n). We will recalculate it and add to the database if we get the same result.
Checklist for the reviewer:

[ ] checked and assigned labels "new (n<50000)" or "recomputation", if needed
[ ] set "replication needed" label (unless it starts immediately)
[ ] changed it to "replication in progress" label when the replication has been started
[ ] changed it to "replicated" after successful replication review
[ ] reproducible value of gnu(n)
[ ] no essential runtime differences
[ ] sufficient level of technical details

Checklist for the maintainer:

[ ] correct arguments of commands to store data
[ ] correct location of new line in the data file
[ ] mention reviewer in the commit message

gnu(6480)=16551
GAP      4.8.3
GrpConst 2.5
Runtime: 19859109 ms (5.52 hrs)
Isomorphic groups eliminated
Replicated by @alex-konovalov on Ubuntu 16.04 on Azure cloud standard DS13 v2 instance (8 cores, 56 GB memory)


Feature/us107 log in

This is not to be merged until we have acceptance tests for this.

Apart from Russ's comment, looks good.

Acceptance tests are working now

My comments have now been actioned. Just need to tidy up the commit history then all good to go.


Failed to setup

I've been using this integration for about a week with no issues, but yesterday, it began to fail. I can't recall the timing of when I began to see the error and when I upgraded to HA Core 2022.10
Error setting up entry<EMAIL_ADDRESS>for ha_hatch
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 365, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/ha_hatch/__init__.py", line 65, in async_setup_entry
    _lazy_install()
  File "/config/custom_components/ha_hatch/__init__.py", line 54, in _lazy_install
    raise RequirementsNotFound(DOMAIN, [pkg])
homeassistant.requirements.RequirementsNotFound: Requirements for ha_hatch not found: ['hatch-rest-api==1.13.2'].

I tried rerunning the integration and am receiving a 500.
Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 148, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 71, in post
    result = await self._flow_mgr.async_init(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 225, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 243, in _async_init
    flow = await self.async_create_flow(handler, context=context, data=data)
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 822, in async_create_flow
    flow = handler()
  File "/config/custom_components/ha_hatch/config_flow.py", line 68, in __init__
    _lazy_install()
  File "/config/custom_components/ha_hatch/__init__.py", line 54, in _lazy_install
    raise RequirementsNotFound(DOMAIN, [pkg])
homeassistant.requirements.RequirementsNotFound: Requirements for ha_hatch not found: ['hatch-rest-api==1.13.2'].

Same here

I'm having the same issue, I opened a ticket with the repo that created our work around https://github.com/qqaatw/aws-crt-python-musllinux/issues/1  Looking into other solutions while I wait to hear back from them

v1.9.1 released with custom work around derived from qqaatw's work around, it takes a few minutes to finish installing but does like the old manual scripts did but automatically.  It over uses the ui thread so be patient on first start as it will appear to be unresponsive for a few minutes while the dependencies are installed.

Thanks Brendan. That seemed to do the trick!


Guidance: How to make an external link which also has geo information

Great plugin!
I am trying to make a link to something external, and also have geo information about it. Imagine a page called "Museums".
If go with something like this.
-  [221b Baker Street](geo:51.5238,-0.1588) [museum](https://www.sherlock-holmes.co.uk/)

Then everything shows up on a map as a pin with a nice title, but queries to find titles to links in my documents all come back as "museum". Also it means my "named" links across my vault are not consistent as some open locations and some websites.
I can get close with something something like:
-  [221b Baker Street](https://www.sherlock-holmes.co.uk/)  [geo](geo:51.5238,-0.1588)

This gives me a nice named link, with a link to the museum website, and everything shows up on a map as a pin. :+1: . But, the map pins are all titled "Museums" "geo".
Can I say something like "Add a geo tag, but when hovering over it (or deriving data from it), calculate and show the "previous link in the document" as the popover name?" ie, when hovering, show "221b Baker Street"?
Hope I half explained that... Thanks!

Not sure I'm following exactly. You have two completely separate links
221b Baker Street
geo
How about
221b Baker Street 221b Baker Street

Yes, I think the latter ultimately gives what I am looking for, but it is a shame to duplicate the title. I suppose I am looking for something like this, but I don't think it exists:
 [221b Baker Street](https://www.sherlock-holmes.co.uk/,geo:51.5238,-0.1588)

The above does not work of course, I don't think that's possible as a limitation of Markdown. I wonder if Obsidian has any other way to pack in more than one "fact" into a markdown link. If not I will go with one of the other options. Thanks for the quick response!


added ipv4net and uri

Added IPv4 network
Removed IPv4 that is part of IPv4 network from IPv4 result
Added URI extract

Looks good - merging.


Use native django search functions

Site views seems not work, but I don't want solr or haystack functionalities, I'm looking to use native django search functions
https://docs.djangoproject.com/en/4.0/ref/contrib/postgres/search/
I've temporary fixed showing all products adding this line to :
		search_context['products'] = Product.objects.all()
https://github.com/django-oscar/django-oscar/blob/ffcc530844d40283b6b1552778a140536b904f5f/src/oscar/apps/catalogue/views.py#L147
before      ctx.update(search_context).
This will show all products when calling URL http://host/catalogue/

To fix Categories filter add :
        search_context['products'] = Product.objects.filter(categories=kwargs['pk'])
before the line:
https://github.com/django-oscar/django-oscar/blob/ffcc530844d40283b6b1552778a140536b904f5f/src/oscar/apps/catalogue/views.py#L209
This will show all products in category when calling URL http://host/catalogue/category/slug/
Originally posted by @Summer88 in https://github.com/django-oscar/django-oscar/issues/2263#issuecomment-1013128288

Can you elaborate more on reproducing this issue? Which search engine did you use. I assumed you were using solr search engine, but did you update the index before searching the products?

I'm not using solr at all, I've just stumbled in this old issue and solved this way:
https://github.com/django-oscar/django-oscar/issues/2263
At time of first writing of django-oscar maybe the fulltext search in django wasn't available, but now I believe this can be an option, to remove the need of third party components at all.


Modified simulation to avoid most rotation errors and added flags  to check simulation

New variable to test in unit test.
The data volume in Root file and in pkl file + number of points in both files .

Looks fine ..


No data after import

Hi!
I have 2 elastics on same Win7Pro machine, 1.6 version and 2.3.4 version. Knapsack on both of them. I want to copy data from one index to the other.
Export went well. I have data in a folder.
Are these file names (null\null) ok by the way?
c:\Users\KarolGo\AppData\Local\Temp_tc\ikomunikator.tar\ikomunikator_settings\null\null
c:\Users\KarolGo\AppData\Local\Temp_tc\ikomunikator.tar\ikomunikator\message_mapping\null
Import failed. No indicies created. No mappings created for incoming data. No data was imported from archive.
My log entry:
[2016-08-08 12:12:00,755][INFO ][KnapsackImportAction     ] start of import: {"mode":"import","started":"2016-08-08T10:12:00.755Z","path":"file:///C:/elasticsearch-2.3.4/logs/ikomunikator.tar.gz","node_name":"Sigmar"} [2016-08-08 12:12:00,888][INFO ][KnapsackImportAction     ] end of import: {"mode":"import","started":"2016-08-08T10:12:00.755Z","path":"file:///C:/elasticsearch-2.3.4/logs/ikomunikator.tar.gz","node_name":"Sigmar"}, count = 3494
Can anybody tell me what is wrong with my importing process?

You edited the message: high disk watermark [90%] exceeded
This the reason why Elasticsearch does not accept any data. It's not a knapsack problem.


Crash in getReturnTypeFromBody during getSemanticDiagnostics

This repro's on master, but not release-1.4:
interface I {
    [s: string]: (p: string) => number;
    func(p: string): number;
}

var x: I = {
    func(
}

TypeError: Unable to get property 'kind' of undefined or null reference
at getReturnTypeFromBody (:12563:13)
at checkFunctionExpressionOrObjectLiteralMethod (:12644:29)
at checkObjectLiteralMethod (:13061:13)
at checkObjectLiteral (:11898:25)
at checkExpressionWorker (:13128:21)
at checkExpressionOrQualifiedName (:13088:17)
at checkExpression (:13080:13)
at checkExpressionCached (:13046:17)
at checkVariableLikeDeclaration (:13842:21)
at checkVariableDeclaration (:13865:13)
at checkSourceElement (:14732:21)
at forEach (:575:17)
at checkVariableStatement (:13873:13)
at checkSourceElement (:14703:21)
at forEach (:575:17)
at checkSourceFile (:14841:17)
at getDiagnostics (:14872:17)
at getSemanticDiagnostics (:24805:13)
at Anonymous function (:28054:17)
at simpleForwardCall (:27951:9)
at forwardJSONCall (:27965:13)
at forwardJSONCall (:27996:13)
at getSemanticDiagnostics (:28053:13)

Simplified repro
interface I {
    func(p: string): number;
}

var x: I = {
    func(
}


Midi Music not working

where can i download these uo files?

which file do you need? I will upload it

where can i download these uo files?

which file do you need? I will upload it

the whole uo folder

the whole uo folder

i sended you a email with the link with the folder files
email<EMAIL_ADDRESS>

https://github.com/sinshu/meltysynth/blob/main/MeltySynth/src/MidiFile.cs

what do you mean with this code?

the music on the game is in the .mid.
Can read the clietn .mid?

the midi files requires a way to translate them, that was linked by @andreakarasho, but also requires a sample database sound, since in the midi you only have simple choords and notes, but without any real sound...if you want midi, it will be a lot complicated, since most OS in modern PCs doesn't have any sample ready to use. So this is kinda pointless.

the midi files requires a way to translate them, that was linked by @andreakarasho, but also requires a sample database sound, since in the midi you only have simple choords and notes, but without any real sound...if you want midi, it will be a lot complicated, since most OS in modern PCs doesn't have any sample ready to use. So this is kinda pointless.

I believe that in the old versions of the client midi files were used (I'm not sure)
if the client is to be compatible with all the latest versions maybe it should be implemented

the .mid or .midi files contains only the map of the tones used + the instrument to use (codes) + tempo, there isn't any sound in them, to make them work you'll need to install some midi database or instrument database in your pc, since midi aren't used anymore in modern computers

in my opinion if the idea is to make the client compatible with all versions without the need to modify the game files while keeping all the original files, it must be there in my opinion.
If it is really not convenient to implement it because it is not efficient, it should notify the user of the problem, in case someone tries to use the client with an old version of the latest online.
what do you think?


[ZEPPELIN-5569] Implement onError

What is this PR for?
This PR implement OnError, which is necessary to cleanup the connectionManager, if possible.
What type of PR is it?

BugFix

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-5569

How should this be tested?

I have done some manual testing, but it is difficult to test this case.

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

If no other comments are received, I will include this PR in the master on Friday.


a lot of changes

Uses less code.
Removes unneeded variables.
Stops relying on third-party libraries. (Copies text using tkinter).
New README.
Fixes an issue where links would not be converted if they did not contain "?usp=sharing" at the end.
(you'd need to also change the "latest download" button in the README)

That's amazing, thank you so much.


WIP: Add support for FIPS compliance

Also restricts all TLS config to FIPS-approved settings.
Note : We (Author of this commit, Datadog Inc. or Cilium Maintainers) are not making any statements or representations about the suitability of this code in relation to the FIPS 140 standard. Interested users will have to evaluate for themselves whether the code is useful for their own purposes.
Fixes: #23919

Hi @hemanthmalla, thanks for the PR. I have some concerns about this change from a maintainability perspective. FIPS compliance is complicated, and while the change may enable compliance for certain aspects of Cilium’s functionality, there are a lot of other features that would not be covered.
Two examples that come to mind are Wireguard (as far as I’m aware there’s currently no way to run Wireguard in a FIPS-compliant manner) and our L7 proxy functionality (Envoy could be run in FIPS-compliant mode, but not in the manner that we distribute it by default). I expect there are similar issues in other parts of Cilium’s functionality.
My concerns are twofold:

Users who see a build tagged with -fips may not understand the full relationship between the features they enable and FIPS compliance, which could cause significant issues for users deploying into regulated environments.
I’m not sure that the project has the bandwidth to support such users if they have questions over FIPS compliance, or to maintain documentation that covers FIPS compliance on an ongoing basis.

If the project is unable to state anything affirmative about FIPS compliance, I am unsure of the value of creating these builds, which could give a false impression of compliance guarantees to users.

@ferozsalam I understand the concerns mentioned. There are definitely a lot more aspects that aren't covered in this PR (on top of the features you mentioned) and was no way meant to be exhaustive. The PR isn't ready for review as well, I'm still exploring the feasibility.
If you take a closer look at the diff, I'm not proposing changes to the release workflow, so we will not be publishing images tagged as FIPS. My intention was to run a single e2e test when compiled with the boringcrypto bits, so that when we add a change in the future that may not be compatible with boringcrypto, we'd get early feedback. We could still decide on ignoring the test failure.
I was thinking of only providing make targets as a starting point for users interested in building their own images. Definitely open to any other feedback if we think that may not be a good idea. I could also rename the CI images to boring instead of fips.

/ci-e2e-upgrade


Starting simulation Date (SDATE) issue when running in batch file mode

Because of the Y4K_DOY subroutines the source code was changed to run under certain conditions and ranges of weather data. Fortunately, an issue was found when running BatchFiles.v48 and your SDATE's differ from each other. This is triggering a condition that stops the model. For example:
EXPE0001.MZX = SDATE -> 21050
EXPE0002.MZX = SDATE -> 21050
EXPE0003.MZX = SDATE -> 21048   <- Triggers an error that date is lower than SDATE.
The reason that could explain this is an error on MAKEFILEW subroutine that is not updating properly SDATE or only updating when it opens the weather file to check the weather date range. For this reason  it needs to be fixed and fully tested.

CropTest Passed and the bug was fixed. The next step will be create the pull request


[1.12] Server Crash

What happens:
When somebody tries to join a server they get a "Fatally missing block and items" error, while in singleplayer everything is fine. It only happens when CraftTweaker is installed.
What you expected to happen:
The player to connect and everything to work fine.
Script used (Please Pastebin or gist your script, posting an unpasted or ungist'd script will automatically close this issue):
https://pastebin.com/inM7iSWp
https://pastebin.com/sm73HRfA
Minetweaker.log file (Please Pastebin or gist your file, posting an unpasted or ungist'd file will automatically close this issue):
https://pastebin.com/FPUphB6w - server
https://pastebin.com/X9MjUAZv - client

Affected Versions (Do not use "latest"):

Minecraft: 1.12
Forge: <IP_ADDRESS>3
Crafttweaker: 12-4.0.1

Your most recent log file where the issue was present:
https://pastebin.com/RvxDPfDi

It looks like you don't have exactly the same scripts for the client and the server, this is required for the 1.12 crt

We do...

It's a known bug and should be fixed in a future release.  See #262

Well that's why I reported this. Because I knew that that was fixed today.

can I get the server log please (game log, not crafttweaker.log)

https://pastebin.com/kgBUWNN
Hmm, seems to do with it messing up advancements. Apparently removing the rail recipe caused it. Before, I had problems with the Cauldron, but at least that was adding a recipe, so I simply changed the name to minecraft:cauldron to fix it. Is there no way to fix the advancements problem?

Your paste isn't there...
On Jul 17, 2017 21:04, "EmosewaGamer"<EMAIL_ADDRESS>wrote:

https://pastebin.com/kgBUWNN
Hmm, seems to do with it messing up advancements. Apparently removing the
rail recipe caused it. Before, I had problems with the Cauldron, but at
least that was adding a recipe, so I simply changed the name to
minecraft:cauldron to fix it. Is there no way to fix the advancements
problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jaredlll08/CraftTweaker/issues/264#issuecomment-315850578,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFS9xYdpHEL7ZOFdvCqF3jqXNnXj4PF2ks5sO7AngaJpZM4OaLAC
.

Forgot a Z at the end.

Advancement errors as safe to ignore, as those check for recipes which don't exist anymore.
I'm not really sure what thing actually it is that is causing problems.
Can you try to remove the line that is adding/removing the recipe for the xu2 resonator?

I can remove it, but because of random issue I cannot test it (for some reason no matter what happens my local host always works fine). I need someone else to test it.

Wait? So you can log in but other people can't? Are those logs you provided from you while you were able to join the server or from the other people who weren't?

Other people tested it on their local hosts multiple times and they got the crash. My local host simply acts like a singleplayer world, so no matter what multiplayer crash there is, caused by any mod to any one else's server, it never happens to me. It's pretty confusing and something that neither I can explain.

You missed the important part of the question. From who are the log files? You or the people where it doesn't work?

Everyone that tested it technically. I didn't even test it as, as I said, I cannot.

Because that is the only line that is different between client and server in the crafttweaker.log
Another thing you could try is giving every recipe a name, and not let crt give them names automatically

What do you mean? I did give every recipe an name. As I know, it wouldn't work othwise.

Did i really...? Hmm, I forgot to add names to my last minute recipes. Coukd that by itself be the problem?

It can be a problem, but it certainly shouldn't be, as we added code that automatically assigns names based on the ingredients, and those should be exactly the same on the server and the client, so it doesn't really matter whether you add names or not

Why did you say that the name was so important then?

Because I am not very confident in the way I generate the names. If you add names to everything and that fixes it, then I know my way of creating the names is broken

Ok, I guess we'll see tomorrow. I guess if it works, that will also be solving another issue.

Yeah, that did not fix it. I added names to then and removed the resonator recipe and it still does not work.

What happens if you start the game with crt installed but no scripts at all?

It's all fine then

We're starting to test how the files do by themselves

We figured it out. Apparently you shouldn't have a colon in the name

Ye that makes sense, a colon is the separator between modid an recipe name, so having those in there might confuse the game.
Maybe we should add in a check to prevent it and replace it with some other character?


How to remove item from grid ?

I splice element from repeated arrays,but the dom is not removed in brower .
How to refresh the grid when i remove a item from the grid ?

I just remove the item from the array and works
    _public.removeItem = function(index){
        var item = _this.dashboardItems[index];

        item.destroy(); // not related to gridister

        _this.dashboardItems.splice( index, 1 );

        DashboardRest.removeItem({id : item.id, dashID : this.dashboard.id});
    };


refactor classes to use TypeToken over Type

Current coverage is 79.21% (diff: 83.87%)

Merging #20 into master will increase coverage by 0.04%

@@             master        #20   diff @@
==========================================
  Files           155        157     +2
  Lines          5166       5192    +26
  Methods           0          0
  Messages          0          0
  Branches        856        849     -7
==========================================
+ Hits           4090       4113    +23
- Misses          805        819    +14
+ Partials        271        260    -11

Powered by Codecov. Last update 442a3d7...83a7484

This is mostly just refactoring so it's safe. I'll have Brad look at the next change which is meatier. He has to reproduce it in Python.


[docs]  Does not resolve to a valid URL. Error

Whatever I import in main.js, I am getting these errors. Currently, I am trying to access the file system.
import { open } from "@tauri-apps/api/dialog";
const readfilecontents = async() => {
  try {
    const selectedpath = await open({
      multiple: false,
      title: "Open Text file",
    });
    console.log(selectedpath)
  } catch (error) {
    console.error(err);
  }
};
document.getElementById('openExplorerBtn').addEventListener('click', () => {
  readfilecontents();
});

Please help me correct this.

Have you added @tauri-apps/api as a dependency for your project in your package.json/installed it via npm or whatever package manager you use? Is this a brand new project created with create-tauri-app, or are you adding this to an existing project?

{
  "name": "exampleapp",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "tauri": "tauri"
  },
  "devDependencies": {
    "@tauri-apps/cli": "^1.5.11"
  },
  "dependencies": {
    "@tauri-apps/api": "^1.5.3",
    "@tauri-apps/plugin-dialog": "^2.0.0-beta.2"
  }
}

Yes i have added and installed with with npm

@mrintroverrt If you use tauri v2, the cli and api must be v2 too, if you use v1, then remove the plugin-dialog again.
That said, this is not the problem here. The problem is that you're trying to use npm packages without a bundler like vite or webpack, that's realistically not really possible.
If you don't want to use a bundler you can replace the import with this syntax
const { open } = window.__TAURI__.dialog;

(requires withGlobalTauri enabled in tauri.conf.json)