async loading model

[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ x] support request

Current behavior
 ngOnInit() {
    this.route.params.subscribe(params => {
        this.service.getConvenzioneById(params['id']).subscribe((data) => {
          this.model = data;
        });
    });
}

When the model is populated for the first time all the field.formControl.valueChanges emit the event.
How to avoid to listen the first event?

the easy way is to avoid init the form until model is ready, using
<formly-form *ngIf`

I used:
 <formly-form *ngIf="model"
and in my template
       lifecycle: {                     onInit: (form, field) => {                                               field.formControl.valueChanges.pipe(               distinctUntilChanged(),                            takeUntil(this.onDestroy$),                             tap(selectedField => {

onInit is called only with field has value
valueChanges is called only after a user modification
Seems working well.

Drawback is a completely empty page until it arrives the model
I'm not satisfy 100% seems the form + model need to be provided at the same time.
Other stuff related to the init of the form:  I need in the template access to other part of the model is possible?
onInit: (form, field) => {
//HERE ... other part of the model ...
           field.formControl.valueChanges.pipe(

@aitboudad I have problem in reloading form.

I'm going to close since it's not clear, please elaborate to get an answer.

@aitboudad you are right. Thank you for your response.
I have this button with this disabled condition: !form.valid || !form.dirty
<button class="btn btn-outline-primary border-0 rounded-0" [disabled]="!form.valid || !form.dirty" (click)="onSubmit()" >
<form *ngIf='model' [formGroup]="form" >
onReload (){
      this.model = null;
      let id = this.model.id;
      this.service.getConvenzioneById(id).subscribe((data) => {
        this.model = data;
      });
}

I call the onReload function.
The form remain in dirty state.
If I did this.form = new FormGroup({});  the form became not modified but it is disconnected from the button.

try with this.form.reset()

Hi @aitboudad the result of the form now is coerent. Thank you.
But the side effect is the form disappear during the update process. Any suggestion?
   this.model = null;
   this.service.updateConvenzione(tosubmit, tosubmit.id).subscribe(
        result => {
          this.form.reset();
          this.isLoading = false;
          this.id = result.id;
          this.model = result;
        },

ok instead of setting model to null rely on a locale variable (for example isLoading) to ignore emitted value during updateConvenzione and use options.reset() to update model value:
// field config
field.formControl.valueChanges.pipe(
  distinctUntilChanged(),
  takeUntil(this.onDestroy$),
  filter(() => !this.isLoading),
  ...
)

// updateConvenzione
   this.service.updateConvenzione(tosubmit, tosubmit.id).subscribe(
        result => {
          this.id = result.id;
          this.options.resetModel(result);
          this.isLoading = false;
        },
  )

Ok great!
I have a valueChanges inside a formly template, how to pass the local variable isLoading inside the template or set it externally?

pass it through formState
https://formly-js.github.io/ngx-formly/examples/form-options/form-state

I like the solution with form-state.
I lost only one behavior in select
          {
            key: 'tipoemittenti_codice',
            type: 'select',
            className: "col-md-6",
            templateOptions: {
              options: [],
              valueProp: 'codice',
              labelProp: 'descrizione',
              label: 'Autorizzato da',
              required: true
            },
            lifecycle: {
              onInit: (form, field) => {
                field.templateOptions.options = [this.model.tipoemittente];
                this.service.getEmittenti().subscribe((data)=> {
                  field.templateOptions.options = data
                });
              }
            }

Using the *ngIf on model when start the onInit the model is populated and
the set  field.templateOptions.options = [this.model.tipoemittente]; in the onInit
work well.
@aitboudad is better uselifecycle onChangeor register form.get('dipartimemto_cd_dip').valueChanges.pipe( and control isLoading

Any update ?
When i try to load model with
<ion-content *ngIf="loadedGame | async as game" padding>
Validation does not work

@rdev-software not sure what you mean, please elaborate in a new issue instead.

@aitboudad That if I have observable loadedGame and I want to async load it in parent in this case ion-content and place dynamic form inside and use loaded object game inside, validation does not work (and maybe other things as well as per this thread)

@rdev-software please replicate what you've done using our starter example https://stackblitz.com/edit/ngx-formly-ui-ionic in order to see what going wrong + fill a new issue.


Failed to Find an ADE extension error

Hello,
I am trying to import GML with importer-exporter version 4.2.0 and db is created by windows shell script in 3dcityDB-4.0.1 "Create_DB.bat"
However getting the error Failed to find an ADE extension for the ADE table 'cityobject'.
12980.gml.txt

Hi, i cannot reproduce the error using the standard release version 4.2.0.
Have you made changes to the source code of the importer-exporter? Have you installed any ADE extensions to the 3DCityDB and importer-exporter?

I reinstalled 4.2.0 and create a new db with 4.0.0. did not install ADE plugin manager. No ADE is available.

Could you install the latest importer-exporter version 4.2.2 https://github.com/3dcitydb/importer-exporter/releases/tag/v4.2.2 and test the CityGML-Import once again?

managed to import and export with 3.3.1. I will check the differences in schema. Thank you

I downloaded version 4.2.2 of the Importer/Exporter and set up a new 3DCityDB instance using the shell and SQL scripts contained in this version. Afterwards, I successfully imported your dataset. So like @yaozhihang, I couldn't reproduce your error.
Note that your dataset is not completely valid. On the "Import" tab of the Importer/Exporter, you can trigger a schema validation by clicking on "Just validate". This will give you a list of schema validations in your dataset.

Hi,
I am receiving the same error "Failed to find an ADE extension for the ADE table 'cityobject." while importing CityGML data using Importer/Exporter Tool. I am following all the steps successfully given in the tutorial "3DCityDB_V4.0_Hands-On_Tutorial" and as Importer/Exporter, the last release 4.2.2 is the one I have used. It creates a 3dcitydb folder which is creating a 3DCityDB instance via Create_DB.bat and its version is 4.0.2. I have tried older releases of Importer/Exporter and also PostgreSQL database. Still didn't manage to import the given data by the tutorial "Berlin_CityGML_lod2.gml". Would you please help me if any suggestion by your side?

Hi, @ZehraKoc91 Which PostgreSQL version are you using? which Java version is on you machine?

Hi, Java 8 is on my laptop and the PostgreSQL 12 is the version I have uploaded.

Hi, today, we've released a new version of 3DCityDB(v4.0.3) and Importer/Exporter(v4.2.3).
The installer package can be obtained from here: https://github.com/3dcitydb/importer-exporter/releases/tag/v4.2.3
Could you please do a test with this new version from the scratch? It means that you need to setup a new 3DCityDB instance and install the Importer/Exporter again.

Hi, today, we've released a new version of 3DCityDB(v4.0.3) and Importer/Exporter(v4.2.3).
The installer package can be obtained from here: https://github.com/3dcitydb/importer-exporter/releases/tag/v4.2.3
Could you please do a test with this new version from the scratch? It means that you need to setup a new 3DCityDB instance and install the Importer/Exporter again.

I have the same problem. I installed newest 3DCityDB(v4.0.3) and Importer/Exporter(v4.2.3).

[13:22:19 INFO] Initializing database import...
[13:22:19 INFO] Spatial indexes are enabled.
[13:22:19 INFO] Normal indexes are enabled.
[13:22:19 INFO] Creating list of CityGML files to be imported...
[13:22:19 INFO] List of import files successfully created.
[13:22:19 INFO] 1 file(s) will be imported.
[13:22:20 INFO] Applying XML validation to CityGML input features.
[13:22:20 INFO] Importing file: D:\RTG_Schulungskurs_2016\CityGML-Data\Berlin_CityGML_Lod2.gml
[13:22:20 ERROR] An error occurred: Failed to find an ADE extension for the ADE table 'cityobject'.
[13:22:20 WARN] Aborting import due to errors.
[13:22:20 INFO] Cleaning temporary cache.
[13:22:20 WARN] Database import aborted.

This error still exist. Java version 8 update 241 and PostgreSQL 12.

Closing because this issue cannot be reproduced.

Use "-Duser.language=en -Duser.region=US" as JVM parameters to solve this. I recognize some of the users are from Turkey and probably using a Turkish OS system. It is natural thet it can not be replicated of course it is easy to miss locale issues though it is a common one;
Issues cause:
"TableEnum" enum modules "TableEnum fromTableName(String name)" method convert TableEnum.BUILDING enumeration as "buıldıng" instead of "building" preventing to access already existing and non-ADE related table in the database.
Fix: getName method of TableEnum should use the overloaded version of the toLowerCase(java.util.Locale locale) not the zero argument overload
public String getName() {
return super.toString().toLowerCase(Locale.ENGLISH);
}

@selimnar, thanks, this is very helpful. I had not thought that TableEnum.BUILDING would be turned into "buıldıng" rather than "building". Reopening and labelling as bug.

No problem and you are welcome @clausnagel. I have done the same mistake again and again in my software development career and I am sure I will do so again in the future. A very common but easy to miss implementation error. Replication is near impossible, if you are not already using an OS with a locale other than English. Thanks to you and all other contributors for this opensource project by the way and gratitude's for the fast reply as well.

Fixed with 7c3d495272916862cd3243f79d758a9f74129523 (well, hopefully, as I can't test on my machine). I adapted more places in the code where I thought this might be a potential issue.

Fixed with 7c3d495 (well, hopefully, as I can't test on my machine). I adapted more places in the code where I thought this might be a potential issue.

Same workaround may help with testing "Use "-Duser.language=en -Duser.region=US" as JVM parameters to solve this". Instead use non-US language/region.

Yes, I did this and tested with -Duser.language=tr -Duser.region=TR. I could reproduce the error in the current release version and could successfully import without errors after 7c3d495272916862cd3243f79d758a9f74129523. So, closing now. Feel free to reopen if the issue still exists.

Just updated the project and run without the "-Duser.language=en -Duser.region=US" JVM parameters using my Turkish OS. I could not replicate the "import" issue.

I am getting the same error in version 4.3.0. I'm using postgresql 13 on windows 10. Can you check again please?

@UmutKoca, the fix has not been released yet but will be part of the upcoming Importer/Exporter version 5.3.0 (see changelog). We are in the final test phase for the release and want to publish it within the next few days.
If you want to test the fix prior to our release, simply clone the Importer/Exporter repository to your local machine and build the tool manually from the master branch.

Thank you @clausnagel

Hello, I am getting the same error and I saw a suggestion as  "use "-Duser.language=en -Duser.region=US" as JVM parameters "
I couldn't find where to change this parameters. Can you please help?

@iremkapucuoglu, please check chapter 4.1 of the online user manual. It describes how to pass JVM parameters using the JAVA_OPTS environment variable.
We are about to launch the release. It should be available by next week. With this release, the issue should be fixed and no additional JVM parameters should be required.

Thank you! @clausnagel

@iremkapucuoglu, @UmutKoca we just published the new version: https://github.com/3dcitydb/3dcitydb-suite/releases/tag/v2022.2.0
Please download and test with the new Importer/Exporter. The issue should be gone now and you should not need to adapt JVM parameters.

merhaba.
aynı hatayı alıyorum. sorunu çözdünüz mü ?


Fixed #472 - Ported two lines of code from iOS for Document.update()

For details, please reference #472


Issues with demos in IE 10

I'm trying to run the demos provided at https://demo.agektmr.com/dialog/ in IE 10 and am getting the prompt: "Your browser doesn't seem to support dialog element yet. This demo is running in polyfill mode." However, none of the demo's seem to be functional. Buttons that are supposed to be on the dialog box are being displayed by default and all buttons don't seem to have any function.

Is there any interesting console etc output? The demo page should be inserting the relevant script and CSS (can you check actually? The Angular code in main.js should do it—although I do wonder whether Angular supports IE10.
We can test in IE10/9, but it's a struggle.

This is the console output upon loading the page.

These are two screen shots of two particular demos on the page, but all of demos are failing

This is a problem with the demo site, not with dialog. We probably won't fix it, but if it's important I can come up with a simpler one.
If you have any problems with using dialog on IE9/10 please file new bugs.

Hello,
I am using this polyfill in my application and it does not work with IE9 or IE10, but it works with IE11. I am getting the same errors as in the demos.
So, I suppose that support for IE9 and IE10 is not available?

This is the error I see in IE10:
"In strict mode, function declarations cannot be nested inside a statement or block. They may only appear at the top level or directly inside a function body. "
This comes from this code block:
    var nativeFormSubmit = HTMLFormElement.prototype.submit;
    function replacementFormSubmit() {
      if (!isFormMethodDialog(this)) {
        return nativeFormSubmit.call(this);
      }
      var dialog = findNearestDialog(this);
      dialog && dialog.close();
    }

This is fixed on master (through PR #160), but has not been published to NPM yet.

I've published 0.4.10 to fix this.

I've published new demos however they use modern JS/CSS and probably won't work in IE10.


Replace depreciated use function calls with useSelector

The use function provided by Legend-State is frequently used inside rhp components to track changes in an observable and re-render when changes occur. The people behind Legend-State have indicated in their blog that use will be depreciated in a later version of Legend-State. Apparently, it uses useSelector behind the scenes so as a preparatory step in migrating to Legend-State 2.0, all uses of the use function should be replaced by useSelector.
Example:
- import { enableReactUse } from '@legendapp/state/config/enableReactUse';
+ import { useSelector } from '@legendapp/state/react';

- enableReactUse();

const Component = () => {
    // Create an observable object inside of a component
    const myLocalObservable = useObservable(1);

-    const currentMyObservableValue = myLocalObservable.use();
+    const currentMyObservableValue = useSelector(myLocalObservable);

    return <div>{currentMyObservableValue}</div>;
};

Completed in commit a21230a


Upgrade to React 0.14

If a09ab9927f78411013a82d551847c0c79a8e2b19 fixes this, it can be closed?

It'll close automagically once the style branch gets merged into master :sunglasses:

:heart_eyes:


MUMUP-2497 Material Setup

Add angular-material dependencies to UW-Frame project

Coverage remained the same at 34.817% when pulling 4758e750174cf585351e5e2d39db96d60fd09901 on addMaterial into 36e179a1abeb07bf7d623bb15101420bda3cd95e on master.


Marker genes cannot be added to the dot plot unless the marker gene panel is closed

From Karen during usability study:
He selected podocyte as a cell type and tried to add all the marker genes to the dot plot via marker gene panel and none of the dots would load on the dot plot.
The dots on the dot plot will load but only if you close the marker gene panel
Slack thread

If no genes, bulk add marker genes will render heatmap as expected
If there are existing genes, bulk add marker genes won't trigger a render
Open/close marker gene panel will force re-render the heatmap


problem with json

Hi,
i wnat to highlight a json multi array but only the last value is green and the other are red. i want to have all values in green! is there a way to do this ?
example: {"key1":"value1","key2":"value2","key3":"value3"}
--> just value3 is red
PLEASE HELP ME! :D

Hi, could you show us your code so we can investigate this issue?
Also, shouting is not necessary ;)

Thanks for replying,
here is the code:
HTML formated:

{"message":"created new file -all-, value inserted;created new file -24h-, value inserted;created new file -168h-, value inserted;created new file -current-, value inserted;","data":"DEIN TEMPERATURWERT","ip":"DEINE IP-ADRESSE","appid":"DEINE APPID","lastinsert":"ZEITPUNKT DES DATENUPLOADES"}

HTML unformated:

 {"message":"created new file -all-, value inserted;created new file -24h-, value inserted;created new file -168h-, value inserted;created new file -current-, value inserted;","data":"YOUR TEMPERATURE VALUE","ip":"YOUR IP-ADDRESS","appid":"YOUR APPID","lastinsert":"TIME OF UPLOADING"}

Just the "TIME OF UPLOADING" is green, other red

Yeah, this looks like a bug on our end. Note that if the JSON was formatted properly, the highlighting works.

Thanks for the code sample. It should be fixed now.

Yes, @Golmote
thanks it works now :D


Export method documentation

Dear extendr authors,
thanks a lot for all that you do! I'm a happy user having a blast learning to wrap Rust libraries, and extendr is an absolute joy to work with. I'm writing today because of a minor quibble I noticed, namely that documentation for impl methods is lost somehow.
For example, in the test library:

MySubmoduleClass provides top- and method-level documentation in the code
The top-level documentation, but not that for the methods, is output to extendr-wrappers.R.
As a result (I think) the documentation is also not present in the generated .Rd files

I haven't been able to figure out exactly how the conversion works; whether the documentation is generated through extendr, for example, or through roxygen. If this is a local issue that you think can be fixed by a beginner, I'd love to investigate further and possibly contribute a fix, and would appreciate any pointers you could give me.
Many kind regards, and thanks again for all of your efforts!
-Felix

I've been looking into this some more, collecting a few notes in hopes that they come in useful:

In extendr-api/src/metadata.rs, it appears that the function write_function_wrapper writes documentation for a function, but write_method_wrapper skips that step.
Both functions appear to operate on the Func struct, which should include the docstring as best I can tell. I haven't figured out yet how this is generated from the Rust code -- my best guess is the black magic in extendr_module.rs, but I'm not sure.

I think I'm going to try my hand at debugging this, but any hints are still super-welcome (and are bound to save a newb hours of head-desking).


GSSOC EXT NOTICE: Improper Labeling in the Project

Dear Project Admin @rahulsainlll
It has come to our attention that your repository not applying the necessary labels to issues and merged PRs, which is affecting contributor scores on the leaderboard.
Please ensure you use the correct labels:

gssoc-ext
level1, level2, level3
hacktoberfest-accepted (only if your repository have Hacktoberfest topic in description)

NOTE: Level labels should not have any dashes between them. Spaces are allowed, but no dashes should be used.
Kindly review and update the labels on your issues and PRs to ensure fairness for all contributors. Failure to address this may result in your project being flagged.
Thank you,
Core Team
GSSoC '24 Extended

@rahulsainlll why r u ignoring ?

@rahulsainlll why r u ignoring ?

No no there were like 8-9 issue and PRs so it missed.
I have corrected all the labels ser. See for yourself anyways i will check again. Thank you

@rahulsainlll why r u ignoring ?

No no there were like 8-9 issue and PRs so it missed.
I have corrected all the labels ser. See for yourself anyways i will check again. Thank you

Its okay , But still labels are not correct please read my above comment again of correct labels @rahulsainlll

now check ser in the merged PRs and Currenct PRs also updating the issues now. If you see any mistake their do let me know!

@rahulsainlll Yes perfect !


Error creating a new chat thread

This issue is for a: (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Deploy all pre-requisites/components/solutions to Azure

build version of the contoso-web-app
full code of contso-node-api

Login as Doctor and Patient on separate browsers to contoso-web-app
Create a booking with a Doctor, and start Chat

Any log messages given by the failure
Following log messages are seen for the contoso-node-api solution:

creating new thread...
initializing chat client...
TypeError: CommunicationUserCredential is not a constructor
at Object.createThread (C:\home\site\wwwroot\services\chat.service.js:62:50)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async createThread (C:\home\site\wwwroot\controllers\chat.controller.js:8:20)
POST /chat/createThread 200 205.443 ms - -

Expected/desired behavior

A new chat thread should be created and message should be delivered to the other party.

OS and Version?

Windows 7, 8 or 10.

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

Dupliate of this issue; closing for now.


kernel panic/soft lock CPU

RancherOS Version: (ros os version)
1.5.4
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
VM in kvm qemu 2.11.1 under ubuntu 18.04.3 4.15.0-70-generic
since last kernel update of ubuntu most probably, I have kernel panic in my rancherOS vm/ soft lock CPU
The VM can stay alive if I let only 3 containers alive, Can't do any docker pull, I haven't change anything to the VM. rancher-server container was making the whole VM crash.
It seems be an I/O problem and I don't have any clue how to debug this. Don't know if it a RAID-related problem either.
Any ideas where I could look to know what's happening?

no lead or idea about what to look for? Why this VM is crashing while it doesn't seem to be corrupted or anything. Can anyone do a test on a ubuntu server and put a rancherdocker VM in kvm-qemu?


[ECS] Fix result merging

Closes #3467

@TomasVotruba oh it doesn't exist as service... should I just create it in constructor? or should I register it somewhere? if register then where?

ping @TomasVotruba

CI is failing.

@TomasVotruba I can see that. Can you answer my question above?

Use the conventions in the code.

:roll_eyes:


init: Parameter to configure what database is used for provider and url example

If would save 2 (small) necessary changes for each project that should use MySQL or SQLite instead of the PostgreSQL default for these values.
Might also be a tiny undocumented internal feature for quicker reproductions etc if we want to keep the API clean.

Small note: you can use this cli for reproductions: https://github.com/timsuchanek/auto
It basically does the same thing described but also install deps and setup a reproduction script.

More elaborate proposal: https://github.com/prisma/prisma/issues/7126


Add development notes about npm publishing

https://github.com/kbss-cvut/s-forms/issues/5
https://github.com/kbss-cvut/s-forms/pull/136

Closing in favour of https://github.com/kbss-cvut/organization/issues/1.


How to change the log level (reducing the amount of debug logs)?

What version of UAA are you running?
4.11.0
How are you deploying the UAA?
Official Maven JAR from Maven Central
What did you do?
UAA is producing a lot of logs.
We want to define different log levels for different environments, but unable to do it or find documentation about it.
We are packaging it in a Docker container and we tried things like below but without success.
# Set logging level
ENV JAVA_OPTS="${JAVA_OPTS} -Dlog4j2.logLevel=INFO"
ENV CATALINA_OPTS="${CATALINA_OPTS} -Dlog4j2.logLevel=INFO"
ENV LOG4J_LEVEL INFO

RUN sed -i 's/level = FINE/level = INFO/g' /usr/local/tomcat/conf/logging.properties

Is there a way to change the level thorough uaa.yml configuration, or something else?
Thanks for the help!
What did you expect to see? What goal are you trying to achieve with the UAA?
Reducing amount of logs

Hi, I work with @bernardpletikosa and should point out that we have also tried adding the following to our uaa.yml file:
logging_level: INFO

We're still seeing a lot of DEBUG messages.
Apr 30 02:00:01:390 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.390] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] .... DEBUG --- DisableIdTokenResponseTypeFilter: post id_token disable:false pathinfo:null request_uri:/check_token response_type:null
Apr 30 02:00:01:390 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.390] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] .... DEBUG --- DisableIdTokenResponseTypeFilter: Processing id_token disable filter
Apr 30 02:00:01:390 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.390] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] .... DEBUG --- DisableIdTokenResponseTypeFilter: pre id_token disable:false pathinfo:null request_uri:/check_token response_type:null
Apr 30 02:00:01:390 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.390] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] .... DEBUG --- SecurityFilterChainPostProcessor$HttpsEnforcementFilter: Filter chain 'checkTokenSecurity' processing request POST /check_token
Apr 30 02:00:01:391 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.391] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] .... DEBUG --- ClientBasicAuthenticationFilter: Basic Authentication Authorization header found for user 'api-gateway'
Apr 30 02:00:01:391 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.391] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] .... DEBUG --- ClientBasicAuthenticationFilter: Authentication success: org.springframework.security.authentication.UsernamePasswordAuthenticationToken@63e605b3: Principal: org.springframework.security.core.userdetails.User@5229e991: Username: api-gateway; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: scim.read,uaa.resource; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=10.x.xx.xx, clientId=api-gateway; Granted Authorities: scim.read, uaa.resource
Apr 30 02:00:01:391 cloud-uaa c204198d-f451-4fe8-a747-f6be9ea6d797:  [2018-04-30 00:00:01.391] cloudfoundry-identity-server - ???? [http-nio-8080-exec-11] ....  INFO --- Audit: ClientAuthenticationSuccess ('Client authentication success'): principal=api-gateway, origin=[remoteAddress=10.x.xx.xx, clientId=api-gateway], identityZoneId=[uaa], authenticationType=[unknown]

Hi @DennisDenuto, thanks for the response.
Is there anything I can do in the mean time to change the log level for that class?  Separate logging config file?  Command line parameter?

You may want to exclude commons-logging from your classpath (e.g. via Maven exclusiona) and add the jcl-over-slf4j bridge instead: https://www.slf4j.org/legacy.html#jcl-over-slf4j

fyi this has been fixed and will be in the next release of uaa


Ledger signature verification fix

Applies the adjustment to the v value when verifying the signature to be able to verify signatures done with Ledger hardware wallet.

lgtm ~


Cocoapods limitation <=0.39 in README still relevant?

There is the limitation in the README:
- Objective-C, Swift (via Carthage, CocoaPods [0.39 and below. See CocoaPods Specs Repo Sharding]) and Swift Package Manager)
- Objective-C (+ CocoaPods 0.39 and below. See CocoaPods Specs Repo Sharding)

Isn't it outdated with the merge of https://github.com/pivotal/LicenseFinder/pull/534 ?
The world has changed since the introduction of this limitation in 2017. There will be no more projects compatible to cocoapods in the mentioned versions so if LicenseFinder does not consider changing this, rather listing Cocoapods as an experimental project type it should list it as a deprecated project type to signal the readers not to expect any compatibility in the future.

@thedarkside Ys that is correct. We forgot to update the readme. We do not really use cocoapods so our experience for this branch of the code is not up to date as it was done by the community. If you can make a change to the readme that better reflects the new world, we would appreciate it but yes it should be compatible!


OpenBazaar ID or GUID?

The user interface has both "OpenBazaar ID" and "GUID". To me, "GUID" is too technical for the user interface, and I would stick with just "OpenBazaar ID", which is much clearer for the average Joe.

I tend to agree. End users will understand OpenBazaar ID (or OpenBazaar Address) or OB ID better than GUID.

Agreed, OpenBazaar ID is probably best
On Jan 28, 2016 8:38 AM, "Sam Patterson"<EMAIL_ADDRESS>wrote:

I tend to agree. End users will understand OpenBazaar ID (or OpenBazaar
Address) or OB ID better than GUID.
—
Reply to this email directly or view it on GitHub
https://github.com/OpenBazaar/OpenBazaar-Client/issues/609#issuecomment-176211036
.


Example in Readme

Hello!
I did not get idea of the project itself, so excuse me.
It would be great to update readme with  some example, that shows using some famous cloud  service through API.
Thanks

Hey @palansher - there are some examples in the example directory of the repo 😃


chore: change log

Description of change
Change log

Pull Request Test Coverage Report for Build<PHONE_NUMBER>4
Details

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 86.704%

Totals

Change from base Build<PHONE_NUMBER>4:
0.0%

Covered Lines:
10587

Relevant Lines:
11832

💛  - Coveralls


YAML base files rename

Description
As discussed on the October 2nd meeting, we should rename all base.yml files to have descriptive names.
base.yml -> base_xyz.yml

Sign me up, I'll start it start of next week :)

Sign me up, I'll start it start of next week :)

You still doing this?

Sign me up, I'll start it start of next week :)

You still doing this?

Yeah will hop on this tomorrow. There weren't many examples I had found that didn't have a reasonable base ID but will go through all the entity bases.

I've just checked a large number of examples and they're currently a combination of xyzBase and BaseXyz and are fairly descriptive.
So just to be sure we're on the same page do we want to transition them all to the same format I.e Base_xyz.
For example "ClothingShoesBase" would become "Base_ClothingShoes" or is this really a non issue? Unless someone can point out an obvious non descriptive base.

@Peptide90 this issue is about YAML filenames, not prototype IDs

@Peptide90 this issue is about YAML filenames, not prototype IDs

My bad, fair enough should be a quick fix then. I'll take a quick look.


New version: CamiXon v1.0.9

Registering package: CamiXon
Repository: https://github.com/walra356/CamiXon.jl
Created by: @walra356
Version: v1.0.9
Commit: 6eb548bf47509dd88604f388c20f01aa2e4e0df0
Reviewed by: @walra356
Reference: https://github.com/walra356/CamiXon.jl/commit/6eb548bf47509dd88604f388c20f01aa2e4e0df0#commitcomment-46834489

@walra356 ☝


Support Azure k8s Metrics Adapter for integration with HPA

Disclaimer: I haven't checked the code so this might already be the case
Why does Keda use MSFTs own metrics adapter instead of adopting the Azure k8s Metrics Adapter to integrate with the HPA?
Is it because it's based on other metrics than Azure Monitor or a different reason?
Based on the docs it's not really clear to me where it's getting the metrics from.

KEDA is a cloud agnostic, vendor neutral project and thus cannot use an Azure only software component.
Even for Azure services, the reliance on Azure Monitor is problematic for a multitude of reasons.

That makes sense, I think my question is more why doesn't Keda integrate with existing metric servers which we can plug in.
For example Ive just opened #156 for Prometheus support, which has a metrics server already, and #155 which improves Monitor support while we could plug in the one mentioned above.
/cc @jeffhollan

Was just talking about Prometheus yesterday :)
Thats indeed a very powerful feature.

Closing this as we have #155 and #156 to track

Fair enough, thanks for following-up!


[Mega-Thread] Documentations - Project Initial Report

Deadline : 13 Nov 2020 (As version 0.1)
TODO List

[x] Create report file (@ChisanaKita)
[x] Draft report structure
[x] Abstract
[x] Introduction

[x] State the goals of the game
[x] Document Structure

[x] Game Design

[x] List of the basic constraints and requirements
[x] Design Thinking

[x] Game Overview

[x] Story background
[x] Play modes
[x] System Architecture

[x] Game World

[x] Game Environment
[x] Level Design
[x] Maps Design
[x] Characters

[ ] Objects
[x] Gameplay Description

[x] User Interface Design
[x] Control

[ ] Software Design    (Optional)

[ ] Use Case Diagram
[ ] Class Diagrams
[ ] Sequence Diagrams

[x] Hardware and Software Requirements
[x] Technical Considerations
[x] Project Plan

[x] Schedule
[x] Milestone description
[x] Action Plan

[ ] References
[ ] Appendices

[x] Workload Distribution
[x] Budget Estimation
[ ] Log Sheets

[ ] QA

[ ] Final check by : @ChisanaKita
[ ] Supervisor feed back
[ ] fixes (If any)

image for object


[Bug report] TypeError: Cannot read properties of undefined (reading 'colorMode')

Description
I use the default theme and a KaTeX plugin. After installing the dependencies, errors occur when running npm run docs:build. The problem is reproduced here, and a brief log is below:
><EMAIL_ADDRESS>docs:build
> vuepress build docs

info Initializing VuePress and preparing data...
⠇ Compiling with vite
(!) Some chunks are larger than 500 KiB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/guide/en/#outputmanualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✔ Compiling with vite - done
⠋ Rendering pages⠋ Rendering pages /TypeError: Cannot read properties of undefined (reading 'value')
    at ReactiveEffect.fn (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1217:101)
    at ReactiveEffect.run (/home/will/blog/node_modules/@vue/reactivity/dist/reactivity.cjs.prod.js:178:25)
    at ComputedRefImpl.get value [as value] (/home/will/blog/node_modules/@vue/reactivity/dist/reactivity.cjs.prod.js:1066:39)
    at setupDarkMode (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1538:76)
    at Object.setup (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1718:5)
    at setup (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1954:59)
    at callWithErrorHandling (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:119:22)
    at setupStatefulComponent (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:5789:29)
    at setupComponent (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:5770:11)
    at renderComponentVNode (/home/will/blog/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:169:17)
[Vue warn]: Component VuepressApp is missing template or render function.
⠙ Rendering pagesTypeError: Cannot read properties of undefined (reading 'colorMode')
    at setupDarkMode (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1538:82)
    at Object.setup (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1718:5)
    at setup (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1954:59)
    at callWithErrorHandling (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:119:22)
    at setupStatefulComponent (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:5789:29)
    at setupComponent (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:5770:11)
    at renderComponentVNode (/home/will/blog/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:169:17)
    at renderToString (/home/will/blog/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:443:26)
    at renderPage (/home/will/blog/node_modules/@vuepress/bundler-vite/lib/build/renderPage.js:21:32)
    at async /home/will/blog/node_modules/@vuepress/bundler-vite/lib/build/build.js:54:13
[Vue warn]: Component VuepressApp is missing template or render function.
TypeError: Cannot read properties of undefined (reading 'colorMode')
    at setupDarkMode (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1538:82)
    at Object.setup (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1718:5)
    at setup (/home/will/blog/docs/.vuepress/.temp/.server/app.js:1954:59)
    at callWithErrorHandling (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:119:22)
    at setupStatefulComponent (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:5789:29)
    at setupComponent (/home/will/blog/node_modules/@vue/runtime-core/dist/runtime-core.cjs.prod.js:5770:11)
    at renderComponentVNode (/home/will/blog/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:169:17)
    at renderToString (/home/will/blog/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:443:26)
    at renderPage (/home/will/blog/node_modules/@vuepress/bundler-vite/lib/build/renderPage.js:21:32)
    at async /home/will/blog/node_modules/@vuepress/bundler-vite/lib/build/build.js:54:13
[Vue warn]: Component VuepressApp is missing template or render function.
…
…
…
…

Reproduction
https://stackblitz.com/edit/vuepress-scrkty
Used Package Manager
npm
System Info
System:
    OS: Linux 5.13 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (1) x64 Intel(R) Xeon(R) CPU E5-2673 v4 @ 2.30GHz
    Memory: 329.54 MB / 908.48 MB
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.16.0 - /usr/bin/node
    Yarn: Not Found
    npm: 8.11.0 - /usr/bin/npm
  Utilities:
    Git: 2.25.1 - /usr/bin/git
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @vuepress/bundler-vite: Not Found
    @vuepress/bundler-webpack: Not Found
    @vuepress/cli: Not Found
    @vuepress/client: Not Found
    @vuepress/core: Not Found
    @vuepress/markdown: Not Found
    @vuepress/plugin-active-header-links: Not Found
    @vuepress/plugin-back-to-top: Not Found
    @vuepress/plugin-container: Not Found
    @vuepress/plugin-docsearch: Not Found
    @vuepress/plugin-external-link-icon: Not Found
    @vuepress/plugin-git: Not Found
    @vuepress/plugin-google-analytics: Not Found
    @vuepress/plugin-medium-zoom: Not Found
    @vuepress/plugin-nprogress: Not Found
    @vuepress/plugin-palette: Not Found
    @vuepress/plugin-prismjs: Not Found
    @vuepress/plugin-pwa: Not Found
    @vuepress/plugin-pwa-popup: Not Found
    @vuepress/plugin-register-components: Not Found
    @vuepress/plugin-search: Not Found
    @vuepress/plugin-shiki: Not Found
    @vuepress/plugin-theme-data: Not Found
    @vuepress/plugin-toc: Not Found
    @vuepress/shared: Not Found
    @vuepress/theme-default: Not Found
    @vuepress/utils: Not Found
    vue: Not Found
    vue-loader: Not Found
    vue-router: Not Found
    vuepress: Not Found
    vuepress-vite: Not Found
    vuepress-webpack: Not Found

Provide a minimal reproduction by opening an new issue plz. You are definitely not providing a minimal production, and no one has any insterest digging in to thousands of lines.

I just encountred this issue and it was resolved after I re-built my pnpm-lock.yaml file.

I got the same issue when upgrade from 2.0.0-beta.49 to 2.0.0-beta.50, still no luck yet

Seems caused by https://github.com/vuepress/vuepress-next/blob/d283ffe3ef0668bfea54e6d973066695f46f13c0/ecosystem/plugin-theme-data/src/client/config.ts#L17
Why routeLocale is undefined?
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'value')
    at ReactiveEffect.fn (config.js:10:100)
    at ReactiveEffect.run (reactivity.esm-bundler.js:185:25)
    at get value [as value] (reactivity.esm-bundler.js:1144:39)
    at setupDarkMode (useDarkMode.js:21:73)
    at Object.setup (config.js:35:9)
    at setup (app.js?v=6ec5f7fd:249:29)
    at callWithErrorHandling (runtime-core.esm-bundler.js:155:22)
    at setupStatefulComponent (runtime-core.esm-bundler.js:7165:29)
    at setupComponent (runtime-core.esm-bundler.js:7120:11)
    at mountComponent (runtime-core.esm-bundler.js:5473:13)

Seems caused by
https://github.com/vuepress/vuepress-next/blob/d283ffe3ef0668bfea54e6d973066695f46f13c0/ecosystem/plugin-theme-data/src/client/config.ts#L17
Why routeLocale is undefined?
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'value')
    at ReactiveEffect.fn (config.js:10:100)
    at ReactiveEffect.run (reactivity.esm-bundler.js:185:25)
    at get value [as value] (reactivity.esm-bundler.js:1144:39)
    at setupDarkMode (useDarkMode.js:21:73)
    at Object.setup (config.js:35:9)
    at setup (app.js?v=6ec5f7fd:249:29)
    at callWithErrorHandling (runtime-core.esm-bundler.js:155:22)
    at setupStatefulComponent (runtime-core.esm-bundler.js:7165:29)
    at setupComponent (runtime-core.esm-bundler.js:7120:11)
    at mountComponent (runtime-core.esm-bundler.js:5473:13)

Have you resolved it?


feat(no-unsupported): Support node 22.3.0 and 20.16.0

I'm not sure how I missed node 22.3.0 :shrug:


feat: apply props

For now, supports

react-dom
react-three/fiber
untested react-native

webpack complains unresolved packages. I'm not sure if there's any way to work it around.
hope someone will come later and give some advice.
meanshile, let's ship it.


feat: add toBeScheduled expectation

This pull request adds a new toBeScheduled expectation that eases the process of asserting that invokable classes, commands or jobs are scheduled.
// With a cron expression
expect(InvokableClass::class)->toBeScheduled('0 * * * *')

// With a callback
expect(CommandClass::class)->toBeScheduled(function (Event $event) {
    expect($event->getExpression())->toBe('0 0 * * *');
    expect($event->getSummaryForDisplay())->toBe('Foo');
})

All done 👍

Thank you!


createdisk.sh: enable fedora-updates repo for qemu-user-static-x86

Issue #967

/retest

/retest

The microshift job failed, I don't know if it's expected, if it's because it tried to run microshift 4.17.0-rc3 instead of something newer, ...
But e2e-snc passed and the PR looks good to me !

/retest

/cherry-pick release-4.18

/cherry-pick master


2064: Read Only Memories [PCSE00972]

App summary

App name: 2064: Read Only Memories
App serial: PCSE00972
App version: 1.00

Vita3K summary

Version: v0.1.5
Build number: 2768-53f45ba6
Commit hash: https://github.com/Vita3K/Vita3K/commit/53f45ba66d56daddd9993ea6ac07f33f4a20abf9
CPU backend:Dynarmic

Test environment summary

Tested by: ?
OS: Windows 10
CPU: Intel Core i7 920
GPU: AMD RX 580
RAM: 16 GB

Issues
nothing
Screenshots
Log
vita3k.log
Recommended labels

Nothing

as of https://github.com/Vita3K/Vita3K/commit/1b0e65e66d17202b1ae9f155cfecea802dd58778, the game is in menu (and not bootable).
Screenshots

Log
vita3k.log
Recommended labels
Menu


pull request for e2e test at 11/26/2016 07:56:03

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add GEM/xsum

Add GM/xsum.
Two questions:

Is "." a good stopping criterion? It seems like most of the examples end in '.' except for a few (~10 out of ~400 for each split). All the examples in xum are supposed to be 'one sentence.

Should I set the max length?

[x] Write.py

[x] Running on GPT2. I am not sure what numbers I should be expecting here, however.

Could you specify the SPLIT per challenge set to be the name of the challenge set?
This way we can (automatically) log that information.

What do you think should be the good split name for {train/validation/test} and {challenge_train_sample/challenge_validation_sample}?

I don't think train/val needs it, but for the others, you could use the names you list in the registery.
Maybe: "challenge_sample", "challenge_test_backtranslation", "challenge_test_bfp_02"....

{
"gem_xsum": gem_xsum.GEMXSUM,
"gem_xsum_challenge_sample": gem_xsum.GEMXSUMChallgeSample,
"gem_xsum_challenge_test_backtranslation": gem_xsum.GEMXSUMChallgeTestBacktranslation,
"gem_xsum_challenge_test_bfp_02": gem_xsum.GEMXSUMChallgeTestBFP02,
"gem_xsum_challenge_test_bfp_05": gem_xsum.GEMXSUMChallgeTestBFP05,
"gem_xsum_challenge_test_nopunc": gem_xsum.GEMXSUMChallgeTestNopunc,
"gem_xsum_challenge_test_covid": gem_xsum.GEMXSUMChallgeTestCovid,
}

So, the thing is that
class GEMXSUM(GEMXSUMBase):loads up all of {train, validation, test} splits. -- When the evaluation is executed by running main.py, it is first going to look at whether  GEMXSUM has a test set or not. Since class GEMXSUM(GEMXSUMBase):' has a test data (along with train and validation), it is going to run the evaluation on test data.
So the question is what name should I use for the SPLIT variable when using class GEMXSUM(GEMXSUMBase):?


[BIOMAGE-1623] Fix metadata tracks infinite loop

Background
Link to issue
https://biomage.atlassian.net/browse/BIOMAGE-1623
Link to staging deployment URL
Links to any Pull Requests related to this
Anything else the reviewers should know about the changes here
Changes
Code changes
Definition of DONE
Your changes will be ready for merging after each of the steps below have been completed:
Code updates
Have best practices and ongoing refactors being observed in this PR

[ ] Migrated any selector / reducer used to the new format
[ ] Validated that current unit tests work as expected and are enough

Testing

[ ] Unit tests written
[ ] Tested locally with Inframock (with latest production data downloaded with biomage experiment pull)
[ ] Deployed to staging
[ ] Passed integration tests

To set up easy local testing with inframock, follow the instructions here: https://github.com/biomage-ltd/inframock
To deploy to the staging environment, follow the instructions here: https://github.com/biomage-ltd/biomage-utils
Documentation updates
Is all relevant documentation updated to reflect the proposed changes in this PR?

[ ] Relevant Github READMEs updated
[ ] Relevant wiki pages created/updated

Approvers

[ ] Approved by a member of the core engineering team
[ ] (UX changes) Approved by vickymorrison (this is her username, tag her if you need approval)

Just before merging:

[ ] After the PR is approved, the unstage script in here: https://github.com/biomage-ltd/biomage-utils is executed. This script cleans up your deployment to staging

Optional

[ ] Photo of a cute animal attached to this PR

Still need to write/fix tests

I noticed that this warning appears on the console after I added custom cell sets track on the heatmap, where custom cell sets is empty (I haven't created any new clusters), and on hover over that track with the mouse. Can you fix it:

I saw that this warning appears on the console the first time I hover over the heatmap. Can you look into it?

I saw that this warning appears on the console the first time I hover over the heatmap. Can you look into it?

Should be fixed now


Pass route parameters into a component on navigation

Describe the solution you'd like
Be able to pass in the route optional parameters into a component when we navigate to it.

This is in the next release


Latest Nuget version can not load images - BUG

Description
After upgrading from Nuget v. 3.4.4 to 3.4.5 SVG can not load images. It has been working in ALL other nuget versions.
It fails with message: Error: 0 : Error loading image: 'https://www.w3.org/Icons/SVG/svg-logo-v.png', error: The header name 'image/svg+xml' has an invalid format.

Example data

SVG
<?xml version="1.0" encoding="utf-8"?>
<svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="100" height="100">
  <image xlink:href="https://www.w3.org/Icons/SVG/svg-logo-v.png" height="100" width="100" />
</svg>

Code:
var svgDocument = SvgDocument.Open<SvgDocument>(stream);
var bitmap = svgDocument.Draw();

Used Versions
Nuget version: 3.4.5  - FAILS with - "Error: 0 : Error loading image: 'https://www.w3.org/Icons/SVG/svg-logo-v.png', error: The header name 'image/svg+xml' has an invalid format."
Nuget version: 3.4.4 - Working

What paltform and framework are you using?

@mrbean-bremen - Windows 10 x64 and .Net 7

@H1Gdev - please also have a look. I will check if I can reproduce the problem later tonight, but given that all tests have been passing I doubt it - so currently I have no real idea what went wrong. Also the error message is quite strange, as it relates to a png, not an svg.

I made a simple Console app to reproduce it.
It can be downloaded here: SVGTestConsoleApp.zip
As it can see on this image, the "output"-window shows the error. Note the output svg.png is just black.

I will make another bugfix release soon, as this was a regression.

The new release is online.

Can confirm its working with latest nuget package. Thanks for fast actions 👍


Suggestion: a Canonical build-environment Docker image

That would  considerably shorten the barrier to entry for those  interested in having a play :)

@SplittyDev what's the situation over on FluoriteOS? Would it be welcome there?

@anicholson FluoriteOS has a more stable base than NuummiteOS and should be the one that gets picked up again if anyone has time to work on it.
PRs are very welcome there, too :)
Having a docker image to build and run FluoriteOS in a reproducible fashion would be really great.


Teams Trial licenses

This article includes this sentence {"All legacy Teams Commercial Cloud Trial licenses will be automatically converted to the new offer before their trial expires." But it is not clear on the number. In my case, the client has more than 100 and when the Microsoft Teams Exploratory Trial is active it is only indicating 100 licenses are available. The article needs to be updated to stated that 'up to 100' licenses will be converted. If they have more than 100 they may have to purchase.

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

ID: 28550025-fde2-9a83-a826-f7e3ccb313db
Version Independent ID: 2a304432-b10c-220f-3453-e19e7a155c67
Content: Manage the Microsoft Teams Exploratory experience - Microsoft Teams
Content Source: Teams/teams-exploratory.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@Jmartinez589 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.


Use with React 15

Not sure what version of React this was written for, but for React 15 you need to import ReactDOMServer.
import React from 'react';
import ReactDOMServer from 'react-dom/server';
import * as HtmlToReact from 'html-to-react';

const htmlInput = '

Title

A paragraph

';
const htmlToReactParser = new HtmlToReact.Parser(React);
const reactComponent = htmlToReactParser.parse(htmlInput);
const reactHtml = ReactDOMServer.renderToStaticMarkup(reactComponent);

Unfortunately it just outputs a string of identical to the HTML input though for me.

You could try my version and see if it works better for you.

This is solved now in master.


Fix rules per suggestions of buildifier

This change is cosmetic, and should not affect functionality in any way.
buildifier is the official linter for Bazel.
https://github.com/bazelbuild/buildtools
buildifier -lint warn -mode check -r .

@jesec - I have invited you to this repo as a collaborator - https://github.com/hdl/bazel_rules_hdl/invitations

/gcbrun

/gcbrun


lz4: fix static build

Description of changes
This patches lz4 with https://github.com/lz4/lz4/pull/1162, fixing the static build.
Before this, I see
$ nix build nixpkgs#pkgsStatic.lz4
error: builder for '/nix/store/4ssbvpxh8bp5gdk7517ip22myl6b39an-lz4-static-x86_64-unknown-linux-musl-1.9.4.drv' failed with exit code 2;
       last 10 log lines:
       > build flags: -j2 -l2 SHELL=/nix/store/p7bpdnxqd3i5hwm92mrscf7mvxk66404-bash-5.1-p16/bin/bash PREFIX=\$\(out\) INCLUDEDIR=\$\(dev\)/include BUILD_STATIC=yes BUILD_SHARED=no WINDRES:=x86_64-unknown-linux-musl-windres
       > make[1]: Entering directory '/build/source/lib'
       > compiling static library
       > compiling dynamic library 1.9.4
       > /nix/store/q8zpwwa77zaa5h0p15iiid26g5ak6s7l-x86_64-unknown-linux-musl-binutils-2.38/bin/x86_64-unknown-linux-musl-ld: /nix/store/ravnd17fg4maxzc5ns8vbijn7ah3p4b1-x86_64-unknown-linux-musl-stage-final-gcc-11.3.0/lib/gcc/x86_64-unknown-linux-musl/11.3.0/crtbeginT.o: relocation R_X86_64_32 against hidden symbol `__TMC_END__' can not be used when making a shared object
       > /nix/store/q8zpwwa77zaa5h0p15iiid26g5ak6s7l-x86_64-unknown-linux-musl-binutils-2.38/bin/x86_64-unknown-linux-musl-ld: failed to set dynamic section sizes: bad value
       > collect2: error: ld returned 1 exit status
       > make[1]: *** [Makefile:122: liblz4.so.1.9.4] Error 1
       > make[1]: Leaving directory '/build/source/lib'
       > make: *** [Makefile:57: lib-release] Error 2

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 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

[ ] Fits CONTRIBUTING.md.

(that CI error seems due to a full disk, error: creating directory '/nix/store/add-3770538-0/x/pkgs/applications/version-management/gitea': No space left on device)

Shouldn't this PR be targeting staging?

Shouldn't this PR be targeting staging?

I don't know. Happy to update if it should.

I don't know. Happy to update if it should.

It causes downstream upgrade of 18463 packages.

I don't know. Happy to update if it should.

It causes downstream upgrade of 18463 packages.

I guess that's a yes? So I'll rebase this on top of staging, and change the PR base to staging?

I guess that's a yes? So I'll rebase this on top of staging, and change the PR base to staging?

Yes.


Remove deprecated use of script_files

Fixes #725
Fixes https://github.com/sphinx-doc/sphinx/issues/6088

Is this backwards compat? I believe it should be, but we should make sure to test it on Sphinx 1.8.

Yes it is backwards compatible.

Hi. Could you make a release, please? This issue is blocking us on several projects. Thanks.


[ENHANCEMENT] Add more tests

Add more pytest tests to cover most parts of the code.
Current coverage: 50%
Todo:

[ ] Add tests for ilanguage\Main\_ast.py
[ ] Add tests for ilanguage\Main\_errors.py
[ ] Add tests for ilanguage\Main\_types.py
[ ] Add tests for ilanguage\Main\lexer.py
[ ] Add tests for ilanguage\Main\shell.py
[ ] Add tests for ilanguage\Modules\_core\Console.py
[ ] Add tests for ilanguage\Modules\_core\Math.py
[ ] Add tests for ilanguage\Modules\_core\Random.py
[ ] Add tests for ilanguage\__init__.py
[ ] Add tests for ilanguage\__main__.py

Tests will be done by @Ranastra, I'll do the cleanups and stuff.


When opening a new program Pock disappears for a flash (shows normal touchbar) and then comes back

This didn't happen in Mojave, just started since I updated to Catalina 10.15.1
It works as expected until I open a new app and then Pock goes away for like half a second and you can see the stock touch bar controls, and then Pock comes back. Not a huge deal, just not very visually pleasing.
EDIT: also I just realized that if I click the applications or download folders on the dock, Pock completely goes away until I click away from the folder.

This also appears when you click control center widgets.
This issue happens to me too.


[HW]

Name:
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/malla-haswanth-41ba5817a/
Attach the homework step I screenshots below:

![Screenshot (293)](https://user-images.githubusercontent.com/47265019/120525301-9c342900-c3f5-11eb-918f-b84a1846c6dd.png)

Attach the homework step II screenshots below:

Nice job deploying to production Malla, thank you. Here's your badge -> https://api.badgr.io/public/assertions/gVEfpyMISyKrP9_xOK1VdA?identity__email=mallahaswanth99%40gmail.com


Persistence and resource lifecycle/lifetime

Currently the wording in the Behaviour: Persistence of Updates section is:
"The API implementation MUST persist updates to the core information properties for the lifetime of a resource uniquely identified by its ID, including consistency over reboots, power cycles, and software upgrades."
I think traditional devices which have fairly static UUID allocations are well covered by the statement.
In terms of more dynamic devices I think we might need to better capture the relationship between persistence requirements and lifecycle/lifetime of resources. I think at the very least we need to define what is the lifetime of a resource.
Some options are:

A. Does the lifetime of a resource end when the host Node expects to never use its UUID again? (e.g. a Node which has a remove resource workflow that permanently destroys the use of that UUID and future newly created resources are not expected to reuse that UUID).
B. Does the lifetime of a resource end when its UUID disappears from the APIs hosted by the Node/Device?

For a Node/Device which has a limited number of operating profiles it can swap between, options A and B may result in different persistence outcomes.
For A the Node/Device is required to persist information for every operating profile even if it is currently offline because their lifetime never really ends.
For B the Node/Device only needs to persist the information for the current online operating profile. Switching away from the current operating profile could clear all associated information as the lifetime of resources ends.
Ultimately I believe our goal is to specify what is the minimum guarantee implementers can rely on.

Nicely put!

Update 2023-06-01: Action all to respond to the A/B question so we can look at a PR.

I think in the last call we largely agreed on Option A?
So something like this... please suggest improvements...
The API implementation MUST persist updates to the annotation properties for the lifetime of a resource uniquely identified by its ID, including consistency over reboots, power cycles, and software upgrades.
The lifetime of a resource ends when the API implementation intends not to use its ID again.
If the implementation removes the resource from the API but can reinstate the resource with the same ID later, for example, as a result of switching between operating profiles, the annotation properties MUST/SHOULD be persisted.

"Hibernated and reawakened" is evocative but without further definition seems insufficiently precise to me.
If the example of "switching between operating profiles" isn't helpful, is there a better one?

We wanted to more clearly capture the fact that if a resource is not in the NodeAPI it doesn't necessarily mean its lifetime has ended.

"If the implementation removes the resource from the API but can reinstate the resource with the same ID later"
Any suggestions?


Add tool : Filter_cells_and_genes

Add new tool that can filter cells(columns) and genes (row) from an expression matrix based on different quality controls.

I have no idea why the travis tests fails with that line !
https://travis-ci.org/ARTbio/tools-artbio/jobs/446770315#L585
Do you have an idea ?

When running flake8 on blast_unmatched.py I get the same error. The reason for this is that since the last PR flake8 was upgraded from 3.5.0 to 3.6.0. In python 3.8 escaping in a string that isn't raw breaks code. I will fix this with PR: #318

Yeah.  Yet, how this lea’s branch is connected with blast_unmarched.py ?........

The lint.sh script is run in the tools-artbio directory so it lints all the scripts every time

@ARTbio/artbio-staff Sympa vos nouveaux avatars ;-)
On another note, could you think about a more "expressive" tool name ?
I find Filter cells and genes cryptic enough...

How about filter_sc_expression_matrix ? Maybe a bit too long ?


Can't seem to get it working

Hey there
I tried getting your filter to run but I cannot seem to get it to append any headers what so ever.
My current config is:
<filters>
  <filter name="undertow-cors-filter" class-name="com.stijndewitt.undertow.cors.Filter" module="com.stijndewitt.undertow.cors">
  <param name="urlPattern" value="^/auth/.*" />
   <param name="policyClass" value="com.stijndewitt.undertow.cors.AllowAll" />
</filter>

To make things simpler i removed the param with the urlPattern but that resulted in a lot of nullpointer exception so it seems to be necessary in the current version. This also sort of tought me that the installation of the module/filter itself must be correct.
But even with the urlPattern I haven't seen any CORS headers appended in my requests - what could be wrong? I took the latest state from master.
Thanks a lot for your help
Alessandro

@AlessandroEmm
Will try to get this published to Maven Central and make sure the example is more clear.

@AlessandroEmm
Please try the current release (0.4.0). Also have a look at the README, I updated it to make it more clear. Also the docs about urlPattern were wrong which is probably why you could not get it to work.
Sorry for the bumpy ride but I'm still working towards 1.0. The current release could be promoted to 1.0.0 as-is if I don't find any issues. I'd be very interested in feedback from your end.

Feel free to re-open if you have any questions.

I have the also the problem with the NullPointerException. The following stacktrace is shown in keycloak log:
14:07:20,761 ERROR [io.undertow.request] (default task-1) UT005071: Undertow request failed HttpServerExchange{ OPTIONS /auth/realms/apiman/protocol/openid-connect/auth request {Accept=[*/*], Accept-Language=[de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7], Access-Control-Request-Method=[GET], Accept-Encoding=[gzip, deflate, br], Origin=[http://localhost:8181], User-Agent=[Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.110 Safari/537.36], Access-Control-Request-Headers=[x-requested-with], Connection=[keep-alive], Host=[localhost:8383]} response {}}: java.lang.NullPointerException         at java.util.regex.Pattern.<init>(Pattern.java:1350)         at java.util.regex.Pattern.compile(Pattern.java:1028)         at com.stijndewitt.undertow.cors.Filter.handleRequest(Filter.java:665)         at io.undertow.server.Connectors.executeRootHandler(Connectors.java:360)         at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830)         at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)         at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)         at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)         at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)         at java.lang.Thread.run(Thread.java:748)
My configuration in the standalone.xml is the following:
        <subsystem xmlns="urn:jboss:domain:undertow:6.0" default-server="default-server" default-virtual-host="default-host" default-servlet-container="default" default-security-domain="other">             <buffer-cache name="default"/>             <server name="default-server">                 <http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true"/>                 <https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>                 <host name="default-host" alias="localhost">                     <location name="/" handler="welcome-content"/>                     <http-invoker security-realm="ApplicationRealm"/>                     <filter-ref name="undertow-cors-filter" />                 </host>             </server>             <servlet-container name="default">                 <jsp-config/>                 <websockets/>             </servlet-container>             <handlers>                 <file name="welcome-content" path="${jboss.home.dir}/welcome-content"/>             </handlers>             <filters>                 <filter name="undertow-cors-filter" class-name="com.stijndewitt.undertow.cors.Filter" module="com.stijndewitt.undertow.cors">                 </filter>             </filters>         </subsystem>

The build of the master works. The issue was the wrong location of the module.
Wrong:
\modules\com\stijndewitt\undertow\cors\main
Right:
\modules\system\layers\base\com\stijndewitt\undertow\cors\main


refator: refator some code of Ckb4Ibc endpoint, solved some fatal bugs

background
there are so many bugs in Axon and CKB endpoints which can stop relaying packet events or just miss some of them, to unwrap, here are some reasons make this case happen:

monitor of CKB endpoint always fetches first 5 packet events in the response data of ckb-indexer, so the packet event beyonds 5th won't process
query_* methods both in Axon and CKB endpoints isn't working well (CKB is worse), and Hermes uses them to indicate wether the counterparty has handled the unhandled packet events
the WriteAck packet cell in CKB endpoint should be consumed in the next time of creating new RecvPacket cell, if not do this, WriteAck packet cell is accumulating and consuming relayer's CKB capacity
Axon endpoint should replay recent packet events, because some of them may not be relayed to CKB
at the same time, there can be over two type of packets share the same sequence, for example, SendPacket packet with sequence 14 and WriteAck packet with sequence 14 too, this could cause query issue
currently, forcerelay is doing better than before

change logs

Axon endpoint supports replaying recent packet events
CKB endpoint will fetch IBC events through ckb-indexer in a loop process
packet related query_* methods are refactored in CKB endpoint
CKB endpoint supports consuming useless WriteAck packet cells
CKB endpoint searches single packet cell using a limit of packet status
ckb contracts has updated

related PRs

https://github.com/synapseweb3/forcerelay-ckb-contracts/pull/29
https://github.com/synapseweb3/ckb-ics/pull/18

Is the contract version changed?

no, I'll fix it

workflow_dispatch test
https://github.com/synapseweb3/forcerelay/actions/runs/6717007105/job/18254104374

I doubt this workflow quotes toml in main branch, I check it later


the same conda environment listed 3 times in kernel picker

Testing #11963
after creating a conda env in the workspace and reloading vscode a few times, and disabling the mru kernel picker, I see the same environment listed multiple times:

jupyterlogs.txt

@amunger i think its only dispalyed 2 times, not three.
if you look at the screen shot, the second item is 2.
Please confirm

1st, 3rd and 4th are the same, the third is just a relative path where the others are fully qualified

@amunger please could you:

Replicate this again
Create the conda env again and ensure you capture the logs
When you get the duplicates as well i need the logs (if you happen to reload vscode)

The logs you have provided aren't sufficient as it doesnlt contain the logs from when you created the conda env.
I believe you may have reloaded vscode in between (ie reloaded after creating the env)

note - the MRU kernel picker was used to create the environment and does not show duplicates. Switching back to the old kernel picker will show the duplicates. (C:\SRC\TEST\6.CONDA\PYTHON.EXE in this repro)
environment creation jupyterlogs.txt
kernel picker duplicates jupyterlogs2.txt
environment creation pythonLogs.txt

Switching back to the old kernel picker will show the duplicates. (C:\SRC\TEST\6.CONDA\PYTHON.EXE in this repro)
environment creation jupyterlogs.txt

how did you create the conda env, did you do this manually via the CLI or via the python extension commands

how did you create the conda env
with the MRU kernel picker: Select another kernel... -> Python Environments -> Create python environment -> conda

Found the problem, sometimes the Uri (path to the executable) is upper cased and in other cases its not upper cased.
Here are two different values returned by the Python extension for the same request
debug 09:31:08.170: Get Active Interpreter, Class name = x, completed in 56ms, has a truthy return value, Arg 1: "/c:/src/test/6", Return Value: {"id":"C:\\SRC\\TEST\\6\\.CONDA\\PYTHON.EXE","sysPrefix":"c:\\src\\test\\6\\.conda","envPath":{"$mid":1,"path":"/c:/src/test/6/.conda","scheme":"file"},"displayPath":{"$mid":1,"path":"/c:/src/test/6/.conda","scheme":"file"},"envName":"","uri":{"$mid":1,"fsPath":"c:\\src\\test\\6\\.conda\\python.exe","_sep":1,"path":"/c:/src/test/6/.conda/python.exe","scheme":"file"},"displayName":"","envType":"Conda","version":{"major":3,"minor":8,"patch":15,"raw":"3.8.15 (default, Nov 24 2022, 14:38:14) [MSC v.1916 64 bit (AMD64)]"}}

debug 09:30:57.943: Get Active Interpreter, Class name = x, completed in 39ms, has a truthy return value, Arg 1: undefined, Return Value: {"id":"C:\\SRC\\TEST\\6\\.CONDA\\PYTHON.EXE","sysPrefix":"c:\\src\\test\\6\\.conda","envPath":{"$mid":1,"path":"/c:/SRC/TEST/6/.CONDA","scheme":"file"},"displayPath":{"$mid":1,"path":"/c:/SRC/TEST/6/.CONDA","scheme":"file"},"envName":"","uri":{"$mid":1,"fsPath":"c:\\SRC\\TEST\\6\\.CONDA\\python.exe","_sep":1,"path":"/c:/SRC/TEST/6/.CONDA/python.exe","scheme":"file"},"displayName":"","envType":"Conda","version":{"major":3,"minor":8,"patch":15,"raw":"3.8.15 (default, Nov 24 2022, 14:38:14) [MSC v.1916 64 bit (AMD64)]"}}

@amunger this should be fixed in the latest pre-release version of Jupyter and Python extensxions.
Please re-open if the issue persists.


Error: 'dependOnInheritedWidgetOfExactType' was called on null

I'm getting the following error when calling the Router.generator method:
The following NoSuchMethodError was thrown building IconTheme(color: Color(0xdd000000)):
The method 'dependOnInheritedWidgetOfExactType' was called on null.
Receiver: null
Tried calling: dependOnInheritedWidgetOfExactType<_InheritedTheme>()

The relevant error-causing widget was
    MaterialApp
lib/app.dart:30
When the exception was thrown, this was the stack
#0      Object.noSuchMethod  (dart:core-patch/object_patch.dart:53:5)
#1      Theme.of
package:flutter/…/material/theme.dart:128
#2      Router.matchRoute.<anonymous closure>
package:fluro/src/router.dart:130
#3      Router.matchRoute
package:fluro/src/router.dart:183
#4      Router.generator

It looks like this change may be the source of the bug.
Is there a reason that null is passed for BuildContext here?

I got this err to when I applyedtransitionType: TransitionType.native in the example existed with fluro package .

I'm getting this on web when going straight to a page that is not the initial route

This was also happening to me when my initial route was not "/". Changed that and all good. 🤷🏾♂

same here.
| JPUSH | Flutter | setup:
| JPUSH | Flutter | applyPushAuthority:
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following NoSuchMethodError was thrown building IconTheme(color: Color(0xdd000000)):
The method 'dependOnInheritedWidgetOfExactType' was called on null.
Receiver: null
Tried calling: dependOnInheritedWidgetOfExactType<_InheritedTheme>()

same error, any update?

same error any updates??
I get an error when I have a parameter in the url
http://url.com/profile/1

I have a good fix for this is an update is not push in the next few days I will publish my own temp package that others can pull from.

here the forked package is. hopefully fluro fixes this soon.
https://pub.dev/packages/fluro_fork

Hi @lukef
This has becoming a blocking issue after updating to Flutter 1.17 and Fluro 1.6.3
@brianschardt 's fork (thanks!) seems to do the trick. Any chance for an official fix?
Thank you

I am using Flutter 1.17.1 and Fluro 1.6.3. In my case, both:
transitionType: TransitionType.nativeModal
and
transitionType: TransitionType.native
are preventing navigation from working. The error is output like this:
The method 'dependOnInheritedWidgetOfExactType' was called on null.
I ran into this error in Android Emulator, when i was testing the "Breaking Bapp" app:

If you would like to take a look, simply
git clone (master branch) and try "flutter run" it. After it loads, click on any of the items in the "Characters" tab or in the "Quotes" tab. Because of this error navigation doesn't work, error is printed in the console instead.
If i comment out transitionType, it works. Any idea when this issue could be fixed?
Best regards,
Jim

You can fork it and update it like here https://github.com/theyakka/fluro/pull/166/commits/ca2e1d927f4b68e8824d5d5569925f2a4a6a587f
it works fine for me as i need native transition

here the forked package is. hopefully fluro fixes this soon.
https://pub.dev/packages/fluro_fork

With this forks works correctly!
Thsnk you very much brianschardt

here the forked package is. hopefully fluro fixes this soon.
https://pub.dev/packages/fluro_fork

awesome, thanks heaps.

Thanks for the fork!
Is the Fluro package still maintained? it seems like a pretty big issue with a simple solution available now for ~3 months

Looks like the last commit was around the same time this was opened.  Has this project been abandoned?

Please see https://github.com/theyakka/fluro/issues/184 for an update about the current status of fluro

I am not able to reproduce this. If this is still an issue would someone please post an MVCE and I'll reopen this?

Can somebody using Fluro Fork post on here when they have confirmed the latest build of fluro doesn't have this issue?

Conversely, if someone using Fluro Fork can reproduce this issue on the latest build of fluro, can you please give me as many details as possible so I can get this resolved?

@tobytraylor @lukepighetti I was using fluro_fork and just tried changing to the original fluro package and am still running into this issue.
My project is open source, and can be reproduced on the v4.1.0+40100003 branch available here: https://github.com/CometTools/LunaSea/tree/v4.1.0%2B40100003
You don't need to add any of the modules/software to see the project, just open the drawer and attempt to open the settings page. You can view where I initialize the core router in core/router.dart, the settings router in modules/settings/core/router.dart and then each individual route definition is inside of that file. I can produce a MVCE if necessary, but it occurs specifically with TransitionType.native being used.
Also to note, I am also using the latest Flutter stable branch (1.22.2).

The issue is relatively easy to identify, using the generator, when it calls matchRoute on line 282, it passes a null BuildContext to the function (which is expected, since there is no context available).
Then on line 167 you attempt to access the platform type by calling if (Theme.of(buildContext).platform == TargetPlatform.iOS) {, which is what throws the error since buildContext is null.
The fluro_fork package remedied this by doing a check for a null context: if (buildContext == null || Theme.of(buildContext).platform == TargetPlatform.iOS) {. This could be considered non-ideal, since buildContext could be null for an Android device and it would still return a CupertinoPageRoute.

I'm unable to get null for buildContext except for when the first route / is pushed. So if you have seen null come in at another time I need a way to reproduce it otherwise I cannot provide assistance with this.
I pushed up https://github.com/lukepighetti/fluro/commit/e341fea57c7064f813e57ade807b2910f7cbdb2a but I'm concerned that if you're getting null values regularly then this will just break all transitions instead of providing relief on the first build.

@lukepighetti Here is a MVCE, everything is contained within the main.dart file: https://github.com/JagandeepBrar/fluro-issue-154-MVCE
Let me know if you need anything else on my side.

Is there even a need to separate the cases when using TransitionType.native?
When reading the MaterialPageRoute class documentation, it says:

A modal route that replaces the entire screen with a platform-adaptive transition.
For Android, the entrance transition for the page slides the route upwards and fades it in. The exit transition is the same, but in reverse.
The transition is adaptive to the platform and on iOS, the route slides in from the right and exits in reverse. The route also shifts to the left in parallax when another page enters to cover it. (These directions are flipped in environments with a right-to-left reading direction.)

Maybe this is new since fluro was originally developed, but testing it personally on iOS and Android devices, using TransitionType.material does in-fact keep the platform-specific transition type.

I have created a PR that simply removes the platform check and always uses MaterialPageRoute. I tested it on iOS 14.0-14.2 and Android 9-11: https://github.com/lukepighetti/fluro/pull/191

Merged, thank you so much!


Tests for the file system protocols

Currently, we have no test coverage for the file system related protocols.
@HadrienG2 on #54:

To prevent filesystem tests from having a long-lasting impact on the testing environment (even if there's a bug in them), it would be good to have them operate on a throwaway ramdisk which QEMU discards at the end.

btw: this is partially covered by https://github.com/rust-osdev/uefi-rs/pull/475

I think we can close this. We have multiple tests, see https://github.com/rust-osdev/uefi-rs/blob/main/uefi-test-runner/src/proto/media/known_disk.rs#L301
feel free to re-open if I've missed something


[BUG] Failed to retrieve the stamp contract status from arweave.net.

Describe the bug
I attempted to retrieve the stamp contract (https://sonar.warp.cc/?#/app/contract/TlqASNDLA1Uh8yFiH-BzR_1FDag4s735F3PoUFEv2Mo) status from the arweave.net gateway.
the script located at
https://github.com/xiaojay/warptest/blob/main/src/stamp_state.ts
got error：
2023-05-28T14:30:02.217Z INFO [ArweaveGatewayBundledContractDefinitionLoader] Contract definition loaded in: 699ms []
readState error: Error: Interaction fNRBubM941UdtaGCelUHceMVWKRudFn3ZwETsk2HqBc is not sequenced by sequencer aborting. Only Sequenced transactions are supported by loader ArweaveGatewayBundledInteractionLoader
at ArweaveGatewayBundledInteractionLoader.attachSequencerDataToInteraction (/home/ubuntu/warptest/node_modules/warp-contracts/src/core/modules/impl/ArweaveGatewayBundledInteractionLoader.ts:177:13)
at /home/ubuntu/warptest/node_modules/warp-contracts/src/core/modules/impl/ArweaveGatewayBundledInteractionLoader.ts:119:34
at Array.map ()
at ArweaveGatewayBundledInteractionLoader.load (/home/ubuntu/warptest/node_modules/warp-contracts/src/core/modules/impl/ArweaveGatewayBundledInteractionLoader.ts:119:8)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at async HandlerBasedContract.createExecutionContext (/home/ubuntu/warptest/node_modules/warp-contracts/src/contract/HandlerBasedContract.ts:496:30)
at async HandlerBasedContract.readState (/home/ubuntu/warptest/node_modules/warp-contracts/src/contract/HandlerBasedContract.ts:164:32) contractId: TlqASNDLA1Uh8yFiH-BzR_1FDag4s735F3PoUFEv2Mo
The reason for this issue seems to be that the stamp tx used the "Sequencer-Prev-Sort-Key" tag to indicate the previous tx's sort key, while the ArweaveGatewayBundledInteractionLoader.ts validates tx using the "Sequencer-Last-Sort-Key” tag (https://github.com/warp-contracts/warp/blob/db83105425ceb23c342b52661a98676694cf28d7/src/core/modules/impl/ArweaveGatewayBundledInteractionLoader.ts#L163), causing the transaction verification to fail.
I believe this is a backward compatibility issue and both tag "Sequencer-Prev-Sort-Key" and "Sequencer-Last-Sort-Key" should be supported during verification.
To Reproduce
https://github.com/xiaojay/warptest/blob/main/src/stamp_state.ts
Expected behavior
The contract state obtained from the arweave.net gateway should be consistent with the one obtained from the warp gateway.
Screenshots
https://arseed.web3infra.dev/TDx2_EHWOf4Xri13ObsIX3ymFKe8I8609EZurqfXjnY
Desktop (please complete the following information):

OS:  ubuntu
Node.js v18.14.2
warp-contracts SDK version: v1.4.9
warp-contracts plugins being used (+ versions): no
Browser [e.g. chrome, safari]: no
Version [e.g. 22]: no

Additional context
no

Thanks @xiaojay for the report and analysis, we will look into this issue

yes, I have same issue with arweave.net gateway, hope they cloud solve it

We have reindexed the bundle that contained the above data item.  It is now available on arweave.net/graphql

some more issues with other data-items -> Discord :-)

1.4.11


Add charset to Content-Type header in redpen-server's response.

redpen-server's response does not contain charset information.
If you do not specify it, ISO-8859-1 may be used at application/json in addition to text/*.
ISO-8859-1 is referred to in RFC2616, and used by PowerShell, etc. (sentence is corrupted.)
Please add charset information or use Unicode escape notation(\uXXXX).
PS C:>(Invoke-RestMethod -Uri http://redpen.herokuapp.com/rest/document/validate/ -Method Post -Body @{lang="ja"; format = "json"; documentParser="PLAIN"; document="古池や,蛙飛び込む水の音"}).errors[-1]
sentence               : å¤æ± ã,èé£ã³è¾¼ãæ°´ã®é³
endPosition            : @{offset=4; lineNum=1}
validator              : InvalidSymbol
lineNum                : 1
sentenceStartColumnNum : 0
message                : Found invalid symbol ",".
startPosition          : @{offset=3; lineNum=1}
RFC2616 ( https://www.ietf.org/rfc/rfc2616.txt ),

The "charset" parameter is used with some media types to define the
character set (section 3.4) of the data. When no explicit charset
parameter is provided by the sender, media subtypes of the "text"
type are defined to have a default charset value of "ISO-8859-1" when
received via HTTP. Data in character sets other than "ISO-8859-1" or
its subsets MUST be labeled with an appropriate charset value. See
section 3.4.1 for compatibility problems.

Thank you very much for the valuable report @karronoli! We will reproduce the behavior and fix it.

FYI, it is often a problem at somewhere.
https://github.com/request/request/issues/383
The default encoding ot 'application/json' is UTF-8 at Section 3 in RFC4627
http://tools.ietf.org/html/rfc4627
But some http client doesn't know the encoding.
You may close this issue if you don't concerned.

I'll take care of the issue.

Thanks!

I can request by PowerShell! Thanks!


Obsolete any keyword

Search Terms
any
Suggestion
I read the faq and confirmed that my suggestion is not a duplicate. Here is my suggestion:
Since typescript is supposed to be a type safe scripting language (hence the name) why don't we get ready of the any keyword?
According to the TypeScript documentation,  any was only included to help people migrate from JavaScript to TypeScript.  Using any allows people to continue to bypass all type safety.
Migrating to good writing code in a type safe object oriented language from writing bad code in a procedural language with no type safety is about learning better solutions and creating better habits to produce more maintainable and less error prone code.  Giving the people of option of using any instead of making them declare the type that they intend allows them to continue to violate the very solid engineering principle of intentionality.  If we force them to declare the type, then they will have be more intentional when they do everything from declaring variables to defining abstract generic classes.  Not only that, everyone else who has to interact with their code will understand what they intended to do.
I know that this will break a lot of code, so I suggest it be done in parts.
First, in one release a warning that any is deprecated will be obsoleted in the next major release. At the same time make no_any the default compiler option.   Also provide suggestions for what to use in the place of any in many cases.
Then obsolete it completely in the next major release.  People can determine whether or not their project is worth migrating to that major release.  All projects that use that major release and all subsequent releases will only have truly typesafe code. (Of course, also standard TypeScript objects and methods would also need stop using any as well.)
Use Cases
Enforce the application of sound engineering principles to produce more maintainable and less error prone code for the browser.
People can continue to use bad habits to produce code that is error prone and hard to maintain as long as any is an option.
Examples
// Currently this is legal, but it will produce an error at run time.
doSomething() {
const newFlag: string = 'test';
this.setToFalse(newFlag);
}
setToFalse(flag: any){
flag = false;
}
//Under proposed change this is not legal, so it will be caught at compile time and intended type of flag will have to be declared.
doSomething() {
const newFlag: string = 'test';
this.setToFalse(newFlag);
}
setToFalse(flag: any){
flag = false;
}
//Under proposed change this is not legal just like the current system, so it will be caught at compile time.
doSomething() {
const newFlag: string = 'test';
this.setToFalse(newFlag);
}
setToFalse(flag: boolean){
flag = false;
}
Checklist
My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code - NO
[ ] This wouldn't change the runtime behavior of existing JavaScript code - yes
[ ] This could be implemented without emitting different JS based on the types of the expressions - yes
[ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.) - yes
[ ] This feature would agree with the rest of [TypeScript's Design Goals] -(https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals) YES.

We consider any to be an important escape hatch. There are style settings available to you via eslint or tslint if you want to forbid use of it in your codebase.
Moreover, we don't really ever remove features, including built-in types.


clarify swarm concept

clarify swarm key concept term
Signed-off-by: Charles Smith<EMAIL_ADDRESS>

ping @abronan @mgoelzer @thaJeztah

LGTM

LGTM


Add directives pubids to tests

closes #57

@mico is this ready to go?

@mico is this ready to go?

yes, now it's ready

Thank you @mico! Let's make a release too. Thanks.


Grades for Marks Spreadsheet shows "1-0" when there are no users

I'll take a look at this David.

@jiangha4 Sorry I forgot to assign this issue to Stephen. Can you do #1977 instead?

No problem.


Update to Async/Await Tasked-Based Asynchronous Programming Pattern

I know that this library was designed with the old style of asynchronous programming using the Begin & End pattern.  Is there currently any push to switch to the new async/await pattern?
If so, I'd be happy to help out rewriting the asynchronous methods.  This library has helped me out a bunch and I'd like to contribute back if I could.

Sure, your help would be greatly appreciated. If you don't have time to convert all the methods please feel free to submit a PR for whatever changes you have done, and I'll look and what you've done and repeat for the remaining methods..

I started working on this, but I've been leaving the current Begin & End methods.  Instead I'm creating new methods that end with*Async().  I'm assuming you don't want this to be a breaking change right?

I started working on this, but I've been leaving the current Begin & End methods and wrapping them since they are already tested.
Sounds okay. Perhaps later we can disable those/ make them private and see if the community is okay with that.

All the new Task-based async methods will end with*Async(). I'm assuming you don't want this to be a breaking change right?
Yes, try to avoid breaking changes.

Additionally, I've been updating the documentation within the code as I go through it. Would you rather me submit the updated comments as a separate pull request or keep it together with this?
Keep it together. Changing comments cannot cause any harm IMO :)

@hgupta9  Regarding making those private / disabling them.  I'd say the methods can probably be rewritten in a more "pure" asynchronous way sometime in the future.  The wrapping will work, but it's kind of a quick & dirty way of allowing this to follow the Task-based async pattern.  In the future these methods can probably be re-written async all the way down.
Here's my current plan.  I'm up to step 3 and will be submitting a pull request once I finish this step and test everything out.

Add overrides to the underlying stream sources (FtpDataStream & FtpSocketStream) to support the task-based async pattern.  As of .NET 4.5 virtual methods already exist on the Stream abstract class so they just needed to be added to those two Stream implementations
Wrap all of the current Begin & End asynchronous methods with Task.Factory.FromAsync() to produce an awaitable Task that encapsulates those methods.
Add awaitable Task methods to the UploadFile / DownloadFile (and multi-versions)
Rewrite all *Async methods to remove wrappers and use async/await pattern "all the way down". This would then depreciate the Begin & End methods.

Just a heads up regarding async/await.  They were introduced in .NET 4.5.  In order to prevent any breaking changes I added some additional build configurations for .NET 4 and a new preprocessor variable NETFX45.  For all of the Task-based async methods I added a preprocessor directives to only build #if (CORE || NETFX45)

Wow! Impressive! Can't wait for the PR.

@hgupta9  Ha!  Don't get too excited.

Thank you so much.

@jblacker Do you think your PR is ready for release? If you think it is I will create a release for nuget. I ran the tests you sent and they work fine.

@jblacker Published on nuget - https://www.nuget.org/packages/FluentFTP/16.5.0

How does your PR compare to https://github.com/rkttu/System.Net.FtpClient.Async/blob/master/System.Net.FtpClient.Async/System.Net.FtpClient.Async/FtpClientAsyncExtension.cs?

@hgupta9  Never seen that library, but certain parts are very similar.  However, not everything is since I went deeper than just adding async wrappers to the FtpClient methods.  I do plan on  unwrapping the methods and truly making them async all the way down in the near future.


Netflixoss build

genie-pull-requests #83 FAILURE
Looks like there's a problem with this pull request

genie-pull-requests #84 SUCCESS
This pull request looks good

Hey @rspieldenner,
A few questions about this pull request I wanted to check with you on.

Why did you take the common dependencies from the root build.gradle and distribute them to all the subprojects? This seems to create more work when we want to go to update these packages as we need to remember to do it in all the projcts.
Why did you take the () wrappings off all the dependencies that didn't explicitly need them? Do they hurt something? I had left them on just to make it easier if we ever had to add some closures.
What is the value of putting jcenter() above mavenCentral() for the dependencies?
For the code analysis stuff I believe I put in the findbugs toolversion explicitly since we weren't on gradle 2.+ yet, now that we will be is that still needed?
I understand why you changed the lines like compile project.parent.childProjects.get('genie-common') to compile project(':genie-common') as this is the standard and cleaner way to do this. However it was done to support building internal Genie via submodule and wrapping the OSS build. I believe this way didn't work in the past which is why I had to change it. Can you change it back or we'll need to figure out another solution for this which may be more work than we can do before 2.1.0 release needs to go?

Thanks,
Tom

I have found that the grand majority of people use that top level dependencies block as a dumping ground for everything and aren't good about keeping them minimal. So my default is to have all dependencies for a project in one block. I also find it easier to reason about dependencies if they're all in one place instead of needing to look at two.
I try to keep my build.gradle as clean as possible so parentheses got deleted out of habit.
I like bintray and jcenter better than mavenCentral. mavenLocal should be a fallback not first.
didn't check
hopefully we can do your internal build cleaner than it currently is


Proofread

[ ] intro
[ ] notation
[ ] steady
[ ] stretched
[ ] tilted
[ ] conclusion

[x] algorithms
[ ] figures
[ ] listings
[ ] theorems


Add new RSS delta metric that removes baseline RSS

As discussed here: https://forums.swift.org/t/compiler-optimisations-for-functional-style-collection-algorithms/68291/17

https://github.com/wadetregaskis/Swift-Benchmarks/commit/eb094691e1dae9d396446d9cad0f52dc46bf3925

Fixed with 1.14.0


pyramid-swagger should not assume that body is present

While working with endpoints which specify an optional body parameter pyramid-swagger raises a really ugly exception related to the fact that the library is trying to decode an empty body.
The raised exception looks like
self = <json.decoder.JSONDecoder object at 0x10e811198>, s = '', idx = 0

    def raw_decode(self, s, idx=0):
        """Decode a JSON document from ``s`` (a ``str`` beginning with
            a JSON document) and return a 2-tuple of the Python
            representation and the index in ``s`` where the document ended.

            This can be used to decode a JSON document from a string that may
            have extraneous data at the end.

            """
        try:
            obj, end = self.scan_once(s, idx)
        except StopIteration as err:
>           raise JSONDecodeError("Expecting value", s, err.value) from None
E           json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

NOTE: the stacktrace above is obtained by running python -m pytest tests/acceptance/request_test.py::test_post_endpoint_with_optional_body[1.2-body0] on sha 79a5cfa2c57b02dbbe351ffc5eaa48b157542f88
In order to prevent unwanted JSON decoding we need to ensure that the PyramidSwaggerRequest will not call self.request.json_body if the body is emtpy.
While writing checking tests I've noticed that object validation fails either on Swagger 1.2 and Swagger  2.0.
Swagger1.2 validation is handled by this library and the fix is alraedy present on this PR (otherwise tests would have been red), while the Swagger2.0 validation is performed by bravado-core.
A PR will be opened for that project too, but in the mean time Swagger 2.0 allows us to disable request validation if needed.

Coverage increased (+0.001%) to 99.558% when pulling 32dd016b85bcb3ad39cfad2049bc4e42c9814d4f on macisamuele:maci-not-assume-that-body-is-present into 2b91cb00ef083d389389cb071fc66677cf0512ff on striglia:master.

Coverage increased (+0.001%) to 99.558% when pulling 32dd016b85bcb3ad39cfad2049bc4e42c9814d4f on macisamuele:maci-not-assume-that-body-is-present into 2b91cb00ef083d389389cb071fc66677cf0512ff on striglia:master.

Coverage increased (+0.001%) to 99.558% when pulling 32dd016b85bcb3ad39cfad2049bc4e42c9814d4f on macisamuele:maci-not-assume-that-body-is-present into 2b91cb00ef083d389389cb071fc66677cf0512ff on striglia:master.

Coverage increased (+0.001%) to 99.558% when pulling 32dd016b85bcb3ad39cfad2049bc4e42c9814d4f on macisamuele:maci-not-assume-that-body-is-present into 2b91cb00ef083d389389cb071fc66677cf0512ff on striglia:master.


[DOCS] Typo issue on documentation.

Description
It should Joining instead of Join
Page URL: https://www.biodrop.io/docs/open-source-roadmap/where
Screenshots

Do you want to work on this issue?
Yes
Additional information
We can also use this issue to keep adding such minor typos and issues in the docs.

Thank you for raising @Abhishek-90 I have assigned this to you.

Hello, I have made the changes required for this story, but I see that the link to EddieHub is just plain text, should create a link in the place? Refer the image where the link is present https://eddiehub.org I can create a link here.


Reagent Allocation -> Rank 2 simultaneously ticks Rank 3 option and can't be unticked

Before the latest update, it was possible to use the Recipe Scan with only Rank 2 mats, but that feature doesn't seem to work anymore. When I click on Reagent Allocation -> Check Rank 2, Rank 3 is also checked.

The Rank 3 can't be unticked. With the Rank 1 Allocation it works ands generates the recipes with only Rank 1.
So is this a bug or is it just not possible anymore to only use Rank 2 materials and make a Recipe Scan? Is this something on my end?
Regards

19.4.1


Add podman as a dependency in the build

I can confirm that adding that podman dep fixed the build and generated an image, I was able to rebase my thinkpad to it, amazing!


Update to byteorder v1.1.0

Shouldn't cargo automatically pull in the newest?

Probably however I couldn't use byteorder v1.1.0 as a direct dependency because Cargo was complaining about bytes using v1.0.0. I don't have the exact error message anymore, but I can try to get it again.

Apparently removin Cargo.lock fixes it, not sure why I didn't think about that last night. But in any case this isn't needed anymore. Sorry for the noise.