[Bug]: Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment
Commit ID
Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment
Other environment information
WhatsApp :- 📞+91<PHONE_NUMBER>, Call Girls in Goa – We brings offer model independent genuine Goa girls our high class luxury and premium call girl agency service We are the best leading Goa girls service providers in Goa who can provide you with all kinds of hot and sexy female girls near Oyo 5-star hotels. Suppose you want a unique and memorable experience with a hot and beautiful call girl. in that case, this is the perfect place for you.$A19

Get A Date with Independent Goa girls Tonight

When meeting a Goa girls for the first time, be sure to keep things light. Avoid becoming overly intimate right away as she might not respond positively to this approach. Additionally, they can accompany you to parties, restaurants and any other location of your choosing as well as business meetings - treating you like royalty while fulfilling all of your desires. These girls are not just beautiful; they are educated and intelligent as well. Well-mannered and capable of speaking multiple languages, these ladies will make great partners for bed or romantic dinner dates alike.

Goa Escort Service is known for both their sexuality and academic credentials. Many are graduates from top universities with high-standards of education; others possess several languages fluency as well From French kissing and sexing, through grabbing and even deep throat consumption and pussy teasing. They know just what their clients need in terms of sensual fulfilment.

 These beautiful young ladies boast soft lips, stunning curves, and flawless skin - the ideal partner for any event imaginable from a romantic date to wild night of kinky fetishes. Always up for a challenge, these girls delight clients by playing playful games while dressing any way that you request - from an alluring one-piece suit or jeans and top combo all the way through to semi-nude or Indian wear attire.
Select Goa Call Girls Who Have Deep Curves

Goa Call Girls are absolutely captivating and attractive, from their full bods, killer body language and seductive voices to their stunning big boobs, killer body language and alluring seduction voice.

Independent Call Girls Goa is party lovers and love exploring new locations. They will take you to all the best bars, clubs, restaurants, discos and entertainment spots.

Actual behavior
Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment
Expected behavior
Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment
Steps to reproduce
Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment

Additional information
Goa Call Girls Whatsapp Number →✬<PHONE_NUMBER> →✬ Escort Service With Cash Payment

WhatsApp :- 📞+91<PHONE_NUMBER>, Call Girls in Goa – We brings offer model independent genuine Goa girls our high class luxury and premium call girl agency service We are the best leading Goa girls service providers in Goa who can provide you with all kinds of hot and sexy female girls near Oyo 5-star hotels. Suppose you want a unique and memorable experience with a hot and beautiful call girl. in that case, this is the perfect place for you.$A19
Get A Date with Independent Goa girls Tonight
When meeting a Goa girls for the first time, be sure to keep things light. Avoid becoming overly intimate right away as she might not respond positively to this approach. Additionally, they can accompany you to parties, restaurants and any other location of your choosing as well as business meetings - treating you like royalty while fulfilling all of your desires. These girls are not just beautiful; they are educated and intelligent as well. Well-mannered and capable of speaking multiple languages, these ladies will make great partners for bed or romantic dinner dates alike.
Goa Escort Service is known for both their sexuality and academic credentials. Many are graduates from top universities with high-standards of education; others possess several languages fluency as well From French kissing and sexing, through grabbing and even deep throat consumption and pussy teasing. They know just what their clients need in terms of sensual fulfilment.
 These beautiful young ladies boast soft lips, stunning curves, and flawless skin - the ideal partner for any event imaginable from a romantic date to wild night of kinky fetishes. Always up for a challenge, these girls delight clients by playing playful games while dressing any way that you request - from an alluring one-piece suit or jeans and top combo all the way through to semi-nude or Indian wear attire.
Select Goa Call Girls Who Have Deep Curves
Goa Call Girls are absolutely captivating and attractive, from their full bods, killer body language and seductive voices to their stunning big boobs, killer body language and alluring seduction voice.
Independent Call Girls Goa is party lovers and love exploring new locations. They will take you to all the best bars, clubs, restaurants, discos and entertainment spots.


Fix tests in Docker

Allow to run server tests when Chrome is not installed.

\сс @miherlosev @AlexKamaev


Please add the constraint JSON serialize setting in FileManagerComponent/Default.cshtml

I think you need to add the constraint JSON serialize setting in this file to avoid my custom JSON setting to affect it.

My custom JSON setting will affect it in below image

issue fixed in my fork since HgoFileManager is no more dependent on json configuration


[BUG] OAuth2 config-> JwtDecoder / NimbusJwtDecoder still uses RestTemplate() instead RestTemplateBuilder

Important: related issues: Connecting to Azure-AD via proxy #26493 #30456
Short story:
Add JwtDecoderFactory into AadOAuth2ClientConfiguration or AadWebSecurityConfigurerAdapter with the jwtDecoder that uses RestTemplateBilder.
  /**
   * Creates jwt decoder factory.
   *
   * @return The factor.
   */
  @Bean
  @ConditionalOnMissingBean
  public JwtDecoderFactory<ClientRegistration> createJwtDecoderFactory(JwtDecoder jwtDecoder) {
    return (ClientRegistration context) -> jwtDecoder;
  }

Long story:
The created AuthentifactionProvider (oauth2Login() ) by AadWebSecurityConfigurerAdapter#configure(HttpSecurity http) uses the default JwtDecoder /NimbusJwtDecoder created by OAuth2LoginConfigurer<HttpSecurity> oauth2Login().
This configurer tries to find  a bean of JwtDecoderFactory .

If no jwtDecoderFactory found, then will OidcAuthorizationCodeAuthenticationProvider creates  a new JwtDecoderFactory that uses default RestTemplate():

After calling NimbusJwtDecoder buildDecoder() with default RestTemplate():

@chenrujun could you please follow up?

Hi, @damir78 , thanks for reaching out. I'll investigate this issue ASAP.

Closing in favor of #31347

Reopen this issue because current plan to fix this issue by a standalone PR.


Allow images to be rotated

Portrait, upside down, etc

Implemented in https://github.com/HerrZatacke/gb-printer-web/commit/28d332424ad6288024de99b6f635130e634d100a


Add arbitrary rule data to ECP

Ref. https://issues.redhat.com/browse/HACBS-2042

Let's merge this and try to work with it, I think it is safe to add now, and modify or remove if we need to in the future.


Why use checkpoint instead of model_init during LMF

Hi, thanks for your great contributions to WeSpeaker! I’ve been reviewing the training code, and from what I understand, ‘checkpoint’ is used to load the full model weights when resuming training after an interruption. On the other hand, ‘model_init’ is used to load parts of the weights (everything except for the projection layer), where the projection layer is initialized randomly for fine-tuning on a specific task.
My question is: why is ’checkpoint‘ used during the LMF (Large Margin Fine-tuning) stage instead of model_init? When the number of classes changes, the ’checkpoint‘ will also randomly initialize the projection layer (with ’strict=False‘), which seems similar to how ’model_init‘ works. What is the difference between the two approaches?
Additionally, if ’checkpoint‘ can continue training when the number of classes remains the same (and initialize the projection layer when the number of classes changes), what is the specific role of ’model_init‘?
Thank you very much for your clarification!

Hello, thanks for your good question!

The difference of checkpoint and model_init is exactly what you understood in your first paragraph. checkpoint is designed for training resuming after an interruption, which model_init is designed for training on dataset A and then fine-tuning on another dataset B, for example.
checkpoint is loaded for both speaker model and projector, while model_init only loads the speaker model. If we use the checkpoint mode to load a checkpoint with different projector output size, the error occurs even strict=False is used (see the following picture). We load the speaker model before adding the projector layer in model_init mode, which avoids this problem.
Why checkpoint is used in LMF? We need the projection layer to be loaded rather than randomly initialized during LMF, but we only use its first 1/3 output nodes, so we set speed_perturb=False (https://github.com/wenet-e2e/wespeaker/blob/2751dd2caac42f5d58eea29b8b8f971cfb0ed0e5/wespeaker/bin/train.py#L142). This could not be done if using the model_init mode.

Hello, thanks for your good question!

The difference of checkpoint and model_init is exactly what you understood in your first paragraph. checkpoint is designed for training resuming after an interruption, which model_init is designed for training on dataset A and then fine-tuning on another dataset B, for example.

checkpoint is loaded for both speaker model and projector, while model_init only loads the speaker model. If we use the checkpoint mode to load a checkpoint with different projector output size, the error occurs even strict=False is used (see the following picture). We load the speaker model before adding the projector layer in model_init mode, which avoids this problem.

Why checkpoint is used in LMF? We need the projection layer to be loaded rather than randomly initialized during LMF, but we only use its first 1/3 output nodes, so we set speed_perturb=False (https://github.com/wenet-e2e/wespeaker/blob/2751dd2caac42f5d58eea29b8b8f971cfb0ed0e5/wespeaker/bin/train.py#L142). This could not be done if using the model_init mode.

Thank you very much for your response. I have learned a lot from it. However, I still have one more question. In the third part of your response, the link you provided shows how speed perturbation is disabled and the projection layer’s number of classes is changed. But I don’t quite understand in which part of the code you use only the first 1/3 of the projection layer’s nodes?

We still preserve all projection layer's node. Since speed_perturb=False, the data pipeline only produces training samples without speed perturb, i.e. speed is always 1.0. Therefore, during LMF, only the first 1/3 classes have corresponding training samples while the last 2/3 classes will not.


Add support for projected volume kubeconfig

How to categorize this PR?

/area security
/kind enhancement
What this PR does / why we need it:
This PR adds the option to configure a projected volume for the validator which can be used as a kubeconfig. It is for example needed, if operators generate their kubeconfigs for the virtual garden cluster via the TokenRequestor.
Release note:

The `gardener-extension-admission-cilium` chart allows to optionally configure a projected volume based kubeconfig.

/test pull-extension-networking-cilium-e2e-kind

/test pull-extension-networking-cilium-e2e-kind


Iroha 1 build breaks when Abseil lib is built on Ubuntu 20 LTS

Yesterday, bzealous007 reported an issue with Iroha builds in Hyperledger Iroha Community Discord.
Context

Ubuntu 20 LTS, 64 bit
Build stops on Abseil: absl/debugging/failure_signal_handler.cc on line 139 with mismatched types, std::initializer_list<_Tp> and long int
Git commit: a544eb269e
Log file

I am trying to check if I can suggest the Iroha Builder as a solution.
First attempt is a failure (log is attached below), but since the network disappeared globally on my machine, I am re-trying it.
ibuilder_Sep_22.log

@6r1d @appetrosyan I think it was fixed here: https://github.com/hyperledger/iroha/pull/2902 so the issue can be closed

Thank you, @baziorek.


rpm command not found

I am trying to instsall VART on a custom board, however it cannot find rpm:
bash: rpm: command not found
or:
sh: rpm: command not found
It also does not work with dpkg....

@kevinkit
It seems that there are no rpm and dpkg command in the custom system.
You can unzip the vart packet in your host, then copy the vart libraries to your custom board. The following are the unzip command.
rpm2cpio libunilog-1.2.0-r.aarch64.rpm | cpio -idmv
rpm2cpio libxir-1.2.0-r.aarch64.rpm | cpio -idmv
rpm2cpio libtarget-factory-1.2.0-r.aarch64.rpm | cpio -idmv
rpm2cpio libvart-1.2.0-r.aarch64.rpm | cpio -idmv
After you unzip the vart packet, you will find the vart libaries under ./usr/lib/.

Just to be clear, I will find the vart libraries on the host machine in ./usr/lib and will then copy it on my target device in the folder ./usr/lib/

Just to be clear, I will find the vart libraries on the host machine in ./usr/lib and will then copy it on my target device in the folder ./usr/lib/

Yes. This method works, too.


Improve the pauseAfterRound sample code

The Duration can be const, and the text argument should have a trailing comma.

Looks wonderful!


Only one file_io

This is just a bit of code cleanup.
We currently have a lib/jxl/base/file_io.h and a tools/file_io.h and they basically duplicate the same code (a function to read a file and one to write a file) with some minor differences like the order and types of the arguments.
The only code that uses file io in lib/jxl/ are some of the tests; libjxl itself doesn't do any file io. So it's better to just remove the lib/jxl/base/ version of the file io code and keep only the one in tools/.

Moving file_io.h to lib/extras/ instead of lib/jxl/base and tools/, since that seems to be the most logical place for it after all...


Color for Purging is blue, should probably be red

v0.27.0-rc1
Steps:

Create multiple containers
Delete containers and wait (so remove turns to purge on it's own)

Results:
Purge color is blue, same as restoring
Expected:
Purge color should probably red

the blue purge is across the application, not just for containers.

Icons and colors were fairly inconsistent and all over the code before.. moved the default set of icons and colors for each state to a single place and there's now just a few overrides for things that need specific icons/colors.
You can view the default list here: https://github.com/vincent99/ui/blob/d321ae4b80be0371dc036f1669f47f1eb07316f0/app/mixins/cattle-transitioning-resource.js
I also made all the transitioning-ey ones the blue color (despite this issue).  Sometimes they were black, sometimes red before.  Now anything that is in a transitioning type state (starting, stopping, removing, purging, etc... largely the ones ending in ing) will be blue, and things that aren't transitioning will be the other colors but never blue.  This makes transitioning things stand out more to make it easier to spot what's changing, I think.

v0.27.0-rc4
Verified fixed


Add empty mutations declaration to doc

Fixes ash-project/ash_graphql/issues/44

So this is a bit complicated. I'm going to have to fix this in a different way because this fix only works if you have some resources that define a mutation, and the ergonomics of that aren't fun. I'm exploring options at the moment.


Add support for YAAC

Hello,
here is another multiplatform client that would be great to get to work with the LORA module.
I tried to set it up like the other examples here but i can't get it to connect neither bia TCP/IP nor via Serial.
https://www.ka2ddo.org/ka2ddo/YAACdocs/config_kissovertcp.html

there is Serial output and also KISS output (TNC2 encapsulated)
did both not work?

yea i tried both options and nothing happens.

Here is a screenshot from the serial option

will try to write the YAAC dev to know what I should do.

Could you please try two variants, for both the TNC Option must be switched on in the iGate.

KISS over TCP: Enter IP from iGate, Port 8001, enter Callsign, enable Transmit, disable TEMP1-1, enable WIDE1-1, disable Beacon, Protocol RAW AX25

Serial Option: Device name /tmp/tnc, Bauf 115200, enter Callsign, enable Transmit, disable TEMP1-1, enable WIDE1-1, disable Beacon, Protocol RAW AX25
Then go to a console and enter  socat PTY,link=/tmp/tnc TCP:ip_of_iGate:8001 &

as 3rd option (but this is not your origin question), you can run XAstir as APRS Client with socat out of option 2:

it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC.
Would the socat method then also theortically work for PAT?

at the moment. I am not entirely sure. there are not that many APRS stations around me to test if i am receiving and on which interface that is. I will need to try again

it does seem that either the tcp/ip or the serial worked as i was receiving stations however when i try to send out any beacons nothing shows up on aprs.fi. The lora-aprs module does show up regularly sending beacons but nothing appears from YAAC.
Would the socat method then also theortically work for PAT?

Take care not to mix up things:
When the iGate runs in TNC mode you can access it via Port 8001. This makes sense if either

the iGate is not connected to APRS-IS and you want to see the stations on the map of XAstir or YAAC
if the is or is not connected to APRS-IS and you want to send and receive messages through the iGates SSID via XAstir
if the iGate is connected to APRS-IS and you additionally want to see the output

In all cases the functionality of connection to aprsis, digipeating, beaconing, ... shall be done via the iGate from Ricardo configurable in the webUI

Would the socat method then also theortically work for PAT?

Basically yes, socat "emulates" a serial KISS interface to PAT and a TCP KISS interface to the iGate

yes, the lora-aprs module is transmitting correctly to aprs.fi the basic hardware installation works without any issues.
yes the ideal would be to be able to connect to the APRS-IS network via the hardware module, and then use YAAC or similar to send beacons, receive stations, send messages etc.
At the moment I am simply not sure if the TCP/IP is working or the Serial Variant is working, if anything is really working at all.
All I can say is that at one point some additional station data did appear on YAAC. However I am certainly not able to transmit anything into the APRS-IS network from YAAC or similar

yes, the lora-aprs module is transmitting correctly to aprs.fi the basic hardware installation works without any issues.

ok

yes the ideal would be to be able to connect to the APRS-IS network via the hardware module, and then use YAAC or similar to send beacons, receive stations, send messages etc.

ok except the beaconing. This should be done through the iGates configuration

At the moment I am simply not sure if the TCP/IP is working or the Serial Variant is working, if anything is really working at all. All I can say is that at one point some additional station data did appear on YAAC. However I am certainly not able to transmit anything into the APRS-IS network from YAAC or similar

Socat and XAstir are working perfect with the configs I sent you, I have this running in test-setup

In terms of sending a beacon from YAAC. Would it not be possible to set the LORA board with callsign:5 and then send a beacon from YAAC with callsign:15

sure, but what is the sense behind ?
Pure sending a beacon to RF or APRS-IS would work, but the way back (if someone wants to drop you a message would be broken up.
For this case you would need to connect to APRS-IS via YAAC and use the iGate as pure hardware lora module. All "intelligence" would have to be done by YAAC. There are more elegant solutions.
Maybe you explain what you are targeting, then we can help you to find a suitable solution.

so if i am supposed to data transfered when using socat, I don't see anything.
So there is still some issue

so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue

How do you try to transfer data ?

I am not sure what you mean, which data exactly? isn't this simply supposed to show any data sent from YAAC when using the tnc option?

I tried using YAAC with the LoRa Digi/IGate and it worked fine with TCP KISS.
Of course, you need to "Select APRS Server" in the LoRa Digi/IGate configuration.
Here is another approach to provide a bridge between LoRa APRS and the existing regular APRS RF network.
https://github.com/wb2osz/direwolf-doc/blob/main/APRS-LoRa-VHF-APRS-Bridge.pdf
73,
John WB2OSZ

then something may be wrong with my network @wb2osz becuase nothing seems to work as expected.
the kissutil does seem to connect but i don't know much more after that.

so if i am supposed to data transfered when using socat, I don't see anything. So there is still some issue

could you try to start socat with -v option ? Then it should show you more

nothing at all.
I even enabled the syslog option and there is only one entry
APRSIS TX / StartUp_Status / https://github.com/richonguzman/LoRa_APRS_iGate 2024.06.15
nothing more is being written to the logs.
Sending and receiving packets to and from the module itself is fine and the module and it's SSID can be found on aprs-fi.

ah finally some data appeared on the socat -v output, although the syslog is still just one entry

ok, syslog is not working when on TNC mode, so this is normal.
When you RX or TX data it could be read in clear-text in the 1st digit of every line...

in any case the data that appears on the syslog output is only what is being sent from YAAC, nothing else. So the data is still not reaching the lora module for some reason.

basic question, in iGate config, have you:

Section "Station", Symbol, set to "Red Diamond with L", entered valid callsign
Section "APRS-IS", enable "Enable APRS-IS connection" and "Gate APRS-IS Messages to RF"
Section "Beaconing", enable "Send our beacon to APRS-IS"
Section "LoRa", enable "Enable LoRa-TX" and "Enable LoRa-RX" and set to same freq

?

Yes, this is why the iGate works and send packages to aprs.fi without an issue. There is something else happening when trying to connect to the igate either via serial or tcp/ip which doesn't seem to work

what is the callsign and ssid which is on iGate and YAAC ?

i'd rather not provide my callsign, in any case the callsign with the iGate ssid is clearly visible on aprs.fi.

please have a look on https://www.findu.com/cgi-bin/raw.cgi?call=CALLSIGN and replace your callsign and ssid in this link.
The link is RAW APRS_IS data.
Check if something was TX from the iGate which looks like what you wanted to have.

its interesting because now of all of a sudden the two ssid's from YAAC just appeared on APRS.fi. So I really don't know what is going on


SIGABRT on matmul()

libc++abi.dylib: terminating with uncaught exception of type Xbyak::Error: can't protect
I got this error on matmul using example from git repo readme with additional row in input data
struct MLPClassifier {
    var w1 = Tensor<Float>(repeating: 0.1, shape: [2, 4])
    var w2 = Tensor<Float>(shape: [4, 1], scalars: [0.4, -0.5, -0.5, 0.4])
    var b1 = Tensor<Float>([0.2, -0.3, -0.3, 0.2])
    var b2 = Tensor<Float>([[0.4]])

    func prediction(for x: Tensor<Float>) -> Tensor<Float> {
        let o1 = tanh(matmul(x, w1) + b1)
        return tanh(matmul(o1, w2) + b2)
    }
}
let input = Tensor<Float>([[0.2, 0.8], [0.2, 0.8]])
print(input.shape)
let classifier = MLPClassifier()
let prediction = classifier.prediction(for: input)
print(prediction)

This issue was submitted in JIRA by Artiom Bastun here: https://bugs.swift.org/projects/TF/issues/TF-1230.  Moving from JIRA to Github Issues as much as possible for the project.

Followup comment from Artiom Bastun:
I managed to get around this with
let locale = Python.import("locale")
locale.setlocale(locale.LC_ALL, "")

I guess it's the same issue like this one https://github.com/Microsoft/homebrew-mssql-release/issues/18

I get the same error even with applying the said work-around. Problem persist on both release and developer versions of S4TF
let a: Tensor<Float> = [[0.0, 1.0, 0.0],
 [0.0, 1.0, 1.0],
 [1.0, 1.0, 1.0]]

 let b: Tensor<Float> = [[-0.074010275, -0.074010275, 0.14814812],
 [ 0.12646824, 0.12646824, 0.12646824],
 [ -0.05096831, 0.14284894, 0.14284894]]

 print(matmul(a, b))

After continued tinkering, it seems that there is issues when predefining a tensor with its shape.
If I create the same tensor and specifying the shape
let a = Tensor(shape: [3,3], scalars: [0.0, 1.0, 0.0, 0.0, 1.0, 1.0, 1.0, 1.0, 1.0])
let b = Tensor(shape: [3,3], scalars: [-0.0740, -0.0740,   0.148, 0.126,   0.126,   0.126, -0.050,
print(matmul(a, b))

the code works.
I'm not sure if this is a bug with tensorflow or its just how it works.

I get the same error even with applying the said work-around. Problem persist on both release and developer versions of S4TF
let a: Tensor<Float> = [[0.0, 1.0, 0.0],
 [0.0, 1.0, 1.0],
 [1.0, 1.0, 1.0]]

 let b: Tensor<Float> = [[-0.074010275, -0.074010275, 0.14814812],
 [ 0.12646824, 0.12646824, 0.12646824],
 [ -0.05096831, 0.14284894, 0.14284894]]

 print(matmul(a, b))

Could you please share details on how you reproduced an error given this code?
I couldn't reproduce it in Colab, or locally on macOS.

I dunno where the problem is but it happens with matmul for two matrices, it works when multiplying vector and matrix.

Also there isn't error when using Python 2.7:
PythonLibrary.useVersion(2, 7)
or setting locale for Python 3.7
locale.setlocale(locale.LC_ALL, "")
I'm using latest swift tensorflow toolchain on mac os 10.15.4, xcode 11.4.1


Spyder crashed suddenly and not opening anymore

I cannot open spyder after it crashed suddenly.
I tried :
Windows restarted
spyder --reset
Traceback I am getting:
Traceback (most recent call last):
  File "C:\ProgramData\Anaconda3\envs\roses\lib\site-packages\qtpy\__init__.py", line 204, in <module>
    from PySide import __version__ as PYSIDE_VERSION  # analysis:ignore
ModuleNotFoundError: No module named 'PySide'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\ProgramData\Anaconda3\envs\roses\Scripts\spyder-script.py", line 10, in <module>
    sys.exit(main())
  File "C:\ProgramData\Anaconda3\envs\roses\lib\site-packages\spyder\app\start.py", line 210, in main
    from spyder.app import mainwindow
  File "C:\ProgramData\Anaconda3\envs\roses\lib\site-packages\spyder\app\mainwindow.py", line 45, in <module>
    requirements.check_qt()
  File "C:\ProgramData\Anaconda3\envs\roses\lib\site-packages\spyder\requirements.py", line 41, in check_qt
    import qtpy
  File "C:\ProgramData\Anaconda3\envs\roses\lib\site-packages\qtpy\__init__.py", line 210, in <module>
    raise PythonQtError('No Qt bindings could be found')
qtpy.PythonQtError: No Qt bindings could be found

Versions
Windows 10
Anaconda

Hey @vivigb, thanks for reporting. Please take a look at our video to learn how to solve this problem.

Closing due to lack of response.


fix(libscap): call vtable->free_handle at shutdown

Signed-off-by: Luca Guerra<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-udig

/area libscap

/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
It looks like the vtable function free_handle exists but is never called. It looks like the right place is in scap_close right before freeing the main scap handle.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

Hi @LucaGuerra. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: LucaGuerra
To complete the pull request process, please assign gnosek after the PR has been reviewed.
You can assign the PR to them by writing /assign @gnosek in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi Luca, thanks for the PR!
/cc @gnosek
/ok-to-test

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gnosek, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 5d3e4bc2de1103de4fb8de17469ce3d0455660f0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, gnosek, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, gnosek, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


add patra webapp

add https://patra.webjeda.com/ webapp

Thanks for the submission. Nice work too. 👍
I think this isn't quite at the scope needed for awesome-sveltekit yet. Happy to reconsider down the road though if the patra grows. Keep it up!


Simplify ChunkIterator, return start, stop, table

Instead of the iterator protocol, it now uses the sequence protocol. This allows random access and simplifies the internal book-keeping.

Instead of storing start, stop on the Iterator, they are returned together with the table(s).

This made the implementation of the apply tool reading the data only once much easier.

Perhaps add collections.abc.Sequence as a base class for ChunkedIterator just for developers to understand what kind of object this is.

That would add a ton of mix-in methods like "in", "count", "index" etc. which I am not sure is useful.


handling multiple graphs

In numerous locations in the documentation, it has been mentioned that it is possible to handle multiple Graphs, but I couldn't find any example.
Since Session only support a single Graph, it seems the only way of doing it is to create multiple Session instances.
Is it safe to have multiple instances Session at the same time?
if not, what is the proper way of handling multiple Graphs?
Thanks

You can do both ways:

Create multiple sessions;
Create a big graph which includes multiple small graphs.

And they can share the same set of variables and you just need to make sure it picks the right graph/session to run.

Please reopen if you have further questions.

Did anyone actually create an explicit (maybe small) example using either of the two suggestions?

I want an example, too. In principle I know how it works, but what's the details?


Get rid of Shape, IndexMode/EditMode and Extent

Discussed in https://github.com/DotSpatial/DotSpatial/discussions/1419

Originally posted by jany-tenaj January  7, 2022
I'm thinking of getting rid of Shape, IndexMode/EditMode and Extent.
As far as I have read, Extent was added, so we didn't have to reference NetTopologySuite in every Project. And something about Envelope being heavier that Extent. If I have a look at Extent and Envelope source code I can't follow the second argument because the code seems to be almost the same.
Including NetToplogySuite is quite simple, so this shouldn't be a reason to have two classes that basically do the same.
What I see is that we have to convert between Envelope and Extent whenever we switch between Geometries and display related things. Furthermore there seem to be errors inside Extent methods that were fixed in Envelope at one point but not in Extent.
Based on the fact, that we have not much time I don't see the benefit of maintaining two different code versions that basically do the same.
The same arguments can be used for Shapes. Basically they are a duplicate of Geometry. They look a little different inside, but do basically the same.
The functions for Geometries are maintained by the NTS people but there are some functions for Shapes that contain errors.
IndexMode/EditMode is basically used to switch between Features with Geometries and Shapes and wouldn't be needed any longer if we remove Shapes.
The fact that one can switch between both more often than not causes side effects as seen in #1417 as well as #801.

closed by accident...


chore(tests): refactor E2E tracer to ease maintenance, writing tests and parallelization

Issue number: #1440
Summary
This PR refactors Tracer E2E test following the new Infrastructure and explicit tests.
Pending

[ ] Test methods (sync, async)
[ ] Break data builders into their own module

Changes

Please provide a summary of what's being changed

User experience

Please share what the user experience looks like before and after this change

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[ ] Meet tenets criteria
[ ] I have performed a self-review of this change
[ ] Changes have been tested
[ ] Changes are documented
[ ] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

Test differences
Besides data builders, I've encapsulated trace fetching and manipulation of different views in its own class. The logic is largely the same, what changed is that we have more flexibility in the type of trace we want (origin, segment name, etc.) and have getters to ease assertion.
Before
def test_basic_lambda_async_trace_visible(execute_lambda: conftest.InfrastructureOutput, config: conftest.LambdaConfig):
    # GIVEN
    lambda_name = execute_lambda.get_lambda_function_name(cf_output_name="basichandlerarn")
    start_date = execute_lambda.get_lambda_execution_time()
    end_date = start_date + datetime.timedelta(minutes=5)
    trace_filter_exporession = f'service("{lambda_name}")'

    # WHEN
    trace = helpers.get_traces(
        start_date=start_date,
        end_date=end_date,
        filter_expression=trace_filter_exporession,
        xray_client=boto3.client("xray"),
    )

    # THEN
    info = helpers.find_trace_additional_info(trace=trace)
    print(info)
    handler_trace_segment = [trace_segment for trace_segment in info if trace_segment.name == "## lambda_handler"][0]
    collect_payment_trace_segment = [
        trace_segment for trace_segment in info if trace_segment.name == "## collect_payment"
    ][0]

    annotation_key = config["environment_variables"]["ANNOTATION_KEY"]
    expected_value = config["environment_variables"]["ANNOTATION_VALUE"]
    expected_async_value = config["environment_variables"]["ANNOTATION_ASYNC_VALUE"]

    assert handler_trace_segment.annotations["Service"] == "e2e-tests-app"
    assert handler_trace_segment.metadata["e2e-tests-app"][annotation_key] == expected_value
    assert collect_payment_trace_segment.metadata["e2e-tests-app"][annotation_key] == expected_async_value

After
def test_lambda_handler_trace_is_visible(basic_handler_fn_arn: str, basic_handler_fn: str):
    # GIVEN
    handler_name = basic_handler.lambda_handler.__name__
    handler_subsegment = f"## {handler_name}"
    handler_metadata_key = f"{handler_name} response"
    trace_query = helpers.build_trace_default_query(function_name=basic_handler_fn)

    # WHEN
    _, execution_time = helpers.trigger_lambda(lambda_arn=basic_handler_fn_arn)
    helpers.trigger_lambda(lambda_arn=basic_handler_fn_arn)

    # THEN
    trace = data_fetcher.get_traces(start_date=execution_time, filter_expression=trace_query)

    assert len(trace.get_annotation(key="ColdStart", value=True)) == 1
    assert len(trace.get_metadata(key=handler_metadata_key, namespace=TracerStack.SERVICE_NAME)) == 2
    assert len(trace.get_subsegment(name=handler_subsegment)) == 2

Huge improvement in readability and code quality @heitorlessa. Too easy to understand now :guitar:

Codecov Report

Merging #1457 (4ec4a0b) into develop (83fb6cc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #1457   +/-   ##
========================================
  Coverage    99.89%   99.89%
========================================
  Files          121      121
  Lines         5479     5479
  Branches       627      627
========================================
  Hits          5473     5473
  Misses           2        2
  Partials         4        4

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

@mploski @rubenfonseca could either of you review before I start Logger and complete the refactoring?
Thanks a lot!

All feedback addressed @mploski - when you're ready

I'm gonna simplify get_metrics return to return the Values so tests are easier to write too ...... but in another PR.

Thanks a lot for the review and suggested changes @mploski @rubenfonseca ! Merging.


dvyukov covfilter minor cleanups

executor: minor coverage filter cleanup
syz-manager: minor coverage filter cleanup

@Bins94 please take a look at these changes

888af9b
I couldn't see there is any negative affect here.
In this case:

["files": "bpf"]

It may filter comparison constants of syscall argument parsing before executing subsystem code. But I believe syzkaller system call descriptions are powerful enough to cover these codes. I always enable all syscalls and specify target only, it works well also. Also, if it's necessary, users can add kernel functions into the coverage filter, it requires users to have enough knowledge to enable function rightly.

It may filter comparison constants of syscall argument parsing before executing subsystem code.

I would assume that if there are any interesting comparisons happening in some code, that code needs to be included into the coverage filter. If there are comparisons, most likely there are also branches on the results of these comparisons, so we very much want to use that coverage as the signal as well.
If we use comparison operands to cover new code paths, we very much want to persist these paths in the corpus. But if this code is not in the coverage filter, we will throw these new interesting inputs away.
Some corner cases are possible, of course, where comparisons are interesting but code coverage is somehow not interesting. But I believe these are very narrow corner cases and it's reasonable to include these small pieces of code into the coverage filter.

Added commit that implements showing filtered coverage percent:
coverage | 55058
filtered coverage | 7945 / 16606 (47%)

https://github.com/google/syzkaller/pull/2318/commits/56bc5b6f9224210505b335a4f8c921778407fc69
Also dropped commit that filters coverage in executor.

It may filter comparison constants of syscall argument parsing before executing subsystem code.

I would assume that if there are any interesting comparisons happening in some code, that code needs to be included into the coverage filter. If there are comparisons, most likely there are also branches on the results of these comparisons, so we very much want to use that coverage as the signal as well.
If we use comparison operands to cover new code paths, we very much want to persist these paths in the corpus. But if this code is not in the coverage filter, we will throw these new interesting inputs away.
Some corner cases are possible, of course, where comparisons are interesting but code coverage is somehow not interesting. But I believe these are very narrow corner cases and it's reasonable to include these small pieces of code into the coverage filter.

Agree, and I had run the code. It looks good to me. It seems to have a slight improvement, and I am still testing.

It seems to have a slight improvement, and I am still testing.

Note: we are collecting a bit more signal now:
https://github.com/google/syzkaller/pull/2318/commits/6188105a760e0cf5ea9985fb8621c8eb06715bea
It may explain some increase in signal.

Note: we are collecting a bit more signal now:
6188105
It may explain some increase in signal.

I know that, I pulled your branch, read every commit change, and run the code.
Everything is good to me. Especially collecting both incoming and outgoing edges, I didn't realize this problem before.

Thanks for testing!
I will merge this now then. And then we can do any additional tweaks/improvements in separate smaller patches if necessary.

Happy to see the coverage filter become easier to use and more efficient! :)


[Op] [TVM] Lightweight TOPI schedule tuner

Description
Based on the recent observation by @zhen-jia, sum sometimes can achieve better performance (up to 10x on p4d) by auto-scheduler. Since the tuning space for sum should be very small, I investigated the well tuned schedule and concluded that the only difference is the choose of thread and block sizes. However, analytically choosing them in TOPI schedules seems challenging, and launching auto-scheduler is too time-consuming for JIT.
Accordingly, this PR proposes a lightweight TOPI schedule tuner. The concept is similar to MetaSchedule presented in TVM, but more straightforward/simpler. We could, of course, get rid of this mechanism after switching to MetaSchedule in the future.
Specifically, this mechanism works as follows:
@profile_schedule(num_thread=[16, 32, 64], max_block=[128, 256, 512])
def schedule_cuda_short_reduce(outs, **kwargs):
    num_thread = kwargs.get(
        "num_thread", _tvm.target.Target.current(allow_none=False).max_num_threads
    )
    max_block = kwargs.get("max_block", 256)
   ...
  return sch

The TOPI schedule accepts **kwargs, which includes tunable parameters.
The TOPI schedule gets the parameter values from kwargs, and assigns default values when missing.
A new introduced decorator profile_schedule for TOPI schedules lets you specify tunable parameters and their possible values.
The tuning is now disabled by default, and could be enabled by an environment variable RAF_JIT_TUNE=1. Please refer to the following evaluation results and share your thoughts about whether we should make it enable by default.

What actually happens underlying is that we wrap the TOPI schedule function, exhaustively generate/evaluate schedules with all parameter combinations, and return the best one. The evaluation simply uses tvm.build and func.time_evaluator to measure the latency. In the above example, it will profile 3x3=9 schedules and select the best one.
With this mechanism, this PR modified the sum schedule and introduces tunable parameters. The tuning space is 4 or 9 depending on the reduction length. Here are the evaluation results based on the sum workloads extracted from custom 1.5B model, BERT, and GPT-2. We evaluated both FP16 and FP32 workloads (note that AMP results are similar to FP16 so we don't put them here) on p3.2xl. There are two insights from the results:

With tuning, we achieve 1x-5.8x speedup. The workloads without speedup are the ones that reduce the outermost dimension. AFAIK, we cannot achieve better speedup with TE schedules for now.
Although the JIT overhead is increased, it could still finish lower-tune-compile within 10 seconds. This should be acceptable, because CuDNN and CUTLASS also take similar time to benchmark algorithms/tile sizes.

 I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

cc @awslabs/raf-reviewer @yzhliu @zhen-jia @hzfan @zhouyuan1119 @whbldhwj @junrushao1994

Could you also provide the chosen optimal parameters for each test case? I'm wondering if a switch condition could cover the most cases so that the tuning can be eliminted?

If 1 fails, and there is no pattern for the optimal parameter with regard to the problem size, I think this tuning should be enabled by default given the speedup here.

Since if the reduction dimension is the not the first dimension of the input tensor, there is almost no speedup for all your testcases. Should we add a heuristic to disable tuning exploration for such a case?

I totally agree with Jie's first comment. It would be useful if we can discover any common patterns from the cases with high speedup.
Regarding whether we should enable this tuning by default: Each model contains multiple sum operators with different input sizes and reduction dimensions. Tuning each operator takes ~4s, so the total tuning time is not negligible here. The sum operator may or may not take a significant portion of execution time in these models. I have some old data from the end of March where all the sum ops take ~12% of GPT2 training time. Because the performance of GPT2 has improved significantly now, it should be helpful to re-evaluate this on popular models before making our decision.

Could you also provide the chosen optimal parameters for each test case? I'm wondering if a switch condition could cover the most cases so that the tuning can be eliminated?

It's not safe to do so. For example, the origin num_thread was 32. I found that changing it to 16 on V100 could make some small workloads much faster, but for others, 64 is a better option. Meanwhile, these values may vary on other GPUs. If we use fixed logic/values for all GPUs without tuning/profiling, we have to choose the most conservative ones to avoid any possible kernel crashing.
On the other hand, if we attempt to have such switch conditions, we have to dive deep into sum schedule and its generated CUDA kernel, and derive an analytical formula to determine the configurations based on input/output shapes and reduction axes. However, 1) it is still possible for aggressive configurations to crash caused by the versions of CUDA, CUDA driver, nvcc, and even the instant GPU utilization. 2) I don't have bandwidth to do it for now.

If 1 fails, i.e., there is no pattern for the optimal parameter with regard to the problem size, I think this tuning should be enabled by default given the speedup here.

Since if the reduction dimension is the not the first dimension of the input tensor, there is almost no speedup for all your testcases. Should we add a heuristic to disable tuning exploration for such a case?

This is a good point and we could definitely do that.

I totally agree with Jie's first comment. It would be useful if we can discover any common patterns from the cases with high speedup.

Responded above.

Regarding whether we should enable this tuning by default: Each model contains multiple sum operators with different input sizes and reduction dimensions. Tuning each operator takes ~4s, so the total tuning time is not negligible here. The sum operator may or may not take a significant portion of execution time in these models. I have some old data from the end of March where all the sum ops take ~12% of GPT2 training time. Because the performance of GPT2 has improved significantly now, it should be helpful to re-evaluate this on popular models before making our decision.

It's worthwhile to re-evaluate, because I added catches for TVM closures and CUTLASS in JIT. Previously, every fused TVM and CUTLASS closure will JIT a kernel even many of them are identical (e.g., the closure for parameter updating). With these catches, the JIT overhead has been significantly reduced, as observed from daily benchmark log.

Update: I mis-read the workload before. The workloads that didn't get any speedup after tuning are the ones that reduce the innermost dimension, but it is larger than the product of all other axes (e.g., <8x512x50257> and reduce 50257 to become <8x512>. In this case reduction length 50257 is larger than output element 4096 ).
Anyways, I added a guard to disable tuning for these workloads.

I agree with @zhouyuan1119, it's good to have evolutions on repressive models before the decision. Before that, I think we can set it disabled by default and let users know that we have the mechanism to tune the sum op and may have better performance.

Ok I'll evaluate BERT/GPT-2 with this PR to help determine whether to enable this feature by default. Meanwhile, please start reviewing the code change.

BTW, I am benchmarking M5 ZeRO-2 with this PR and will let you know when I have the result.

I performed end-to-end evaluations using Razor with this PR.
Configs: Sequence length 512, AMP, Remat, Adam

Model
Batch
Origin Latency (ms)
Origin Warmup (s)
ThisPR Latency (ms)
ThisPR Warmup (s)
Speedup
JIT Overhead (s)

BERT-base
24
305.89
366.64
292.70
383.43
1.05
16.79

BERT-large
8
286.97
810.30
281.68
857.86
1.02
47.56

GPT-2
16
245.22
310.29
239.95
318.22
1.02
7.93

Please refer to speedup and JIT overheads.
Also @zhen-jia helped evaluate custom 1.5B model with multiple GPUs:

#GPU
Batch
Origin
AuthScheduler
ThisPR
Speedup over Origin
Speedup over AutoScheduler

2
12
368.24
347.93
343.78
1.06
1.01

4
24
353.21
333.29
328.24
1.06
1.02

8
64
440.00
419.04
409.19
1.05
1.02

Based on the above results, I argue that this tuning is beneficial, and I feel the JIT overhead is acceptable.
@whbldhwj @zhouyuan1119 @zhen-jia please share your thoughts.

From what I have benchmarked, I endorse @comaniac that it's beneficial and the tuning overhead is acceptable. Especially for large model like M5, which I experienced long compiling time, the tuning time should not be  a concern.

Gentle ping @whbldhwj @zhouyuan1119 @yzhliu

Judging from the results in the tables I agree with @zhen-jia. The warmup time seems negligible in most cases.


ImageView Alignment Not Scaling Properly

Problem description
ImageView offset alignment is increasingly inaccurate as parent composite size decreases.
Snippet
let dot = (layout) => {
	let i = new ImageView(layout);
	i.top = '59%';
	i.bottom = '37%';
	i.background = 'red';
	i.tintColor = 'blue';
	i.image = 'src/images/loading_dot_min2.png';
	return i;
};

let c = new Composite({
	top: MARGIN,
	bottom: MARGIN,
	left: MARGIN,
	right: MARGIN,
	background: '#000000'
})
.append(
	dot({ id: 'dotMiddle', centerX: 0}),
	dot({ id: 'dotLeft', /* left: '35%' OR right: '#dotMiddle 15'*/ }),
	dot({ id: 'dotRight', /* right: '35%' OR left: '#dotMiddle 15' */ })
).appendTo(this);

Expected behavior
My goal is to align three dots (images) onto the screen and have all the properties shrink and grow relative to the size of the parent composite. So if the parent is big, I want the dots to be big, and if the parent is small, I want the dots to be small. I accomplish this by setting the top of the dots as a % offset from top of the parent, and the bottom with a % offset from the bottom of the parent. This part works as expected.
I also want the distance between the dots to remain relative to the parent composite size as well. The way I do this is put a middle dot at centerX: 0 and then align the left dot offset from the center dot's left edge, and align the the right dot offset from the center dot's right edge. As far as I'm aware, this should accomplish what I'm attempting to do, but it's producing unexpected results.
When I set #dotLeft.right: '#dotMiddle 15', and #dotRight.left: '#dotMiddle 15', effectively aligning the left and right dots to the middle dots with an offset of 15% (of the parent), I get these results:
When const MARGIN = 0:

This is what I would expect. However, when const MARGIN = 44%, the following occurs:

Note: I've zoomed in a lot for the second photo so we can see it more clearly.
I can't figure out why the dots are so far apart.

Workaround
I've found that I can accomplish the original goal by aligning the left and right dots to their respective walls instead of the center dot.
When #dotLeftleft: '35%', and #dotRight.right: '35%', we get the original expected behavior:
When const MARGIN = 0:

When `const MARGIN = '44%':

As you can see, the second photo looks the same as the first, except just smaller.
Environment

Tabris: 3.0.0-beta1, iPhone 7, iOS 11.1.1
Serving from<EMAIL_ADDRESS>

However, when const MARGIN = 44%, the following occurs:

I can't tell you why exactly that is happening but could it be that the three dots do not fit into the available space of 12% anymore? That might cause the items to go all over the place (not expected though).

There is a misunderstanding in how the layout works. You say:

When I set #dotLeft.right: '#dotMiddle 15', and #dotRight.left: '#dotMiddle 15', effectively aligning the left and right dots to the middle dots with an offset of 15% (of the parent)…

This is where I see the issue. We do not support the percentage offset from the other widget. Please look at https://docs.tabris.com/latest/layout.html#top-right-bottom-left. There is a list of relation types that can be used. In short:

offset (in points)
widget id
percentage (to the parents' edge)
percentage and offset (to the parents' edge)
widget offset (in points)

#dotMiddle 15 means 15pt from #dotMiddle and not 15% from #dotMiddle.
If you make a screenshot of your layout with container margin set to 44% please try to measure the distance between the tiny dots. It is 15pt, so on your iPhone 7, it should be 30 pixels.

Oh, I see now. My bad! I misread the docs. I suppose this would be an interesting feature that I think would be useful, though. What I'm going to have to do for my use case is edit the actual images to add more white space around the dots and then attach the outside dots to the center dots with no offset.

Closing this issue as resolved. Feel free to reopen if you have any more problems.


Put all reexports of given entry in Suggestion Database.

Currently, we know only a single, least-nested place where a given entry is reexported. But to properly interpret what is currently imported, avoid names conflicts, and put proper qualified names.
So the reexport field should be instead an array of all places where a given entity is reexported.

It would be good if the first reexport was "the main one" (the least nested)


Adds instancing to ModelExperimental.js

This PR adds support for instancing in ModelExperimental by adding an InstancingPipelineStage and an associated shader. This functionality requires browser support for ANGLE_instanced_arrays, which is supported pretty much everywhere.
This PR also modifies the way GltfLoader loads instancing attributes. Instancing attributes are always loaded as typed arrays, except for the case where the accessor for the TRANSLATION attribute provides a min and max and ROTATION is not present.

Thanks for the pull request @sanjeetsuhag!

:heavy_check_mark: Signed CLA found.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Here is a local Sandcastle for testing.

@ptrgags Your feedback has been addressed.

Babylon.js 5.0.0-alpha.36 works very well, but with model-experimental-instancing.
track_gpu_instance.zip

@XYCaptain The issue stems from the min and max values of the accessors in the glTF you provided. When those are provided for the TRANSLATION and ROTATION is not present, the code attempts to use those values to construct bounding volumes for the geometry. For a lot of the EXT_mesh_gpu_instancing accessors, the min and max are set to the same value. Once that is fixed, the track model seems to work:

@XYCaptain The issue stems from the min and max values of the accessors in the glTF you provided. When those are provided for the TRANSLATION and ROTATION is not present, the code attempts to use those values to construct bounding volumes for the geometry. For a lot of the EXT_mesh_gpu_instancing accessors in your sample, the min and max are set to the same value. Once that is fixed, the track model seems to work:

I put the shared mesh in each node. With instancing transfroms, the track model looks like this (use Babylon.js):

@XYCaptain Thanks a lot for sharing your sample data - it correctly pointed out a bug in our instancing code. The model-experimental-staging branch correctly renders the train track model:
Side View

Back View

Front View

It seems to do more test when instancing b3dm embedded in 3dtiles.

More tests seem to be needed when instancing b3dm embedded in 3dtiles.

@XYCaptain Just to clarify, are you trying to load B3DM with EXT_mesh_gpu_instancing in Model.js (not ModelExperimental.js)?

More tests seem to be needed when instancing b3dm embedded in 3dtiles.

@XYCaptain Just to clarify, are you trying to load B3DM with EXT_mesh_gpu_instancing in Model.js (not ModelExperimental.js)?
I remember I ran the codes below, but not 100% sure now. The test case is accessible after 9 hrs, plus 12 hrs time difference, my feedback is  quite slow, so if convenient please run the test case with the track model. Thanks for help.

 local Sandcastle for testing 3D Tiles

@XYCaptain Since https://github.com/CesiumGS/cesium/pull/9726 was merged, the results below are shown from the main branch.

Model.js - Sandcastle
ModelExperimental.js - Sandcastle

This is the expected result since Model.js currently does not support EXT_mesh_gpu_instancing. If we disable support for EXT_mesh_gpu_instancing in BabylonJS, we see the same result.

@sanjeetsuhag Thinks a lot. I've got right way.😃


New mobile nav

Summary
Partially fixes #2656 (nav only)

Currently the header and nav are fixed to the top of the viewport. Since its getting bigger, maybe we should un-fix it, and leave on the top of the document, like as on React page?

It is sooo pretty and so much nicer. You are awesome.

Current coverage is 68.08% (diff: 100%)

Merging #2664 into new-docs will not change coverage

@@           new-docs      #2664   diff @@
==========================================
  Files           139        139
  Lines          5044       5044
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           3434       3434
  Misses         1610       1610
  Partials          0          0

Powered by Codecov. Last update f1163f1...a31df6f

Is there any more CSS we can kill/cleanup in jest.css? It's such a mess.

For sure there is. It would also be great to split css into components and shared parts. Right now it's really difficult to edit that file in 2 separate PRs

A day later, looking at this, I still think this is amazing. The new website is gonna be so good.


Formatting AvatarGroup in ConversationHeader

I'm using AvatarGroup in ConverstationHeader, but it's not formatting correctly - avatars are stacking vertically instead of horizontally:

I'm seeing the same with ConverstationList also.
Any idea on how to make it appear as it does in the storybook? Thanks!

@Anjum48 Please paste the header code

Here's the header code:
<ConversationHeader>
  <ConversationHeader.Back />
  <AvatarGroup size="md" max={2}>
    {currentConv.names.map((c, i) => (
      <Avatar
        src={currentConv.avatar[i]}
        name={currentConv.names[i]}
        key={"Avatar" + i}
      />
    ))}
  </AvatarGroup>
  {/* <Avatar
    src={currentConv.avatar[0]}
    name={currentConv.names[0]}
  /> */}
  <ConversationHeader.Content userName={currentConv.title} />
  <ConversationHeader.Actions>
    <AccountMenu />
  </ConversationHeader.Actions>
</ConversationHeader>

The styles are applied from import styles from<EMAIL_ADDRESS>

I think I fixed this with CSS. Turns out that .cs-conversation-header__avatar and .cs-conversation-list__avatar need their own specific CSS for the desired behaviour


Allow subprojects in current project to be addressed by GA coordinates

If I have a project like
├── part-a
├── part-b
└ settings.gradle.kts

Where part-b depends on part-a and both set their group to org.myorg, this should be possible:
dependencies {
  implementation("org.myorg:part-a"))
}

instead of
dependencies {
  implementation(project(":part-a"))
}

Why do we want this?

This feature is needed in composite builds to enable included builds to depend on something from the including build. This can happen because there are situations where such "build cycles" are desired (see #6229 which has to be fixed as well).
To have unified way to refer to "components" independent of whether they are published, defined by another build of a composite, or in a separate subproject of the current build.
Makes it easier to refactor a build (e.g. split up a large build into multiple)
Allows us to discourage the use of the project("...") API completely, as we already discourage it now for cross-project configuration or for accessing the internal state of another project.

This should probably be implemented the same way it is done for the other builds of a composite right now: register a global dependency substitution rule for each subproject. This needs to be done after the project has been configured so that the group of each project is known, but (obviously) before dependencies are resolved.

Fixed for the case where the build is a composite (#4638)

Spike to continue this work:  #14633

Maybe project accessors make this better?


Cannot format golang file in sublime text

Traceback (most recent call last):
File "/Users/gur/Library/Application Support/Sublime Text/Installed Packages/Gofmt.sublime-package/gofmt.py", line 257, in run_formatter
formatter = Formatter(view)
File "/Users/gur/Library/Application Support/Sublime Text/Installed Packages/Gofmt.sublime-package/gofmt.py", line 166, in __init__
self.cmds = [Command(cmd, self.view, self.window) for cmd in cmds]
File "/Users/gur/Library/Application Support/Sublime Text/Installed Packages/Gofmt.sublime-package/gofmt.py", line 166, in <listcomp>
self.cmds = [Command(cmd, self.view, self.window) for cmd in cmds]
File "/Users/gur/Library/Application Support/Sublime Text/Installed Packages/Gofmt.sublime-package/gofmt.py", line 77, in __init__
self.window)
File "/Users/gur/Library/Application Support/Sublime Text/Lib/python33/golangconfig.py", line 227, in subprocess_info
raise exception
golangconfig.EnvVarError: The following environment variable is currently unset: GOPATH

I have added in my ~/.zshrc
export GOPATH=/usr/local/go
export PATH=$PATH:$GOPATH/bin

And added in Golang.sublime-settings
{
    "root": "/usr/local/go/bin"
}

I am also facing same issue


Expose refresh token in MSAL

Core Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
MSAL React (@azure/msal-react)
Public or Confidential Client?
Public
Description
After trying to figure out how to get access to the refresh token in msal-react I came across a few issues and documentation that the refresh token isn't exposed. One consideration for exposing the refresh token is using it to provide a biometric login option within our Cordova Hybrid app. Today we store the refresh token on the device (encrypting it with a biometric challenge) as part of our biometric login flow. Sure would love to have access to the refresh token, unless there's another way to solve this problem that I'm not aware of.
Source
External (Customer)

@mpbiehn We intentionally do not expose the refresh token on our API surface, and are not likely to change that stance as we are actively working on features which would further protect the refresh token by not returning it to MSAL.js at all. Can you please go into more detail about why biometric login in Cordova requires an RT?

@tnorling sure, today we aren't using MSAL (msal-react) but would like to soon as part of our Singe Page Application. At a high level, here's what our biometric login flow looks like:

We leverage two Cordova plugins as part of our hybrid Single Page Application, Fingerprint All-In-One and Secure Storage

Refresh access token documentation that we referenced during initial development on how to refresh the access token

After first successful login, we present the user an option to login biometrically (face, fingerprint, etc.) based on their device capabilities. If they select the biometric option we use Fingerprint to handle the biometric authentication then use Secure Storage to save the refresh token. We also are sure to update refresh token using Secure Storage after each successful login.

At next login, if the user selects "biometric" login versus default login (username,password), we use Fingerprint to handle the biometric authentication, upon success we get the previously saved refresh token using SecureStorage and call the /token endpoint passing the refresh_token vs code to refresh/renew the access token.

Here's another article that might explain it better - https://developer.okta.com/docs/guides/unlock-mobile-app-with-biometrics/android/main/.
I'm open to other options on how to handle biometric login, just haven't found a better option yet.
If MSAL doesn't return the refresh token at all in the future, how will MSAL handle refreshing the access token? Doesn't the current version of MSAL use the refresh token (in the background) to do this?

There's potentially a bigger issue here than just returning refresh tokens. We do not currently support custom storage solutions (i.e. SecureStorage), which means, if I'm understanding your scenario correctly, you would be storing tokens in SecureStorage in addition to the storage used by MSAL.js (local or session storage). If that's the case, I'm not sure I see the value in using SecureStorage at all until we do support custom storage (we do have an item in the backlog to look into this).
Furthermore, it sounds like the biometric sign-in doesn't actually require that it return a refresh token but rather just unlocks access to SecureStorage. Do I understand that correctly? If so, once MSAL.js supports custom storage the pattern I would suggest is to unlock SecureStorage and then use the MSAL APIs to acquire an access token - letting MSAL.js reach into SecureStorage and retrieve what it needs. I don't see a reason why your application would need to be aware of the implementation details of acquiring access tokens (getting a refresh token and calling the /token endpoint with it), that is after all what an authentication library like MSAL.js is designed to abstract away from you.

@tnorling thanks for the quick response.  :)
You are correct in that biometric sign-in unlocks access to SecureStorage. Today, we aren't using MSAL so we are storing the refresh token in SecureStorage. Was thinking of following a similar pattern (not knowing any better) with MSAL but doesn't sounds like that is possible (no refresh token available) in the current version.
To be sure I understand your suggested pattern, are you saying once MSAL.js supports custom storage, we would leverage the custom storage vs local or session storage? And we'd leverage MSAL APIs (getting what it needs from the custom storage) to acquire an access token? Any ETA on the backlog item for custom storage or somehow I could follow the progress on this backlog item?
Also, any thoughts on how to handle biometric login with MSAL until custom storage is available? This might hold us up from using MSAL. :(

You can track progress on custom storage in issue #1588, I unfortunately don't know right now when it will be prioritized.

To be sure I understand your suggested pattern, are you saying once MSAL.js supports custom storage, we would leverage the custom storage vs local or session storage? And we'd leverage MSAL APIs (getting what it needs from the custom storage) to acquire an access token?

That's correct. We haven't really sat down to design the feature yet but I imagine we would expose some sort of cache interface for you to provide implementations of cache getters and setters, which MSAL.js would then use instead of localStorage and sessionStorage for all cache operations.

Also, any thoughts on how to handle biometric login with MSAL until custom storage is available? This might hold us up from using MSAL. :(

I wish I could give you a better answer but unfortunately we don't have any explicit support for Cordova or any other hybrid frameworks at the moment. So while you could try to come up with some sort of workaround in the meantime, it would likely require doing some things we wouldn't endorse and we would not be able to offer much help if you run into issues :/

@tnorling thank you for your quick responses, much appreciated!

@mpbiehn My pleasure! I'm going to go ahead and close this issue but you can track #1588 for news on custom storage.


Error:"invalid_grant", Description:"Invalid email or User ID", Uri:""

Hello,
I have an error to access the data : Error:"invalid_grant", Description:"Invalid email or User ID", Uri:""
Steps to reproduce the behavior:

Get-GSUser -Filter *

Do you have any idea, how to solve this?
Kr,
Pierre

@pdewas - There are two components that could be impacting:

New Google Dev Console project/service account (takes some time for permissions to propagate)
PSGSuite was not explicitly imported (sometimes auto-loading the module results in unexpected behavior due to SDK types not loading correctly)

This is also an error you can get if your PSGSuite Config file is is incorrect
If you run Show-PSGsuiteConfig Is that value for "AppEmail" filled out?


Passthrough CSI 3 J in Conpty

Summary of the Pull Request
Conpty doesn't need CSI 3 J, it doesn't have a scrollback. The terminal that's connected should use that. This makes conpty pass it through, like other sequences that conpty has no need for.
References
PR Checklist

[x] Closes #2715
[x] I work here
[x] Tests added/passed
[n/a] Requires documentation to be updated

I don't want sound like I'm objecting to this PR, because it does at least improve the situation, but "passthrough" as a solution is almost never going to solve the problem completely. In this particular case you're fixing the CSI 3 J escape sequence, but any app that clears the scrollback through the console APIs is still not going to work.
In particular, issue #3126 (which was a closed as a dup of #2715) is not fixed by this PR. So if you close #2715 then you'll need to reopen #3126.

I don't want sound like I'm objecting to this PR, because it does at least improve the situation, but "passthrough" as a solution is almost never going to solve the problem completely. In this particular case you're fixing the CSI 3 J escape sequence, but any app that clears the scrollback through the console APIs is still not going to work.
In particular, issue #3126 (which was a closed as a dup of #2715) is not fixed by this PR. So if you close #2715 then you'll need to reopen #3126.

I reactivated 3126, @j4james. Thanks for the consideration.


not able to open the new job dialog

with latest master code, i am not able to launch the new job dialog from the dashboard agent tab. no error or warning in the console. i am using Mac.
IIRC, @aaomidi,  you are making changes in this area. could u please take a look?

repro'ed also on Windows.

Don't think I've made any changes here recently just looked at it. Will assign the area owner.


Document Camera coordinate space

Objective
Missing docs
Solution
Add docs paraphrased from the Cart's mouth: https://discord.com/channels/691052431525675048/691052431974465548/1172305792154738759

It follows the natural "results" of right handed y-up. The default camera will face "forward" in -Z, with +X being "right". The RH y-up setup is reasonably common. Thats why I asked for existing examples.I think we should appeal to the masses here / see how other RH Y-up 3D packages / engines handle this

Another PR added a similar comment, might be good to update that comment to match the one from this PR


_typeof is not a function on commonjs import

I'm trying to import clipboard from npm. This results in _typeof is not a function which seems to be a function defined by babel to support es2015 symbols.
The imported module is plain JavaScript so babel transpilation seems unnecessary to me (but we might not know this while importing). I think it might be some rollup issue where _typeof is wrongly hoisted?
My ember-cli-build.js configuration:
'use strict';

const GlimmerApp = require('@glimmer/application-pipeline').GlimmerApp;
const resolve = require('rollup-plugin-node-resolve');
const commonjs = require('rollup-plugin-commonjs');

module.exports = function(defaults) {
  let app = new GlimmerApp(defaults, {
    rollup: {
      plugins: [
        resolve({ jsnext: true, module: true, main: true }),
        commonjs()
      ]
    }
  });

  return app.toTree();
};

My component definition:
import Component from '@glimmer/component';
import Clipboard from 'clipboard/dist/clipboard';

export default class TmpyClipboard extends Component {
  args: { content: string };

  didInsertElement() {
    let clipboard = new Clipboard(this.element, {
      text: () => this.args.content
    });
  }
};

@topaxi This is caused by double transpiling code. As recommended by documentation of https://github.com/rollup/rollup-plugin-babel you should exclude node_modules e.g:
'use strict';

const GlimmerApp = require('@glimmer/application-pipeline').GlimmerApp;
const babel = require('rollup-plugin-babel');
const resolve = require('rollup-plugin-node-resolve');
const commonjs = require('rollup-plugin-commonjs');

module.exports = function(defaults) {
  let app = new GlimmerApp(defaults, {
    rollup: {
      plugins: [
        babel({
          exclude: 'node_modules/**'
        }),
        resolve({
          jsnext: true,
          module: true,
          main: true
        }),
        commonjs()
      ]
    }
  });

  // Use `app.import` to add additional libraries to the generated
  // output files.
  //
  // If you need to use different assets in different
  // environments, specify an object as the first parameter. That
  // object's keys should be the environment name and the values
  // should be the asset to use in that environment.
  //
  // If the library that you are including contains AMD or ES6
  // modules that you would like to import into your application
  // please specify an object with the list of modules as keys
  // along with the exports of each module as its value.

  return app.toTree();
};

Nice this works!
We should probably make this easier to use or put some documentation on this on glimmerjs.com
Let me know how I can help out with this.


[test] skip running test for doc change

Is your feature request related to a problem?/Why is this needed

Currently all changes including doc change would trigger full test running, while it's not necessary, need to skip test when there is only doc change, e.g. *.md
Describe the solution you'd like in detail

Describe alternatives you've considered

Additional context

@andyzhangx Can I do it?

sure

@andyzhangx I might not be able to finish it now. I have read the documentation for Travis CI and I found that this feature is not supported. Please see travis-ci/issues/6301 for details. I have already subscribed to it. I will solve this problem after it is solved.

that's ok, thanks for the investigation.

@andyzhangx Thanks. And I find oni/.travis.yml. This seems like a good temporary solution.


Fix feature warning by adding import clause in UCSingleCatalog.scala

PR Checklist

[x] A description of the changes is added to the description of this PR.
[x] If there is a related issue, make sure it is linked to this PR.
[x] If you've fixed a bug or added code that should be tested, add tests!
[x] If you've added or modified a feature, documentation in docs is updated

Description of changes
Fixes #425

@rameshchandra to merge


Read-Only File System Errors w/ SD Card Install

Output of sudo sh edit-chroot -all:
name: trusty
encrypted: no
mount: cannot remount /dev/sdb1 read-write, is write-protected

The Issue:
I've been using crouton to primarily be able to run Android Studio on my Chromebook for quite some time now. The special case that I have with my crouton install is that I've performed the installation onto an SD card instead of directly onto my SSD storage. The main reasoning for this is so that I don't waste any of the precious SSD that I have available (16GB) and make use of the 64GB I have on the SD.
However, every now and then, I run into read-only file system errors. What I mean by this is that I can't perform any tasks after some time because of some strange read-only errors. When I initially boot up my crouton target (which is XFCE), everything works great: Android Studio runs, as well as Google Chrome, etc. However, after closing and reopening my CBook a few times, the read-only errors arise.  The number of times the close/reopens need to happen in order to reproduce the issue varies: sometimes it only occurs after closing/reopining once, sometimes it occurs after several closes/reopens. And when I say close/reopen, I mean "putting the CBook to sleep" and "reawakening it". What I believe the issue is that upon reawakening the CBook, the SD card isn't mounted properly in the way it was originally. A very vague explanation but it's the best I can come up with on my own.
For example, I was going to take a screenshot of one of the errors that normally occur when I try to relaunch Android Studio. However, when I attempted to save the screenshot onto my desktop, I received the following error message:
Failed to open '/home/mike/Desktop/Screenshot - 051716 - 20:51:55.png' for writing: Read-only file system
Furthermore, the error message that I received when I try to launch Android Studio is the following:
Log path '/root/.AndroidStudio2.1/system/log' is inaccessible.
If you have modified the 'idea.log.path' property please make sure it is correct,
otherwise please re-install the IDE.

After doing some research, it turns out that I need to edit the idea.log.path property in the mentioned file. However, when I attempted to do this using vim, it would not allow me to save my edits since the file was marked as read-only.
I tried chown, chmod, which I don't completely understand how to use, but it did not make a difference for the issue.
I've given two examples on what occurs with this issue in order to emphasize that this is not a software-specific issue (not just Android Studio is experiencing this problem). Obviously, if I can't even take a simple screenshot using the default program that's built into XFCE (straight from the applications menu) and save the image onto my desktop, then the problem is more widespread.
I'm not expecting a complete resolution to this. However, what I would like to know is what is the cause of this issue, why is it happening? I've already prepared myself that this will eventually lead me down the road to reinstall crouton onto my SSD and use the SD as expanded storage. However, some explanation for potential causes of the problem would be appreciated.
Temporary Solution to the Issue
In order for me to get back into my crouton target, I need to restart my CBook and relaunch it. This is because once I log out of XFCE and trusty and try to launch the target once again, the following happens:
chronos@localhost /media/removable/SDCard/crouton/bin $ sudo sh /media/removable/SDCard/crouton/bin/enter-chroot  Entering /media/removable/SDCard/crouton/chroots/trusty... /media/removable/SDCard/crouton/bin/enter-chroot: 509: cannot create /run/crouton/media/removable/SDCard/crouton/chroots/trusty/etc/crouton/name: Read-only file system Unmounting /media/removable/SDCard/crouton/chroots/trusty...
I then umount my SD card and run sudo mount -a to be certain that every device is properly mounted and retry the above command. However, I always receive the same output. So, in order to avoid manually removing the SD card (and cringing over the thought of ruining the card), I simply reboot and start up XFCE once again.

I solved this issue by installing Keep Awake extension. When running my chroot I just click the icon to be sunset which keeps the system awake when the lid is closed. Battery life seems to be the same.

Hey, appreciate the input! Just curious, even if I enable the PC to be awake through the extension, does the screen at least turn off when I close the lid? As in, when I close the lid, I shouldn't see the light emitting from the screen in a dark room.

Yep it puts the screen nicely into sleep and other stuff too. I haven't noticed a bit on the battery life.


[User Interface: STRAPI-based Page]: Featured Page Template and type listing

Issue Name
Featured Page Template and type listing
Issue Description
The NIAID team has expressed a desire for clarification on what this would actually look like and how a user might navigate to on on the site. To clarify what it would look like, we should create the STRAPI template for a featured page, create an example featured page, and generate a spreadsheet of the types of content that would be showcased on a featured page (e.g. repositories are one thing, anything else? user stories?)
To Do:

[x] Create a STRAPI template for Featured page
[x] Create a spreadsheet with types of content that would be displayed on Featured page
[x] Create an example Featured Page to illustrate one of the types of content mentioned in the spreadsheet

Issue Discussion
This was discussed at the bi-weekly meetings dated 2024.03.05 and 2023.03.19
Mockup URL
No response
Related WBS task
https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/5
https://github.com/NIAID-Data-Ecosystem/nde-roadmap/issues/45
For internal use only. Assignee, please select the status of this issue

[ ] Not yet started
[x] In progress
[ ] Blocked
[ ] Will not address

Status Description
No response
STRAPI page status check list

[ ] This page/documentation/change has yet to be discussed between NIAID, Scripps, Leidos
[X] This page/documentation/change has been discussed/reported between NIAID, Scripps, Leidos
[x] This page/documentation/change has been mocked up
[x] This page/documentation/change has been implemented on Staging
[ ] This page/documentation/change has been approved for Production
[ ] This page/documentation/change has been implemented on Production

The featured page content types is now available here: https://docs.google.com/spreadsheets/d/1hh3IVSI8TlFYWtPCbeE7XxzLdoGuuKKc3_dT_XJsm34/edit?usp=sharing

@rshabman @lisa-mml @hartwickma @sudvenk
The featured page (WBS task 1.1.4) provides an opportunity to highlight use cases, NIAID-funded repositories, and the like for user engagement.
What sort of content is featured
As we did with the news page, we have created a spreadsheet on the types of content we would expect to highlight on a featured page. This spreadsheet is now available here: https://docs.google.com/spreadsheets/d/1hh3IVSI8TlFYWtPCbeE7XxzLdoGuuKKc3_dT_XJsm34/edit?usp=sharing
What does a featured page look like
An example of what a featured page could look like can be found here: https://data-staging.niaid.nih.gov/featured/draft
How to reach a featured page
We expect that users would see a new featured page from the landing page news carousel. For old featured pages, users would be viewable on a featured pages archive similar to the news page archive
Content maintenance of the featured page
As with the news page, the featured page will have spreadsheet where new featured page content will be drafted and shared for approval.
The Ask
We are seeking approval to move the infrastructure of the featured page to production.

Thank you for providing this information and an example of content for the Featured Pages.
In response to 'the ask' "We are seeking approval to move the infrastructure of the featured page to production", can you clarify:

What is the anticipated frequency of new content,
How will content be selected,
Who will be involved with the review process,
How will the subject of the Feature be contacted and engaged in the content development process?

We have reached out to the Repo owners for their feedback on the draft featured page for ACDN. In the interim, NIAID would also like to see an example of the content for a Featured Page of ImmPort.
NIAID ask for next steps:

Address items 1-4
Provide an editable version of the ACDN Feature
Provide a draft of an ImmPort Feature

Please let us know if we can provide additional information or details.

@EmilyHaag Can you generate an SOP to address 1-4 above?
@hartwickma as with the News page, the featured page will have a tracking/approval spreadsheet. You can find the editable version of the ACDN example feature there: https://docs.google.com/spreadsheets/d/1hh3IVSI8TlFYWtPCbeE7XxzLdoGuuKKc3_dT_XJsm34/edit?usp=sharing
@EmilyHaag Can you add an ImmPort feature to the content proposal spreadsheet?

The SOP for the feature page has been developed and is now available at https://docs.google.com/document/d/1H48It-24oTbKTRsfHLZArX53eBBnUOAT/edit?usp=sharing&ouid=114065631315523104759&rtpof=true&sd=true . The SOP addresses the questions raised in a comment made on May 31st, 2024

In response to 'the ask' "We are seeking approval to move the infrastructure of the featured page to production", can you clarify:
What is the anticipated frequency of new content,
How will content be selected,
Who will be involved with the review process,
How will the subject of the Feature be contacted and engaged in the content development process?

The example Feature page for ImmPort has also been drafted and is visible in staging: https://data-staging.niaid.nih.gov/features/immportdraft. This also appears in the staging home page carousel.
This draft has a placeholder for where we would want to include some behind-the-scenes info from ImmPort.

Per discussions at the biweekly meeting dated 2024.06.25 an overview of the metadata augmentation would make for an interesting feature or news page blurb

@hartwickma, @rshabman, @lisa-mml, @sudvenk
As discussed in biweekly meetings, the feature pages may be used to share about more user-centric content such as how to leverage functions of the site, or how the site can help the user.
Towards that end, @EmilyHaag has drafted an example feature, illustrating how the site can be used for meeting data sharing mandates: https://docs.google.com/document/d/1ii5MV8Dd4I3tr75WYsGfxZTRO9AvUFk8iKAuFJJmdq0/edit?tab=t.0#heading=h.22khugp8tjxy
The Ask: Please let us know if you have any suggestions for improving the draft, or if it is approved to move to STAGING

Hi @gtsueng and @EmilyHaag, thank you for providing an example of content for the features page the highlights features of the Portal. NIAID will review internally. It would be helpful to understand what other types of subjects are under consideration. If possible, please provide a few items that would eb developed for this feature page.

@hartwickma @gtsueng @sudvenk we've created a list of potential Feature pages in this spreadsheet: https://docs.google.com/spreadsheets/d/1hh3IVSI8TlFYWtPCbeE7XxzLdoGuuKKc3_dT_XJsm34/edit?usp=sharing
Please let me know if you have feedback on this list or the draft above.


Fix NPE when getting the running process

Task/Issue URL: https://app.asana.com/0/1199371158290272/1201395476838293/f
Description
This PR fixes an NPE we're seeing in some devices when getting the running procss on Application#onCreate.
The getSystemService call can return a nullable value
Steps to test this PR
Nothing to test

Current dependencies on/for this PR:

develop

PR #1563  (this PR)

This comment was auto-generated by Graphite and will continue to be automatically updated while this PR remains open.


Fetch data source owner

Description

Fixes https://github.com/dust-tt/tasks/issues/1368.
This PR corrects the request data source flow within the new "data sources" tab for non-admin users viewing company data. I plan to do more extensive refactoring to consistently enforce the presence of editedBy in dataSource using proper types.
Risk

Deploy Plan

PMRR.


remove 404 from not found strings

at first this package is very good,
please remove 404 from the string if the key is not found
Why
in some cases i forgot to set the key in my json file so i need to use the default one
The good advantage for removing it is to allow us use a default strings may be just make one json file for Arabic and leave the English use  the default strings
note that the keys may be readable strings
like this
 "Withdraw profits": "سحب الأرباح"
now  if   the language is arabic the right side will be used
else the left will be used

Thanks for reaching out to me
Your suggestion considered and implemented in v2.0.10
Do not hesitate contacting me with any further enhancement suggestions.


Make a shorter file extension

BRUHIFF doesn't currently comply with the MS-DOS file naming system, as its file extension is four letters, but MS-DOS supports only three.

I have used a MS-DOSimeter to see who cares and I couldn't even detect the atmospheric radiation caring.


Add US, songs, led matrix, and some other things

Scotty,
I have added a lot of code. I am still working on it, But wanted to give you a heads up and get you to start a review. I have tested it on my ESP32 OTTO dev board that I have had setup for a while. It has a US sensor. Buzzer and LED matrix connected. It is not connected to a body so I have not tested the servos.
I still have some gestures to add. I have not started on the noise and battery, but my system has those as well. I will work on these in the next day or so.
As an aside, I have also been working on a version of edublocks-micropython (It is working but I need to add alot, But it does run on my system. I have not been able to get it to work with a version of micropython that has the PSRAM enabled, But I will work on that after everything else.
Let me know what you think.
Michael

Scotty,
I got all the gestures working.

Still need to do the ADC for noise and battery.
Michael

excellent 😃

@mishafarms I didn't look before asking but how are you handling battery level? if the esp adc is read internally it will show 3.3v and would be reading after the regulator and not show a true battery level (as it would show 3.3v no matter what) what are your plans for how to power the otto pcb board? did you have a battery connector (in addition to the DC input jack) on the pcb? and if so ... maybe a voltage divider added to the next pcb version to feed the adc with the battery connector voltage from before the regulator ...

I do have a voltage divider so that at we can read it scaled to 3.3 volts. We may have to play with the resistor values. I do have an external 5V power port as well as usb power and battery.
Sent from my iPhone

On Sep 22, 2020, at 3:11 PM, Scotty Franzyshen<EMAIL_ADDRESS>wrote:
@mishafarms I didn't look before asking but how are you handling battery level? if the esp adc is read internally it will show 3.3v and would be reading after the regulator and not show a true battery level (as it would show 3.3v no matter what) what are your plans for how to power the otto pcb board? did you have a battery connector (in addition to the DC input jack) on the pcb? and if so ... maybe a voltage divider added to the next pcb version to feed the adc with the battery connector voltage from before the regulator ...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Update for a docker driver

This commit enables a fully functioning volume driver that is
able to run from VMs in VirtualBox and perform introspection
necessary to issue commands to underlying VB SOAP API
to perform storage orchestration for volume attachemnt.

This looks great! I'm glad you were able to build on my work for this. :+1:
I haven't had a chance to review this in detail yet, but the first thing that jumps out are the changes to vboxwebsrv/vboxwebsrv.go. Since that file was generated by gowsdl, it may be better to make the changes there and regenerate vboxwebsrv.go.
I'll find some time to review this more fully in the coming week.

Btw.. just noticed this is a v4 thing only.  The API changed, which I have adjusted for.  But I am running into an issue locking the instances while running.

I think in general a vboxwebsrv client will probably have to deal with
multiple versions of the API. I haven't thought much about how to do that
yet, but it would be cool if there were a stable API call to query the
version. I haven't yet checked to see if that exists, though querying the
WSDL could be an option.

I think one of the problems may turn into bloat though.  If each SOAP API has its own WSDL with minor changes, then that turns into a ton of extra code as versions change.  It might be worth the effort to identify the differences and manually add new methods etc all consolidated under the same vboxwebsrv.go file.

I suppose that depends on whether Virtualbox is using semantic versioning or not. I would hope it would be possible to have only V4, V5, etc.

It looks like IVirtualBoxgetVersion is the operation to call, but you need to call logon first to get the object to call it on. As long as the logon operation stays consistent, this should be doable, but it seems like it could be brittle. I also took a quick look at the WSDL and it doesn't provide any indication of which version of the API it supports...

I've opened https://github.com/hooklift/gowsdl/pull/50 to propose your err handling changes for the generator tool used to generate vboxwebsrv.go.
As for the log.Println changes, I'd rather not bring those in. What would you thing about having the code that uses go-virtualboxclient call log.SetOutput to control where the logging goes instead?

@clintonskitson FYI, https://github.com/hooklift/gowsdl/pull/50 has been merged.

Verry cool.  I have the 5.0.10 WSDL all dialed in and working for the use case.  I can re-run it and make the minor tweak re commenting out the XML def as referenced above.  Wondering if you would rather have that as the PR for now and then deal with backward/forward versioning in the future?  Maybe just leave them as separate branches for now?

I'm happy to have this PR just targeting the V4 binding. Opening a branch for V5 compatibility also seems like a reasonable approach until I have the time to work out a better approach. I've created a v5-api branch if you want to send a PR that way.
Regarding the XMLName removal, I'm hesitant to accept a patch that removes it. If you could provide some more information on how it was failing, perhaps including the returned SOAPBody, that would likely help.

Actually, perhaps it would be better to have master be V5 and have a v4-api branch...
What do you think?

Yeah, I think keeping master at the latest would

OK. I've killed v5-api and created v4-api.

BTW, were there any adjustments needed to the code under virtualboxclient based on the V4 v. V5 api changes?

Not for the direct bindings.  But there was a helper function for creating
storage that did need to be updated.
On Thursday, December 17, 2015, Mike Dillon<EMAIL_ADDRESS>wrote:

BTW, were there any adjustments needed to the code under virtualboxclient
based on the V4 v. V5 api changes?
—
Reply to this email directly or view it on GitHub
https://github.com/appropriate/go-virtualboxclient/pull/1#issuecomment-165533896
.

Opened https://github.com/appropriate/go-virtualboxclient/pull/2 and https://github.com/appropriate/go-virtualboxclient/pull/3


Add new slopes to circual saw and remove saw-less recipes for slopes

This contribution

adds support of lately added slopes to circular saw
adds circular recipe for 3-microblock stairs (to allow crafting them back into microblocks)
adds comments for harder-to-read crafting recipes
fixes incorrect amouts of slopes taken from circular saw
removes saw-less recipes for slopes (since they're not mathematically correct)

Closing since from start it was an accident with taking too much commits in pull request.

It's not a problem if there are separate commits. It's even good to see what got merged step by step.

Each step will be done in separate pull-request.