Add support for /account/coins

Is your feature request related to a problem? Please describe.
Rosetta spec added a new api /accounts/coins, rosetta-bitcoin should support it.
Describe the solution you'd like
Add a new endpoint /account/coins based on Rosetta spec
https://www.rosetta-api.org/docs/AccountApi.html#accountcoins
Additional context
Let me know if someone is already working on it. I'd be happy to create a PR if I can get some help.

👋  @HelloKashif! I've been working on the rosetta-sdk-go PRs to support this new endpoint (https://github.com/coinbase/rosetta-sdk-go/pull/231 + https://github.com/coinbase/rosetta-sdk-go/pull/232) and was planning to update rosetta-bitcoin. If you'd like to take a stab (once I put out the next SDK release), I'd be happy to support you!
The changes should be pretty easy (at least the "no mempool support" version) because I've already implemented the functionality as part of the /account/balance response (returning coins here was deprecated as of v1.4.7): https://github.com/coinbase/rosetta-bitcoin/blob/7e7f67e2e600e5a29dcc6f013a63a9dda30ace1f/services/account_service.go#L56-L78

@patrick-ogrady awesome. Once the sdk is released I'll create a PR here based on above code.
Thanks

Give it a go @HelloKashif! There may be some small breaking changes unrelated to this fix that were made in rosetta-sdk-go. Let me know if you have any questions!

@patrick-ogrady sure I'll get on it.
Few questions:

For filtering by currencies, how do we compare two currencies? Do we just compare currency.Symbol or should we check currency.Decimals and Metadata etc. Also would be nice if this was a utility on the types.Currency itself.
maybe like currency.IsEqual(otherCurr)

Do you have hints on how to go about the include_mempool one?

For filtering by currencies, how do we compare two currencies? Do we just compare currency.Symbol or should we also check currency.Decimals and Metadata etc. Also would be nice if this was a utility on the types.Currency itself.
maybe like currency.IsEqual(otherCurr)

Great question! We use types.Hash(curr) to determine equality (a currency is uniquely defined by its symbol, decimals, and metadata). Fortunately, we created a function to help with this (although we should probably move this to the types package): https://github.com/coinbase/rosetta-sdk-go/blob/1e6eb643cdd559971e60578a76050a069591f329/asserter/account.go#L39-L53

Do you have hints on how to go about the include_mempool one?
This will include some temporary db state (to cache the mempool contents) and could be quite complex to do well. I'm totally fine if we punt on this until a future PR. Make sure to return NetworkOptionsResponse.Allow.MempoolCoins = false until then: https://github.com/coinbase/rosetta-sdk-go/blob/e6be00ef9da16599780777ca9e3140035f5c6b4b/types/allow.go#L54


Expose the AUX ?

Just wondering if you can expose the AUX setting for the Ecobee? I would like to be able to have a trigger to AUX function when I have a power outage and not use my heat pump. HomeKit does not show it.
Guess you would need to expose the HEAT, COOL, and AUTO as well even though HomeKit does.

Hello,
I'm not exactly sure what you mean by AUX setting for the ecobee. But I probably won't be able to get to it anytime soon. This is a hobby projects that I work on in my personal time.
So if you really need the feature, try to work on it yourself, I'll be happy to merge a PR.

In the Ecobee you can switch your system to heat, cool, auto and AUX.  Aux
is the backup heat source ( electric or gas) if you have a heat pump.
Switches on if it goes below 36 or so degrees Fahrenheit.
Ecobee does not present this function in the HomeKit, and does not plan
too.
I would like to switch to gas heat when there is a power outage and not use
the heat pump. My house has a battery back up but running the gas heat is
less drain on batteries.
Thanks for taking the time to respond.
Steve
Pardon the brevity, sent from a mobile device.
On Fri, Jan 5, 2024 at 12:01 PM Vojta Molda @.***>
wrote:

Hello,
I'm not exactly sure what you mean by AUX setting for the ecobee. But I
probably won't be able to get to it anytime soon. This is a hobby projects
that I work on in my personal time.
So if you really need the feature, try to work on it yourself, I'll be
happy to merge a PR.
—
Reply to this email directly, view it on GitHub
https://github.com/vojtamolda/homebridge-ecobee3-sensors/issues/50#issuecomment-1879193671,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APRMG4WSFLTM4PILBDSYQX3YNBLYTAVCNFSM6AAAAABBK3DUVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZZGE4TGNRXGE
.
You are receiving this because you were assigned.Message ID:
@.***>

Okay. That's really nice. Like I said have fun working on it yourself. I personally don't need, so it's very unlikely I'll spend time on it.


Get an Article Written About the FPA by a Reputable News Organization

Idea
The FPA is growing at a tremendous rate but we need to get more press coverage. One way to do this is to request coverage from news organizations who occasionally write stories about new open-source, non-profits.
If you want to help, let me know who you will contact, (you don't have to contact everyone, other people can help) and I will assign you to the issue.
Possible Contacts

[ ] TechCrunch
[ ] CNET
[ ] Gizmodo
[ ] Wired
[ ] The Verge
[ ] Axios

If you have any that you want to add, comment them below!
Background
The Fairfield Programming Association was founded in 2020 by William McGonagle and Neil Chaudhari. William McGonagle is now the President of the FPA, and his LinkedIn profile is here. And Neil Chaudhari is the Vice President of the FPA, and his LinkedIn profile is here. The Fairfield Programming Association is currently hiring many new senior engineers to lead teams of junior engineers in building tons of new projects including an open-source educational website for programming, a social network for young programmers, and development tools like linters, testers, server hosting software.
Some numbers- in the last weeks: we made it onto the GitHub Explore page, our blog has over 500 daily readers, we have contributors from five different countries, and we are in talks to organize a programming competition between a number of high schools and colleges in the northeastern United States.


Truncate select-entities option

Hi.
It would be nice to be able to truncate entities in the select-entities list. Maybe with some kind of property for setting truncation on/off and limit on component-level.

Hi @jegsen - thanks for your suggestion. Is this what you had in mind?

Absolutely brilliant :1st_place_medal: The main focus was to limit entry-descriptions to one line in the cloud app.

Great- we've released version 1.4.1 which includes this and updated the doc. Hope this helps.

Great work :-)
Can you perhaps supply me with (a link to a) how to bring the new release in action for an existing project?
Thanks.

Hi @jegsen - you can update the version in the package.json file, and then run npm install:
"eca-components": "^1.4.1",


Update windows-10-1903-removed-features.md

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3777
Added NOTE.

@nenonix @JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@greg-lindsay The PR that addresses issue #3777 is available for review. Thanks.

@greg-lindsay Following up for updates.

@greg-lindsay Following up for updates.
cc @dansimp

Sorry but we can't accept changes to this page. All edits even small ones need to be processed through legal due to the sensitive nature of deprecation.


V2 update

lbry.go depends on itself, if imports to itself aren't upgraded to v2 it will use a weird mix of dependencies.
This PR ports every usage to V2.
Additionally, several modules were updated, I updated them all (skipped btcd because it's still broken)
I tested this with ytsync and it still works fine. jsonrpc tests also pass (though the wallet related ones added by Andrey didn't pass, probably due to differences in chains?).

Thanks for doing the work I should've done! I fixed TestClient_WalletList which was failing for me, others seem to run fine. All in all looks good to me.


Upgrade to Laravel 10.x

Codecov Report
Base: 72.36% // Head: 73.52% // Increases project coverage by +1.16% :tada:

Coverage data is based on head (4983bb5) compared to base (db6261a).
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff              @@
##               main       #6      +/-   ##
============================================
+ Coverage     72.36%   73.52%   +1.16%
  Complexity       21       21
============================================
  Files             3        3
  Lines            76       68       -8
============================================
- Hits             55       50       -5
+ Misses           21       18       -3

Impacted Files
Coverage Δ

src/Console/InstallCommand.php
0.00% <ø> (ø)

src/LockScreen.php
95.23% <ø> (ø)

src/LockScreenServiceProvider.php
100.00% <ø> (ø)

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

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


Request for better installation instructions for TF on Ampere GPUs!

After 6 weeks of trial and error, I gave up and replaced our brand new 3090 cards with the old 2080 Ti. I just could not get tensorflow on the new GPUs to work.
My colleagues and I have worked with TF from its early days. We have always been early adopters of the latest GPU generation. There was never a mess like this. In the worst case, the new TF system didn't utilize all the GPU's new resources, but we never had installation troubles like this.
I tried all installation approaches mentioned in the TF home page (python packages, docker containers, compilation from source). Either it failed completely or - after hours/days on Stack Overflow - ended in disappointing results.
The closest I got to a success came with the upgrade to TF 2.4, but I was getting a million times the warning message
"your cuda software stack is old. we fallback to the nvidia driver for some compilation. update your cuda version to get the best performance. the ptxas error was: ptxas fatal : value 'sm_86' is not defined for option 'gpu-name'"
at each start of a TF script.
This is not inspiring confidence in the coupling of TF and CUDA. This is plainly unusable.
As I understand it, the CUDA toolkit is too old compared to the driver, so the driver is recompiled to match the CUDA version. But why does this happen again and again? Once should be enough. We have Ubuntu 20.04 with driver 460 installed. It should be possible to go back to version 450, but we could not achieve that. I don't know if this would help, anyway.
With Docker containers, there seem to be the same problems because they use the driver of the host system.
Another word about working with containers because they are recommended in the installation instructions: We work with an IDE which offers Docker support only for extra cost. No IDE, no debugger (and other important tools). And like this, Docker is not an option.

@wittmarf
Please refer to this comment and let us know.

I was aware of this possibility, but I don't think hiding error or warning messages is a solution.
With "not inspiring confidence in the coupling of TF and CUDA", this is exactly what I meant. It would be a solution if the Nvidia PTX compiler was invoked just once and saved its result.

OS Windows 10 Pro : 1909 18363.1379
CUDA TOOLKIT : 11.1
CUDNN: 8.1.0
GPU : MSI RTX 3090 x trio
CPU i7 3930k 32GB ram
using Anaconda
python 3.7.9
tf-nightly-gpu 2.5.0.dev20210114
tf-nightly  2.5.0.dev20210114
=> The above config allows me to run my code LSTM code in tensor flow (extract below):
However clone the environment in Anaconda and upgrade the tf-nightly build to anything more recent, including todays build
of 2.5.0.dev20210228 ... when the code reaches tf.model.fit .. it crashes out with no error reporting at all.
The reason why i tried upgrading the tf-nightly build : currently the model training time is about the same as on my RTX 2080ti and sometimes even slower which thought was down to issues with the tf-nightly builds and Ampere.
Would very appreciate  any suggestions on why the newer tf-nightly builds are making my code crash
code block:
model = tf.keras.models.Sequential([
#input shape equals term points in curve
tf.keras.layers.Bidirectional(tf.keras.layers.LSTM(32,return_sequences=True),input_shape=(n_days,n_cols)),
tf.keras.layers.Dropout(0.2),
tf.keras.layers.Bidirectional(tf.keras.layers.LSTM(32)),
tf.keras.layers.Dropout(0.2),

tf.keras.layers.Dense(64, activation='relu',kernel_initializer=initializer),
tf.keras.layers.BatchNormalization(),
tf.keras.layers.Dropout(0.2),

tf.keras.layers.Dense(64, activation='relu',kernel_initializer=initializer, bias_initializer=output_bias),
tf.keras.layers.BatchNormalization(),
tf.keras.layers.Dropout(0.2),

tf.keras.layers.Dense(t_cols, activation='sigmoid', bias_initializer=output_bias)])

#list of keras metrics to compute in model
METRICS = [
keras.metrics.BinaryAccuracy(name='binary_accuracy'),
keras.metrics.Precision(name='precision'),
keras.metrics.Recall(name='recall'),
keras.metrics.AUC(name='auc'),
]
model.compile(optimizer=Adam(learning_rate=lng_rate),
loss='binary_crossentropy',
metrics=METRICS)
history=model.fit(
X_train,
Y_train,
epochs=training_epochs,
batch_size=training_batch_size,
verbose=1,
class_weight=label_weights[0],
validation_data=(X_validation,Y_validation))

@ALIANS-PRODUCTIONS Looks like you may have different issue when compared to the current issue. Can you please open a new issue with the standalone code. Creating new issue may help others who are facing similar issue like you. Thanks!

Hi there, I created a separate ticket with sample code attached in the second comment and extensive detail:
Thank you very much for looking at my case!
tf-nightly-gpu builds from February are crashing on 'tf.keras model.fit()' for Nvidia RTX 3090; January builds performance is slower than 2080ti on : 2Layer Bidirectional LSTM + 3 Dense Layers #47473
From: Vishnuvardhan Janapati<EMAIL_ADDRESS>Sent: 01 March 2021 22:35
To: tensorflow/tensorflow<EMAIL_ADDRESS>Cc: ALIANS-PRODUCTIONS<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [tensorflow/tensorflow] Request for better installation instructions for TF on Ampere GPUs! (#47066)
@ALIANS-PRODUCTIONShttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FALIANS-PRODUCTIONS&data=04|01||ae1b3260d0624a81b32008d8dd02500e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637502349289372535|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Fik26nHxqe210Q47sP0kYYlRHY6x2yXyB%2BvvUgm%2BnrE%3D&reserved=0 Looks like you may have different issue when compared to the current issue. Can you please open a new issue with the standalone code. Creating new issue may help others who are facing similar issue like you. Thanks!

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftensorflow%2Ftensorflow%2Fissues%2F47066%23issuecomment-788353650&data=04|01||ae1b3260d0624a81b32008d8dd02500e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637502349289382526|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=TF25fPfivkpO5XilgpfF4QBWwoJQzizUK7nNFT5lBY4%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFCITOOMUBLWY6WV7QE2V63TBQJC7ANCNFSM4XM7QYCQ&data=04|01||ae1b3260d0624a81b32008d8dd02500e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637502349289382526|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=9E2xTH4OhZIshckoBM1sPFIdrSpJUKGjhU7g6TofhdA%3D&reserved=0.


unexpected directory layout while running make

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
After gave the make k8s-keystone-auth command, during the dep ensure phase i receive the following error:
CGO_ENABLED=0 GOOS=linux go build
-ldflags "-w -s -X 'main.version=b4f24944-dirty'"
-o k8s-keystone-auth
cmd/k8s-keystone-auth/main.go
unexpected directory layout:
import path: github.com/golang/glog
root: /home/dilallo/go/src
dir: /home/dilallo/go/src/k8s.io/cloud-provider-openstack/vendor/github.com/golang/glog
expand root: /home/dilallo/go/src
expand dir: /home/dilallo/go/src/k8s.io/cloud-provider-openstack/vendor/github.com/golang/glog
separator: /
Makefile:88: recipe for target 'k8s-keystone-auth' failed
make: *** [k8s-keystone-auth] Error 1
My GO version go1.10.3 linux/amd64

@RdL87 i am not seeing an issue currently, here's my output:
root@cloud-provider-openstack:/usr/local/lib/go/src/k8s.io/cloud-provider-openstack# make -j6 k8s-keystone-auth
pip install Mercurial
Collecting Mercurial
  Downloading https://files.pythonhosted.org/packages/12/e7/46894628ed3d6b0ae1e324523b09fdb8a90f0720bebe43cab88e0ea91b39/mercurial-4.6.1.tar.gz (6.4MB)
    100% |████████████████████████████████| 6.4MB 4.3MB/s
Building wheels for collected packages: Mercurial
  Running setup.py bdist_wheel for Mercurial ... done
  Stored in directory: /root/.cache/pip/wheels/03/67/cd/64e70d0fb8e4ac88f2f6ffdaeba34b67eb8b899eb11f37c53a
Successfully built Mercurial
Installing collected packages: Mercurial
Successfully installed Mercurial-4.6.1
curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  4594  100  4594    0     0  15816      0 --:--:-- --:--:-- --:--:-- 15786
ARCH = amd64
OS = linux
Will install into /usr/local/lib/go/bin
Fetching https://github.com/golang/dep/releases/latest..
Release Tag = v0.4.1
Fetching https://github.com/golang/dep/releases/tag/v0.4.1..
Fetching https://github.com/golang/dep/releases/download/v0.4.1/dep-linux-amd64..
Setting executable permissions.
Moving executable to /usr/local/lib/go/bin/dep
dep ensure
CGO_ENABLED=0 GOOS=linux go build \
	-ldflags "-w -s -X 'main.version=6ecf8d7c'" \
	-o k8s-keystone-auth \
	cmd/k8s-keystone-auth/main.go
root@cloud-provider-openstack:/usr/local/lib/go/src/k8s.io/cloud-provider-openstack# uname -a
Linux cloud-provider-openstack 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
root@cloud-provider-openstack:/usr/local/lib/go/src/k8s.io/cloud-provider-openstack# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.4 LTS"
root@cloud-provider-openstack:/usr/local/lib/go/src/k8s.io/cloud-provider-openstack#

@mrhillsman i repeated the same procedure many times yesterday and always got that error. Today, i did the same and everything works. I don't know if it is the case to investigate what happened. Doing some research i found sometimes this kind of error is related to go version or to git packet you're installing. But i checked both and nothing changed fro m yesterday to now.

@RdL87 i am not sure unfortunately, afaik we did not make any code changes and we are not seeing any build failures for the jobs related to k8s-keystone-auth binary which can be seen here
the failures there are a result of some refactoring and not related to the error you experienced.

@mrhillsman Maybe it has been an error on my side. I will investigate it so it could help someone who fell in the same situation.


Data-arrow value seems to be ignored

I'm trying to make simple tour where I must reposition the arrow or else the leg will overflow to the right, out of the body, but no matter what parameter combination I use it is always centered:

Am I doing something wrong?

data-arrow only affects... The arrow! :)
If you want to move the actual leg element you're looking for data-left/data-top
https://ryanfunduk.com/jquery-tourbus/#leg-options

Yes, I know that :) The leg element position is working fine, I need to change the arrow to be at 10% or 40px but it seems to ignore the setting: the arrow is always at the center.

Hmm, well, the arrow repositioning is working for me. Here's a screenshot from a tour I recently implemented which has the arrow set to 25%:

That's with data-orientation='left' obviously. Here's another one with data-orientation='top' and data-arrow='90%':

Here is a simplified version of the problem: jsfiddle
Am I missing something?

The code in the fiddle appears to be working fine for me...

Looks better at 7% IMO 😉

Ok, got it: I just checked: in Firefox it works correctly. I'm on Chrome 57.0.2987.133 (64-bit), Win10.

Hmm... my screenshot is also from Chrome 57, but OSX. I'll dust off my windows box and give it a try.

Yea workin fine here. Same version (57.0.2987.133):

Ok, I owe you a beer... There was a buggy userstyle installed in Stylish which affected every site. Now it is fine here too. blush

Haha oh man, I probably spend half my working life down rabbit holes like that.
Let's me honest - half my off-time, too 😛


CKernelNormalizer cannot be set via put

should we add CKernelNormalizer to the base interface?

yes

is this issue still opened?? i want to work on this .as this will be my first contribution can you guide me a little how to start.


python3Packages.pywlroots: 0.14.11 -> 0.14.12

Motivation for this change
Package bump.
Things done
qtile (this package's only reverse dependency) still runs as expected.

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 154603 run on x86_64-linux 1

3 packages built:

python310Packages.pywlroots
python39Packages.pywlroots
qtile


Need a animated Blog page

Is your feature request related to a problem? Please describe.
[ I need a blog page where students can upload their blog in that section ]
Describe the solution you'd like
You can create a simple blog page and add this link on blog nav bar option, but blog page should be mobile responsive.

Hi, I would like to do this task, It may take some time

Please clarify whether users can use this website to create or is it a non functional page for future use. in the first case you need a database to store the blog input.

Do one thing design a simple blog page and add yourself 2-3 blogs manually and after completing send me ss and i will let you know the changes

ok I'm working on it can you assign it to me

Great

#68 pull request created for the issue


fix: Add method setSessionFromRefreshToken

What kind of change does this PR introduce?
The setSession method doesn't work with a refresh token, so I made a function using much of a same code that sets the session using a refresh token.
What is the current behavior?
Currently, there is no way to set the session using a refresh token, as was possible in previous versions and documented here: https://supabase.com/docs/reference/javascript/next/auth-setsession
What is the new behavior?
The session can be set using a refresh token.

I created this as its own method so I could use it with supabase-js. However, it would make more sense to fix the setSession() method so it can set a session using the refresh token. If you want that done, I can do it.
This is the broken method:
/**
   * Sets the session data from the current session. If the current session is expired, setSession will take care of refreshing it to obtain a new session.
   * If the refresh token in the current session is invalid and the current session has expired, an error will be thrown.
   * If the current session does not contain at expires_at field, setSession will use the exp claim defined in the access token.
   * @param currentSession The current session that minimally contains an access token, refresh token and a user.
   */
  async setSession(
    currentSession: Pick<Session, 'access_token' | 'refresh_token'>
  ): Promise<AuthResponse> {
    try {
      const timeNow = Date.now() / 1000
      let expiresAt = timeNow
      let hasExpired = true
      let session: Session | null = null
      if (currentSession.access_token && currentSession.access_token.split('.')[1]) {
        const payload = JSON.parse(decodeBase64URL(currentSession.access_token.split('.')[1]))
        if (payload.exp) {
          expiresAt = payload.exp
          hasExpired = expiresAt <= timeNow
        }
      }

      if (hasExpired) {
        if (!currentSession.refresh_token) {
          throw new AuthSessionMissingError()
        }
        const { data, error } = await this._refreshAccessToken(currentSession.refresh_token)
        if (error) {
          return { data: { session: null, user: null }, error: error }
        }

        if (!data.session) {
          return { data: { session: null, user: null }, error: null }
        }
        session = data.session
      } else {
        const { data, error } = await this.getUser(currentSession.access_token)
        if (error) {
          throw error
        }
        session = {
          access_token: currentSession.access_token,
          refresh_token: currentSession.refresh_token,
          user: data.user,
          token_type: 'bearer',
          expires_in: expiresAt - timeNow,
          expires_at: expiresAt,
        }
      }

      await this._saveSession(session)
      this._notifyAllSubscribers('TOKEN_REFRESHED', session)

      return { data: { session, user: session.user }, error: null }
    } catch (error) {
      if (isAuthError(error)) {
        return { data: { session: null, user: null }, error }
      }

      throw error
    }
  }

It seems it was made only to take a Session object, and contains a lot of unused code, as 'access_token' and 'refresh_token' can't be used.

Hey @Aerilym unfortunately you can't use setSession with a refresh token only. This was fixed in #445.
An outline of the reasons:

A refresh token alone does not represent a user's session, but the combination of access and refresh token do.
If you use only the refresh token, your users will experience random logouts because a refresh token is designed to be used only once.
You will be filling up the database with refresh tokens each time you want to validate it, which can become expensive both from a data storage perspective and from a performance standpoint.

Can I inquire about your use case for using only the refresh token?

Hey @Aerilym unfortunately you can't use setSession with a refresh token only. This was fixed in #445.
An outline of the reasons:

A refresh token alone does not represent a user's session, but the combination of access and refresh token do.
If you use only the refresh token, your users will experience random logouts because a refresh token is designed to be used only once.
You will be filling up the database with refresh tokens each time you want to validate it, which can become expensive both from a data storage perspective and from a performance standpoint.

Can I inquire about your use case for using only the refresh token?

The issue came up when I was trying to sign in with an oauth endpoint using react native and expo. I followed this guide, and it worked on previous versions of supabase-js. Also according to your v2 documentation about setSession(), this is still a valid way of using setSession().
Is there another way I should be going about logging in on expo?
Here is specifically how I'm using the new function in the same way as the example and old setSession() usage:
async function handleLogin(provider: Provider) {
    if (Platform.OS === 'web') {
      await supabase.auth.signInWithOAuth({
        provider,
      });
      return;
    }

    const returnUrl = makeRedirectUri({ useProxy: false });
    const authUrl = `${supabaseUrl}/auth/v1/authorize?provider=${provider}&redirect_to=${returnUrl}`;
    const response = await startAsync({ authUrl, returnUrl });

    if (response.type !== 'success') {
      return;
    }

    const refreshToken = response.params?.refresh_token;
    if (!refreshToken) return;
    await supabase.auth.setSessionFromToken(refreshToken);
  }

Yeah, that input change and doc change fixes it too. My solution for making it work with expo is:
    const returnUrl = makeRedirectUri({ useProxy: false });
    const authUrl = `${SB_URL}/auth/v1/authorize?provider=${provider}&redirect_to=${returnUrl}`;
    const response = await startAsync({ authUrl, returnUrl });

    if (response.type !== 'success') {
      return;
    }

    const refreshToken = response.params?.refresh_token;
    const accessToken = response.params?.access_token;
    if (!refreshToken) return;
    supabase.auth.setSession({
      refresh_token: refreshToken,
      access_token: accessToken,
    });

I'll look into expanding on the doc changes introduced in #511 as the example usage is outdated.


buildGo{Module,Package}: Support PIE mode on Linux

Description of changes
In order to support PIE builds on Linux CGO_ENABLED must be set and -linkmode=external added to ldflags, otherwise generated binaries are broken and depend on interpreter paths such as /lib64/ld-linux-x86-64.so.2.
This is a part of a larger effort (treewide PIE) documented at https://github.com/NixOS/nixpkgs/pull/252310
Reproducer:
$ CGO_ENABLED=0 go build -buildmode=pie test.go

$ file test
test: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, Go BuildID=my3pP23M4JFJ_7Ae-mCr/HxVEDoplFn0--pK_qJP6/jXZx9JN4CCLlMgD9XW61/SA-rP2uTLzlPPj243UmO, with debug_info, not stripped

$ CGO_ENABLED=1 go build -buildmode=pie -ldflags=-linkmode=external test.go

$ file test
test: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /nix/store/3dyw8dzj9ab4m8hv5dpyx7zii8d0w6fi-glibc-2.39-52/lib/ld-linux-x86-64.so.2, for GNU/Linux 3.10.0, Go BuildID=QQ3cSgZ3iTfBlspGeTL8/tObSc2zUB7g-T2pTJDil/jXZx9JN4CCLlMgD9XW61/n44KpOU6t6YmePjqwRk5, with debug_info, not stripped

Things done
Enabled those two options for PIE/Linux/Glibc builds.

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

https://github.com/NixOS/nixpkgs/blob/24959f933187217890b206788a85bfa73ba75949/pkgs/build-support/go/module.nix#L201-L204

https://github.com/NixOS/nixpkgs/blob/24959f933187217890b206788a85bfa73ba75949/pkgs/build-support/go/module.nix#L201-L204

Yes, I'm aware. But this is not enough. For example:
$ nix build --impure --expr  '(import <nixpkgs> {}).fzf.overrideAttrs (oldAttrs: { hardeningEnable = ["pie"]; })'
error: builder for '/nix/store/db99q432j9z6dabwd5391d5rj30iyzj9-fzf-0.55.0.drv' failed with exit code 1;
       last 10 log lines:
       > Building subPackage .
       > Building subPackage ./src
       > Building subPackage ./src/algo
       > Building subPackage ./src/protector
       > Building subPackage ./src/tui
       > Building subPackage ./src/util
       > Running phase: checkPhase
       > fork/exec /build/go-build3493889823/b001/src.test: no such file or directory
       > FAIL	github.com/junegunn/fzf/src	0.001s
       > FAIL
       For full logs, run 'nix log /nix/store/db99q432j9z6dabwd5391d5rj30iyzj9-fzf-0.55.0.drv'.

@chivay are you targeting 24.11 with this PR? If yes, please notice the approaching deadline for breaking changes to staging in less than a month.


bootc enablement for ppc64le

I am trying to figure out how bootc (bootable container) works and started experimenting with it on Power(ppc64le arch).
I came across https://developers.redhat.com/articles/2024/05/07/image-mode-rhel-bootable-containers# and attempted to create a bootable container image on Power using the recipe mentioned in bootc image builder project .
I used following command (Fedora40 running on PowerVM Logical Partition [LPAR])
podman run --pull=newer --rm --privileged --pid=host  quay.io/sacsant/fedora-bootc:40 bootc install to-disk --target-no-signature-verification --wipe --block-setup direct --filesystem xfs /dev/sdc
WARN[0000] Failed to decode the keys ["storage.options.thinpool"] from "/usr/share/containers/storage.conf"
time="2024-05-25T06:03:33-04:00" level=warning msg="Failed to decode the keys ["storage.options.thinpool"] from "/usr/share/containers/storage.conf""
time="2024-05-25T06:03:34-04:00" level=warning msg="Failed to decode the keys ["storage.options.thinpool"] from "/usr/share/containers/storage.conf""
Installing image: docker://quay.io/sacsant/fedora-bootc:40
Digest: sha256:6c88359c24a8c351bf2f742c0f5cfd9a5b32b1e6e475499fc9612c017e2cf860
Wiping /dev/sdc1
Wiping device /dev/sdc1
Wiping /dev/sdc2
Wiping device /dev/sdc2
Wiping /dev/sdc3
Wiping device /dev/sdc3
/dev/sdc3: 4 bytes were erased at offset 0x00000000 (xfs): 58 46 53 42
Wiping /dev/sdc
Wiping device /dev/sdc
/dev/sdc: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sdc: calling ioctl to re-read partition table: Success
ERROR Installing to disk: Creating rootfs: Unsupported architecture: powerpc64
Can someone help me debug this problem? Is code missing for ppc64le arch?

It's x86_64 and aarch64 only L251
anyhow::bail!("Unsupported architecture: {}", std::env::consts::ARCH);
It'd be great to get ppc64le support.

Following the s390x enablement tracker, I was able to make some progress on this.

Updated the image.go to include ppc64le arch
Updated partition_tables.go with ppc64le specific data
To get around the (panic: required mounts for bootupd stage [/boot/efi] missing) issue for now commented the /boot/efi line from images repo
AnacondaContainerInstaller specific customisation code in image.go also possibly needs some update to avoid following errors. For now I commented these statements to move forward

cmd/bootc-image-builder/image.go:237:7: img.Users undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Users)
cmd/bootc-image-builder/image.go:238:7: img.Groups undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Groups)
cmd/bootc-image-builder/image.go:240:50: img.KickstartKernelOptionsAppend undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method KickstartKernelOptionsAppend)
cmd/bootc-image-builder/image.go:242:7: img.KickstartNetworkOnBoot undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method KickstartNetworkOnBoot)
cmd/bootc-image-builder/image.go:246:14: img.Users undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Users)
cmd/bootc-image-builder/image.go:246:36: img.Groups undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Groups)

I have run into following boot loader related error:
Installing image: docker://quay.io/sacsant/fedora-bootc:latest
Initializing ostree layout
Initializing sysroot
ostree/deploy/default initialized as OSTree stateroot
Deploying container image
Deployment complete
Running bootupctl to install bootloader
Installing for powerpc-ieee1275 platform.
/usr/sbin/grub2-install: error: the chosen partition is not a PReP partition.
error: boot data installation failed: installing component BIOS: Failed to run "/usr/sbin/grub2-install" "--target" "powerpc-ieee1275" "--boot-directory" "/run/osbuild/mounts/boot" "--no-nvram" "/dev/loop0"
ERROR Installing to filesystem: Installing bootloader: Task Running bootupctl to install bootloader failed: ExitStatus(unix_wait_status(256))
Traceback (most recent call last):
File "/run/osbuild/bin/org.osbuild.bootc.install-to-filesystem", line 53, in
r = main(args["options"], args["inputs"], args["paths"])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/run/osbuild/bin/org.osbuild.bootc.install-to-filesystem", line 48, in main
subprocess.run(pargs, env=env, check=True)
File "/usr/lib64/python3.12/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['bootc', 'install', 'to-filesystem', '--source-imgref', 'containers-storage:[overlay@/run/osbuild/containers/storage+/run/containers/storage]b3a026083aa7f61628b5fdc3ab90b5b692139668ec583485d0f2e48fe34e46d9', '--skip-fetch-check', '--generic-image', '--karg', 'rw', '--karg', 'console=tty0', '--karg', 'console=ttyS0', '--target-imgref', 'quay.io/sacsant/fedora-bootc:latest', '/run/osbuild/mounts']' returned non-zero exit status 1.
Any suggestions on how to solve this error? I am unable to connect the dots and having trouble identifying code that needs a change to fix this.

To be specific I am currently focussed on creating a qcow2 based bootable image.
podman run --rm -it --privileged --pull=newer --security-opt label=type:unconfined_t -v $(pwd)/config.toml:/config.toml -v $(pwd)/output:/output -v /var/lib/containers/storage:/var/lib/containers/storage quay.io/sacsant/bootc-image-builder:latest --type qcow2 --rootfs xfs --local quay.io/sacsant/fedora-bootc:latest

/usr/sbin/grub2-install: error: the chosen partition is not a PReP partition.
error: boot data installation failed: installing component BIOS: Failed to run "/usr/sbin/grub2-install" "--target" "powerpc-ieee1275" "--boot-directory" "/run/osbuild/mounts/boot" "--no-nvram" "/dev/loop0"
ERROR Installing to filesystem: Installing bootloader: Task Running bootupctl to install bootloader failed: ExitStatus(unix_wait_status(256))

That's in https://github.com/coreos/bootupd/

Thanks Colin for the pointer.  Since I am completely new to this project/code, I am still unable to connect the dots.
Should I use the coreos/bootupd code as reference and make similar changes to other repositories (bootc-image-builder or images or perhaps bootc??) or should I change coreos/bootupd? Can you guide me on this?
I noticed that coreos/bootupd uses powerpc64 as a value to identify IBM Power architecture while other projects like bootc-image-builder and likes use ppc64le as a value. Is there a theory behind this difference ?

I noticed that coreos/bootupd uses powerpc64 as a value to identify IBM Power architecture while other projects like bootc-image-builder and likes use ppc64le as a value. Is there a theory behind this difference ?

This is based on how your programming language detects the platform
e.g:
golang
# go env GOARCH
ppc64le      <=============================

rust:
# rustc --target=powerpc64le-unknown-linux-gnu --print=cfg
debug_assertions
panic="unwind"
target_abi=""
target_arch="powerpc64"             <=============================
target_endian="little"
target_env="gnu"
target_family="unix"
target_has_atomic="16"
target_has_atomic="32"
target_has_atomic="64"
target_has_atomic="8"
target_has_atomic="ptr"
target_os="linux"
target_pointer_width="64"
target_vendor="unknown"
unix

What's extra fun here is that it's actually only for ppc64le on Fedora derivatives that the "Rust vs RPM" architecture naming is different.  Rust=powerpc64 RPM=ppc64le whereas they match for s390x, x86_64 and aarch64.  Note that the Go and RPM names are otherwise different for amd64 vs x86_64 etc.

Going back to the original error of "Unsupported architecture: powerpc64" , I added following code in bootc
} else if cfg!(target_arch = "powerpc64") {         // BIOS-BOOT         sgdisk_partition(             &mut sgdisk.cmd,             1,             "0:+4M",             "BIOS-BOOT",             Some("9E1A2D38-C612-4316-AA26-8B49521E5A8B"),         );
Is the above code correct?
With this code using install to-disk command the operation proceeds further but fails eventually with
DEBUG exec: "sgdisk" "-Z" "/dev/sdb" "-U" "R" "-n" "1:0:+4M" "-c" "1:BIOS-BOOT" "-t" "1:9E1A2D38-C612-4316-AA26-8B49521E5A8B" "-n" "3:0:0" "-c" "3:root" "-t" "3:0FC63DAF-8483-4772-8E79-3D69D8477DE4"
[14381.355893]  sdb: sdb1 sdb3
DEBUG Created partition table
[14381.356751]  sdb: sdb1 sdb3
DEBUG argv0=Some("exe")
ERROR Installing to disk: Creating rootfs: Missing partition for index 3
Following partition layout was written to the disk
Device     Start      End  Sectors  Size Type
/dev/sdb1    256     1279     1024    4M PowerPC PReP boot
/dev/sdb3   1280 26214394 26213115  100G Linux filesystem
What partition is missing and is referenced by index 3?  I guess there should be /dev/sdb2 pointing to /boot . Can someone help decode this error?

What partition is missing and is referenced by index 3? I guess there should be /dev/sdb2 pointing to /boot . Can someone help decode this error?

I was able to modify the code to move past this issue.
Using block setup: direct
Initializing partitions
Creating boot filesystem (xfs) on device /dev/sdb2 (size=510M)

mkfs.xfs -m uuid=e14c7dd8-4297-4cb4-b41b-eb027167d941 -L boot /dev/sdb2
Creating root filesystem (xfs) on device /dev/sdb3 (size=99.5G)
mkfs.xfs -m uuid=ad5cdc91-0ca9-4cf5-afda-5aeaf53b1370 -L root /dev/sdb3
Mounting /run/bootc/mounts/rootfs
Mounting /run/bootc/mounts/rootfs/boot
Initializing ostree layout
Initializing sysroot
ostree/deploy/default initialized as OSTree stateroot
Deploying container image...Freed objects: 118 bytes
done
Running bootupctl to install bootloader

Now both the methods qcow2 and install to-disk fail during boot loader install
Running bootupctl to install bootloader

bootupctl backend install --write-uuid --update-firmware --auto --device /dev/sdb /run/bootc/mounts/rootfs
Installing for powerpc-ieee1275 platform.
/usr/sbin/grub2-install: error: the chosen partition is not a PReP partition.
error: boot data installation failed: installing component BIOS: Failed to run "/usr/sbin/grub2-install" "--target" "powerpc-ieee1275" "--boot-directory" "/run/bootc/mounts/rootfs/boot" "--no-nvram" "/dev/sdb"
ERROR Installing to disk: Installing bootloader: Task Running bootupctl to install bootloader failed: ExitStatus(unix_wait_status(256))

With some additional changes (read hard coded values) I was able to successfully use bootc install to-disk and to-filesystem commands on ppc64le architecture.  I was also able to successfully verify boot of these images (disk device as well as qcow2) on IBM Power.

Cool! Feel free to send a PR, it's OK if it's not polished, we can iterate on it!

I have submitted following pull requests for initial set of changes
PR 497 against bootc-image-builder
PR 636 against bootc
Working on following changes:

images : Remove dependency on /boot/efi for ppc64le arch
bootc-image-builder compile time failure

cmd/bootc-image-builder/image.go:237:7: img.Users undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Users)
cmd/bootc-image-builder/image.go:238:7: img.Groups undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Groups)
cmd/bootc-image-builder/image.go:240:50: img.KickstartKernelOptionsAppend undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method KickstartKernelOptionsAppend)
cmd/bootc-image-builder/image.go:242:7: img.KickstartNetworkOnBoot undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method KickstartNetworkOnBoot)
cmd/bootc-image-builder/image.go:246:14: img.Users undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Users)
cmd/bootc-image-builder/image.go:246:36: img.Groups undefined (type *"github.com/osbuild/images/pkg/image".AnacondaContainerInstaller has no field or method Groups)

bootupd changes

Hi @sacsant
I am working on s390x support, and I just raised this PR https://github.com/osbuild/images/pull/758

images : Remove dependency on /boot/efi for ppc64le arch

I think my patch may be relevant to this issue.

Hi @sacsant
I am working on s390x support, and I just raised this PR osbuild/images#758

images : Remove dependency on /boot/efi for ppc64le arch

I think my patch may be relevant to this issue.

Indeed. Thanks @yoheiueda

mkfs.xfs -m uuid=2e332d8b-8cca-46df-8d63-9d874333cada -L root /dev/sdb3
Mounting /run/bootc/mounts/rootfs
Mounting /run/bootc/mounts/rootfs/boot
Initializing ostree layout
Initializing sysroot
ostree/deploy/default initialized as OSTree stateroot
Deploying container image...Freed objects: 118 bytes
done
ERROR Installing to disk: Installing bootloader: realpath failed with exit status: 1

Is there a restriction on running commands like realpath in bootc environment? If I manually run the command it does return correct output $ realpath /dev/disk/by-partlabel/PowerPC-PReP-boot /dev/sdb1

The failure is due to  non-existent directory
Initializing ostree layout
Initializing sysroot
ostree/deploy/default initialized as OSTree stateroot
Deploying container image...Freed objects: 118 bytes
done
realpath: /dev/disk/by-partlabel/PowerPC-PReP-boot: No such file or directory
ERROR Installing to disk: Installing bootloader: realpath failed with exit status: 1

I have submitted https://github.com/containers/bootc/pull/667 to include ppc64le specific boot loader install logic.

At this point, I think we've fixed everything that's needed in this specific project! There's clearly more work - such as enabling c9s bootc that are probably best tracked in e.g. https://gitlab.com/fedora/bootc/tracker/-/issues/15


Add support for loading and storing Decimal

Add initializer to MySQLData for Decimal values and a MySQLDataConvertible extension on Decimal so it can be converted from and to string-form as expected by MYSQL_TYPE_{,NEW}DECIMAL.

We just need to add an extra case right here to support the decimal type.

Hey @tholo, you just merged a pull request, have a coin!
You now have 2 coins.


Unable to set n_latent for PoissonVI

Hello,
Thanks for your help in the recent months regarding other issues.
I have been testing poissonvi and noticed that I am unable to set n_latent for the model prior to training. It seems to always use the default calculation, both in the pre-release and the recent version from yesterday.
I was wondering if I am missing something and this is by design or a potential bug.
Let me know if you need to see an example, thanks.
@lauradmartens

Hi @shahrozeabbas, sorry about this issue. Indeed, it looks like the model does not correctly apply a user-supplied n_latent. I'll go ahead and fix this and release it with 1.1.1.

@shahrozeabbas Just released the fix with 1.1.1, let me know if this works on your end!

Working as expected, thanks so much! @martinkim0


organismQuantity is not interpreted by GBIF

I have just discovered thanks to the early alert web application that something goes wrong with organismQuantity, see screenshot from
https://www.gbif.org/occurrence/3761877057

This is not an isolated example. This is another one where value "o" is not interpreted:
https://www.gbif.org/occurrence/3761870387

@peterdesmet, maybe can you know the reason why this happens and fix it? Or @LienReyserhove as backbup? THanks for helping me.

I think this should be reported at GBIF.


Increase initial delay from 0ms to 10ms in LimitedExponentialBackoff

Having 0ms as a first delay seems a bit useless.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6a9cf81). Click here to learn what that means.
The diff coverage is 84.61%.

@@            Coverage Diff            @@
##             master    #5951   +/-   ##
=========================================
  Coverage          ?   83.09%
  Complexity        ?    12364
=========================================
  Files             ?     1429
  Lines             ?    46739
  Branches          ?     5739
=========================================
  Hits              ?    38839
  Misses            ?     5229
  Partials          ?     2671

Impacted Files
Coverage Δ
Complexity Δ

...ava/io/crate/action/LimitedExponentialBackoff.java
76.92% <84.61%> (ø)
4 <3> (?)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a9cf81...ff174d5. Read the comment docs.


SEO - add missing descriptions

We need to divide and conquer and over time add the missing descriptions for SEO purposes.
Assigning to the current milestone, so we continuously work on this as a team.
Missing Meta Description.xlsx
Excel spreadsheet with missing descriptions attached.

I think we could split the folders between the 4 of us:
@BillWagner - csharp
@rpetrusha - visual-basic
@mairaw - framework, fsharp and core
@JRAlexander - standard
Submit a few/week so we can make progress towards adding descriptions for all .NET topics.

@mairaw I think this is done now?  If you agree, we can close it.

Unfortunately not @BillWagner. A lot of topics still don't have descriptions. Let me see if I can find updated data.

I lowered the priority for now and the spreadsheet should still be pretty accurate. The global metadata changes wouldn't impact missing descriptions. These have to be individually written for each article.


please use cmake.txt

hi 👍
This is good project,can u use cmake profile and set up linux,pls give me doc

I have never written code on other platform, so it will be late.


Use JSON notation for CMD's arguments in Dockerfile

Reference - Best practices for writing Dockerfiles:

https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#cmd

CMD should almost always be used in the form of CMD ["executable","param1", "param2"…]

Coverage remained the same at 95.192% when pulling 7ad819528e141b16bd1c2daf710abe7596f44e84 on PeterDaveHello:RefactorDockerfile into 4a85c52776bbc5cfecbe2a4eec4c68b54011c259 on cla-assistant:master.


Release/5.0.0

I hope I did this right...

Thanks @kab163,
I did not have time to review all 244 files.  But as long as the recipe was followed, I am okay with this.

Thanks @kab163,
I did not have time to review all 244 files. But as long as the recipe was followed, I am okay with this.

Yea haha, the "initial release modifications" commit has all the release-specific stuff - but yea I just followed the confluence recipe. (https://github.com/LLNL/Umpire/pull/499/commits/9b30e8cfae2a0cfaa06e4a3a6f0b48ea0ad29704)

You can visit this url to see the release-specific changes: https://github.com/LLNL/Umpire/compare/develop...release/5.0.0


Add ILocIndexer.

This PR adds loc property for DataFrame and Series.
The limitation is that the row access is only allowed to .iloc[:10, ...] (limit(10)) or .iloc[:, ...] (get all rows).
Resolves #247.

Codecov Report

Merging #364 into master will increase coverage by 0.06%.
The diff coverage is 92.18%.

@@            Coverage Diff             @@
##           master     #364      +/-   ##
==========================================
+ Coverage    94.4%   94.46%   +0.06%
==========================================
  Files          36       36
  Lines        3646     3743      +97
==========================================
+ Hits         3442     3536      +94
- Misses        204      207       +3

Impacted Files
Coverage Δ

databricks/koalas/missing/frame.py
100% <ø> (ø)
:arrow_up:

databricks/koalas/missing/series.py
100% <ø> (ø)
:arrow_up:

databricks/koalas/generic.py
95.34% <100%> (+0.16%)
:arrow_up:

databricks/koalas/tests/test_indexing.py
87.5% <88.13%> (+2.24%)
:arrow_up:

databricks/koalas/indexing.py
92.69% <95.38%> (+1.78%)
:arrow_up:

databricks/koalas/__init__.py
88.88% <0%> (-3.71%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3cffb28...8cfdd08. Read the comment docs.

+1 ! sorry @ueshin, seems I caused the conflict. Let's get this in first before my other PRs.

@HyukjinKwon no problem! that happens!


Adds AMIUpdater.

Overview
This PR Adds AMIUpdater. A README is forthcoming in a future PR.

I need more :coffee:. Disregard this PR in favor of #273


Visualizers should be able to use more than one sequence at a time

Visualizers should be able to call and interact with several sequences.  This could be part of a new UI refactor.

Closing as duplicate of #32


[Queston] Using with Jwplayer

How would you use this with jWplayer?

no help on this?

Hi!
Sorry I was busy with work.
Here is example with JW Player: https://github.com/Dador/JavascriptSubtitlesOctopus/blob/master/example/jwplayer.html


Update ASM workshop post-IstioCon 2022

[X] New title: Distributed services with Managed Anthos Service Mesh (ASM)
[X] Move Enforce policies section at the end, as optional
[X] istio-injection=enabled instead of istio.io/rev=asm-managed to simplify the sidecar injection process
[X] Fix ServiceAccount for transaction-history and userservice (no issues with original workshop, but by anticipation of AuthorizationPolicies
[X] fleet instead of hub
[X] Simplify the experience by creating the Namespaces with one command + by removing the -n parameter with any kubectl apply -f command (namespace field for any resources in YAML files)
[X] Both GKE and ASM are in Rapid channel instead of Regular
[x] Update the ControlPlaneRevision installation way by gcloud Fleet API instead
[x] Add AuthorizationPolicies in Policies
[x] Add Sidecars in Services discovery

Ready for your merge @ckim328 and/or @NimJay. No need to spend too much time in the review, it's already merged/deploy in the Qwiklab instance).


rri-203-1.md (What is Fairness?)

The following root file has been created:

Title: What is Fairness?
Module: Fairness
Skills Track: Responsible Research and Innovation
Section: 1

Tasks

[x] Review root file (Clau)
[x] Answer comments (Chris)
[ ] Draft web version (Clau)
[ ] Review web version (Chris)
[ ] Create slides (Chris)
[ ] Review slides and draft script (Clau)

Link to file: https://github.com/alan-turing-institute/turing-commons/blob/drafts/drafts/rri-skillstrack/rri-modules/root-files/rri-203-1.md

No comments for you to answer Chris :)
I do think this section is looking really good as an introduction to fairness!

@ClauFischer: not sure if you have started drafting the main files yet, but I made some edits to the root file while reviewing the content. Only small ones, but will need a review if you have started on the next stage of drafting.


An unknown error occurred. Directory is already a symlink.

      Error: An unknown error occurred. Please file a bug report at https://github.com/squattingmonk/nasher/issues using the stack trace info below:
nasher.nim(115)          nasher
unpack.nim(260)          unpack
os.nim(2557)             createDir
os.nim(2526)             existsOrCreateDir
Error: unhandled exception: Failed to create 'framework' [IOError]

Which is normal, framework is a symlink.

Hmm... This function is supposed to follow symlinks. I will do some testing and may need to report upstream to Nim.

Come to think of it, framework pointed to an unexisting directory. So it's a very minor bug.

Ah, okay. mkdir fails if a broken symlink of the same name is in the path, so this is expected behavior.


List test

This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Added test suite for frost-list
Updated repo to follow new convention guidelines
Updated usage to Ember.typeOf()
Removed unused method from frost-list-core.js

Changes Unknown when pulling 41612d686f86c9a4678c952dc9257b9ee70ed262 on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling c3fd9674c35e9dfaa0400090d5dc5c0c96574927 on juwara0:listTest into ** on ciena-frost:master**.

I am working on a few more tests to cover util.js and floor helper. Do not merge.

Changes Unknown when pulling 2de972ea196b89b63d2876c69f10d00941e6288a on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling 2de972ea196b89b63d2876c69f10d00941e6288a on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling ee21ea815a0ca416f92f1c772bbd1142f37b691f on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling ee21ea815a0ca416f92f1c772bbd1142f37b691f on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling ee21ea815a0ca416f92f1c772bbd1142f37b691f on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling b72953b651e0b0c6cffc845992e5108a14e7dcca on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling b72953b651e0b0c6cffc845992e5108a14e7dcca on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling ed9076291edc2ea97cbda11a4e42c8e4eae72caf on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling ed9076291edc2ea97cbda11a4e42c8e4eae72caf on juwara0:listTest into ** on ciena-frost:master**.

Changes Unknown when pulling a32c6492b8a794cd4defc24b2b90abf39b91f110 on juwara0:listTest into ** on ciena-frost:master**.

Coverage increased (+39.7%) to 94.118% when pulling c999650bbb22a3a00ad7f8e9d4a56061dd4717c1 on juwara0:listTest into acca2eba5d1a9439072151042119c88b386b0d34 on ciena-frost:master.

👍

Coverage increased (+39.7%) to 94.118% when pulling 9edfd096a3e03b3baa939409b7ce2c5bcc049469 on juwara0:listTest into acca2eba5d1a9439072151042119c88b386b0d34 on ciena-frost:master.


Release: hwc-buildpack (08-08)

Release reminder for hwc-buildpack
The ideal release date window for this buildpack starts on: 08-08 and ends on 08-13.

See diff from latest version and validate if a release is required.
Make sure the latest commit on  has passed tests on the CI
Refer release instructions. (private link)

nothing to release


feat: update cli with include-existing-events for creating batch exporter

…rters

:tada: This PR is included in version 1.16.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


LC0027: Page.Run(Modal) must be implemented through the Page Management codeunit from the Base Application.

Based on the idea: https://github.com/StefanMaron/BusinessCentral.LinterCop/discussions/258 Page.RunModal(0, ...) can be implemented through the "Page Management" codeunit
There are some limitations on the Page Management code unit, so I've included all the exceptions that I could think of. See the different scenario's below.
codeunit 50100 MyCodeunit
{
    local procedure TestFunction()
    var
        CustomerRec: Record Customer;
        CustomerCard: Page "Customer Card";
        PageManagement: Codeunit "Page Management";
    begin
        // Do nothing (no Record present)
        Page.Run(Page::"Customer Card");

        // Raise the LC0027 rule
        Page.Run(Page::"Customer Card", CustomerRec);

        // Raise the LC0027 rule
        Page.Run(Page::"Customer Card", CustomerRec, CustomerRec.FieldNo(Name));

        // Do nothing (Page has been specific declared as a variable)
        CustomerCard.Run();

        // Do not raise the LC0027 rule (no support for action return)
        if Page.RunModal(Page::"Customer Lookup", CustomerRec) = Action::LookupOK then;

        // Do not raise the LC0027 rule when the PageID come from a Record
        Page.Run(CustomerRec.Priority, CustomerRec);
    end;
}

page 50100 MyPage
{
    local procedure DoPageBackgroundTask()
    var
        TaskIdCalculateCue: Integer;
    begin
        // Do not raise a LC0027 rule on running a page for PBT
        CurrPage.EnqueueBackgroundTask(TaskIdCalculateCue, Codeunit::"AAD Application Interface");
    end;
}

To my knowledge, pagemanagement.pagerun would not work if the source table does not have a lookuppage assigned (and the getconditionalcardpageid does not return any value either). The rule can't detect these scenario's, but might be good to list this case as a possible exception on the wiki page.
https://github.com/StefanMaron/BusinessCentral.LinterCop/wiki/LC0027


Newest Nager.Date v1.5.0 Nuget package pulls in a ton of dependencies

I'm not sure why is that, but when I updated to this newest 1.5 package depends on
.NETStandard, Version1.1
NETStandard.Library (>= 1.6.1)
When installing, <package id="NETStandard.Library" version="1.6.1" targetFramework="net461" />
is added to my project, but as dependencies all of these packages are also pulled in, almost doubling my existing number of packages in my APS.NET MVC project:
<package id="Microsoft.NETCore.Platforms" version="1.1.0" targetFramework="net461" />
<package id="Microsoft.Win32.Primitives" version="4.3.0" targetFramework="net461" />
<package id="System.AppContext" version="4.3.0" targetFramework="net461" />
<package id="System.Collections" version="4.3.0" targetFramework="net461" />
<package id="System.Collections.Concurrent" version="4.3.0" targetFramework="net461" />
<package id="System.Console" version="4.3.0" targetFramework="net461" />
<package id="System.Diagnostics.Debug" version="4.3.0" targetFramework="net461" />
<package id="System.Diagnostics.DiagnosticSource" version="4.3.0" targetFramework="net461" />
<package id="System.Diagnostics.Tools" version="4.3.0" targetFramework="net461" />
<package id="System.Diagnostics.Tracing" version="4.3.0" targetFramework="net461" />
<package id="System.Globalization" version="4.3.0" targetFramework="net461" />
<package id="System.Globalization.Calendars" version="4.3.0" targetFramework="net461" />
<package id="System.IO" version="4.3.0" targetFramework="net461" />
<package id="System.IO.Compression" version="4.3.0" targetFramework="net461" />
<package id="System.IO.Compression.ZipFile" version="4.3.0" targetFramework="net461" />
<package id="System.IO.FileSystem" version="4.3.0" targetFramework="net461" />
<package id="System.IO.FileSystem.Primitives" version="4.3.0" targetFramework="net461" />
<package id="System.Linq" version="4.3.0" targetFramework="net461" />
<package id="System.Linq.Expressions" version="4.3.0" targetFramework="net461" />
<package id="System.Net.Http" version="4.3.1" targetFramework="net461" />
<package id="System.Net.Primitives" version="4.3.0" targetFramework="net461" />
<package id="System.Net.Sockets" version="4.3.0" targetFramework="net461" />
<package id="System.ObjectModel" version="4.3.0" targetFramework="net461" />
<package id="System.Reflection" version="4.3.0" targetFramework="net461" />
<package id="System.Reflection.Extensions" version="4.3.0" targetFramework="net461" />
<package id="System.Reflection.Primitives" version="4.3.0" targetFramework="net461" />
<package id="System.Resources.ResourceManager" version="4.3.0" targetFramework="net461" />
<package id="System.Runtime" version="4.3.0" targetFramework="net461" />
<package id="System.Runtime.Extensions" version="4.3.0" targetFramework="net461" />
<package id="System.Runtime.Handles" version="4.3.0" targetFramework="net461" />
<package id="System.Runtime.InteropServices" version="4.3.0" targetFramework="net461" />
<package id="System.Runtime.InteropServices.RuntimeInformation" version="4.3.0" targetFramework="net461" />
<package id="System.Runtime.Numerics" version="4.3.0" targetFramework="net461" />
<package id="System.Security.Cryptography.Algorithms" version="4.3.0" targetFramework="net461" />
<package id="System.Security.Cryptography.Encoding" version="4.3.0" targetFramework="net461" />
<package id="System.Security.Cryptography.Primitives" version="4.3.0" targetFramework="net461" />
<package id="System.Security.Cryptography.X509Certificates" version="4.3.0" targetFramework="net461" />
<package id="System.Text.Encoding" version="4.3.0" targetFramework="net461" />
<package id="System.Text.Encoding.Extensions" version="4.3.0" targetFramework="net461" />
<package id="System.Text.RegularExpressions" version="4.3.0" targetFramework="net461" />
<package id="System.Threading" version="4.3.0" targetFramework="net461" />
<package id="System.Threading.Tasks" version="4.3.0" targetFramework="net461" />
<package id="System.Threading.Timer" version="4.3.0" targetFramework="net461" />
<package id="System.Xml.ReaderWriter" version="4.3.0" targetFramework="net461" />
<package id="System.Xml.XDocument" version="4.3.0" targetFramework="net461" />

This is crazy, I don't know why it's happening, but I could deal with it.
Actually one of these packages had an earlier version in my projects:
<package id="System.Net.Http" version="4.0.0" targetFramework="net461" />
Maybe the fact that that is needed to be 4.3.0 causes all of the other packages to be pulled in. "NETStandard.Library" version="1.6.1" requires that 4.3.0 System.Net.Http? I don't know what to do. Because after all of these packages installed, my project is throwing a mysterious exceptions:
Exception thrown: 'System.MissingMethodException' in ThruThink.dll
Additional information: Method not found: 'Void System.Web.Http.HttpResponseException..ctor(System.Net.Http.HttpResponseMessage)'.

I'm not blaming this on Nager.Date, but I wonder if there's a way to adjust the dependency so it won't pull in packages.

Hi, i know i have update to visual studio 2017 and try the new project type .net standard but i not found any option to remove this dependencies. At the moment i suggest the 1.4 version.

Good info. Since the fix is about Thanksgiving, which is some time away (November) I can downgrade, but now that you mention Visual Studio 2017 maybe I should install that and see if that solves the problem. There's another package too which started to do this, so I cannot resist forever, I need to figure out what's happening.

VS 2017 install didn't help. Let's see if SO can come up with anything: https://stackoverflow.com/questions/42896662/why-method-not-found-void-system-web-http-httpresponseexception-ctor-after


Global fixes for minor updates & corrections

What type of PR is this?
Add one of the following kinds:

bug
correction

What this PR does / why we need it:
(all) Correct YAML examples to use upper case enum of areaType
(geofencing) Rename in the OAS SubscriptionEventType to NotificationEventType
(retrieval) Fix format for attribute lastLocationTime in location retrieval
(retrieval & verification) Revise Description to Meet GDPR Compliance - REMOVAL OF " Location-based advertising" in Documentation (sentence from @iamdatanick  proposal)
Which issue(s) this PR fixes:

Fixes #136
Fixes #139
Fixes #137
Fixes #135
Special notes for reviewers:
Changelog input
 Correct YAML examples to use upper case enum of areaType
-For geofencing: Rename in the OAS SubscriptionEventType to NotificationEventType
-For Retrieval:  Fix format for attribute lastLocationTime in location retrieval
Revise Description to Meet GDPR Compliance - REMOVAL OF " Location-based advertising" in Documentation

Additional documentation
This section can be blank.
docs

Should we create the rc2 now? or do we wait after the next meeting?

I think, if this PR is merged we can create the RC2

Fixed the line 204 - sorry Akos for the misunderstanding - for me once merge we can create RC2.


Fix upgrade docs

This PR fixes upgrade instructions that suggest the use of --reuse-values when upgrading Helm chart version. When --reuse-values is passed, the default values.yaml packaged in the Helm chart is ignored. As a result, if it contains some new default values that are used in templates, upgrade to a new version will fail with a templating error. We're not always adding defaults in the templates themselves.
It's ok to use --reuse-values when upgrading appVersion only.
Checklist

[ ] I have added unit tests
[ ] I have applied the change to all applicable products
[ ] The E2E test has passed (use e2e label)
[ ] (Atlassian only) Internal Bamboo CI is passing

@nanux yes you got it right, --reuse-values breaks update from 1.5.0 to, say, 1.8.1 because of that.


SearchSortDropdown [Vue warn]: Invalid default value for prop "value"

Step to reproduce:

go to landing
switch to bsx chain
error in console: [Vue warn]: Invalid default value for prop "value": Props with type Object/Array must use a factory function to return the default value.

found in
--->  at components/rmrk/Gallery/Search/SearchSortDropdown.vue

👋


Documentation request: how to configure vue-cli to build non src/App.vue files so they can be mounted directly in main.js

Version
4.1.1
Reproduction link
https://gitlab.com/SumNeuron/vuetify-rollup-alcarte
Environment info
Environment Info:

  System:
    OS: Linux 4.16 Ubuntu 16.04.6 LTS (Xenial Xerus)
    CPU: (40) x64 Intel(R) Xeon(R) Gold 5115 CPU @ 2.40GHz
  Binaries:
    Node: 11.10.0 - ~/.nvm/versions/node/v11.10.0/bin/node
    Yarn: Not Found
    npm: 6.7.0 - ~/.nvm/versions/node/v11.10.0/bin/npm
  Browsers:
    Chrome: 77.0.3865.120
    Firefox: 70.0.1
  npmGlobalPackages:
    @vue/cli: 4.1.1

Steps to reproduce

Created empty project repo: mkdir test && cd test
Created fresh project via vue-cli: vue create dev
Added Vuetify to project: cd dev && vue add veutify
Pulled config files from test/dev up to test
Updated vue.config.js to point to new location:

//vue.config.js
{
//...
pages: {
    index: {
      entry: 'dev/src/main.js',
      template: 'dev/public/index.html',
      filename: 'index.html',
    }
  },
}

Made a very simple component CountButton.vue which is just a wrapper of the Vuetify component <v-btn> imported a la carte (see test/dev/components/CountButton.vue)
tried mounting multiple instances of the component CountButton in dev/src/main.js e.g.

// dev/src/main.js
// ...
import CountButton from './components/CountButton.vue'
new Vue({
  store,
  vuetify,
  render: h => h(CountButton)
}).$mount('#app')

new Vue({
  store,
  vuetify,
  render: h => h(CountButton)
}).$mount('#app2') // <--- copy pasted
 and gave it new id "app2" in `public/index.html`

Noticed that direct mounting this way does not work as expected (CountButton.vue was mounted and data was reactive in Vue inspector, but not the template)
Updated dev/src/App.vue to contain just CountButton.vue
Tried the multi-mount, and that works.
Copy pasted the file dev/src/App.vue to dev/src/App0.vue and tried mounting the App0 component. This failed in the same manner as (8) as the vue-cli targets dev/src/App.vue as the entry point.
Tried to then convert component to a WebComponent by adding the following package.json

"build:wc": "npx vue-cli-service build --target wc --name pub 'dev/src/components/*.vue'",

inspected the resulting dist/pub.min.js and dist/demo.html files and noticed the component regained its dynamic template - error from (8) - but lost all styling

Thought that this may be due to Vuetify styles not being bundled with the the Vuetify component

Setup rollup to try and force the CSS to be bundled with the component (see rollup.config.js, dev/src/rollup.entry.js and package.json)

then I rolled up npm run build:r

then I tried to use the component: (dist/demo.html)

Am back to where I was at step (13); namely, I have WebComponents, but despite bundling vuetify.min.css with the CountButton.vue component, but no styling.

This belabored process raises two questions:

How to mount multiple components (not App.vue) in main.js from vue-cli3
How to rollup Vue Components that are built on top of Vuetify.js to keep their styling and functionality outside of

The former is related to vue-cli.
ideally I would be able to, in src/main.js import my components / subapps and mount them to any divs I point them to in public/index.html
What is expected?
I can mount any component (from src/components) imported in main.js` and they will work correctly
What is actually happening?
Some functionality of the components are lost

See repo and long commnets above

There's nothing special to consider, you can mount any component.
I would rather suspect thatyour issue is completely related to Vuetify, but can't take a look at the code right now.
Did you try to mount a non-vuetify component ?

Can't reproduce the first issue.
Don't have the time to reproduce the second one.
Please boil down the reproduction to a minimal one.

@sodatea @LinusBorg Yes. To simply things, I created a second, smaller MWE repo as I tried to overcome many problems in the first.
Here is the smaller repo specifically for the first problem: https://gitlab.com/SumNeuron/vue-cli-multi-mount
What did I do?

mkdir vue-cli-multi-mount
cd vue-cli-multi-mount
vue create dev
cd dev
vue add vuetify
move all config files from vue-cli-multi-mount/dev to vue-cli-multi-mount
updated vue.config.js to point to the new location of all components.
created 5 test components:

VuetifyBtn: vbtn used wrapped in div
VuetifyBtnVApp: v-btn used wrapped in v-app
VuetifyBtnALaCarte: v-btn imported a la carte, wrapped in div
VuetifyBtnALaCarteVApp: v-btn imported a la carte, wrapped in v-app
WrapBtn: a div over an html button

updated public html to have the mount points:

       Vuetify Btn

       Vuetify Btn in VApp

       Vuetify Btn A La Carte

       Vuetify Btn A La Carte in VApp

       Wrapper over normal button

updated main.js to load components and mount them:

import Vue from 'vue'
// import App from './App.vue'
import VuetifyBtn from './components/VuetifyBtn.vue'
import VuetifyBtnVApp from './components/VuetifyBtnVApp.vue'
import VuetifyBtnALaCarte from './components/VuetifyBtnALaCarte.vue'
import VuetifyBtnALaCarteVApp from './components/VuetifyBtnALaCarteVApp.vue'
import WrapBtn from './components/WrapBtn.vue'
import store from './store'
import vuetify from './plugins/vuetify';

Vue.config.productionTip = false

new Vue({
  store,
  vuetify,
  render: h => h(VuetifyBtn)
}).$mount('#btn1')
new Vue({
  store,
  vuetify,
  render: h => h(VuetifyBtnVApp)
}).$mount('#btn2')
new Vue({
  store,
  vuetify,
  render: h => h(VuetifyBtnALaCarte)
}).$mount('#btn3')
new Vue({
  store,
  vuetify,
  render: h => h(VuetifyBtnALaCarteVApp)
}).$mount('#btn4')
new Vue({
  store,
  vuetify,
  render: h => h(WrapBtn)
}).$mount('#btn5')

ran npm run serve to ensure everything works in dev. All good here
ran npm run build
opened dist/index.html to see 100% disappointment with nothing there.

To clarify, the issue is for production in that npm run build only mounts what is specifically targeted in App.vue
@LinusBorg

opened dist/index.html to see 100% disappointment with nothing there.

...but that file contains all the mount points and includes the correct javascript file that will mount to those mount points.
So what specifically is your disappointment about?

Oh, did you doubleclick the dist/index.htmlfile and expect that to work? It won't, as we build ith absolute paths by default, which means opening the file via file:// will not work as that requirews relative paths.
so now imports for e.g. the vendors-hash.js chunk fail.

@LinusBorg correct I double clicked what I was hoping to be a static SPA dist/index.html. How can I:

have it build without absolute paths
serve index.html for production?
build a static site with the mount points?

I also just pushed a branch retool, which includes a rolluped version, where even the plan WrapBtn component is unfunctional complaining of
[Vue warn]: Error in nextTick: "TypeError: this.$root.$options.customElement is undefined"

which includes a rolluped version,

We will not debug rollup configs here. Vue CLI doesn't use rollup, so this it out of scope for a bug report unless you can show how this is because of something Vue CLI does.
Feel free to ask the community on discord or forum.vuejs.org for help regarding that.

have it build without absolute paths

https://cli.vuejs.org/config/#publicpath

serve index.html for production?

Explaining how to serve an index.html with a webserver is out of scope for a bug report. There's pleanty of tutorials available online, and our documentation offers deployment guides for various plattforms.

build a static site with the mount points?

I don't understand what you mean by that.

re rollup
Fair enough. Rollup was included as the webcomponents generated by

npx vue-cli-service build --target wc --name pub 'dev/src/components/*.vue'

also did not work

re publicPath
That allows local inspection of index.html which works as expected.

Re serve index.html
I understand that explaining how to serve index.html with a webserver is out of scope for a bug report but this is a documentation request. Similarly to the vue-cli, nuxt has npm run dev (npm run serve for vue-cli) and npm run build to build the production site. The difference is that nuxt also has npm run start to serve the built site, which vue cli does not have by default. Perhaps including it in package.json would be worth while?

There's no start command because vue-cli projects are not server-rendered, they are entirely client-side.

So I'll close this issue as the original problem was ansered with a relative public path.
You also mentioned something about web components but I don't see how that directly relates. So if this is a separate problem you are encountering, please open a new issue for that problem alone.

@LinusBorg ,
you said

So I'll close this issue as the original problem was ansered with a relative public path.

I am confused this thread ask for documentation can you explain why a relative path fixes that problem?
I am have the same problem trying to figure out how the build system works, I been trying to ssr with
vite-plugin-ssr which I think , breaks  "vue cli".
you said

Vue CLI doesn't use rollup,

It look to me that "vue cli" expect to use webpack but vite want to use roll-up.I often wounder why it doesn't use vite.
I been asking for documention on the build and using of "vue cli"  on  vite  and vite-plugin-ssr,  so far with out much help.  I been trying to figure out how all the pieces go together.  I like read documentations that you have but sadly I have not been able to figure it out. I been fight this for weeks now.
I coming to the conclusion  that even though Vite and vue( I thought where made by the same person)  They where not meant to work together with the "vue cli".  There no documentation that I could find for that.   All vue documentation seem to use "vue cli" tool making the "vuejs" documentations almost worthless without info for the build and use of  ssr.

It fixes the original issue ok insof as r as it uses Vitey which uses roll-up.
You seem to want to propose a whole architecture for spring multiple build systems, which sounds cool but likely will not make it into create-vue due to the insane complexity


how to use option --leases

i saw this option , and i dont see how to use  it ? can you provide a example ?

This is is just a proof of concept code. That was left over for testing purposes.


added emqx png icon

Signed-off-by: Stas Yakobov<EMAIL_ADDRESS>

wrong PR


Simple example calling a mutation on click and handling the response

I am playing around with mutations and would like to have a simple flutter widget that has a button.
When that button is pressed the mutation will be fired, and the button should show a loading state.
It is not clear to me, having been in and out of the documentation and github issues on how to accomplish this.
Can somebody help me in the right direction?
Here me fumbling around in the dark:
class HomeScreen extends StatefulWidget {
  const HomeScreen({super.key});
  @override
  State<HomeScreen> createState() => _HomeScreenState();
}

class _HomeScreenState extends State<HomeScreen> {
  GAnalyzeImageReq uploadRequest = GAnalyzeImageReq(
    (b) => b
      ..vars.base64 = '123' // As a hot-fix, I'm setting a dummy value here
      ..executeOnListen = false,
  );

  @override
  initState() {
    super.initState();

    // ideally I wish to listen to the stream here
    // and do something with the data depending if it's an error or not
  }

  @override
  Widget build(BuildContext context) {
    return FerryClientProvider(
      child: (ferryClient) => Expanded(
        child: Align(
          alignment: Alignment.center,
          child: FerryOperation(
            request: uploadRequest,
            builder: (context, response, error) {
              if (response != null && response.data != null) {
                final data = response.data!.analyzeImage;

                if (data != null) {
                  // now I have data, do something with it
                }
              }

              return AnalyzeImageButton(
                isLoading: response?.loading == true,
                onPressed: () async {
                  uploadRequest = uploadRequest.rebuild(
                    (b) => b..vars.base64 = base64Image,
                  );

                  ferryClient.requestController.add(uploadRequest);
                },
              );
            },
          ),
        ),
      ),
    );
  }
}

class FerryClientProvider extends ConsumerWidget {
  final Widget Function(Client client) child;

  const FerryClientProvider({super.key, required this.child});

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    final ferry = ref.watch(ferryProvider);

    return ferry.when(
      data: child,
      error: (error, stackTrace) {
        return Text('Error: $error');
      },
      loading: () {
        return const CircularProgressIndicator();
      },
    );
  }
}

@knaeckeKami I know you're probably very busy, but if you ever get a few minutes, I would love your input on this one

Did you check https://ferry.gql-dart.dev/docs/flutter-operation-widget#usage-with-mutations ?
If yes, is there anything concrete you have question for?

Yes thank @knaeckeKami - I did review the whole documentation. Still, from that, it's not quite easy for me to understand how I can fire a single request on submit

Interesting, thanks @knaeckeKami - I'll look into it again when working on the project, and report back. Thanks!

@knaeckeKami If it's awaited, will the loading state also be maintained? E.g. a prop on the button.

you'll need to use basic state management approaches (setState, FutureBuilder...) for that.


SNOW-947589: Error When Running Application "No secrets files found. Valid paths for a secrets.toml file are: /home/udf/.streamlit/secrets.toml, /.streamlit/secrets.toml"

SnowCLI version
2.0.0-dev
Python version
3.9.6
Platform
macOS-13.5.2-arm64-arm-64bit
What happened
When I try to run my app, it cannot find the secrets.toml file. Where and how do I upload the file?

Console output
No response
How to reproduce
No response

@sfc-gh-zblackwood Any thoughts on what the command should look like to upload the secrets.toml file? I tried using the same command as you suggested for the functions file, but I still get the same error above.

How does it relate to snowcli?

Closing this one as an issue with Streamlit not snowcli.


Dark Mode To Light Mode Toggler in JS

I would like to work on adding a dark mode to a light mode toggler using JS.
I request you to, please assign this task to me under the second phase of HCSSOC.

Already we have


Web - Resources Scheduled for Termination View hanging with large csv

Hello thanks for the work on this project, it's great!
Currently I'm running into an issue when viewing the webpage when we have a large number of items on the termination list (~20k+).
What happens is that when you click on the box to view the resources, it will pull up the modal and start spinning as usual.  It will then hang and not finish.  It seems to fire off the lambda function and that runs successfully, however it is never presented on the webpage.  If you wait a while, occasionally I've gotten a error:
Aw, Snap!

Something went wrong while displaying this webpage.

Error code: Out of Memory

or in the chrome console:
index.js:198          GET https://amend.. 2022%2F07%2Faws_resources_scheduled_for_termination_2022_07_07_17_30_04.csv net::ERR_FAILED 504
We run this on multiple accounts, and most of the accounts are fine; however we have a few accounts with excessive amount of log groups that get populated (the csv file has over 18k listed for one, up to 69k).
At first I thought it was some of the lambdas memory, increasing them didn't help.  Also tried increasing the ecs task, and didn't seem to help as well.  Currently our workaround has been to disable the specific service with all of the resources (log groups) for the affected accounts.
Not sure yet if this is a limitation on the s3 website or elsewhere.  Currently looking into it and inquiring with AWS as well for the s3 website limitations.
Thanks and take care!

Hey @kjblanchard. Thanks for raising this issue. I didn't think I'd ever see an execution log of that size :) but here we are.
I've made a test execution log of 20K records and whilst it does take time to load from S3 and render in Chrome, I can see that anything larger will probably kill the browser.
Let me look into this a little bit longer to see if we can do something with the DataTable that displays the rows.

So... played around with this today. I think I managed to make it work using DataTables native functionality. Instead of creating the table in HTML then converting that table to a DataTable, we instead pass the data to DataTable which only loads records visible to the other. This should hopefully prevent Chrome from hitting the out of memeory error it did before.
Could you do me a favour to pull the change from https://github.com/servian/aws-auto-cleanup/tree/large-execution-log-support and test it for me?

I also noticed this error in the "default-log-execution-read-api" lambda CW logs:
[ERROR] [1657552536217] LAMBDA_RUNTIME Failed to post handler success response. Http response code: 413.
According to the following page, it seems this might be a limitation of lambdas invocation payload.  My CSV file is just above 6MB.
https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html

Hmmm depending on how old your previous instance was, I would suggest you update all 3 modules, app, api, and web. You shouldn't get any CORS issues tbh.
Regarding the 6MB response limit, that is still in place. A 20K file was about 3MB for me, so anything larger than say a 35/40K would probably exceed that limit. Not much I can do about that without re-architecting the whole app. Only solution would be to not clean CloudWatch Logs as you've been doing already. Sorry about that.

@kjblanchard I just pushed a change https://github.com/servian/aws-auto-cleanup/commit/0827dc62cdc1b15503421f68317f2fa3476ca9de that should hopefully solve this issue.
Basically, to work around Lambda's 6MB response payload limitation, I've compressed the output payload using Zlib for execution logs greater than 10K lines. We then decompress using Zlib on the frontend. I've managed to work with a file over 100K lines, at around 15MB in S3... so hopefully this should help you too.
Let me know how you go.

Perfect, you rock.
I've grabbed that commit and pushed out to our accounts and I'm able to get the CSV file now when attempting to view the list on the page, thanks for adding in zlib/compression!  I'm getting a Error code: RESULT_CODE_HUNG though when it is trying to display the results.  Seems like my cpu gets pegged at 100% prior.  I saw there was a couple of commits after 0827dc6 so I'm going to go ahead and try adding the following commits and see if it fixes it and will update here.
Again, thanks a lot!

@kjblanchard I know this may be hard for you to do, but do you think you could share one of your execution logs with me? De-identify everything in there and if you'd like, you can email me a link directly instead of posting it here (mlevit at gmail dot com).
Your logs are different to mine and I'd love to test with yours directly.

OK so I've pushed more log processing into the backend with this commit https://github.com/servian/aws-auto-cleanup/commit/bc6284e45b0de547fa9a6f4aff0e6b7d0d956067.
The frontend would receive the log, calculate the stats and do create a smaller log list with just the columns necessary for the table. Instead of doing that all in the frontend, I've moved that into the Lambda and returned it in the response JSON. This should hopefully 🤞 reduce the strain on the browser.
Give it a go and see how you go.

@kjblanchard any chance you've had time to test this out?

Hey, sorry about not responding here.  I've added in the latest changes and still seeing the issue.  I went ahead and de-identified the csv file, but just going through "approvals" to be able to send out the csv file.  Thanks for reaching out about it.

@mlevit Finally was able to get one.  Will send it to your email now.  Thanks again for everything


vagrant-hostmanager don't support override feature ?

I've this configuration, with hostmanager configured only for "virtualbox"
Vagrant.configure("2") do |config|
    config.vm.hostname = "foobar"
    config.ssh.forward_agent = true

    config.vm.provider "virtualbox" do |v, override|
        override.vm.box = "debian-wheezy64"
        override.vm.box_url = "...."
        override.hostmanager.enabled = true
        override.hostmanager.manage_host = true
        override.hostmanager.ignore_private_ip = false
        override.hostmanager.include_offline = true
        override.hostmanager.aliases = ["foobar.example.com", "example.com"]

        override.cache.auto_detect = true
        override.vm.network :private_network, ip: "<IP_ADDRESS>"
    end
    config.vm.provider :lxc do |v, override|
        override.vm.box = "fgrehm/wheezy64-lxc"
        override.vm.box_url = "https://vagrantcloud.com/fgrehm/wheezy64-lxc"
    end
    config.vm.provider :lxc do |lxc|
        lxc.customize "network.type", "veth"
        lxc.customize "network.link", "lxcbr0"
        lxc.customize "network.hwaddr", "22:90:e8:45:3c:34"
    end
end

If I launch "vagrant up" on this configuration, I've no hostname configured in /etc/hosts
But it's work with this configuration :
Vagrant.configure("2") do |config|
    config.vm.hostname = "foobar"
    config.ssh.forward_agent = true
    config.hostmanager.enabled = true
    config.hostmanager.manage_host = true
    config.hostmanager.ignore_private_ip = false
    config.hostmanager.include_offline = true
    config.hostmanager.aliases = ["foobar.example.com", "example.com"]

    config.vm.provider "virtualbox" do |v, override|
        override.vm.box = "debian-wheezy64"
        override.vm.box_url = "...."

        override.cache.auto_detect = true
        override.vm.network :private_network, ip: "<IP_ADDRESS>"
    end
    config.vm.provider :lxc do |v, override|
        override.vm.box = "fgrehm/wheezy64-lxc"
        override.vm.box_url = "https://vagrantcloud.com/fgrehm/wheezy64-lxc"
    end
    config.vm.provider :lxc do |lxc|
        lxc.customize "network.type", "veth"
        lxc.customize "network.link", "lxcbr0"
        lxc.customize "network.hwaddr", "22:90:e8:45:3c:34"
    end
end

I think that vagrant-hostmanager don't support override feature ?
Best regards,
Stephane

I have this same issue.  I've tried using override and also just defining it in the individual machine.


Give write permissions to the deploy workflow

coverage: 100.0%. remained the same
when pulling b26b40a78023bffca8f45d280a9f782317c2fdce on give_write_permissions_to_the_deploy_workflow
into a9adcd9a48cb6cb2ad3104c22b3393d7410a43be on master.


CodeBlock issue on safari

Current Behavior
Could not find the language 'plaintext', did you forget to load/include a language module?
Error: Unknown language: "plaintext"
at _highlight (/Users/bhanu/repos/dev/my-skeleton-app/node_modules/highlight.js/lib/core.js:2107:13)
at Object.highlight (/Users/bhanu/repos/dev/my-skeleton-app/node_modules/highlight.js/lib/core.js:1720:9)
at /Users/bhanu/repos/dev/my-skeleton-app/node_modules/@skeletonlabs/skeleton/dist/utilities/CodeBlock/CodeBlock.svelte:41:37
at Object.$$render (/Users/bhanu/repos/dev/my-skeleton-app/node_modules/svelte/src/runtime/internal/ssr.js:156:16)
at eval (/Users/bhanu/repos/dev/my-skeleton-app/src/routes/dashboard/+page.svelte:49:835)
at Object.$$render (/Users/bhanu/repos/dev/my-skeleton-app/node_modules/svelte/src/runtime/internal/ssr.js:156:16)
at Object.default (/Users/bhanu/repos/dev/my-skeleton-app/.svelte-kit/generated/root.svelte:45:41)
at Object.default (/Users/bhanu/repos/dev/my-skeleton-app/src/routes/+layout.svelte:81:47)
at /Users/bhanu/repos/dev/my-skeleton-app/node_modules/@skeletonlabs/skeleton/dist/components/AppShell/AppShell.svelte:54:64
at Object.$$render (/Users/bhanu/repos/dev/my-skeleton-app/node_modules/svelte/src/runtime/internal/ssr.js:156:16)
Expected Behavior
The default codeblock language type plaintext doesnt work on safari.
Steps To Reproduce
No response
Link to Reproduction / Stackblitz
No response
More Information
No response

Hey @pvbhanuteja, we talk about setting up the requirements for Highlight.js here. Including steps for setting up the language modules that you require for your project:
https://www.skeleton.dev/utilities/codeblocks#configure-your-project
As far as I can recall, Highlight doesn't provide a module for plaintext (read no language specified). In the case of Skeleton we typically need something like this for terminal commands. So we opt for shell.
import shell from 'highlight.js/lib/languages/shell';
hljs.registerLanguage('shell', shell);

All in all, just make sure you have a language prop set and the correct module registered.
See Highlight's docs for more infoformation:

https://highlightjs.org/#usage
https://highlightjs.readthedocs.io/en/latest/supported-languages.html

Hey @endigo9740 thanks for the response. Is there anyway I can skip the language prop. I don't want shell badge in my python/other lan codes.

If you're using Python or other languages, then install the appropriate language modules for those.
Python would be something like this:
import shell from 'highlight.js/lib/languages/python';
hljs.registerLanguage('python', python);


[Rails] Allow super admin to reset passwords for community admin users

When logged in as a super admin (e.g. via username<EMAIL_ADDRESS>and password terrastories per the default seed data), we are able to view the communities that are located on the Terrastories instance, as well as the users registered to those communities. Let's make it possible for the super admin to reset a password for any of the users on a community with admin credentials.
User story: if a Community administrator loses their password, the super admin should be able to reset that for them.

I would like to work on this. Kindly assign it to me

@hassyyy done! Thanks for wanting to work on this.

Hi @hassyyy just checking if you still wanted to work on this?

Hey @rudokemper
I couldn't find time to work on this. Please assign to someone else. Sorry for the inconvenience

If this one is back on the market, i'd love to take a crack at it as well.

thanks @DuldR !

Thanks @DuldR for the work until now - the draft PR is open at #904 if anyone else wants to continue the work.


Improve typography with SmartyPants-like rich text processing

Issue Summary
Wagtail doesn't automatically replace "dumb quotes" " with “smart quotes” “ + ”
Steps to Reproduce
Enter some text with dumb quotes into the rich text editor
Today: On the published page, see the dumb quotes
When fixed: See smart quotes
Longer explanations about this can be found around the web, eg https://www.fastcodesign.com/3018353/be-smart-dont-use-dumb-quote-marks
A simple plugin for basic CMS that does this, from 2004, is https://daringfireball.net/projects/smartypants/

Thanks for the suggestion @davelab6!
As a policy, Wagtail does not impose any opinions about how content is presented on the site front-end - that's entirely down to you as a site developer, and your use of the Django template language. As such, I'd consider this feature to be out of scope of Wagtail itself - it's something you could achieve through a library such as django-typogrify, though.

There is (very early) discussions of whether this is a desirable feature in a new rich text editor we want to introduce in an upcoming release of Wagtail, over at https://github.com/springload/draftail/issues/53.
Opinions welcome.

We're still "pre-release" at the moment while we experiment with this, but here's a small wagtail plugin that will do smartquote replacements on all text input fields on page-edit pages. https://github.com/nhsuk/wagtail-smartquotes/
We've identified a need to do smartquote replacements to help our editors use correct punctuation. I think the right place to do this is in the editor and not on the front-end.


Hamburger menu not working as expected

Nice skeleteon/theme!
When I view it on my phone, het hamburgermenu only displays 1 entry: Home.
Can it be adapted that it displays all menu-items?

This is not a bug.. The menu items are 'on-page' menu items, and it makes no sense to display those in a side menu.  Any other regular pages will be displayed in the menu.
A better option in this scenario is to turn off the side-menu completely by removing it, but it's there to allow for other pages to be added.

I agree with awrog's view that the hamburger menu's default behaviour is problematic. The hamburger menu replaces a full menu of modular pages with a mere redundant duplication of the Home link. If indeed it made 'no sense' to display the modular pages in the hamburger menu, then surely the same assertion would have to apply to the regular non-hamburger navigation in the first place: it wouldn't make any sense either.
In the hamburger menu, couldn't the modular page links be nested under the Home link, using indents to show their subsumption?